Component | Message | Cause |
---|---|---|
Trap Mgr | Link Up/Down: unit/slot/port | An interface changed link state. |
Component | Message | Cause |
---|---|---|
DHCP (Dynamic Host Configuration Protocol) Filtering | Unable to create r/w lock for DHCP Filtering | Unable to create semaphore used for dhcp filtering configuration structure. |
DHCP Filtering | Failed to register with nv Store. | Unable to register save and restore functions for configuration save. |
DHCP Filtering | Failed to register with NIM | Unable to register with NIM for interface callback functions. |
DHCP Filtering | Error on call to sysapiCfgFileWrite file | Error on trying to save configuration. |
Component | Message | Cause |
---|---|---|
NVStore | Building defaults for file XXX | A component‘s configuration file does not exist or the file‘s checksum is incorrect so the component‘s default configuration file is built. |
NVStore | Error on call to osapiFsWrite routine on file XXX | Either the file cannot be opened or the OS‘s file I/O returned an error trying to write to the file. |
NVStore | File XXX corrupted from file system. Checksum mismatch. | The calculated checksum of a component‘s configuration file in the file system did not match the checksum of the file in memory. |
NVStore | Migrating config file XXX from version Y to Z | A configuration file version mismatch was detected so a configuration file migration has started. |
Component | Message | Cause |
---|---|---|
RADIUS | RADIUS: Invalid data length - xxx | The RADIUS Client received an invalid message from the server. |
RADIUS | RADIUS: Failed to send the request | A problem communicating with the RADIUS server. |
RADIUS | RADIUS: Failed to send all of the request | A problem communicating with the RADIUS server during transmit. |
RADIUS | RADIUS: Could not get the Task Sync semaphore! | Resource issue with RADIUS Client service. |
RADIUS | RADIUS: Buffer is too small for response processing | RADIUS Client attempted to build a response larger than resources allow. |
RADIUS | RADIUS: Could not allocate accounting requestInfo | Resource issue with RADIUS Client service. |
RADIUS | RADIUS: Could not allocate requestInfo | Resource issue with RADIUS Client service. |
RADIUS | RADIUS: osapiSocketRecvFrom returned error | Error while attempting to read data from the RADIUS server. |
RADIUS | RADIUS: Accounting-Response failed to validate, id = xxx | The RADIUS Client received an invalid message from the server. |
RADIUS | RADIUS: User (xxx) needs to respond for challenge | An unexpected challenge was received for a configured user. |
RADIUS | RADIUS: Could not allocate a buffer for the packet | Resource issue with RADIUS Client service. |
RADIUS | RADIUS: Access-Challenge failed to validate, id = xxx | The RADIUS Client received an invalid message from the server. |
RADIUS | RADIUS: Failed to validate Message-Authenticator, id = xxx | The RADIUS Client received an invalid message from the server. |
RADIUS | RADIUS: Access-Accept failed to validate, id = xxx | The RADIUS Client received an invalid message from the server. |
RADIUS | RADIUS: Invalid packet length – xxx | The RADIUS Client received an invalid message from the server. |
RADIUS | RADIUS: Response is missing Message-Authenticator, id = xxx | The RADIUS Client received an invalid message from the server. |
RADIUS | RADIUS: Server address doesn't match configured server | RADIUS Client received a server response from an unconfigured server. |
Component | Message | Cause |
---|---|---|
TACACS+ | TACACS+: authentication error, no server to contact | TACACS+ request needed, but no servers are configured. |
TACACS+ | TACACS+: connection failed to server x.x.x.x | TACACS+ request sent to server x.x.x.x but no response was received. |
TACACS+ | TACACS+: no key configured to encrypt packet for server x.x.x.x | No key configured for the specified server. |
TACACS+ | TACACS+: received invalid packet type from server. | Received packet type that is not supported. |
TACACS+ | TACACS+: invalid major version in received packet. | Major version mismatch. |
TACACS+ | TACACS+: invalid minor version in received packet. | Minor version mismatch. |
Component | Message | Cause |
---|---|---|
LLDP (Link Layer Discovery Protocol) | lldpTask(): invalid message type:xx. xxxxxx:xx | Unsupported LLDP packet received. |
Component | Message | Cause |
---|---|---|
SNTP (Simple Network Time Protocol) | SNTP: system clock synchronized on %s UTC | Indicates that SNTP has successfully synchronized the time of the box with the server. |
Component | Message | Cause |
---|---|---|
DHCP6 Client | ip6Map dhcp add failed. | This message appears when the update of a DHCP leased IP address to IP6Map fails. |
DHCP6 Client | osapiNetAddrV6Add failed on interface xxx. | This message appears when the update of a DHCP leased IP address to the kernel IP stack fails. |
DHCP6 Client | Failed to add DNS Server xxx to DNS Client. | This message appears when the update of a DNS6 Server address given by the DHCPv6 Server to the DNS6 Client fails. |
DHCP6 Client | Failed to add Domain name xxx to DNS Client. | This message appears when the update of a DNS6 Domain name info given by the DHCPv6 Server to the DNS6 Client fails. |
Component | Message | Cause |
---|---|---|
DHCP4 Client | Unsupported subOption (xxx) in Vendor Specific Option in received DHCP pkt | This message appears when a message is received from the DHCP Server that contains an un-supported Vendor Option. |
DHCP4 Client | Failed to acquire an IP address on xxx; DHCP Server did not respond. | This message appears when the DHCP Client fails to lease an IP address from the DHCP Server. |
DHCP4 Client | DNS name server entry add failed. | This message appears when the update of a DNS Domain name server info given by the DHCP Server to the DNS Client fails. |
DHCP4 Client | DNS domain name list entry addition failed. | This message appears when the update of a DNS Domain name list info given by the DHCP Server to the DNS Client fails. |
DHCP4 Client | Interface xxx Link State is Down. Connect the port and try again. | This message appears when the Network protocol is configured with DHCP without any active links in the Management VLAN. |