GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Setting up new server
Operating System - HP-UX
1847702
Members
5345
Online
110265
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
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
12-12-2002 02:40 PM
12-12-2002 02:40 PM
Hi all.
I have just powered up our new rp5470 server and I'm having a little trouble getting it on the network.
There are 2 core I/O cards and the bottom of the stack. At the very top, in slot 12 is a 10/100/1000 card that we spec'd. The system recognizes the card as lan1, and the core i/o card as lan0.
The cable is plugged into the lan1 card and I'm trying to configure it. There is no cable plugged into lan0. I got some message about not being able to configure additional cards, must do primary first? I cannot ping the server at all. I can get to it from a console however.
Do I have to use the core i/o card to get started and then configure the other one?
Thanks!
I have just powered up our new rp5470 server and I'm having a little trouble getting it on the network.
There are 2 core I/O cards and the bottom of the stack. At the very top, in slot 12 is a 10/100/1000 card that we spec'd. The system recognizes the card as lan1, and the core i/o card as lan0.
The cable is plugged into the lan1 card and I'm trying to configure it. There is no cable plugged into lan0. I got some message about not being able to configure additional cards, must do primary first? I cannot ping the server at all. I can get to it from a console however.
Do I have to use the core i/o card to get started and then configure the other one?
Thanks!
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2002 02:56 PM
12-12-2002 02:56 PM
Solution
Hi Tim,
You don't need to use the core i/o card.
When the system boots for the first time after install (of factory supplied), it will ask for system and network parameters and configures the default interface (lan0). So, this might have happened.
Run the following commands to fix your problem.
#netstat -in
Find out the lan cards and the corresponding IP addresses. If 'lan0' is already configured, take out the IP address using ifconfig command.
#ifconfig lan0 unplumb
Repeat the same for other interfaces except for lo0 (loopback) and make sure the interfaces do not carry any IPs. Then run ifconfig command to assign the IP
#ifconfig lan1 your_ip netmask your_netmask
verify that the IP is bound
#ifconfig lan1
or
#netstat -in
Also, make sure that the speed of the interface matches with that you configured ont he switch. On HP servers, you will need to configure both switch and lan cards to 100 FullDuplex. Once your switch is set to 100FD, use the following command
#lanadmin -X 1 100FD
Then edit /etc/rc.config.d/netconf and /etc/rc.config.d/hpbtlanconf and make changes so that they will be permanent. You can see examples in those files for syntax.
-Sri
You don't need to use the core i/o card.
When the system boots for the first time after install (of factory supplied), it will ask for system and network parameters and configures the default interface (lan0). So, this might have happened.
Run the following commands to fix your problem.
#netstat -in
Find out the lan cards and the corresponding IP addresses. If 'lan0' is already configured, take out the IP address using ifconfig command.
#ifconfig lan0 unplumb
Repeat the same for other interfaces except for lo0 (loopback) and make sure the interfaces do not carry any IPs. Then run ifconfig command to assign the IP
#ifconfig lan1 your_ip netmask your_netmask
verify that the IP is bound
#ifconfig lan1
or
#netstat -in
Also, make sure that the speed of the interface matches with that you configured ont he switch. On HP servers, you will need to configure both switch and lan cards to 100 FullDuplex. Once your switch is set to 100FD, use the following command
#lanadmin -X 1 100FD
Then edit /etc/rc.config.d/netconf and /etc/rc.config.d/hpbtlanconf and make changes so that they will be permanent. You can see examples in those files for syntax.
-Sri
You may be disappointed if you fail, but you are doomed if you don't try
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2002 03:05 PM
12-12-2002 03:05 PM
Re: Setting up new server
You can not have two NIC cards on the same subnet.
If you set them up that way and you get no network connectivity.
At the console ifconfig lan0 down
See if you get connectivity then.
For the permanent fix, look at
/etc/rc.config.d/netconf
I have three new L2000 servers and went through the same problem. Learn from the fool Luke, no duplicate subnets on lan cards.
I would be happy to look at your netconf file if you wish.
Steve
Paid in points and the accolades of my peers.
If you set them up that way and you get no network connectivity.
At the console ifconfig lan0 down
See if you get connectivity then.
For the permanent fix, look at
/etc/rc.config.d/netconf
I have three new L2000 servers and went through the same problem. Learn from the fool Luke, no duplicate subnets on lan cards.
I would be happy to look at your netconf file if you wish.
Steve
Paid in points and the accolades of my peers.
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
12-12-2002 03:31 PM
12-12-2002 03:31 PM
Re: Setting up new server
Tim: there is a command to set up additional networks, it is:
set_parms addl_netwrk
See man page for set_parms. Alternatively, if not familiar with setting up networking at the command line, you can set up the second NIC via SAM.
Both set_parms and SAM simply do a scripted edit of the /etc/rc.config.d/netconf file mentioned earlier. I would recommend that you learn what this file does (it has some comments that indicate what it does, with examples), and just edit it yourself.
Once this file has the right networking setup, which will allow you to make any NIC your primary LAN, etc, I recommend a reboot to bring the changes into effect. It is possible to reset networking on-the-fly, but networking is set up early in the boot process for a reason, it is very basic to lots of Unix functions and processes. In your case (non-production, from your description), I'd reboot to come up clean on your new networking scheme.
Good luck, and keep at it, this starts to make sense once you beat your head on the side of the server a few times...
Regards, --bmr
set_parms addl_netwrk
See man page for set_parms. Alternatively, if not familiar with setting up networking at the command line, you can set up the second NIC via SAM.
Both set_parms and SAM simply do a scripted edit of the /etc/rc.config.d/netconf file mentioned earlier. I would recommend that you learn what this file does (it has some comments that indicate what it does, with examples), and just edit it yourself.
Once this file has the right networking setup, which will allow you to make any NIC your primary LAN, etc, I recommend a reboot to bring the changes into effect. It is possible to reset networking on-the-fly, but networking is set up early in the boot process for a reason, it is very basic to lots of Unix functions and processes. In your case (non-production, from your description), I'd reboot to come up clean on your new networking scheme.
Good luck, and keep at it, this starts to make sense once you beat your head on the side of the server a few times...
Regards, --bmr
We must indeed all hang together, or, most assuredly, we shall all hang separately. (Benjamin Franklin)
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 2026 Hewlett Packard Enterprise Development LP