HP Switch Software. Event Log Message Reference Guide

HP Switch Software Event Log Message Reference Guide September 2015

HP Networking Abstract This switch software guide is intended for network administrators and support personnel, and applies to the switch models listed unless otherwise noted. This guide does not provide rmation about upgrading or replacing switch hardware. The rmation in this guide is subject to change without notice. September 2015 Event Log Message Reference Guide

Copyright 2015 Hewlett-Packard Development Company, L.P. The rmation contained herein is subject to change without notice. All Rights Reserved. This document contains proprietary rmation, which is protected by copyright. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of Hewlett- Packard. Publication Number 5998-4397 Rev. C September 2015 Applicable Products HP 2520G Switches (J9298A, J9299A) HP 2520 Switches (J9137A, J9138A) HP 2530 Switches (J9772A, J9773A, J9775A J9776A) HP 2615 Switch (J9565A) HP 2620 Switches (J9623A, J9624A, J9625A, J9626A, J9627A) HP 2910al Switches (J9145A, J9146A, J9147A, J9148A) HP 2915 Switch (J9562A) HP 2920 Switches (J9726A, J9727A, J9728A, J9729A HP 3500 Switches (J9470A, J9471A, J9472A, J9473A) HP 3500yl Switches (J8692A, J8693A) HP 3800 Switches (J9573A, J9574A, J9575A, J9576A, J9584A, J9585A, J9586A, J9587A, J9588A) HP 5400zl Switches (J8697A, J8698A, J9447A, J9448A) HP 6200yl Switch (J8992A) HP 6600 Switches (J9263A, J9264A, J9265A, J9451A, J9452A) HP 8200zl Switches (J9475A, J8715A/B ) Disclaimer The rmation contained in this document is subject to change without notice. HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not furnished by Hewlett-Packard. Software End User License Agreement and Hardware Limited Warranty For the software end user license agreement and the hardware limited warranty rmation for HP Networking products, visit www.hp.com/networking/support. Trademark Credits Microsoft, Windows, and Microsoft Windows NT are US registered trademarks of Microsoft Corporation. Hewlett-Packard Company 8000 Foothills Boulevard, m/s 5551 Roseville, California 95747-5551 www.hp.com/networking/support

0 Unknown var type The variable type is unknown. RMON_SNMP_UNKNOWN_VAR_TYPE 1 <vlan-id> virtual LAN enabled The specified virtual LAN is enabled. RMON_VLAN_UP_INDIC 2 <vlan-id> disabled The specified virtual LAN is disabled. RMON_VLAN_DOWN_INDIC 3 Changing IP address to <ipaddr> 4 IP initialization failed for vlan <vlan-id> 5 ARP: <ip-addr> at <mac-addr> <encap-type> Changing the current IP address to the specified IP address. RMON_IP_IP_ADDR_CHANGE IP initialization on the specified VLAN has failed. RMON_IP_VLAN_INIT_ERROR A new entry has been learned through the Address Resolution Protocol (ARP) and added to the IP address translation table. The new entry consists of the specified IP address (host address), MAC address (physical address), and the type of encapsulation used (for example, ENET or SNAP). RMON_IP_ARP_INSERT 6 Reserved RMON_IP_RESERVED21 7 Entity enabled debug IP routing has been successfully enabled on the switch. RMON_IP_ENABLED 8 Invalid ARP source: <ip- addr> on <ip-addr> 9 Invalid ARP Target: <ip-addr> on <ip-addr> The specified ARP source address is invalid for the IP address. RMON_IP_INVALID_ARP_SOURCE The specified ARP target address is invalid on the IP address. RMON_IP_INVALID_ARP_TARGET 10 Reserved RMON_IP_RESERVED20 11 ICMP: Unsolicited Echo Reply from <ip-addr> There has been an unsolicited reply from the specified IP address. RMON_IP_UNSOL_ECHO_REPLY 12 Network enabled on <ip-addr> The network is enabled on the specified IP address. RMON_IP_NETWORK_ENABLED 13 Network disabled on <ip-addr> The network is disabled on the specified IP address. RMON_IP_NETWORK_DISABLED 14 Duplicate IP network There are two networks with the same IP address. RMON_IP_DUPLICATE_NET 15 Reserved RMON_IP_RESERVED19 16 Bad ip address <ip-addr> Invalid IP address. RMON_IP_BAD_IP_ADDR 1

17 Bad mask <ip-addr><mask> Invalid mask. RMON_IP_BAD_IP_MASK 18 IP address <ip-addr>/<mask> configured on vlan_id <vlan-id> 19 IP address <ip-addr> removed from vlan id <vlan-id> 20 MAC address <mac-addr> configured on vlan id <vlan-id> 21 MAC address <mac-addr> removed from vlan id <vlan-id> The specified IP address has been configured on the VLAN. RMON_IP_ADDR_ADD The specified IP address has been removed from the VLAN. RMON_IP_ADDR_DEL The specified MAC address has been configured on the VLAN. RMON_IP_MAC_ADD The specified MAC address has been removed from the VLAN. RMON_IP_MAC_DEL 22-35 Reserved RMON_IP_RESERVED1-14 36 Too many COS rules configured - limit of <max- rules> exceeded 37 Some COS configuration items will not be active 38 VLAN <vlan-id> QoS not configured on all new ports. Some QoS resources exceeded. 39 Too many QoS features enabled, mask resources exceeded 40 Initialization failed for TCP/UDP priority 41 Too many QoS ranges requested. Some configurations did not succeed. An attempt to create more than the maximum number of QoS rules allowed has occurred. RMON_COS_TOO_MANY_ERROR Some Class of Service (CoS) settings are not enabled. RMON_COS_NOT_ACTIVE_ERROR Some Class of Service (CoS) settings configured for the specified VLAN are not enabled on all ports. The threshold for certain QoS settings has been exceeded. RMON_COS_VLAN_COS_WONT_FIT Some of the items configured for Class of Service (QoS) will not be working. The maximum resources available have been exceeded. RMON_COS_MASKS_EXCEEDED For CoS TCP/UDP priority, the initialization failed. RMON_COS_APPTYPE_INIT_ERROR There was an error during CoS initialization for protocol-based prioritization. RMON_COS_RANGES_EXCEEDED 42 Reserved RMON_COS_RESERVED1-2 43 Unable to apply ACL <acl-name> to vlan <vlan-id>, failed to add entry <ace-num> to port <portnum> 44 Unable to add ACL entry to vlan <vlan-id>, not enough hw resources on port <port-num> The ACL was not applied to the specified VLAN and the ACE entry was not added to the port due to a lack of hardware resources on the port. RMON_ACL_WONT_FIT_VLAN_ERROR An ACE entry was not applied to an ACL, which has already been applied to the specified VLAN, due to a lack of hardware resources on the port. RMON_ACE_WONT_FIT_ERROR 2

45 Unable to add port to vlan <vlanid>, not enough hw resources on port <port-num> 46 Unable to add port to vlan <vlanid>, GVRP is enabled 47 Unable to add port <port-num> to trunk, ACL is configured on vlan <vlan-id> 48 Unable to apply ACL <acl-name> to port <port-num>, failed to add entry <ace-num> 49 Unable to add port <port-num> to trunk, ACL is configured on port. 50 Unable to add ACL to port <portnum>, an ACL is already configured on this port 51 Unable to modify ACL <aclname>, ACL is applied 52 Unable to delete ACL <aclname>, ACL is applied 53 Unable to apply ACL <acl-num> to vlan <vid> in direction <direction>, failed to add entry <entry> 54 Unable to apply ACL <acl-num> to port <port-num> in direction <direction>, failed to add entry <entry-num> 55 Unable to apply ACL <acl-num>, failed to add entry <entry-num>, max ACE limit reached The port was not added to the specified VLAN due to low hardware resources on the port. RMON_ACL_PORT_ADD_ERROR The port was not added to the specified VLAN because GVRP is enabled. RMON_ACL_NO_CONFIG_GVRP The port was not added to a dynamic trunk because an ACL is already configured on the port. When an ACL is applied to a port, the port does not support a dynamic trunk. RMON_ACL_PORT_ADD_TRUNK_VLAN_ERROR The ACL was not applied to the port and the ACE entry was not added due to a lack of hardware resources. RMON_ACL_WONT_FIT_PORT_ERROR The port was not added to the trunk because an ACL is configured on the port. RMON_ACL_PORT_ADD_TRUNK_PORT_ERROR The ACL is not added to the port because an ACL is configured on the port. RMON_ACL_PORT_ADD_ERROR_ACL_CONFIG The ACL name cannot be modified once it has been applied. RMON_ACL_MODIFY_ERROR The ACL cannot be deleted because it is applied. RMON_ACL_DELETE_ERROR There was an error applying the ACL due to lack of hardware resources. RMON_ACL_VLAN_HW_RESOURCE_ERROR There was an error applying the ACL because of insufficient hardware resources. RMON_ACL_PORT_HW_RESOURCE_ERROR There was an error applying the ACL because the maximum ACE limit for ACLs was reached. RMON_ACL_MAX_ACE_ERROR 56 Spanning Tree Protocol enabled The spanning tree protocol has been enabled. RMON_STP_ENABLE 57 Spanning Tree Protocol disabled The spanning tree protocol has been disabled. RMON_STP_DISABLE 58 STP: stp max age should be >= XXX STP: stp fwd delay should be >= XXX The STP Max Age or Forward Delay parameter should be greater than the value "XXX", where XXX is calculated by the switch. RMON_STP_BAD_CONFIG 3

59 STP: BPDU has MAX_AGE 0 from port <port-num> STP: BPDU has HELLO_TIME 0 from port <port-num> STP:BPDU has FWD_DELAY 0 from port <port-num> 60 Bad reconfiguration request <request> The switch received a BPDU packet with an invalid Max Age, Hello Time, or Forward Delay value on the specified port. Check to see if the parameter was misconfigured on the other bridge. RMON_STP_BAD_BPDU An invalid configuration request has been made. RMON_STP_BAD_DYNAMIC_REQ 61 --------------------- Blank line RMON_BOOT_BLANK_LINE 62 Management module <modulenum> went down without saving crash rmation 63 Mgmt Module <mod-num> went down The specified management module crashed without saving a crash record. RMON_BOOT_NO_CRASH_RECORD The specified management module was rebooted. RMON_BOOT_CRASH_RECORD0 64 <crash- msg> Text message explaining the reasons for a system crash, which may include the type of crash (out of resources or bus error), task name, filename and line number (bus address). RMON_BOOT_CRASH_RECORD1 65 Boot-up selftest failed Self test failed while switch is booting up. RMON_BOOT_SELFTEST_FAILURE 66 System booted System booted up. RMON_BOOT_COMPLETE 67 Slot <slot-num> removed The module in the specified slot has been removed. RMON_CHASSIS_HOTSWAP_REMOVED 68 Slot <slot-num> inserted A module has been inserted into the specified slot. RMON_CHASSIS_HOTSWAP_SELFTEST0 69 Slot <slot-num> Hotswap Failure A module hotswap failure occurred in the specified slot. RMON_CHASSIS_HOTSWAP_FAILURE 70 Fan <fan-num>: Fan: <fan-state> Failures: <num> 71 Power Supply <pwr-supply>: Supply: <pwr-state>, Failures: <num> A fan (fan 1 or fan 2) has failed or a failed fan is no longer failing, as indicated by the fan state (failure or OK). The number of times that the fan failed is also displayed. In case of failure, the fan fail LED is lit. RMON_CHASSIS_FAN_STATUS One of the following power conditions exists: The redundant power-supply (RPS) is failing. The RPS is operational but the main power supply is failing. A failed power supply is no longer failing. The state of the power supply (main or RPS) is indicated as failure or OK. The number of times that the power supply failed is also displayed. In case of failure, the power fail LED is lit. RMON_CHASSIS_POWER_STATUS 4

72 Slot <slot-num> Inactive: Module/Configuration mismatched The module or configuration is incompatible for this slot. RMON_CHASSIS_MODULE_INCOMPAT 73 Reserved RMON_CHASSIS_RESERVED 74 Unused RMON_BUF_PIG 75 Out of <msg_pkt> buffers; miss count: <num> The number of misses indicates the number of times that an attempt to allocate the specified message or packet buffer failed. RMON_BUF_MISS 76 Port <port-num> is now on-line The specified port is now online. RMON_PMGR_PORT_UP 77 Port <port-num> is now off-line The specified port is now offline. RMON_PMGR_PORT_DOWN 78 Trunk <trunk-num> is now active The specified trunk is now active. RMON_PMGR_TRUNK_UP 79 Trunk <trunk-num> is now inactive. The specified trunk is now inactive. RMON_PMGR_TRUNK_DOWN 80 Entity enabled debug DHCP has been successfully enabled on the switch. RMON_DHCP_ENABLED 81 Initialization failed The initialization failed. RMON_DHCP_INIT_FAILED 82 Can t allocate any msg buffers DHCP needs to allocate message buffers, but none are available. No message buffers can be allocated. RMON_DHCP_NO_NSG_BUFS 83 Updating IP address and subnet mask 84 Subnet in DHCP/BOOTP reply is already being used 85 Unable to renew an expired DHCP lease. 86 Invalid IP address <ip-address> is received for Option 66 87 Unable to download Config File (using TFTP) with <num-retries> retries 88 Unexpected hostname received in DHCP response DHCP is updating the IP address, subnet mask and default gateway for a VLAN interface. If this is a lease renewal, then the IP configuration is different from the prior lease configuration. RMON_DHCP_IP_UPDATE The subnet in the DHCP/BOOTP reply is already in use. RMON_DHCP_DUP_SENT The expired DHCP lease cannot be renewed. RMON_DHC_RENEW_FAILED The TFTP server IP address received for DHCP Option 66 is invalid. RMON_DHCP_INCORRECT_OPTION_66 After multiple retries, DHCP is unable to download the configuration file from the TFTP server. RMON_DHCP_GET_CFG_FAIL An unexpected hostname was received from DHCP. RMON_DHCP_UNEXPECTED_HOSTNAME 5

89 Unable to download Image File (using TFTP) with <number> retries 90 Trying to download Config File (using TFTP) received in DHCP from <source> 91 Trying to download Image file (using TFTP) received in DHCP from <source> 92 Enabling Auto Image Config Download via DHCP and turning off auto-tftp if enabled 93 Image file download and validation vai DHCP completed sucessfully 94 Config file download and validation via DHCP completed successfully 95 DHCP lease expired on Primary VLAN. Cleaning up DNS entries The image file could not be downloaded after the specified number of retries. RMON_DHCP_GET_IMG_FAIL There is an attempt to download the config file received in DHCP from the indicated source. RMON_DHCP_GET_CFG_TRY There is an attempt to download an image file received in DHCP from the indicated source. RMON_DHCP_GET_IMG_TRY The auto image feature is enabled; if auto-tftp is active, it is turned off. RMON_DHCP_GET_IMG_ON The image file download and validation has completed successfully. RMON_DHCP_GET_IMG_SUCCESS The config file download and validation has completed successfully. RMON_DHCP_GET_CFG_SUCCESS The DCHP lease on the primary VLAN expired. The DNS entries are being cleaned up. RMON_DHCP_LEASE_EXPIRED 96 DHCP disabled on Primary VLAN DHCP is disabled on the primary VLAN. The DNS entries are being cleaned up. RMON_DHCP_DISABLED 97 No Resource for Download Request from <ip-addr> or <ipxnetwork-num> The resource identified by the IP address or IPX network number, from which a remote download request was received, could not be found. RMON_SNMP_DOWNLD_NO_RESOURCE 98 Download Request Received from <ip-addr> or <ipx-networknum> A download request was received from the specified IP address or IPX network. RMON_SNMP_DOWNLD_REQ_RCVD 99 Download: OS TFTP in progress, SNMP denied. From Switch Console or <ip-addr>. A TFTP download may already be in progress. The current download attempt from the switch console or a remote device is temporarily denied. RMON_SNMP_DOWNLD_ABORTED 100 Reserved RMON_SNMP_DOWNLD_RESERVED2 101 Unused RPM_TCP_INIT_BAD_CFG_STAT 102 Unused RMON_TCP_INIT_ENABLED 6

103 Reserved RMON_TCP_RESERVED5 104 Unused RMON_TCP_NO_CTRL_BLOCK 105 Unused RMON_TCP_CLOSE_EVENT 106-109 Reserved RMON_TCP_RESERVED1-4 110 telnetd service enabled The telnet service has been enabled. RMON_TLNT_ENABLED 111 Telnet connection <connection> has closed 112 Telnet connection <session> from <ip-address> The telnet connection has closed. RMON_TLNT_DISCON A telnetd telnet has connected on the specific session id from the specified IP address. RMON_TLNT_CONN 113 Unused RMON_TLNT_OUT_ENABLED 114 The telnetd subsytem has issued a 115 The telnetd subsystem has issued an error standard The telnet subsystem has issued a. RMON_TLNT_WARNING The telnet subsystem has issued an error. RMON_TLNT_ERROR 116 Unused RMON_TLNT_OPEN_FAIL_P23 117 Unused RMON_TLNT_RESERVED 118 Timep client enabled The TimeP client has been enabled. RMON_TIMEP_ENABLED 119 Can t reach time server <ipaddr> Unable to connect to the time server at the specified IP address. RMON_TIMEP_NO_SERVER 120 Client polling server at <ip-addr> A client is polling the time server at the specified IP address. RMON_TIMEP_POLLING_SERVER 121 Changing time The time is being changed. RMON_TIMEP_CHANGING_TIME 122 New time set A new time has been set. RMON_TIMEP_SET_TIME 123-125 Reserved RMON_TIMEP_RESERVED1-3 126 TFTP: PUT <type> to <ip-addr>, file <filename> TFTP is trying to copy the specified file and object type (CONFIG or CRASH RECORD) to the host IP address. RMON_TFTP_PUT_FILE 7

TFTP is trying to copy a remote file from the host IP address to the specified local file of object type CONFIG, OS, or CRASH RECORD. RMON_TFTP_GET_FILE 128 Enable succeeded The download TFTP capability has been successfully initialized. RMON_TFTP_ENABLED 129 WRQ from <ip-addr> for file <filename> 130 RRQ from <ip-addr> for file <filename> TFTP received a write request from the sender at the IP address for the specified file. RMON_TFTP_WRQ_FILE TFTP received a read request from the sender at the IP address for the specified file. RMON_TFTP_RRQ_FILE 131 Transfer completed The TFTP transfer has been completed. RMON_TFTP_XFER_COMPLETE 132 RCVD error: <err-num>, msg: <msg-text> There was an error during the TFTP transfer process. RMON_TFTP_RCVD_ERR 133 Transfer timed out The TFTP transfer timed out. RMON_TFTP_TIMED_OUT 134 Sent error: <err-num>, msg: <msg-text> An error message about the TFTP transfer was logged. RMON_TFTP_ERR_SENT 135 Transfer aborted, wrong file The TFTP transfer was aborted because of an incorrect file. RMON_TFTP_WRONG_FILE 136 Connection to <server-name> failed The connection to the TFTP server failed. RMON_TFTP_CONN_FAILED 137 Request failed. The request for a TFTP transfer failed. RMON_TFTP_REQ_FAILED 138 TFTP daemon enabled debug The TFTP process has been enabled for debugging purposes. RMON_TFTP_DAEMON_ENABLED 139 TFTP daemon failed The TFTP process would not run. RMON_TFTP_DAEMON_FAILED 140 Transfer canceled. No workspace left on device 141 Transfer canceled. Downloaded file corrupt. 142 Transfer Fatal Error. Hardware fault on device, Corrupt FLASH. 143 Transfer canceled. File too big to fit in FLASH. The TFTP transfer was canceled because there is no more room on the device. RMON_TFTP_NO_SPACE The TFTP transfer was canceled because the file is corrupt. RMON_TFTP_CORRUPT_FILE The flash on the hardware device is corrupt, so the TFTP transfer failed. RMON_TFTP_HARDWARE_FAULT The transfer was canceled because the file won t fit in FLASH. RMON_TFTP_TOO_BIG 127 TFTP: GET <local-filename> from <ip-addr>, file <remotefilename> 144-149 Reserved RMON_TFTP_RESERVED19-24 8

150 Completed File transfer is completed RMON_FT_XFER_COMPLETE 151 Aborted. No workspace left in switch DRAM. The file transfer was aborted because there is no space in DRAM. RMON_FT_NO_SPACE 152 Aborted. Downloaded file invalid. The file being downloaded is invalid so the transfer is aborted. RMON_FT_CORRUPT_FILE 153 Aborted with Fatal Error. Hardware fault on device, Corrupt FLASH. 154 Aborted. File too big to fit in FLASH. The Flash is corrupt so the file transfer was aborted. RMON_FT_HARDWARE_FAULT The file was too big to fit in FLASH so the transfer was aborted. RMON_FT_TOO_BIG 155 Aborted, wrong file The wrong file was being transferred, so the transfer was aborted. RMON_FT_WRONG_FILE 156 Finished, identical file, no update performed 157 Disabled RMON to retrieve memory for download The transfer was not completed because the same file is already there. RMON-FT-IDENTICAL_FILEE RMON was disabled so memory can be used for downloading a file. RMON_FT_DISABLE_RMON 158 Line <line-num> <msg-txt> This error is generated when a corrupt command file is parsed. The line number and a text message describing the type of corruption are displayed. RMON_FT_CLI_CORRUPT_FILE 159 <filename> transferred successfully 160 <filename> transfer failed after <num> retransmits 161 Aborted. File does not contain required code signature. 162 Aborted. File code signature is invalid The specified file was transferred successfully. RMON_FT_FILE_XFER_COMPLETE The file transfer failed after the indicated number of retransmits. RMON_FT_FILE_XFER_FAILURE Aborted. Firmware imaged does not contain a signature. RMON_FT_MISSING_SIGNATURE The firmware image signature is not valid. RMON_FT_BAD_SIGNATURE 163 File contains valid signature The firmware image contains a valid signature. RMON_FT_VALID_SIGNATURE 164 Aborted. File does not support enhanced secure mode The firmware image does not support enhanced secure mode. RMON_FT_ENHSEC_INCAPABLE 165-175 Reserved RMON_FT_RESERVED 176 debug Unused RMON_DMA_GENERIC 9

177 Changing time The system time has been changed. RMON_NCL_CHANGING_TIME 178 New time set A new system time was set. RMON_NCL_NEW_TIME 179 Mgr: SME CONSOLE Session - MANAGER Mode established Mgr: SME CONSOLE Session - OPERATOR Mode established A console session has started either through a device connected to the console port or Telnet. The console is in manager or operator mode. RMON_NCL_SESSION_EST 180 A remote login attempt failed A remote login attempt failed. RMON_NCL_INVALID_PASSWORD 181 10 invalid passwords on <session-type> session. 182 Password(s) removed via clear button 183 Password file corrupted - ignoring passwords 184 Log cleared as a result of clear logging command 10 or more invalid passwords were entered in a Telnet or console session. RMON_NCL_MANY_INVALID_PASSWORD The passwords were cleared when the Clear button was pressed. RMON_NCL_PASSWORDS_REMOVED The password file is corrupt so passwords are ignored. RMON_NCL_PASSWORD_FILE_CORRUPT The clear logging command was issued and the log was cleared. RMON_NCL_LOG_CLEAR 185-186 Reserved RMON_NCL_RESERVED2-3 187 Terminal connection broken The terminal connection has been broken. RMON_XM_TR_DISC 188 Failed Checksum during Transfer The checksum failed during transfer. RMON_XM_BAD_CHECKSUM 189 Transfer terminated by remote Transfer terminated by the remote terminal. RMON_XM_TR_TERMINATED 190 Cannot open local file, transfer aborted 191 Received a bad 32 bit CRC on a data packet 192 Transfer canceled. No space left on device. The transfer was aborted because the local file could not be opened. RMON_XM_OPEN_ERROR Received a bad 32 bit Cyclic Redundancy Check (CRC) data packet. RMON_XM_BAD_32CRC_DATA The transfer was canceled because there is no space left on the device. RMON_XM_NO_SPACE 193 Too many bytes before SOF Too many bytes before the Start of Frame (SOF). RMON_XM_JABBER_SOF 194 Bad data subpacket from remote There was a bad data packet from the remote device. RMON_XM_BAD_SUBPACKET 10

195 Transfer terminated due to timeout 196 Received a bad 16 bit CRC on binary header 197 Received a bad 32 bit CRC on binary header 198 Received a bad 16 bit CRC on hex header warm The transfer was terminated because it timed out. RMON_XM_TR_TIMEOUT A bad 16 bit CRC packet was received on a binary header. RMON_XM_BAD_16CRC_BINARY A bad 32 bit CRC packet was received on a binary header. RMON_XM_BAD_32CRC_BINARY A bad 16 bit CRC packet was received on the hexadecimal header. RMON_XM_BAD_16CRC_HDR 199 Reserved RMON_XM_RESERVED3 200 No Question Marks Unused RMON_XM_TIMEOUT_REMOTE 201 Unable to get remote init parameters Unable to get the initialization parameter from the remote device. RMON_XM_REMOVE_INIT_FAILED 202 Transfer complete The Xmodem transfer was completed. RMON_XM_XFER_COMPLETE 203 Unable to connect to remote Xmodem device unable to connect to the remote device. RMON_XM_REMOTE_CONNECT_FAILED 204 Config file cannot be appended, set for overwrite The configuration file is set to be overwritten; the new rmation is not appended. RMON_XM_CONFIG_APPEND_FAILED 205 Reserved RMON_XM_RESERVED2 206 Unable to synchronize with remote Unable to synchronize with the remote device. RMON_XM_UNABLE_SYNC_REMOTE 207 Transfer aborted, wrong file The Xmodem file transfer was aborted because of an incorrect file. RMON_XM_TR_WRONG_FILE 208 Reserved RMON_XM_RESERVED1 209 Unable to read header from remote Unable to read the header in the packet from the remote device. RMON_XM_BAD_HDR_REMOTE 210 Unable to read data from remote Unable to read the data from the remote device. RMON_XM_BAD_DATA_REMOTE 211 Filename too long The XModem transfer filename is too long. RMON_XM_FILENAME_TOO_LONG 212 remote appended data to existing file The remote device appended the transfer data to the existing file. RMON_XM_TR_WARN_FILE_APPEND 11

213 Timeout trying to sync with remote The transfer timed out because the Xmodem device could not sync with the remote device. RMON_XM_TIMEOUT_TRYING_SYNC_REMOTE 214 Xmodem transfer aborted The XMODEM transfer was aborted. RMON_XM_ABORT 215 Unexpected character from remote An unexpected character was received from the remote. RMON_XM_UNEXPECTED_CHAR 216- Reserved RMON_XM_RESERVED4 217 Config file updated to default configuration. 218 Config file converted due to OS upgrade 219 Config file updated via configuration editor 220 Config file updated from network download 221 Config file erased via testmode clear command 222 Config file erased via the NCL delete command 223 Config file updated via Bootp Reply 224 No configuration summary record The configuration file has been updated to the default configuration. RMON_CFG_DEFAULT_SET The Operating System file was upgraded and the configuration file converted. RMON_CFG_CONVERSION A user has updated the configuration file with the editor. RMON_CFG_USER_CHANGE The configuration file was updated from a download over the network. RMON_CFG_DOWNLOAD The configuration file was erase because a testmode clear command was executed. RMON_CFG_TESTMODE_CLEAR The configuration file was erased using the NCL delete command. RMON_CONFIG_NCL_CLEAR The config file was updated via a BOOTP reply. RMON_CFG_BOOTP_REPLY There is no configuration summary record. RMON_CFG_BAD_CONFIG 225 Attempt to store a string with an illegal character (tilde): <char> 226 Unsupported feature \ FEC\ for trunk configuration: see release notes. 227 Partial config deleted for subsystem <subsystem-name> standard The specified character is not supported in the string to be stored. RMON_CONFIG-ILLEGALCHAR Refer to the release notes for the installed software version to verify Fast EtherChannel (FEC) support. RMON_CONFIG_FEC_UNSUPPORTED An unrecognizable configuration item was deleted when the firmware was updated. RMON_CONFIG_REC_CONV_ERR 12

228 Traffic filter configured in row <row-num> is not active 229 Traffic filter configured in row <row-num> is not valid 230 Traffic filter configured in row <row-num> was deleted The traffic filter in the specified row is not active. RMON_FILTER_NOT_ACTIVE The traffic filter configured in the specified row is not valid. RMON_FILTER_NOT_VALID The traffic filter configured in the specified row was deleted. RMON_FILTER_DELETED 231-232 Reserved RMON_FILTER_RESERVED1-2 233 \ public\ community deleted. Net Mgmt may have problems snmp: public community deleted. Net Mgmt may have problems 234 Too many manager addrs for <src-ip-addr> - ignoring rest 235 Too many communities specified - ignoring <community-name> 236 SNMP Security access violation from <src-ip-addr> 237 SNMP Security write violation from <src-ip-addr> The community name public was deleted. Network management may not function correctly without the presence of this community name. RMON_SNMP_PUBLIC_DELETED Unused RMON_SNMP_TOO_MANY_MANAGERS Too many community names have been configured; the specified community name is ignored. RMON_SNMP_TOO_MANY_COMMUNITIES There has been a security access violation from the specified source IP address. RMON_SNMP_SECURITY_ACCESS_VIOLATION There has been an SNMP security write violation from the specified source IP address. RMON_SNMP_SECURITY_SET_VIOLATION 238 Alarm <alarm-name> The specified alarm occurred. RMON_SNMP_ALARM 239 SNMP community configured in row <row-num> not active 240 SNMP manager address configured in row <row-num> not active 241 SNMP trap receiver configured in row <row-num> not active The SNMP community name in the specified row is not active. RMON_SNMP_COMM_NOT_ACTIVE The SNMP manager address in the specified row is not active. RMON_SNMP_MGR_NOT_ACTIVE The SNMP trap configured in the specified row is not active. RMON_SNMP_TRAP_NOT_ACTIVE 242 Event <event-desc> The specified event occurred. RMON_SNMP_EVENT 243 SNMP changed Engine Id to <idnum>. The user table may need to be re-entered 244 SNMP Engine boots value maxed. SNMPv3 Administration may no longer work. The engine ID changed. The new value needs to be entered in the SNMP user table. RMON_SNMP_ENGINEID_CHANGED The boots value of the SNMP engine is maxed out. SNMPv3 may no longer work correctly. RMON_SNMP_ENGINE_BOOTS_MAXED 13

245 RMON <filename> file corrupt, is being renamed to <filenamebad> SNMP: RMON events file corrupt, is being renamed to event_bad. SNMP: RMON alarms file corrupt, is being renamed to alarms_bad. 246 Unable to add port <port-num> to trunk, IP lockdown is configured on port. 247 Unable to apply IP lockdown to port <port-num>, not enough hw resources 248 Unable to add IP lockdown to port <port-num>, IP lockdown already configured on port. 249 Unable to modify IP lockdown on port <port-num>, IP lockdown already active on port Either the alarms file or the events file is corrupt and was renamed to alarms_bad or event_bad, respectively. RMON_SNMP_MOVE_CORRUPT_FILE The port was not added to the trunk because IP lockdown is configured on the port. RMON_IPLOCK_TRUNK_ERROR IP lockdown was not applied to the port due to a lack of hardware resources. RMON_IPLOCK_RESOURCE_ERROR IP lockdown is already configured on the specified port. RMON_IPLOCK_EXISTS_ERROR IP lockdown cannot be modified on the port as it is already active on the port. RMON_IPLOCK_MODIFY_ERROR 250-254 Reserved RMON_IPLOCK_UNUSED4-8 255 Cannot configure trunk <trunknum> - out of resources Sufficient hardware resources are not available to configure the specified trunk. RMON_PMGR_CANT_CONFIGURE_TRK 256-259 Reserved RMON_UNUSED_256-259 260 Mgmt Module <mod-num> Active 261 Mgmt Module <mod-num> in Standby Mode 262 Mgmt Module <mod-num> Failed - Synchronization Failed 263 Mgmt Module <mod-num> Offline (redundancy disabled) 264 Mgmt Module <mod-num> Failed Selftest The specified management module is active. RMON_SYSTEM_MGMT_MOD_ACTIVE The indicated management module is in standby mode. RMON_SYSTEM_MGMT_MOD_STANDBY The specified module failed to synchronize. RMON_SYSTEM_MGMT_FAILED_SYNC The no redundancy management-module command was issued. The specified management module is offline. The management module redundancy feature is now disabled. RMON_SYSTEM_MGMT_OFFLINE The specified management module failed self-test and will not become an active or standby management module. RMON_SYSTEM_MGMT_FAILED 14

265 Lost communication with Mgmt Module <mod-num> 266 Resetting Mgmt Module <modnum> 267 Mgmt Module <mod-num>- Running different version of SW 268 Mgmt Module <mod-num> - Failover occurred 269 Mgmt Module <mod-num>] - User initiated switchover occurred 270 Mgmt Module <mod-num>- Offline (incompatible SW versions) 271 Other management module is not in standby, shutdown request ignored 272 Mgmt Module <mod-num> Offline (shutdown) 273 Resetting Mgmt Module <modnum> <reason for reset> 274 Slot <slot-num> self test failure or unsupported module. 275 STP not enabled - multiple VLANS defined 276 testmode: Internal use only. DO NOT PUBLISH 277 testmode: Internal use only. DO NOT PUBLISH A management module failed to receive heartbeats from the other management module. RMON_SYSTEM_MGMT_LOST_COMM The specified management module is reset. This can occur if you perform a boot standby command or for other reasons when an individual module is rebooted. RMON_SYSTEM_MGMT_RESET The specified management module is running a different version of software from the other management module. RMON_SYSTEM_MGMT_OS_DIFF A switchover occurred because of a hardware or software failure or because the management module reset button was pressed. RMON_SYSTEM_MGMT_FAILOVER The user has initiated switchover using the redundancy switchover command so that the other management module can become the active management module. RMON_SYSTEM_MGMT_SWITCHOVER The software version in the specified management module is not compatible with the other module and it has gone offline. RMON_SYSTEM_MGMT_INCOMPAT_OS A shutdown request is ignored because the standby module is not in standby mode. A management module must be in active or standby mode to be shut down. The module goes into a down state which allows you to safely swap it out. RMON_SYSTEM_MGMT_HSBUTTONERR The specified management module is offline because of a shutdown. RMON_SYSTEM_MGMT_SHUTDOWN The indicated management module is being reset for the reason displayed. RMON_SYSTEM_MGMT_RESET_REASON The specified slot failed self-test. There may be an unsupported module in the slot. RMON_CHASSIS_SLOT_FAIL STP was not enabled because multiple VLANs are defined. RMON_STP_MULTI_VLANS Test mode RMON_TESTMODE_INFO Test mode RMON_TESTMODE_WARN 15

