Moved 2nd NIC to new subnet, slow response

[Lonny Balderston]

Sorry if this post is in the wrong forum...
HP 9000 with 2 NICS, each connected to different subnet (IPs 136.151.164.241 and 136.151.165.218). We recently swung the 2nd NIC to a new "faster" subnet (IP 106.108.55.17). Traceroutes from PCs in the field show a significant slowdown as the packets get close to the HP. Our network folks think that there may be "source quenching" occuring. I troubleshot and found that there is no 2nd default route defined for the 2nd subnet on the HP 9000 (but there was not for the previous subnet either). Insight? Thanks.

[paolo barila]

Hi,

check if configuration is appropriate (100 full duplex autoneg...)

# lanadmin -x N # for lanN


If you need change (sample)

# vi /etc/rc.config.d/hpbtlanconf

HP_BTLAN_INTERFACE_NAME[0]=lan0
HP_BTLAN_STATION_ADDRESS[0]=
HP_BTLAN_SPEED[0]=100FD
HP_BTLAN_MTU[0]=1500

/sbin/init.d/hpbtlan stop

/sbin/init.d/hpbtlan start

Pablo

[Steven E. Protter · Accepted solution]

Shalom Lonny,

Right forum. Good choice.

lanadmin -x 0

zero if for lan0
1 for lan1

etcetera.

landadmin -X can let you change on the fly.

Older 10/100 BaseT HP nics require manual(explicit) configuration as far as speed and duplex.

1000 BaseT NIC's MUST be autonegotiate. Switch port settings in either case MUST match the NIC settings. See the btlan post above for details.

I would restart the system and perhaps use the route add command to improve speed on the new subnet.

SEP