Netgear M4300-52G (GSM4352S) - Stackable Managed Switch with 48x1G and 4x10G including 2x10GBASE-T and 2xSFP+ Layer 3 软件指南

下载
页码 1143
Switch Software Log Messages 
1103
 M4200 and M4300 Series ProSAFE Managed Switches
O/S Support
OS
USL: failed to sync terminator table on unit = x
Could not synchronize unit x due to a transport 
failure or API issue on remote unit. A 
synchronization retry will be issued.
OS
USL: failed to sync ip-multicast table on unit = x
Could not synchronize unit x due to a transport 
failure or API issue on remote unit. A 
synchronization retry will be issued.
Table 71.  BSP Log Message 
Component
Message
Cause
BSP
rc = 10
Second message logged at bootup, right after 
Starting code…. Always logged.
Table 72.  OSAPI Log Messages 
Component
Message
Cause
OSAPI
osapiNetLinkNeighDump: could not open socket! 
- or –
ipstkNdpFlush: could not open socket! – or – 
osapiNetlinkDumpOpen: unable to bind socket! 
errno = XX
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. 
OSAPI
ipstkNdpFlush: sending delete failed
Failed when telling the kernel to delete a 
neighbor table entry (the message is incorrect).
OSAPI
unable to open 
/proc/net/ipv6/conf/default/hop_limit
IPv6 MIB objects read, but /proc file system is not 
mounted, or running kernel does not have IPV6 
support.
OSAPI
osapimRouteEntryAdd, errno XX adding 0xYY to 
ZZ – or – 
osapimRouteEntryDelete, errno XX deleting 
0xYY from ZZ
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.
OSAPI
l3intfAddRoute: Failed to Add Route – or – 
l3intfDeleteRoute: Failed to Delete Route
Error adding or deleting a default gateway in the 
kernel’s routing table (the function is really 
osapiRawMRouteAdd()/Delete()).
OSAPI
osapiNetIfConfig: ioctl on XX failed: addr: 0xYY, 
err: ZZ – or – 
osapiNetIPSet: ioctl on XX failed: addr: 0x%YY
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). 
Table 70.  Error Messages (continued)
Component
Message
Cause