Monitoring, Management & Location Tracking

eth0 error on HP Chassis

For AMP, the eth0 interface is matched with license key and tied to the template configurations.

For HP Chassis, the initial setup goes okay, but after rebooting, there are some errors including an eth0 error. The tricky part was that HP labels it's interfaces eth1 and eth2, whereas we usually see eth0 and eth1 on most linux boxes.

Accepted Solution - Redirecting eth1 to be eth0
1 - Connect to the AMPs command line
2 - # cd /etc/sysconfig/network-scripts
3 - Check eth0 and eth1 interfaces:
# more ifcfg-eth0
# more ifcfg-eth1
Assuming eth1 has a HWADDR - we are going to redirect eth0 to point at the HWADDR of eth1
4 - grep HWADDR /etc/sysconfig/network-scripts/ifcfg-eth1 >> /etc/sysconfig/network-scripts/eth0
This copies the HWADDR line to the bottom of eth0
5 - vi ifcfg-eth1
POUND '#" the HWADDR line
6 - vi ifcfg-eth0
Make sure ONBOOT=yes
7 - Reboot the system to test.

Version history
Revision #:
1 of 1
Last update:
‎06-09-2014 09:43 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.