adding new 100baseT NIC to AlphaServer 2100

[Sharky_1]

Hello all,

We have an very old 2100 that is running on a 10baseT card. We have installed a new DEC500A card that is 10/100 capable. Using the net config tool, I'm able to change the speed to 100mb full-duplex. After a reboot the system reverts to 10mb half-duplex. The system sees it as tu1 and is operational in 10mb mode half duplex only. Is there a setting I must change in the ARC shell for this device. Is there a particular ARC syntax I need to use. Here are some messages from /var/adm/messages, ip addresses have xxx to protect the innocent :)

after installing

Jul 28 14:32:25 jackdaniels vmunix: tu1: DEC TULIP (10/100) Ethernet Interface, hardware address: 00-00-F8-08-26-69
Jul 28 14:32:25 jackdaniels vmunix: tu1: no console mode: defaulting to 10BaseT (UTP) port: half duplex

I ran this command to manually change speed and duplex:

# lan_config -i tu1 -s 200 <= 200 is 100mb full duplex


#
# ifconfig -a
lo0: flags=100c89
inet 127.0.0.1 netmask ff000000 ipmtu 4096

sl0: flags=10

tu0: flags=c63

tu1: flags=c63
inet 10.xxx.xxx.78 netmask ffffff00 broadcast 10.xxx.xxx.255 ipmtu 1500

Thanks in advanced for any help,

-Guillermo Barton
gbarton@sybase.com

[Rani sawade]

Hello,
Are you looking at keeping the changes to
tu1 permanent? Add an entry of lan-config command that
you are executing to /etc/inet.local file. Thus changes will remain even after reboot.

-Rani.

[Vladimir Fabecic]

In SRM console type:
>>> set ewa1_mode fastfd
Maybe you current ewa1_mode is set tenbt which is 10 Mbps half duplex.
OS uses console parameter by default.

[Michael Schulte zur Sur]

Hi,

no console mode
This points to tu1 having no console evironment variables.
show ewa*mode
and then set as Vladimir suggests.

greetings,

Michael

[Ivan Ferreira]

After you setup the adaptar at console level, also add the command:

lan_config -i tu1 -a 0 -x 1 -s 100

To the /etc/inet.local file, so it gets excecuted on reboots.

If you use Tru64 V5.X, use the command:

hwmgr get attr -cat network

To identify the speed, duplex and mode status.

[Sharky_1]

Thank you all very much for your replies, I will try the steps mentioned and will report success hopefully.

Kind regards,

-Guillermo

[Sharky_1]

Hello all,

After entering the ewa1_mode fastfd command, the systems still found no console mode and now failed to initialize the NIC. I noticed the ewa0 had the following entries, while there were none at all for ewa1:

ewa0_loop_count 3e8
ewa0_loop_inc a
ewa0_loop_patt ffffffff
ewa0_loop_size 2e
ewa0_lp_msg_node 1
ewa0_mode Twisted-Pair

Do I need to add these entries for ewa1? Can I use the same values? Will the entry in the /etc/inet.local file suffice to enable the NIC at 100mbt?

Thanks again for your help,

-Guillermo

[Sharky_1]

Hello all,

Turns out that the device was named ewb0. I enabled the auto-negotiate flag as follows:

>>> set ewb0_mode auto-negotiate


This did it!! got a messages right away that 100bt full duplex was active and the card LED's came on.

Thanks for pointing me in the right direction, much appreciated.

-Guillermo

[Michael Schulte zur Sur]

Hi,

nice to hear that you found the solution.
I forgot that the numbering goes ewa, ewb
One thing check. We do not have so good experiences with tulip cards and auto-negotiate. If we use copy or remote copy the transfer rate is almost zero. Please check that and if that is the same with you, set 100 full duplex manually with fastfd.

greetings,

Michael
ps. please check out the point system here.
http://forums1.itrc.hp.com/service/forums/helptips.do?#28
Thanks.

[Ralf Puchner]

so much replies for a question already answered previously. Why not simple use the "search" function within the forum?