HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Network Config conflect problem. Maybe?
Operating System - HP-UX
1833867
Members
1969
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
11-17-2003 05:09 AM
11-17-2003 05:09 AM
I'm confused.
When we rebooted our HP-9000 with HP-UX 11.0 the other day after adding a JBOD, the system hung on the LAN causing it to take forever to come up. Thinking it was a bad NIC that just happened to fail, we removed it and it was fine.
The new NIC did the same thing.
Here is what I found that is confusing.
With only the one NIC (looking in sam)
LAN0 shows 192.168.1.5
LAN0:1 shows 192.168.1.10
This is what I think it should be.
With the second NIC installed (looking in sam)
LAN0 shows 192.168.1.5
LAN0:1 shows 0.0.0.0
LAN0 shows 192.168.1.10
LAN0:1 shows 0.0.0.0
But the system hangs on boot an you can not ping the box.
========================
Now I have the box up with only NIC. I can not down it because Production needs it.
========================
Here is what I found in /etc/rc.config.d/netconf
IP_ADDRESS[0]=192.168.1.5
SUBNET_MASK[0]=255.255.0.0
BROADCAST_ADDRESS[0]=192.168.255.255
INTERFACE_STATE[0]=up
DHCP_ENABLE[0]=0
IP_ADDRESS[1]=192.168.1.10
SUBNET_MASK[1]=255.255.0.0
INTERFACE_NAME[1]=lan1
BROADCAST_ADDRESS[1]=192.168.255.255
INTERFACE_STATE[1]=up
DHCP_ENABLE[1]=0
IP_ADDRESS[2]=192.168.1.10
SUBNET_MASK[2]=255.255.0.0
INTERFACE_NAME[2]=lan0:1
BROADCAST_ADDRESS[2]=192.168.255.255
INTERFACE_STATE[2]=up
I'm thinking this may be the cause. Not sure.
I think this is telling me that there is the same IP address on 2 cards and when I remove LAN1 then LAN0:1 uses the .10 else when both NICs are installed it tries to asign the same IP to both causing the lan to fail.
I think the fix would to remove the settings for LAN1 in /etc/rc.config.d/netconf
Then reset as needed after the NIC is reinstalled.
Can you help me clear this up?
Is there any other Config files I should look at?
Marty
When we rebooted our HP-9000 with HP-UX 11.0 the other day after adding a JBOD, the system hung on the LAN causing it to take forever to come up. Thinking it was a bad NIC that just happened to fail, we removed it and it was fine.
The new NIC did the same thing.
Here is what I found that is confusing.
With only the one NIC (looking in sam)
LAN0 shows 192.168.1.5
LAN0:1 shows 192.168.1.10
This is what I think it should be.
With the second NIC installed (looking in sam)
LAN0 shows 192.168.1.5
LAN0:1 shows 0.0.0.0
LAN0 shows 192.168.1.10
LAN0:1 shows 0.0.0.0
But the system hangs on boot an you can not ping the box.
========================
Now I have the box up with only NIC. I can not down it because Production needs it.
========================
Here is what I found in /etc/rc.config.d/netconf
IP_ADDRESS[0]=192.168.1.5
SUBNET_MASK[0]=255.255.0.0
BROADCAST_ADDRESS[0]=192.168.255.255
INTERFACE_STATE[0]=up
DHCP_ENABLE[0]=0
IP_ADDRESS[1]=192.168.1.10
SUBNET_MASK[1]=255.255.0.0
INTERFACE_NAME[1]=lan1
BROADCAST_ADDRESS[1]=192.168.255.255
INTERFACE_STATE[1]=up
DHCP_ENABLE[1]=0
IP_ADDRESS[2]=192.168.1.10
SUBNET_MASK[2]=255.255.0.0
INTERFACE_NAME[2]=lan0:1
BROADCAST_ADDRESS[2]=192.168.255.255
INTERFACE_STATE[2]=up
I'm thinking this may be the cause. Not sure.
I think this is telling me that there is the same IP address on 2 cards and when I remove LAN1 then LAN0:1 uses the .10 else when both NICs are installed it tries to asign the same IP to both causing the lan to fail.
I think the fix would to remove the settings for LAN1 in /etc/rc.config.d/netconf
Then reset as needed after the NIC is reinstalled.
Can you help me clear this up?
Is there any other Config files I should look at?
Marty
The only thing that always remain the same are the changes.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2003 05:22 AM
11-17-2003 05:22 AM
Solution
IP_ADDRESS[1]=192.168.1.10
SUBNET_MASK[1]=255.255.0.0
INTERFACE_NAME[1]=lan1
BROADCAST_ADDRESS[1]=192.168.255.255
INTERFACE_STATE[1]=up
DHCP_ENABLE[1]=0
IP_ADDRESS[2]=192.168.1.10
SUBNET_MASK[2]=255.255.0.0
INTERFACE_NAME[2]=lan0:1
Two interfaces with the same ip address. Virtual or not this an unsupported configuration.
SEP
SUBNET_MASK[1]=255.255.0.0
INTERFACE_NAME[1]=lan1
BROADCAST_ADDRESS[1]=192.168.255.255
INTERFACE_STATE[1]=up
DHCP_ENABLE[1]=0
IP_ADDRESS[2]=192.168.1.10
SUBNET_MASK[2]=255.255.0.0
INTERFACE_NAME[2]=lan0:1
Two interfaces with the same ip address. Virtual or not this an unsupported configuration.
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-17-2003 05:40 AM
11-17-2003 05:40 AM
Re: Network Config conflect problem. Maybe?
Steven,
I'm less confuesed now.
I'll remove it and go on from there.
Thanks,
Marty
I'm less confuesed now.
I'll remove it and go on from there.
Thanks,
Marty
The only thing that always remain the same are the changes.
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