I have a v890 with a 4 port gig eth card running Solaris 9. I assume it is
called ce. Can someone send me a copy of their /etc/system,
/platform/sun4u/kernel/drv/ce.conf or any other file that is used
to configure a ce card? Thanx in advance.

In comp.sys.sun.hardware zion_curtain <fu@bar.com> wrote:
> I have a v890 with a 4 port gig eth card running Solaris 9. I assume it is
> called ce. Can someone send me a copy of their /etc/system,
> /platform/sun4u/kernel/drv/ce.conf or any other file that is used
> to configure a ce card? Thanx in advance.

Normal configuration is via 'ifconfig ce0 plumb' or by putting an IP or
hostname in /etc/hostname.ce0 and rebooting.

Is there some reason that you need to configure something else about the
card? I don't have a ce.conf or anything about it in /etc/system.

--
Darren Dunham ddunham@taos.com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >

Darren Dunham wrote:

> Is there some reason that you need to configure something else about the
> card? I don't have a ce.conf or anything about it in /etc/system.


What do u say is correct, but you need this file if you need to set some
parameters for CE configuration. You can found into EIS CDs the script
called S68net-tune where you can set with ndd command all what you wants
for your NIC.
Since some times Sun have excluded ce interface from this script and
have created this new configuration file ce.conf.
But i can tell you that you can continue to use the S68net-tune script
or simple script with ndd command.

Fabrizio I.

zion_curtain wrote On 01/17/06 15:13,:
> I have a v890 with a 4 port gig eth card running Solaris 9. I assume it is
> called ce. Can someone send me a copy of their /etc/system,
> /platform/sun4u/kernel/drv/ce.conf or any other file that is used
> to configure a ce card? Thanx in advance.

As pointed out by other posters, you would typically either plumb the
interface by hand OR create the /etc/hostname.ce0 file containing the
hostname of the system (preferred).

The only time you would need a ce.conf file (or /etc/system or
/etc/rc2.d/S68net-tune) is when you need to force speed and duplex
settings to your switch. By default, the sun interfaces will do
autonegotiation and assumes that your switch port is configured for
autoneg as well.

ML Starkey <martha.starkey@sun.com> writes:
> The only time you would need a ce.conf file (or /etc/system or
> /etc/rc2.d/S68net-tune) is when you need to force speed and duplex
> settings to your switch. By default, the sun interfaces will do
> autonegotiation and assumes that your switch port is configured for
> autoneg as well.

I believe the current IEEE standards for gigabit operation _require_
autonegotiation. You can force the settings, but you're generally on
your own if you do that. (And most people who do it end up hurting
themselves in the process.)

I don't think it's at all recommended.

--
James Carlson, KISS Network <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677

I can understand the frustration in overcoming a network engineer
hardcoding all their interfaces. The ce.conf file is a tricky beast to
say the least (if you read the docs that come with the controller, or
from docs.sun.com that seem to be wrong).

$ cat ce.conf
name="ce" parent="/pci@8,700000/pci@5/pci@0" unit-address="0"
adv_autoneg_cap=0 adv_100hdx_cap=0 adv_100fdx_cap=1 adv_1000fdx_cap=0
adv_10hdx_cap=0 adv_10fdx_cap=0 adv_1000hdx_cap=0 adv_100T4_cap=0;
name="ce" parent="/pci@8,700000/pci@5/pci@0" unit-address="1"
adv_autoneg_cap=1 adv_100hdx_cap=0 adv_100fdx_cap=0 adv_1000fdx_cap=1
adv_10hdx_cap=0 adv_10fdx_cap=0 adv_1000hdx_cap=0 adv_100T4_cap=0;
name="ce" parent="/pci@8,700000/pci@5/pci@4" unit-address="2"
adv_autoneg_cap=1 adv_100hdx_cap=0 adv_100fdx_cap=0 adv_1000fdx_cap=1
adv_10hdx_cap=0 adv_10fdx_cap=0 adv_1000hdx_cap=0 adv_100T4_cap=0;
name="ce" parent="/pci@8,700000/pci@5/pci@4" unit-address="3"
adv_autoneg_cap=1 adv_100hdx_cap=0 adv_100fdx_cap=0 adv_1000fdx_cap=1
adv_10hdx_cap=0 adv_10fdx_cap=0 adv_1000hdx_cap=0 adv_100T4_cap=0;
name="ce" parent="/pci@9,700000/pci@4/pci@0" unit-address="0"
adv_autoneg_cap=0 adv_100hdx_cap=0 adv_100fdx_cap=1 adv_1000fdx_cap=0
adv_10hdx_cap=0 adv_10fdx_cap=0 adv_1000hdx_cap=0 adv_100T4_cap=0;
name="ce" parent="/pci@9,700000/pci@4/pci@0" unit-address="1"
adv_autoneg_cap=1 adv_100hdx_cap=0 adv_100fdx_cap=0 adv_1000fdx_cap=1
adv_10hdx_cap=0 adv_10fdx_cap=0 adv_1000hdx_cap=0 adv_100T4_cap=0;
name="ce" parent="/pci@9,700000/pci@4/pci@4" unit-address="2"
adv_autoneg_cap=1 adv_100hdx_cap=0 adv_100fdx_cap=0 adv_1000fdx_cap=1
adv_10hdx_cap=0 adv_10fdx_cap=0 adv_1000hdx_cap=0 adv_100T4_cap=0;
name="ce" parent="/pci@9,700000/pci@4/pci@4" unit-address="3"
adv_autoneg_cap=1 adv_100hdx_cap=0 adv_100fdx_cap=0 adv_1000fdx_cap=1
adv_10hdx_cap=0 adv_10fdx_cap=0 adv_1000hdx_cap=0 adv_100T4_cap=0;


Everything in the file from the name= to the semicolon is all on one
line. The sun docs will tell you to grab name from the driver_aliases
file, but after talking to frontline support for a few minutes, i was
convinced to use ce as the name instead of pci108e,abba or pci100b,35.


The parent and unit addresses from from the relevant lines in
path_to_inst. The parent is everything in path_to_inst up to the
network portion. The unit_address is the value listed in network@ for a
given interface.

$ grep ce /etc/path_to_inst
"/pci@8,700000/pci@5/pci@0/network@0" 0 "ce"
"/pci@8,700000/pci@5/pci@0/network@1" 1 "ce"
"/pci@8,700000/pci@5/pci@4/network@2" 2 "ce"
"/pci@8,700000/pci@5/pci@4/network@3" 3 "ce"
"/pci@9,700000/pci@4/pci@0/network@0" 4 "ce"
"/pci@9,700000/pci@4/pci@0/network@1" 5 "ce"
"/pci@9,700000/pci@4/pci@4/network@2" 6 "ce"
"/pci@9,700000/pci@4/pci@4/network@3" 7 "ce"
"/pci@9,700000/pci@3/network@0" 8 "ce"
"/pci@9,700000/pci@3/network@1" 9 "ce"
"/pci@9,700000/pci@3/network@2" 10 "ce"
"/pci@9,700000/pci@3/network@3" 11 "ce"


In my ce.conf from above i am running ce0 and ce4 at 100mfdx and
ce1,2,3,5,6,7 at 1000mFDX. I have left the autoneg on for the gig
interfaces, but only let them auto to gig (in our network we sometimes
had 100half autoneg even when the switches were auto).

ce8 - ce11 are not used yet on my system and as such dont have any
representation in ce.conf.


Hope this helps,


Darren