1. Oracle Hardware Management Pack 2.4 Release Notes
  2. Known Issues and Notes for Software Release 2.4
  3. Host-to-ILOM Interconnect Issues
  4. Internal Error When Enabling Host-to-ILOM Interconnect (29242138, 29344445)

Internal Error When Enabling Host-to-ILOM Interconnect (29242138, 29344445)

In some cases, the local Host-to-ILOM interconnect (the USB Ethernet connection to the service processor) might fail in Oracle Linux due to a routing table issue. Attempting to re-enable the Host-to-ILOM interconnect using either ilomconfig or itpconfig commands fails with an Internal error. For example: 

[root@test1 ~]# ilomconfig enable interconnect
Set 'state' to 'enabled'

ERROR: Internal error
[root@test1 ~]#

To check to see if this is a host-side routing table issue, do the following:

  1. From the host, ping the service processor USB Ethernet interconnect port address.

    Note:

    The USB Ethernet interconnect uses Oracle pre-assigned addresses; one on the host side and one on the service processor side. These addresses are not the same as the service processor NET MGT port IP address.

    [root@test1 ~]# ping 169.254.182.76
PING 169.254.182.76 (169.254.182.76) 56(84) bytes of data.
From 192.0.2.24 icmp_seq=1 Destination Host Unreachable
From 192.0.2.24 icmp_seq=3 Destination Host Unreachable
^C
--- 169.254.182.76 ping statistics ---
3 packets transmitted, 0 received, +2 errors, 100% packet loss, time 2084ms

    If you see the error "Destination Host Unreachable" and ping statistic errors, you likely have a routing table issue.

  2. Next, use the route command to check the routing table to see if the Host-to-ILOM interconnect USB interface destination is listed. Look for the usb# in the Iface column of the output. For example: 

    [root@test1 ~]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.0.2.24      0.0.0.0         UG    100    0        0 eth0
203.0.113.0     0.0.0.0         255.255.255.0   U     100    0        0 eth0
203.0.113.15    0.0.0.0         255.255.255.0   U     0      0        0 virbr0

    If a destination for the Host-to-ILOM interconnect USB interface is missing, you will need to add it to the routing table.

Workaround

Add the network destination address to the Host-to-ILOM interconnect USB interface to the routing table:

  1. From the host, enter the route add command as follows: 

    [root@test1 ~]# route add -net 169.254.182.0 netmask
255.255.255.0 usb0

  2. Check to see if the destination address has been added to the routing table by entering the route command: 

    [root@test1 ~]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.0.2.24      0.0.0.0         UG    100    0        0 eth0
169.254.182.0   0.0.0.0         255.255.255.0   U     0      0        0 usb0
203.0.113.0     0.0.0.0         255.255.255.0   U     100    0        0 eth0
203.0.113.15    0.0.0.0         255.255.255.0   U     0      0        0 virbr0

  3. Ping the service processor USB Ethernet interconnect port address to confirm it can be found.

    [root@test1 ~]# ping 169.254.182.76
PING 169.254.182.76 (169.254.182.76) 56(84) bytes of data.
64 bytes from 169.254.182.76: icmp_seq=1 ttl=64 time=0.507 ms
64 bytes from 169.254.182.76: icmp_seq=2 ttl=64 time=0.222 ms
64 bytes from 169.254.182.76: icmp_seq=3 ttl=64 time=0.239 ms
^C
--- 169.254.182.76 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2060ms
rtt min/avg/max/mdev = 0.222/0.322/0.507/0.132 ms

    Once the routing table issue is fixed, you can use the Host-to-ILOM interconnect with Oracle Hardware Management Pack commands.

Parent topic: Host-to-ILOM Interconnect Issues