278 Module in slot <slot-num> not allowed The module in the specified slot is not supported by current configuration rules; for example, the third ESP module in an alpha chassis is not supported. Slots are lettered, starting with A'. RMON_CHASSIS_INVALID_SLOT 279 Reserved RMON_UNUSED_279 280 Unused RMON_STACK_TEMP_STATUS 281 Unused RMON_STACK_POWER_STATUS 282 Unused RMON_STACK_DEVICE_STATUS 283 Unused RMON_STACK_DEVICE_FAIL 284 Unused RMON_STACK_RPS_FAIL 285 Unable to learn/age MAC addresses, table FULL 287 Static address missing during address deletion attempt debug The MAC address table is full, so MAC addresses cannot be discovered or aged. RMON_ADDRMGR_TBL_FULL The static address was not found during an address deletion attempt. RMON_ADDRMGR_ADDR_MISSING 288-289 Reserved RMON_ADDRMGR_RESERVED3-4 290 Multicast address table is full The multicast table is full, so the IGMP MAC address is not added. RMON_IGMP_MAC_NOT_ADDED 291 IGMP feature enabled. The IGMP feature has been enabled. RMON_IGMP_ENABLED 292 Querier initialization failed The querier initialization failed. RMON_IGMP_QUERIER_INIT_ERROR 293 Port initialization failed for port <port-num> The initialization on the specified port failed. RMON_IGMP_PORT_INIT_ERROR 294 IGMP feature disabled IGMP has been disabled. RMON_IGMP_DISABLED 295 Querier Election feature disabled The querier election feature has been disabled. RMON_IGMP_QUERIER_DISABLED 296 Querier Election feature enabled The querier election feature has been enabled. RMON_IGMP_QUERIER_ENABLED 297 Entity enabled debug IGMP has been successfully enabled on the switch. RMON_IGMP_INIT 16

298 Querier Election in process The querier election is in process. RMON_IGMP_ELECTION_IN_PROC 299 This switch has been elected as Querier 300 This switch was not elected as Querier The switch has been chosen as the querier switch for IGMP. RMON_IGMP_ELECTION_WON The switch was not chosen as the querier switch for IGMP. RMON_IGMP_ELECTION_LOST 301 Other Querier detected. Another Querier has been detected. RMON_IGMP_QUERIER_DETECTED 302 This switch is no longer Querier This switch is no long the Querier switch. RMON_IGMP_QUERIER_BACK_OFF 303-305 Reserved RMON_ADDRMGR_RESERVED14-16 306 Unable to alloc memory <operation> 307 Number of domains at max <maxlimit> 308 BAD multicast range <ip-addr>, <ip-addr> passed in 309 Requested Domain was not found <domain-name> 310 Domain <domain-name> still associated with VLANs, cannot delete 311 Unable to alloc a packet buffer, to send <pkt-type> 312 IP address not enabled on VLAN <vlan-id> 313 VLAN <vlan-id> already associated with the IGMP Domain <domain-name> 314 VLAN <vlan-id> not currently associated with domain <domain-name> standard standard The switch was unable to allocate the required memory for one of the following operations: Initialization Configuration To add proxy join To send proxy join RMON_IGMP_PROXY_MALLOC_FAILED The number of domains has reached the maximum limit allowed. RMON_IGMP_PROXY_DOMAIN_LIMIT_EXCEEDED An invalid multicast range was entered. RMON_IGMP_PROXY_BAD_MULTICAST_RANGE The requested domain was not found. RMON_IGMP_PROXY_DOMAIN_NOT_FOUND A domain associated with a VLAN cannot be deleted. RMON_IGMP_PROXY_DOMAIN_CONNECTED_TO_VLAN The switch was unable to allocate a packet buffer to send one of the following types of reference packet: JOIN, LEAVE, or QUERY. RMON_IGMP_PROXY_PKT_ALLOC_FAILED The IP address was not enabled on the VLAN. RMON_IGMP_PROXY_NO_IP_ADDRESS The VLAN is already associated with the IGMP domain. RMON_IGMP_PROXY_VLAN_ASSOC_WITH_DOMAIN The VLAN is not associated with the domain. RMON_IGMP_PROXY_VLAN_NOT_ASSOC_WITH_DOMAIN 17

315 NULL Domain name passed for target IP <ip-addr> There was no domain name given to the target IP address. RMON_IGMP_PROXY_NULL_DOMAIN_NAME 316 VLAN ID out of range <vlan-id> The VLAN ID requested is not within the range of valid values. RMON_IGMP_PROXY_BAD_VLAN 317 BAD Target IP address <ip-addr> Bad target IP address. RMON_IGMP_PROXY_BAD_TARGET 318-322 Reserved RMON_UNUSED_318-322 323 VLAN <vlan-id> defined but not active 324 Port <port-num> is member of an invalid VLAN <vlan-id> 325 Port initialization failed for port <port-num> 326 Port <port-num>: Xcvr not supported in current OS 327 Port <port-num> - Excessive undersized/giant packets. See help. 328 Port <port-num> - Excessive jabbering. See help. 329 Port <port-num> - Excessive CRC/alignment errors. See help. 330 Port <port-num> - Excessive late collisions. The VLAN has been configured but is not active. RMON_VLAN_NOT_ACTIVE The port is a member of an invalid VLAN. RMON_VLAN_INVALID_MEMBER Initialization failed on the specified port. RMON_PMGR_INVALID_PORT The transceiver in the specified port is not supported with the current software version. RMON_PPMGR_XCVR_INVALID An excessive number of undersized or giant packets were received on the specified port. Refer to the help rmation for more details. RMON_FF_BAD_DRIVER_NIC A device on this port is incessantly transmitting packets ( jabbering is detected as oversized packets with CRC errors) or transmitting excessive fragments. Possible causes: A misconfigured NIC, or a malfunctioning NIC or transceiver. It could also be caused by a short-circuit in the network cable path. Actions: 1. Check the NIC for a misconfiguration. 2. Update the NIC firmware. 3. UPdate the NIC driver software. 4. Replace the NIC or transceiver. 5. Check for a short-circuit in the cable path connected to this port. RMON_FF_BAD_XCVR_NIC An excessive number of cyclic redundancy check (CRC) or alignment errors were reported on the specified port. Refer to the help rmation for more details. RMON_FF_BAD_CABLE An excessive number of late packet collisions have been reported on the specified port. RMON_FF_CABLE_LEN_HOPS 18

331 Port <port-num> - High collision or drop rate. See help. 332 Port <port-num> - Excessive Broadcasts. See help. A high collision or drop rate for packets has been reported on the specified port. Refer to the help rmation for more details. RMON_FF_LOOP_OVER_BAND An excessive number of broadcast packets have been received on the specified port. Refer to the help rmation for more details. RMON_FF_BCAST_STORM 333 Port <port-num> - Loss of Link The link on the specified port was lost. RMON_FF_LOSS_OF_LINK 334 Port <port-num> - Security violation 335 Port <port-num>: exceeded threshold broadcast throttling started 336 Port <port-num>: broadcast throttling stopped 337 Port <port-num> is Forwarding in Trunk mode 338 Port <port-num> is Forwarding in Trunk Mode Port <port-num> is Listening for PAgP re-negotiation 339 Port <port-num> is Forwarding in Trunk mode Network misconfiguration is detected. Port <port-num> is blocked. 340 Port <port-num> is Forwarding in FEC mode, nego. successful 341 Port <port-num> is Listening for PAgP negotiation 342 Detected network misconfiguration on port <portnum> A security violation occurred on the specified port. RMON_FF_SECURITY_VIOLATION Broadcast throttling has been initiated because a threshold was exceeded. RMON_PPMGR_PORT_BCASTSTART Broadcast throttling has been disabled on the specified port. RMON_PPMGR_PORT_BCASTSTOP The specified port is forwarding packets in trunk mode. RMON_PAGP_NEGO_FAIL_FWD A port is forwarding traffic in trunk mode. The specified port is listening for renegotiation. RMON_PAGP_NEGO_FAIL_BLOCK The specified port is forwarding traffic in trunk mode. A network misconfiguration is detected and the port is blocked. RMON_PAGP_NETWORK_MISCFG_BLOCK The specified port is forwarding traffic in FEC mode; PAgP negotiation was successful. RMON_PAGP_NEGO_SUCCEED_FWD PAgP negotiation has started on the specified port. RMON_PAGP_PORT_UP_BLOCK A network misconfiguration was detected on the specified port. RMON_PAGP_NETWORK_MISCFG 343 Reserved RMON_PAGP_RESERVED 344 Load Balance Protocol enabled The load balancing protocol is enabled. RMON_LDBAL_ENABLE 345 Load Balance Protocol disabled The load balancing protocol is disabled. RMON_LDBAL_DISABLE 19

346 Port <port-num> - established The port is established for load balancing. RMON_LDBAL_PORT_ESTABLISHED 347 Port <port-num> - not established 348 Port <port-num> - detected topology error: <mac-addr> 349 Domain size exceeded protocolimposed limit: <limit-size> 350 Port <port-num> - Rx untagged pkt. PktType <pkt-type> 351 Port <port-num> - Rx Type2 Query NAK 352 MAC <mac-addr> moved from <slot-num> <port-num> to <slotnum> <port-num>: <mac-addr> 353 Port <port-num> - Received Update Pkt from <mac-addr> 354 Non existent address <macaddr> deleted debug debug debug debug The port is not established for load balancing. RMON_LDBAL_PORT_NOT_ESTABLISHED An invalid topology was detected on a port configured for load balancing at the specified MAC address. RMON_LDBAL_PORT_TOPOLOGY_ERROR The domain size exceeded the limit the protocol allows. RMON_LDBAL_DOMAIN_SIZE_EXCEEDED An untagged packet was received on the specified port configured for load balancing. RMON_LDBAL_RX_UNTAGGED_PKT A Type2 Query NAK was received on the specified port configured for load balancing. RMON_LDBAL_BAD_QUERY_ADDR A MAC address was moved from one port to another port on the switch. RMON_LDBAL_MAC_ADDR_MOVE The specified port received an update packet from the MAC address. RMON_LDBAL_RX_UPDATE_PKT A non-existent MAC address was deleted. RMON_LDBAL_ADDR_NOT_EXIST 355 debug Unused RMON_LDBAL_ADDR_MISMATCH 356 Port <port-num> - ACK failure for pkt <pkt-num> 357 Port <port-num>: ldbal version <ver-num> not supported, update OS 358 Type-2 qry rvc: dup MAC <macaddr> debug debug There was an packet acknowledgement failure on the specified port. RMON_LDBAL_ACK_FAILURE The specified load balancing version is not supported on the current software version. RMON_LDBAL_VERSION_NOT_SUPPORTED A duplicate MAC address was received in a Type-2 query. RMON_LDBAL_GENERIC 359 GARP protocol enabled The GARP protocol has been enabled. RMON_GARP_ENABLE 360 GARP Protocol disabled The GARP protocol has been disabled. RMON_GARP_DISABLE 361 Unknown application <appname> PDU received A PDU from an unknown application was received. RMON_GARP_UNKNOWN_APPN 362 GVRP Protocol enabled The GVRP protocol has been enabled. RMON_GVRP_ENABLE 20

363 GVRP Protocol disabled The GVRP protocol has been disabled. RMON_GVRP_DISABLE 364 <msg-txt> GVRP received a malformed packet. One of the following messages is displayed: Unknown attribute Type. Received <value> Expected 1. Packet too small. Got <pkt-size>. Expected <pkt-size>. Invalid attribute length. Got <pkt-size>. Expected <pkt-size>. RMON_GVRP_BAD_PKT 365 Failed to create VLAN <vlan-id>. Max VLANs created. 366 Port <port-num> Carrier Sense Stuck, Resetting Xcvr The VLAN was not created because the maximum number of supported VLANs are already configured. RMON_GVRP_NO_RESOURCES The Carrier Sense is stuck on the indicted port. The transceiver is being reset. RMON_PPMGR_PORT_XCVRCS 367 Unused RMON_PPMGR_PORT_XCVRCS1 368 Port <port-num> Xcvr Error, Resetting Xcvr... There is a transceiver error on the specified port. The transceiver is being reset. RMON_PPMGR_PORT_XCVRCS2 369 Unused RMON_PPMGR_PORT_XCVRERR 370 Resetting port <port-num>: remote fault, ieee, parallel detect The port is being reset because of a remote fault. RMON_PPMGR_PORT_XCVRERR2 371 Port <port-num> self test failure The self-test failed on the port. The port is not usable. RMON_CHASSIS_PORT_FAIL 372 Invalid transceiver installed in Port <port-num> There is an invalid transceiver in the specified port. RMON_CHASSIS_INVALID_XCEIVER 373 Boot ROM self test failure The Boot ROM self-test failed. RMON_CHASSIS_ROM_ST_FAIL 374 Lost Communication with Slot <slot-num> The chassis manager failed to receive a heartbeat response. RMON_CHASSIS_HEARTBEAT_FAILURE 375 Slot <slot-num> Downloading The chassis manager has begun downloading a new card. RMON_CHASSIS_DOWNLOADING 376 Slot <slot-num> Download Complete The chassis manager finished downloading a new card. RMON_CHASSIS_DOWNLOAD_COMPLETE 377 Slot <slot-num> Download Failed The chassis manager failed to download a new card. RMON_CHASSIS_DOWNLOAD_FAILED 378 Port <port-num>: Slot <slot-num> Interrupt <value> The interrupt value on the specified port is displayed. RMON_PPMGR_ASIC_STATUS 21

379 Port <port-num> in half duplex, flow control is auto-disabled 380 Port <port-num> - disabled due to speed mismatch. See help. 381 Initialization failed for protocol priority 382 Initialization failed for Vlan priority 383 Initialization failed for device priority Flow control is automatically disabled on the port because it is in half-duplex mode. RMON_PPMGR_FC_AUTODISABLE There is a speed mismatch on the specified port. Refer to the help rmation for more details. RMON_FF_BADCFG_AUTODISABLE The initialization failed for the priority protocol (CoS). RMON_COS_PROTO_INIT_ERROR The initialization failed for the vlan priority (CoS). RMON_COS_VLAN_INIT_ERROR The initialization failed for the device priority. RMON_COS_ADDR_INIT_ERROR 384 Initialization failed for TOS mode The initialization failed for the Type of Service mode. RMON_COS_TOS_INIT_ERROR 385 Initialization failed for DiffServ priority 386 Initialization failed for port priority 387 Passive Dynamic LACP enabled on all ports. The initialization failed for the DiffServ priority (CoS). RMON_COS_DIFFSERV_INIT_ERROR The initialization failed for the port priority (CoS). RMON_COS_PORT_INIT_ERROR Passive and dynamic LACP is enabled on all ports. RMON_LACP_PASSIVE_DYNAMIC_BOOT 388 No listing. 389 Dynamic LACP trunk <trunknum> is now online. 390 Dynamic LACP trunk <trunknum> is now off-line. The trunk is now online. RMON_LACP_DYNAMIC_TRUNK_ON_LINE The trunk is now off-line. RMON_LACP_DYNAMIC_TRUNK_OFF_LINE 391 No Trunks available No trunks are available. RMON_LACP_NO_TRUNKS_AVAILABLE 392 Port <port-num> is in Half Duplex - set to Individual 393 Port <port-num> is blocked - error condition 394 Port <port-num> is blocked - negotiation 395 Port <port-num> is blocked - renegotiation The trunk port is configured to transmit in half-duplex mode and set to Individual. RMON_LACP_PORT_IS_HALF_DUPLEX An error condition occurred on the specified trunk port. The port is blocked. RMON_LACP_ERROR_CONDITION_BLOCK The LACP trunk port is blocked while it is negotiating with a peer. RMON_LACP_NEGOTIATION_BLOCK The LACP trunk port is blocked while it is re-negotiating with a peer. RMON_LACP_RE_NEGOTIATION_BLOCK 22

396 Port <port-num> is moved from trunk <trunk-num> to <trunknum> 397 LACP port <port-num> is moved to trunk <trunk-num> 398 Port <port-num> is removed from trunk <trunk-num>. The LACP trunk port has been moved to another trunk group. RMON_LACP_PORT_MOVED_FROM_DYNX_TO_DYNY The LACP trunk port has been moved to the specified trunk group. RMON_LACP_PORT_MOVED_TO_DYNX The LACP port has been removed from the trunk group. RMON_LACP_PORT_REMOVED_FROM_DYNX 399 Stack Protocol enabled The stacking protocol is enabled. RMON_STACK_ENABLE 400 Stack Protocol disabled The stacking protocol is disabled. RMON_STACK_DISABLE 401 debug Unused RMON_STACK_GENERIC 402 Stack member <mac-addr> lost Communication with the specified switch has been lost. The address is unreachable. RMON_FF_UNREACHABLE_STACK_MEMBER 403 DHCP relay agent feature enabled 404 DCHP relay agent feature disabled 405 Port <port-num> xcvr hot-swap insert Port <port-num> xcvr inserted. Need reboot. Port <port-num> xcvr inserted. Remove/install module. 406 Port <port-num> xcvr hot-swap remove Port <port-num> xcvr removed 407 Port <port-num> new xcvr invalid type and/or speed 408 Port <port-num> xcvr type change. Check switch config 409 Port <port-num> GigT xcvr invalid mode change. Need reboot. The DHCP relay agent feature has been enabled. RMON_DHCPR_ENABLED The DHCP relay agent feature has been disabled. RMON_DHCPR_DISABLED There has been a transceiver change. Reboot the switch. RMON_PPMGR_XCVR_HOTSWAP_INSERT A transceiver has been removed. RMON_PPMGR_XCVR_HOTSWAP_REMOVE The new transceiver is an invalid type and/or runs at an incorrect speed. RMON_PPMGR_XCVR_HOTSWAP_INVALID The transceiver has been changed in the specified port. Check the switch configuration. RMON_PPMGR_XCVR_HOTSWAP_TYPECHG The gigabit-t transceiver on the specified port had an invalid mode change. The switch needs to be rebooted. RMON_PPMGR_XCVR_HOTSWAP_GIGTMDCHG 410 Client enabled debug The SNTP client was enabled. RMON_SNTP_ENABLED 411 Timed out on server <ip-addr> The specified server timed out. RMON_SNTP_TIMEOUT_SERVER 23

412 Timed out waiting for broadcast The device timed out while waiting for an SNTP broadcast. RMON_SNTP_TIMEDOUT_BROADCAST 413 Updated time by <num> seconds The time was updated by the specified number of seconds. RMON_SNTP_UPDATED_TIME 414 All configured servers failed All the configured SNTP servers have failed. RMON_SNTP_ALL_SERVERS_FAILED 415 Preferred broadcast server did not send broadcast in time 416 Found new preferred broadcast server at <ip-addr> The preferred SNTP broadcast server did not send the SNTP broadcast before it timed out. RMON_SNTP_PREF_BROADCAST_FAILED A new preferred SNTP broadcast server was found at the specified IP address. RMON_SNTP_NEW_PREF_BROADCAST 417 CDP enabled CDP has been enabled. RMON_CDP_ENABLED 418 CDP disabled CDP has been disabled. RMON_CDP_DISABLED 419 Invalid user name/password on <session-type> session Authentication failed because the user exceeded the maximum number of supported authentication attempts in one of the following types of session: web user interface, console, Telnet, port-access, SSH, web-authentication, or MAC-authentication. RMON_AUTH_FAILED 420 Can t reach TACACS+ server Unable to establish communication with a TACACS+ server. RMON_TACACS_NO_SERVER 421 Can t reach RADIUS server <server-name> A designated RADIUS server is not responding to an authentication request. Try pinging the server to determine whether it is accessible to the switch. If the server is accessible, then verify that the switch is using the correct encryption key and that the server is correctly configured to receive an authentication request from the switch. RMON_RADIUS_NO_SERVER 422 Slot <slot-num> Ready The slave card in the specified slot number is ready. RMON_CHASSIS_SLOT_READY 423 Unable to Download to Slot <slotnum>. Please remove card. 424 Module in Slot <slot-num> not Supported or may be Faulty. 425 Backplane link to slot <slot-num> failed self-test A slave card has exceeded the number of download retries. Remove the card from the slot. RMON_CHASSIS_DOWNLOAD_RETRIES The module in the specified slot is not supported or is not operating correctly. The Master has not received a download request from a slave card. RMON_CHASSIS_NO_DWNLD_REQ_RECVD The self-test on the backplane link to the specified slot failed. The slot is not usable. RMON_CHASSIS_BACKPLANE_SLOT_FAIL 426 Invalid VLAN <vlan-id> supplied for port <port-num> An invalid VLAN ID was provided for the specified port. 802.1X authorization failed. RMON_AAA8021X_AUTH_BAD_VLAN 24

