O/S Support - NETGEAR M6100 Series Reference Manual

Table 71. Error Messages (continued)
Component Message
OS USL: failed to sync terminator table on unit = x
OS USL: failed to sync ip-multicast table on unit = x

O/S Support

Table 72. BSP Log Message
Component Message
BSP rc = 10
Table 73. OSAPI Log Messages
Component Message
OSAPI osapiNetLinkNeighDump: could not open socket!
- or –
ipstkNdpFlush: could not open socket! – or –
osapiNetlinkDumpOpen: unable to bind socket!
errno = XX
OSAPI ipstkNdpFlush: sending delete failed
OSAPI unable to open
/proc/net/ipv6/conf/default/hop_limit
OSAPI osapimRouteEntryAdd, errno XX adding 0xYY to
ZZ – or –
osapimRouteEntryDelete, errno XX deleting
0xYY from ZZ
OSAPI l3intfAddRoute: Failed to Add Route – or –
l3intfDeleteRoute: Failed to Delete Route
OSAPI osapiNetIfConfig: ioctl on XX failed: addr: 0xYY,
err: ZZ – or –
osapiNetIPSet: ioctl on XX failed: addr: 0x%YY
M6100 Series Switches
NETGEAR Managed Switch Software Log Messages
1181
Cause
Could not synchronize unit x due to a transport
failure or API issue on remote unit. A
synchronization retry will be issued.
Could not synchronize unit x due to a transport
failure or API issue on remote unit. A
synchronization retry will be issued.
Cause
Second message logged at bootup, right after
Starting code.... Always logged.
Cause
Couldn't open a netlink socket. Make sure "ARP
Daemon support" (CONFIG_ARPD) is enabled in
the kernel, if the reference kernel binary is not
being used.
Failed when telling the kernel to delete a
neighbor table entry (the message is incorrect).
IPv6 MIB objects read, but /proc file system is not
mounted, or running kernel does not have IPV6
support.
Error adding or deleting an IPv4 route (listed in
hex as YY), on the interface with name ZZ Error
code can be looked up in errno.h.
Error adding or deleting a default gateway in the
kernel's routing table (the function is really
osapiRawMRouteAdd()/Delete()).
Failed trying to set the IP address (in hex as YY)
of the interface with name XX, and the interface
does not exist. Sometimes this is a harmless
race condition (e.g. we try to set address 0 when
DHCPing on the network port (dtl0) at bootup,
before it's created using TAP).