Tru64 Tu(x) incrementing with DE500 move

Hello all,

I am new around here with this being my first post. I am not sure if this group also discusses Tru64 but since I did not see a Tru64 section I will ask here. Let me know if I am posting in the wrong area. :o Here is my issue, well one of them anyway. :rolleyes:

I have an AlphaServer 1200 running Tru64 5.1B non-commercial. After the initial install of the OS the sole NIC, a DE500-21143-PC installed as Tu0 as expected. After the install and network configuration I needed to install a different video card that required I relocate the DE500 to a different PCI slot. Upon restart the network services were not running and I found Tu0 had incremented to Tu1. To confirm this behavior I moved the card back to its original PCI slot and restarted. Tu1 has now become Tu2. Tu0 and Tu1 are not recognized by Tru64 and are reported as unavailable, as they should be since there is no physical interface, but I cannot figure out how I can force the DE500 Tu2 back to being Tu0 or Tu1. I have looked at all the SRM environment variables as well as all network related config files. I cannot find where ewa0 get mapped to Tu(x). SRM has not incremented the DE500 which remains ewa0 regardless of slot position. Has anyone seen this behavior? Thanks.

Look at the network_manual_setup manpage(7). I believe you will have to change some variables in /etc/rc.config.

Yes, That was the first place I looked and what I found were new values in rc.config for the new interface. I deleted the additions that refered to the new 'tu' and reverted to config back to a tu0 setup, with not impact on the interface.

NETDEV_0="tu0"
IFCONFIG_0="192.168.0.16 netmask 255.255.255.0"
NUM_NETCONFIG="1"

NETDEV_1="tu1" << deleted
IFCONFIG_1="" << deleted
NUM_NETCONFIG="2" << changed back to 1

I also replaced the empty NETDEV_1= and IFCONFIG_1= lines at the top of the rc.config file. This had no impact on the system. tu1 and later tu2 were still the only NICs detected and configurable. I believe the NETDEV_0="tu0" is ignored because there isn't a tu0 interface available when the tu gets incremented.