427 <num-timeouts> auth-timeouts for the last <num-secs> sec 428 <num-failures> auth-failures for the last <num-secs> sec 429 Port <port-num>, re-auth timeout <time-period> too short The specified number of authorization timeouts have occurred during this time period. RMON_AAA8021X AUTH_GENSTAT_TO The specified number of authorization failures has occurred during the time period. RMON_AAA8021X_AUTH_GENSTAT_FL The reauthorization timeout period for the specified port is too short. RMON_AAA8021X_AUTH_INVALID_RTO 430 Supp port <port-num>: <msg-txt> The switch has received an 802.1x supplicant message on the specified port. The message type is Notification. RMON_AAA8021X_SUPP_MSG_RCVD 431 Authentication failed for supp port <port-num> 432 VID supplied for trunked port <port-num> Authentication failed on the specified port. RMON_8021X_SUPP_AUTHFAILED A VLAN ID has been supplied for the specified trunk port. RMON_AAA8021X_AUTH_TRUNK_VID 433 SSH server enabled The Secure Shell (SSH) server has been enabled. RMON_SSH_ENABLED 434 SSH server disabled The SSH server has been disabled. RMON_SSH_DISABLED 435 Port <port-num> is Blocked by <subsystem-type> The specified port is blocked by one of the following subsystems: STP, PAGP, MESHING, LACP, AAA, or UDLD. RMON_PMGR_PORT_BLOCK 436 Route entry creation(s) failed The route entry was not created. RMON_NETINET_RT_MALLOC_FAILED 437 ARP entry creation(s) failed The arp entry was not created. RMON_NETINET_ARP_MALLOC_FAILED 438 Mask for route allocation(s) failed The mask for route allocation was not created. RMON_NETINET_MASK_ALLOC_FAILED 439 Router LSA database overflow The router s LSA database has overflowed. RMON_OSPF_RTR_LSA_OFLOW 440 Network LSA database overflow The network LSA database has overflowed. RMON_OSPF_NET_LSA_OFLOW 441 Summary Net LSA database overflow 442 Summary ASBR LSR database overflow 443 AS External LSA database overflow 444 Port <port-num>: received packet on non-mesh port The summary net LSA database has overflowed. RMON_OSPF_SUM_LSA_OFLOW The summary ASBR LSR database has overflowed. RMON_OSPF_ASB_LSA_OFLOW The AS external LSA database has overflowed. RMON_OSPF_ASE_LSA_OFLOW The specified non-mesh port received a packet. RMON_LDBAL_NON_MESH_PORT_RCV_MESH_PKT 25

445 Cannot accept switch 1600/24xx/ 4000/8000 into mesh 446 Max hop count exceeded. Check your mesh topology. The 1600, 4000, 8000 and Series 2400 switches cannot be part of a mesh. RMON_LDBAL_DUP_MAC_MULTI_VLAN_ERROR The maximum hop count was exceeded. Check the topology of the mesh. RMON_LDBAL_MAX_HOP_EXCEEDED 447 Port <port-num> - initialized The port was initialized for load balancing. RMON_LDBAL_PORT_INITIALIZED 448 Port <port-num> disabled due to faulty link partner The port was disabled due to an invalid peer in the link. RMON_PPMGR_FAULTY_PARTNER 449 Port <port-num> RJ-45 is enabled The RJ-45 port is enabled. RMON_PPMGR_DUALPHY_RJ45_ENABLED 450 Port <port-num> mini_gbic is enabled 451 Unsupported protocol. Upgrade <mac-addr> firmware 452 Inconsistent <mac-addr> config with <config-type> - <configtype> The mini-gbic port is enabled. RMON_PPMGR_DUALPHY_FIBER_ENABLED The protocol is not supported. You must upgrade the firmware. RMON_LDBAL_PROTOCOL_NOT_SUPPORTED There is a mismatch in configuration type across the mesh with the switch at the specified MAC address. According to mesh rules, the configuration mismatch is not allowed. Valid configuration types are: STP, RSTP, MSTP, GVRP, IGMP, CDP, 802.1x, Jumbo, LLDP, VLAN, or OS version. RMON_LDBAL_ATTRIBUTE_MISMATCH An invalid meshing packet was received from the specified MAC address range. RMON_LDBAL_RECV_DIFF_MODE_PKT 453 Received invalid meshing mode pkt from <mac-addr> - <macaddr> 454-462 Reserved RMON_LDBAL_RESERVED_1-9 463 SSL HTTP server enabled on TCP port <port-num> A Secure Socket Layer (SSL) connection is enabled on the specified TCP port. RMON_SSL_SERVER_UP 464 SSL HTTP server disabled You are unable to connect with SSL because the SSL server is disabled. RMON_SSL_SERVER_DOWN 465 SSL HTTP startup failed no RSA key present 466 SSL HTTP startup failed: no certificate present 467 SSL HTTP startup failed: cert/ RSA key pair mismatch The SSL HTTP failed to start because you have not generated a certificate key. For rmation on how to generate a server certificate before enabling SSL, refer to the Configuring Secure Socket Layer (SSL) chapter in the Access Security Guide. RMON_SSL_KEY_MISSING The SSL HTTP failed to start because the certificate was not present. RMON_SSL_CERT_MISSING SSL HTTP did not start because there was a certificate/rsa key pair mismatch. RMON_SSL_CERT_KEY_MISMATCH 26

468-477 Reserved RMON_SSL_RESERVED_1-10 478 Unable to Malloc a buf of size <buffer-size> in <mod-num> 479 Duplicate IP address <ip-addr> detected 480 IP address <ip-addr> in use, XRRP cannot take over 481 Unable to alloc a msg buffer from routine <routine-name> 482 Cannot add MCAST address <mac-addr> 483 No IP address configured for VR on rtr <router-id>, vid <vlan-id> 484 Unexpected state/event state = <state-name>, event <eventname> 485 Failed to alloc a pkt buf for an XRRP pkt from <src-ip-addr> 486 Pkt rcvd that was too short, len = <length>, min = <minimumlength> 487 Pkt rcvd with a checksum error from rtr <router-addr> 488 Pkt rcvd with an illegal domain number of <domain-num> 489 Pkt rcvd with an illegal rtr number of <router-id> in domain <domain-name> 490 Pkt rcvd with dup number of <router-id> in domain <domainname> 491 Rcvd its own pkt back (network loop) on rtr <router-id> standard standard standard standard standard standard XRRP could not allocate memory of the specified buffer size in the source code module. RMON_XRRP_MALLOC_ERROR The specified IP address is a duplicate. RMON_XRRP_DUPLICATE_IP_ADDR XRRP cannot take over because the specified IP address is being used. RMON_XRRP_SECONDARY_IN_USE Unable to reserve memory for a message buffer from the specified routine. RMON_XRRP_NO_MSG_BUF The specified multicast address cannot be added as a destination. RMON_XRRP_CANNOT_ADD_MCAST_DEST An IP address was not configured for the virtual router on the specified router and VLAN ID. RMON_XRRP_NO_IP_ADDR_ON_VR An unexpected state or event occurred. RMON_XRRP_UNEXPECTED_STATE_ERROR A packet buffer was not allocated for an XRRP packet from the specified source IP address. RMON_XRRP_PKT_ALLOC_FAILURE The packet received was less than the minimum allowable length indicated. RMON_XRRP_PKT_TOO_SHORT A packet with a checksum error was received from the specified router. RMON_XRRP_CHECKSUM_ERROR A packet was received with an illegal domain number. RMON_XRRP_ILLEGAL_DOMAIN A packet with an illegal router number was received in the specified domain. RMON_XRRP_ILLEGAL_ROUTER A packet was received with a duplicate router number in the specified domain. RMON_XRRP_DUPLICATE_ROUTER The router received its own packet because there is a network loop. RMON_XRRP_LOOP_BACK_PKT 27

492 Rcvd pkt with version number <ver-num>, expected <ver-num> A packet was received with an unexpected version number. RMON_XRRP_VER_MISMATCH 493 Rcvd pkt from rtr <router-id>, owner <owner>, vid <vlan-id>, no such VR 494 Rcvd pkt from rtr <router-addr>, with unknown pkt type <pkttype> 495 Rcvd pkt from rtr <router-addr>, with ver/type = <type>, expected <type> A packet from the specified source router and VLAN was received with an unknown virtual router ID. RMON_XRRP_NO_VR_FOR_XRRP_PKT A packet of an unknown packet type was received from the specified router. RMON_XRRP_RC_UNKNOWN_XRRP_PKT_TYPE A packet of an unexpected type was received from the specified router. RMON_XRRP_VRRP_VERSION_UNKNOWN 496 No local IP addr <ip-addr> from rtr <router-addr> on vid <vlan-id> There is no local IP address on the router and VLAN ID. RMON_XRRP_VRRP_IP_ADDR_MISMATCH 497 Rtr <router-addr> has <num> IP addrs on vid <vlan-id>, local rtr has <num> 498 Rcvd pkt from rtr <router-id> on vid <vlan-id> with the wrong password 499 Rcvd pkt from rtr <router-id> on vid <vlan-id> with a mismatched ad int 500 No VR instances for the local rtr <router-id> 501 No VR instances for the remote rtr <router-id> 502 Rtr <router-id> has taken <ipaddr> IP address control 503 Rtr <router-id> has relinquished <ip-addr> IP address control 504 Remote rtr <router-id> domain <domain-name> is misconfigured 505 PKT received on VID <vlan-id> sent on VID <vlan-id> 506 (Local or remote) rtr <router-id> configuration corrected 507 Local rtr missing secondary VR on Vid <vlan-id> standard standard A remote router had the specified number of IP addresses on the VLAN ID, which does not agree with the local router. RMON_XRRP_VRRP_IP_COUNT_MISMATCH A packet with an incorrect password was received from the router on the VLAN ID. RMON_XRRP_VRRP_AUTH_FAILURE A packet was received from the router with a mismatched add integer RMON_XRRP_VRRP_ADD_INT_MISMATCH There are no virtual router instances of the local router. RMON_XRRP_NO_PRIMARY_VR_SETUP There are no virtual router instances of the remote router. RMON_XRRP_NO_SECONDARY_VR_SETUP The router has acquired control of the IP address. RMON_XRRP_TAKEN_CONTROL The router has relinquished control of the IP address. RMON_XRRP_LOST_CONTROL Invalid configuration settings have been detected on the remote router. RMON_XRRP_REMOTE_MISCONFIG A packet with an received on the VLAN ID was transmitted on another VLAN ID. RMON_XRRP_WRONG_VID Invalid configuration settings have been corrected on the router. RMON_XRRP_MISCONFIG_CORRECTED On the specified VLAN, the local router cannot connect to the backup router. RMON_XRRP_SECONDARY_VR_MISSING 28

508 Peer router has permanent control. 509 User has triggered failback to router <router-id>. 510 Infinite failback has been enabled on this router. 511 Infinite failback has been disabled on this router The peer router has taken master control of the virtual router. RMON_XRRP_PEER_HAS_PERMANENT_CTRL A VR failback has been initiated on the specified router. RMON_XRRP_USER_TRIGGERED_FAILBACK A failback has been enabled so that the local router recovers master status. RMON_XRRP_INF_FAILBACK_ON A failback has been disabled on the local router so that the peer router recovers master status. RMON_XRRP_INF_FAILBACK_OFF 512-513 Reserved RMON_XRRP_RESERVED_8-9 514 Unable to learn HW IP host routes, table FULL 515 IP host route table is nearing max capacity 516 Unable to learn HW IP multicast group, table FULL 517 Unable to learn HW IP multicast address, table FULL The IP route table is full. New entries for routing paths to IP destinations cannot be added. RMON_IPADDRMGR_HWTBL_FULL The IP route table is almost full. Only a few new entries of routing paths to IP destinations are supported. RMON_IPADDRMGR_TBL_SIZE_WARN The IP route table is full. New entries to distribute multicast traffic for a group address are not supported. RMON_IPADDRMGR_MRT_FULL The IP route table is full. New entries to transmit multicast traffic for an IP address are not supported. RMON_IPADDRMGR_MCAST_FLOW_FULL 518 <> The switch is reporting that the node at an IP address <address> cannot be resolved by ARP, but the traffic is continually being sent to the unresponsive node at a rate of <num-packets/sec>. RMON_IPADDRMG_WARN 519 Unknown msg opcode: <msg-txt> 520 Module <slot-num>: unknown msg opcode: <msg-txt> Message identifiers are displayed for use in troubleshooting and debugging. RMON_IPADDRMGR_BAD_OPCODE Message identifiers are displayed for use in troubleshooting and debugging. RMON_IPADDRMGR_FIX_SLOT_BAD_OPCODE 521 Unused RMON_KMS_RXTX_TIME_NOT_SET 522 No send key found No active key chain entry has been found to transmit packets. RMON_KMS_TX_NO_KEY 523 No send key, used the first to be activated 524 No send key, used the last activated No active key chain entry has been found to transmit packets. The first send key to be activated will be used. RMON_KMS_TX_KEY_FIRST No active key chain entry has been found to transmit packets. The last send key to be activated was used. RMON_KMS_TX_KEY_LAST 29

525 Multiple send keys for current daytime Multiple key chain entries are active to transmit packets during this time period. RMON_KMS_TX_KEY_OVERLA 526 Bad reference Key request does not correspond to configured key chain entries. RMON_KMS_GEN_ERROR 527-531 Reserved RMON_KMS_RESERVED_0-4 532 Port <port-num> Unsupported transceiver. (SelfTest Err) Check: www.hp.com/rnd/ device_help/2_rm for more. 533 Port <port-num> Not a ProCurve transceiver. Please go to: \ www.hp.com/rnd/device_help/ 2_rm for more. 534 Port <port-num> transceiver type not supported in this software\ version. Please check for an updated release. 535 Port <port-num> This switch only supports revision B and above transceivers. 536 Port <port-num> transceiver type not supported in this port. 537 Syncing [primary secondary] OS to standby [started completed] 538 Standby <boot image default boot> updated, rebooting standby 539 Initial active to standby sync <started completed> 540 Redundant Standby Management Module syncing is <module>. Configuration changes are <changes>. The transceiver installed in the port failed self-test and is not supported. RMON_XCVR_CTRFT0 The transceiver installed in the port is not a ProCurve device. RMON_XCVR_CTRFT1 The transceiver type installed in the port is not supported in this software release. RMON_XCVR_CTRFT2 The transceiver installed in the port is not supported. The switch supports only revision B (or later) transceiver types. RMON_XCVR_CTRFT3 The transceiver type installed in the port is not supported in this port. RMON_XCVR_CTRFT4 This message is logged when the OS begins synchronizing to the standby module. It displays the status of the synchronization. RMON_SYSTEM_OS_SYNC This message is logged when the standby s management module boot image is overwritten, requiring a reboot. RMON_SYSTEM_STANDBY_REBOOT Indicates the beginning or end of the initial synchronization of the active management module s flash image to the standby management module. RMON_SYSTEM_INITIAL_SYNC The redundant management module is syncing. Configuration changes are temporarily disabled. RMON_SYSTEM_INITIAL_SYNC_BLOCK_CONFIG 541 Out of storage space on standby The standby switch is out of storage space. RMON_SYSTEM_MODULE_DISK_FULL 30

542 system: Runtime Error Skipped: <err-msg> Skips the runtime error messages that are not being used. RMON_SYSTEM_ERR_SKIP 543-548 Reserved RMON_XXX_UNUSED5-16 549 Insufficient power supplies to power Slot <slot-num> The slot is not receiving sufficient power. RMON_CHASSIS_POWER_INSUFFIENT 550 <slot-num> Module Present A module is installed in the specified slot. The chassis manager sees the inserted module. RMON_CHASSIS_MODULE_PRESENT 551 <slot-num> Module failed self test 552 Module insertion detected: Reboot required 553 Over-temperature detected. Failures: <num> 555 RPS state: <slot-num>. Failures: <num> 556 Power Supply is <slot-num>. Failures: <num> 557 Temperature back to normal. Failures: <num> The module installed in the specified slot failed its self-test. RMON_CHASSIS_MODULE_ST_FAIL A new module has been installed and you must now reboot the switch to activate the module. RMON_CHASSIS_MODULE_HS_DETECTED An over-temperature condition in the switch has been detected or the RPS is failing. The number of switch failures is displayed RMON_CHASSIS_OVERTEMP A failure in the redundant power supply in the specified slot has been detected. The number of power failures is displayed. RMON_CHASSIS_RPS_STATUS A failure in the single power supply in the specified slot has been detected. The number of power failures is displayed. RMON_CHASSIS_SINGLE_POWER_STATUS The over-temperature condition has passed and the chassis temperature is normal. The number of power failures is displayed. RMON_CHASSIS_TEMP_NORMAL 558 NMI Error: <msg-txt> The message identifies the subsystem that has triggered the NMI error. NMI non-maskable interrupt errors occur when a subsystem requires use of the CPU for an unusually long time. RMON_CHASSIS_NMI_ERR_LOG 559 <msg-txt> Used for debugging. Displays a log of an NMI event. RMON_CHASSIS_BACKPLANE_FAILED 560 Port <port-num> PD Detected. The switch has detected a Power over Ethernet (PoE) device connected to the specified port. RMON_POEMGR_PD_DETECTED 561 Port <port-num> Applying Power to PD. 562 Port <port-num> PD Over Current indication. A PoE device is connected to the port and receiving power. RMON_POEMGR_PD_APPLY_POWER The powered device (PD) connected to the port has requested more than 15.4 watts of power. This may indicate a short-circuit or other problem in the PD. RMON_POEMGR_PD_OVERCURRENT 31

563 Port <port-num> PD MPS Absent indication. 564 Port <port-num> PD Invalid Signature indication. The switch no longer detects a powered device on the port. The device may have been disconnected, powered down, or stopped functioning. RMON_POEMGR_PD_MPS_ABSENT The switch has detected a non-802.3af-compliant device on the port. This message appears for all non-802.3af devices connected to the port, such as other switches and PC-NICs. RMON_POEMGR_PD_INVALID_SIG 565 Port <port-num> PD Removed. The powered device connected to the port has been removed. RMON_POEMGR_PD_REMOVED 566 Port <port-num> PD Denied power due to insufficient power allocation. 567 Port <port-num> PD Other Fault indication. 568 <slot-num> Ext Power Supply connected, supplying <num> W of <num> W max. 569 <slot-num> Ext Power Supply: <eps-type> Failures: <num>. 570 <slot-num> Ext Power Supply connected but not responding. There is insufficient power available to power the PD on the port and the port does not have sufficient PoE priority to take power from another active PoE port. RMON_POEMGR_PD_DENIED_POWER There is a problem with the PD connected to the port. RMON_POEMGR_PD_OTHER_FAULT The external power supply installed in the slot is providing the displayed amount of total power required. RMON_POEMGR_EPS_CONNECTED A fault condition has been detected on the external power supply installed in the slot. The number of power failures is displayed. Potential Cause and Resolution: This may have been caused by a switch that was currently drawing PoE power (50v) requiring the additional power supplied by the External Power Supply. When the switch internal power supply failed, this caused an overcurrent situation and the External Power Supply may now need to be reset (unplugged, plugged back in) to bring it back online. RMON_POEMGR_EPS_ERROR The external power supply installed in the slot is installed but not responding to communication attempts. RMON_POEMGR_EPS_COMM_FAULT 571 RMON_POEMGR_USAGE_THRESH_EXCEEDED 572 Slot <slot-num> POE usage has exceeded threshold of <1-99>%. 573 <slot-num> Ext Power Supply disconnected. POE usage in the slot has exceeded the configured threshold for the module, as set by the power threshold or power slot <slotnum> threshold command. (The switch also generates an SNMP trap for this event.) RMON_POEMGR_SLOT_USAGE_THRESH_EXCEEDED The external power supply installed in the specified slot is no longer connected. RMON_POEMGR_EPS_DISCONNECTED 32

574 Slot <slot-num> POE usage is below configured threshold of <1-99>% 575 <slot-num> EPS not supported by switch code. Please update. 576 50V Power Supply is faulted. Failures: x 50V Power Supply is OK. Failures: x 577 Ext Power Supply: <slot-num> Failures: <num>. 578 <slot-num> Unrecoverable fault on PoE controller <controller-id>. 579 Slot <slot-num> Software update started on PoE controller <controller-id> and Slot <slot-num> Software update completed on PoE controller <controller-id> POE usage on the specified module has a configured threshold of <1-99>%, which has decreased below the threshold value set by the power threshold command. This message occurs if, after the last reboot, the PoE demand on the module exceeded the power threshold and then later dropped below the threshold value. RMON_POEMGR_SLOT_USAGE_UNDER_THRESH The external power supply installed in the slot is not supported by the current software release. RMON_POEMGR_EPS_NOT_SUPPORTED Internal power supply has faulted. Internal power supply is now operational. RMON_POEMGR_INTERNAL_50V_FAULT The power supply installed in the slot has failed. There is a danger of possible damage to the chassis. The number of power failures is displayed. RMON_POEMGR_EPS_FATAL_ERROR An error condition has been detected on the PoE controller on the module in the slot. RMON_POEMGR_CONTROLLER_FAULT A module needs to have its PoE firmware updated and the PoE controller software begins the update process. On Series 5400zl switches, the <controller-id> value is always 1 A module has its PoE firmware updated and the software has finished this process. RMON_POEMGR_FIRMWARE_UPDATE 580 Reserved RMON_POEMGR_RESERVED6 581 Invalid VLAN <vlan-id> supplied for port <port-num> 582 <num> auth-timeouts for the last <num> secs. 583 <num> auth-failures for the last <num> secs. 584 Port <port-num>, re-auth timeout <num> too short. During web or MAC authentication, an invalid port assignment has been detected for the VLAN ID. RMON_WEBMAC_AUTH_BAD_VLAN During web or MAC authentication, no server response has been received and the authentication request has timed out for the specified number of times during this time period. RMON_WEBMAC_AUTH_GENSTAT_TO The specified number of failures have occurred for web or MAC authentication requests during this time period. RMON_WEBMAC_AUTH_GENSTAT_FL The configured timeout period (in seconds) for performing a reauthentication request on the port is too small. RMON_WEBMAC_AUTH_INVALID_RTO 33

585 VID supplied for trunked port <port-num> 586 VID <vlan-id> supplied for port <port-num> with VID <vlan-id> During web or MAC authentication, a VLAN ID has been returned for the specified trunk port. RMON_WEBMAC_AUTH_TRUNK_VID During web or MAC authentication, a different VLAN ID is returned for this port instead of the specified VLAN ID. RMON_WEBMAC_AUTH_DOUBLE_VID 587 EWA Server down <ip-address> The indicated server is down. RMON_WEBMAC_AUTH_EWA_SERVER_DOWN 588-591 Reserved RMON_WEBMAC_UNUSED_0-4 592 <mod-num>: Move <mac-addr> to port <port-num> denied 593 <mod-num>: Ceasing movedenied logs for <num> 594 <mod-num>: <mac-addr> detected on port <port-num> 595 <mod-num>: Ceasing lock-out logs for <num> The movement of a locked-down MAC address was attempted by a suspicious packet received from the specified module. The station using the locked MAC address could have attempted to move the address to a different port, or possibly a malicious station attempted to masquerade as the owner of the locked address. RMON_MACLOCK_MOVE More than one static address move was attempted from the specified module. To avoid filling the log file with repeated attempts, static address move attempts will not be logged for the specified time period (in seconds). RMON_MACLOCK_MOVE_SUSP A locked out MAC address attempted to transmit a packet into the network from the specified module. This event was recognized by the reception of a packet on the specified port with a source address matching the locked-out address. RMON_MACLOCKOUT More than one packet was received on the module from a lockedout source address. To avoid filling the log file with repeated events, future transmission attempts will not be logged for the specified time period (in seconds). RMON_MACLOCKOUT_SUSP 596-599 Reserved RMON_MACLOCK_RESERVED1-4 600 Port(s) <port-num> have multiple voice vlan configurations More than one voice VLAN is configured on the specified port(s). RMON_VOICE_VLAN_MISCONFIG 601 Unused RMON_JUMBO_VLAN_MISCONFIG 602 Mgmt vlan could not be configured on vlan <vlan-id> 603 Cannot apply the Appletalk Arp protocol to protocol vlan <vid> A management VLAN is not supported on the specified VLAN ID. RMON_MGMT_VLAN_FAIL Cannot apply the Appletalk ARP protocol to protocol vlan <vid> due to inadequate resources on some ports. RMON_APPLETALK_ARP_VLAN 34

604 Unable to alloc a buf of size <bytes> for <data-flow> 605 Unable to alloc a msg buffer for <msg-text> 606 Unexpected state/event <statename>/<event-name> in <statemachine> statemach 607 Failed to alloc a PIM <data-type> pkt 608 Send error (<failure-type>) on <pkt-type> pkt on VID <vlan-id> standard Multicast routing is unable to acquire memory for a flow. Router memory is oversubscribed. Reduce the number of VLANs or the number of features in use. Remedies include one or more of the following: Reduce the number of configured VLANs by moving some VLANs to another router. Free up system resources by disabling another feature, such as one of the spanning-tree protocols or either the RIP or the OSPF routing protocol. (Unless you are using static routes, you will need to retain a minimum of one unicast routing protocol.) Another option that may help is to reduce the number of configured QoS filters. Move some hosts that create multicast demand to another router. RMON_PIM_MALLOC_ERROR Multicast routing is unable to acquire memory for a flow. Router memory is oversubscribed. Reduce the number of VLANs or the number of features in use. Remedies include one or more of the following: Reduce the number of configured VLANs by moving some VLANs to another router. Free up system resources by disabling another feature, such as one of the spanning-tree protocols or either the RIP or the OSPF routing protocol. (Unless you are using static routes, you will need to retain a minimum of one unicast routing protocol.) Another option that may help is to reduce the number of configured QoS filters. Move some hosts that create multicast demand to another router. RMON_PIM_NO_MSG_BUF PIM received an event type in a state that was not expected. RMON_PIM_UNEXPECTED_STATE_ERROR The router was unable to allocate memory for a PIM control packet. Router memory is oversubscribed. Reduce the number of VLANs or increase the hello delay and/or the override interval to reduce the number of simultaneous packet transmissions. Note that if the number of flows exceeds 1022, the excess flows are routed in software, which reduces the number of packet transmissions. In this case, reducing the number of flows by moving some clients to other routers can help. RMON_PIM_PKT_FALLOC_FAILURE Indicates a send error on a packet. This can occur if a VLAN went down right after the packet was sent. The message indicates the failure type, the packet type, and the VLAN ID on which the packet was sent. RMON_PIM_PKT_SEND_FAILURE 35

