HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Moved 2nd NIC to new subnet, slow response
Operating System - HP-UX
1833772
Members
2315
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2006 10:36 AM
02-06-2006 10:36 AM
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.
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.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2006 07:05 PM
02-06-2006 07:05 PM
Re: Moved 2nd NIC to new subnet, slow response
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
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
share share share
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2006 07:38 PM
02-06-2006 07:38 PM
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
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
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP