setup ee0 (backup NIC) without rebooting system

[Peter Wang_4]

Hi,
my ES45 running 5.1A, has two NICs: alt0 (for system) and ee0(for data backup LAN). Both were working fine before. After reboot for maintenance yesterday, the ee0 lost its setting. ifconfig -a and netstat -nr shows that ee0 was not configured. Firstly, I configured ee0 with "ifconfig" cmd, it works fine, but I know ee0 will loss setting again once reboot, so I used netconfig to deconfigure ee0, then reconfigure it. However, ee0 doesn't work after that, even ifconfig -a shows up. The NIC LED is off.
# ifconfig -a
ee0: flags=c63
inet 10.10.137.31 netmask fffffc00 broadcast 10.10.139.255 ipmtu 1500

Following cmd shows LINK DOWN
# hwmgr get attribute -category network
58:
name = ee0
category = network
sub_category = Ethernet
model = Intel 82559
hardware_rev = 8
firmware_rev =
MAC_address = 00-08-02-CD-49-2A
MTU_size = 1500
media_speed = 100
media_selection = Automatic
media_type = Unshielded Twisted Pair (UTP)
loopback_mode = 0
promiscuous_mode = 0
full_duplex = 1
interface_number = 1
link = Down
registration_time = Wed Jul 21 18:45:53 2004
user_name = (null) (settable)
location = (null) (settable)
software_module = (null)
state = unavailable
state_previous = available

I wonder if anybody can help me setup ee0 without rebooting system.

Thanks,

Peter

[Ralf Puchner]

if link is down there is a cabling or hub/switch problem.

Does a ping to the interface work?
What does the switch/hub and led tell us?

Steps:
1. check led on switch/card
2. # ifconfig ee0 /
3. # ifconfig ee0 up
4. # ping
5. check led, if connection doesn't work use lan_config to setup proper speed.

[Peter Wang_4]

Hi Ralf,
After working with network person, I found its switch port was disabled for some reason (prob. the autosense feature on the switch side). Now, speed 100MB was forced on both NIC and switch sides. ee0 works now.
I have one more question with "netconfig". I don't have testing box and can't find answer from Tru 64 docs. When finished all the network setup steps, I was asked to restart network servcies. Since I have two NICs (for system: alt0 and data backup: ee0), say I am configuring ee0 via netconfig, my question is when I select to restart, will it restart all NICs on the system, or only ee0 will be impacted and alt0 is intact (in other word, my production box's alt0 connectivity is not impacted).

thanks,

P

[Ralf Puchner · Accepted solution]

it will restart all startup scripts which are involved with network, so your alt device will loose all connections...

[rachel_11]

Hello Peter,

The command:
lan_config -i ee0 -a 0 -s 100 -x 1
will set ee0 to 100, full duplex, no autonegotiate.

Add the line to the file /etc/inet.local
and it will reconfigure correctly after reboot.

Regards,
Rachel

[Ralf Puchner]

it is not wise to configure ee0 without autoneg (eg. using lan_config).

The intel chips works best with autoneg enabled (default). so settings both side of the connection to autoneg is required, if it will not sync to the speed you require there is a compatiblity or hardware issue between your components.

[Peter Wang_4]

Thanks all for your kindest help.
The autonegotiate were enabled on both side of connection before I got the problem. One of my another production ES45 box lost LAN ee0 connectivity which led to backup failure yesterday (nothing was changed on sys network). The status on switch was sth like "Errdisable", so autoneg was disabled, and 100MB, full-duplex were set to true on switch . "lan_config -i ee0 -a 0 -s 100 -x 1" were issued on all ES40/45 boxes, but haven't put it into /etc/inet.local file. I will do it later.

thanks,
P

[Ralf Puchner]

if you use lan_config you must also configure the switch properly. A connection must always set identically on both sides!

[Orrin]

Hi Peter,

If you need ee0 to hold it's configuration through reboots, you have to use the rcmgr set command.

Regards,
Orrin.

[Ralf Puchner]

orin,

why so complicated? netsetup/netconfig (supported way) will do the job fine, rcmgr is only for manual intervention.

[Orrin]

Hi Ralph,

I agree it's easier with netconfig.

The reason I mentioned this is because the method is failsafe, and is not dependent upon the terminal setup.

We have had problems, our GS160 has a windows box configured as a console, using Kea. HP set it up for us. Well whenever we tried to start up sysman, we got all kinds of Garbage on the screen, and could not proceed.

We were stuck and had to use rcmgr set and ifconfig commands to configure the cluster interconnects and LAN interfaces as Net Rain Pairs.

Hope this clarifies things. Didn't mean to contradict what you said. I agree with your answer.

Regards,
Orrin.

[Ralf Puchner]

Orin,

why not correcting the KEA settings? All the setup tools are also available as textmode menues.

[ADJOLOHOUN_1]

Hi,


Tru64 DE600 driver ee.mod often ignore SRM console variables ei*0_mode.

"# man ee" instructs to use lan_config to make stable setting into /etc/inet.local.

Even if your switch has autonegotiation enabled,
I suggest for your interface (ee0) on Tru64 : autonegotiation disabled , fullduplex enabled.

Then your /etc/inet.local will contain :
"/usr/sbin/lan_config -i ee0 -m utp -s 100 -a 0 -x 1"


Regards,

fx@hp.com

[Al Licause]

RE: ADJOLOHOUN "DE600 driver ee.mod often ignore SRM console...."

If you change the "often" to "always" you'd have it right. The non-Digital
produced devices have never read the console variables. Those include the
Intel (ee), Broadcom (bcm) and Alteon (alt). Only the Digital devices using
the tulip driver read the console variables. So don't bother trying to manipulate the network devices from the console.

RE: rcmgr vs netconfig......from experience it is best to use the lan_config
command in the /etc/rc.config file as this file is never changed by any of the
system configurators. Rcmgr can be used, as suggested, as a safe method for
manipulating the contents of the rc.config and rc.config.common files but since
these changes can be "botched" by the configurators, you are better off using
the inet.local file.

It should also be noted that lan_config can change all of the manageable parameters
for the interface, whereas, the ifconfig command which is what is executed when inet runs and the contents of rc.config* are read cannot change all parameters.

RE: auto vs manual settings on the port/nic.....again as mentioned in previous
replies, if using auto on one or the other, then they should both be set to auto.
Same for manual. But in all cases, you need to do what works best for your
particular situation. If something works, but seems to break the rules, then
by all means, use it. But do try following the rules/recommendations first.
They'll usually save time.