609 Pkt dropped from <ip-addr>, (<cause>), vid <vlan-id> 610 Pkt rcvd with a cksum error from <ip-addr> 611 Rcvd pkt ver# <ver-num>, from <ip-addr>, expected <ver-num> 612 Rcvd pkt from rtr <ip-addr>, unkwn pkt type <value> 613 MCAST MAC add for <macaddr> failed 614 MCAST flow <mcast-addr> <srcip-addr> not rteing (rsc low) 615 No IP address configured on VID <vlan-id> 616 Multicast Hardware Failed to initialize A PIM packet from the specified IP address was dropped due to one of the following causes: No PIM interface on the VLAN Bad packet length Bad IP header length Bad IP total length RMON_PIM_PKT_DROPPED A packet having a checksum error was received from the specified IP address. Check the cabling and ports on the local and the remote routers. RMON_PIM_PKT_CKSUM_ERR The versions of PIM-DM on the sending and receiving routers do not match. Differing versions will typically be compatible, but features not supported in both versions will not be available. RMON_PIM_PKT_VER_MISMATCH A packet received from the router at the specified IP address is an unknown PIM packet type. (The <value> variable is the numeric value received in the packet.) RMON_PIM_PKT_TYPE_UNKNOWN Indicates a hardware problem. Check the cabling and router ports. RMON_PIM_CANNOT_JOIN_MCAST_DEST The indicated multicast flow is not routing. The routing switch is low on memory resources as a result of too many flows for the number of configured VLANs. Remedies include one or more of the following: Reduce the number of configured VLANs by moving some VLANs to another router. Free up system resources by disabling another feature, such as one of the spanning-tree protocols or either the RIP or the OSPF routing protocol. (Unless you are using static routes, you will need to retain a minimum of one unicast routing protocol.) Another option that may help is to reduce the number of configured QoS filters. Move some hosts that create multicast demand to another router. RMON_PIM_LOW_MEM_MCAST_FLOW PIM has detected a VLAN without an IP address. Configure an IP address on the indicated VLAN. RMON_PIM_IP_NOT_CONFIG Indicates a hardware failure that halts hardware processing of PIM traffic. The software will continue to process PIM traffic at a slower rate. Contact your ProCurve customer care center. RMON_PIM_MCAST_ROUTING_HW_FAILURE 36

617 <alpha-str> pkt, src IP <ip-addr> vid <vlan-id> (not a nbr) 618 Rcvd hello from <ip-addr> on vid <vlan-id> 619 Rcvd incorrect hello from <ipaddr> 620 Rcvd unkwn opt <opt-nbr> in <text-str> pkt from <ip-addr> 621 Rcvd unkwn addr fmly <addrtype> in <text-str> pkt from <ipaddr> 622 Rcvd <text-str> pkt with bad len from <ip-addr> 623 Failed flow add: vid <vid> <multicast group ip-addr> <multicast source ip-addr> 624 Failed to initialize <text-str> as a call back routine 625 I/F configured with IP <ip-addr> on vid <vlan-id> 626 I/F removal with IP <ip-addr> on vid <vlan-id> A PIM packet arrived from another router for which no neighbor was found. May indicate a misconfiguration between the sending and receiving router. May also occur if a connected router is disconnected, then reconnected. RMON_PIM_NO_NBR Indicates a misconfiguration where two routers are directly connected with different subnets on the same connected interface. RMON_PIM_MISCONFIG Indicates receipt of a malformed hello packet (the packet does not match the current specification). Ensure that compatible versions of PIM-DM are being used. RMON_PIM_BAD_HELLO The router received a PIM packet carrying an unknown PIM option. The packet may have been generated by a newer version of PIM-DM, or is corrupt. In most cases, normal PIM-DM operation will continue. RMON_PIM_UNKNOWN_OPT The router received a PIM packet with an unrecognized text string encoding. As of February, 2004, the router recognizes IPv4 encoding. RMON_PIM_UNKNOWN_ADDR_FAMILY A peer router may be sending incorrectly formatted PIM packets. RMON_PIM_BAD_LENGTH The switch failed to add a flow programmed into hardware. RMON_PIM_HW_ADD_FAIL Indicates an internal error. Report the incident to your ProCurve customer care center and re-install the router software. RMON_PIM_IP_ADDR_CALLBACK_FAIL Indicates that the interface (VLAN) has been configured with the indicated IP address. At boot-up or when an IP address is changed, the switch generates this message for each PIMconfigured VLAN. RMON_PIM_IP_ADDR_CONFIG Indicates that a PIM interface (VLAN) has been removed from the router as a result of an IP address change or removal. RMON_PIM_IF_REMOVAL 37

627 Unable to allocate <text-str> table 628 Bad <param-name> in <pkttype> pkt from IP <ip-addr> The router was not able to create some tables PIM-DM uses. Indicates that the router is low on memory resources. Remedies include one or more of the following: Reduce the number of configured VLANs by moving some VLANs to another router. Free up system resources by disabling another feature, such as one of the spanning-tree protocols or either the RIP or the OSPF routing protocol. (Unless you are using static routes, you will need to retain a minimum of one unicast routing protocol.) Another option that may help is to reduce the number of configured QoS filters. Move some hosts that create multicast demand to another router. RMON_PIM_TABLE_ALLOC_ERROR The PIM packet was dropped due to a bad parameter in the packet from the specified IP address. RMON_PIM_PKT_BAD_PARM 629 PIM socket error There was an error regarding the PIM socket, either on a sockopt call or a recvfrom call. RMON_PIM_SOCKET_ERROR 630 No RP for group <ip-addr> standard PIM-SM needed an RP for the indicated group address, but none was found. RMON_PIM_NO_RP_FOR_GROUP 631 No route to source/rp <ip-addr> standard PIM was unable to find a route to the specified IP address. RMON_PIM_NO_ROUTE 632 Port <port-num> Duplex Mismatch. Reconfig port to Full Duplex. There is a mismatch in the configured transmission mode between the specified port and a peer. Reconfigure the data transmission setting to Full Duplex. RMON_PPMGR_DMM_SET_FULL_WARN 633 Port <port-num> Duplex Mismatch. Reconfig port to Auto. There is a mismatch in the configured transmission mode between the specified port and a peer. Reconfigure the data transmission setting to Auto (auto-configuration). RMON_PPMGR_DMM_SET_AUTO_WARN 634 Front panel clear button pressed; switch reset. 635 Alternate password used to gain access. A manual reset of the switch is taking place after pressing the Clear button. RMON_FPANEL_RESET_ON_CLEAR A different password was used to access the switch. RMON_FPANEL_ALT_PASS_USED 636 SFTP session from <ip-addr> An SFTP session was started from the specified IP address. RMON_SSH_SFTP_SESS 637 SCP session from <ip-addr> An SCP session was started from the specified IP address. RMON_SSH_SCP_SESS 638 Not enough space available to complete the file transfer The file transfer was aborted due to insufficient memory. RMON_SSH_FT_NO_MEM 38

639 SCP error: <ip-addr> An error was detected in the SCP session with the device at the specified IP address. RMON_SCP_ERR 640 SFTP error: <ip-addr> An error was detected in the SFTP session with the device at the specified IP address. RMON_SFTP_ERR 641 <session>, session aborted The SSH session was aborted. RMON_SSH_ERR 642 SSH server enabled in IPv4 mode The SSH server is enabled in IPv4 mode. RMON_SSH_IPv4_ENABLED 643 SSH server enabled in IPv6 mode The SSH server is enabled in IPv6 mode. RMON_SSH_IPv6_ENABLED 644 SSH server disabled for IPv4 The SSH server is disabled for IPv4. RMON_SSH_IPv4_DISABLED 645 SSH server disabled for IPv6 The SSH server is disabled for IPv6. RMON_SSH_IPv6_DISABLED 646 New <num-bits>-bits <rsa dsa> SSH host key installed The new SSH host key is installed. RMON_SSH_HOSTKEY_INSTALLED 647 SSH host key zeroized The SSH host key is set to zero. RMON_SSH_HOSTKEY_ZEROIZED 648 <mod-num>: Self-test failed <msg-txt> 649 <mod-num>: base configuration transfer failed 650 <mod-num>: incompatible BIOS version: <msg-txt> 651 <mod-num> diagnostics partition is ready 652 <mod-num>: Maximum clientport VLANs count reached 653 <mod-num>: Maximum system VLANs count reached 654 <mod-num>: Reboot system to complete client-port configuration A self-test failure occurred on the module. RMON_HPESP_SELF_TEST_ERROR The module configuration being performed by the BIOS handshake protocol failed. RMON_HPESP_BIOS_ERROR The BIOS version is not supported by the current switch firmware. RMON_HPESP_INCOMPATIBLE_BIOS The diagnostics partition has been loaded and is ready for user interaction. RMON_HPESP_DIAGNOSTICS The maximum number of security VLAN groups have been configured on the module. RMON_HPESP_MAX_SEC_VLAN The maximum number of VLANs have been configured on the module. RMON_HPESP_MAX_SYS_VLAN Reboot the switch for the security VLAN configuration to take effect. RMON_HPESP_REBOOT 39

655 <mod-num>: Unable to create VLAN. <msg-txt> 656 <mod-num>: VLAN <vlan-id> is created. 657 <mod-num>: Application initialization failed. 658 <mod-num>: Illegal event <event-type> at state <statemachine> 659 <mod-num>: Excessive reboots detected 660 <mod-num> removed before shutdown completed A VLAN configuration on a downlink port has failed. RMON_HPESP_CONFIG_ERROR A VLAN has been successfully configured and a downlink port is assigned as a tag member. RMON_HPESP_VLAN_CREATED Module initialization has failed for one of the following reasons: HPESP version is not supported. VLANs cannot be created. RMON_HPESP_APP_ERROR Used for debugging. RMON_HPESP_ILLEGAL_EVENT The module rebooted many times before establishing communication with the switch. The watchdog timer expired unexpectedly. The module is inoperational. RMON_HPESP_EXCESSIVE_REBOOT The module was removed before the shutdown process was complete. RMON_HPESP_SHUTDOWN_NOT_COMPLETE 661 <mod-num> is safe for removal The module shutdown process is complete and it is safe to remove the module. RMON_HPESP_SAFE_TO_REMOVE 662 <mod-num>: incompatible application version: <msg-txt> 663 <mod-num> member of one or more <vlan-type> An application on the module is not supported by the current switch firmware. RMON_HPESP_INCOMPATIBLE_ESPD Ports on the module are configured as members of both client and non-client VLANs, which may compromise switch security. RMON_HPESP_SECVLAN_WARN 664 <mod-num> is shutting down The module has started the shutdown process. RMON_HPESP_SHUTDOWN_INITIATED 665 <mod-num> is rebooting The module is rebooting. RMON_HPESP_REBOOTING 666 <mod-num> is booting The module is booting. RMON_HPESP_BOOTING 667 <mod-num> is ready The module has booted and is operational. RMON_HPESP_READY 668 <mod-num> HPLAP send TLV error condition <error-type> on connection ID <connection-id> 669 VLAN <vlan-id> caution <msgtxt> A transfer TLV failure has occurred on the module in the specified connection. RMON_HPESP_HPLAP_SENDTLV_ERROR A caution message is displayed concerning VLAN configuration on the module. RMON_HPESP_VLAN_CFG_WARN 40

670 <msg-txt> A error has occurred while updating the software license. RMON_HPESP_LICENSE_FATAL 671 <msg-txt> The license update is successful. RMON_HPESP_LICENSE_INFO 672 <msg-txt> An unexpected event occurred when accessing module application data. RMON_HPESP_APPLDATA_ERROR 673 <mod-num> flash write aborted; write already in progress. 674 <mod-num> shutdown completed 675 Invalid COS attribute value from server for port <port-num> 676 Invalid rate-limit-ingress attribute value from server for port <port-num> 677 Unable to reset COS value for port <port-num> Write-to-flash memory was aborted due to a write operation already in progress. RMON_HPESP_FLASH_WR_IN_PROG Shutdown of the X86 is completed. RMON_HPESP_SHUTDOWN_COMPLETED An invalid Class of Service (CoS) priority assignment for inbound traffic was received on the port from the RADIUS server. RMON_RADIUS_INVALID_COS_ATTRIBUTE An invalid rate-limiting value for inbound traffic was received on the port from the RADIUS server. RMON_RADIUS_INVALID_RATE_LIM_INGRESS_ATTRIBUTE A CoS priority value could not be reset on the port by the RADIUS server. RMON_RADIUS_UNABLE_TO_RESET_COS_VALUE 678 Unable to reset rate-limitingingress value for port <port-num> A rate-limiting value for inbound traffic could not be reset on the port by the RADIUS server. RMON_RADIUS_UNABLE_TO_RESET_RATE_LIMITING_INGRESS_VALUE 679 Unable to set rate-limitingingress value for port <portnum>. Unavailable resources. 680 Unable to set COS value for port <port-num>. Unavailable resources. A rate-limiting value for inbound traffic could not be reset by the RADIUS server due to insufficient resources. RMON_RADIUS_RATE_LIMITING_INGRESS_RESOURCE_UNAVAIL A CoS priority value could not be reset by the RADIUS server due to insufficient resources. RMON_RADIUS_COS_RESOURCE_UNAVAIL 681 Invalid port number. An invalid port number was entered for a RADIUS-based configuration. RMON_RADIUS_INVALID_PORT_NUMBER 682 Radius: RADIUS user config too large. 683 There are no RADIUS servers configured The RADIUS-assigned configuration on the switch has too many configured values. RMON_RADIUS_TOO_LARGE_RESPONSE There are no RADIUS servers configured. RMON_RADIUS_NOT_CONFIGURED 684-685 Reserved RMON_RADIUS_UNUSED_2-4 686 <msg-txt> An upgrade to boot read-only memory (ROM) failed. RMON_BOOTROM_UPGRADE_FAILED 41

687 <msg-txt> An upgrade to boot ROM was successful. RMON_BOOTROM_UPGRADE_PASSED 688 LLDP - enabled The Link-Layer Discovery Protocol (LLDP) is globally enabled. RMON_LLDP_ENABLED 689 LLDP - disabled LLDP is disabled. LLDP traffic will not be received on the switch. RMON_LLDP_DISABLED 690 DHCP relay agent feature enabled 691 DHCP relay agent feature disabled 692 UDP broadcast forwarder feature enabled 693 UDP broadcast forwarder feature disabled 694 Src IP address <ip-addr> high connection rate 695 Src IP address <ip-addr> throttled The DHCP relay agent is enabled on the switch to forward DHCP client packets to configured DHCP servers for each VLAN. RMON_UDPF_DHCP_RELAY_ENABLED The DHCP relay agent has been disabled RMON_UDPF_DHCP_RELAY_DISABLED UDP broadcast forwarding has been globally enabled on the router. Appears in the Event Log and, if configured, in SNMP traps. RMON_UDPF_BCAST_FWD_ENABLED UDP broadcast forwarding has been globally disabled on the router. This action does not prevent you from configuring UDP broadcast forwarding addresses, but does prevent UDP broadcast forwarding operation. Appears in the Event Log and, if configured, in SNMP traps. RMON_UDPF_BCAST_FWD_DISABLED A port with the specified IP address is configured for notify-only and detects a relatively high number of connection-rate attempts from a host. RMON_VIRUSTH_SA_NOTIFY A port with the specified IP address has been throttled after detecting a relatively high number of connection-rate attempts from a host. RMON_VIRUSTH_SA_THROT 696 Src IP address <ip-addr> blocked A port with the specified IP address has been blocked after detecting a relatively high number of connection-rate attempts from a host. RMON_VIRUSTH_SA_BLOCK 697 Unable to add port <port-num> to trunk, CRF is enabled 698 Unable to remove trunk <trunknum>, CRF is enabled 699 ACE parsing error, permit/deny keyword, <ace-index-num>, client <mac-addr>, port <portnum> 700 Unable to add ACL entry <<aceindex-num>, client mac <macaddr>, port <port-num> The port could not be added to a trunk port. A connection-rate filtering (CRF) ACL is enabled on the port. RMON_VIRUSTH_TRUNK_PORT_ERROR The trunk port could not be deleted. A connection-rate filtering (CRF) ACL is enabled on the port. RMON_VIRUSTH_TRUNK_REMV_ERROR An error was detected in the permit/deny keyword in the specified ACE, configured in an ACL on the specified client and port. RMON_IDM_ACE_PARSE_ACTION_ERROR The ACE entry, configured in an ACL on the specified client and port, could not be added to the internal ACL storage. RMON_IDM_ADD_ACL_ENTRY_ERROR 42

701 Could not create ACL entry. client mac <mac-addr>, port <portnum> 702 Could not add ACL, client mac <mac-addr>, port <port-num>, At max per-port ACL quantity. 703 ACE parsing error, IN keyword, <ace-index-num>, client <macaddr>, port <port-num> 704 ACE parsing error, protocol field, <ace-index-num>, client <macaddr>, port <port-num> 705 ACE parsing error, FROM keyword, <ace-index-num>, client <mac-addr>, port <portnum> 706 ACE parsing error, ANY keyword, <ace-index-num>, client <macaddr>, port <port-num> 707 ACE parsing error, TO keyword, <ace-index-num>, client <macaddr>, port <port-num> 708 ACE parsing error, destination IP, <ace-index-num>, client <macaddr>, port <port-num> 709 ACE parsing error, tcp/udp ports, <ace-index-num>, client <macaddr>, port <port-num> 710 Rule limit per ACL exceeded. <ace-index-num>, client <macaddr>, port <port-num> 711 Duplicate mac. An ACL exists for client. Deauthenticating second. client <mac-addr>, port <portnum> 712 Invalid Access-list entry length, client <mac-addr>, port <portnum>. 713 Memory allocation failure for IDM ACL. The ACL, configured on the specified client and port, could not be added to the internal ACL storage. RMON_IDM_CREATE_ACL_ERROR The ACL, configured on the specified client and port, could not be added because the threshold number of per-port ACLs supported in internal ACL storage has been reached. RMON_IDM_ADD_ACL_ERROR An error was detected in the IN keyword value of an ACL entry of an ACL on the specified client and port. RMON_IDM_ACE_PARSE_IN_ERROR An error was detected in the protocol field value of an ACL entry of an ACL on the specified client and port. RMON_IDM_ACE_PROTOCOL_ERROR An error was detected in the FROM keyword value of an ACL entry of an ACL on the specified client and port. RMON_IDM_ACE_FROM_ERROR An error was detected in the ANY keyword value of an ACL entry of an ACL on the specified client and port. RMON_IDM_ACE_ANY_ERROR An error was detected in the TO keyword value of an ACL entry of an ACL on the specified client and port. RMON_IDM_ACE_TO_ERROR An error was detected in the destination IP field value of an ACL entry of an ACL on the specified client and port. RMON_IDM_ACE_DEST_IP_ERROR An error was detected in the TCP/UDP port field value of an ACL entry on the specified client and port. RMON_IDM_ACE_TCP_UDP_PORTS_ERROR The number of entries in an ACL exceeds the maximum number of supported rules. RMON_IDM_QTY_RULE_PER_ACL_LIMIT_ERROR An ACL for the specified MAC address already exists. The ACL with the duplicate MAC address on the specified port is disabled. RMON_IDM_DUPLICATE_MAC_ON_PORT The string configured for an ACL entry on the specified client and port exceeds 80 characters. RMON_IDM_INVALID_ACE_LENGTH A memory allocation occurred for a RADIUS-based ACL. RMON_IDM_MEMORY_ALLOC_FAILURE_ACL 43

714 ACE limit per port exceeded. client <mac-addr>, port <portnum> 715 Exceeded counter per slot limit. client <mac-addr>, port <portnum> 716 Could not apply ACL. client <macaddr>, port <port-num> 717 Logging/hit counter per-port limit exceeded, client <mac-addr>, port <port-num> The maximum number of configured entries has been exceeded on ACLs assigned to the specified port and device. RMON_IDM_QTY_RULE_PER_PORT_LIMIT_ERROR The maximum number of supported packet counters has been exceeded on ACLs assigned to the specified port and device. RMON_IDM_QTY_CNT_PER_SLOT_LIMIT_ERROR An ACL could not be assigned to the specified port and device. RMON_IDM_APPLY_ACL_ERROR The threshold for the packet counters on an ACL assigned to the specified port and device has been exceeded. RMON_IDM_QTY_CNTRS_PER_PORT_LIMIT_ERROR 719 ACE parsing error, icmp types, aceindex <index-num> client <client> port <port-num> 720 ACE parsing error, unexpected syntax, aceindex <index>, client <client>, port <port-num> 721 ACE parsing error, IPv6 ACE received and IPv6 ACEs are not enabled, aceindex <index> There was an error parsing the list of icmp types in the ACE. RMON_IDM_ACE_ICMP_TYPES_ERROR There was some unexpected syntax in the ACE. RMON_IDM_ACE_UNEXPECTED_SYNTAX An IPv6 ACE was received when IPv6 ACEs were not configured. RMON_IDM_ACE_IPV6_NOT_ENABLED 722 Reserved RMON_IDM_UNUSED_8-12 723 Port <port-num> both flow ctrl and jumbo frames enabled. Flow control may not function properly. Flow control and jumbo frames are both enabled and may result in a malfunction in flow control. RMON_PPMGR_FL_JUMBOS_WARN The threshold for ICMP traffic configured on the specified port has been exceeded. A trap for excess ICMP traffic has occurred. RMON_RL_ICMP_LIM_EXCEEDED_ERROR 724 ICMP traffic exceeded configured limit on port <portname> 725-730 Reserved RMON_RL_UNUSED_1-6 731 Ports <port-num> Recognized A hot swap was successful. The specified port(s) passed self-test and are usable. RMON_CHASSIS_FIX_SLOT_HOTSWAP_SELFTEST0 732 Ports <port-num> self test failure The specified port(s) failed to initialize during self-test and are not usable. RMON_CHASSIS_FIX_SLOT_SLOT_FAIL 733 Lost Communication with Ports <port-num> Transmission of heartbeat packets to the specified port(s) was not successful. No connection exists. RMON_CHASSIS_FIX_SLOT_HEARTBEAT_FAILURE 44

734 Ports <port-num> Downloading A software download on the specified port(s) is in progress. RMON_CHASSIS_FIX_SLOT_DOWNLOADING 735 Ports <port-num> Download Complete 736 Ports <port-num> Download Failed The software download on the specified port(s) was successful. RMON_CHASSIS_FIX_SLOT_DOWNLOAD_COMPLETE An attempted software download on the specified port(s) was not successful. RMON_CHASSIS_FIX_SLOT_DOWNLOAD_FAILED 737 Ports <port-num> Ready The specified port(s) are now operational. RMON_CHASSIS_FIX_SLOT_SLOT_READY 738 Unable to Download to Ports <port-num> An attempted retry to download software on the specified port(s) was not successful. RMON_CHASSIS_FIX_SLOT_DOWNLOAD_RETRIES 739 Ports <port-num> may be Faulty There may be an error condition on the specified port(s). RMON_CHASSIS_FIX_SLOT_NO_DWNLD_REQ_RECVD 740 Backplane link to Ports <portnum> failed self test The backplane connection to the specified port(s) failed during the self-test and is not usable. RMON_CHASSIS_FIX_SLOT_BACKPLANE_SLOT_FAIL 741 <mod-num> Ports Present The ports on the specified module are operational. RMON_CHASSIS_FIX_SLOT_MODULE_PRESENT 742 Ports <port-num> NCI Error IntReg=<msg-txt> An NCI error on the specified port(s) has been detected. The message identifies the subsystem that has triggered the NCI error. RMON_CHASSIS_FIX_SLOT_NCI_ERROR 743-745 Reserved RMON_CHASSIS_FIX_SLOT_UNUSED_1-3 746 BSM send to <ip-addr> failed A bootstrap message (BSM) send failed. The specified IP address is the BSM destination address. RMON_PIM_BSR_BSM_SEND_FAIL 747 C-RP advertisement send to <ipaddr> failed 748 Enabled as Candidate BSR using address: <ip-addr> 749 Enabled as Candidate RP using address: <ip-addr> 750 Candidate BSR functionality disabled <pkt-type> 751 Candidate RP functionality disabled 752 Illegal operation in BSR state machine A C-RP advertisement send failed. The specified IP address is the destination address of the message. RMON_PIM_BSR_CRP_SEND_FAIL Candidate BSR functionality has been enabled at the specified IP address. RMON_PIM_BSR_CBSR_ENABLED Candidate RP functionality has been enabled at the specified IP address. RMON_PIM_BSR_CRP_ENABLED Candidate BSR functionality has been disabled. RMON_PIM_BSR_CBSR_DISABLED Candidate RP functionality has been disabled.rmon_pim_bsr_crp_disabled An illegal state/event combination has been detected in the BSR state machine. RMON_PIM_BSR_STATEMACHINE_ILLEGAL 45

753 Static RP configuration failure: <src-ip-addr>, <mcast-addr> 754 Malformed Candidate-RP adv recvd from <ip-addr> 755 Failed flow remove: vid <vid> <multicast group ip-addr> <multicast source ip-addr> The configuration of a static RP for the specified multicast group has failed on the interface. RMON_PIM_BSR_STATIC_RP_CONFIG_FAIL The switch received a malformed C-RP-advertisement. RMON_PIM_BSR_MALFORMED_CRP_ADV The switch failed to delete a flow programmed into hardware. RMON_PIM_HW_REMOVE_FAIL 756-769 Reserved RMON_PIM_BSR_UNUSED_2-16 770 Failed to alloc msg buffer for <routine-name> event 771 Unable to add MCAST address <mcast-addr> 772 Illegal event/state combination called 773 Pkt rcvd that was too short, len = <bytes>, min = <bytes> 774 Vrid <vr-id>, Vid <vlan-id> recd pkt with checksum error standard A message buffer could not be allocated in the specified routine. RMON_VRRP_NO_MSG_BUF Initialization failed because the specified VRRP multicast receive address could not be set up. RMON_VRRP_CANNOT_ADD_MCAST_DEST VRRP received an illegal event/state combination. RMON_VRRP_ILLEGAL_EVENT_STATE_ERROR A VRRP packet of the specified length was received, which is less than the minimum supported packet size. RMON_VRRP_PKT_TOO_SHORT The VR on the specified VLAN has received a VRRP advertisement packet with a checksum error. The VR has therefore dropped that packet. RMON_VRRP_CHECKSUM_ERROR 775 Pkt rcvd with version number <ver-num>, expected <ver-num> A VRRP packet was received with a wrong version number. RMON_VRRP_VER_MISMATCH 776 No VR with vrid <vr-id> found on vid <vlan-id> 777 Vrid <vr-id>, Vid <vlan-id> recd pkt with bad IP-TTL 778 Vrid <vr-id>, Vid <vlan-id> recd pkt with auth type mismatch Indicates a VRRP packet received for a VR that does not exist on the VLAN. This can indicate asymmetric configuration of VRs across VRRP routers. RMON_VRRP_NO_VR_ON_VID A VRRP packet was received by the VR on the specified VLAN with an IP TTL value not equal to 255. RMON_VRRP_PKT_RECD_WITH_BAD_TTL Indicates the VR has received a packet with the auth type mismatch authentication type set to 1 or 2. These are generally valid authentication types, but are not required by RFC 3768. Thus, the software supports only an authentication type of 0 (zero), and VRRP packets with 1 or 2 for authentication type are dropped. For more rmation, refer to the Operating Notes section in the Virtual Router Redundancy Protocol (VRRP) chapter of the Multicast and Routing Guide. RMON_VRRP_AUTH_TYPE_MISMATCH 46

779 Vrid <vr-id>, Vid <vlan-id> recd pkt with invalid auth type 780 Vrid <vr-id>, Vid <vlan-id> recd pkt with advt int mismatch 781 Vrid <vr-id>, Vid <vlan-id> recd pkt with invalid type 782 Vrid<vr-id>, Vid <vlan-id> recd pkt with IP addr mismatch 783 Pkt recd on a non-vrrp Vlan with vid <vlan-id> 784 Vrid<vr-id>, Vid <vlan-id> recd pkt from a duplicate master 785 Failed to allocate pkt buffer for <pkt-type> 786 Failed to allocate memory for <vrrp-app> 787 Failure to send out pkt for vrid <vr-id>, vid <vlan-id> 788 VRRP has been enabled on this router 789 VRRP has been disabled on this router 790 Vrid <vr-id> on Vid <vlan-id> has taken owner IP ctrl 791 Vrid <vr-id> on Vid <vlan-id> has taken backup IP ctrl standard standard standard Indicates the VR has received a VRRP packet with an authentication type set to a value other than the 0, 1, or 2 (allowed by RFC 3768) and has dropped the packet. RMON_VRRP_INVALID_AUTH_TYPE A VR on the specified VLAN has received a VRRP packet with an advertising interval that does not match the interval in the VRRP Master message and has dropped the packet. RMON_VRRP_ADVT_INT_MISMATCH A VRRP packet was received by the indicated VR on the indicated VLAN with the packet type not equal to 1. RMON_VRRP_INVALID_PKT_TYPE A VRRP packet was received by the VR on the specified VLAN with virtual IP address(es) that did not match the virtual IP addresses configured on the receiver VR. RMON_VRRP_VR_IP_MISMATCH A VRRP packet was received on a VLAN that does not have any VRs. This could possibly be a result of misconfiguration of VRs on VLANs. RMON_VRRP_NO_VID A VRRP packet was received from a duplicate master VR by the VR on the specified VLAN. RMON_VRRP_DUP_MASTER_RTR A failure to allocate a packet buffer for gratuitous ARP or VRRP traffic occurred. RMON_VRRP_PKT_ALLOC_FAILURE A failure to allocate memory for the specified VRRP application occurred. RMON_VRRP_MEM_ALLOC_FAILURE A VRRP packet could not be sent out for the specified VR on the specified VLAN due to a system-dependent problem. If packets could not be sent out, the expected protocol operation may be hampered. RMON_VRRP_PKT_SEND_FAILURE VRRP was enabled at the global config level RMON_VRRP_GLOBAL_ENABLE VRRP was disabled at the global config level. RMON_VRRP_GLOBAL_DISABLE The virtual router on the specified VLAN has taken control of its owned IP addresses. RMON_VRRP_VR_TOOK_OWN_IP_CTRL The virtual router on the specified VLAN has taken control of its backup IP addresses. RMON_VRRP_VR_TOOK_BACKUP_IP_CTRL 47

792 Vrid <vr-id> on Vid <vlan-id> lost backup IP ctrl 793 Vrid <vr-id>, Vid <vlan-id> IP addr is duplicated on network 794 Vrid <vr-id> inettype <type> on Vid <vlan-id> has moved to nullauth-compatibility mode. 795 Vrid <vr-id> inettype <type> on Vid <vlan-id> has moved to nonnull-auth-compatiblity mode The specified VR has been preempted by either the owner or a higher-priority master. RMON_VRRP_VR_LOST_BACKUP_IP_CTRL The virtual IP address owned by the VR on the specified VLAN is duplicated on the network. RMON_VRRP_VR_DUP_IP_DETECTED VR has moved to num-auth-compatibility mode. RMON_VRRP_VR_NULL_AUTH_EN VR has moved to non null-auth-compatibility mode (normal mode). RMON_VRRP_VR_NULL_AUTH_DIS 796 Transfer completed USB successfully completed the file transfer. RMON_USB_XFER_COMPLETE 797 Transfer canceled. No workspace left on device. File transfer was interrupted due to insufficient memory on the USB device to complete the operation. RMON_USB_NO_SPACE 798 Transfer aborted, wrong file File transfer stopped due to a missing file or an invalid ID string or revision. RMON_USB_WRONG_FILE 799 Request failed. TFTP request failed due to resource error. RMON_USB_REQ_FAILED 800 Device detected <vendor> <product-id> <serial number> A USB device has been inserted. RMON_USB_STORAGE_INSERTED 801 Unable to mount ufa0 An internal error. Unable to mount ufa0. RMON_USB_MOUNT_FAILURE 802 storage removed The USB was removed. RMON_USB_STORAGE_REMOVED 803 port enabled The USB device was enabled via CLI or SNMP. RMON_USB_PORT_ENABLED 804 port disabled The USB port was disabled via CLI or SNMP. RMON_USB_PORT_DISABLED 805 Unable to block <ip-addr> in hardware, port <port-num> Due to insufficient hardware resources, the port could not be configured to block the specified source IP address. RMON_VIRUSTH_UNABLE_TO_BLOCK 806 Src IP <ip-addr> unblocked The specified source address has been unblocked. RMON_VIRUSTH_SA_UNBLOCK 807-809 Reserved RMON_VIRUSTH_UNUSED_2-4 48

810 <sw-id> installed, key <keynum> 812 Licensing error (<err-num>) occurred, if this problem continues please contact support. A software package has been installed with a license key on the switch. RMON_LICENSING_INSTALL A software package and its license key have been removed from the switch. RMON_LICENSING_UNINSTALL An error has occurred in ProCurve software licensing. RMON_LICENSING_PROTEUSERROR 811 <sw-id> uninstalled, key <keynum> 813-816 Reserved RMON_LICENSING_UNUSED_1-4 817 Slot <slot-num> self test failure The module in the specified slot failed its self-test and is not usable. RMON_CHASSIS_SLOT_FAIL_SELFTEST 818 Slot <slot-num> Invalid: This switch supports only <mod-type> modules 819 Slot <slot-num> Invalid: Module not supported by this software version 820 Booted f/secondary. Primary corrupt, needs reload! Or Booted f/primary. Secondary corrupt, needs reload! 821 Maximum system VLANs count reached. The module in the specified slot is not supported. Only the specified type of modules are supported in the switch. RMON_CHASSIS_SLOT_INVALID The module in the specified slot is not supported by the current software version. RMON_CHASSIS_SLOT_UNSUPPORTED The main or backup version of the software image is corrupt. Reload the image. The switch booted by using the valid software image. Load a new image to replace the corrupt version. RMON_SYSTEM_BOOT_IMAGE The auto-provision could not create the VLAN due to the maximum system VLAN count being reached. At this point the autoprovision functionality is not operational. Delete one VLAN to resolve the issue. RMON_LLDP_MAX_SYS_VLANS 822 Created VLAN <vlan-id> The specified VLAN has been successfully configured automatically by LLDP. RMON_LLDP_CREATED_VLAN 823 Deleted VLAN <vlan-id> The specified VLAN configuration has been deleted automatically by LLDP. RMON_LLDP_DELETED_VLAN 824 Port(s) <port-num> added to VLAN <vlan-id> 825 Port(s) <port-num> removed from VLAN <vlan-id> The specified port(s) have automatically been added to the specified VLAN configuration. RMON_LLDP_ADDED_PORTS The specified port(s) have been removed from the VLAN configuration. RMON_LLDP_REMOVED_PORTS 49

826 Port <port-num> released from VLAN <vlan-id> 827 Port <port-num> inhibited from joining VLAN <vlan-id> 828 PVID mismatch on port <portnum> (VID <vid>) with peer device port (VID<vid>) 829 RTC: Battery Failure Detected or RTC: Clock Initialization failure The specified port has been released from the specified VLAN configuration. This is most likely due to another application configuring the port for temporary untagged membership in some other VLAN, the port being configured in a trunk, or the VLAN being deleted. RMON_LLDP_TPVID_RELEASED The specified port has been prevented from joining the VLAN configuration. RMON_LLDP_TPVID_INHIBITED Port VLAN mismatch observed on the specified VLAN interface with peer device interface. RMON_LLDP_VID_MISMATCH Failure of the switch battery or switch clock occurred. RMON_RTC_FAILURE 830 Limit for IP addresses <addrlimit> is exceeded <num> The limit for IP addresses (1000) is exceeded (1001). RMON_INST_MON_THRESHOLD_EXCEEDED 832 Possible configuration problem detected on port <port-num>. UDLD VLAN configuration does not match port's VLAN configuration. 833 Link state on port <port-num> is changed to ' <link-state>' state. The VLAN configuration for uni-directional link detection (UDLD) on the specified port does not match the VLAN configuration on the port. RMON_UDLD_WARN A change in the uni-directional link state on the port occurred. RMON_UDLD_LINK_STATE_CHANGE 834-838 Reserved RMON_UDLD_UNUSED1-4 839 <stp-priority-level> Root changed from <mac-addr> to <mac-addr> 840 port <port-num> disabled <secs>- BPDU received on protected port. 841 port <port-num> - BPDU protection auto-reenable timer expired. The Spanning Tree Protocol (STP) root MAC address has changed for the specified STP priority level. RMON_STP_NEW_ROOT The port has been disabled for the specified time period (in seconds) when a BPDU was received on a protected port. RMON_STP_ERROR_DISABLED_PORT The timer used to re-enabled BPDU protection has expired on the specified port. RMON_STP_ENABLE_AFTER_ERROR 842 <CIST or MSTI<num>> starved for <MSTI msg Rx or BPDU Rx> on port <port-num> from <bridgeid:bridge MAC address> The spanning-tree instance indicated is starved for messages on the indicated port from the indicated address. RMON_STP_RX_STARVATION 50

843 bpdu loss - port <port-num> moved to inconsistent state for <CIST or MSTI<num>> 844 port <port-num> moved out of inconsistent state for <CIST or MSTI<num>> Port is changed to inconsistent state for the indicated CIST or MSTI number. RMON_STP_TO_INCONSISTENT Port is no longer in an inconsistent state for the indicated CIST or MSTI number. RMON_STP_OUT_OF_INCONSISTENT 845-849 Reserved RMON_STP_UNUSED_9-16 850 <mod-num>: Server <ip-addr> packet received on untrusted port <port-num> dropped 851 <mod-num>: Ceasing untrusted server logs for <secs> A DHCP server is trying to transmit a packet on an untrusted port. RMON_DSNOOP_UNTRUSTED_PORT_SERVER Multiple packets were received on an untrusted port from a DHCP server and the packets were dropped. To avoid filling the event log with repeated transmission attempts from an untrusted server, dropped-packet events will not be logged for the specified number of seconds. RMON_DSNOOP_UNTRUSTED_PORT_SERVER_SUSP 852 <mod-num>: Client packet destined to untrusted port <portnum> dropped A unicast packet with a destination address on an untrusted port was received from a DHCP client and was dropped. RMON_DSNOOP_UNTRUSTED_PORT_CLIENT_DEST 853 <mod-num>: Ceasing untrusted port destination logs for <secs> 854 <mod-num>: Unauthorized server <ip-addr> detected on port <port-num> 855 <mod-num>: Ceasing unauthorized server logs for <secs> 856 <mod-num>: Received untrusted relay rmation from client <mac-addr> -<mac-addr> on port <port-num> Multiple unicast packets with an untrusted port destination were received from a DHCP client and were dropped. To avoid filling the event log with repeated messages about dropped packets with an untrusted port destination, these events will not be logged for the specified number of seconds. RMON_DSNOOP_UNTRUSTED_PORT_CLIENT_SUSP An unauthorized DHCP server is trying to send packets to the port. The server packets are dropped because the server address is not configured in the authorized server table maintained by DHCP snooping. RMON_DSNOOP_UNAUTHORIZED_SERVER Multiple packets from an unauthorized DHCP server were dropped. To avoid filling the event log with repeated messages about dropped packets from an unauthorized DHCP server, these events will not be logged for the specified number of seconds. RMON_DSNOOP_UNAUTHORIZED_SERVER_SUSP Packets with relay option rmation were received from a DHCP client on an untrusted port and were dropped. RMON_DSNOOP_UNTRUSTED_OPT82 857 <mod-num>: Ceasing untrusted relay rmation logs for <secs> Packets with DHCP relay rmation were received from a DHCP client on an untrusted port and were dropped. To avoid filling the event log with repeated attempts, events for packets with untrusted DHCP relay rmation will not be logged for the specified number of seconds. RMON_DSNOOP_UNTRUSTED_OPT82_SUSP 51

858 <mod-num>: Client address <mac-addr> not equal to source MAC <mac-addr> detected on port <port-num> 859 <mod-num>: Ceasing client address mismatch logs for <secs> 860 <mod-num>: Attempt to release address <ip-addr> leased to port port-num> detected on port <port-num> 861 <mod-num>: Ceasing bad release logs for <secs> 862 <mod-num>: Lease table is full, DHCP lease was not added 863 <mod-num>: Ceasing lease table is full logs for <secs> 864 <mod-num>: reading <portnum>:<mac-addr> <ip-addr> 865 <mod-num>: Ceasing remote server lease file read status logs for <secs> 866 <mod-num>: writing <portnum>:<mac-addr> <ip-addr> 867 <mod-num>: Ceasing remote server lease file write status logs for <secs> 868 <module>: The dynamic binding <binding> port <port-num> was replaced with a manual binding The DHCP agent detected that a source MAC address in a client packet does not match the MAC address in the Change Address (chaddr) field of the packet. The packet was dropped. RMON_DSNOOP_MAC_MISMATCH Packets that were received from a DHCP client with mismatched source MAC address and Change Address (chaddr) values were dropped. To avoid filling the event log with repeated attempts, events for mismatched DHCP client addresses will not be logged for the specified number of seconds. RMON_DSNOOP_MAC_MISMATCH_SUSP A DHCP client tried to release an IP address while a DHCPRELEASE or DHCPDECLINE packet was received on a port different from the port to which the IP address is leased. RMON_DSNOOP_BAD_RELEASE Packets that were received from a DHCP client with an invalid release were dropped. To avoid filling the event log with repeated messages about dropped DHCP client packets, these events will not be logged for the specified number of seconds. RMON_DSNOOP_BAD_RELEASE_SUSP The lease database maintained by DHCP snooping i s full. The lease entry cannot be added to the table. RMON_DSNOOP_TABLE_FULL Multiple attempts were made to add an entry to the lease database when the lease table is full. To avoid filling the event log with repeated attempts, events reporting that the lease table is full will not be logged for the specified number of seconds. RMON_DSNOOP_TABLE_FULL_SUSP The lease file specified by the DHCP snooping database string could not be read. RMON_DSNOOP_READ_LEASES_ERROR Multiple attempts to read the lease file from a remote server were made. To avoid filling the event log with repeated attempts, status messages for failed lease-file read operations will not be logged for the specified number of seconds. RMON_DSNOOP_READ_LEASES_SUSP The lease file specified by the DHCP snooping database string could not be written to the remote server. RMON_DSNOOP_WRITE_LEASES_ERROR Multiple attempts to write the lease file to a remote server were made. To avoid filling the event log with repeated attempts, status messages for failed lease-file write operations will not be logged for the specified number of seconds. RMON_DSNOOP_WRITE_LEASES_SUSP DHCP replaced a learned binding with a manual binding because the lease table is full. RMON_DSNOOP_TABLE_FULL_REM_LEASE 52

869 Ceasing removed lease logs for <duration> 870 Drop request from <mac-addr> for <ip-addr> because the address is assigned to another client 871 Ceasing status logs for Duplicate IP request for <duration> 872 RMON <file-type> file corrupt, is being deleted Removed lease logs will not be logged for the specified duration. The dsnooping table is full. RMON_DSNOOP_TABLE_FULL_REM_LEASE_SUSP The client is requesting an IP address that is already in use by a different client in the same VLAN. The request from the indicated MAC address is dropped. RMON_DSNOOP_BAD_IP_REQ Status logs are not being continued. The duration can be in seconds, for example, 5s, or minutes, for example 5m. RMON_DSNOOP_BAD_IP_REQ_SUSP The RMON alarms or events file is corrupt and will be deleted. RMON_SNMP_REMOVE_CORRUPT_FILE 873-882 Reserved RMON_SNMP_UNUSED_1-10 883 Port failure. Port <port-num> has been reset. 884 Port <port-num> disabled - loop detected. 885 Port <port-num> disabled - trunk is disabled. The failed port has now been reset and is operational. RMON_FF_DEAD_PHY A loop on the port has been detected. The port is disabled. RMON_LOOP_PROTECT_DISABLE_PORT The port was disabled by loop protection because it was added to a trunk that has been disabled by loop protection. RMON_LOOP_PROTECT_DISABLE_TRUNKED_PORT 886 Port <port-num> - loop detected. A loop on the switch has been detected on the specified port by the loop protection protocol. The port was not disabled because the loop protection packet was received on a port that is configured to not disable other ports. RMON_LOOP_PROTECT_LOOP_DETECTED 887 Port <port-num> - disabled period expired. 888 Port <port-num> - received packet failed authentication. 889 port <port-num> continuous loop detected; manually disable port to stop this message 890 Flow-control and sflow sampling now enabled. Egress-sampling being disabled. The disable period for the port has expired and an attempt was made by loop protection to re-enable the port. RMON_LOOP_PROTECT_ENABLE_PORT Loop protection packets on the port are not being processed because they are not authentic. This can happen if a malicious user is trying to spoof loop protection packets. RMON_LOOP_PROTECT_SECURITY_AUTH_FAILED Loop protection has repeatedly detected a loop on the specified port and the port should be disabled. RMON_LOOP_PROTECT_CONTINUOUS_LOOP Because flow control and sampled flow are now enabled, egress sampling has been disabled. (Egress sampling is disabled even if sampled flow is not enabled.) RMON_SFLOW_DISABLE_EGRESS 891 Flow-control is disabled. Reenabling sflow egress-sampling. Because flow control is now disabled, egress sampling has been re-enabled. (Egress sampling is re-enabled even if sampled flow is is not enabled.) RMON_SFLOW_ENABLE_EGRESS 53

892-896 Reserved RMON_SFLOW_UNUSED_1-5 897 The existing config requires changing default for parameter: <parameter> 898 LP Manager s has disabled port <port-num> for <num-secs> seconds 899 LP Manager has disabled port <port-num> 900 port <port-num> time requested by LP Manager has expired. 901 Failed to allocate new <route table rmation> entry 902 Failed to deallocate <route table rmation> entry 903 Failed to allocate memory for <route table rmation> 904 Failed to add entry <route table rmation> entry may already exist 905 Failed to find entry <route table rmation> 906 Invalid route descriptor for operation <route table rmation> 907 <slot> <memory location> <table type> parity recovery <table entry> 908 Failed to add neighbor timer entry for rtdesc: <desc> timeout: <time> vrf: <value> ipaddr: <ipaddr> You must change the default for the parameter indicated, for this configuration. RMON_CFG_INIT_OVERRIDE_DEFAULT The specified port has been disabled for the indicated number of seconds by LP Manager. RMON_LPMGR_DISABLE_TIMEOUT LP Manager has disabled the indicated port with no timeout. RMON_LPMGR_DISABLE_INFINITE The port disable timer has expired. RMON_LPMGR_TIMEOUT_EXPIRED New <route table rmation> was not allocated. RMON_IPADDRMGR_ENTRY_ALLOC_FAIL <route table rmation> was not deallocated. RMON_IPADDRMGR_ENTRY_DEALLOC_FAIL Memory for <route table rmation> was not allocated. RMON_IPADDRMGR_MEM_ALLOC_FAIL Entry <route table rmation> was not added; it may exist already. RMON_IPADDR_ENTRY_ADD_FAIL Entry <route table rmation> was not found. RMON_IPADDRMGR_ENTRY_FIND_FAIL The route descriptor is invalid. RMON_IPADDRMGR_INVALID_ROUTEDESC There has been a successful recovery from a parity error. RMON_IPADDRMGR_PARITY_ERROR_RECOVERY This message is logged when out neighbor cache management runs into a serious error and can t add a timer queue entry. These are used to manage the neighbor cache. The logged parameters are the IP address of the neighbor cache entry that was affected. RMON_IPADDRMGR_NUD_TIMER_ADD_FAIL 937 Fabric <mod-num> inserted The indicated fabric module has been inserted into the chassis for the first time (or first detected at boot). 928 Fabric <blade> active The fabric blade is actively passing traffic. RMON_CHASSIS_FABRIC_ACTIVE 929 Fabric <blade> removed The indicated fabric blade was removed from the chassis. RMON_CHASSIS_FABRIC_REMOVE 54

930 Slot Link failure: Fabric <module> has faulty link to Slot <slot-num> A fault on a line card prevents it from connecting to fabric. The error may be recoverable. RMON_CHASSIS_FABRIC_FAIL_LC 931 Fabric failure: link error between Fabric <module> and Slot <slotnum> 932 chassis: Unknown fabric failure: link between Fabric <module> and Slot <slot-num> down 933 Chassis running at reduced backplane capacity 934 Chassis has no active fabrics. Line cards resetting. 935 Fabric <blade> disabled via the configuration setting. The fabric blade has a faulty link to a slot in the chassis. The error may be recoverable. RMON_CHASSIS_FABRIC_FAIL_FABRIC The link between a fabric blade and a slot has an error that can t be traced to either the fabric or the slot without further testing. RMON_CHASSIS_FABRIC_FAIL_EITHER The switch is operating with fewer active fabrics than required to maintain the backplane s full capacity. RMON_CHASSIS_FABRIC_LOW_CAP There are no active fabric modules. They are either not present, failed, or disabled. RMON_CHASSIS_FABRIC_NOT_AVAIL The indicated fabric module is disabled via SNMP or the command line interface (redundancy fabric-module disable) RMON_CHASSIS_FABRIC_DISABLED 936 Fabric <blade> enabled The indicated fabric module is enabled via SNMP or the command line interface (redundancy fabric-module enable) RMON_CHASSIS_FABRIC_ENABLED 937 Fabric <blade> inserted The fabric blade has been inserted or first detected at boot. RMON_CHASSIS_FABRIC_INSERT 938 Fabric failure: Fabric <bladename> is not responding 939 Fabric failure: Fabric <bladename> failed selftest 940 Fabric failure: Fabric <bladename> power failure A fabric blade is not responding on the SRI. RMON_CHASSIS_FABRIC_NOT_RESPONDING The fabric blade indicated failed selftest. RMON_CHASSIS_FABRIC_ST_FAIL The fabric blade s power supply has failed. RMON_CHASSIS_FABRIC_POWER_FAIL 941-942 Reserved 943 Filter-rule length greater than 80 char MAX, list-index <list-num> rule-index <rule-num> 944 Filter-rule parsing error. permit/ deny keyword, list-index <listnum> rule-index <rule-num> 945 Filter-rule parsing error. in keyword, list-index <list-num> rule-index <rule-num> The filter-rule s length exceeded the 80 character maximum. RMON_DCA_RULE_PARSE_LENGTH_ERROR There was an error with the permit/deny keyword while parsing the filter rule entry. RMON_DCA_RULE_PARSE_PERMIT_KWD_ERROR There was an error with the in keyword while parsing the filter entry rule. RMON_DCA_RULE_PARSE_IN_KWD_ERROR 55

946 Filter-rule parsing error. ip keyword or protocol number, listindex <list-num> rule-index <rule-num> There was an error with the ip keyword or the protocol number while parsing the filter rule entry. RMON_DCA_RULE_PARSE_IP_PROTOCOL_NUM_ERROR 947 Filter-rule parsing error. from keyword, list-index <list-num> rule-index <rule-num> 948 Filter-rule parsing error any keyword, list-index <list-num> rule-index <rule-num> 949 Filter-rule parsing error. to keyword, list-index <list-num> rule-index <rule-num> 950 Filter-rule parsing error. destination address/mask, listindex <list-num> rule-index <rule-num> 951 Filter-rule parsing error. tcp/udp ports, list-index <list-num> rule index <rule-num> 952 VLAN-id validation error, client mac <mac-address> port <portnum>, profile-index <profilenum>, VLAN-id <vid> 953 VLAN-id validation error, untagged/tagged conflict, profile-index <profile-num>, VLAN-id <vid> 954 PriorityRegen validation error, profile-index <profile-num> 955 Profile filter index validation error, profile-index <profilenum>, filter index <filter-num> 956 Profile validation error, No attributes enabled. profile-index <profile-num> 957 Profile validation error, Tagged Egress Vlan Map, profile-index <profile-num> There was an error with the from keyword while parsing the filter rule entry. RMON_DCA_RULE_PARSE_FROM_KWD_ERROR There was an error with the any keyword while parsing the filter rule entry. RMON_DCA_RULE_PARSE_ANY_KWD_ERROR There was an error with the to keyword while parsing the filter rule entry. RMON_DCA_RULE_PARSE_TO_KWD_ERROR There was an error with the destination address/mask while parsing the filter rule entry. RMON_DCA_RULE_PARSE_DESTINATION_ERROR There was an error with the tcp/udp port while parsing the filter rule entry. RMON_DCA_RULE_PARSE_TCPUDP_ERROR There was an error with the setting of a VLAN-id for the given profile for the hpidfusrprof MIB. RMON_DCA_VID_VALIDATION_PROFILE_ERROR There was a conflict between the untagged vid and tagged vid in the profile. RMON_DCA_VID_VALIDATION_PROFILE_CONFLICT_ERROR There was an error with the setting of a VLAN-id for the given profile for the hpicfusrprof MIB. RMON_DCA_PRIOR_RGEN_VALIDATION_PROFILE_ERROR An inactive or invalid filter index was used when setting the given profile for the hpicfusrprof MIB. RMON_DCA_FILTERINDEX_VALIDATION_PROFILE_ERROR No attributes were enabled in the attempted profile set for the hpicfusrprof MIB. RMON_DCA_NO_ATTRIBUTES_ENABLED_PROFILE_ERROR There was an invalid or conflicting tagged vids list in the attempted profile set for the hpidfusrprof MIB. RMON_DCA_TAGGED_EGRESS_VLAN_PROFILE_ERROR 56

958 Profile apply error, untagged vlan conflict, MAC <mac-address> port <port-num> profile (profilenum> 959 Profile apply error, tagged vlan conflict, MAC <mac-address>, port <port-num> profile <profilenum> 960 Profile apply error, priority regen conflict, MAC <mac-address> port <port-num> profile <profilenum> 961 Profile apply error, max ingress bandwidth conflict, MAC <macaddress> port <port-num> profile <profile-num> 962 No DHCPv6 servers have responded to a SOLICIT message on vlan: <vid> 963 DHCPv6 server has not responded to a REQUEST message on vlan <vid> 964 Failed to allocate memory for <module> 965 DHCPv6 client has been enabled on Vlan-id: <vid> 966 DHCPv6 client has been disabled on Vlan-id: <vid> 967 Lease has expired for the DHCPv6 address <ip-address> on vlan: <vid> 968 DHCPv6 server has no IPv6 addresses to lease out on vlan: <vid> 969 DHCPv6 message on vlan: <vid> failed receive path checks - dropped 970 DHCPv6 address not added on Vlan: <vid>. Maximum Ipv6 address limit reached standard standard standard There was an untagged VLAN conflict in the attempted profile set for the hpicfusrprof MIB RMON_DCA_PROFILE_APPLY_PVID_ERROR There was a tagged VLAN conflict in the attempted profile set for the hpicfusrprof MIB. RMON_DCA_PROFILE_APPLY_TVID_ERROR There was a priority regeneration conflict in the attempted set for the hpicfusrprof MIB. RMON_DCA_PROFILE_APPLY_PRIRGEN_ERROR There was a max ingress bandwidth conflict in the attempted set for the hpicfusrprof MIB. RMON_DCA_PROFILE_APPLY_MXINGBWDTH_ERROR The DHCPv6 server is not available. RMON_DHCPV6C_NO_SRVR_AVAILABLE The DHCPv6 server is not responding to requests. RMON_DHCPV6C_NO_SRVR_RESPONSE The memory for the indicated module was not allocated. RMON_DHCPV6C_MEM_ALLOC_FAILURE The DHCPv6 client is enabled on the indicated VLAN. RMON_DHCPV6C_ENVLAN The DHCPv6 client is disabled on the indicated VLAN. RMON_DHCPV6C_DISVLAN The lease has expired for the indicated IPv6 address on the specified VLAN. RMON_DHCPV6C_ADDR_LEASE_EXPIRY The DHCPv6 server has no IPv6 addresses to lease to the specified VLAN. RMON_DHCPV6C_SRVR_NOADDRSAVAIL The message on the indicated VLAN was dropped because it failed the path checks. RMON_DHCPV6C_PKTRECV_FAIL The DHCPv6 address was not added for the indicated VLAN because the maximum number of addresses was reached. RMON_DHCPV6C_MAXLIMIT_REACHED 57

971 DHCP address not added on Vlan: <vid>. Subnet already exists. 972 port <port-num> removed from dhcp-snooping enabled vlan <vid> 973 dhcp-snooping disabled globally, dynamic IP lockdown also disabled 974 dhcp-snooping disabled on vlan <vid>, dynamic IP lockdown also disabled The DHCPv6 address was not added to the indicated VLAN as that VLAN already exists. RMON_DHCPV6C_SUBNET_EXISTS A port configured for dynamic IP lockdown was removed from a dhcp-snooping enabled VLAN. RMON_DIPLD_PORT_REMOVED_DSNOOP_VLAN DHCP snooping was globally disabled; DIPLD is no longer being configured in hardware. RMON_DIPLD_DSNOOP_DISABLED_GLOBAL DHCP snooping was disabled on a VLAN; DIPLD is no longer being configured on that VLAN. RMON_DIPLD_DSNOOP_DISABLED_VLAN 975 port <port-num> is untrusted A port has transitioned from the trusted state to the untrusted state. RMON_DIPLD_PORT_TRUST_TO_UNTRUSTED 976 unable to add port <port-num> to trunk, insufficient hw resources 977 unable to apply dynamic IP lockdown to port <port-num>, insufficient hw resources 978 unable to configure dynamic IP lockdown on port <port-num>, ACL is configured on port 979 unable to add binding for <ipaddress>, <mac-address> on port <port-num> 980 unable to ip lock-down vlan <vid> on port <port-num>, not enough hw resources 981 Access denied <ip-addr> -> <ipaddr> port <port-num> <packetcount> packets received since last log. 982 too large packet received from <ip-address> server 983 malformed packet received from <ip-address> server There was an error attempting to add a port to a trunk because of insufficient hardware resources on that port. RMON_DIPLD_PORT_ADD_TO_TRUNK_ERROR There was an error applying the ACL because of insufficient hardware resources. RMON_DIPLD_PORT_ADD_HW_RESOURCE_ERROR There was an error attempting to configure DIPLD on a port because an ACL is already applied on the port. RMON_DIPLD_PORT_ADD_ACL_CONFLICT_ERROR There was an error attempting to add a DIPLD binding to a port. RMON_DIPLD_ADD_BINDING_OUT_OF_RESOURCES There was an error attempting to lock down the IP address on the indicated port and the indicated VLAN because of insufficient hardware resources. RMON_DIPLD_VLAN_DENY_OUT_OF_RESOURCES A new dynamic IP lockdown violation was detected. The source ip address, destination IP address, source port and the packet count since the last log is provided. RMON_DIPLD_VIOLATION A packet that is too large was received from the indicated server. RMON_TACACS_TOO_LARGE_PACKET A malformed packet was received from the indicated server. RMON_TACACS_MALFORMED_PKT 58

984 wrong ver# <version-number> in packet from <ip-address> server The wrong version number was in the packet received from the indicated server. RMON_TACACS_VER_MISMATCH_PKT 985 wrong seq# <seq-num> (expected <seq-num>) in packet from <ip-address> server An incorrect packet sequence number was received from the specified server. RMON_TACACS_BAD_SEQ_NUM_PKT 986-988 Reserved for TACACS 989 AUTHORIZED Access granted for access method <accessmethod> 990 Conflict on port <port-num>: 802.1x without client limit and Web/Mac-authentication both configured 991 Unauthenticated VLAN can t be simultaneously enabled on both 802.1X and Web or MAC auth 992 Permit Command: user <username> command <command> 993 Denied Command: user <username> command <command> 994 system: <module port> <id> <number> parity error recoveries in previous <interval> 995 <num> parity recoveries in previous <time-period> Authorized access is granted for the indicated access method. RMON_AUTH_AUTHORIZED_ACCESS Port-based 802.1X is co-existing with web auth or MAC auth, probably from a legacy configuration. One of the features may have malfunctioned. RMON_AUTH_8021X_WMA_CONFLICT Port-based 802.1X is co-existing with Web or MAC auth, most likely from a legacy configuration. The legacy configuration may have enabled a Guest VLAN for both 802.1X and Web or MAC authentication. RMON_AUTH_8021X_WMA_GUESTVLAN_CONFLICT A local user executed a permitted command. RMON_AUTH_CMD_PERMITTED A local user executed a command for which he did not have authorization. RMON_AUTH_CMD_DENIED Logs the number of successful recoveries that occurred during the interval: 5 minutes, 1 hour, 24 hours. This reduces the number of system log events when many recoveries happen close in time. RMON_PARITY_ERROR_RECOVERY A summary of the number of parity recoveries in the indicated time period. 996 Provider Bridge Mode -<provider bridge mode> 997 Provider Bridge _ <number> bpdus seen on customernetwork ports RMON_PARITY_ERROR_SUMMARY Indicates the Provider Bridge Mode. RMON_PBRIDGE_MODE There is a possible misconfiguration with the Provider Bridge port. RMON_PBRIDGE_PORT_TYPE_MISCONFIG 1000 Unused RMON_HPESP_ESPD_EVT_1 1999 Unused RMON_HPESP_ESPD_EVT_MAX 59

2000 Unable to alloc a buf of size <size> for %s 2001 Unable to alloc a msg buffer for %s 2002 Unexpected state/event <state>/ <event> in %s statematch 2003 Rcvd unkwn addr fmly <family> in pkt. 2004 Failed to register IPAM call back routine. 2005 Failed to register IFM callback routine 2006 Subsystem <subsystem> api <api> failed 2007 Internal api <api> failed: <system> 2008 IPv6 mcast fileter allocation failure: <failure> 2009 An IPv6 multicast filter moved to a non-multicast client: <client>. 2010 An Ipv4 multicast filter moved to a non-multicast client: <client>. 2011 Per VLAN unknown Data filter for VLAN <vid> moved to non multicast client: <client>. 2012 A non-multicast client: <client>, is registerd with client ID <id>. 2013 A non-multicast client: <client>, with client ID: <id> got unregistered. MTM could not allocate memory. RMON_MTM_MALLOC_ERROR A message buffer could not be allocated. RMON_MTM_NO_MSG_BUF MTM received an event type in a state that was not expected. RMON_MTM_UNEXPECTED_STATE_ERROR An MTM packet with an unknown address family was received. RMON_MTM_UNKNOWN_ADDR_FAMILY The IPAM MTM callback routine failed to initialize. RMON_MTM_IPAM_CALLBACK_FAIL The IFM MTM callback routine failed to initialize. RMON_MTM_IFM_CALLBACK_FAIL The specifed API for the indicated subsystem failed. RMON_MTM_SUBSYSTEM_API_FAILURE An internal API has failed. RMON_MTM_INTERNAL_API_FAILURE All the IPv6 multicast filters available for this switch have been used. RMON_MTM_MCAST_FILTERS_ALLOCATION_FAILURE The IPv6 multicast filter has been moved to a non-multicast client. RMON_MTM_IPV6_FILTER_MOVED_TO_NONMCAST The IPv4 multicast filter has been migrated to a non_multicast client. RMON_MTM_IPV4_FILTER_MOVED_TO_NONMCAST The per-vlan DD filter has been migrated to a non-multicast client. RMON_MTM_PERVLAN_DD_MOVED_TO_NONMCAST A non-multicast client has been registered with MTM. RMON_MTM_NON_MCAST_CLIENT_REGISTERED A non-multicast client has been unregistered with MTM. RMON_MTM_NON_MCAST_CLIENT_UNREGISTERED 2400 <type of authentication> client, RADIUS-assigned VID validation error. MAC <mac-address> port <port-num> VLAN-Id <vid> There was a validation error of some kind for a RADIUS-assigned vid. RMON_DCA_RADIUS_VID_VALIDATION_ERROR 60

2401 <type of authentication> client RADIUS-assigned priority-regen validation error, MAC <macaddress> port <port-num> 2402 <type of authentication> client untagged VLAN-id arbitration error, MAC <mac-address> port <port-num> 2403 <type of authentication> client tagged VLANs arbitration error, MAC <mac-address> port <portnum> 2404 <type of authentication> client priority regeneration (aka COS) arbitration error, MAC <macaddress> port <port-num> There was a validation error of some kind for a priorityregeneration (or port-cos). RMON_DCA_PRIOR_RGEN_VALIDATION_RADIUS_ERROR There was an untagged VLAN-id arbitration conflict for the particular auth client for the particular auth mode. RMON_DCA_PVID_ARB_ERROR There was a tagged VLAN-id arbitration conflict for the particular auth client for the particular auth mode. RMON_DCA_TVIDS_ARB_ERROR There was a priority regeneration arbitration conflict for the particular auth client for the particular auth mode. RMON_DCA_PRIO_RGEN_ARB_ERROR 2405 <type of authentication> client max ingress bandwidth (aka ratelimiting) arbitration error, MAC <mac-address> port <port-num> There was a max ingress bandwidth arbitration conflict for the particular auth client for the particular auth mode. RMON_DCA_MAX_INGR_BW_ARB_ERROR 2406 Invalid option: NAWS SE Missing (RFC 1073) 2409 Filter-rule parsing error. icmp types, list-index <number> ruleindex <number> 2410 Filter rule parsing error. unexpected syntax, list-index <number> rule-index <number> 2411 802.1X client max egress bandwidth (aka rate-limiting) arbitration conflict MAC <macaddr> port <port-num> There was an invalid telnet option. NAWS stands for Negotiate About Window Size ; the telnet client has sent a message rming the telnet server that the window width and height rmation is missing. RMON_TELNET_INVALID_OPTION There was an error with ICMP types while parsing the filter rule entry. RMON_DCA_RULE_PARSE_ICMP_ERROR There was an error while parsing the filter rule entry. RMON_DCA_RULE_PARSE_UNEXPECTED_SYNTAX There was a max egress bandwidth arbitration conflict for a particular auth client for a particular auth mode. RMON_DCA_MAX_EGR_BW_ARB_ERROR 2502 Autorun Agent initialized Autorun log in is initialized. RMON_AUTORUN_EVT_LOGINIT 2503 Autorun Agent terminated The Autorun agent is terminated. RMON_AUTORUN_EVT_LOGCLOSED 2504 USB Secure Management (Autorun) is disabled 2505 Can t find file: <filename> or Cannot open file: <filename> Autorun is disabled. RMON_AUTORUN_EVT_DISABLED Autorun can t get the file rmation. RMON_AUTORUN_EVT_CANNOT_STAT_FILE 61

2506 Filename too long: <filename> The file name is too long. RMON_AUTORUN_EVT_FILENAME_TOO_LONG 2507 Cannot create file: <filename> The file can t be created. RMON_AUTORUN_EVT_CANNOT_CREATE_FILE 2508 Cannot delete file: <filename> The file can t be deleted. RMON_AUTORUN_EVT_CANNOT_DELETE_FILE 2509 Cannot write to file: <filename> Autorun cannot write to the file. RMON_AUTORUN_EVT_CANNOT_WRITE_TO_FILE 2510 Cannot stat dir <directory-path> Autorun can t get directory rmation. RMON_AUTORUN_EVT_CANNOT_STAT_DIR 2511 Cannot open dir <directory-path> Autorun can t open the directory. RMON_AUTORUN_EVT_CANNOT_OPEN_DIR 2512 Cannot create directory: <directory-name> 2513 Error when processing file: <filename> Autorun can t create the directory. RMON_AUTORUN_EVT_CANNOT_CREATE_DIR There is a command file parsing error. RMON_AUTORUN_EVT_CMDFILE_PARSING_ERROR 2514 No valid command file found No valid command file was found. RMON_AUTORUN_EVT_NO_CMDFILE_FOUND 2518 Fail to execute command: <command> 2519 No command found in file: <filename> 2521 Execution failure system out of resources The execution of the CLI command failed. RMON_AUTORUN_EVT_FAILED_EXEC No CLI command was found in the command file. RMON_AUTORUN_EVT_NO_COMMAND_IN_FILE A command failed to execute because of lack of resources. RMON_AUTORUN_EVT_FAILED_SYSTEM 2522 <autorun version> Displays the autorun version. RMON_AUTORUN_EVT_USBSEDMGT_VERSION 2523 <command file processed> Displays the command file processed. RMON_AUTORUN_EVT_COMMANDFILE_PROCESSED 2524 <author and operator id> Displays the author and operator IDs. RMON_AUTORUN_EVT_AUTHOR_OPERATOR_INFO 2523 Command file processed: <filename> or Post command file processed: <filename> 2550 Requesting co-processor OS image location in flash Information about the command file processed. RMON_AUTORUN_EVT_COMMANDFILE_PROCESSED The chassis manager is requesting the slave OS image from the download task. RMON_CHASSIS_LOAD_REQ_OS 62

2551 Failed to obtain co-processor OS image location 2552 Loading of co-processor OS image in progress 2553 Loading of co-processor OS image complete 2554 Failed loading the co-processor OS image The download task was unable to provide the slave OS image location. RMON_CHASSIS_LOAD_REQ_OS_FAILED Chassis manager is getting the slave OS from flash, decompressing it, and copying the OS into the slave area of RAM. RMON_CHASSIS_LOAD_OS_IN_PROGRESS Chassis manager has completed copying the slave OS into the slave area of RAM. RMON_CHASSIS_LOAD_OS_COMPLETE The chassis manager failed to copy the slave OS into the slave area of RAM. RMON_CHASSIS_LOAD_OS_FAILED 2555 Coprocessor ready The slave core goes into the available state. RMON_CHASSIS_LOAD_OS_COPROCESSOR_READY 2556 Stack port <port-num> cable inserted 2557 Stack port <port-num> cable removed 2558 Stack port <port-num> is now online 2559 Stack port <port-num> is now offline 2560 Stack port <port-num> cable initialization error 2561 Expansion module <module> Not a ProCurve module. Please go to: www.hp.com/rnd/device_help/ 2_rm for more. A slot is reloaded in an operational chassis. RMON_CHASSIS_STACKPORT_INSERTED A slot is reloaded in an operational chassis. RMON_CHASSIS_STACKPORT_REMOVED A slot is reloaded in an operational chassis. The indicated stack port is online. RMON_CHASSIS_STACKPORT_ONLINE A slot is reloaded in an operational chassis. The indicated stack port is offline. RMON_CHASSIS_STACKPORT_OFFLINE When the slot is reloaded, there is a cable initialization error. RMON_CHASSIS_STACKPORT_FAILED The expansion module you have inserted is not an approved ProCurve module. See the indicated URL for more rmation about approved ProCurve modules. RMON_CHASSIS_EXP_MODULE_FAILED_HPIDV2 63

2562 Port <port-num>: PSE detected. Port PoE disabled. 2564 PoE pre-std-detect mode is enabled. Power may be applied to non-pds. Use only with legacy devices. To disable power on specific ports, use no interface <port-list> power. 2568 Slot <slot-id> Core Dump Uploading 2569 Slot <slot-id> Core Dump Upload Complete 2570 Slot <slot-id> Core Dump Upload Failed PSE = Power Sourcing Equipment. A PoE+ port is linked to a PoE port (switch-to-switch link). The port detects that the connected port is capable of providing PoE, so PoE delivery for that port is disabled. It appears as an error even though it is expected behavior for switch to switch links. If this occurs on a port that was connected to a PoE device, it might indicate a port PoE problem. To recover PoE functionality on that port without rebooting: 1.On the PoE chassis, disable PoE power (no power-overethernet [port-num]) 2.Power down the affected module (savepower module <slot>) 3.Power up the affected module (no savepower module <slot>) RMON_POEMGR_PORT_FET_BAD This message displays when the PoE pre-std-detect command is enabled on the switch. RMON_POEMGR_PRE_STD_DETECT The chassis manager is uploading a core dump. RMON_CHASSIS_CD_UPLOADING The chassis manager has finished uploading the core dump. RMON_CHASSIS_CD_UPLOAD_COMPLETE The chassis manager has failed to upload the core dump. RMON_CHASSIS_CD_UPLOAD_FAILED 2572 Vrid <vr-id> inettype <type> Vid <vlan-id> recd pkt with incorrect number of addresses. VRRP packet was received with a mismatch in the number of IP addresses. RMON_VRRP_VR_MISMATCH_VIP_CNT 2611 <subsystem> subsystem saved some internal change(s) to startup config 2612 <subsystem> subsystem save the whole running config to startup config The indicated subsystem saved some internal changes to the startup configuration file. RMON_CFG_ORIGTREE_SAVE_FLASH The indicated subsystem saved the startup config file to the running config file. RMON_CFG_FULL_SAVE_FLASH 64

2613 Inconsistent config for the subsystem <subsystem>; at least one loopback interface must exist on the System before configuring standard A loopback interface must be configured on the system. RMON_CONFIG_IPV6_ONLY_ERR 2614 Config attempt failed <err> A configuration attempt failed. RMON_CONFIG_ATTEMPT_FAILED 2615 SVLANS cannot be added to any MST instance in qinq mixed vlan mode. Inconsistent configurations have been deleted. You can t add SVLANS to an MST instance in QinQ mixed VLAN mode. The erroneous configurations are deleted. RMON_CFG_MSTP_INSTANCE_WITH_DUALMODE_SVLAN_ERR 2616 The number of IPV6 ND DAD attempts was reduced to the maximum of 255. The maximum number of ND DAD attempts is 255. RMON_CONFIG_DAD_ATTEMPTS_CHANGED 2618 Software downgrade performed from <version> to <version> 2619 A configuration file operation is already in progress. Please try again later. 2620 A corruption was found in the configuration file. The corrupted section was <section> 2621 MAC mirroring cannot be enabled. MAc Mirroring configurations have been removed. A software downgrade was performed. RMON_CFG_COMPATIBILITY_ERROR The configuration file is currently busy with an operation. RMON_CONFIG_MUTEX_ERROR There is a corrupted section in the configuration file. RMON_CFG_INFORM_CORRUPTION MAC Mirroring cannot be enabled when Distributed Trunking is enabled. MAC Mirroring configurations have been removed. RMON_CFG_LOSS_DT_MAC_MIRROR_EXCLUSIVE 2631 Server not found at <address> Info The configured server is not available. The client could not find the configured SNTP servers. RMON_SNTP_NO_SERVER 2632 Client authentication is enabled Info Client authentication is enabled. RMON_SNTP_AUTH_ENABLED 2666 <num-bits>-bits <rsa dsa> client public key <installed removed> <manager operator> access. (key-comment) 2671 Port <port-num> has been downgraded to 10/100. See www.procurve.com/ device_help/nic_up Displays the size of the RSA or DSA client public key as well as if it is being installed or removed and its access, manager or operator. RMON_SSH_CLIENTKEY The port has been changed to 10/100 mbps. RMON_FF_AUTO_DOWNGRADE 65

2672 Port <port-num> - Excessive link state transitions. 2673 port <port-num> - Port disabled by Fault-finder 2674 port <port-num> - Administrator action required to re-enable 2681 Workaround nic82566dm occurred. See www.procurve.com/ device_help/nic_update for more details. 2682 Out of band management port enabled 2683 Out of band management port disabled 2684 Drop offer from <ip-addr> of <ipaddr> because the address is already assigned to another client. 2685 Ceasing status logs for Duplicate IP offers for <duration> 2686 Drop offer from <ip-addr> of <ipaddr>; address is illegal. 2687 Ceasing illegal lease rmation logs for <duration>. There were too many link state transitions (link up and link down states) and the port is disabled. RMON_FF_LINKFLAP The port indicated has been disabled. RMON_FF_DISABLE Administrative action is needed to re-enable the indicated port. RMON_FF_ADMIN_ACTION A NIC is transmitting excessive fragments. Actions: 1. Check to see if the switch is receiving fragments by issuing walkmib etherstatsfragments from the CLI. 2. Update the NIC firmware. 3. Update the NIC driver software. 4. By default, FFI will automatically downgrade the port speed to auto-10/100 if excessive fragments have been detected on the gig port. 5. Check www. procurve.com/device_help/nic_update for more details RMON_NIC82566DM_SUCCESS Out-of-Band management port Enabled. RMON_OOBM_ENABLED Out-of-Band management port Disabled. RMON_OOBM_DISABLED The DHCP server offered an IP address that is already in used by a different client in the same VLAN. RMON_DSNOOP_BAD_IP_OFFER Status logs are not being continued. The duration can be in seconds, for example, 5s, or minutes, for example 5m. RMON_DSNOOP_BAD_IP_OFFER_SUSP DHCP snooping dropped a packet because it contained illegal lease rmation. RMON_DSNOOP_ILLEGAL_LEASE A packet was dropped because it contained illegal lease rmation. To avoid filling the log file with repeated attempts, illegal lease messages will not be logged for the specified duration. RMON_DSNOOP_ILLEGAL_LEASE_SUSP 2688 Clear Dhcp-snooping statistics DHPCP-snooping event statistics have been cleared for the indicated reason. RMON_DSNOOP_CLEAR_STATS 66

2689 Ceasing cleared dhcp-snooping event statistics 2690 Drop request from <MAC-addr> for <ip-addr> because the maxbinding limit has reached on the port <port-num>. 2691 Ceasing max-binding limit crossed packet rmation logs for <port-num>. 2692 Max-binding on port <port-num> was removed. 2693 Ceasing removed maxbinding logs for port <port-num>. 2694 Current bindings on the port <port-num> is same as maxbinding set. 2695 Ceasing current bindings on port <port-num> equals max-binding set. 2696 The port <port-num> exceeded the max-binding configured. 2697 Ceasing the port <port-num> exceeded the max-binding configured. The clearing of DHCP-snooping event log statistics has stopped. RMON_DSNOOP_CLEAR_STATS_SUSP Packets are being dropped because the max binding limit has been reached for the specified port. RMON_DSNOOP_BINDING_LIMIT_CROSSED Discontinuing max-binding limit rmation logs for the specified port. RMON_DSNOOP_BINDING_LIMIT_CROSSED_SUSP Max binding on the specified port was removed. RMON_DSNOOP_EVENT_MAXBINDING_REMOVED Discontinuing removing max binding logs for the specified port. RMON_DSNOOP_EVENT_MAXBINDING_REMOVED_SUSP Current bindings on the specified port are the same as the maxbinding set. RMON_DSNOOP_EVENT_BINDINGS_EQUALS_MAXBIND The current bindings no longer equal the max-binding set. RMON_DSNOOP_EVENT_BINDINGS_EQUALS_MAXBIND_SUSP The specified port exceeded the max-binding that is configured. RMON_DSNOOP_EVENT_MAXBIND_BELOW_BINDINGS The specified port no longer exceeds the configured max-binding. RMON_DSNOOP_EVENT_MAXBIND_BELOW_BINDINGS_SUSP 2702 ADJCHG: Neighbor with Router ID <id-num> on <interface name> moved from <old state> to <new state> <event> event determines priority A neighbor on the specified interface moved to a different state for the specified event. RMON_OSPF_ADJCHGLOG_DETAIL_MSG 2703 Neighbor with Router ID <idnum> on <interface name> moved to <new state> state - <event> 2720 DHCP REQUEST dropped for <mac-address> port <portnum>, unable to add binding; port limit reached 2721 Access was denied on VLAN <vid>, <num packets> received since last log. event determines priority A neighbor on the specified interface moved to a new state for the specified event. RMON_OSPF_ADJCHGLOG_BRIEF_MSG A dynamic binding could not be added to hardware because of a resource error; a port limit was reached on the indicated port. RMON_DIPLD_DHCP_REQUEST_DROPPED New dynamic IP lockdown violations were detected on a VLAN. The VLAN ID and packet count since the last log are provided. RMON_DIPLD_VIOLATION_ON_VLAN 67

2750 Blade <module> LEDs configured to be OFF 2751 Blade <module> LEDs configured to be ON 2752 Blade <module> PHY put to Auto Low power mode 2753 Blade s <module> PHY put to Auto Low power mode 2754 Request for savepower module <module> The module s LED s are configured to be off in savepower mode, in an operational chassis. RMON_SAVEPOWER_LEDOFF_ENABLED A module s LED s are configured to be on in normal mode, in an operational chassis. RMON_SAVEPOWER_LEDOFF_DISABLED A module s PHY are configured to Auto Low power mode in an operational chassis. RMON_SAVEPOWER_PHY_LOWPOWER_ENABLED A module s PHY are configured to normal power mode in an operational chassis. RMON_SAVEPOWER_PHY_LOWPOWER_DISABLED The indicated slot is being powered down in an operational chassis. RMON_SAVEPOWER_SLOT_ISSUED 2755 Slot <slot-num> is powered down A slot is being powered down. RMON_SAVEPOWER_SLOT_ENABLED 2756 Slot <slot-num> is powered up A slot is powered up. RMON_SAVEPOWER_SLOT_DISABLED 2757 Savepower LED time is ACTIVE The time for the LED powersave feature is active. RMON_SAVEPOWER_LEDOFF_TIMER_ACTIVE 2758 Savepower LED time is SCHEDULED The timer for the LED powersave feature is scheduled. RMON_SAVEPOWER_LEDOFF_TIMER_SCHEDULED 2759 Savepower LED timer is off The timer for the LED powersave feature expires or is canceled. RMON_SAVEPOWER_LEDOFF_TIMER_OFF 2762 Request for reload module <slot-list> 2763 Configuration removed for module in slot <slot>. 2765 Unsupported mixed power supply types (PoE & PoE+) detected in chassis 2766 Supported same power supply types (PoE or PoE+) restored in chassis 2767 Port <port-num> detected non- HPID xcvr or DAC A slot is reloaded in an operational chassis. RMON_RELOAD_SLOT_ISSUED A slot has been removed with the no module command and the entire configuration for the module has been deleted. RMON_CHASSIS_MODULE_CONFIG_REMOVED Mixed power supplies (PoE and PoE+) are present in the chassis. This is not supported. RMON_POE_MIXED_POWER_SUPPLY_CFG The same type (PoE or PoE+) of power supplies are present in the chassis. Mixed types are not supported. RMON_POE_SAME_TYPE_POWER_SUPPLY_CFG The indicated port has detected a non-hp transceiver. RMON_PPMGR_NON_HPID_XCVR 68

2768 Port <port-num> PoE power dropped. Exceeded physical classification for a PoE Type1 device. 2769 Ext Power Supply <powersupply> measured out of spec or is faulty. Please change or contact 2770 Port <port-num> EEE disabled due to Polarity Error found on the cable. Correct the polarity. 2771 Port <port-num> PoE power dropped. Exceeded physical classification due to change in classification type. LLDP is disabled at runtime and the PD was draining PoE+ power negotiated through LLDP. RMON_POE_RESTRICT_PWR_FOR_TYPE1_PD An EPS is plugged in and the software reads invalid isrc value. RMON_POEMGR_EPS_INVALID_ISRC A cable is found with paira/pairb polarity swapped. Correct the polarity. RMON_PPMGR_PORT_BAD_POLARITY LLDP is enabled at runtime and the PD was draining PoE+ power that exceed the physical classification because the classification type was changed. RMON_POE_RESTRICT_PWR_FOR_TYPE2_PD 2778 Internal power supply <pwrsupply>: Fan <fan-id> failed. 2779 Internal power supply <pwrsupply>: Output power exceeded threshold. 2780 Internal power supply <pwrsupply>: System current exceeded threshold. 2781 Internal power supply <pwrsupply>: PoE current exceeded threshold 2782 Internal power supply <pwrsupply>: Auxiliary inlet power loss. 2783 Internal power supply <pwrsupply>: System power temperature exceeded threshold. 2784 Internal power supply <pwrsupply>: POE power temperature exceeded threshold. 2785 Internal power supply <pwrsupply>: Inlet air temperature exceeded threshold. A fan on an internal power supply failed. The power supply still provides power and is not shut down. RMON_IPS_FAN_FAILURE_WARN The power supply s output has exceeded the threshold. The power supply still supplies power and is not shut down. RMON_IPS_OUTPUT_PWR_EXCEEDED_WARN The power supply s system current has exceeded the threshold. The power supply still supplies power and is not shut down. RMON_IPS_SYS_CURRENT_EXCEEDED_WARN The power supply s PoE current has exceeded the threshold. The power supply still supplies power and is not shut down. RMON_IPS_POE_CURRENT_EXCEEDED_WARN The power supply s auxiliary power inlet has lost power. The power supply still supplies power and is not shut down. RMON_IPS_AUX_INLET_PWR_LOSS_WARN The power supply s system power rail s temperature has exceeded the threshold. The power supply still supplies power and is not shut down. RMON_IPS_SYS_PWR_TEMP_EXCEEDED_WARN The power supply s system power rail s temperature has exceeded the threshold. The power supply still supplies power and is not shut down. RMON_IPS_POE_PWR_TEMP_EXCEEDED_WARN The power supply s inlet air temperature has exceeded a threshold. The power supply still supplies power and is not shut down. RMON_IPS_INLET_TEMP_EXCEEDED_WARN 69

2786 Internal power supply <pwrsupply>: System exceeded current threshold, caused shutdown. 2787 Internal power supply <pwrsupply>: System exceeded current threshold, caused shutdown. 2788 Internal power supply <pwrsupply>: System exceeded voltage threshold, caused shutdown. 2789 Internal power supply <pwrsupply>: Auxiliary POE exceeded current threshold, caused shutdown. 2790 Internal power supply <pwrsupply>: Auxiliary POE exceeded voltage threshold, caused shutdown. 2791 Internal power supply <pwrsupply>: Main POE exceeded current threshold, caused shutdown. 2792 Internal power supply <pwrsupply> : Main POE exceeded voltage threshold. Power supply has shut down. 2793 Internal power supply <pwrsupply>: Main inlet lost power. 2794 Internal power supply <pwrsupply>: High POE power temperature caused shutdown. 2795 Internal power supply <pwrsupply>: High system power temperature caused shutdown. 2796 Internal power supply has been removed. 2797 Internal power supply <pwrsupply> has lost power. The power supply s output power has exceeded a threshold. Power supply has shut down. RMON_IPS_OUTPUT_PWR_EXCEEDED_FAULT The power supply s system power current has exceeded a threshold. The power supply has shut down. RMON_IPS_SYS_CURRENT_EXCEEDED_FAULT The power supply s system power voltage has exceeded a threshold. The power supply has shut down. RMON_IPS_SYS_VOLTAGE_EXCEEDED_FAULT The power supply s auxilliary PoE power has exceeded its current threshold. The power supply has shut down. RMON_IPS_POE_AUX_CURRENT_EXCEEDED_FAULT The power supply s auxilliary PoE power has exceeded its voltage threshold. The power supply has shut down. RMON_IPS_POE_AUX_VOLTAGE_EXCEEDED_FAULT The power supply s main POE power has exceeded its current threshold. The power supply has shut down. RMON_IPS_POE_MAIN_CURRENT_EXCEEDED_FAULT The power supply s main POE power has exceeded its voltage threshold. The power supply has shut down. RMON_IPS_POE_MAIN_VOLTAGE_EXCEEDED_FAULT The power supply s main power inleg has lost power. The power supply has shut down. RMON_IPS_MAIN_INLET_PWR_LOSS_FAULT The power supply s POE power temperature is too high. The power supply has shut down. RMON_IPS_POE_TEMP_EXCEEDED_FAULT The power supply s POE temperature is too high. The power supply has shut down. RMON_IPS_SYS_TEMP_EXCEEDED_FAULT The power supply has been removed. RMON_IPS_REMOVED_FAULT The power supply has lost all power. RMON_IPS_PWR_LOSS 70

2798 Internal power supply <pwrsupply> has lost main POE power. The power supply s main POE source has lost power. RMON_IPS_POE_MAIN_PWR_LOSS_FAULT 2799 Internal power supply <pwrsupply> has lost auxiliary POE power. The power supply s auxiliary POE source has lost power. RMON_IPS_POE_AUX_PWR_LOSS_FAULT 2801 Invalid HELLO packet from <source> on interface<interface>: Invalid Hello Interval 2802 Invalid HELLO packet from <source> on interface <interface>: Invalid Router Dead Interval 2803 Invalid HELLO packet from <source> on interface <interface> : Stub/Transit area option 2804 Invalid DD packet from <source> on interface <interface>: MTU too large: expected <size> 2805 Invalid DD packet from <source> on interface <interface>: No such neighbor 2806 Invalid LSR packet from <source> on interface <interface>: No such neighbor 2807 Invalid LSU packet from <source> on interface <interface>: No such neighbor 2808 Invalid LSA packet from <source> on interface <interface>: No such neighbor 2809 Neighbor <neighbor> on interface <interface> moved to <state> state to <state> state 2810 Neighbor <neighbor> on interface <interface> moved from <state> state to <state> state none none none none none none none none none none Hello interval mismatch in Hello packet. RMON_OSPF3_ADJCHG_DETAIL_HELLO_HELLOINTERVAL Dead Interval mismatch in Hello packet. RMON_OSPF3_ADJCHG_DETAIL_HELLO_DEADINTERVAL Option mismatch in Hello packet. RMON_OSPF3_ADJCHG_DETAIL_HELLO_OPTIONS MTU mismatch in DD packet. RMON_OSPF3_ADJCHG_DETAIL_DD_MTU Invalid neighbor in DD packet. RMON_OSPF3_ADJCHG_DETAIL_DD_NEIGHBOR Invalid neighbor in LSR packet. RMON_OSPF3_ADJCHG_DETAIL_LSR_NEIGHBOR Invalid neighbor in LSU packet. RMON_OSPF3_ADJCHG_DETAIL_LSU_NEIGHBOR Invalid neighbor in LSA packet. RMON_OSPF3_ADJCHG_DETAIL_LSA_NEIGHBOR A brief log message for adjacency state transition. RMON_OSPF3_ADJCHG_BRIEF_MESSAGE A detailed log message for adjacency state transition. RMON_OSPF3_ADJCHG_DETAIL_MESSAGE 71

2811 Discarding <packet> packet from <source> on interface <interface> at <state> state 2812 Invalid router priority configuration on interface <interface> 2813 Too many neighbors for HELLO packet on interface <interface> none none none A packet is dropped. RMON_OSPF3_ADJCHG_DETAIL_WRONG_PACKET There is an invalid router priority configuration. RMON_OSPF3_ADJCHG_DETAIL_INVALID_PRIORITY There are too many neighbors for the OSPF3 packet. RMON_OSPF3_ADJCHG_TOO_MANY_NEIGHBORS 2814 Invalid event at <state> state none There is an invalid OSPF3 event. RMON_OSPF3_ADJCHG_DETAIL_INVALID_EVENT 2815 Router ID is not defined. OSPFv3 is not enabled. none The router ID is not defined. RMON_OSPF3_INIT_NO_ROUTERID 2816 Failed to get socket none A socket cannot be created. RMON_OSPF3_INIT_SOCKET 2817 Failed to set receive buffer size to <size> 2818 Failed to set send buffer size to <size> 2819 Failed to set receive destination address none none none The receive buffer size cannot be set. RMON_OSPF3_INIT_RECV_BUFFER_SIZE The send buffer size cannot be set. RMON_OSPF3_INIT_SEND_BUFFER_SIZE The receive destination address cannot be set. RMON_OSPF3_INIT_RECV_DEST_ADDRESS 2820 Failed to set receive interface none The receive interface cannot be set. RMON_OSPF3_INIT_RECV_INTERFACE 2821 Failed to set receive hoplimit none The receive hoplimit cannot be set. RMON_OSPF3_INIT_RECV_HOP_LIMIT 2822 Failed to set outgoing multicast hoplimit to 1 none The outgoing multicast hoplimit cannot be set to 1. RMON_OSPF3_INIT_OUT_MULTICAST_HOP_LIMIT 2823 Discarding <packet> packet from <source> on interface <interface>: Receive queue full none The receiving queue is full so the packet is dropped. RMON_OSPF3_RECV_QUEUE_FULL 2824 Failed to join multicast group <group> on interface <interface> none The multicast group was not joined. RMON_OSPF3_INTF_ROUTER_MULTICAST_GROUP 2825 Failed to send virtual link packet: Non-linklocal address is not configured 2826 Failed to set multicast on interface <interface> 2827 Discarding packet on interface <interface> none none none A non link-local address must be configured before the virtual packet is sent. RMON_OSPF3_SEND_NON_LINK_LOCAL_ADDRESS Multicast was not set on the specified interface. RMON_OSPF3_INTF_FAILED_MULTICAST A packet is discarded on the specified interface. RMON_OSPF3_RECV_DISCARDING_PACKET 72

2828 Discarding packet on interface<interface>: Received frame size <size> is less than OSPFv3 header size 2829 Discarding packet on interface <interface>: Header length <length> is not equal to kernel read length 2830 OSPFv3 instance mismatch on interface <interface>, expected <instance>, received <instance> 2831 Discarding packet on interface <interface>: Mandatory zero field(s) not zero. 2832 Discarding packet on interface <interface>: Protocol version mismatch: expect <version> 2833 Discarding packet on interface <interface> : Unknown packet type <type> 2834 Discarding packet on interface <interface>: Duplicate router-id: router id <id> same 2835 Discarding packet on interface <interface>: Invalid IPv6 hop limit: expect <limit>, received <limit> 2836 Discarding LSA on interface <interface>, lsid <lsid>: LSA type <type> 2837 Invalid grace LSA on interface <interface>: Option length mismatch 2838 Invalid Grace LSA on interface <interface>: Invalid Grace Period TLV length 2839 Invalid Grace LSA on interface <interface>: Grace period TLV missing none none none none none none none none none none none none The received frame size is less than the OSFv3 packet header size. RMON_OSPF3_RECV_SMALL_FRAME The packet header length is not equal to the kernel read length so the packet is discarded. RMON_OSPF3_RECV_KERNEL_READ_LENGTH There is an OSPFv3 instance mismatch. RMON_OSPF3_RECV_O3INSTANCE_MISMATCH The packet is ignored because fields that must be zero are not zero. RMON_OSPF3_RECV_MANDATORY_ZERO_FIELD There is a protocol version mismatch so the packet is ignored. RMON_OSPF3_RECV_PROTOCOL_VERSION The packet type is unknown so the packet is ignored. RMON_OSPF3_RECV_UNKNOWN_PACKET There is a duplicate router-id so the packet is ignored. RMON_OSPF3_RECV_DUPLICATE_ROUTER_ID There is an invalid IPv6 hop limit so the packet is ignored. RMON_OSPF3_RECV_INVALID_IPV6_HOPLIMIT The LSA is discarded. RMON_OSPF3_RECV_DISCARDING_LSA The grace LSA is invalid due to an option length mismatch. RMON_OSPF3_RESTART_OPTION_LENGTH_MISMATCH The grace period TLV is invalid, so the grace LSA is invalid. RMON_OSPF3_RESTART_GRACE_PERIOD_TLV_LENGTH The grace period TLV is missing, to the Grace LSA is invalid. RMON_OSPF3_RESTART_GRACE_PERIOD_TLV_MISSING 73

2840 Invalid Grace LSA on interface <interface>: Invalid Restart Reason TLV length 2841 Invalid Grace LSA on interface<interface>: Restart Reason TLV missing 2842 Invalid Grace LSA on interface<interface>: Unknown restart reason <reason> 2843 Failed to find local interface for nexthop <next hop> 2844 Restart will not happen. Grace Period already expired 2845 Configured Hello Interval <numsecs> seconds on virtual interface <int> is greater than config. none none none none none The grace LSA is invalid because the TLV length is incorrect. RMON_OSPF3_RESTART_REASON_TLV_LENGTH The grace LSA is invalid because the TLV is missing. RMON_OSPF3_RESTART_REASON_TLV_MISSING The grace LSA is invalid for an unknown restart reason. RMON_OSPF3_RESTART_UNKNOWN_REASON The local interface for the next hop can t be found. RMON_OSPF3_SPF_NO_NEXTHOP_INTERFACE The grace period expired, so the restart will not occur. RMON_OSPF3_RESTART_GRACE_PERIOD_EXPIRED The configured hello interval indicated is invalid. RMON_OSPF3_INVALID_HELLO_INTERVAL 2846 Configured Dead Interval <numsecs> seconds on virtual interface <int> is less than config The configured Dead Interval indicated is invalid. RMON_OSPF3_INVALID_DEAD_INTERVAL 2847 Entering graceful helper mode for neighbor <neighbor> 2848 Exiting helper mode for neighbor <neighbor> 3001 System reboot due to Power Failure 3002 System reboot due to Switch Reset 3003 Configuration hash calculation started. 3004 Configuration hash calculation finished 3005 Max hop count <count> reached for a <type> type stack packet. 3006 Unknown stacking packet type <type> Entering graceful helper mode for the indicated neighbor. RMON_OSPF3_RESTART_ENTER_HELPER_MOFE Exiting helper mode for the indicated neighbor. RMON_OSPF3_RESTART_EXIT_HELPER_MODE Appears when switch reboots due to a power failure. RMON_POWER_FAILURE_REBOOT The switch performs a soft reboot when boot system flash <primary secondary> is executed. RMON_RESET_ SWITCH_REBOOT The hash generation for the running configuration has started. RMON_SYSTEM_HASH_CALC_START The hash generation for the running configuration is finished. RMON_SYSTEM_HASH_CALC_FINISH The maximum hop count for a packet type has been reached. RMON_PRO_STACK_MAX_HOP_COUNT An unknown packet type has been received. RMON_PRO_STACK_UNKNOWN_PKT_TYPE 3007 Stack port cable looped back on ports <port-num> to <port-num> The stack cable is looped back to the same switch. RMON_PRO_STACK_LOOPBACKED 74

3008 Stack bndry mbr <port-num> port <port-num> other stack id <address> 3009 MAX stack switches exits cannot add switch <address> 3010 Received <packet> from unknown member <address> 3011 Received <packet> from unknown member number <number> 3012 Unable to open/create <filename> 3013 Unable parse <line> in <filename> 3014 Unable write <data> to <filename> The stack cable is looped back to the same switch. RMON_PRO_STACK_BOUNDARY_FOUND If this switch is added, the maximum number of switches allowed in the stack will be exceeded. RMON_PRO_STACK_MAX_SWITCHES_EXCEEDED A packet was received from an unknown stack member. RMON_PRO_STACK_UNKNOWN_MEMBER A packet was received from an unknown stack member using the member number as a key. RMON_PRO_STACK_UNKNOWN_MEMBER_NUM The stack.dat file could not be created or opened. RMON_PRO_STACK_STACKFILE_ERROR A line in the stack.dat file could not be parsed. RMON_PRO_STACK_STACKFILE_PARSE_ERROR The stack.dat could not be written to. RMON_PRO_STACK_STACKFILE_WRITE_ERROR 3015 Reboot of <address> <status> Indicates the status of a reboot request. RMON_PRO_STACK_REBOOT_STATUS 3016 <switch> switch with Member ID <id>, removed due to <status> 3031 Failed to join multicast group <group> on interface <interface>: <reason> event determines priority Indicates the status of a reboot request. RMON_PRO_STACK_MEMBER_LOST Router failed to join the multicast group. RMON_OSPF_INTF_ROUTER_MULTICAST_GROUP 3051 BGP configured, AS <network> BGP is configured for the indicated Autonomous System. RMON_BGP_CONFIGURED 3052 BGP un-configured BGP is unconfigured. RMON_BGP_UNCONFIGURED 3053 BGP disabled BGP is disabled. RMON_BGP_ADMIN_DISABLE 3054 BGP enabled BGP is enabled. RMON_BGP_ADMIN_ENABLE 3055 BGP route count exceeds maximum allowed prefix limit - <num> routes. The BGP route count exceeds the maximum allowed routes. RMON_BGP_EXCEED_MAXPREFIX 75

3056 BGP route count falls below maximum allowed prefix limit - <num> routes. The BGP route count has fallen below the maximum allowed. RMON_BGP_FALLBELOW_MAXPREFIX 3057 BGP router-id changed. The BGP router ID has changed. RMON_BGP_ROUTERID_CHANGED 3058 Router-id on device changed, this affects BGP. A router ID changed, affecting BGP. RMON_BGP_GLOBAL_ROUTERID_CHANGED 3071 <peer>: Peer configured, AS <network> A BGP peer is configured. RMON_BGP_PEER_CONFIGURED 3072 <peer>: Peer up The BGP peer is up. RMON_BGP_PEER_UP 3073 <peer>: Peer down The BGP peer is down. RMON_BGP_PEER_DOWN 3074 <ip-addr>: NOTIFICATION Recv - <ip-addr> 3075 <ip-addr>: NOTIFICATION Send - <ip-addr> BGP peer notification is received. RMON_BGP_PEER_NOTIFICATION_RECV BGP peer notification is sent. RMON_BGP_PEER_NOTIFICATION_SEND 3076 <peer>: User reset request There was a user reset request. RMON_BGP_PEER_USER_RESET_REQUEST 3077 <peer>: Peer timeout A peer timed out. RMON_BGP_PEER_TIMEOUT 3078 <peer>: Peer password changed The peer s password has changed. RMON_BGP_PEER_PASSWORD_CHANGED 3079 <peer>: Peer deleted The peer has been deleted. RMON_BGP_PEER_DELETED 3080 <peer>: Peer disabled The peer has been disabled. RMON_BGP_PEER_ADMIN_DISABLE 3081 <peer>: Peer enabled The peer has been enabled. RMON_BGP_PEER_ADMIN_ENABLE 3082 <peer>: BGP route count from peer exceeded maximum allowable prefix limit of <num>. 3083 <peer>: Peer interface <num> is down 3084 <peer>: Peer interface <num> is up The BGP route count from the BGP peer has exceeded the maximum allowable prefix limit. RMON_BGP_PEER_EXCEED_MAXPREFIX The indicated BGP peer interface is down. RMON_BGP_PEER_INTERFACE_DOWN The indicated BGP peer interface is up. RMON_BGP_PEER_INTERFACE_UP 76

3085 <peer>: Peer remote-as changed to <AS> 3086 <peer>: Peer local-as changed to <AS> 3087 <peer>: Peer source-address changed to <address> 3088 <peer>: Capabilities announced to peer changed - <ip-addr> 3089 <peer>: Peer ignore-lead-as configuration changed 3090 <peer>: Peer remove-privateas configuration change 3091 <peer>: BGP Identifier sent by Peer <ip-addr> matches ours. BGP session may not establish The AS of the remote peer is changed. RMON_BGP_PEER_REMOTEAS_CHANGED The AS of the local peer is changed. RMON_BGP_PEER_LOCALAS_CHANGED The BGP peer source address has changed to the indicated address. RMON_BGP_PEER_SRCADDR_CHANGED The BGP peer capabilities changed. RMON_BGP_PEER_CAPANNOUNCED_CHANGED The BGP peer ignore-lead-as configuration has changed. RMON_BGP_PEER_IGNLEADAS_CHANGED The BGP remove-private-as configuration has changed. RMON_BGP_PEER_REMOVEPRIAS_CHANGED The BGP identifier sent by the peer matches an existing identifier and the BGP session may not be established. RMON_BGP_PEER_SAME_ROUTERID 3121 SPF computation started at <time>: current SPF interval is set to <time> 3122 SPF will be scheduled after <seconds> seconds: last SPF computed at <time> none none Shortest Path First computation started at indicated time. Traces the time stamp when SPF is run. RMON_OSPF_SPF_THROTTLE_COMPUTED SPF is scheduled after the indicated number of seconds. Traces the time stamp when the SPF timer is triggered. RMON_OSPF_SPF_THROTTLE_SCHEDULED 3125 new Startup Config Seq Num= <num> by <num> There is a new startup configuration file sequence number. RMON_STARTUP_CONFIG_CHANGED 3132 Discarding invalid packet: <packet> 3133 Packet received on interface <port-num> has its MD5 key expired. 3134 Discarding Invalid Hello packet on interface <interface-name>: <reason> event determines priority event determines priority event determines priority An invalid packet was received and discarded. RMON_OSPF_RECV_INVALID_PACKET The MD5 key expired. The life of the last acceptable key is being extended. RMON_OSPF_RECV_MD5_KEY_EXPIRED An invalid Hello packet was discarded on the specified interface. RMON_OSPF_ADJCHG_DETAIL_HELLO_PACKET_PROCESSING 77

3135 Discarding invalid DD packet on interface <port-num>: <reason> 3136 Discarding invalid LSR packet on interface <port-num>: <reason> 3137 Discarding invalid LSU packet on interface <port-num>: <reason> 3138 Discarding invalid LSA packet on interface <port-num>: <reason> event determines priority event determines priority event determines priority event determines priority An invalid DD packet was discarded on the specified port. RMON_OSPF_ADJCHG_DETAIL_DD_PACKET_PROCESSING An invalid LSR packet was discarded on the specified port. RMON_OSPF_ADJCHG_DETAIL_LSR_PACKET_PROCESSING An invalid LSU packet was discarded on the specified port. RMON_OSPF_ADJCHG_DETAIL_LSU_PACKET_PROCESSING An invalid LSA packet was discarded on the specified port. RMON_OSPF_ADJCHG_DETAIL_LSA_PACKET_PROCESSING 3139 Failed to get a RAW socket. event determines priority Unable to obtain a RAW socket. RMON_OSPF_INSTANCE_INIT_SOCKET 3140 Failed to set SIGIO on the socket, using normal I/O 3141 Failed to set receive buffer size to <max packet> 3142 Failed to set transmit buffer to <max packet> event determines priority event determines priority event determines priority The SIGIO could not be set on the socket. Normal I/O will be used. RMON_OSPF_INSTANCE_INIT_SIGIO The receive buffer size could not be set. RMON_OSPF_INSTANCE_INIT_REV_BUFFER_SIZE The transmit buffer size could not be set. RMON_OSPF_INSTANCE_INIT_TRANSMIT_BUFFER_SIZE 3143 Failed to set receive interface event determines priority The incoming interface index was requested, but not obtained. RMON_OSPF_INSTANCE_INIT_RECV_IFINDEX_SIZE 3144 Restart will not happen. Grace Period already expired event determines priority The graceful restart period expired. Restart will not occur. RMON_OSPF_INSTANCE_INIT_PLANNED_GRACEFUL_RESTART_EXPIRED 3145 Invalid Grace LSA on interface <interface name>: Option length mismatch event determines priority There is an invalid Grace LSA option length mismatch. RMON_OSPF_RESTART_GRACE_LSA_LENGTH 3146 Invalid Grace LSA on interface <interface name>. Grace Period TLV length <TLV length> event determines priority There is an invalid Grace LSA grace period on the specified interface. RMON_OSPF_RESTART_GRACE_LSA_GRACE_PERIOD 3147 Invalid Grace LSA on interface <interface-name>: Grace period TLV missing 3148 Invalid Grace LSA on interface <interface name>: Invalid Restart Reason TLV length event determines priority event determines priority The Grace period TLV is missing, causing an invalid Grace LSA on the specified port. RMON_OSPF_RESTART_GRACE_LSA_NO_GRACE_PERIOD Invalid Grace LSA restart reason is TLV length. RMON_OSPF_RESTART_GRACE_LSA_RESTART_REASON 78

3149 Invalid Grace LSA on interface <interface name>: Restart Reason TLV missing 3150 Invalid Grace LSA on interface <interface name>: Invalid interface Addr TLV length 3151 Invalid Grace LSA on interface <interface name>: Interface Addr TLV missing 3152 Invalid Grace LSA on interface <interface name>: Unknown restart reason 3153 Planned restart failed as network is changing 3154 Discarding received LSU packet on interface <interface name> Bad LSA length <length> 3155 Discarding received LSU on interface <interface name: Bad LSA checksum, LSA: <checksum> 3156 Discarding received LSA packet on interface <interface name>: Invalid type of LSA 3157 Invalid router priority configuration on interface <interface name>. No DR elected. 3158 Invalid event <event> at <state> state event determines priority event determines priority event determines priority event determines priority event determines priority event determines priority event determines priority event determines priority event determines priority event determines priority The TLV is missing so the Grace LSA is invalid. RMON_OSPF_RESTART_GRACE_LSA_RESTART_REASON_TLV The interface address length is incorrect so the Grace LSA is invalid. RMON_OSPF_RESTART_GRACE_LSA_RESTART_REASON_ADDR There is no interface address TLV so the Grace LSA is invalid. RMON_OSPF_RESTART_GRACE_LSA_INTERFACE_ADDR_TLV There is invalid Grace LSA with an unknown restart reason. RMON_OSPF_RESTART_GRACE_LSA_UNKNOWN_RESTART_REASON The planned restart failed because the network is changing. RMON_OSPF_RESTART_ATTEMPTED_WHEN_NW_CHANGING The LSA length was bad so the LSU packet was discarded. RMON_OSPF_RECV_LSA_LENGTH There was a bad receive LSA checksum. RMON_OSPF_RECV_LSA_CHECKSUM There was an invalid type of LSA so the received packet was discarded. RMON_OSPF_RECV_LSA_INVALID There is an invalid configuration because no DR was selected. RMON_OSPF_ADJCHG_DETAIL_INVALID_PRIORITY An invalid state event was received. RMON_OSPF_ADJCHG_DETAIL_INVALID_EVENT 3159 UFD - Enabled globally UFD is enabled globally. RMON_UFD_ENABLED 3160 UFD - Disabled globally UFD is disabled globally. RMON_UFD_DISABLED 316 1 UFD - Link to monitor down The UFD link to the monitor is down. RMON_UFD_LTM_LINK_DOWN 3162 UFD - LtD Auto-Disabled The LtD has been automatically disabled. RMON_UFD_LTD_AUTO_DISABLED 79

3163 UFD - Link to Monitor Up and LtD auto-enabled 3164 Track ID <id num>: LACP conflict! If dynamic LACP trunks were monitored with the lacp-key between <1-key num> or <num - 65535>. The UFD link to the monitor is up and the LtD is auto-enabled. RMON_UFD_LTD_AUTO_ENABLED There is an LACP key conflict. RMON_UFD_LTM_STATIC_LACP_RANGE 3166 Attempting unplanned restart. Grace period: <time-period> grace time: <time-period> 3167 Entering graceful helper mode for <router-id of neighbor> on <area-id> 3168 exiting helper mode for ngb <neighbor> none none none An unplanned switch restart is attempted. RMON_OSPF_UNPLANNED_RESTART_STARTED Entering helper mode for the indicated OSPF neighbor on the indicated OSPF area. RMON_OSPF_RESTART_ENTER_HELPER_MODE Exiting helper mode for the specified neighbor. RMON_OSPF_RESTART_EXIT_HELPER_MODE 3170 Authentication rmation missing for <type of message> reply message on VLAN <vid> 3171 Authentication failed for <type of message> reply message on VLAN <vid> 3172 Replay detection failed for <type of message> reply message on VLAN <vid> 3173 Received invalid authentication option for <type of message> reply message on VLAN <vid> 3174 Send too many Decline messages on vid <vid>. Retrying server selection after <num-min> minutes. The authentication rmation is missing for the indicated reply message on the VLAN. RMON_DHCPV6C_AUTH_NO_SRVR_AVAILABLE The authentication failed for the specified type of message on the specified VLAN. The types of messages include solicit, request, confirm, renew, rebind, and release. RMON_DHCPV6C_AUTH_HMAC_FAILURE Replay detection failed on the specified VLAN. The types of messages include solicit, request, confirm, renew, rebind, and release. RMON_DHCPV6C_AUTH_RDCHECK_FAILURE An invalid authentication option was received on the specified VLAN. The types of messages include solicit, request, confirm, renew, rebind, and release. RMON_DHCPV6C_AUTH_INVALID_MESSAGE Too many Decline messages were sent on the VLAN. Will retry the server selection after the indicated number of minutes. RMON_DHCPV6C_REACHED_DECLINE_MSG_MAX 3175-3206 unused 80

3207 <auth-type> client max dynamic port-access settings arbitration error, MAC <mac-addr> port <port-num> 3210 <num> client max dynamic portaccess settings arbitration error, MAC <mac-num> port <portnum> 3211 Illegal combination of attributes <attribute> and <attribute> in received RADIUS packet on port <port-num> 3212 Conflict between Configuration and attribute <attribute> received in RADIUS packet on port <port-num> 3213 Illegal value of attribute <attribute> received for authentication type <auth-type> There is an error in applying the dynamic port-access settings for the specified auth client for the particular auth mode. RMON_DCA_APPLY_DYN_PA_SETTINGS_ERROR There is an error in applying the dyn port-access settings for the particular auth client for the particular auth mode. RMON_DCA_APPLY_DYN_PA_SETTINGS_ERROR There is an illegal combination of dyn port-access attributes for the particular auth client for the specified auth mode. RMON_DCA_ILLEGAL_VSA_COMBINATION There is an illegal combination between the dyn port-access and the configuration tree setting. RMON_DCA_CNFIG_VSA_CONFLICT An illegal value for the specified attribute was received for the indicated authentication type. RMON_DCA_ILLEGAL_VSA_VLAUE 3220 An ARP reply packet was received from <hdware-addr of sender> for <ip-addr>, an existing static ARP entry 3225 Switch-interconnect link is down. Primary is up and running so disabled all DT ports on Secondary 3226 Switch-interconnect link is up. Primary has gone down, enabling all DT ports on Secondary. 3227 Peer keep-alive link not configured An ARP reply packet was received from the sender for an existing static ARP entry. RMON_NETINET_ARP_STATIC_EXISTS The ISC link is down. If a peer-keepalive packet is received, all the DT ports are disabled. RMON_DIST_TRUNK_KEEPALIVE_RECEIVED The ISC link is up. A DT keepalive timeout has been received, all DT ports are enabled. RMON_DIST_TRUNK_KEEPALIVE_TIMEOUT The peer-keepalive link is not configured. RMON_DT_NO_KEEPALIVE_CONFIG 3228 Peer keep-alive link is down The keep-alive link is down. Enable DT ports on Secondary. RMON_DT_KEEPALIVE_DOWN 3229 Peer keep-alive send is successful The peer-keepalive link is down. Enable DT ports on Secondary. RMON_DT_KEEPALIVE_SEND_SUCCESS 3230 Peer keep-alive send failed The peer-keepalive link is down. Enable DT ports on Secondary. RMON_DT_KEEPALIVE_SEND_FAIL 3231 Received keep-alive message from peer DT switch The keep-alive link is down. Enable DT ports on Secondary. RMON_DT_KEEPALIVE_RECV_SUCCESS 81

3232 Switch role is Primary A keep-alive packet was received. This switch is selected as Primary. Traffic continues to be forwarded on DT ports. RMON_DT_SWITCH_ROLE_PRIMARY 3233 Switch role is Secondary, disabling all DT trunks 3234 Failed to receive keep-alive messages from peer DT switch A keep-alive packet was received. This switch is selected as Secondary; the DT ports are disabled. RMON_DT_SWITCH_ROLE_SECONDARY A keep-alive timeout occurred. DT ports on Secondary are enabled. RMON_DT_KEEPALIVE_TIMEOUT 3235 Enabling all DT trunks The DT ports are enabled when the ISC is up or a keepalive timeout occurs. RMON_DT_ENABLE_TRUNKS 3250 Received stacking packet with incompatible version 3251 Stack port cable looped back between ports <num> and <num> 3252 Switch with stack ID <id> cannot join stack 3253 Maximum number of switches in the stack has been reached. Cannot add <switch-id>. A packet was received with a different proto version. RMON_PRO_STACK_INCOMPATIBLE_VER The stack cable is looped back to the same switch. RMON_PRO_STACK_LOOPBACKED The stack cable is looped back to the same switch. RMON_PRO_STACK_BOUNDARY_FOUND This switch cannot be added as the maximum number of switches allowed in the stack has been reached. RMON_PRO_STACK_MAX_SWITCHES_EXCEEDED 3254 Reboot of <switch-id> Indicates the status of a boot request. RMON_PRO_STACK_REBOOT_STATUS 3255 <switch-id> switch with Member ID <id> removed due to <reason> Indicates a stack member was removed for the specified reason. RMON_PRO_STACK_MEMBER_LOST 3256 The switch software version doesn t match the version on the stack commander A stack member has an incorrect software version and has to reboot. RMON_PRO_STACK_MEMBER_SW_MISMATCH 3257 Member booted A stack member has booted. RMON_PRO_STACK_BOOT_COMPLETE 3258 Member active A stack member is active. RMON_PRO_STACK_MOD_ACTIVE 3259 Member failed because synchronization failed 3260 Member went down: <memberid> A stack member failed synchronization. RMON_PRO_STACK_FAILED_SYNC A stack member crashed. RMON_PRO_STACK_BOOT_CRASH_RECORD0 82

3261 Crash : <reason> Indicates the reason for the crash. RMON_PRO_STACK_BOOT_CRASH_RECORD1 3262 Lost Communication with Member <member-id> Communication is lost with a stack member. RMON_PRO_STACK_LOST_COMM 3263 Resetting member A stack member is resetting. RMON_PRO_STACK_RESET 3264 Failover occurred A failover occurred. RMON_PRO_STACK_FAILOVER 3265 User initiated switchover occurred A user-initiated switchover occurred. RMON_PRO_STACK_SWITCHOVER 3266 Shutting down member A stack member is being shut down. RMON_PRO_STACK_SHUTDOWN 3267 Topology is a <topology-type> There is an unsupported topology. RMON_PRO_STACK_WARN_TOPOLOGY_TYPE 3268 Topology is a <topology-type> Indicates the current topology. RMON_PRO_STACK_TOPOLOGY_TYPE 3269 Stack <state> Indicates the stack state. RMON_PRO_STACK_STATE 3270 Member <member-id> with mac <MAC-addr> was deleted so missing member could be added 3271 Member <member-id> with mac <MAC-addr> was replaced so missing member could be added 3272 <switch-id> switch with Member ID <id> removed due to user request 3273 <switch-id> switch with Member ID <id> removed A stacking member was deleted from the configuration to make room for a missing member. RMON_PRO_STACK_FORCE_MEMBER_CFG_DELETE A stacking member in the configuration was updated with a new MAC address so a missing member could be added. RMON_PRO_STACK_FORCE_MEMBER_CFG_REPLACE A member switch has been removed from the stack due to a user request. RMON_PRO_STACK_MEMBER_REMOVED_USER_REQUEST A stack member has been removed. RMON_PRO_STACK_MEMBER_REMOVED 3274 Member <id> cannot join stack due to incorrect product id: <id> A member was not allowed to join the stack due to a mismatched product id (J-number). RMON_PRO_STACK_MISMATCHED_PRODUCT_ID 3275 Member <id> elected as commander. Reason: <reason> 3276 Member <id> chosen as standby. Reason: <reason> 3277 Ignoring Member <member-id>: unsupported topology Provides the reason this member won the commander election. RMON_PRO_STACK_CMDR_WIN_REASON Provides the reason this member won the standby election. RMON_PRO_STACK_STBY_WIN_REASON An unsupported topology exists. RMON_PRO_STACK_UNSUPPORTED_TOPOLOGY 83

3305 ISC port <port-num> is deleted from keepalive VLAN <vid> 3306 Trunk type mismatch detected on <trunk, disabling <trunk> 3307 Keepalive mis-configuration detected. Reconfigure the keepalive VLAN ISC port will be deleted from a VLAN when the VLAN is configured as a keepalive VLAN. RMON_DT_ISC_DELETED_FROM_VLAN The hello packet indicates that the peer trunk is a different type. RMON_DT_TRUNK_TYPE_MISMATCH The keepalive VLAN is misconfigured. RMON_DT_KEEPALIVE_MIS_CONFIG 3350 Unable to permit client, no available MAC-based VLAN entries, MAC <mac-num>, port <port-num> 3351 Invalid port-speed <portspeed>received in HP-PORT- SPEED VSA for client <client> on port 3352 port-speed VSA not applied for client <client> on port <portnum> as dynamic port-speed 3353 Multiple clients on port <portnum> Port-speed is set to portspeed VSA received 3354 There are existing clients on port <port-num>. Port-speed VSA not applied for client. 3355 Port <port-num> does not support the port-speed <portspeed> received in HP-PORT- SPEED VSA 3360 Cert Prov Initialization failed <type of failure) r All MAC-based VLAN resources have been exhausted. RMON_DCA_MBV_TABLE_FULL An invalid port speed has been received. RMON_DCA_INVALID_SPEED The port does not support the port-speed received in the VSA. The port-speed feature is not enabled. RMON_DCA_SPEED_VSA_NOT_ENABLED The port can honor only the port-speed received from the first client. RMON_DCA_WITHOUT_SPEED_VSA The port can honor only the port-speed received from the first client. RMON_DCA_MULTIPLE_CLIENTS The port cannot honor the port-speed received from the first client. RMON_DCA_SPEED_NOT_SUPPORTED Either the creation of a directory or the initialization of a data structure failed in the indicated way. RMON_HPESP_CERT_INIT_ERROR 3361 Interface Module image id <idnum> corrupted The slave image loaded during chassis bootup is corrupt. Either the source is corrupt or the image was corrupted during the copy process. RMON_CHASSIS_DNLD_SLAVEIMAGE_CORRUPTED 84

3362 Hostname must contain only letters, numbers, and hyphens, and must not start with a hyphen or end with a hyphen. RFC for protocols mandates that component hostname labels may contain only the ASCII letters a through z (in a case-sensitive manner), the digits 0 through 9, and the hyphen (-). RFC 1123 permits hostname labels to start with digits, but not hyphens. No other symbols, punctuation characters, or blank spaces are permitted. RMON_SYSTEM_HOSTNAME_INVALID 3362 User <user> login from <source> Authenticated user login. RMON_AUTH_USER_LOGIN 3363 User <user> logout Authenticated user logout. RMON_AUTH_USER_LOGOUT 3364 Last login file access error <error> An unexpected error is returned from the file access function, which should never occur. It asserts in QA mode. RMON_AUTH_LAST_LOGIN_FILE_ERROR 3365 Creating user last login file The initial creation of the user last login file. RMON_AUTH_LAST_LOGIN_FILE_CREATE 3366 Corrupt or incompatible user last login file, recreating. The last user login file was corrupt and is being recreated. RMON_AUTH_LAST_LOGIN_FILE_RECREATE 3367 Clearing user last login file Use the clear last-login command to clear the user last login file. RMON_AUTH_LAST_LOGIN_FILE_CLEAR 3368 User last login table is full, replacing oldest user <user>. 3369 User <user> from <location> is locked out for <num> seconds. 3370 TBD 3371 Switch admin approved the application <app> 3372 Switch admin denied the application <app> 3373 Authorization Approve Fail: revoke certificate prior to new approval 3374 Switch admin revoked access authorization for application <app> The last login table is full and the oldest entry is being replaced. RMON_AUTH_LAST_LOGIN_TABLE_FULL The user plus the IP address is newly locked out. RMON_AUTH_RECENT_LOGIN_USER_LOCKOUT Indicates the creation of a directory or the initialization of data structures. RMON_HPESP_CERT_APPROVED Indicates the creation of a directory or initialization of a data structure failed. RMON_HPESP_CERT_DENIED Unable to create a new cert entry, too many certs, delete one before adding another. Indicates that the creation of a directory or the initialization of a data structure failed. RMON_HPESP_CERT_CREATE_FAIL Access authorization for the indicated application was revoked. RMON_HPESP_CERT_REVOKE 85

3375 <%s> does not have a valid entry The hash of the UUID grant date chassis MAC does not match with the cert entry. RMON_HPESP_CERT_INVALID_ENTRY 3376 A new APP request has been received This is a log message about a received request on the HPesp Sys connection. RMON_HPESP_CERT_CSR_RECV 3385 Unknown users from <location> are locked out for <num> seconds. An unknown user plus the IP address is locked out. RMON_AUTH_RECENT_LOGIN_UNKNOWN_LOCKOUT 3400 Function <function> started selftest 3401 Function <function) passed selftest 3402 Function <function> failed selftest 3403 Attempted to install certificate of unsupported file format. 3404 OpenFlow TLS authentication failure 3405 Trust Anchor Profile <profile> created. 3406 Trust Anchor Profile <profile> removed. Selftest for the indicated function is started. RMON_CRYPTO_SELFTEST_START The indicated function passed selftest. RMON_CRYPTO_SELFTEST_PASSED The indicated function failed selftest. RMON_CRYPTO_SELFTEST_FAILED An attempt was made to install a certificate of an unsupported file format. RMON_CRYPTO_CERTMGR_CERT_UNSUP_FORMAT TLS authentication failure has occurred. RMON_CRYPTO_CERTMGR_CONN_DENIED The indicated Trust Anchor Profile was created. RMON_CRYPTO_CERTMGR_TA_PROF_CREATED The indicated Trust Anchor Profile was removed. RMON_CRYPTO_CERTMGR_TA_PROF_DELETED 3407 Identity Profile <profile> created. The indicated Identity Profile was created. RMON_CRYPTO_CERTMGR_ID-PROF-CREATED 3408 Identity Profile <profile> removed. 3409 Trust Anchor Root Certificate installed on Trust Anchor. 3410 Self-signed certificate <cert> installed on Trust Anchor. Profile <profile> for usage <usage>. The indicated Identity Profile was removed. RMON_CRYPTO_CERTMGR_ID_PROF_DELETED The Trust Anchor Root Certificate has been installed on the Trust Anchor. RMON_CRYPTO_CERTMGR_TA_CERT_INSTALLED The specified self-signed certificate has been installed on the Trust Anchor with the indicated profile and usage. RMON_CRYPTO_CERTMGR_SS_CERT_INSTALLED 86

3412 CA-signed certificate <cert> installed on Trust Anchor. Profile <profile> for usage <usage>. 3413 Local Certificate <cert> removed. The specified CA-signed certificate has been installed on the Trust Anchor with the indicated profile and usage. RMON_CRYPTO_CERTMGR_CA_CERT_INSTALLED The specified local certificate has been removed. RMON_CRYPTO_CERTMGR_CERT_REMOVED 3414 Certificate <cert> is invalid. The chain exceeds 5 certificates. The specified certificate is invalid because the chain exceeds 5 certificates. RMON_CRYPTO_CERTMGR_CHAIN_INVALID_LENGTH 3415 Attempted to install certificate containing formatting errors. 3416 Failed to initialize SSL connection for OpenFlow. 3417 OpenFlow SSL connection expiring soon. 3418 Local Certificate <cert is about to expire. 3419 Local Certificate <cert> has expired and is no longer valid. An attempt was made to install a certificate that contained formatting errors. RMON_CRYPTO_CERTMGR_CERT_FORMAT_ERROR The SSL connection for OpenFlow failed to initialize. RMON_CRYPTO_CERTMGR_SSL_INIT_FAILED The OpenFlow SSL connection will expire soon. RMON_CRYPTO_CERTMGR_CONN_EXPIRED The specified local certificate is about to expire. RMON_CRYPTO_CERTMGR_CERT_EXPIRE_SOON The specified local certificate has expired. RMON_CRYPTO_CERTMGR_CERT_EXPIRED 3500 The supportablility rmation in file <filename> is corrupt and has been removed. Some crash or boot-history rmation is corrupt and has been removed. RMON_CRASH_FILE_CORRUPT 3510 SLP service enabled SLP service is enabled. RMON_SLP_ENABLE_SUCCESS 3511 SLP service enable failed <errnum> SLP service enable failed. RMON_SLP_ENABLE_FAIL 3512 SLP service disabled SLP service is disabled. RMON_SLP_DISABLE_SUCCESS 3513 SLP service disable failed SLP service could not be disabled. RMON_SLP_DISABLE_FAIL 3514 Service <service> registered successfully The service to be advertised is registered. RMON_SLP_SVC_REG_SUCCESS 3515 Service <service> register failed The service to be advertised failed registration. RMON_SLP_SVC_REG_FAIL 87

3516 Service <service> deregistered The service advertised has been deregistered. RMON_SLP_SVC_DEREG_SUCCESS 3517 Service <service> deregister failed 3518 Listening on IP <address> port <port-num> for SLP request 3519 Stopped listening on IP <address> port <port-num> for SLP requests There has been a failure in deregistering the advertised service. RMON_SLP_SVC_DEREG_FAIL Listening for SLP requests has begun. RMON_SLP_LISTEN_IP_ADD_SUCCESS Listening for SLP requests has stopped. RMON_SLP_LISTEN_IP_DEL_SUCCESS 3520 Socket error <err-num> Socket related errors, including create, accept, bind, send, or receive errors. RMON_SLP_SOCKET_ERROR 3561 initialization success ECM initialization was successful. RMON_ECM_INIT_SUCCESS 3562 initialization failed. error-code <err-code> 3563 sending data to ECM failed. errorcode <err-code> 3564 starting service <service> <%d> failed 3565 stop service <service> <%d> failed 3566 closing connection <connection> failed ECM initialization failed. RMON_ECM_INIT_FAIL Sending data to ECM failed. RMON_ECM_TX_DATA_FAIL Starting an ECM service failed. RMON_ECM_START_SVC_FAIL Stopping an ECM service failed. RMON_ECM_STOP_SVC_FAIL Closing a connection failed. RMON_ECM_STOP_CONNECTION_FAIL 3567 internal error <error> An internal error has occurred. RMON_ECM_INTERNAL_ERROR 3568 port authorization failed uuid <num> service <service> peer ip< addr> 3569 adding to authorization table failed uuid <num> service <service> attribute <attribute> 3570 delete from authorization table failed uuid <num> service <service> attribute <attribute> debug debug Port authorization failed RMON_ECM_PORT_AUTHR_FAIL Adding to the authorization table failed. RMON_ECM_ADD_AUTHR_FAIL Deleting from the authorization table failed. RMON_ECM_DELETE_AUTHR_FAIL 88

3571 modify authorization table failed uuid <num>, service <service>, attribute <attribute> 3572 ssl handshake failed. peer ip <addr>, service <service> 3573 saving author file to flash failed. error code <err-code> 3574 authorization file in the flash is corrupted debug debug Modifying an entry from the authorization table failed. RMON_ECM_MODIFY_AUTHR_FAIL The SSL handshake failed for a connection. RMON_ECM_SSL_HANDSHAKE_FAIL Saving the authorization table to flash failed RMON_ECM_SSL_HANDSHAKE_FAIL The authorization file in the flash is corrupted. RMON_ECM_AUTHOR_FILE_CORRUPT 3612 Slot-up event for port <portnum> on vlan <vid> 3613 VLAN <vid> not available for HPSMA 3614 VLAN <vid> exists as normal VLAN, not assigned to HPSMA 3615 VLAN <vid> creation failed for HPSMA debug Slot-up event for the port on the indicated VLAN. RMON_HPESP_IP_SLOT_UP The VLAN is not available for HPSMA. RMON_HPESP_IP DEFAULT_SMA_VLAN_NOT_AVAILABLE This is a normal VLAN, it is not available for HPSMA. RMON_HPESP_IP_DEFAULT_SMA_VLAN_EXISTS_AS_NORMAL_VLAN The indicated VLAN is not available for HPSMA. RMON_HPESP_IP_DEFAULT_SMA_VLAN_CREATION_FAILED 3616 VLAN <vid> created for HPSMA The indicated VLAN was created. RMON_HPESP_IP_DEFAULT_SMA_VLAN_CREATED 3617 IP address <ip-addr> already taken, not assignable to HPSMA VLAN 3618 Port <port-num> not assigned to HPSMA-VLAN 3619 Port <port-num> assigned to HPSMA-VLAN 3620 Port <port-num> already part of HPSMA-VLAN 3621 IP address <ip-addr> assigned to MAC <mad-addr> 3622 DHCP Server started with IP Address <ip-addr> debug The default IP address is not available for HPSMA-VLAN. RMON_HPESP_IP_DEFAULT_IP_NOT_AVAILABLE The indicated port is not assigned to the HPSMA-VLAN. RMON_HPESP_IP_PORT_NOT_ASSIGNED The indicated port is assigned to the HPSMA-VLAN. RMON_HPESP_IP_PORT_ASSIGNED The indicated port is already part of the HPSMA-VLAN. RMON_HPESP_IP_PORT_ALREADY_ASSIGNED The IP address is leased. RMON_HPESP_IP_DHCP_IP_LEASED The DHCP server is started with the indicated IP address. RMON_HPESP_IP_DHCPS_STARTED 3623 HPSMA-VLAN set to <vid> The HPSMA VLAN is set. RMON_HPESP_IP_SMA_VLAN_SET 3624 DHCP server set with IP address <ip-addr> The DHCP server is set with the indicated IP address. RMON_HPESP_IP_DHCPS_IP_SET 89

3625 DHCP server stopped The DHCP server is stopped. RMON_HPESP_IP_DHCPS_STOPPED 3626 DHCP server restart failed The DHCP server restart failed. RMON_HPESP_IP_DHCPS_RESTART_FAILED 3627 DHCP server IP range set to <ipaddr-range> 3628 DHCP server lease time set to <num-secs> seconds 3629 Config inconsistency detected. Some records may have been deleted. 3700 Caution: Non-HP transceiver detected in port <port-num>, which may cause network problems. HP will not support or troubleshoot problems with this transceiver. 3701 Port <port-num> still has an unsupported transceiver, which may cause network problems. The DHCP server IP address range has changed. RMON_HPESP_IP_DHCPS_IP_RANGE_SET The DHCP server lease time has changed. RMON_HPESP_IP_DHCPS_LEASE_TIME_SET There is an inconsistency in SMA VIDMAP and the VLAN records. RMON_HPESP_IP_INCONSISTENT_CONFIG Logs a port that has a non-hp transceiver in it. RMON_XCVR_CLONE_DET The indicated port still has an unsupported, non-hp transceiver in it. RMON_XCVR_CLONE_REMIND 3750 unable to apply ra-guard to port <port-num> 3751 unable to apply ra-guard to port <port-num>, not enough hw resources 3752 unable to add port <port-num> to trunk, ra-guard is configured on port 3760 unable to delete ra-guard port <port-num> There was an error applying RA-guard to a port. RMON_RA_GUARD_PORT_ERROR There was an error applying RA-guard due to lack of hardware resources. RMON_RA_GUARD_PORT_NO_RESOURCES_ERROR There was an error attempting to add a port to a trunk. Dynamic trunks cannot be configured on ports with RA-guard configured. RMON_RA_GUARD_PORT_ADD_TRUNK_PORT_ERROR Unable to delete the specified RA-guard port. RMON_RA_GUARD_PORT_REMOVE_ERROR 3782 DHCP learnt DNS server entries <ip-addr> and <ip-addr> configured 3783 DHCP erver did not offer all the DNS parameters on Primary VLAN The indicated DNS server entries were configured RMON_DHCP_LEARNT_DNSPARAMS The DCHP server is not offering all the DNS paramters on the primary VLAN. RMON_DHCP_NODNSPARAMS 90

3784 Invalid domain name provided by DHCP Server on Primary VLAN 3785 Invalid DNS server address provided by DHCP Server on Primary VLAN An invalid domain name was provided by the DHCP server. RMON_DHCP_INVALID_DNS_SUFFIX The DNS server address provided by the DHCP server on the primary VLAN is invalid. RMON_DHCP_INVALID_DNS_SVRADDR 3801 Mgmt module <module> - Nonstop switching disabled because of SW version mismatch. Warm standby enabled. 3831 EEE cannot be enabled on <slot> on this hardware revision. There is a software version mismatch between the management modules. Non-stop switching is disabled and warm standby is enabled. RMON_SYSTEM_MGMT_OS_DIFF_WARM_STBY EEE cannot be enabled on the specified slot on this hardware. RMON_CHASSIS_SLOT_EEE_UNSUPPORTED 3841 <error message> FPGA upgrade failed. RMON_SSC_FPGA_UPGRADE_FAILED 3842 <message> FPGA upgrade passed. RMON_SSC_FPGA_UPGRADE_PASSED 4050 Distributed power to this switch has changed to <num> watts by %s 4051 Unable to distribute power as requested. Reason: <reason> 4052 External power supply connection status changed from <status> to <status>. 4053 External power supply has been restored to factory default. 4054 There is a mismatch in power supply ratings between external power supply and this switch. Configuration of external supply will not be allowed. 4055 12v standby rail on external power supply has failed. 4056 Unable to communicate with external power supply. External power supply power-share request is completed. RMON_PPS_DISTRIBUTE_PWR_CHANGE Unable to perform power-share as requested. RMON_PPS_DISTRIBUTE_PWR_REQ_FAIL The external power supply connection status changed from <previous state> to <current state>. RMON_PPS_STATUS_CHANGE This message displays when the external power supply has been restored to the factory default. RMON_PPS_FAC_RESET_DONE There is a mismatch in power supply ratings between the external power supply and the switch. The external power supply will not be configured. RMON_PPS_PSU_MISMATCH The 12v standby rail on the external power supply has failed. RMON_PPS_12V_STDBY_BAD Unable to get i2c access to external power supply. RMON_PPS_COMM_BAD 91

4057 An over-current has been detected on external power supply. 4058 An overtemperature has been detected on external power supply. 4059 Main power rail on external power supply has failed. 4060 Internal power supply failure detected. Over current has been detected on the external power supply. RMON_PPS_OVER_CURRENT_DET The external power supply is over temperature. RMON_PPS_OVER_TEMP_DET The main power rail on the external power supply has failed. RMON_PPS_MAINPWR_RAIL_BAD Internal power supply is bad. RMON_PPS_IPS_BAD_DET 4061 External power supply ready The external power supply is ready. RMON_PPS_READY 4062 Unsupported power supply confiugrations detected on external power supply 4063 Hotswap controller is now in <state> state. 4064 Unable to restor external power supply to factory default as requested. Reason: <reason>. 4065 Mailbox on external power supply is <status> by <status> 4066 Low priority power reduction completed. 4067 Unable to reduce low priority power as requested. Reason: <reason>. Unsupported power supply configurations are detected on the external power supply. RMON_PPS_PSU_UNSUPPORTED The external power supply port is now in <enabled/disabled/autorecovery disabled/auto-recovery enabled> state. RMON_PPS_HSC_CTRL_CHANGE The external power supply cannot be restored to the factory default. RMON_PPS_FAC_RESET_FAIL The external power supply zone record status: <status>. RMON_PPS_MAILBOX_STATUS Can be either: External power supply power reduction completed or External power supply power reduction not required. RMON_PPS_ALLOC_PWR_REDUCED The low priority power reduction was unsuccessful. RMON_PPS_ALLOC_PWR_DROP_FAIL 4068 Unable to enable or disable hotswap controller as requested. Unable to control external power supply port <cable> as requested. RMON_PPS_HSC_CMD_FAIL 4069 External power supply <message> External power supply rmation. QA-only log message. RMON_PPS_XPS_INFO 92

unk Configuration removed for module in slot <slot>. A slot has been removed with the no module command and the entire configuration for the module has been deleted. RMON_CHASSIS_MODULE_CONFIG_REMOVED 93

94

Technology for better business outcomes To learn more, visit www.hp.com/networking Copyright 2013 Hewlett-Packard Development Company, L.P. The rmation contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP will not be liable for technical or editorial errors or omissions contained herein. September 2015 Manual Part Number 5998-4397 Rev. B