ExtremeWare Error Message Decoder Software Version 7.8 Extreme Networks, Inc. 3585 Monroe Street Santa Clara, California 95051 (888) 257-3000 http://www.extremenetworks.
Alpine, Altitude, BlackDiamond, EPICenter, Ethernet Everywhere, Extreme Ethernet Everywhere, Extreme Networks, Extreme Turbodrive, Extreme Velocity, ExtremeWare, ExtremeWorks, GlobalPx Content Director, the Go Purple Extreme Solution Partners Logo, ServiceWatch, Summit, the Summit7i Logo, and the Color Purple, among others, are trademarks or registered trademarks of Extreme Networks, Inc. or its subsidiaries in the United States and other countries.
Contents Preface Chapter 1 Chapter 2 Chapter 3 Introduction 33 Conventions 34 Related Publications 34 Emergency Error Messages cluster mbufs 35 Diagnostic Failure, Port 36 Hot Swap 37 No Power Values 38 netJob Error 39 POST Failure 40 VDSL Read/Write 41 Alert Messages Flash Error 43 ipmcDelCache Problem 44 VDSL Port Not Ready 45 VDSL Task Message 46 Cable Diagnostics on Port Failed 47 Disable Port Failed 48 Restoring Permanent FDB MAC Entries Failed 49 Critical Message
Contents 4 Cannot Start EAPS 52 Checksum Error on CPU Packet 53 Checksum Error on CPU Packet of 64 54 Checksum Error on External Port 55 Checksum Error on Internal Port 56 Checksum Error on Motherboard 57 Checksum Error on MSM 58 Checksum Error on EDP Packet and Slot 1 59 Checksum Error on PoE Calibration Data 60 CPU Dialogue 61 Decoder Timeout 62 EAPS Domain Does Not Exist 63 EAPS Instances Exceeding Limit 64 EAPS Send 65 EPC Task Crash 66 Fail Timer Expired, State Complete
Contents ExtremeWare Error Message Decoder Not a Control VLAN 87 OSPF Assertion Failed 88 Out of MBufs 89 Out of Memory, Adding Control VLAN 90 Out of Memory, Adding Protected VLAN 91 Out of Memory, Binding VLAN 92 Out of Memory, Creating EAPS Domain 93 Out of Memory, Initializing EAPS 94 Packet Corruption on Motherboard 95 PoE Calibration Required 96 PoE Firmware Update Failed 97 Port State Blocked 98 Power Supply Failure, No Backup Available 99 Power Supply Failure, Trying Agai
Contents 6 Power Supply Normal 121 Power Supply Failed 122 Corrupted Backplane Health Check Packet 123 Download Configuration File Not Available 124 Download Configuration Task Spawn Failed 125 Overwrite Download Configuration Buffer 126 Configuration Download Size Too Large 127 Error Getting Information on Internal Card 128 Add and Remove Xen Card 129 STPD Tag From Bridge That Ignores BPDU 130 Receive Task Spawn Failed 131 Transmission Task Spawn Failed 132 LSM Filter: Drop Receiv
Contents ExtremeWare Error Message Decoder HTTPD Socket Non-blocking IOCTL Failed 155 HTTPD Bind Failed 156 Rx Buffer Allocation Failed 157 Socket Creation Failed 158 Checksum Error on Slot 159 Corrupted Packets on Slot 160 Card Diagnostic Failed 161 Registry Operation Timeout 162 CPU Control Timeout 163 Registry Operation Timeout 164 Corrupted Packets on M-BRD 165 System Restarted by Hardware Watchdog 166 Task Running During Watchdog Timer Expiry 167 Checksum Error on Frame 168
Contents 8 Fast Path Checksum Threshold Exceeded 189 Invalid Card State 190 Invalid Event in Checksum Failure 191 Missed System-Health-Check Packet 192 Power Supply Temperature Failed 193 Power Supply Unit: Fan Failed 194 Power Supply Unit: Input failure 195 LSM Transmit Task Message Queue Receive Failed 196 LSM Receive Task Message Queue Receive Failed 197 LSM Receive Task: Unable to Start Timer 198 Cannot Write to CFGDB Port 199 Unicast Route is a Blackhole Route 200 MSM-B HAS TA
Contents ExtremeWare Error Message Decoder SFLOW: Configuration Parsing Failed for Port 223 Allocating IP SA Entry Failed 224 Corrupted EDP PDU: Bad OUI 225 Corrupted EDP PDU: Bad Length 226 Corrupted EDP PDU: Bad Version 227 Corrupted EDP PDU: Bad SNAP 228 Configuring Hardware Queue Before Starting the Card 229 No Memory In Bind to Route-map 230 Disable ARP Learning 231 Port List Not Present For Unbind 232 Loadshare Port List: Memory Allocation Failed 233 MAC Lock Age Task Message:
Contents Chapter 4 10 System Health Check: Checksum Error 257 VRRP Allocation: Memory Failure 258 Failed to Change MAC Address on Port 259 Unable to Clear Netlogin Entry for MAC 260 Remote Set Request Not Implemented 261 Memory Allocation for Bridge-Interface Failed 262 Memory Allocation for Segment Interface Failed 263 Memory Allocation for ESD Domain Failed 264 Hello Timer Creation Failed 265 Fail Timer Creation Failed 266 No EAPS Domain on the Control VLAN 267 Segment Timer Creat
Contents ExtremeWare Error Message Decoder Login Failed 290 Messages from Interrupt Level Lost 291 No 802.1q Tag 292 No PIF for BIF 293 Packet Send Buffer Failed 294 PBUS CRC Error 295 PoE Firmware Invalid on Blade 296 PoE Firmware Invalid on Slot 297 PoE Hardware Problem, Disabling PoE on Port 298 PoE Not Operational 299 Port in 802.
Contents 12 Invalid Message Type 324 Manual Diagnostics In Progress 325 Memory Allocation for Manual Diagnostics Failed 326 Message Queue Receive Failed 327 slot 1 port 5 Good Response PPP Link Status Size 12 328 No Physical Port Associated to STP Port 329 Unable to Allocate Memory for Bridge STPD List 330 PPP Link Configuration Too Short 331 STP Task: Cannot Get Transmission Mbufs 332 STP Timer Message Queue Send Failed 333 No Response for PPP Link Configuration 334 No Response for
Contents ExtremeWare Error Message Decoder Error Reading Register 358 Active MSM Failed to Program FLASH 359 Running Configuration Not Saved 360 Error Getting Information on Internal Card Slot 361 Failed to Delete RIP Route 362 Failed to Delete RIP Route 363 Failed to Send IP Datagram 364 Session Time Out While Reading Register 365 Interface Not Specified for the Route 366 Slave NMC Not Active 367 No Communication Between MSM-A and MSM-B 368 Enabling and Disabling Auto Polling: Card
Contents 14 No Physical Interface 392 Platform Not Supported 393 Skipping Bridge Learning 394 Invalid Card Type for Slot 395 Invalid Switch Card 396 TFTP Initialization Errors 397 Insufficient Instance Object ID 398 Empty STP Packet 399 STP Packets with Incorrect Version Number 400 STP BPDU Does Not Match with Port Mode 401 Cannot Delete STP Domain 402 Large STP Packets 403 DVMRP Interface Creation Failed 404 DVMRP Task: Invalid Message Type 405 Linking or Adding Timer Node to
Contents ExtremeWare Error Message Decoder AP Returned Non-existent VLAN ID 426 Card Not Supported 427 Card SEM Received Invalid Event 428 Configuration: Card Type Not Allowed 429 Failed to Read Card EEPROM 430 Quake Register: Read Failed 431 Card SEM Received Invalid Event 432 Could Not Allocate Memory 433 Cloning OID Failed 434 Cloning varbinds Failed 435 Error Updating FDB 436 Deleting STP Instance Failed 437 Creating STP Domain Failed 438 Enabling VRRP On Interface Failed 43
Contents 16 Log Filter: Accepting Factory Default Failed 460 Deleting Log Filter Failed 461 Log Filters: Maximum Configured 462 Deleting Log Filter Failed 463 Log Filter: Cannot Copy Completely 464 Modifying Log Filter Failed 465 Log Filter Does Not Exist 466 Log Filter Does Not Exist 467 Log Filter Exceeds Maximum Length 468 Permanent Entry With MAC Not Found 469 FDB: Port Already In Permanent Entry Table 470 FDB Ageing Time Too Large 471 MAC FDB Refresh: Null ARP 472 Invalid AR
Contents ExtremeWare Error Message Decoder Deleting Bridge Interface for Port Failed 494 Deleting Bridge Interface for VLAN Failed 495 Adding Segment Port Interface Failed 496 Control VLAN Interface Not Found 497 Unknown Port State 498 EAPS Domain Segment Interface Not Found 499 Removing Segment Port Interface Failed 500 EAPSD Domain Part of Another ESD Instance 501 Invalid Port Type 502 Shared-port Instance Out of Range 503 ESD Controller in Wrong State 504 Cannot Set Port 505 Can
Contents Chapter 5 18 Partner Mode in a Controller Event 528 EAPSD: Error In Stopping the Domain 529 EAPSD: Error In Stopping All Domains 530 EAPSD: Error in Unbinding Protected VLAN 531 EAPS Shared-port: Stopping the Domain Failed 532 EAPS Shared-port: Unbinding from L2 Domains Failed 533 EAPS Shared-port: Disabling the Domain Failed 534 Upgrading Bootloader Failed 535 Upgrading Bootloader Failed 537 Bootloader Header Update Failed 538 Reboot Loop Detected For Back-up MSM 539 No Un
Contents ExtremeWare Error Message Decoder Btree Insert Failed 561 Cannot Add VLAN to EAPS 562 Cannot Allocate Memory for Timer 563 Cannot Find Default VLAN 564 Cannot Get Memory Buffer Transaction 565 Cannot Save Default STPD 566 Cannot Send Card 567 Cannot Send Health PDU 568 Cannot Send nmc 569 card_db.
Contents 20 ESRP Enabled, Action Not Possible 595 Exceeded Committed-Rate Condition Clear 596 Exceeded Committed-Rate Condition Set 597 Failed Diagnostic Packet 598 Failed to Obtain Statistics 599 Failed to Receive Message 600 FDB Entry Not Found 601 FDB Error 602 Free List 603 GARP Event 604 Get EEPROM Error 605 Get Failed, Port Not Found 606 Incorrect State 607 Install STPD Tag Failed, Ignore BPDU Enabled 608 Insufficient Memory, PIF Structure 609 Insufficient Memory, Port
Contents ExtremeWare Error Message Decoder msgQSend Message Queue Full 629 MsgQ Send Error 630 MSM Module Type Mismatch 631 ngRxFirst Failed 632 No Associated STPD Port 633 No BIF for VLAN ID 634 No EAPSD-Bridge Links Exist 635 No Matching FDB Entry 636 No Message Buffer 637 No Protected VLANs Configured 638 otpRamBusy 639 PDU Received on Wrong Port 640 Port Binding Failed, Bound to Another STPD 641 Port Binding Failed, Bound to that STPD 642 Port Creation Failed, Bad STPD Inst
Contents 22 SNMP IP QoS ACL Missing 663 Spurious Link State 664 STP Disabled for Port 665 STP Disabled for STPD 666 STPD Instance Does Not Exist 667 STPD Malloc Failed 668 STPD Table Malloc Failed 669 STP Port Creation Failed 670 STP Port Does Not Exist 671 STP Port Malloc Failed 672 STPD Tag Removal Failed 673 SuperBridge Error 674 System Overheated 675 Stuck Interrupt 676 Task Exceeded Stack Boundary 677 Task Failed 678 Timer Delay Exceeds Capacity 679 Timer Error, Non-
Contents ExtremeWare Error Message Decoder VLAN Does Not Contain Port 697 VLAN ID Already Bound 698 VLAN ID No Longer in STPD 699 VLAN Is Not Control VLAN 700 VLAN Is Not Protected VLAN 701 Port Number Out of Range 702 Slot Number Out of Range 703 Too Many Announcements on Port 704 FDB Scan Entries Remapped 705 Problem with I/O Modules 706 Bridge and EAPSD Link Exists 707 Changing QoS Policy Default Value 708 Netlogin VLAN: IP Address Not Configured 709 Write Error While Download
Contents 24 VLAN ID Not in STP Domain 731 BPDU Carrier VLAN Not Auto-Bind 732 STP Disabled 733 DVMRP: Received Bad Metric 734 DVMRP: Prune Received From Non-DVMRP Neighbor 735 DVMRP: Received Short Prune NBR On VLAN 736 DVMRP: Access Violation 737 DVMRP: Allocating Packet Memory On VLAN Failed 738 DVMRP: Allocating Memory For NBR Failed 739 DVMRP: No Route For Group 740 DVMRP: Allocating Memory To Transmit Prune Failed 741 DVMRP: Group And Source Does Not Match In Graft 742 DVMRP:
Contents EAPSD: VLAN Already Part of Another EAPS Domain Chapter 6 Chapter 7 ExtremeWare Error Message Decoder 765 Notice Messages Current Below Specification 767 Current Over Specification 768 Port Cannot Power 769 Informational Messages Bad PoE Hardware 771 Calibration Data Updated 772 Cannot Allocate Memory Buffer 773 Disabling EAPS 774 EEPROM Read Retried 775 Enabling EAPS 776 Fail Timer Flag Cleared, EAPS=E05B 777 Fail Timer Flag Cleared, EAPS=VLAN1 778 Fail Timer Flag Set
Contents 26 Port Status Changed to Up 798 Power Is Up for Slot 799 Power Supply Failure, Switching to Backup 800 Preforward Timer Expired, EAPS=E38A 801 Preforward Timer Expired, EAPS=VLAN1 802 Primary Port Status Changed to Blocked 803 Primary Port Status Changed to Down 804 Primary Port Status Changed to Up, from Blocked 805 Primary Port Status Changed to Up, from Unknown 806 QoS Profile, Invalid QoS Configuration 807 Reached G1 Limitation 808 RIP, MBZ Field 809 Ring Break, Flush
Contents ExtremeWare Error Message Decoder Transit Node State Changed to Links-Up, from Idle 832 Updating PoE Calibration 833 User Logged Out from Telnet 834 Index Position 835 SNMP Object Identification 836 Initializing GPP Module 837 Aborted Cable Diagnostics in Auto Mode 838 Started Cable Diagnostics in Manual Mode 839 BootROM image: Bad CRC 840 Updating BootROM Image 841 BootROM Image: Wrong Magic 842 PSU Output Ready 843 Binding IP Address Information 844 No Wireless Interfa
Contents 28 Upgrading Bootstrap: Do Not Remove Power 866 Upgrading Bootloader: Do Not Disconnect Power 867 Operating With Reserve Power 868 Bridge Learning: New Entry for Frame 869 Bridge Learning: Changing Static Entry Failed 870 Bridge Learning: Updating Frame Entry 871 Switch Configuration Changed Using SNMP 872 Output Not in Mirror-card 873 Setting Card State Delayed 874 Card State Set To Mismatch 875 Card State Set To Unknown 876 Converting Serial EEPROM To New Format 877 EEPR
Contents ExtremeWare Error Message Decoder EAPSD: Received Link Up PDU 900 EAPSD: Received Link Down PDU 901 EAPSD: Received Query Link Status PDU 902 EAPSD: Received Health PDU, Ring State Complete 903 EAPSD: Received Health PDU on Primary Port 904 EAPSD: State Transition to Down, from Up 905 EAPSD: State Transition to Unknown, from UP 906 EAPSD: State Transition to Up, from Down 907 EAPSD: State Transition to Blocked, from Down 908 EAPSD: State Transition to Unknown, from Blocked 909
Contents Chapter 8 30 Radius Receive Time Out 934 Invalid Message Authenticator 935 User Authenticated by Radius Server 936 Nonexistent Radius User or Wrong Password 937 Debug Messages 100 Messages Queued 939 Failed to Add Address 940 Invalid Destination 941 MAC Based VLAN 942 pqmWaitKill Failed 943 PTAG Error, NGDelCard 944 QuakeWaitPbut2CacheXfer Failed 945 Recv Buffers Not Empty 946 RIP/VLSM 947 Failed to Send IP FDB Age Message 948 Failed to Send FDB Age Message 949 MAC
Contents Index ExtremeWare Error Message Decoder 31
Contents 32 ExtremeWare Error Message Decoder
Preface This guide lists the most common ExtremeWare error messages, and provides the following for each: • Software version • Hardware version • Explanation • Action Introduction ExtremeWare sends these error messages to the console or log during normal operation. Some of these messages are informational, some help diagnose problems, and some indicate problems.
Preface Conventions Table 1 and Table 2 list conventions used throughout this decoder. Table 1: Notice Icons Icon Notice Type Alerts you to... Note Important features or instructions. Caution Risk of personal injury, system damage, or loss of data. Warning Risk of severe personal injury. Table 2: Text Conventions Convention Description Screen displays This typeface represents information as it appears on the screen, or command syntax.
1 Emergency Error Messages Emergency errors indicate severe problems that require immediate corrective action. Check the “Issues Resolved In” sections in the latest ExtremeWare Installation and Release Notes to see if the error message indicates an issue that has been corrected in a recent software release. cluster mbufs MCLGET: No cluster mbufs. Task 86708f30 gw-517 last message repeated 29 times gw-517 KERN: MCLGET: No cluster mbufs. Task gw-517 KERN: MCLGET: No cluster mbufs.
Emergency Error Messages Diagnostic Failure, Port N6_OOB_BD6800 PORT: Port 3:19 failed in diagnostic, it is disabled DIAG: Slot 4 port 34 Failed vlan loop back test Software Version ExtremeWare 4.x, 6.1.5, and later Hardware Version BlackDiamond Explanation These messages indicate that a port failed diagnostics. Action Check the system and replace the I/O module as necessary.
Hot Swap Hot Swap SWL-AL03 KERN: ngRxFirst failed WTX2 - (9, e0, 4000) SWL-AL03 SYST: MSM A Card Shutdown called Software Version ExtremeWare 6.1.9b17 and later Hardware Version BlackDiamond Explanation These messages indicate that the module has been hot swapped while traffic was present. Action Remove and re-insert the module into the slot.
Emergency Error Messages No Power Values PWR MGMT: System is using no power values: Software Version ExtremeWare 6.1.x Hardware Version BlackDiamond “i” series Explanation This message indicates a problem with power values. While EEPROM on the power supply unit was being read, an unknown power supply type has been indicated. This can happen due to multiple reasons such as faulty power supply or other read errors. Action Contact Technical Support to troubleshoot the problem.
netJob Error netJob Error fdbAgeTask panic: netJobAdd: ring buffer overflow! tNetTask panic: netTask: netJobRing overflow! Software Version ExtremeWare 6.1.5b23 Hardware Version BlackDiamond “i “series Explanation These messages indicate that the MSM64i has run out of memory. Action Contact Technical Support to troubleshoot the problem.
Emergency Error Messages POST Failure Slot 1 failed PQM internal memory test Slot 1 PQM ASIC failed register test Slot 1 failed FDB memory test FDB extension memory bus failed at data bit Slot 1 failed VPST memory test VPST memory bus test failed at data bit 19 Slot 1 AFC ASIC failed register test Slot 1 RR No.
VDSL Read/Write VDSL Read/Write Could not read VDSL reg 0x8c00 on 4:1 Could not write VDSL reg 0x8c00 on 4:1 Software Version ExtremeWare 6.1.8W301b51 Hardware Version VDSL Explanation These messages indicate a hardware failure that is most likely limited to the one port reported. Action RMA the module.
Emergency Error Messages 42 ExtremeWare Error Message Decoder
2 Alert Messages Alert messages indicate problems that require corrective action. Check the “Issues Resolved In” sections in the latest ExtremeWare Release Notes to see if the error message indicates an issue that has been corrected in a recent software release.
Alert Messages ipmcDelCache Problem MIKE: FIXME: ipmcDelCache problem. g/s/m=229.55.150.208/16.100.104.0/255.255.252.0. Software Version ExtremeWare 4.1.x Hardware Version BlackDiamond and Summit Explanation This message indicates that you are trying to remove an entry whose PTAG entry might be invalid. This can occur as a result of running out of internal resources in the router (PTAGs).
VDSL Port Not Ready VDSL Port Not Ready VDSL port not ready: 4:1(3) Port 4:1 failed to be initialized correctly Software Version ExtremeWare 6.1.8W301b51 Hardware Version VDSL Explanation These messages indicate that there was an error during the initialization of the VDSL port, which is a result of a hardware failure on the module.
Alert Messages VDSL Task Message VDSL err task message failure Software Version ExtremeWare 6.1.8W301b51 Hardware Version VDSL Explanation This message indicates that ExtremeWare could not send the “loss of normal or low voltage” power change message. Action Contact Technical Support to troubleshoot the problem.
Cable Diagnostics on Port Failed Cable Diagnostics on Port Failed Cable Diags Failed: Port [1:21], Mode [Auto]\n Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation This message indicates that the cable diagnostic module has detected a fault on the cable connected to port 1:21. Action Check the cable connected to port 1:21. If found to be faulty, replace the cable.
Alert Messages Disable Port Failed Cable Diags Alert: Unable to Disable Port [2:16] Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation This message indicates that the cable diagnostic module failed to disable port 2:16 before running the diagnostics. Action Check whether the port is part of any load sharing group. If the port is part of any load sharing group, disable the sharing on the port and then run the cable diagnostics.
Restoring Permanent FDB MAC Entries Failed Restoring Permanent FDB MAC Entries Failed • fdbParseNv: Get GM_FDB_MAC_ENTRY returned error • fdbParseNv: Get GM_FDB_PORT_ENTRY returned error Software Version ExtremeWare 7.3 Hardware Version All “i” and “e” series switches Explanation This message indicates that the switch encountered an error while restoring the permanent FDB (Forwarding Database) MAC entries. Action Contact Technical Support.
Alert Messages 50 ExtremeWare Error Message Decoder
3 Critical Messages Critical messages indicate problems that require corrective action. Check the “Issues Resolved In” sections in the latest ExtremeWare Installation and Release Notes to see if the error message indicates an issue that has been corrected in a recent software release. Calibration Required, Programming Failure Slot X requires PoE calibration - programming failure Software Version ExtremeWare 7.2.
Critical Messages Cannot Start EAPS eaps.c 421: Error! spawning EAPS task Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the Ethernet Automatic Protection Switching (EAPS) task could not be started. Action The switch may have become unstable. Contact Technical Support.
Checksum Error on CPU Packet Checksum Error on CPU Packet ERROR: Checksum Error on CPU received pkt. Software Version ExtremeWare 6.1.8b12 and later Hardware Version All “i” series Explanation This message indicates a new CPU Cyclic Redundancy Check (CRC). It prevents bad packets from being passed up to the CPU. Action If this error is seen only once in the log, no action is necessary. If you are using ExtremeWare 6.2.
Critical Messages Checksum Error on CPU Packet of 64 ERROR: Checksum Error on CPU recived pkt of 64 from port 8. status=0x3/0x500 Software Version ExtremeWare 6.1.8b12 and later Hardware Version All “i” series Explanation This message indicates a health check. Action No action is necessary.
Checksum Error on External Port Checksum Error on External Port ERROR: Checksum Error on external port Slot 6 port 47, Previous=0xeb, Current=0x71 Software Version ExtremeWare 6.1.8b12 and later Hardware Version All “i” series Explanation This message indicates that the switch fabric has detected an external corruption of the packets on slot 6, port 47. Action If this error is seen only once in the log, no action is necessary. If you are using ExtremeWare 6.2.
Critical Messages Checksum Error on Internal Port ERROR: Checksum Error on internal port Slot 3 port 7, Previous=0xd2d2, Current=0x4b4b Software Version ExtremeWare 6.1.8b12 and later Hardware Version All “i” series Explanation This message indicates that the switch fabric has detected an internal corruption of the packets on slot 3, port 7. Action If this error is seen only once in the log, no action is necessary. If you are using ExtremeWare 6.2.
Checksum Error on Motherboard Checksum Error on Motherboard Sys-health-check [CPU] checksum error on M-BRD Software Version ExtremeWare 7.2 and later Hardware Version All Explanation The motherboard of a Summit switch received a CPU checksum error. A packet that was sent to the CPU had a checksum error. Action If the system reports more than three errors (any combination) within a 60 minute period, the system needs attention.
Critical Messages Checksum Error on MSM ERROR: Checksum Error on MSM-A Software Version ExtremeWare 6.1.8b12 and later Hardware Version BlackDiamond “i” series Explanation This message indicates that the checksum on an EDP packet has failed, the port is internal, and MSM A has an internal PBus error. This implies that the checksum error is induced on MSM A. Action If this error is seen only once in the log, no action is necessary. If you are using ExtremeWare 6.2.
Checksum Error on EDP Packet and Slot 1 Checksum Error on EDP Packet and Slot 1 ERROR: Checksum Error on Slot 1 Software Version ExtremeWare 6.1.8b12 and later Hardware Version All “i” series Explanation This message indicates that the checksum on an EDP packet has failed, the port is internal, and the checksum error is induced on slot 1 which has one or more: PBus internal/external errors, CPU packets, or CPU dialogue packet errors.
Critical Messages Checksum Error on PoE Calibration Data Slot X PoE calibration data checksum failure Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that the checksum on the PoE calibration data has failed. The data could be invalid. Action RMA the blade.
CPU Dialogue CPU Dialogue Missed CPU diag data (type 4) on card 3 Software Version ExtremeWare 6.1.7 and earlier Hardware Version BlackDiamond Explanation This message indicates that the health-check messages which are being sent from the I/O module to the MSM64i have not been received within 3 seconds. Action Use the show diag command and look at the diag fail column for missing packets.
Critical Messages Decoder Timeout PORT: Slot 7 port 2 lane 2 decoder timeout! RR_Decoder = 0 Software Version ExtremeWare 4.x and 6.x Hardware Version BlackDiamond and Summit Explanation This error indicates that there is a problem in bringing up the internal backplane of the I/O module. Action Contact Technical Support to troubleshoot the problem. If the problem persists, upgrade to the latest software.
EAPS Domain Does Not Exist EAPS Domain Does Not Exist eaps.c 4853: Error! EAPS domain does not exist for instance 1 Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that there is an invalid internal number for the EAPS domain. Action EAPS task may have become unstable. Contact Technical Support.
Critical Messages EAPS Instances Exceeding Limit eaps.c serial eaps.c serial eaps.c serial 2639: ERROR! Reached maximum limit of EAPS instances admin: create eaps domain_67 2639:ERROR! Reached maximum limit of EAPS instances admin: create eaps domain_66 2639:ERROR! Reached maximum limit of EAPS instances admin: create eaps domain_65 Software Version ExtremeWare 6.
EAPS Send EAPS Send eaps.c407:Error!eapsWdTime:msgQSenerror3997698,errmsg_count4 Software Version ExtremeWare 6.2.1b17 Hardware Version BlackDiamond Explanation This message indicates that the EAPS timer has reached 5; therefore, EAPS packets are not sent out from the buffer. NOTE The EAPS timer starts as soon as the EAPS task starts. Action If you see this message during the boot-up process, ignore it.
Critical Messages EPC Task Crash Task: 0x8b5ea8b0 "tBGTask" Access Address: 0x00000017 Cause Register: 0x00001010 Status Register: 0x3400ad00 Exception Program Counter: 0x803ada38 Address load Exception Software Version All ExtremeWare versions Hardware Version All Explanation These messages indicate a generic task crash dump on a switch.
Fail Timer Expired, State Complete Fail Timer Expired, State Complete eaps_runtime.c 2429: Fail timer expired, while state is Complete, EAPS="E05B" Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the fail timer expired while the state is Complete. If there is an actual break in the ring, the Master should receive a Link-Down message from the Transit.
Critical Messages Fail Timer Expired, State Init eaps_runtime.c 2429: Fail timer expired, while state is Init, EAPS="eaps1" Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the fail timer expired while the state is Init. However, the fail timer should not expire. If there is an actual break in the ring, the Master should receive a Link-Down message from the Transit.
Firmware Download Failed Firmware Download Failed Slot X PoE firmware download failure - mismatch version IDs Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that the firmware’s version does not match the version supported by this version of ExtremeWare. Action Run CLI to download the firmware.
Critical Messages Hardware Failure, Attempting to Initiate Corrective Action Sys-health-check [ACTION] (PBUS checksum) (CARD_HWFAIL_PBUS_CHKSUM_EDP_ERROR) M-BRD Software Version ExtremeWare 7.2 and later Hardware Version All Explanation The motherboard on the Summit switch detected a EDP checksum error in the PBUS system of the Motherboard, causing a failure. This is a corrective action message. It is to alert the user that, if a corrective action was configured, it will take action now.
High CPU Utilization, fdbAgeTask High CPU Utilization, fdbAgeTask task fdbAgeTask cpu utilization is 100% PC: 80175f98 Software Version ExtremeWare 6.x Hardware Version All Explanation If this message appears continuously, it indicates that the fdbAgeTask is using most of the CPU power. It is most likely caused by a problem within the network (such as, broadcast storm, packet storm).
Critical Messages High CPU Utilization, tSnmpd task tSnmpd cpu utilization is 94% PC: 805aaaa4 last message repeated 1 times Software Version ExtremeWare 6.1 Hardware Version All Explanation These messages indicate that the SNMP task is taking up excessive CPU time. ExtremeWare 6.1.4b20 and earlier creates this message when you perform an SNMP bulkget or if there are many SNMP queries sent to a switch that has more than 1,000 VLANs defined. Action Upgrade to the latest software.
Illegal Calibration Data Illegal Calibration Data Slot X PoE calibration data illegal Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that the blade has illegal calibration data. Action RMA the blade.
Critical Messages Invalid EAPS Domain Instance eaps_runtime.c 1403: Error! Invalid EAPS Instance. vlanId=1001 Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the incoming EAPS PDU is mapped to an invalid EAPS domain. Action EAPS task may have become unstable. Contact Technical Support.
Invalid EAPS Domain Instance 65, Out of Range Invalid EAPS Domain Instance 65, Out of Range eaps.c 3406: Error! EAPS Domain instance 65 out of range Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that there is an invalid internal number for the EAPS domain. Action The EAPS task may have become unstable. Contact Technical Support.
Critical Messages Invalid Object ID eaps.c 4886: Error! Unknown gmId 0x Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that there is an invalid EAPS object ID. Action Probably using an incorrect software image. Contact Technical Support.
Invalid PTAG Invalid PTAG ptagInvalidSlotFunc() called (00000003, 00000204, 00000060, 00000ffd) Software Version All ExtremeWare versions Hardware Version Alpine Explanation This message indicates that the switch rebooted when the module with the slave load-sharing port was not present in the switch. If the slave port module is present and you get this message, you need the ExtremeWare 6.2.1b21 patch image.
Critical Messages Maximum EAPS Domains eaps.c 3396: Error! Reached maximum limit of EAPS instances Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the maximum limit of EAPS domains exists. You cannot create any more EAPS domains. Action Do not create any more EAPS domains, because you have reached the maximum number of supported domains.
Maximum Limit for VLANs Maximum Limit for VLANs eaps.c 4946: Error! Already reached max limit of Eapsd-Bridge links 4096 Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the maximum limit of EAPS domains to VLAN associations exists. You cannot add any more VLANs. Action Do not add any more VLANs as control or protect because you have reached the maximum limit of 4096.
Critical Messages Message Queue Creation Failed eaps.c 407: Error! creating eaps_msgQ Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the software could not create the message queue while initializing EAPS. Action The switch may have run out of resources. Contact Technical Support.
MII Reset MII Reset MAC: Port = 20 failed MII reset MAC: Port = 19 failed MII reset Software Version All ExtremeWare versions Hardware Version All Summit chipset products Explanation These messages indicate that either you have booted up the switch for the first time or the link on a port is down. It could be a hardware problem (caused by a bad chip) or a link problem. Action If you receive this error when you boot up the switch for the first time, no action is necessary.
Critical Messages msgQReceive Error eaps.c 453: Error! msgQReceive returned error Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the message queue returned an error. This message appears while attempting to process messages from the EAPS queue. Action EAPS task may have become unstable. Contact Technical Support.
msgQSend Error, OSPF Exception msgQSend Error, OSPF Exception Core-A-BD6800 OSPF: ospfWdTime: msgQSend error 3997698 Software Version ExtremeWare 4.x and 6.x Hardware Version All Explanation This message indicates that the Open Shortest Path First (OSPF) task has had an exception. Action Check for any EPC information prior to this message and use the show tech-support command and contact Technical Support to troubleshoot the problem.
Critical Messages MSM64i Packet Problem counter is CPU health-check packet missing type 0 on slot 5 CPU health-check packet problem on card 5 card.C 1937: card5 (type 20) is reset due to autorecovery config reset 1 Software Version ExtremeWare 6.x and later Hardware Version All Explanation These messages indicate that the system is running a system health-check to check the internal connectivity.
MSM Connection Broken MSM Connection Broken The connection between MSM-A daughter board and I/O module 2 is broken, need to fix immediately Software Version All ExtremeWare versions Hardware Version BlackDiamond Explanation This message indicates that the backplane connection between MSM A and the I/O module in slot 2 is broken. One of the two modules is bad. This can be faulty hardware or a seating problem with the modules. Action 1 Remove and re-insert the affected I/O module and MSM.
Critical Messages If you have an MSM64i seating problem, you might see some of the following additional errors: MSM-B may have problem to boot. Reboot it. ERROR: PSU-A input failure Failed to write vpst slot 2 Cannot send packet out slot 1. Card not present. Fan(3) is back to normal Fan(3) failed Quake Sched RAM request timeout Quake Queue Descriptor RAM request timeout quakeWaitTx Failed.
Not a Control VLAN Not a Control VLAN eaps.c 627: Error! "v1" is not a Control Vlan Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the VLAN receiving EAPS messages is not configured to be a control VLAN. Action If there is a single message, it can be ignored. If the messages occur on a regular basis, there is probably a software error. Contact Technical Support.
Critical Messages OSPF Assertion Failed assertion failed at ospf_cfg.c:2491 Software Version ExtremeWare 6.16b19/6.1.7b7 Hardware Version All “i” series Explanation This message is cosmetic. Action No action is necessary.
Out of MBufs Out of MBufs eaps_runtime.c 1231: Error! edpmbuf not available Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that an “out of MBufs” error occurred while attempting to send an EAPS PDU. Action The switch may have run out of resources. Contact Technical Support.
Critical Messages Out of Memory, Adding Control VLAN eaps.c 4095: Error! Out of memory Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that an out of memory error occurred while adding control VLAN. Action The switch may have run out of resources. Contact Technical Support.
Out of Memory, Adding Protected VLAN Out of Memory, Adding Protected VLAN eaps.c 4192: Error! Out of memory Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that an out of memory error occurred while adding protected VLAN. Action The switch may have run out of resources. Contact Technical Support.
Critical Messages Out of Memory, Binding VLAN eaps.c 4450: Error! Out of memory Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that an out of memory error occurred while binding a VLAN to EAPS domain. Action The switch may have run out of resources. Contact Technical Support.
Out of Memory, Creating EAPS Domain Out of Memory, Creating EAPS Domain eaps.c 3413: Error! Out of memory Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that an out of memory error occurred while creating EAPS domain. Action The switch may have run out of resources. Contact Technical Support.
Critical Messages Out of Memory, Initializing EAPS eaps.c 384: Error! Out of memory Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that an out of memory error occurred while initializing EAPS. Action The switch probably has a memory leak. Contact Technical Support.
Packet Corruption on Motherboard Packet Corruption on Motherboard Sys-health-check [DIAG] pkt corruption on M-BRD Software Version ExtremeWare 7.2 and later Hardware Version All Explanation This message indicates that a CPU-Diagnostic packet corruption error was received on the Motherboard of the switch. This switch is also a Summit stackable type. Action If the system reports more than three errors (any combination) within a 60 minute period, the system needs attention.
Critical Messages PoE Calibration Required Slot X requires PoE calibration Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that the blade was not calibrated and the PoE may not work at all. Action RMA the board.
PoE Firmware Update Failed PoE Firmware Update Failed Slot X PoE firmware update failed Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that a problem occurred while updating the firmware. Action Retry updating a few times. If it still fails, contact Technical Support.
Critical Messages Port State Blocked eaps_runtime.c 921: Error! State=LINK_DOWN, while Port TmpBlocked! "eaps1" Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the Transit node’s state is Link-Down, but has a port in blocked state. This is an illegal situation. Action The EAPS task may have become unstable. Contact Technical Support.
Power Supply Failure, No Backup Available Power Supply Failure, No Backup Available External 48V Supply failure on slot %d, no backup available Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This informational message indicates a loss of the external PoE power supply and no backup is available. All ports will lose power. Action Enable the backup or replace the external supply.
Critical Messages Power Supply Failure, Trying Again Later Internal 48V failure on slot x will retry later Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates a loss of the internal PoE power supply. All ports will lose power. Because the internal is the backup, ExtremeWare will keep trying to enable internal 48V supply. Action RMA the board.
Power Supply Failure, Trying Again Power Supply Failure, Trying Again Internal 48V up and running on slot x Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This informational message indicates a loss of the internal PoE power supply. All ports will lose power. Because the internal is the backup, ExtremeWare will keep trying to enable internal 48V supply. Action RMA the board.
Critical Messages Queue Descriptor Timeout Quake Queue Descriptor RAM request timeout Software Version ExtremeWare 6.x Hardware Version BlackDiamond Explanation This message indicates that ExtremeWare is unable to write to the RAM. This problem is generally caused by a mis-seating of an MSM or I/O module. Action Remove and re-insert all of the modules in the switch. If the problem persists, RMA the module(s) in question.
Received PDUs from Two Nodes Received PDUs from Two Nodes eaps_runtime.c 1424: Error!! Received "Health-Pdu" from another master [MAC=] Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the EAPS domain configured to be the Master node has received an EAPS PDU from another Master node on the same EAPS domain. This is not allowed. Action You must immediately configure one of the two Master nodes to be a Transit.
Critical Messages Register Failed RR - readRRRegister failed - RR NOT READY port = 18 Software Version ExtremeWare 4.x and 6.x Hardware Version BlackDiamond Summit chipset products Explanation This message indicates that the register on the I/O module (in the case of BlackDiamond) or on the port (in the case of Summit) is not ready. Action This could be a hardware problem. Run diagnostics. If the diagnostic results indicate bad hardware, RMA the I/O module or Summit.
sbmfree Double sbmfree Double sbmfree double (0/-1/0x8b200a1c/0x8b200a2c) Software Version ExtremeWare 6.x Hardware Version All Explanation This message indicates that the switch is attempting to free a memory block that is already freed. The switch will suspend the task for which it is attempting to free the memory. This will generate Exception Program Counter (EPC) task crash errors. Action Contact Technical Support to assist in collecting switch information.
Critical Messages Software Error at Runtime eaps_runtime.c : Bug! Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates a software error and should never appear. Action Contact Technical Support.
Software Error Software Error eaps.c : Bug! Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates a software error and should never appear. Action Contact Technical Support.
Critical Messages Spoofing Attack Possible spoofing attack from 00:81:bb:10:9c:80 port 3:3 Software Version ExtremeWare 4.x Hardware Version All Explanation This message indicates one of the following: • You have a duplicate IP address on the network (same as an address on a local interface). • The IP source address equals a local interface on the router and the packet needs to go up the IP stack (that is, multicast/broadcast).
sysEnvMsg msgQSend Error sysEnvMsg msgQSend Error sysEnvMsgQId: -msgQSend got Error Software Version All ExtremeWare versions Hardware Version All Explanation This message indicates that there is a problem in the environmental system tests like the fan, temperature, or power supply. Action If you have a trap receiver station setup, look for the SNMP trap that might indicate the problem. A busy CPU can also create this error.
Critical Messages System Chunk NULL arptimer 2751 0x82152fdc: System Chunk is NULL Software Version ExtremeWare 6.2.1 and earlier Hardware Version All Explanation This message indicates a software memory error. Action Use the show tech-support and show log commands to capture the log and contact Technical support.
TCP Connection TCP Connection HC: issuePortConnect(0):192.98.8.42:8206 socket 21(L4), error cncting, (errno=55) Software Version All ExtremeWare versions Hardware Version All except VDSL Explanation This message indicates that there is an error for the TCP connection for a particular IP address (192.92.8.42). This error can happen due to multiple reasons. In this example, errorno==55 indicates that it has run out of buffers.
Critical Messages TospfSpfTask Failed Task tospfSpfTask(8663f3c0) failed Software Version All ExtremeWare versions Hardware Version All Explanation This message indicates a crash in the Open Shortest Path First (OSPF) task. Action Use show tech-support and show log commands to capture the log and contact Technical Support.
Twister Access Timeout Twister Access Timeout Twister access timeout slot=2 Software Version ExtremeWare 6.1.x Hardware Version All Explanation This message indicates that ExtremeWare is having problems accessing this particular microchip. Action Reboot the switch. If the error continues, replace the module. The error is indicating hardware problems. If the error is generated while hot-swapping I/O modules, it might be related to your configuration.
Critical Messages VLAN Does Not Exist eaps.c 5217: Error! Vlan "v1"<->Eapsd "eaps1" does not exist Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the request to add a VLAN to the EAPS domain failed because the VLAN does not exist. Action The VLAN has not been added yet, so it cannot be deleted.
VLAN Not Found VLAN Not Found eaps.c 634: Error! Bridge not found for vlanId=1001 Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the VLAN ID receiving EAPS messages does not correspond to any VLANs currently on the system. Action If there is a single message, it can be ignored. If the messages occur on a regular basis, there is probably a software error. Contact Technical Support.
Critical Messages Watchdog Timer Creation Failed eaps.c 397: Error! creating eaps_wdTimer Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the Watchdog timer could not be create during initialization of EAPS. Action The switch may have run out of resources. Contact Technical Support.
Watchdog Timer Reboot Watchdog Timer Reboot The system currently running was restarted due to a hardware watchdog. The task executing when the watchdog took effect was tBGTask. Software Version ExtremeWare 6.19 and later Hardware Version All “i” series Explanation This message indicates a system-level safety network: a device to protect the CPU from certain time-consuming tasks. Action Contact Technical Support to troubleshoot these problematic tasks.
Critical Messages Loop Detected on VLAN Loop Detected on VLAN port sent port received Software Version ExtremeWare 7.3 and later Hardware Version All Explanation Extreme Loop Recovery Protocol (ELRP) has detected a loop on the VLAN. ELRP works with other services such as EAPS, STP and ESRP. The client registers with ELRP to detect loop on the VLAN.
Write to NVRAM Failed Write to NVRAM Failed Cannot write to the NVRAM ELRP Client defaults Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The switch failed to write ELRP client defaults to the NVRAM or Flash. The error could be due to one of the following reasons: • Flash not ready. • Object was not found on NV config. • Object not writable. Action Verify the logs for more information. Retry the command. If problem persists, contact Technical Support.
Critical Messages No Memory Available for VRRP Table no memory available for vrrpTable Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that the switch could not allocate memory resources to create the VRRP table. Action Save the log files and contact Technical Support.
Power Supply Normal Power Supply Normal Internal Power supply back to normal External Power supply back to normal Software Version ExtremeWare 7.5 Hardware Version Summit 400 Explanation The switch periodically checks the internal and external power supply for possible failures. The messages are logged when the internal or external power supply returns to normalcy after a power outage. Action Informational only. No action needed.
Critical Messages Power Supply Failed Internal Power supply failed External Power supply failed Software Version ExtremeWare 7.5 Hardware Version Summit 400 Explanation The switch periodically checks the internal and external power supply for failures. These messages are logged when the internal or external power supply fails. Action Reboot the switch. If the reboot does not fix the problem, contact Technical Support.
Corrupted Backplane Health Check Packet Corrupted Backplane Health Check Packet Backplane health check packet is corrupted in bit slice %d, Compared=0x%x, Actual=0x%x Software Version ExtremeWare 7.5 Hardware Version Alpine, BlackDiamond Explanation The message indicates that the diagnostics has detected a corrupted packet during backplane health check. Action Run the diagnostics on the card. If diagnostics reports any problem, reboot the switch.
Critical Messages Download Configuration File Not Available ERROR: Parse, fd not available Software Version ExtremeWare 7.5 Hardware Version Alpine, BlackDiamond, and Summit Explanation The message indicates that the configuration file was not available while trying to run the command download config a.b.c.d config.txt INCR. Action Reboot the switch, then run the command.
Download Configuration Task Spawn Failed Download Configuration Task Spawn Failed ERROR: Parse, taskSpawn failed Software Version ExtremeWare 7.5 Hardware Version Alpine, BlackDiamond, and Summit Explanation The tdownloadConfigTask task spawn failed while downloading the configuration. Action Reboot the switch, then download the configuration.
Critical Messages Overwrite Download Configuration Buffer Overwrite download configuration buffer Software Version ExtremeWare 7.5 Hardware Version Alpine, BlackDiamond, and Summit Explanation The switch sets the download bit of the configuration flag in CMOS if the configuration was downloaded successfully. Action Informational only. No action needed.
Configuration Download Size Too Large Configuration Download Size Too Large Download size %u too large Software Version ExtremeWare 7.5 Hardware Version Alpine, BlackDiamond, and Summit Explanation The size of the configuration file to be downloaded is larger than the buffer size (9MB) of the switch. Action Verify the configuration.
Critical Messages Error Getting Information on Internal Card Can not find a operational card cardno Software Version ExtremeWare 7.5 Hardware Version Alpine, BlackDiamond, and Summit Explanation Error occurred while obtaining the information on internal card slot that matches the NMC. Action Repeat the diagnostics task. If the problem persists, reboot the hardware and then run the diagnostics. Run diagnostics to isolate the hardware.
Add and Remove Xen Card Add and Remove Xen Card Detected hot plug-in of Xen Card, this must be done while switch is powered down. Please reboot system. Detected hot plug-out of Xen Card, this must be done while switch is powered down. Please reboot system. Software Version ExtremeWare 7.5 Hardware Version Summit 400 Explanation The message indicates that you have tried to add or remove a Xen card while the switch is powered on. Before you add or remove a Xen card, power off the switch.
Critical Messages STPD Tag From Bridge That Ignores BPDU configStpdFilters: Stpd tag is from a bridge that ignores BPDU Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that the switch has received an stpd tag from a bridge that is configured to ignore BPDU. Incoming STP BPDUs will be ignored for the VLAN. Action Disable the ignore BPDU feature for the VLAN.
Receive Task Spawn Failed Receive Task Spawn Failed lsmInit: Could not spawn Rx Task Software Version ExtremeWare 7.3 and later Hardware Version All Explanation During the link status monitoring (LSM) initialization, the task spawn command failed while spawning the LSM receive task. Action Reboot the switch. If the reboot does not fix the problem, contact Technical Support.
Critical Messages Transmission Task Spawn Failed lsmInit: Could not spawn Tx Task Software Version ExtremeWare 7.3 and later Hardware Version All Explanation During the link status monitoring (LSM) initialization, the task spawn command failed while spawning the LSM transmit task. Action Reboot the switch. If the reboot does not fix the problem, contact Technical Support.
LSM Filter: Drop Received Packet LSM Filter: Drop Received Packet lsmFilter: Drop received packet: Task suspended, Port %P Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The link status monitoring (LSM) module has dropped the LSM hello packet received on the port. The LSM receive or LSM transmit task is suspended. Action Reboot the switch. If the reboot does not fix the problem, contact Technical Support.
Critical Messages Hello Receive Timer Creation Failed lsmEnable: Hello Rx timer creation failure, Port %P Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The link status monitoring (LSM) hello receiver timer creation failed while enabling the LSM feature on the port. The LSM remains disabled for the port. Action Reboot the switch. If the reboot does not fix the problem, contact Technical Support.
Memory Allocation Failed Memory Allocation Failed lsmInit: Mbuf Memory Allocation Failure Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The switch could not allocate memory while creating the initial buffer for the link status monitoring module. Action Reboot the switch. If the reboot does not fix the problem, contact Technical Support.
Critical Messages Message Send Failed for Rx Queue on Port sysObjSetLsm: Message Send (CLR_RST - 2) failed for Rx Queue, Port %P Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message posting to the link status monitoring (LSM) Rx Queue failed while enabling the LSM auto restart feature for the port. The auto restart feature for the port will remain disabled. Action Reboot the switch.
Packet Received is Not an LSM Packet Packet Received is Not an LSM Packet lsmFilter: Packet received is not LSM type %d for Port %P Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The packet received on the port by the link status monitoring (LSM) module does not contain the correct EDP TLV type 15. EDP TLV type 15 denotes an LSM packet. The packet is dropped without processing further. Action Informational only. No action needed.
Critical Messages Semaphore Allocation Failed on Port lsmEnable: Semaphore allocation failure, Port %P Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The semaphore allocation failed while enabling the link status monitoring (LSM) feature on the port. The LSM will remain disabled for the port. Action Reboot the switch. If the reboot does not fix the problem, contact Technical Support.
Transmission Message Queue Creation Failed Transmission Message Queue Creation Failed lsmInit: Could not create Tx Message Queue Software Version ExtremeWare 7.3 and later Hardware Version All Explanation During the link status monitoring (LSM) module initialization, the switch failed to create the message queue for the LSM Tx Queue. Action Reboot the switch. If the reboot does not fix the problem, contact Technical Support.
Critical Messages Up Timer Creation Failed lsmEnable: Up timer creation failure, Port %P Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The switch failed to create the link status monitoring (LSM) up timer while enabling the LSM feature on the port. The LSM will remain disabled for the port. Action Reboot the switch. If the reboot does not fix the problem, contact Technical Support.
Access Profile Configuration Restore Failed Access Profile Configuration Restore Failed alistParseNv: Cannot parse alist (%d). Error=0x%x Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that the switch failed to restore the access-profile configuration. Action Retry to configure access-profile. Or Download and save the access-profile configuration.
Critical Messages Access Profile Configuration Entry Restore Failed Invalid Type %d , in alistEntryCfg2Entry Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that the switch failed to restore the access-profile configuration entry. Action Retry to configure access-profile. Or Download and save the access-profile configuration.
Access Profile Configuration Entries Restore Failed Access Profile Configuration Entries Restore Failed alistParseNv: Cannot parse entry (%d). Error=0x%x Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that the switch failed to restore the access-profile configuration entries. Action Retry to configure access-profile. Or Download and save the access-profile configuration.
Critical Messages Cannot Create Security Management List for SSH smlistParseNv: Cannot create smlist for ssh Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that security management access profile for SSH access was not created because the switch could not allocate memory. Action Reconfigure the security management access profile for SSH access. If you see this message repeatedly, contact Technical Support.
Access List with Invalid Pointer or Address Access List with Invalid Pointer or Address Invalid alist_p2i Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that the switch is trying to retrieve an access-profile with an invalid pointer or address. Action Reboot the switch.
Critical Messages Access Profile with Invalid ID Invalid alist_i2p Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that the switch is trying to retrieve an access-profile with an invalid ID. Action Reconfigure the access-profiles. If this does not fix the problem, contact Technical Support.
Cannot Create Access List Instance for SSH Cannot Create Access List Instance for SSH smlistParseNv: invalid alist instance for ssh Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that the switch failed to restore the security management access profile configuration for SSH access. Action Reconfigure the security management access profile for SSH access.
Critical Messages Cannot Create Security Management List for HTTPS smlistParseNv: invalid alist instance for https Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that the switch failed to restore the security management access profile configuration for the secured web access. Action Reconfigure the security management access profile for secured web access.
Invalid Access List Instance for Telnet Invalid Access List Instance for Telnet smlistParseNv: invalid alist instance for telnet Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that the switch failed to restore the security management access profile configuration for telnet access. Action Reconfigure the security management access profile for telnet access.
Critical Messages Invalid Access List Instance for Web smlistParseNv: invalid alist instance for web Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that the switch failed to restore the security management access profile configuration for web access. Action Reconfigure the security management access profile for web access.
Cannot Create Security Management List for Web Cannot Create Security Management List for Web smlistParseNv: Cannot create smlist for web Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that security management access profile for web access was not created because the switch could not allocate memory. Action Reconfigure the security management access profile for web access. If you see this message repeatedly, contact Technical Support.
Critical Messages Cannot Create Security Management List for Telnet smlistParseNv: Cannot create smlist for telnet Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that security management access profile for telnet access was not created because the switch could not allocate memory. Action Reconfigure the security management access profile for telnet. If you see this message repeatedly, contact Technical Support.
Cannot Create Security Management List for HTTPSC Cannot Create Security Management List for HTTPSC smlistParseNv: Cannot create smlist for web Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that security management access profile for secured web access was not created because the switch could not allocate memory. Action Reconfigure the security management access profile for secured web access.
Critical Messages HTTPD Listen Failed ERROR: httpd listen failed Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation The message is logged during the web server TCP initialization. The message indicates that the listen system call, indicating the number of simultaneous connections that can be queued in the web server socket, has failed.
HTTPD Socket Non-blocking IOCTL Failed HTTPD Socket Non-blocking IOCTL Failed ERROR: httpd socket non-blocking ioctl failed Software Version ExtremeWare 7.3 and later Hardware Version All “i“ series and “e“ series Explanation This error message is logged during the web server TCP initialization. The message indicates that the ioctl call for making the newly created web server socket non-blocking has failed.
Critical Messages HTTPD Bind Failed ERROR: httpd bind failed Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation This error message is logged during the web server TCP initialization. The message indicates that the binding of the HTTP port to the newly created socket has failed. HTTP port could be the default port 80 or the configured alternate port.
Rx Buffer Allocation Failed Rx Buffer Allocation Failed ERROR: Could not allocate rx buffer Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation The buffer allocation fails failed during the web server TCP initialization. The web server could be initialized either during the switch startup or while configuring an alternate port using the command enable web access-profile. Action If the error occurs during the switch startup, restart the switch.
Critical Messages Socket Creation Failed ERROR: could not create socket for HTTPD Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation The message is logged during the web server TCP initialization. The message indicates that the switch failed to create the socket for listening and accepting the incoming HTTP and HTTPS connections.
Checksum Error on Slot Checksum Error on Slot Sys-health-check [ACTION] (PBUS checksum) (CARD_HWFAIL_PBUS_CHKSUM_CPU_PKT_DIAG_ERROR) slot 1 Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond, Alpine, and Summit (“i“ series) Explanation The CPU diagnostics detected checksum error on slot 1. This Message also indicates that the system health check has taken configured action on detection of systematic errors. Action Run diagnostics on the card.
Critical Messages Corrupted Packets on Slot Sys-health-check [DIAG] First 16 bytes of unknown pkt on slot 9 Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond, Alpine, and Summit Explanation CPU diagnostics has detected corrupted packets on slot 9. Action Run Show Diagnostics, and then compare the output with log message. If the counter is increasing rapidly, isolate the module.
Card Diagnostic Failed Card Diagnostic Failed Sys-health-check [ACTION] (hardware failure) (CARD_HWFAIL_BLADE_CONTROL_REG_TIMEOUT) slot 1 Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond Explanation The message indicates a card diagnostic failure during the system boot, manual diagnostics, card initialization, or a transceiver test failure. Message also indicates that the system health check has taken configured action on detection of systematic errors.
Critical Messages Registry Operation Timeout Sys-health-check [ACTION] (hardware failure) (CARD_HWFAIL_BLIZZARD_REGOP_TIMEOUT) slot 1 Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond, Summit Explanation The message indicates a card diagnostic failure during the system boot, manual diagnostics, card initialization, or a transceiver test failure. Message also indicates that the system health check has taken configured action on detection of systematic errors.
CPU Control Timeout CPU Control Timeout Sys-health-check [ACTION] (hardware failure) (CARD_HWFAIL_CPU_CNTRL_QUAKE0_TIMEOUT) slot 1 Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond, Summit “i” series Explanation The message indicates a card diagnostic failure during the system boot, manual diagnostics, card initialization, or transceiver test failure. Message also indicates that the system health check has taken configured action on detection of systematic errors.
Critical Messages Registry Operation Timeout Sys-health-check [ACTION] (hardware failure) (CARD_HWFAIL_TSUNAMI_REGOP_TIMEOUT) slot 1 Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond, Summit “i” series Explanation The message indicates a card diagnostic failure during the system boot, manual diagnostics, card initialization, or transceiver test failure. Message also indicates that the system health check has taken configured action on detection of systematic errors.
Corrupted Packets on M-BRD Corrupted Packets on M-BRD Sys-health-check [DIAG] First 16 bytes of unknown pkt on M-BRD Software Version ExtremeWare 6.2 and later Hardware Version Summit Explanation The message indicates that the CPU diagnostics has detected corrupted packets. Action Run diagnostics on the card. If the problem persists, contact Technical Support.
Critical Messages System Restarted by Hardware Watchdog The system currently running was restarted due to a hardware watchdog Software Version ExtremeWare 7.3 and later Hardware Version All Explanation If the system is working properly, various tasks will reset the watchdog timer from time to time. If the watchdog timer is not reset, the timer will restart the system after the timer expires. Action Verify the logs. If you see this message frequently, contact Technical Support.
Task Running During Watchdog Timer Expiry Task Running During Watchdog Timer Expiry The task executing when the watchdog took effect was tPortUtilization. Software Version ExtremeWare 6.2 and later Hardware Version All Explanation The tPortUtilization task was running and crashed while the watchdog timer expired. Action Informational only. No action needed.
Critical Messages Checksum Error on Frame Sys-health-check [CPU] checksum error (slow-path) on M-BRD Software Version ExtremeWare 6.2 and later Hardware Version Summit Explanation The switch fabric has detected an error on a frame destined for the CPU. Action Run diagnostics on the card and replace it, if required.
MSM Rebooted by Slave MSM Rebooted by Slave MSM HAS BEEN REBOOTED BY SLAVE Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond Explanation MSM is normally rebooted by the MSM you have assigned as the master. By default MSM-A is the master. If the master MSM is not active when the system reboots, the slave system resets the master system and takes over the control. Action Verify the cause for last MSM failover using show msm-failover-output.
Critical Messages PtagIndex for Multicast Entries on Threshold Multicast Table Index is below low water mark (ptagMCSnoopIndex) Software Version ExtremeWare 6.2 and later Hardware Version All Explanation The PtagIndex for the multicast entries has reached the threshold level. No more multicast entries will be created. Action Clear IGMP snooping and IP multicast FDB. If present, clear the IP multicast cache.
EDP Frame in Wrong Format EDP Frame in Wrong Format Sys-health-check [EDP] error on slot 7 Software Version ExtremeWare 6.2 and later Hardware Version All Explanation The CPU has received an EDP frame in wrong format. The data would have been corrupted in the I/O module or MSM. Action Informational only. No action needed.
Critical Messages Failed to Clear Log On Slot Statistics clear failed on slot 9 internal port –2045 Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond, Summit Explanation The switch failed to clear the log on slot 9. Action Reset the slot. If the problem persists, contact Technical Support.
Session Timeout While Accessing FDB Table Session Timeout While Accessing FDB Table Failed in quakeFdbBusyWait slot 1 Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond and Summit Explanation The session timed out while the ASIC was accessing the FDB table. Action Reboot the card. Run diagnostics to figure out whether the problem is related to hardware or timing. If problem persists, contact Technical Support.
Critical Messages FDB Timeout Sys-health-check [ACTION] (hardware failure) (CARD_HWFAIL_FDB_QUAKE0_TIMEOUT) slot 1 Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond, Alpine, and Summit Explanation The message indicates a card diagnostic failure during the system boot, manual diagnostics, card initialization, or transceiver test failure. Message also indicates that the system health check has taken configured action on detection of systematic errors.
System Recovery Action System Recovery Action sys-recovery: none Software Version ExtremeWare 6.2 and later Hardware Version All Explanation The system recovery action is set to none. You can configure the system recovery action. If something goes wrong in the system, such as software exception, the switch recovers using the action you have set.
Critical Messages Mismatch Between Power Supply Types CONFIGURATION NOT RECOMMENDED! PSU-A is a DC power supply and the other is AC Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond, Alpine Explanation There is a mismatch between power supply types of the PSUs. Action Use PSUs with the same type of power supply; DC or AC.
EDP Frame with Bad Length EDP Frame with Bad Length Sys-health-check [EDP] bad length Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond Explanation The CPU has received an EDP frame in a wrong format. The data would have been corrupted in the I/O module or MSM. Action Informational only. No action needed.
Critical Messages System Initialized in Minimum Mode System has not been initialized Software Version ExtremeWare 6.2 and later Hardware Version All Explanation System reboots in minimum mode due to diagnostics failure. Action Clear log diagnostics status and reboot the system. If the problem persists, run the command unconfigure switch-all. Reboot the system.
Error Reading MAC Error Reading MAC slot 6 Error Reading MAC Software Version ExtremeWare 7.3 and later Hardware Version BlackDiamond and Alpine Explanation The switch was not able to read the MAC address while the connection down log was executed. Action Reset the card. If you still face the problem, reboot the system. If the problem persists, contact Technical Support.
Critical Messages Error While Reading Register Error: tsunamiWriteReg: Slot 6 port 2 reg e not ready Software Version ExtremeWare 7.3 and later Hardware Version BlackDiamond Explanation Error occurred while tsunami ASIC tried to read register e of port 2 on slot 6. The switch will take the action configured using sys-health-check. If you have configured sys-health-check to shut down the card, the card is set to non-operational.
Diagnostics Failed Diagnostics Failed Sys-health-check [ACTION] (hardware failure) (CARD_HWFAIL_QD_RAM_QUAKE0_TIMEOUT) slot 6 Software Version ExtremeWare 7.3 and later Hardware Version BlackDiamond, Alpine, and Summit Explanation The message indicates a card diagnostic failure during the system boot, manual diagnostics, card initialization, or transceiver test failure. Message also indicates that the system health check has taken configured action on detection of systematic errors.
Critical Messages Error Accessing FDB Information Failed to write Fdb slot 6 Software Version ExtremeWare 7.3 and later Hardware Version BlackDiamond Explanation The system faced problem while accessing FDB information from the ASIC. Action Reset the card. If the problem persists, run diagnostics on the hardware. Contact Technical Support, if required.
AFC Status Timeout AFC Status Timeout Sys-health-check [ACTION] (hardware failure) (CARD_HWFAIL_AFC_STATUS_QUAKE1_TIMEOUT) slot 6 Software Version ExtremeWare 7.3 and later Hardware Version BlackDiamond, Alpine, and Summit Explanation The message indicates a card diagnostic failure during the system boot, manual diagnostics, card initialization, or transceiver test failure. Message also indicates that the system health check has taken configured action on detection of systematic errors.
Critical Messages No Memory Available for vlanBtreeAttach No memory available for vlanBtreeAttach Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that the system is not able to allocate memory to add the newly allocated VLAN specific node to the data structure. Action Reboot the system. If the problem persists, contact Technical Support.
Access Profile Configuration with Invalid Index Access Profile Configuration with Invalid Index sysObjGetAlist: Invalid instance Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that ExtremeWare is trying to lookup an access profile configuration, but the access profile does not have a valid index. If this message appears repeatedly, it indicates that any of the modules (such as, BGP) using this access profile is corrupted. Action Reboot the system.
Critical Messages Configuring Access Profile Using Invalid Index sysObjTestAlist: Invalid gmID Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that ExtremeWare is trying to configure an access-profile using an invalid access-profile index. Action Delete the access-profile configuration and add the configuration again.
Corrupted CPU Health Check Packet Corrupted CPU Health Check Packet CPU health check packet is corrupted in bit slice %d, Compared=0x%x, Actual=0x%x Software Version ExtremeWare 7.5.x Hardware Version BlackDiamond, Alpine Explanation The switch has detected a corrupted health check packet during the CPU diagnostics. Action Reboot the system and perform the task again.
Critical Messages PSU(id) Removed PSU(id) removed Software Version ExtremeWare 7.5.x Hardware Version BlackDiamond, Alpine, and Summit Explanation The message indicates that the power supply has been removed from the switch. Action Check the power supply unit.
Fast Path Checksum Threshold Exceeded Fast Path Checksum Threshold Exceeded Fast-path checksum threshold exceeded on %s Software Version ExtremeWare 7.5.x Hardware Version BlackDiamond, Alpine, and Summit Explanation The number of packets with checksum failure exceeded the configured fast-path threshold. Action Reboot the slot.
Critical Messages Invalid Card State CARD STATE for card %d invalid Software Version ExtremeWare 7.5.x Hardware Version BlackDiamond, Alpine, and Summit Explanation The switch has detected an invalid card state. Action Disable and enable the card.
Invalid Event in Checksum Failure Invalid Event in Checksum Failure Invalid chksum error type [%x] for %s Software Version ExtremeWare 7.5.x Hardware Version BlackDiamond, Alpine, and Summit Explanation The switch has detected invalid event while updating the statistics for checksum failure. Action If the problem persists, reboot the system.
Critical Messages Missed System-Health-Check Packet Sys-health-check [DIAG] pkt missed (slow-path) on %s %s Software Version ExtremeWare 7.5.x Hardware Version BlackDiamond, Alpine Explanation The message indicates that a packet was missed during CPU diagnostics. Action Reboot the system and perform the task again.
Power Supply Temperature Failed Power Supply Temperature Failed PSU(id) temperature failure Software Version ExtremeWare 7.5.x Hardware Version BlackDiamond, Alpine, and Summit Explanation The message indicates that a temperature failure was detected in the power supply unit. Action Check the power supply unit. If problem occurs again, contact Technical Support.
Critical Messages Power Supply Unit: Fan Failed PSU(id) fan failure Software Version ExtremeWare 7.5.x Hardware Version BlackDiamond, Alpine, and Summit Explanation The message indicates that the fan in the power supply unit has failed. Action Check the power supply unit. If problem occurs again, contact Technical Support.
Power Supply Unit: Input failure Power Supply Unit: Input failure PSU(id) input failure Software Version ExtremeWare 7.5.x Hardware Version BlackDiamond, Alpine, and Summit Explanation The message indicates that the input to the power supply unit has failed. Action Check the power supply unit. If problem persists, contact Technical Support.
Critical Messages LSM Transmit Task Message Queue Receive Failed ELSM Tx Task Msg Queue receive failed Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that the message queue receive function for the LSM (Link Status Monitoring) transmit task failed. The task continues to wait for further messages. Action If the problem persists, reboot the system.
LSM Receive Task Message Queue Receive Failed LSM Receive Task Message Queue Receive Failed LSM Rx Task Msg Queue receive failed Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that the message queue receive function for the LSM (Link Status Monitoring) receive task failed. The task continues to wait for further messages. Action If the problem persists, reboot the switch.
Critical Messages LSM Receive Task: Unable to Start Timer lsmRxTask: Unable to start lsmProcTimer, error %d, Retry in 5s Software Version ExtremeWare 7.3 and later Hardware Version BlackDiamond, Alpine, and Summit Explanation The message indicates that the LSM (Link Status Monitoring) receive task timer failed to start. Whenever this happens, the switch waits for five seconds to start the timer again. Action If timer restart fails continuously, reboot the system.
Cannot Write to CFGDB Port Cannot Write to CFGDB Port Cannot write to CFGDB Port Software Version ExtremeWare 7.3 and later Hardware Version All Explanation During reboot, the LSM (Link Status Monitoring) module generates default values and tries to store the values in the NVRAM. This message indicates that the switch failed to write the values to NVRAM. Action Reboot the switch. If problem persists, contact Technical Support.
Critical Messages Unicast Route is a Blackhole Route pimRtLookup: for , got blackhole route to Software Version ExtremeWare 7.3 and later Hardware Version All ”i” series and Summit “e” series Explanation This error is generated when the unicast route chosen to reach RP or source is a blackhole route. Action 1 Add a unicast route to reach the RP or the source. 2 Configure the route to choose the new unicast route as the preferred route.
MSM-B HAS TAKEN OVER AS THE MASTER MSM-B HAS TAKEN OVER AS THE MASTER MSM-B HAS TAKEN OVER AS THE MASTER Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond Explanation This message indicates that MSM-B has taken over as the master. By default MSM-A is the master. Action This message is informational only.
Critical Messages PSU-A Removed PSU-A removed Software Version ExtremeWare 6.2 and later Hardware Version Alpine Explanation This message indicates that PSU-A has been removed from the switch. Action This message is informational only.
Diagnostic Failures Diagnostic Failures System has recorded diag failures Software Version ExtremeWare 6.2 and later Hardware Version Alpine Explanation The message indicates that the switch has detected hardware failure during diagnostic; either through sys-health check or by running diagnostics. Action Check the hardware and replace it, if necessary.
Critical Messages Out of Memory While Allocating Agent X Request Out of memory while allocating agent x request Software Version ExtremeWare 7.3 and later Hardware Version Altitude 350, Altitude 350-2, and Summit WM series Explanation This message indicates that the switch was not able to allocate memory for the task. Action 1 Save the log file. 2 Contact Technical Support.
Ping Control Table Full Ping Control Table Full Reached the upper limit of pingindex Software Version ExtremeWare 7.3 and later Hardware Version Altitude 350, Altitude 350-2, and Summit WM series Explanation The message indicates that the ping control table is full. Action Delete entries from the ping control table and enter the command.
Critical Messages Adding L2 FDB Entry for a Port Failed failed arl add unit for : status: Software Version ExtremeWare 7.3 Hardware Version Summit “e” series (S300-48) Explanation The message indicates that the switch failed to add anL2 FDB (Forwarding Database) entry corresponding to a port other than the CPU port. Action Restart the switch.
Adding L2 FDB Entry for CPU Port Failed Adding L2 FDB Entry for CPU Port Failed failed CPU arl add unit for : status: Software Version ExtremeWare 7.3 Hardware Version Summit “e” series (S300-48) Explanation The message indicates that the switch failed to add an L2 FDB (Forwarding Database) entry corresponding to a CPU port. Action Restart the switch.
Critical Messages Deleting L2 FDB Entries Failed failed fdb all port flush unit status: Software Version ExtremeWare 7.3 Hardware Version Summit “e” series (S300-48) Explanation The message indicates that the switch failed to delete the L2 FDB (Forwarding Database) entries from all the units. The entries are deleted port by port starting from 0 to the maximum number of ports on the switch. Action Restart the switch.
Deleting L2 FDB Entry for VLAN Failed Deleting L2 FDB Entry for VLAN Failed failed fdb vlan flush for unit vlan status: Software Version ExtremeWare 7.3 Hardware Version Summit “e” series (S300-48) Explanation This message indicates that the switch failed to delete the L2 FDB (Forwarding Database) entries corresponding to a specific VLAN from all units in S300-48. Action Restart the switch.
Critical Messages Initializing the Switch Failed failed Init unit : Software Version ExtremeWare 7.3 Hardware Version Summit “e” series (S300-48) Explanation The message indicates that the switch failed to initialize the unit in S300-48. Action Restart the switch.
Power Consumption Exceeds Reserved Power Power Consumption Exceeds Reserved Power Power consumption exceeds the amount of reserve power Software Version ExtremeWare 7.5 Hardware Version BlackDiamond Explanation The message indicates that the switch is consuming more power than the power reserved. Action Check the power supply unit. If the error appears again, contact Technical Support.
Critical Messages Power Supply Unit: Memory Allocation Failed Failed to allocate memory for ps units Software Version ExtremeWare 7.5 Hardware Version Alpine, BlackDiamond Explanation The message indicates that the switch failed to allocate memory for the power supply unit during initialization. Action Restart the switch. If the error appears again, contact Technical Support.
Power Consumption Exceeds Minimum Required Level Power Consumption Exceeds Minimum Required Level Power consumption exceeds minimum required power levels Software Version ExtremeWare 7.5 Hardware Version BlackDiamond Explanation The message indicates that the power consumption exceeds the minimum required levels. Action Check the power supply. If you see the problem again, contact Technical Support.
Critical Messages Switch Operating Below Minimum Required Power The system is operating below minimum required power levels Software Version ExtremeWare 7.5 Hardware Version BlackDiamond Explanation The message indicates that the switch is operating below minimum required power levels. This may be due to issues with the power supply unit. Action Check the power supply. If the error appears again, contact Technical Support.
Old and New AC Power Supply On the Switch Old and New AC Power Supply On the Switch A configuration of old and new AC power supplies is not valid for this system Software Version ExtremeWare 7.5 Hardware Version BlackDiamond Explanation The message indicates that you have configured new and old power supply on the same switch. You cannot configure old and new power supply on the same switch. Action Use the same type of power supply on the system.
Critical Messages AC and DC Power Supply Configured on the Switch A configuration of AC and DC power supplies is not allowed Software Version ExtremeWare 7.5 Hardware Version BlackDiamond Explanation The message indicates that you have configured both AC and DC power supply on the same switch. Configure either AC power supply or DC power supply. Action Use the same type of power supply on the switch.
Power Supply Mismatch Power Supply Mismatch CONFIGURATION NOT RECOMMENDED! %s is a DC power supply and the other is DC-J Software Version ExtremeWare 7.5 Hardware Version Alpine, BlackDiamond Explanation The message indicates that one power supply unit on the switch is using DC and the other power supply unit is using DC-J. You cannot use different type of power supply units on the same switch. Action Use same type of power supply.
Critical Messages Power Supply Mismatch CONFIGURATION NOT RECOMMENDED! %s is a DC power supply and the other is AC Software Version ExtremeWare 7.5 Hardware Version Alpine, BlackDiamond Explanation The message indicates that one power supply unit on the switch is DC and the other power supply unit is AC. Use power supply of same type; either both AC or both DC. Action Change one of the power supplies to AC or DC, so that both the power supply units will be of the same type.
Single and Dual AC Power Supply Configuration Single and Dual AC Power Supply Configuration A configuration of single and dual AC power supplies is not recommended Software Version ExtremeWare 7.5 Hardware Version BlackDiamond Explanation The message indicates that you have configured single and dual AC power supplies on the switch. You must not configure single and dual AC power supplies on the same switch. Action Configure the same type of power supplies.
Critical Messages Cannot Write to CFGDB Global Cannot write to CFGDB Global Software Version ExtremeWare 7.3 Hardware Version All “i” series Explanation This message indicates that the switch was failed to write to the CFGDB global while generating the default configuration for the SFLOW module. Action Reboot the switch. If the error appears again, contact Technical Support.
Cannot Write to CFGDB Sflow Port Cannot Write to CFGDB Sflow Port Cannot write to CFGDB Sflow Port Software Version ExtremeWare 6.2 and later Hardware Version All “i” series Explanation This message indicates that the switch was not able to write to the CFGDB global while generating the default configuration for the SFLOW module. Action Reboot the switch. If the error appears again, contact Technical Support.
Critical Messages SFLOW: Configuration Parsing Failed Config parse failure for Sflow Global error Software Version ExtremeWare 7.3 Hardware Version All “i” series Explanation This message indicates that the switch failed to parse the configuration while restoring the configuration for SFLOW module. Action Contact Technical Support.
SFLOW: Configuration Parsing Failed for Port SFLOW: Configuration Parsing Failed for Port Config parse failure for port error Software Version ExtremeWare 7.3 Hardware Version All “i” series Explanation This message indicates that the switch failed to parse the configuration for the port while restoring the configuration for SFLOW module. Action Contact Technical Support.
Critical Messages Allocating IP SA Entry Failed Failed to allocate IP SA entry SA= Redirect rule= Software Version ExtremeWare 7.3 Hardware Version All “i” series Explanation The message indicates that the switch failed to allocate IP SA entry while adding a flow-redirect entry. Action Reboot the switch. If the error persists, contact Technical Support.
Corrupted EDP PDU: Bad OUI Corrupted EDP PDU: Bad OUI Sys-health-check [EDP] bad OUI (oui1:oui2:oui3) port Software Version ExtremeWare 7.2 Hardware Version All “i” series Explanation The message indicates that during the health check process the sys-health-check module received an EDP PDU with error. Action Contact Technical Support.
Critical Messages Corrupted EDP PDU: Bad Length Sys-health-check [EDP] bad length port Software Version ExtremeWare 7.2 Hardware Version All “i” series Explanation This message indicates that during the health check process the sys-health-check module received an EDP PDU with errors. Action Contact Technical Support.
Corrupted EDP PDU: Bad Version Corrupted EDP PDU: Bad Version Sys-health-check [EDP] bad version port Software Version ExtremeWare 7.2 Hardware Version All “i” series Explanation This message indicates that during the health check process the sys-health-check module received an EDP PDU with error. Action Contact Technical Support.
Critical Messages Corrupted EDP PDU: Bad SNAP Sys-health-check [EDP] bad SNAP port Software Version ExtremeWare 7.2 Hardware Version All “i” series Explanation This message indicates that during the health check process the sys-health-check module received an EDP PDU with error. Action Contact Technical Support.
Configuring Hardware Queue Before Starting the Card Configuring Hardware Queue Before Starting the Card pifDefaultQCfgBCM %d slot %d invalid num slices %d Software Version ExtremeWare 7.3 and later Hardware Version All “e” series Explanation This message indicates an error while configuring the number of packet buffers per hardware queue. This indicates that the switch may be trying to configure the hardware queues before the cards are fully initialized. Action Check whether the message appears again.
Critical Messages No Memory In Bind to Route-map No more memory in bindToRtMap Software Version ExtremeWare 7.3 and later Hardware Version BlackDiamond, Summit, Alpine, "i" series,"e" series Explanation This message indicates that the switch is unable to allocate memory to bind a function to a route-map. This may be due to high memory usage. Action Configure the switch to use less memory and then retry.
Disable ARP Learning Disable ARP Learning Disable ARP learning Global Config parse failure error Software Version EW 7.3 and later Hardware Version BlackDiamond, Summit, Alpine, "i" series,"e" series Explanation This message indicates the switch is not able to read the configuration related to disable arp-learning. Action 1 If you are not using disable arp-learning feature, ignore this message. If you are using disable arp-learning feature, reconfigure disable arp-learning and save the configuration.
Critical Messages Port List Not Present For Unbind Port list not present for unbind, master=%P,slave=%P Software Version EW 7.5 and later Hardware Version BlackDiamond, Summit, Alpine, "i" series,"e" series Explanation The message indicates that the switch was not able to retrieve the port list from the master port. Action Restart the switch. If the problem appears again, contact Technical Support.
Loadshare Port List: Memory Allocation Failed Loadshare Port List: Memory Allocation Failed Mem not available for loadshare port list, reboot required Software Version EW 7.3 and later Hardware Version BlackDiamond, Summit, Alpine, "i" series,"e" series Explanation The message indicates that the switch was not able to allocate memory to create load share port list. Action Restart the switch. If the problem appears again, contact Technical Support.
Critical Messages MAC Lock Age Task Message: Receive Failed Mac lock age task message receive failure Software Version EW 7.5 and later Hardware Version BlackDiamond, Summit, Alpine, "i" series,"e" series Explanation This message indicates that the task tFdbMacLockAgeTask is unable to receive messages to age out the entries learnt on a port with mac-lockdown enabled.
VLAN Creation At Startup Failed VLAN Creation At Startup Failed MacVlanDiscover vlan could not be created at startup Software Version ExtremeWare 7.3 and later Hardware Version BlackDiamond, Summit, Alpine, "i" series,"e" series Explanation This message indicates the switch failed to create MacVlanDiscover VLAN. Action 1 Restart the switch. 2 Upload the configuration and download the configuration back to the switch. 3 If the message appears again, contact Technical Support.
Critical Messages Invalid Route Map Instance Invalid Route Map Instance Software Version ExtremeWare 7.3and later Hardware Version BlackDiamond, Summit, Alpine, "i" series,"e" series Explanation This message indicates that the switch is trying to access a route-map using an invalid instance. Action Restart the switch. If the message appears again, contact Technical Support.
Invalid Route Map Pointer Invalid Route Map Pointer Invalid Invalid Invalid Invalid Route Route Route Route Map Map Map Map Pointer Entry Pointer Entry Instance %d Statement Pointer Software Version ExtremeWare 7.3 and later Hardware Version BlackDiamond, Summit, Alpine, "i" series,"e" series Explanation This message indicates that system is trying to access a route-map or route-map entry using an invalid instance or an invalid pointer. Action Restart the switch.
Critical Messages Adding Entry to Empty Route Map Failed Cannot add entry to empty rtmap Software Version ExtremeWare 7.3 and later Hardware Version BlackDiamond, Summit, Alpine, "i" series,"e" series Explanation This message indicates the switch is trying to add an entry to a route-map that was already deleted from the switch. Action 1 Check whether the route map is present; use CLI command show route-map. 2 If the route-map is not present, create a route-map and add the route-map entry.
Free Entry Not Available Free Entry Not Available Free Entry not available Software Version ExtremeWare 7.3 and later Hardware Version BlackDiamond, Summit, Alpine, "i" series,"e" series Explanation This message indicates you have configured maximum number of route-maps on the switch. Action Informational only. No action needed.
Critical Messages VRRP Initialization: Queue Creation Failed vrrpInit: Q create failed Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that the switch failed to create the queue while initializing the VRRP. Action 1 Check the log for details. 2 Restart the switch. If the problem appears again, contact Technical Support.
VRRP Initialization: Task Spawn Failed VRRP Initialization: Task Spawn Failed vrrpInit: taskSpawn failed Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that the switch failed to spawn the task while initializing the VRRP. Action 1 Check the log for details. 2 Restart the switch. If the problem appears again, contact Technical Support.
Critical Messages VRRP: Unable To Start WD Timer VRRP: Unable to start WD timer! Retry in 5 sec Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that the switch failed to start the WD timer for VRRP. The switch will retry to start the timer in 5 seconds. Action 1 Check the log for details. 2 Check whether the switch corrects the problem in the specified time period. 3 After the specified time period, restart the switch.
VRRP: Memory Allocation Failure VRRP: Memory Allocation Failure vrrpAlloc: sbmalloc failure. size= Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that the switch failed to allocate memory for VRRP. This may be due to insufficient resources. Action Check the logs for details. If this is not a temporary condition caused due to traffic burst, contact Technical Support.
Critical Messages System Health Check: Bad Length Sys-health-check [EDP] bad length (%x, %x) %s, port 0x%x", pdu->length, packetlength, slotName(rootSlot), portNum); Software Version ExtremeWare 7.4 Hardware Version All Explanation The message indicates that the switch has received an EDP packet with wrong length. The log displays the slot and port numbers on which the EDP packet was received. Action 1 Find the device that is transmitting the wrong EDP packet.
System Health Check: Bad SNAP System Health Check: Bad SNAP Sys-health-check [EDP] bad SNAP (%x, %x) %s, port 0x%x", hdr->llcSnap.type, ntohs(EDP_SNAP_ID), slotName(rootSlot), portNum) Software Version ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the EDP packet received has a wrong SNAP type. The log displays the slot and port numbers on which the wrong EDP packet was received. Action 1 Find the device that is transmitting the wrong EDP packet.
Critical Messages System Health Check: Bad OUI Sys-health-check [EDP] bad OUI (%02x:%02x:%02x) %s, port 0x%x", hdr->llcSnap.oui[0], hdr->llcSnap.oui[1], hdr->llcSnap.oui[2],slotName(rootSlot), portNum); Software Version ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation This message indicates that the switch has received an EDP packet with wrong OUI type. The log provides details on the slot and port numbers on which the wrong EDP packet was received.
Writing To EEPROM Not Supported Writing To EEPROM Not Supported Do not support EEPROM write for device number Software Version ExtremeWare 7.5 Hardware Version BlackDiamond Explanation The message indicates that the switch does not support the write operation on the EEPROM device. Action Informational only. No action needed.
Critical Messages Message Queue Creation Failed Message queue creation failure Software Version ExtremeWare 7.3, 7.4, 7.5 Hardware Version All Explanation The message indicates that the switch failed to create the message queue. Action Restart the switch.
PTag Allocation Failed PTag Allocation Failed Ptag allocation failure Software Version ExtremeWare 7.3, 7.4, 7.5 Hardware Version All Explanation The message indicates that the switch failed to allocate Ptag. The Ptag table may be full. Action Restart the switch or stop the process which consumes more ptag in the memory.
Critical Messages Read EEPROM Failed Read of EEPROM failure (%d) Software Version ExtremeWare 7.3, 7.4, 7.5 Hardware Version All Explanation The message indicates that the switch could not read the MAC address from the EEPROM. Action Restart the switch and then try. If the problem appears again, contact Technical Support.
STP Domain Allocation Failed STP Domain Allocation Failed • STP domain allocation failure • STP domain table allocation failure Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the switch could not allocate memory for the STP domain. Action 1 Restart the switch. 2 Delete the STP domain. 3 Create the STP domain.
Critical Messages Task Creation Failed Task creation failure (%d, %d) Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the switch failed to create the task. Action Restart the switch.
Timer Bucket Allocation Failed Timer Bucket Allocation Failed Timer bucket allocation failed Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the switch failed to allocate memory for the STP timer. Action Check the hardware and replace it, if necessary.
Critical Messages Failed To Allocate Memory For VLAN sbmalloc(%d) failure Software Version ExtremeWare 7.3, 7.4, 7.5 Hardware Version All Explanation The message indicates that the switch failed to allocate memory for the VLAN associated with the STP domain. Action Restart the switch.
Transmit Mbuf Allocation Failed Transmit Mbuf Allocation Failed transmit mbuf allocation failure (%p/%p/%p) Software Version ExtremeWare 7.3, 7.4, 7.5 Hardware Version All Explanation The message indicates that the switch could not allocate memory for mbuf. Action Restart the switch.
Critical Messages System Health Check: Bad Version Sys-health-check [EDP] bad version (%x) %s,port 0x%x", pdu->edpVersion, slotName(rootSlot), portNum); Software Version ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the version of the received EDP has a wrong value. The log displays the slot and port numbers on which the wrong EDP packet was received. Action 1 Find the device that is transmitting the wrong EDP packet.
System Health Check: Checksum Error System Health Check: Checksum Error Sys-health-check [EDP] checksum error (slow-path) on %s, port 0x%x %s", slotName(rootSlot), portNum, serial_no); Software Version ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the switch has received an EDP packet with a wrong checksum. The log displays the slot and port numbers on which the wrong EDP packet was received.
Critical Messages VRRP Allocation: Memory Failure vrrpAlloc: sbmalloc failure. size= Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates an error in the memory sub-system. This could be due to insufficient resources. Action Check the logs for details. If this is not a temporary condition caused due to traffic burst, contact Technical Support.
Failed to Change MAC Address on Port Failed to Change MAC Address on Port Failed to change MAC address on port Software Version ExtremeWare 7.3 and later Hardware Version All “i” series Explanation This message indicates that the switch failed to update the MAC address in the router table. This may be due to a version mismatch of the chipset. Action Contact Technical Support.
Critical Messages Unable to Clear Netlogin Entry for MAC Unable to clear Netlogin entry for Software Version ExtremeWare 7.3 and later Hardware Version Cards that support wireless ports. Such as, Altitude 350, Summit WM100, and Summit WM1000. Explanation The message indicates that the switch failed to clear a netlogin MAC entry from the station table and bridge. Action Verify the logs for details.
Remote Set Request Not Implemented Remote Set Request Not Implemented Remote set request for member not yet implemented (Interface) Software Version ExtremeWare 7.3 and later Hardware Version Cards that support wireless ports. Such as, Altitude 350, Summit WM100, and Summit WM1000. Explanation The message indicates that the switch does not support the specified SNMP set requests. Action See the documentation for a list of supported set requests for the ExtremeWare release.
Critical Messages Memory Allocation for Bridge-Interface Failed EAPS Shared-port 1:1 - Out of memory. Cannot malloc Bridge-interface for vlan %s, port %P Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the EAPS super domain (ESD) failed to allocate memory for Bridge interface for VLAN. Action 1 Check the available memory on the switch. 2 Reboot the switch to free up memory for the ESD process.
Memory Allocation for Segment Interface Failed Memory Allocation for Segment Interface Failed EAPS Shared-port 1:1 - Out of memory. Cannot malloc Segment-interface Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the EAPS super domain (ESD) failed to allocate memory for the segment-interface. Action 1 Check the available memory on the switch. 2 Reboot the switch to free up memory for the ESD process.
Critical Messages Memory Allocation for ESD Domain Failed Out of memory. Cannot malloc ESD domain. Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the EAPS super domain (ESD) failed to allocate memory for the ESD Domain. Action 1 Check the available memory on the switch. 2 Reboot the switch to free up memory for ESD process. If you notice any issues such as memory leak, contact Technical Support.
Hello Timer Creation Failed Hello Timer Creation Failed EAPS Shared-port 1:1 - Cannot create Hello-timer Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the EAPS super domain (ESD) failed to create a hello-timer. This could occur if the switch could not allocate memory for the hello-timer. Action 1 Check the available memory on the switch. 2 Reboot the switch to free up memory for the ESD process.
Critical Messages Fail Timer Creation Failed EAPS Shared-port 1:1 - Cannot create Fail-timer. Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the EAPS super domain (ESD) failed to create the fail-timer. This could occur if the switch could not allocate memory for the fail-timer creation process. Action 1 Check the available memory on the switch. 2 Reboot the switch to free up memory for the ESD process.
No EAPS Domain on the Control VLAN No EAPS Domain on the Control VLAN Received ESD PDU on Vlan Id (%d). No EAPS domain found with this as Control vlan Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the switch has received EAPS super domain (ESD) PDU on a VLAN that is not configured as a control VLAN for the EAPS domain. Action Add the vlan as control vlan to EAPS domain.
Critical Messages Segment Timer Creation Failed EAPS Shared-port Segment-Port 2:1 - Cannot create Segment-timer Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the EAPS super domain (ESD) failed to create a segment-timer. This could occur if the switch could not allocate memory for the segment-timer creation process. Action 1 Check the available memory on the switch. 2 Reboot the switch to free up memory for the ESD process.
Shared Port Timer Creation Failed Shared Port Timer Creation Failed EAPS Shared-port 1:1 - Cannot create Shared-port-timer Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the EAPS super domain (ESD) failed to create a shared port-timer. This could occur if the switch could not allocate memory for the shared port timer. Action 1 Check the available memory on the switch. 2 Reboot the switch to free up memory for the ESD process.
Critical Messages EAPSD: Multiple Masters On Same EAPS Domain EAPS: EAPSD eaps1a - Multiple Masters on the same EAPS domain. Received Health-Pdu from another master [MAC=00:01:30:3d:99:00] Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation The message indicates that another EAPS master domain exists on the same EAPS ring.
EAPSD: Fail Timer Expired While State Is Init EAPSD: Fail Timer Expired While State Is Init EAPS: EAPSD eaps-up - Fail timer expired, while state is Init Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the fail timer on the EAPS master domain has expired, but the EAPS master has not received any healthcheck PDU on the secondary port.
Critical Messages System Rebooted Due to Stack Merge System rebooted due to stack merge. Prev Master found Software Version ExtremeWare 7.7 and later Hardware Version All “i” and “e” series Explanation This message indicates the switch restarted due to a stack merge. Action No action needed. This message is informational only.
System Rebooted Due to Discovery Failure System Rebooted Due to Discovery Failure System rebooted due to discovery failure :%d Num timeouts : %d Software Version ExtremeWare 7.7 and later Hardware Version All “i” and “e” series Explanation This message indicates that the switch restarted due to failure in the discovery process.
Critical Messages 274 ExtremeWare Error Message Decoder
4 Error Messages Error messages indicate problems that require corrective action, but not immediately. Check the “Issues Resolved In” sections in the latest ExtremeWare Installation and Release Notes to see if the error message indicates an issue that has been corrected in a recent software release. Boot ROM Version Download Error ERROR: The Boot ROM you have downloaded cannot boot the ExtremeWare images that are installed on this system. The boot ROM will not be written to the flash.
Error Messages Boot ROM Version Synchronization Error Error: execution of the command failed Attempt to sync incorrect BootROM version 7.8 for MSM-3 MSM-3 requires BootROM version 8.1 or greater Software Version ExtremeWare 7.1.1 and later Hardware Version BlackDiamond with MSM-3 Explanation This message indicates that an attempt was made to synchronize an incompatible version of Boot ROM to an MSM-3 module. MSM-3 requires Boot ROM version 8.1 or greater.
Cannot Create VLAN Cannot Create VLAN ERROR: Cannot create vlan "IN_test" Hardware resource is not available (2/0) Software Version ExtremeWare 7.0.0 and later Hardware Version All Explanation This error appears on the console when you are trying to create a VLAN and the hardware resource is not available. You need hardware resources to create a VLAN. For example, you need some PTAGs (OTPs) to hold all ports in the vlan for broadcast and unknown destination packets.
Error Messages Committed Rate Exceeded for Port ERROR: max allowable committed-rate exceeded for port 1:1 Software Version ExtremeWare 7.1.0 and later Hardware Version BlackDiamond and Alpine High-Density Gigabit Ethernet modules (G16X3, G24T3, GM-16X3, and GM-16T3) Explanation This message indicates that the maximum allowable ingress committed-rate for the indicated port will be exceeded if the attempted ingress QoS configuration is allowed.
Delete FDB Entry Delete FDB Entry MSM64:139 # delete coconut1 updateEdpFilter: Trying to double del Deleted vlan coconut1 Software Version ExtremeWare 2.x, 4.x, and 6.x Hardware Version All Explanation These messages indicate that the switch is trying to delete an FDB entry that is not available at the moment you are deleting the VLAN. Action No action is necessary.
Error Messages ExtremeWare Download Error, Version Incompatible The ExtremeWare version being downloaded is 7.0.1b13. ERROR: This system requires ExtremeWare version 7.1.1 or greater Software Version ExtremeWare 7.1.1 and later Hardware Version BlackDiamond with MSM-3 Explanation This message indicates that an attempt was made to download an incompatible version of ExtremeWare to an MSM-3 module (either the master or slave). MSM-3 requires version 7.1.1 or greater.
ExtremeWare Synchronization Error, Version Incompatible ExtremeWare Synchronization Error, Version Incompatible Error: execution of the command failed Attempt to sync incorrect E-Ware version 7.0.1 for MSM-3 MSM-3 requires E-Ware version 7.1.1 or greater Software Version ExtremeWare 7.1.1 and later Hardware Version BlackDiamond with MSM-3 Explanation This message indicates that you tried to synchronize an incompatible version of ExtremeWare to an MSM-3 module.
Error Messages ExtremeWare Version Incompatible Error: execution of the command failed Attempt to use incorrect E-Ware version 7.0.1 for MSM-3 MSM-3 requires E-Ware version 7.1.1 or greater. Software Version ExtremeWare 7.1.1 and later Hardware Version BlackDiamond with MSM-3 Explanation This message indicates that the selected ExtremeWare version is incompatible with an MSM-3 module. MSM-3 requires ExtremeWare version 7.1.1 or greater.
fetchPacket64 Failed fetchPacket64 Failed fetchPacket64 failed WTX - (0, 50, ffff) Software Version ExtremeWare 6.x Hardware Version BlackDiamond “i” series Explanation This message indicates that ExtremeWare will try to fetch more data from the packet driver. It will first try to read 64/128 bytes from the incoming packet. ExtremeWare waits for these bytes, and if it gets no response, it displays this message. This is caused by obsolete software. Action Upgrade to the latest software.
Error Messages Firmware Version Not Supported Slot X - Firmware mismatch, disabling PoE feature, use CLI to download appropriate firmware Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that the version of firmware on the blade is not supported by ExtremeWare. Action Run the download CLI command to obtain the version built into ExtremeWare.
Initialization Failed Initialization Failed Slot x PoE system failed to initialize Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates an initialization failure. The firmware might have a problem. Action Download firmware again. If it happens again, contact Technical Support.
Error Messages Invalid Cost pifChangeStpPathCosts: Invalid cost for port 0x8ea8b120(0) Software Version ExtremeWare 2.x and 4.x Hardware Version All Summit chipset products Explanation This message indicates that you tried to set the STP path cost for a port to zero. Action Set the cost to a value other than zero.
Invalid Link Speed Invalid Link Speed pifChangeHwPortMode: Invalid link speed 0 Software Version All ExtremeWare versions Hardware Version All Explanation This message indicates that you tried to set a port link speed other than 10, 100, 1000, or 10/100. Action Set port link speed to 10, 100, 1000, or 10/100.
Error Messages Invalid Port Speed stpPortDefaultPathCost: Invalid port speed for pif Software Version ExtremeWare 2.x Hardware Version All Summit chipset products Explanation This message indicates that you are trying to set the default path cost for a port with a link speed other than 10, 100, 1000, or 10/100. Action Set port link speed to 10, 100, 1000, or 10/100.
Link Down Link Down N9_BD6800_Sec SYST: Port 2:6 link down Software Version All ExtremeWare versions Hardware Version All Explanation This message indicates a link has gone up and down. Action Check links to ensure there is no unexpected port flapping.
Error Messages Login Failed USER: Login failed for user through telnet (149.127.139.142) Software Version All ExtremeWare versions Hardware Version All Explanation This message indicates that someone failed a login attempt. Action No action is necessary.
Messages from Interrupt Level Lost Messages from Interrupt Level Lost rack:6 # 0x874e5b90 (tExcTask): 41 messages from interrupt level lost. Software Version ExtremeWare 4.x and 6.x Hardware Version All Explanation This message indicates that the CPU is temporarily busy. Action No action is necessary.
Error Messages No 802.1q Tag testBindBifToStpd: Stpd "name" no dot1q tag Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that there was an attempt to bind a VLAN to an STPD, but an STPD other than s0 has no 802.1q tag. Action Reconfigure to assign the tag to the STPD.
No PIF for BIF No PIF for BIF stpPortTestSetPortMode: No pif for bif "x", bridge "y" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that there was an attempt to add an STP port to an STPD that has no bridge interface structure. Action This situation occurs as a result of no memory. Reduce memory needs and retry.
Error Messages Packet Send Buffer Failed ngPacketSendBuffer failed WTX - (6, 400, fe0) Software Version Any Hardware Version All “i” series Explanation This message indicates that ExtremeWare started an operation, but in the middle it could not access the quake on the particular slot. There are two possible reasons for this occurring: • Hot swapping • Faulty hardware Action Run the extended diagnostics on the slot.
PBUS CRC Error PBUS CRC Error ERROR: Slot 1 port 22 PBUS CRC Error Software Version ExtremeWare 6.0 Hardware Version All “i” series Explanation This message indicates that the hardware has detected an internal corruption of packets. Action If this message occurs only once in the log, no action is necessary. If this message occurs repeatedly, contact Technical Support.
Error Messages PoE Firmware Invalid on Blade Slot X no valid PoE firmware on flash Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that there is no firmware loaded on the blade. Action Download the firmware. If it happens again, RMA the board.
PoE Firmware Invalid on Slot PoE Firmware Invalid on Slot PoE Firmware not valid on slot X Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that there is no firmware loaded or the firmware is bad. Action Download the firmware. If it happens again, call customer support.
Error Messages PoE Hardware Problem, Disabling PoE on Port Port x:x has a PoE hardware problem, disabling PoE for the port. Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that the PoE is no longer functioning on the port. Action Switch to another port that supports PoE or use the port only for regular Ethernet use.
PoE Not Operational PoE Not Operational PoE system on slot X not operational Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that the PoE system is not functioning. Action Try downloading firmware via the CLI. If there is still a problem, RMA the board.
Error Messages Port in 802.1d Mode Already Exists stpPortTestSetPortMode: Stpd "name" Port "x" in .1d mode Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that an STP port on the physical port is already in 802.1d mode. You cannot add another STP port to STPD s0. Action Reconfigure to use one STP port per physical port in 802.1d mode.
Power Consumption Normal for Slot Power Consumption Normal for Slot ERROR: PSU-[Internal | External] consumption normal for slot x Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that the total measured power for the slot has returned to normal consumption. Action Informational only. No action needed.
Error Messages Power Consumption Normal for System ERROR: PSU-[Internal | External] consumption normal for system Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that the total measured power for the system has returned to normal consumption. Action Informational only. No action needed.
Send Slave Config Length Error Send Slave Config Length Error sendSlaveCfgDb: Save fn.for EAPS returns 8. Max.possible length = 4 Software Version ExtremeWare 7.1.1 and later Hardware Version BlackDiamond with MSM-3 module Explanation This message indicates that a benign internal software error occurred during configuration transfer while Hitless Failover was enabled. Because the software recovers automatically from this error, no problematic behavior is seen.
Error Messages Unable to Allocate Memory, STPD Bridge List Unable to alloc memory for stpd bridge list Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that memory allocation failed when binding a VLAN to an STPD. Action Reduce memory needs and retry.
VDSL vPowRead VDSL vPowRead vPowRead returned err 4:1 Software Version ExtremeWare 6.1.8W301b51 Hardware Version VDSL Explanation This message indicates that an error occurred while reading remote power registers. You will only see this message if you use the hidden show vdsl power command. Action No action is necessary.
Error Messages VDSL Reduced Mode VDSL reduced mode link up on port 4:1 VDSL link up on port 4:1 Software Version ExtremeWare 6.1.8W301b51 Hardware Version VDSL Explanation These messages indicate that a change in link state has occurred. The ports first come up in reduced mode to allow for noisy line conditions and later attempt to come up in normal mode.
VLAN ID Conflict VLAN ID Conflict testBindBifToStpd: vlan id "x" conflicts with another Stpd "name" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that there was an attempt to bind a VLAN to an STPD, but VLAN ID is already used by another STPD. Action Reconfigure to use VLAN ID as tag on only one STPD.
Error Messages VLAN Not in STPD Bridge "name" not associated with stpd "name" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the VLAN you tried to remove does not belong to the specified STPD. Action Informational only. No action needed.
GPP Initialization Error GPP Initialization Error gppDisp: Initialization Error! Software Version ExtremeWare 7.3 and later Hardware Version Alpine and Black Diamond (MPLS and PoS modules) Explanation This message is displayed if the general purpose processor (GPP) module fails to initialize. The GPP module is responsible for the communication between the eXecutive Process (XP) and the general purpose processor (GPP) of the network process blade. Action Save the log files and contact Technical Support.
Error Messages TACACS Server Not Configured for Session No tacacs server configured for session Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This error message indicates that the TACACS server is not configured, or is incorrectly configured. The TACACS is a mechanism for providing authentication, authorization, and accounting on a centralized server. Action Refer ExtremeWare User Guide and configure the primary and secondary TACACS server.
Unsupported Data Type Unsupported Data Type Unsupported data Type in WLMObjectSetValueNVRAM() function Software Version ExtremeWare 7.3 and later Hardware Version All Explanation Since the internal varband data type was not in the expected format (integer or octet string), the switch could not write to NVRAM. Action Check the SNMP command sent and retry. If problem persists, contact Technical Support.
Error Messages RADIUS Authentication Server Not Found TACP sendAuthen req: Did not find Radius Auth server: Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that the RADIUS server is not configured or is incorrectly configured. The RADIUS service is a mechanism for providing authentication and centrally administering access to network nodes. Action Refer ExtremeWare User Guide and configure the primary and secondary RADIUS server.
No MAC Entries Available on lkup Table No MAC Entries Available on lkup Table vrrp-enable on vlan No mac-entries available in lkup table Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation This message indicates that there is a mismatch between the software and hardware entries for the VRRP MAC. Action Reboot the switch. If the reboot does not fix the problem, contact Technical Support.
Error Messages Cannot Create Permanent Entry with MAC Address fdbCreatePermEntry: Can not create permanent entry with MAC Address Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation This message indicates that the switch failed to create a permanent FDB entry. Action Run the command show fdb permanent to see if a mac of 00:00:00:00:00:00 is created. If it is not created, then reboot the system. If the reboot does not fix the problem, contact Technical Support.
sysObjSetStpd Returned Error for StpBridgePriority sysObjSetStpd Returned Error for StpBridgePriority dot1dStp_set: sysObjSetStpd returned error for StpBridgePriority Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation The message indicates that the SNMP set operation on the stpBridgePriority has failed. The SNMP operator will observe that the SET operation has failed.
Error Messages sysObjSetStpd Returned Error for dot1dStpBridgeHelloTime dot1dStp_set: sysObjSetStpd returned error for dot1dStpBridgeHelloTime Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation The message indicates that the SNMP set operation on the stpBridgeHelloTime has failed. The SNMP operator will observe that the SET operation has failed. Action Verify the values given for stpBridgeHelloTime, and confirm that the values are within the allowed range.
sysObjSetStpPort Returned Error for dot1dStpPortPriority sysObjSetStpPort Returned Error for dot1dStpPortPriority dot1dStpPortEntry_set: sysObjSetStpPort returned error for dot1dStpPortPriority Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation The message indicates that the SNMP set operation on the dot1dStpPortPriority variable has failed. The SNMP operator will observe that the SET operation has failed.
Error Messages sysObjSetStpPort Returned Error for dot1dStpPortPathCost dot1dStpPortEntry_set: sysObjSetStpPort returned error for dot1dStpPortPathCost Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation The message indicates that the SNMP set operation on the dot1dStpPortPathCost variable has failed. The SNMP operator will observe that the SET operation has failed.
Failed to Send Timer Tick to DLA Task Failed to Send Timer Tick to DLA Task Failed to send timer tick to DLA task. Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation The message indicates that an error has occurred in the timer processing of the LACP module. Action Check the logs and see whether the error message appears again. If you see the message again, reboot the switch. If reboot does not fix the problem, contact Technical Support.
Error Messages No Trunk ID for Port trunk-id not found for port Software Version ExtremeWare 7.3 Hardware Version All “e” series Explanation The message indicates an error in the IP FDB Creation over load-shared ports. Action Reboot the system. If reboot does not fix the problem, contact Technical Support.
Auto Diagnostic Running While Timer Expiry Auto Diagnostic Running While Timer Expiry Error: Auto-Diags already Running @ Timeout> Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the auto diagnostics was running while the auto diagnostics timer expired. Action Reboot the system. If reboot does not fix the problem, contact Technical Support.
Error Messages Cable Diagnostic Module Management Queue Failed Error (): Creating CDM_MGMT_IN_Q Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the switch failed to create the message queue for cable diagnostics. Action Reboot the system. If reboot does not fix the problem, contact Technical Support.
Cable Diagnostic Module Message Queue Failed Cable Diagnostic Module Message Queue Failed Error (): Creating CDM_MSG_IN_Q Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the switch failed to create the message queue for cable diagnostics. Action Reboot the system. If reboot does not fix the problem, contact Technical Support.
Error Messages Invalid Message Type Error: Invalid msgType Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the switch has received a message which is not recognized by the cable diagnostics. Action Reboot the system. If reboot does not fix the problem, contact Technical Support.
Manual Diagnostics In Progress Manual Diagnostics In Progress Error, Manual Diags already Running Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the cable diagnostics module is already running in manual mode. Action Run the command after the switch completes the task that is in progress.
Error Messages Memory Allocation for Manual Diagnostics Failed Error: Failed to allocate memory for Manual Diagnostics Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the switch failed to allocate memory for the cable diagnostics module. Action Reboot the system. If the reboot does not fix the problem, contact Technical Support.
Message Queue Receive Failed Message Queue Receive Failed Error: msgQReceive returned error Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the message queue receive failed. Action Reboot the system. If the reboot does not fix the problem, contact Technical Support.
Error Messages slot 1 port 5 Good Response PPP Link Status Size 12 slot 1 port 5 good response PPP Link status size 12 Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message is returned by the SNMP test request and indicates that a PPP message was sent successfully to the card. Action Informational only. No action needed.
No Physical Port Associated to STP Port No Physical Port Associated to STP Port STP port 10 has no physical port associated with it Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that the STP port does not have an associated physical port. The message usually appears when the port state changes from the listening or learning, and forwarding. Action 1 Check the port status using the show port command. 2 Delete the STP port and STP domain.
Error Messages Unable to Allocate Memory for Bridge STPD List stpTask: Can't get tx_mbuf Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The switch has failed to allocate memory for STP bridge list when a VLAN was added to the STP domain. Action 1 Check the memory available in the switch using the command show memory on switch. 2 Reboot the switch to fix the memory allocation errors. 3 Report the problem to Technical Support.
PPP Link Configuration Too Short PPP Link Configuration Too Short slot 1 port 5 bad response PPP Link config -- too short Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The SNMP test or get request returns failure message when the switch was not able to sent a PPP message to the card successfully. Action Check the card status. If the card or port is down, enable it.
Error Messages STP Task: Cannot Get Transmission Mbufs stpTask: Can't get tx_mbuf Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The switch failed to allocate memory for STP BPDU packet. Action 1 Check the memory available on the switch using the command show memory. 2 Reboot the switch to fix the memory allocation errors. 3 Report the problem to Technical Support.
STP Timer Message Queue Send Failed STP Timer Message Queue Send Failed stpTimer: MsgQ send error Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The switch failed to send the stptimer message in stptimer queue. One reason could be that the queue is full. Action 1 Check the CPU utilized by stptimer and stptask. 2 If necessary, disable few STP ports and STP domains.
Error Messages No Response for PPP Link Configuration slot 1 port 5 no response PPP Link config Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The SNMP test or get request returns failure message when the switch was not able to sent a PPP message to the card successfully. Action Check the card status. If the card or port is down, enable it.
No Response for PPP Link Status Message No Response for PPP Link Status Message slot 1 port 5 no response PPP Link status Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message is returned by the SNMP test request and indicates that the card has not responded to the PPP link status message. Action Check the card status. If the card or port is down, enable it.
Error Messages Could Not sbmalloc gselectedDvmrpVlansPtr Could not sbmalloc gselectedDvmrpVlansPtr Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that the switch is out of memory. Action Reboot the switch to fix the memory allocation errors. If reboot does not fix the problem, contact Technical Support.
Unable to Set Global Status Message Unable to Set Global Status Message Unable to set global status message. Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that status message to be displayed on the Vista web page is longer than the defined maximum length. Action Informational only. No action needed.
Error Messages Vendor Information Not Available cgiSelectContact: Could not get vendor Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The switch is not able to find the vendor information of the switch. Action Report the problem to Technical Support.
Could Not Get VLAN Instance Could Not Get VLAN Instance Could not get vlan instance. Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The VLAN name given in the Vista web page does not exist on the switch. Action Check whether the VLAN name given in the Vista web page exists on the switch. If the VLAN name exist, contact Technical Support.
Error Messages URL Not Found Did not find the requested URL Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation The URL or the path specified in the supplicant does not match any of the URLs or paths predefined on the switch. Action Check the URL and path specified in the supplicant.
HTTP User Authentication Failed HTTP User Authentication Failed Authentication failed for HTTP user Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation Authentication for the HTTP session (Vista session) has failed. Action • Check the user name and the password specified in the client during login. • Check the RADIUS configuration on the switch. • Check the reachability of the radius server from the switch and vice-versa.
Error Messages Network Login Authentication Failed Authentication failed for Network Login HTTP user Mac Port Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation Authentication for the network login HTTP session has failed. You can identify the source of the HTTP session from the MAC address in the message.
HTTP Initialization Failed HTTP Initialization Failed failed to init http Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation The message is logged when the web server TCP initialization fails. This error occurs during initialization or while configuring an alternate port. The web server could be initialized during the switch startup or while configuring an alternate port using the command enable web access-profile.
Error Messages Wrong Index for vlanIndex in Set Request vlanIfIndex in Set request exists but is not of a VLAN Software Version ExtremeWare 7.3 Hardware Version All Explanation The message indicates that you are trying to get information, using network manager or SNMP agent, about a VLAN that is not present on the switch. Action Check whether the VLAN name used in the SNMP request exists on the switch.
DOSprotect: Filter Precedence Conflicts with Rule DOSprotect: Filter Precedence Conflicts with Rule DOSprotect: filter precedence conflicts with rule \"%s\", please modify CPU DOS precedence Software Version ExtremeWare 7.3 Hardware Version All Explanation CPU DoS protection ACL precedence configuration conflicts with other ACLs. Action Verify the configuration and resolve the conflicts.
Error Messages DOSprotect Timeout: Restarting the ACL Timer DOSprotect timeout: Continuous attack detected, restarting ACL timer Software Version ExtremeWare 7.3 Hardware Version All Explanation The message indicates that there was a denial of service attack and the DoS protection feature has reset the ACL timer. DoS Protection feature creates dynamic ACLs to prevent the DoS attack. If the attack persists after the ACL timeout period, the switch retains the ACL and restarts the ACL timer.
DOSprotect Timeout: ACL Removed DOSprotect Timeout: ACL Removed DOSprotect timeout: remove ACL Software Version ExtremeWare 7.3 Hardware Version All Explanation The message indicates that the DoS protect feature has removed an ACL. If a DoS attack is detected, the DoS protect feature creates dynamic ACLs. These ACLs are removed if the DoS attack stops after the ACL time out period. Action Informational only. No action needed.
Error Messages Error Enabling FDB Entry Flag Port 1:2 is wireless enabled. Not calling SET_FDB_ENTRY_EXTFLAGS_ING Software Version ExtremeWare 7.3 Hardware Version Summit 300-24, Summit 300-48, Alpine, and Summit 400-24P Explanation The message indicates that the switch is not enabling the FDB entry flags for port 1:2 because wireless is enabled on the port. Action Informational only. No action needed.
Failed to Get HTTPS Port Number Failed to Get HTTPS Port Number Error: Failed to get https port number Software Version ExtremeWare 7.3 Hardware Version All Explanation Switched failed to get the HTTPS port number while the user tried to view the SSL Configuration. Action Repeat the command. If the problem persists, contact Technical Support.
Error Messages Invalid VLAN IfIndex Invalid ifIndex. Either non-existent or not of a VLAN. Software Version ExtremeWare 7.3 Hardware Version All Explanation Error occurred while looking up for a VLAN using SNMP. Action Provide the name of an existing VLAN in the SNMP request.
Reading Private Key Failed Reading Private Key Failed Error: Failed to read private key Software Version ExtremeWare 7.3 Hardware Version All Explanation The message indicates that there was an error while fetching the SSL private key using show config command. Action Repeat the command. If problem persists, contact Technical Support.
Error Messages TFTP Initialization Failed tftpInit failed Software Version ExtremeWare 7.3 Hardware Version All Explanation TFTP initialization failed. Action Check if TFTP server is reachable from the switch. If the problem persists, contact Technical Support.
Create VLAN Request: VlanIfIndex Exists Create VLAN Request: VlanIfIndex Exists extremeVlanIfTable: The VlanIfIndex in the Create request already exists. Software Version ExtremeWare 7.3 Hardware Version All Explanation You are trying to create a VLAN with the name of an existing VLAN. Action Use a VLAN name that does not exist in the switch configuration.
Error Messages Read Back Verification Failed Failed setting led to (4) on slot 1 Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond Explanation Read back verification fails after writing an I/O module register to change an LED state. Action Informational only. No action needed.
PSU Output Failed PSU Output Failed PSU-x output failed Software Version ExtremeWare 7.3 and later Hardware Version BlackDiamond and Alpine Explanation PSU is connected to the chassis. But, the power cable is not connected properly. Action Connect the power cable properly. Check the power supply. If you see this problem frequently, replace the power unit.
Error Messages ngRxFirst Failed ngRxFirst failed on no packet for the CPU in the packet buffer - (1, 0, 1) Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond, Alpine, and Summit Explanation The CPU diagnostics has detected checksum error. Action Run diagnostics on the card. If diagnostics does not report any problem, reboot the system.
Error Reading Register Error Reading Register ERROR: tsunamiReadReg: Slot 1 port xx register d not ready after select Software Version ExtremeWare 6.2 and later. Hardware Version BlackDiamond, Summit “i” series Explanation Error occurred while Tsunami ASIC tried to read register d of port XX found on slot 1. The switch will take the action configured using sys-health-check. If you have configured sys-health-check to shut down the card, the card is set to non-operational.
Error Messages Error Reading Register ERROR: Slot 1 port xx register 8a not ready after select Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond, Summit “i” series Explanation Timeout occurred while the ASIC tried to read a register on slot 1 on port xx. May be the card is not active. The switch will take the action configured using sys-health-check. If you have configured sys-health-check to shut down the card, the card is set to non-operational.
Active MSM Failed to Program FLASH Active MSM Failed to Program FLASH Remote FLASH Program data failed sector 1 offset 16223 Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond Explanation If you have two MSM on the chassis, the active MSM can program the flash of the other MSM. In this case, the active MSM failed to program the FLASH of the other MSM. Action Reboot the MSM. If you see the problem again, contact Technical Support.
Error Messages Running Configuration Not Saved NV:Failed configuration save (primary) operation Software Version ExtremeWare 6.2 and later Hardware Version All Explanation The switch failed to save the running configuration to NVRAM. Action Informational only. No action needed.
Error Getting Information on Internal Card Slot Error Getting Information on Internal Card Slot sendCardRunTimeBackplaneDiagPkt(): Failed to get destination card information from card 8 port 26 Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond Explanation Error occurred while obtaining the relevant information on internal card slot or port matching the network management controller. Action Repeat the task. If the problem persists, reboot the hardware and then run the task.
Error Messages Failed to Delete RIP Route ripExpireRt: SIOCDELRT (S_errno_EWOULDBLOCK) Software Version ExtremeWare 6.0 and later Hardware Version All Explanation The system failed to delete RIP route from the IP routing table. The RIP route to be deleted is not found in the Kernel routing table. Action Verify whether the expired RIP route entry is present in the IP routing table. If any invalid route entry is present, reboot the switch.
Failed to Delete RIP Route Failed to Delete RIP Route ripExpireRt: SIOCDELRT (S_objLib_OBJ_TIMEOUT) Software Version ExtremeWare 6.0 and later Hardware Version All Explanation The switch has failed to delete an RIP route entry from the IP routing table. The RIP route to be deleted is not found in the Kernel routing table. Action Verify whether the expired RIP route entry is present in the IP routing table. If any invalid route entry is present, reboot the switch.
Error Messages Failed to Send IP Datagram ip_output.c 539: ERROR: if_output failed (62). source/dest=10.128.132.151/10.128.51.184 gw=10.128. Software Version ExtremeWare 6.0 Hardware Version All Explanation The switch failed to send an IP datagram to the specified destination. The system was trying to send the datagram when the interface was inactive. Or The system does not contain enough Mbufs. Action If you are seeing this for the first time, ignore it.
Session Time Out While Reading Register Session Time Out While Reading Register ERROR: Slot 2 port 16 register d not ready Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond Explanation The session timed out while the ASIC was trying to read a register on slot 2 on port 16. One reason could be that the card in the slot is not active. The switch will take the action configured using sys-health-check.
Error Messages Interface Not Specified for the Route ripValidateKernelRt: No intf for intf rt 172.19.14.0 gw 0.0.0.0 Software Version ExtremeWare 6.0 and later Hardware Version All Explanation The route from the specified IP address does not have a corresponding interface. The interface details obtained from gateway or interface of a RIP route is NULL. Action Verify whether the interface to the gateway is active.
Slave NMC Not Active Slave NMC Not Active nmc.c 1013: SLAVE NMC(0) is not alive. Reset SLAVE NMC Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond Explanation Slave network management controller (NMC) is not active. NMC alive status is detected using keep-alive timer expiration. Action Hard reset the slave NMC.
Error Messages No Communication Between MSM-A and MSM-B nmc.c 1010: 2 master NMCs (8 & 10)in the system. Reset the system Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond Explanation There is no communication between MSM-A and MSM-B. Both modules try to act as master. By default, MSM-A is the master. Action Reboot the system. If the problem persists, contact Technical Support.
Enabling and Disabling Auto Polling: Card Not Active Enabling and Disabling Auto Polling: Card Not Active ERROR: Slot 8 port 21 MII write failed to complete. Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond, Alpine Explanation While enabling or disabling the auto polling on MAC ASIC, the card in slot 8 was not active. When auto-polling is enabled, MAC ASIC will use MII bus. The switch will take the action configured using sys-health-check.
Error Messages Error Getting Information on Internal NMC Slot card_db.c 2980: getNMCIntPort(): wrong port 65536 for card 5 Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond, Alpine Explanation Error occurred while getting the information on the internal network management controller (NMC) slot and port. Action Repeat the commands or reset the switch.
Unsupported GBIC Unsupported GBIC Unsupported GBIC type detected in slot 6 port 1 Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond, Alpine, and Summit Explanation ExtremeWare does not support the GBIC used on port 1 in slot 6. Action Use GBICs supported by ExtremeWare. For a list of GBICs supported by ExtremeWare, see release notes.
Error Messages FDB Memory Test Failed Quake 1 FDB memory test failed Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond, Alpine, and Summit Explanation Diagnostics has detected a hardware failure; either through sys-health check or through diagnostics. Action Reboot the system. If the problem persists, contact Technical Support.
Internal Links on Card Down Internal Links on Card Down All internal links on card 6 are down,set this card to NON-OPERATIONAL Software Version ExtremeWare 7.3 and later Hardware Version BlackDiamond Explanation The connection between the backplane or MSM and I/O module is broken. Action Reset or hotswap the card. If the problem persists, contact Technical Support.
Error Messages Unsupported Card Card 1 is unsupported. Please check if you need to upgrade ExtremeWare Software Version ExtremeWare 7.3 and later Hardware Version BlackDiamond, Alpine, and Summit Explanation ExtremeWare does not support the module connected to slot 1. Action Upgrade ExtremeWare or contact Technical Support.
Cannot Read Temperature Cannot Read Temperature Cannot read temperature Software Version ExtremeWare 6.2 and later Hardware Version All Explanation The switch was not able to read the temperature. Action Reboot the system. If the problem occurs again, contact Technical Support.
Error Messages No Card in Slot card.c 603: cardSM_BLANK(1): Invalid event(3). Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond, Alpine Explanation You are trying to operate a slot without a module. Action Verify whether the module is inserted correctly.
IPDA SUBNET Lookup: FDB Registration Failed IPDA SUBNET Lookup: FDB Registration Failed ERROR: IPDA SUBNET Lookup FDB registration failure Software Version • ExtremeWare 7.3 and later for “i” series • ExtremeWare 7.5 and later for “e” series Hardware Version All Explanation This message indicates that ExtremeWare has failed to register IP Destination Address (IPDA) subnet with the switch. Action Reboot the switch. If the problem occurs again, contact Technical Support.
Error Messages Unsupported Access-Profile Attribute "Invalid Attrib in Alist %s.\n",alist->name Software Version ExtremeWare 7.3 and later Hardware Version BlackDiamond, Summit, Alpine, "i" series, "e" series Explanation This message indicates that ExtremeWare does not support the specific access-profile attribute. Action 1 Get the access-profile name given in the log. 1 Delete the access-profile with the access-profile name given in the log. 2 Create the access-profile.
OTP Block Allocation Failed; Cannot Create Bridge OTP Block Allocation Failed; Cannot Create Bridge ERROR: Bridge create failed due to OTP block allocation failure (%d) Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that system was unable to allocate an OTP block for the new VLAN on a slot. Action Informational only. No action needed.
Error Messages Cannot Create Bridge ERROR: Bridge create failed (%x) Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that the maximum possible number of VLANs have already been created on the switch. Action Informational only. No action needed.
pifValidQ: Invalid Port Number pifValidQ: Invalid Port Number pifValidQ: Invalid portNum %d Software Version ExtremeWare 7.3 and later Hardware Version All “i” series Explanation This message indicates that ExtremeWare is trying to access a port interface with an invalid port number. Action Reboot the switch. If the problem occurs again, contact Technical Support.
Error Messages Semaphore Initialization Failed for QoS Port semMInit failed for Port QOS Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that ExtremeWare was not able to create a semaphore for the QoS port. Action Reboot the switch. If the problem occurs again, contact Technical Support.
Unsupported Access-Profile Type Unsupported Access-Profile Type "%s:Type %d in Alist %s, Not Valid.\n", 1563 __FUNCTION__,alist->type,alist->name Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that ExtremeWare does not support the particular access-profile type. Action 1 Get the access-profile name from the log. 2 Delete the access-profile. 3 Create the access-profile.
Error Messages Invalid Option Invalid option to Software Version ExtremeWare 7.3 and later Hardware Version Altitude 350, Altitude 350-2, and Summit WM series Explanation The message indicates that a set request failed on one of the object IDs. Action Confirm that the you have configured the correct set request.
SNMP Request Returned Error SNMP Request Returned Error addSNMPRequest for SNMP_extremeAPMACFilterDot1pValue returned error Software Version ExtremeWare 7.3 and later Hardware Version Altitude 350, Altitude 350-2, and Summit WM series Explanation The message indicates that a get or set request for the object APMACFilterDot1pValue Failed. Either the object ID (OID) specified was wrong or there was an internal software error. Action Check the OID generated in the get or set request.
Error Messages SNMP Request for AP MAC Filter Status Returned Error addSNMPRequest for SNMP_extremeAPMACFilterStatus returned error Software Version ExtremeWare 7.3 and later Hardware Version Altitude 350, Altitude 350-2, and Summit WM series Explanation This message indicates that a get or set request for the object APMACFilterStatus failed. Either the object ID (OID) specified was wrong or there was an internal software error. Action Check the OID generated in the get or set request.
Interface Not Configured as Wireless Interface Interface Not Configured as Wireless Interface This command can be executed only on a LAC", <__FUNCTION__> Software Version ExtremeWare 7.3 and later Hardware Version Altitude 350, Altitude 350-2, and Summit WM series Explanation This message indicates that you are trying to run a command for wireless interface on an interface that is not configured for wireless. Action 1 Verify the interface configuration.
Error Messages Initialization Agent Request Returned Error sysObjSetMacFilter:initAgentXRequest returned error Software Version ExtremeWare 7.3 and later Hardware Version Altitude 350, Altitude 350-2, and Summit WM series Explanation The mac filter allows you to specify a group of MAC addresses. The filter can be applied to one or more ports. You can specify permit or deny action for the filter. This message indicates that the SNMP agent returned an error in response to a request to create the filter.
Send Set Request Returned Error Send Set Request Returned Error sendSetRequest for
Error Messages Ping Initialization Agent Request Returned Error sysObjTestPingControl:initAgentXRequest returned error Software Version ExtremeWare 7.3 and later Hardware Version Altitude 350, Altitude 350-2, and Summit WM series Explanation The MAC Filter allows you to specify a group of MAC addresses. The filter can be applied to one or more ports. You can specify permit or deny action for the filter. The message indicates that the SNMP agent returned an error for a request to create the MAC filter.
STP Port: Memory Allocation Failed STP Port: Memory Allocation Failed • Could not malloc gselectedStpPortPtr • Could not malloc gselectedStpPortPtr->portNum Software Version ExtremeWare 7.4 and later Hardware Version All Explanation The message indicates that the system is out of memory. Action 1 Reboot the system. 2 Check whether the problem persists. 3 If the problem persists, contact Technical Support.
Error Messages No Physical Interface ERROR no phys ifc card=%d ptag=%x Software Version ExtremeWare 7.3 Hardware Version All Explanation The message indicates that the switch has received the physical interface information as NULL when it tried to send a packet to the interface. Action Verify the configuration.
Platform Not Supported Platform Not Supported Platform is not supported YET! Software Version ExtremeWare 7.3 Hardware Version All Explanation ExtremeWare does not support the platform. Action Informational only. No action needed.
Error Messages Skipping Bridge Learning bridgeLearning called for unauthenticated Netlogin Wireless client %m Software Version ExtremeWare 7.3 and later Hardware Version Summit 300-24,Summit 300-48, Summit 400-24p, Alpine Explanation This message indicates that the switch is skipping the bridge learning because it is called for unauthenticated wireless client. Action Informational only. No action needed.
Invalid Card Type for Slot Invalid Card Type for Slot Invalid card type=%d for slot=%d Software Version ExtremeWare 7.3 Hardware Version All Explanation The message indicates that the card type specified is not valid for the selected slot. Action Verify the configuration.
Error Messages Invalid Switch Card Invalid switch card=%d Software Version ExtremeWare 7.3 Hardware Version All Explanation The message indicates that the switch has received an invalid card number when it tried to send a packet. Action Verify the configuration.
TFTP Initialization Errors TFTP Initialization Errors • tftpModeSet failed • tftpGet failed • tftpQuit failed • tftpPeerSet failed Software Version ExtremeWare 7.3 Hardware Version All Explanation These messages indicates that there was an error while initializing TFTP. Action • Verify the TFTP configuration. • Check the network connectivity.
Error Messages Insufficient Instance Object ID • ExtremePethMainPse get: Insufficient instance OID • pethMainPse set: Insufficient instance OID • ExtremePethPsePort set: Insufficient instance OID • ExtremePethPseSlot set: Insufficient instance OID • extremePethPortPse get: Insufficient instance OID • ExtremePethPseSlot set: Insufficient instance OID Software Version ExtremeWare 7.
Empty STP Packet Empty STP Packet Bad parameter - NULL mbuf Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that the incoming STP packet is NULL or empty. Action 1 Capture the incoming STP BPDU and analyze the fields. A packet is not copied from port hardware to system CPU. 2 Reboot the switch. 3 Continue monitoring the switch.
Error Messages STP Packets with Incorrect Version Number Invalid/unknown BPDU "version 0x%x type 0x%x" Software Version ExtremeWare 7.3 and later Hardware Version All Explanation Incoming STP packets carry wrong version number. Action 1 Capture the incoming STP BPDU and analyze the fields. 2 Check the STP configuration of the neighbor switches.
STP BPDU Does Not Match with Port Mode STP BPDU Does Not Match with Port Mode BPDU mismatch on STP Domain","%s (received %s, expected %s" Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that the incoming STP BPDU does not match the configured port mode. Action 1 Capture the incoming STP BPDU and analyze the fields. 2 Check STP ports configured encapsulation mode.
Error Messages Cannot Delete STP Domain Cannot delete local STP domain Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that you are trying to delete the default STP domain (S0) through SNMP or VISTA. Action You can ignore this message. You cannot delete the default STP domain.
Large STP Packets Large STP Packets • “Malformed packet - bad length”,”(0x%x)” • Malformed packet - incorrect length Software Version ExtremeWare 7.3 and later Hardware Version All Explanation These messages indicate that the incoming STP packet size is greater than the packet size supported by the switch. Action 1 Capture the incoming STP BPDU and analyze the fields. 2 If the packet is corrupted, check the interface status.
Error Messages DVMRP Interface Creation Failed extDvmrpAddIf: Cicuit creation failed Software Version ExtremeWare 7.3 and later Hardware Version All “i” series and Summit “e” series Explanation This message indicates that the switch failed to create Distance Vector Multicast Routing Protocol (DVMRP) interface. This would mainly occur when the memory allocation for the DVMRP circuit fails. Action Delete some of the DVMRP interfaces and retry.
DVMRP Task: Invalid Message Type DVMRP Task: Invalid Message Type dvmrpTask: Invalid msg type Software Version ExtremeWare 7.3 and later Hardware Version All “i” series and Summit “e” series Explanation The message indicates that the switch has received a message on the DVMRP message queue, but the message is not of a DVMRP (Distance Vector Multicast Routing Protocol) timer tic or a DVMRP packet type. Action Informational only. No action needed.
Error Messages Linking or Adding Timer Node to Timer List Failed suspending in working on Software Version ExtremeWare 7.3 and later Hardware Version All “i” series and Summit “e” series Explanation This message indicates that the switch has failed to link or add the timer node to the timer list. Action Informational only. No action needed.
DVMRP Initialization: Task Spawn Failed DVMRP Initialization: Task Spawn Failed extDvmrpInit: taskSpawn failed Software Version ExtremeWare 7.3 and later Hardware Version All “i” series and Summit “e” series Explanation The message indicates that the switch failed to spawn the DVMRP (Distance Vector Multicast Routing Protocol) task. This error could occur: • During system initialization, if DVMRP is already enabled. • While enabling DVMRP after system initialization.
Error Messages DVMRP Initialization: Cannot Allocate Packet Memory extDvmrpInit: Cannot allocate packet memory Software Version ExtremeWare 7.3 and later Hardware Version All “i” series and Summit “e” series Explanation This message indicates that the switch failed to allocate memory for the incoming packet while initializing the DVMRP (Distance Vector Multicast Routing Protocol) module. Action Restart the switch.
DVMRP Initialization: Watchdog timer Creation Failed DVMRP Initialization: Watchdog timer Creation Failed extDvmrpInit: wdCreate failed Software Version ExtremeWare 7.3 and later Hardware Version All “i” series and Summit “e” series Explanation This message indicates that the watch dog timer failed during DVMRP (Distance Vector Multicast Routing Protocol) module initialization. Action Restart the switch.
Error Messages DVMRP Initialization: Queue Creation Failed extDvmrpInit: QCreate failed Software Version ExtremeWare 7.3 and later Hardware Version All “i” series and Summit “e” series Explanation This message indicates that the switch failed to create the DVMRP (Distance Vector Multicast Routing Protocol) message queue while initializing the DVMRP module. Action Reboot the switch.
DVMRP Initialization Failed DVMRP Initialization Failed extDvmrpInit: Init failed Software Version ExtremeWare 7.3 and later Hardware Version All “i” series and Summit “e” series Explanation The message indicates that the switch failed to initialize the DVMRP. Usually this error will not occur. Action Informational only. No action needed.
Error Messages Bridge Create Failed ERROR: Bridge create failed (%x) Software Version ExtremeWare 7.3 and later Hardware Version All “i” series, “e” series, BlackDiamond, Summit, Alpine Explanation This message indicates that ExtremeWare tried to create a vlan with an invalid instance while restoring the configuration. Action Reboot the switch. If the problem appears again, contact Technical support.
Memory Allocation for Bridge Failed Memory Allocation for Bridge Failed Bridge malloc failed (%x) Software Version ExtremeWare 7.3 and later Hardware Version All “i” series, “e” series, BlackDiamond, Summit, Alpine Explanation The message indicates that the switch failed to allocate memory for the bridge data structures. Action Reboot the switch. If the problem appears again, contact Technical support.
Error Messages Renaming System Defined VLAN Failed Cannot rename system defined VLAN (Default)\ Software Version ExtremeWare 7.3 and later Hardware Version All “i” series, “e” series, BlackDiamond, Summit, Alpine Explanation The message indicates that you are trying to rename the default VLAN. You cannot rename the default VLAN. Action Informational only. No action needed.
Invalid STPID for Bridge Invalid STPID for Bridge Invalid configured stpdId %d for bridge Software Version ExtremeWare 7.3 and later Hardware Version All “i” series, “e” series, BlackDiamond, Summit, Alpine Explanation The message indicates that the switch tried to restore a VLAN configuration with an invalid STP instance. Action 1 Download the Configuration. 2 Reboot the switch. 3 If problem appears again, contact Technical Support.
Error Messages Configuring Hardware Queue Before Initializing Cards pifDefaultQCfg: Invalid configuration. numSlices=0 Software Version ExtremeWare 7.3 and later Hardware Version All “i” series, “e” series, BlackDiamond, Summit, Alpine Explanation This message indicates an error in configuring the number of packet buffers per hardware queue. This may be because the switch tried to configure the hardware queues before the cards were initialized completely.
Memory Allocation for Port/VLAN Flush Mask Failed Memory Allocation for Port/VLAN Flush Mask Failed Unable to malloc port/vlan flush mask Software Version ExtremeWare 7.3 and later Hardware Version All “i” series, “e” series, BlackDiamond, Summit, Alpine Explanation This message indicates that the switch failed to allocate memory for Port/VLAN flush mask. Action Reduce the memory requirements and retry the command.
Error Messages Failed to Take Semaphore to Read Port QoS Statistics Semtake failed for bg task card %d with error %x Software Version ExtremeWare 7.3 and later Hardware Version All “i” series, “e” series, BlackDiamond, Summit, Alpine Explanation This message indicates that switch failed to take the semaphore to read port QoS statistics. Action If you see the message repeatedly, reboot the switch. If the error appears after restarting the switch, contact Technical Support.
VLAN Translation Flush Mask: Memory Allocation Failed VLAN Translation Flush Mask: Memory Allocation Failed Unable to malloc vlan translation flush mask Software Version ExtremeWare 7.3 and later Hardware Version All “i” series, “e” series, BlackDiamond, Summit, Alpine Explanation This message indicates that the switch failed to allocate memory for VLAN translation flush mask. Action Reduce the memory requirements and retry the command.
Error Messages Security Profile Not Found Could not find security profile with index on interface Software Version ExtremeWare 7.3 and later Hardware Version Altitude 350, Altitude 350-2, and Summit WM series Explanation This message indicates that the security profile for the MAC group was not configured or the profile was not configured correctly. The MAC filter allows you to specify a group of MAC address. You can associate a security profile to each profile.
SNMP Agent Not Found SNMP Agent Not Found No AgentX request for MFE_FLAGS Software Version ExtremeWare 7.3 and later Hardware Version Altitude 350, Altitude 350-2, and Summit WM series Explanation The message indicates that the SNMP agent was not found, during a setRequest to the object. The mac filter feature allows you to specify a group of MAC addresses. The filter can be applied to one or more ports and permit or deny action can be specified for the filter.
Error Messages Adding SNMP Request for APMAC Filter MAC Failed addSNMPRequest for SNMP_extremeAPMACFilterMAC returned error Software Version ExtremeWare 7.3 and later Hardware Version Altitude 350, Altitude 350-2, and Summit WM series Explanation This message indicates that the SNMP agent returned an error while trying to create a filter. The MAC filter feature allows you to specify a group of MAC addresses. You can apply filter to one or more ports and specify permit or deny action to each filter.
MAC Ping Address: Wrong Format MAC Ping Address: Wrong Format AgentXGet for extremeAPMACPingDestAddr returned bytes, expected 48 bytes Software Version ExtremeWare 7.3 and later Hardware Version Altitude 350, Altitude 350-2, and Summit WM series Explanation The message indicates that the MAC ping address was not formatted correctly in the SNMP request or response. Action 1 Check the SNMP request. 2 Retry the command.
Error Messages addSNMPRequest Returned Error addSNMPRequest for SNMP_extremeWirelessInterfaceMacDefaultDot1p returned error Software Version ExtremeWare 7.3 and later Hardware Version Altitude 350, Altitude 350-2, and Summit WM series Explanation The message indicates that the SNMP agent returned an error for a request to create the object WirelessInterfaceMacDefaultDot1p. The MAC filter feature allows you to specify a group of MAC addresses.
Error Creating SNMP Request for Create Ping Error Creating SNMP Request for Create Ping createPing:initAgentXRequest returned error Software Version ExtremeWare 7.3 and later Hardware Version Altitude 350, Altitude 350-2, and Summit WM series Explanation The message indicates that the switch encountered an error while creating the SNMP request for the createPing function. Action 1 Check whether the SNMP agent is configured correctly. 2 Check whether the agent responds to other requests.
Error Messages AP Returned Non-existent VLAN ID AP returned a non-existent VLAN id Software Version ExtremeWare 7.3 and later Hardware Version Altitude 350, Altitude 350-2, and Summit WM series Explanation The message indicates that the VLAN ID, specified in the GetRequest or Response, was not found on the switch. Action 1 Check the SNMP Request and Response. 2 Verify the VLAN Configuration on the switch and make sure you have configured the VLAN and have enabled it.
Card Not Supported Card Not Supported ExtremeWare Card is unsupported. Please check if you need to upgrade Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the ExtremeWare version running on the switch does not support the card. Action 1 Upgrade ExtremeWare. 2 If the error appears again, contact Technical Support.
Error Messages Card SEM Received Invalid Event cardSM_BLANK(): Invalid event() Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the card SEM received an invalid event in the given state. This may be due to timing restrictions. Action Contact Technical Support.
Configuration: Card Type Not Allowed Configuration: Card Type Not Allowed Card Type= not allowed in this configuration Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the given card cannot be used on the particular slot because the configuration is invalid for the switch. Action Contact Technical Support.
Error Messages Failed to Read Card EEPROM Failed to read card %d EEPROM Software Version ExtremeWare 7.4 Hardware Version BlackDiamond Explanation The message indicates the system failed to read the EEPROM on the card. Action 1 Disable and Enable the card. 2 If the problem exists, reboot the system. 3 If the error appears again, contact Technical Support.
Quake Register: Read Failed Quake Register: Read Failed Card : Quake RX PBUS DEAD. Count Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the system failed to read a Quake register. Action 1 Disable and Enable the card. 2 If the problem exists, reboot the system. 3 If the error appears again, contact Technical Support.
Error Messages Card SEM Received Invalid Event cardSM_PRESTART(): Invalid event() Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the card SEM received an invalid event in the given state. This may be due to timing restrictions. Action Contact Technical Support.
Could Not Allocate Memory Could Not Allocate Memory • Could not malloc gipCfgOptionsPtr • Could not malloc gipCfgOptionsPtr->vlanName • Could not malloc gselectedDvmrpVlansPtr->vlanName • Could not malloc gselectedDvmrpVlansPtr->vlanName[] • Could not malloc gselectedOspfVlanAreasPtr • Could not malloc gipCfgOptionsPtr->vlanName[] Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.
Error Messages Cloning OID Failed Could not clone the OID Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the OID cloning has failed. When the switch receives an SNMP Get Next Request, it tries to allocate memory for individual OIDs for cloning the request. The OID cloning may fail if the switch does not have enough memory. Action Reboot the switch.
Cloning varbinds Failed Cloning varbinds Failed Could not clone varbinds Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the switch failed to clone varbinds. When the switch receives an SNMP Get Request, it tries to allocate memory for cloning the request. The cloning may fail if the switch does not have enough memory. Action Reboot the switch.
Error Messages Error Updating FDB null pif ? exit! 0 Software Version ExtremeWare 7.3 Hardware Version All “i” series and “e” series Explanation The message indicates that the switch encountered an error while updating the FDB on a port for which mirroring is enabled. Action Reboot the switch. If error still persists, contact Technical Support.
Deleting STP Instance Failed Deleting STP Instance Failed Delete STP instance %d failed. ERR=%d Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the switch failed to delete the STP domain. Action Restart the switch and try again.
Error Messages Creating STP Domain Failed Create STP domain '%s' failed. ERR=%d Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the switch failed to create the STP domain. Action Restart the switch and try again.
Enabling VRRP On Interface Failed Enabling VRRP On Interface Failed Cannot enable vrrp on interface Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that the switch failed to enable VRRP on the interface. Action 1 Restart the switch. 2 Confirm that the switch has license for VRRP. If the problem appears again, contact Technical Support.
Error Messages Invalid RTIF Instance Invalid rtifInstance at vrrpAddRtif Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that there was an internal error in the instance assigned to a Virtual Router. Action Contact Technical Support.
IP Output Returned Error IP Output Returned Error ip_output returned error Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that an error was generated at layer 3. Action 1 Check the logs for details. 2 Check the IP statistics to verify whether packets are being dropped. If the problem appears again, contact Technical Support.
Error Messages VLANS Share Same Broadcast Domain vlans and share the same broadcast domain. Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This error is displayed while associating a virtual router with a VLAN. The message indicates that the broadcast domain you are trying to configure is already being used by another VLAN. Action Change the broadcast domain and retry the command.
No Buffers For Multicast Options No Buffers For Multicast Options vrrp_transmit: No mbufs for multicast options Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that the switch failed to get buffers to transmit VRRP packets. This may be a temporary situation due to heavy traffic. Action Check the logs. If problem appears even under reduced traffic conditions, contact Technical Support.
Error Messages Reading Card Hardware Database Failed Card Type= cannot obtain card HW database Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the switch failed to read the card hardware database. Action 1 Disable and enable the card. 2 If the problem appears again, restart the switch.
Daignostics On Card Failed Daignostics On Card Failed Card failed diagnostics (diag-result) Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the diagnostics failed on the card. The card will be moved to Failed state. Action Disable and enable the card. If the error appears again, contact Technical Support.
Error Messages Card Inserted While Slot Was Disabled Card (type=) is inserted while slot in disabled state Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the card was inserted while the user had administratively disabled the slot. The card will be active only after the user enables the slot. Action Informational only. No action needed.
Reading From Card EEPROM Failed Reading From Card EEPROM Failed Card already had Hardware Failure - set to Fail state Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the switch failed to read the card EEPROM and the card is being placed in Failed state. Action Disable and enable the card. If the error appears again, contact Technical Support.
Error Messages Card Type Not Compatible Card type= is not compatible with card type= Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the types of cards present in the system are incompatible with the card type configured for the slot. This may happen if there are NP SAK cards in the system and the actual card types do not match. Action Contact Technical Support.
IPDA Subnet Lookup Feature Enabled IPDA Subnet Lookup Feature Enabled cardSM_START: NP card = Conflicts with IPDA SUBNET Lookup Disable IPDA SUBNET Lookup to use NP card [cardno] Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the IPDA subnet lookup feature is enabled on a system with NP cards. Action Disable the IPDA Subnet lookup feature. Or Remove the NP cards.
Error Messages Vectors Mismatch Vectors Mismatch, rejecting the card , type Software Version ExtremeWare 7.4 Hardware Version All “e” series Explanation The message indicates that the operational parameters of the members in the stack does not match. Operational parameters include license information, software versions, and platform type. Action Contact Technical Support.
STPD Parameters in Vista: Memory Allocation Errors STPD Parameters in Vista: Memory Allocation Errors • Could not malloc gselectedStpdParamsPtr • Could not malloc gselectedStpdVlansPtr • Could not malloc gselectedStpdVlansPtr->vlanName[] • Could not malloc gselectedStpdVlansPtr->vlanName • Could not malloc gselectedUncfgStpdPtr Software Version ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the switch failed to allocate memory for the task.
Error Messages Loading Boot Load Image Failed ERROR: BootROM cannot boot load image Software Version ExtremeWare 7.5 Hardware Version BlackDiamond Explanation The message indicates that the BootROM was not able to load the selected image. Action Please upgrade to version 1.0.30.0 or later. If the problem appears again, contact Technical Support.
Getting Destination Card Failed Getting Destination Card Failed sendCardRunTimeBackplaneDiagPkt(): Failed to get destination card information from card %d port %d Software Version ExtremeWare 7.5 Hardware Version BlackDiamond Explanation The message indicates that the switch failed to get the destination card details while running the back plane diagnostics. Action Reboot the system and try the diagnostics test again. If problem appears again, contact Technical Support.
Error Messages Invalid EEPROM Device Number Invalid EEPROM device number %d Software Version ExtremeWare 7.5 Hardware Version BlackDiamond Explanation The message indicates that the switch received an Invalid EEPROM device number. Action Restart the switch. If problem appears again, contact Technical Support.
User Account Out Of Range User Account Out Of Range User account instance %d out of range Software Version ExtremeWare 7.5 Hardware Version All Explanation The message indicates that you are configuring more user account instances than the maximum allowed. You can configure a maximum of 16 user account instances. Action Informational only. No action needed. If the error appears again, contact Technical Support.
Error Messages ARP Entry Not Found CANNOT FIND ARP ENTRY FOR %I Software Version ExtremeWare 7.3 Hardware Version All Explanation The message indicates that the switch was not able to find the ARP (Address Resolution Protocol) entry for the destination IP address while trying to send out an MPLS encapsulated packet over the wire. Action Informational only. No action needed.
Adding Bogus Memory Block Adding Bogus Memory Block ERROR: attempting to manually add bogus memory block %p (%x bytes) back to system memory pool! Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation This message indicates that the switch is trying to add bogus memory block to the memory pool. Action Informational only. No action needed.
Error Messages Allocating Memory Buffer Failed • Couldn't Alloc Mbuf#2 • Unable to get mbuf#1 chain Software Version ExtremeWare 7.3 Hardware Version All Explanation The message indicates that the switch failed to allocate required memory buffer while trying to send out an MPLS encapsulated packet over the wire. Action Informational only. No action needed.
Log Filter: Same Match Parameter Log Filter: Same Match Parameter ERROR: log filter - Same match parameter type specified more than once. Note that parameters on the same 'configure' command are logically AND'ed together. Use multiple 'configure' commands for logical OR, such as to match MAC address X -orMAC address Y Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation This message indicates that you are using the same parameter more than once.
Error Messages Log Filter: Accepting Factory Default Failed ERROR: log filter could not accept the factory default item Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation This message indicates that the switch does not have enough memory to reset the factory default settings. You can unconfigure the log filters you have configured. When you unconfigure the log filter, the factory default settings are restored. Action Restart the switch.
Deleting Log Filter Failed Deleting Log Filter Failed ERROR: log filter is required and cannot be deleted Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation You can delete a log filter by entering the name of the filter. The message indicates that the switch does not contain a log filter with the name you have specified. Action Informational only. No action needed.
Error Messages Log Filters: Maximum Configured ERROR: log filter cannot be added. Maximum already configured Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the you have already configured the maximum number of log filters on the switch. You can configure a maximum of 20 filters. Action Informational only. No action needed.
Deleting Log Filter Failed Deleting Log Filter Failed ERROR: log filter cannot be deleted, since it has associated log targets Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version BlackDiamond Explanation This message indicates that you cannot delete the log filter. The log filter is in use and has log targets associated with it. Action Informational only. No action needed.
Error Messages Log Filter: Cannot Copy Completely ERROR: log filter could not be copied completely, insufficient memory Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation You can create log filters by copying the characteristics of an existing log filter. This message indicates that the switch does not have enough memory to copy the log filter. Action Restart the switch.
Modifying Log Filter Failed Modifying Log Filter Failed ERROR: log filter cannot be modified, insufficient memory Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the switch failed to modify the log filter. This could be due to insufficient memory. Action Restart the switch. If the problem appears again, contact Technical Support.
Error Messages Log Filter Does Not Exist ERROR: log filter does not exist, cannot copy Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation You can create log filters by copying the characteristics of an existing log filter. This message indicates that you are trying to copy a log filter that does not exist on the switch. Action Informational only. No action needed.
Log Filter Does Not Exist Log Filter Does Not Exist ERROR: log filter does not exist Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation You can see the log filter by providing the name of the log filter. This message indicates that you have entered the name of the log filter that does not exist on the switch. Action Informational only. No action needed.
Error Messages Log Filter Exceeds Maximum Length ERROR: log filter exceeds maximum length Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation This message indicates that the filtername used in the log filter command contains more than 32 characters. Action Use a name that contains less than 32 characters.
Permanent Entry With MAC Not Found Permanent Entry With MAC Not Found fdbAddPortToPermEntry: Could not find permanent entry with MAC vlanId Software Version ExtremeWare 7.3 Hardware Version All “i” series and “e” series switches Explanation The message indicates that the switch failed to find the permanent FDB entry while trying to add a port to the permanent FDB entry. Action Contact Technical Support.
Error Messages FDB: Port Already In Permanent Entry Table fdbAddPortToPermEntry: Port already in perm entry vlan Software Version ExtremeWare 7.3 Hardware Version All “i” series and “e” series switches Explanation The message appears when you add a new port to the permanent FDB entry. The message indicates that the port indicated by the port number is already a member of the FDB entry represented by the MAC address and the vlan ID. Action Contact Technical Support.
FDB Ageing Time Too Large FDB Ageing Time Too Large fdbSetAgeingTime: value too large Software Version ExtremeWare 7.3 Hardware Version All “i” series and “e” series switches Explanation This message indicates that the FDB ageing was configured with an invalid value. Action Contact Technical Support.
Error Messages MAC FDB Refresh: Null ARP macFdbRefresh: arp is null! Software Version ExtremeWare 7.3 Hardware Version All “i” series and “e” series switches Explanation The message indicates that the switch encountered an error while deleting IP ARP entries. This can occur if the associated FDB entry is removed. Action Contact Technical Support.
Invalid ARP Entry Invalid ARP Entry macFdbArp: invalid arp entry ! Software Version ExtremeWare 7.3 Hardware Version All “i” series and “e” series switches Explanation The message indicates that the switch encountered an error while deleting IP ARP entries. This can occur if the associated FDB entry is removed. Action Contact Technical Support.
Error Messages Delete Invalid ARP macFdbRefresh: delete invalid arp ! Software Version ExtremeWare 7.3 Hardware Version All “i” series and “e” series switches Explanation The message indicates that the switch encountered an error while deleting IP ARP entries. This can occur if the associated FDB entry is removed. Action Contact Technical Support.
Failed to Allocate SSH Eloop Event Failed to Allocate SSH Eloop Event Out of memory allocating ssh_eloop_event_rec Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the switch does not have enough memory to allocate to SSH eloop event. Action Restart the switch. Verify whether the problem exists. If the problem appears again, contact Technical Support.
Error Messages Error Allocating Global Head List Problems allocating head_list global Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the switch does not have enough memory to allocate to the global head_list task. Action Restart the switch. Verify whether the problem persists. If the problem appears again, contact Technical Support.
Allocating SSH Debug Globals Failed Allocating SSH Debug Globals Failed Out of memory allocating ssh_debug_globals Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the switch does not have enough memory to allocate to the SSH global debug task. Action Restart the switch. Verify whether the problem exists. If the problem appears again, contact Technical Support.
Error Messages Allocating Memory Failed ERROR: real_ssh_xmalloc: out of memory (allocating %ld bytes) Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the switch does not have enough memory to allocate to the task. Action Restart the switch. Verify whether the problem exists. If the problem appears again, contact Technical Support.
Allocating Memory for SSH Failed Allocating Memory for SSH Failed Out of memory allocating ssh_dlp_param_list global Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the switch does not have enough memory to allocate to the ssh_dlp_param_list task. Action Restart the switch. Verify whether the problem exists. If the problem appears again, contact Technical Support.
Error Messages Virtual Router ID Not Found BAD instance for vrid at GM_VRRP_DELETE Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that the switch could not find the virtual router id specified, while trying to delete a VRRP instance. Action Verify the configuration. See the virtual router configuration and make sure that you are using the correct id.
Virtual Router Instance Not Found Virtual Router Instance Not Found vrrp table-inst not configured yet Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that the while a parameter—such as priority—was being set, the switch failed to find the corresponding virtual router instance. Action Verify whether the virtual router instance exists. Retry the command.
Error Messages Null Interface Interface is NULL at vrrp_rtifVrid2Ptr, rtif= vrid= Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates a wrong configuration in the virtual router configuration, or an Internal error. Action 1 Verify the Virtual router configuration. 2 Retry the command. 3 If the problem appears again, please contact Tech Support.
VRRP Message: Message Queue Receive Error VRRP Message: Message Queue Receive Error VrrpMsgTask: msgQReceive returned error Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates an internal error generated while the inter-process message system cannot deliver a message. Action No action needed. The switch will recover from this error without external intervention.
Error Messages Sending DNS Server Configuration to APs Failed Could not send DNS server configuration to APs. See logs for details. Software Version ExtremeWare 7.3 and later Hardware Version Cards that support wireless ports; such as, the Altitude 350, Summit WM100, Summit WM1000 Explanation This message indicates that the switch failed to send the DNS server information to the access points (AP). Action Make sure the required ports are online. Verify the logs for details.
Allocating Memory for Clients Failed Allocating Memory for Clients Failed Unable to allocate memory for clients Software Version ExtremeWare 7.3 and later Hardware Version Cards that support wireless ports; such as, the Altitude 350, Summit WM100, Summit WM1000 Explanation This message is displayed when an SNMP command is issued to get some client data. The message indicates that the switch failed to allocate enough memory to store the client data.
Error Messages Diffserv Examination: Resources Not Enough ERROR: not enough resources to enable diffserv examination on ports specified Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message appears while enabling DiffServ examination on all ports. DiffServ examination use 64 rules per port. On Summit 200 and Summit 300 switches, 256 rules are shared among a block of eight 10/100 ports.
SSHD: Exec Command Not Supported SSHD: Exec Command Not Supported sshd: exec not supported: "show tech” Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that you are trying to connect to the switch using SSH and to run the execute command “show tech”. ExtremeWare does not support the exec command. Action Informational only. No action needed.
Error Messages Shared Port Not a Ring Port in EAPS Domain EAPS Shared-port 1:1 - Shared-port not a ring port in EAPS domain DOM1 Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the shared port is not a primary or secondary port in the EAPS domain. To configure the port as a shared port in ESD (EAPS super domain), the port should be either a primary port or a secondary port in the EAPS domain.
Allocating Memory for Bridge Failed Allocating Memory for Bridge Failed EAPS Shared-port 1:1 - Out of memory. Cannot malloc bridge structure Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the switch failed to allocate memory for the bridge structure. Action Check the available memory on the system using show memory command. Restart the switch.
Error Messages Adding VLAN Failed EAPS Shared-port 1:1 - Could not add vlan %s Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the ESD (EAPS super domain) failed to add the VLAN to the shared port domain. Action Delete the ESD domain and create the domain again. Check the memory available on the switch.
Deleting VLAN Failed Deleting VLAN Failed EAPS Shared-port 1:1 - Cannot delete vlan %s. ESD-bridge value is NULL Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the VLAN you are trying to delete does not exist in the ESD (EAPS super domain). This could be due wrong configuration or the vlan has already been removed from the ESD. Action Informational only. No action needed.
Error Messages Adding Bridge Interface for Segment Port Failed EAPS Shared-port 1:1 - Cannot add bridge interface for segment port 2:1. Segment interface value is NULL Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the ESD (EAPS super domain) does not have the interface for the segment port. Action Delete the port from EAPS and add it again. If the problem appears again, delete and create the shared port ESD.
Adding Bridge Interface for VLAN Failed Adding Bridge Interface for VLAN Failed EAPS Shared-port 1:1 - Cannot add bridge interface for vlan %s. Bridge interface value is NULL Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the ESD (EAPS super domain) does not have the interface for the bridge. Action Delete the vlan from the EAPS and add it again. If the problem appears again, delete and create the shared port ESD.
Error Messages Deleting Bridge Interface for Port Failed EAPS Shared-port 1:1 - Cannot delete bridge interface for port %P. Value is NULL Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the ESD (EAPS super domain) does not have the interface for the given segment port. Action Informational only. No action needed.
Deleting Bridge Interface for VLAN Failed Deleting Bridge Interface for VLAN Failed EAPS Shared-port 1:1 - Cannot delete bridge interface for vlan %s. Value is NULL Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the ESD (EAPS super domain) does not have the interface for the bridge. Action Informational only. No action needed.
Error Messages Adding Segment Port Interface Failed EAPS Shared-port 1:1 - Could not add segment port interface Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the ESD (EAPS super domain) does not exist for the passed ESD instance. Action 1 Check the ESD configuration. 2 Create the ESD instance.
Control VLAN Interface Not Found Control VLAN Interface Not Found EAPS Shared-port 1:1 - Could not find Control Vlan interface for EAPSD DOM1 Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the EAPS is having the details of control vlan in its configuration, but the control vlan does not exist. ESD (EAPS super domain) shared port domains points to EAPS domain running on the shared and segment ports.
Error Messages Unknown Port State EAPS Shared-port 1:1 - Unknown port state (%d) Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation Controller in ESD shared port can be in BLOCKING, PREFORWARDING, IDLE, or READY state. The message indicates that the controller is in a state other than any of these states. Action Disable ESD and Enable Or Delete and create the ESD.
EAPS Domain Segment Interface Not Found EAPS Domain Segment Interface Not Found EAPS Shared-port 1:1 - Could not find EAPS domain %s segment interface Software Version ExtremeWare 7.2 and later Hardware Version Version Explanation The message indicates that the switch could not find the EAPS domain on the segment interface. Non shared ports are considered as the segment port for the ESD and the segment port will be associated to the EAPS Domain. Action Delete the shared port and create it again.
Error Messages Removing Segment Port Interface Failed EAPS Shared-port 1:1 - Error in removing segment-port interface for EAPSD %s Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that ESD (EAPS super domain) does not exist for the passed ESD instance. Action Verify the ESD configuration.
EAPSD Domain Part of Another ESD Instance EAPSD Domain Part of Another ESD Instance EAPSD DOM1 - Already part of another ESD instance Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the EAPS domain is already part of another ESD. EAPS domain can never be part of two shared port domains (ESD). Action Reconfigure the EAPS and ESD domains.
Error Messages Invalid Port Type EAPSD DOM1 - Invalid port type (%d) Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the port is neither a primary port nor a secondary port in EAPS domain. Action Delete the port and create it again.
Shared-port Instance Out of Range Shared-port Instance Out of Range EAPS Shared-port instance (%d) out of range Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that you are trying to create more than allowed number of shared port instance. You can create a maximum of two shared port instances on a switch. Action Before creating a new shared port, check the number of shared ports on the switch.
Error Messages ESD Controller in Wrong State EAPS Shared-port 1:1 - State should not have been %s Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates the state of the ESD (EAPS super domain) controller. The controller should not be in blocking or pre-forwarding when the shared port is removed or when the mode is changed. Action Make sure that the ESD is in proper state before changing the mode or deleting it.
Cannot Set Port Cannot Set Port EAPS Shared-port 1:1 - Already up. Cannot set port 1:1 Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that you cannot configure a new port. You cannot configure a new port when the ESD is in UP state. Action 1 Delete the shared port. 2 Configure new ports as shared port.
Error Messages Cannot Stop Domain EAPS Shared-port 1:1 - Error in stopping domain Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that you are trying to delete an ESD that is in UP state. You cannot delete an ESD when it is active. Action 1 Disable the ESD.
Invalid ESD Instance: Cannot Set the Mode Invalid ESD Instance: Cannot Set the Mode Could not set the mode. Invalid ESD instance %d Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates the ESD instance you have entered is not a valid ESD instance. You cannot set the mode to partner or controller. Action 1 Check number of ESD instance exist in the system. You can create a maximum of 2 ESD instance on a switch.
Error Messages Invalid ESD Instance: Cannot Set the Link ID Could not set the link-id. Invalid ESD instance %d Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the ESD (EAPS super domain) instance entered is not a valid ESD instance. You can set the link-id only if the ESD instance is valid. Action 1 Check number of ESD instance exist in the system. You can create a maximum of 2 ESD instance on a switch.
Invalid ESD Instance: Cannot Set Shared Port Timeout Invalid ESD Instance: Cannot Set Shared Port Timeout Could not set the shared-port-timeout. Invalid ESD instance %d Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the ESD (EAPS super domain) instance entered is not a valid ESD instance. You can set the shared-port-timeout only if the ESD instance is valid. Action 1 Check number of ESD instance exist in the system.
Error Messages Invalid ESD Instance: Cannot Set Segment Timeout Could not set the segment-timeout. Invalid ESD instance %d Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the ESD (EAPS super domain) instance entered is not a valid ESD instance. You can set the segment-timeout only if the ESD instance is valid. Action 1 Check number of ESD instance exist in the system. You can create a maximum of 2 ESD instance on a switch.
Setting Segment-Timeout Expiry Action Failed Setting Segment-Timeout Expiry Action Failed Could not set the segment-timeout Expiry Action. Invalid ESD instance %d Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the ESD (EAPS super domain) instance entered is not a valid ESD instance. You can set the segment-timeout expiry action only if the ESD instance is valid. Action 1 Check number of ESD instance exist in the system.
Error Messages Shared Port Domain Instance Out of Range EAPS Shared-port Domain instance (%d) out of range Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the ESD (EAPS super domain) shared-port domain instance is out of range. Action 1 Check number of ESD instance exist in the system. You can create a maximum of 2 ESD instance on a switch. 2 Delete the ESD instance that and create the ESD instance again.
No Shared Port Domain No Shared Port Domain EAPS Shared-port domain does not exist for instance %d Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the ESD Shared-port domain does not exist for the instance. Action 1 Check number of ESD instance exist in the system. You can create a maximum of 2 ESD instance on a switch. 2 Delete the ESD instance that and create the ESD instance again.
Error Messages Invalid ESD Instance Invalid ESD instance Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the switch has received an ESD (EAPS super domain) PDU but the ESD does not exist. Action 1 Check number of ESD instance exist in the system. You can create a maximum of 2 ESD instance on a switch. 2 Delete the ESD instance that and create the ESD instance again.
Unknown Root-blocker State Unknown Root-blocker State EAPS Shared-port 1:1 - Root-blocker-state is unknown (%d) Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the root blocker is in a state not known to the switch. The root-blocker can be in any of the following states: • False • Active • Inactive Action Check the Root-blocker state.
Error Messages Segment-port Not Found EAPS Shared-port 1:1 - Cannot find segment-port for port (%P) Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the ESD (EAPS super domain) is in blocking state and the ESD PDU is received on segment port. This indicates that while checking the PDU, the segment port for the shared port in the ESD does not exist. Action Check whether the segment ports are part of the EAPS domain.
Shared Port State Unknown Shared Port State Unknown EAPS Shared-port 1:1 - State is unknown (%d) Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the share port is in an unknown state. The valid states are idle, ready, preforwarding, and blocking. Action Delete the shared port. Add it again to the ESD (EAPS super domain), then check the state of the ESD.
Error Messages Controller Mode for a Partner Event EAPS Shared-port 1:1 - Mode is Controller in a Partner event Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the ESD (EAPS super domain) is in partner mode. In the normal condition, this message will not appear. Before starting the partner event handling, the ESD is moved to partner mode. Action Informational only. No action needed.
Wrong Event for ESD Partner Wrong Event for ESD Partner EAPS Shared-port 1:1 - Partner should not be getting event Esd-Ev-Seg-RingUp Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the ESD (EAPS super domain) partner is getting an event that should not have been delivered to the ESD partner. ESD partner can handle shared port up, shared port down, segment up, and segment down events only. Action Check the configured mode of ESD.
Error Messages Unknown Event EAPS Shared-port 1:1 - Event is unknown (%d) Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the ESD (EAPS super domain) is in partner mode and has encountered an unknown event. The valid events are: • Shared down • Shared up • Segment down • Segment up • Segment ring up Action Check the state of the partner and verify the incoming ESD PDU.
Segment and Bridge Interface Status Segment and Bridge Interface Status EAPS Shared-port 1:1 - Segment-port 2:1. Segment status %s, Bridge-interface status %s Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This error appears in any of the following scenarios: • During a segment down event; the controller and the segment is in blocking mode, and the bridge interface status is in non-blocking.
Error Messages Wrong Bridge-Interface Status EAPS Shared-port 1:1 - Segment port 2:1. Bridge-interface status should not have been %s Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the bridge-interface is in a wrong state. This could happen during a segment up event, if the controller is in blocking mode; segment status is down, and the bridge interface status is in blocking state.
Wrong Bridge-Interface State Wrong Bridge-Interface State EAPS Shared-port 1:1 - Segment-port interface 2:1, vlan %s, should not have bridge-interface in state %s Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the VLAN has got a bridge-interface in wrong state.
Error Messages Bridge Interface Status EAPS Shared-port 1:1: Segment 2:1 status is %s. Bridge-interface status is already %s Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the bridge interface is already in down state; but the switch is trying to move the bridge interface from open state to blocked state. This might occur in the controller, if the segment was down, and the port has moved to down state.
Wrong Bridge Interface Status Wrong Bridge Interface Status EAPS Shared-port 1:1: Segment 2:1 status is %s. Bridge-interface status is %s. Should have been %s Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the bridge interface is in blocked, active open, or unknown state; instead of being in open state. This might occur in the controller, if the segment was down and the port state has moved to down.
Error Messages Unknown Segment-port State EAPS Shared-port 1:1 - Segment-port 2:1 state unknown (%d) Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that in the controller, the segment status is in an unknown state. The known segment statuses are: • Segment Up • Segment Down • Blocking UP • Blocking Down Action 1 Check the bridge status in ESD (EAPS super domain). 2 Disable and enable the shared port.
ESD Controller Domain in Ready State ESD Controller Domain in Ready State EAPS Shared-port 1:1: State is %s. Shared-port status is %s. Should have been %s Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the ESD (EAPS super domain) controller domain is in ready state and the share port is not in segment up state while the switch processed the shared port up event.
Error Messages Partner Mode in a Controller Event EAPS Shared-port 1:1 - Mode is Partner in a Controller event Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the mode is partner in a controller event. Before starting the controller event-handling function, the switch confirms that the ESD (EAPS super domain) is in controller mode. Action Informational only. No action needed.
EAPSD: Error In Stopping the Domain EAPSD: Error In Stopping the Domain EAPS: EAPSD eaps2a - Error in stopping the domain Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation The message appears when you disable or delete the EAPS domain. Action Create the EAPS domain again.
Error Messages EAPSD: Error In Stopping All Domains EAPS: EAPSD eaps2a - Error in stopping all domains Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message appears when you disable or delete all EAPS domains configured on the switch. Action Create the EAPS domain again.
EAPSD: Error in Unbinding Protected VLAN EAPSD: Error in Unbinding Protected VLAN EAPS: EAPSD eaps1a - Error in unbinding vlan emistp2a, type Protected Vlan, from all EAPS domains. Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that you have removed the protected VLAN from all EAPS domains.
Error Messages EAPS Shared-port: Stopping the Domain Failed EAPS Shared-port 1:1 - After setting mode, problem in stopping the domain Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the EAPS domains were not removed or unbound from the ESD domain. ESD (EAPS Shared Port domain) mode can be configured as Partner or Controller.
EAPS Shared-port: Unbinding from L2 Domains Failed EAPS Shared-port: Unbinding from L2 Domains Failed EAPS Shared-port 1:1 - Error in unbinding from L2 domains Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the EAPS domains were not removed or unbound from the ESD domain. ESD (EAPS Shared Port domain) mode can be configured as Partner or Controller.
Error Messages EAPS Shared-port: Disabling the Domain Failed EAPSD Dom1 - Error in disabling the domain Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS domain was not stopped while trying to disable the EAPS domain. Action 1 Delete the EAPS domain 2 Create the domain again.
Upgrading Bootloader Failed Upgrading Bootloader Failed • Upgrade bootloader failed. Unknown file type • Upgrade bootloader failed. Checksum failed • Upgrade bootloader failed. Filetype mismatch detected • bootloader upgrade failed. TFTP failed : Unknown host • bootloader upgrade failed. TFTP failed : Server not reachable • bootloader upgrade failed. TFTP failed : File not found • bootloader upgrade failed. TFTP failed : General Error • bootloader upgrade failed.
Error Messages Action If the Upgrade Bootstrap/bootloader failed due to... Then... Unknown file type Configure the correct filetype. Checksum failed Check the network and retry the upgrade again. Filetype mismatch detected Configure the correct filetype. TFTP failed : Unknown host Configure the correct server name. TFTP failed : Server not reachable Check the configuration and network connectivity. TFTP failed : File not found Check the configuration.
Upgrading Bootloader Failed Upgrading Bootloader Failed Bootloader upgrade failed. Failed to open primary bootloader file. Software Version ExtremeWare 7.7 Hardware Version All Explanation This message indicates that the bootloader upgrade failed because the switch failed to open the primary bootloader. Action Retry. If the problem appears again, contact Technical Support.
Error Messages Bootloader Header Update Failed Bootloader header update failed. Software Version ExtremeWare 7.7 Hardware Version All Explanation This message indicates that the bootloader upgrade failed because the switch failed to update the bootloader header. Action Retry. If the problem appears again, contact Technical Support.
Reboot Loop Detected For Back-up MSM Reboot Loop Detected For Back-up MSM Reboot loop detected for back-up MSM. Shutting down backup MSM Software Version ExtremeWare 7.7 Hardware Version All Explanation This message indicates that the switch has shutdown the back-up MSM because the switch has detected a reboot loop. Action Upgrade the software in the back-up MSM. If the problem appears again, contact Technical Support.
Error Messages No Untagged Port in VLAN ERROR: No Untagged Port in vlan "vlanName". Software Version ExtremeWare 7.8 Hardware Version All Explanation This message indicates that you are trying to configure or unconfigure limit-learning or lock-learning for the untagged ports that are not in the VLAN. Action Add ports to the VLAN as untagged and try configuring it.
Memory Threshold Limit Memory Threshold Limit ERROR: Memory Threshold limit must be between 0 and 100. Software Version ExtremeWare 7.8 Hardware Version All Explanation This message indicates that you are trying to configure memory-monitoring threshold limit with a value that is not in the range of valid limits. Action Configure the memory-monitoring threshold with a value between 0 and 100.
Error Messages Trap Interval Value ERROR: Trap Interval must be between 180 and 360 seconds Software Version ExtremeWare 7.8 Hardware Version All Explanation This message indicates that you are trying to configure memory-monitoring trap interval with out-of-range value. Action Configure the memory-monitoring trap interval with the range 180-360.
Unable to Configure VLAN “Mgmt” Unable to Configure VLAN “Mgmt” ERROR: vlan "Mgmt" cannot be configured Software Version ExtremeWare 7.8 Hardware Version All Explanation The messages indicates that you are trying to configure or unconfigure limit-learning or lock-learning for Management VLAN. You cannot configure limit-learning or lock-learning for the management VLAN. Action None.
Error Messages Unable to Monitor Management VLAN ERROR: vlan "Mgmt" cannot be monitored Software Version ExtremeWare 7.8 Hardware Version All Explanation This message indicates that you are trying to configure or unconfigure management VLAN to monitor. You cannot configure or unconfigure management VLAN to monitor. Action None.
Cloning Attributes of an Inactive User Cloning Attributes of an Inactive User ERROR : You cannot clone Attributes of an inactive user. Software Version ExtremeWare 7.8 Hardware Version All Explanation This message indicates that you are trying to clone the existing user attributes from an inactive user to the new SNMPv3. Action Try to clone the new SNMPv3 user from an existing and active SNMPv3 user.
Error Messages Adding User to an Inactive Group ERROR : Group “admin” is not active. Add user to an active group. Software Version ExtremeWare 7.8 Hardware Version All Explanation This message indicates that you are trying to add new SNMPv3 user to the default group that is inactive. Action Try to add the new SNMPv3 user to the active group.
SNMPv3 Access Disabled SNMPv3 Access Disabled ERROR: SNMPv3 access not enabled Software Version ExtremeWare 7.8 Hardware Version All Explanation You cannot enable SNMPv3 default-user or default-group access while the SNMPv3 access is disabled. Action Enable SNMPv3 access before enabling the SNMPv3 default-user or default-group access.
Error Messages Could Not Add L3 Entry for Unit Could not add L3 entry for unit at 0xbff(-6: Table full) Software Version ExtremeWare 7.7 Hardware Version All Explanation L3 entries cannot be added to the IP unicast table when the table is full. 0xbff is the last entry of the fdb table and unlike other hash index, the available entries for this entry is 7 and not 8. The 8th entry is used internally (in software).
5 Warning Messages Warning messages indicate a possible conflict that might require corrective action. Check the “Issues Resolved In” sections in the latest ExtremeWare Installation and Release Notes to see if the error message indicates an issue that has been corrected in a recent software release. Access Rule Does Not Exist Access rule does not exist Software Version ExtremeWare 7.
Warning Messages ACK Error Write Address: Didn't get an ack. Read Command: Didn't get an ack. Write Command: Didn't get an ack. Software Version ExtremeWare 2.x and 4.x Hardware Version All Explanation These messages indicate that the switch cannot communicate with the GBICs. Action Remove and re-insert the GBICs and power cycle the switch. If this action does not fix the problem, replace the GBICs.
Activate Failed, No PIF Activate Failed, No PIF stpPortAddToActive: No pif Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the request to mark the STP active failed due to no physical I/f (PIF). Action Retry. If it repeatedly fails, contact Technical Support.
Warning Messages Add Port Failed, 802.1D Port Already Active stpPortAddOneToActive: Another dot1d is already active Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that you cannot add the STP port in 802.1D mode to a physical port because another STP port in 1D mode was found. Only one STP port in 802.1D mode is permitted per physical port. Action No action is necessary.
Bad Ethernet Type/Length Bad Ethernet Type/Length bpduFilter: Ethertype II frame. Bad type/length "type/length" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that a bad Ethernet type/length is in the received BPDU. Action Check configuration of peer device.
Warning Messages Bad Length for BPDU bpduFilter: Port "x" malformed BPDU Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the received BPDU has a bad length. Action Check configuration of peer device.
Bad MAC Read Bad MAC Read WARNING: Slot 7 Port 2 reg read bad MAC = 4 WARNING: Slot 8 Port 3 reg read bad MAC = 4 Software Version ExtremeWare 6.1.7 and earlier Hardware Version All Explanation These messages indicate that an internal software error has occurred. Action Upgrade to the latest software.
Warning Messages BlackDiamond Memory Block Already Free tNetTask: Block 4018 on slot 7 is already free Software Version All ExtremeWare versions Hardware Version BlackDiamond Explanation This message indicates that a task tried to free a portion of memory that was already free. Action Check the behavior of the switch. Use show log and show tech-support commands to collect information about what happened earlier on the switch. Contact Technical Support to help debug the problem.
ASIC Error ASIC Error ERROR: Blizzard link up, phy link down Software Version All ExtremeWare versions Hardware Version All “i” series Explanation This message indicates that you had either a very fast or a spurious link transition on a 10/100 port. The transition was so fast that ExtremeWare did not process a link up event. Action If the slot:port is indicated in the error message, swap the port to see if the message follows the port or the connection.
Warning Messages BPDU Mismatch bpduFilter: Stpd "name" Port "x" ("mode"<-"format") BPDU mismatch Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that an incorrect BPDU encapsulation was received. Action Ensure that the proper encapsulation is configured (that is, EMISTP, PVST+, and 802.1d).
Bracket Buffer Full Bracket Buffer Full addToBracketBuffer: Bracket buffer full Software Version ExtremeWare 7.1.1 and later Hardware Version BlackDiamond with MSM-3 module Explanation This message indicates that the message queue is full on the slave MSM-3 that receives configuration information from the master MSM-3 when Hitless Failover is enabled. This means that some of the configuration was not successfully transferred to the slave MSM-3.
Warning Messages Bridge ID Not Assigned sysObjTestStpd: Bridge Id mac addr 0 Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the management action on STPD is not possible because an STPDID is not assigned. Action Configure a valid STPDID.
Btree Insert Failed Btree Insert Failed insertStpPort2Tree: Btree insert failed Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates a Btree insertion failure when adding a port to the port tree. Action Retry STP port creation. If it repeatedly fails, contact Technical Support.
Warning Messages Cannot Add VLAN to EAPS eaps.c 5063: Warning! Cannot assign vlan "v1" to EAPS "eaps1" interface Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the request to add the VLAN to EAPS as control/protected failed. Action Look at syslog or console for other warning messages to determine the cause.
Cannot Allocate Memory for Timer Cannot Allocate Memory for Timer Can not allocate memory for timer buckets Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the system was unable to allocate memory for the timer. Action If there are multiple messages, contact Technical Support.
Warning Messages Cannot Find Default VLAN edpSendBackplaneDiagPkt: Can not find default VLAN Software Version ExtremeWare 6.1.x Hardware Version All “i” series Explanation This message indicates that the default VLAN has been renamed, and as a result the health-check processes failed. Action Reboot the switch to reset the configuration with the default VLAN.
Cannot Get Memory Buffer Transaction Cannot Get Memory Buffer Transaction stpInit: Can't get tx_mbuf Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates an STP initialization error. Action Reboot. Retry STP port creation. If it fails again, contact Technical Support.
Warning Messages Cannot Save Default STPD stpdGenerateDefault: Cannot save default stpd to nv "x" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that STPD creation failed. Action Retry STPD creation. If it repeatedly fails, contact Technical Support.
Cannot Send Card Cannot Send Card Cannot send card message(3,7,0x0,0x0). Error=-1 (0xffffffff) Software Version ExtremeWare 4.x and 6.x Hardware Version All Explanation This message indicates that the switch has crashed resulting in the module task exception. Action Check for Exception Program Counter (EPC) information in the log prior to the error message. Contact Technical Support to assist you in obtaining switch information for reproduction and resolving the problem.
Warning Messages Cannot Send Health PDU eaps_runtime.c 2799: Warning! Cannot send Health PDU on startup for "eaps1" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that EAPS has just been enabled, but cannot send out Health-check PDUs. Action This warning is most likely due to the system just coming up and the ports are not up, or EDP is still not running. This situation should be resolved automatically in the next few seconds.
Cannot Send nmc Cannot Send nmc Cannot send nmc message(3,10,0x0,0x0). Error=3997698 (0x3d0002) Software Version ExtremeWare 6.1 and later Hardware Version BlackDiamond Explanation This message indicates that one MSM64i cannot communicate with the other MSM64i. This is most likely caused by a hardware problem or a seating problem with the MSM64i or an I/O module in the system. Action Remove and re-insert the I/O modules.
Warning Messages card_db.c Module Memory Defect card_db.c 821: Card 2 has nonrecoverable packet memory defect card_db.c 832: Card 2 is back online Software Version ExtremeWare 6.2.2 and later Hardware Version Alpine and Summit Explanation These messages indicate that the memory mapping feature found memory defects. During the check, the software allows the switch to work normally with eight or less defects by mapping around the bad sections.
Card Removed Card Removed SYST: card.c 1000: Card 3 (type=2) is removed. Software Version All ExtremeWare versions Hardware Version BlackDiamond Explanation This message indicates that a module has been removed. Action No action is necessary.
Warning Messages Checksum Error on MSM and Slot edpProcessPdu1078: Checksum failed for pdu between MSM-A and slot 1 Software Version ExtremeWare 6.1.8b12 and later Hardware Version BlackDiamond “i” series Explanation This message indicates that the checksum on an EDP packet has failed, and the port is internal. MSM A does not have an internal PBus error, and slot 1 does not have any PBus internal/external errors or any other CPU packet/CPU diag packet errors.
Checksum Error on PDU Checksum Error on PDU edpProcessPdu1011: Checksum failed for pdu on port 1:1 Many others like: bad OUI, bad length, bad SNAP, bad version etc Software Version ExtremeWare 6.1.8b12 and later Hardware Version All “i”series Explanation This message indicates that the checksum on an EDP packet fails on an external port.
Warning Messages Control VLAN Already Exists eaps.c 5043: Warning! EAPS "eaps1" cannot have >1 control vlan. Vlan "v1" is already controller Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the EAPS domain already has a control VLAN. Action An EAPS domain cannot have more than one control VLAN added to it.
Control VLAN Not Configured for EAPS Domain Control VLAN Not Configured for EAPS Domain eaps_runtime.c 1198: Warning! Control Vlan not configured for EAPS domain "eaps1" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the control VLAN has not been added to the EAPS domain and EAPS PDUs cannot be sent. Action Configure the EAPS control VLAN and add it to EAPS.
Warning Messages Create STPD Failed StpdCreate: Bad instance "x" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the STPD creation task failed. Action Retry STPD creation. If it repeatedly fails, contact Technical Support.
Datagram Fragment Datagram Fragment DLCS: received datagram fragment - discarding Software Version ExtremeWare 4.x, 6.x Hardware Version All Explanation This message indicates that Extreme Networks does not support IP fragmentation in DLCS. Action Check the Maximum Transmission Unit (MTU) size in the network. The hosts or routers on the path might fragment packets. The DHCP server might also specify small MTU size. Make sure that the MTU size is larger than 1000 bytes along the path.
Warning Messages Default Cost Zero for Port stpPortCreate: Default cost 0 for port "x" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that a path cost of zero was found while creating the STP port. Action Informational only. No action needed.
Delete Failed, EAPS Interface Delete Failed, EAPS Interface eaps.c 5230: Warning! Cannot delete EAPS "eaps1" interface to vlan "v1" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the request to delete VLAN “v1” from EAPS domain “eaps1” failed. Action EAPS task may have become unstable. Contact Technical Support.
Warning Messages Delete Failed, EMISTP Group Address deleteStpFilter: Unable to remove emistp group addr vlan "x" from fdb Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the request to remove a EMISTP group address entry from the FDB failed. Action If there are multiple messages, contact Technical Support.
Delete Failed, FDB Entry Delete Failed, FDB Entry deleteStpFilter: Unable to remove bridge group addr vlan "x" from fdb Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the request to remove an FDB entry failed. Action If there are multiple messages, contact Technical Support.
Warning Messages Delete Failed, Local STPD stpdDelete: Cannot delete local stpd Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the request to delete STPD s0 failed. Action It is not permitted to delete s0.
Delete Failed, No PIF Delete Failed, No PIF stpPortDelFromActive: No pif Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the STP port was not deleted due to a missing physical I/f (PIF). Action Retry. If it repeatedly fails, contact Technical Support.
Warning Messages Delete Failed, Port Mismatch stpPortDelOneFromActive: Active untagged stp port mismatch Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the STP port was not deleted due to port mismatch. Action Retry. If it repeatedly fails, contact Technical Support.
Diagnostic Failure, Port Invalid Speed Diagnostic Failure, Port Invalid Speed pifQBw2PqmBw: Invalid speed 0 Port 44 Failed IP Route loop back test Packet received from port 45 rather than from port 44 Software Version ExtremeWare 4.x Hardware Version All Explanation These messages indicate that the port failed diagnostics; therefore, it is a hardware problem.
Warning Messages Diagnostic Failure, Slot MAC Chip of slot 3 port 1 is not ready init internal receive TOS look-up table failed on slot 3 port 1! init MAC Id look-up table failed on slot 3 port 1! init internal App Rec look-up table failed on slot 3 port 1! init App Cmp internal look-up table failed on slot 3 port 1! init Vlan Rec look-up table failed on slot 3 port 1! init Vlan Cmp look-up table failed on slot 3 port 1!
Domain Already Exists Domain Already Exists eaps.c 3797: EAPS Domain "eaps1" already exists. Inst(1) Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the attempt to rename an EAPS domain failed because one already exists with that name. Action Pick another name to rename the EAPS domain.
Warning Messages Dropped Bytes Condition Clear Dropped bytes condition clear, port 1:1 queue IQP1, reporting 539072 bytes Software Version ExtremeWare 7.2.0 and later Hardware Version BlackDiamond and Alpine High-Density Gigabit Ethernet modules (G16X3, G24T3, GM-16X3, and GM-16T3) Explanation This message indicates that ingress traffic is no longer being dropped on the indicated port and queue.
Dropped Bytes Condition Set Dropped Bytes Condition Set Dropped bytes condition set, port 1:1 queue IQP1 Software Version ExtremeWare 7.2.0 and later Hardware Version BlackDiamond and Alpine High-Density Gigabit Ethernet modules (G16X3, G24T3, GM-16X3, and GM-16T3) Explanation This message indicates that ingress traffic on the indicated port and queue is being discarded.
Warning Messages Duplicate MAC Entry fdbCreatePermEntry: Duplicate entry found mac 00:40:26:75:06:c9, vlan 4095 Software Version ExtremeWare 4.1.17b6 Hardware Version All Explanation This message indicates that you added the same permanent MAC address twice. Action Delete the duplicate MAC address.
EAPS Task Not Running EAPS Task Not Running eaps.c 3502: EAPS task is not running Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the EAPS task is not running. Action The EAPS task may have become unstable. Contact Technical Support.
Warning Messages EDP Checksum Checksum failed for pdu on port 7:3 Checksum failed for pdu on port 7:1 Software Version All ExtremeWare versions Hardware Version All Explanation These messages indicate that a switch has reported EDP checksum errors. This occurs when the switch receives corrupted EDP data on the port. This could be a physical layer issue or a problem with the switch. Contact Technical Support for details of the EDP checksum problem.
EDP Not Enabled EDP Not Enabled eaps_runtime.c 1188: Warning! EDP not enabled Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the EDP task is not yet enabled. Action This message will most likely be seen during bootup, because the EAPS task comes up before the EDP task. After EDP starts running, this message should not appear anymore. If it does, check to make sure EDP is not disabled on any of the ring-ports.
Warning Messages ESRP Enabled stpdEnableStp: ESRP enabled on Bridge "name" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that there was an attempt to enable both ESRP and STP on a VLAN. Action Disable either STP or ESRP for the named VLAN.
ESRP Enabled, Action Not Possible ESRP Enabled, Action Not Possible sysObjTestStpd: ESRP enabled on Bridge "name" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that this action on the STPD is not possible because ESRP is enabled on VLAN. Action Disable either STP or ESRP for the named VLAN.
Warning Messages Exceeded Committed-Rate Condition Clear Exceeded committed-rate condition clear, port 1:1 queue IQP1, reporting 4196 bytes Software Version ExtremeWare 7.2.0 and later Hardware Version BlackDiamond and Alpine High-Density Gigabit Ethernet modules (G16X3, G24T3, GM-16X3, and GM-16T3) Explanation This message indicates that the configured maximum ingress committed-rate is no longer being exceeded for the indicated port and queue.
Exceeded Committed-Rate Condition Set Exceeded Committed-Rate Condition Set Exceeded committed-rate condition set, port 1:1 queue IQP1 Software Version ExtremeWare 7.2.0 and later Hardware Version BlackDiamond and Alpine High-Density Gigabit Ethernet modules (G16X3, G24T3, GM-16X3, and GM-16T3) Explanation This message indicates that the configured maximum ingress committed-rate has been exceeded for the indicated port and queue.
Warning Messages Failed Diagnostic Packet sendCardRunTimeBackplaneDiagPkt(): Failed to send diag pkt from card 10 port 24 Software Version ExtremeWare 6.1.6b19 Hardware Version BlackDiamond Explanation This message indicates that ExtremeWare failed to send out a health-check diagnostic packet from the module or MSM64i. Action Investigate if there was a broadcast storm on the network.
Failed to Obtain Statistics Failed to Obtain Statistics MP:Failed to obtain stats. (ffffffff) Software Version ExtremeWare 6.2.1b25 Hardware Version Summit5iTX and all switches with the MGMT port Explanation This message indicates that ExtremeWare did not get the statistics on the Management port. Action If this message occurs once, no action is necessary. If this message occurs continuously, use on Ethernet port instead of the Management port.
Warning Messages Failed to Receive Message stpTask: msgQReceive returned error Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that msgQReceive failed to receive a message. Action If there are multiple messages, contact Technical Support.
FDB Entry Not Found FDB Entry Not Found deleteStpFilter: No matching entry for VlanId "x" in fdb Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the FDB entry for the VLAN or STPD is not up. Action If there are multiple messages, contact Technical Support.
Warning Messages FDB Error fdbGeneratePtag: Cannot find bif (0xfff,8) fdbCreatePermEntry: Unable to bind mac 00:40:26:75:06:c9 vlan 4095 to qosP QP1 Software Version ExtremeWare 4.1.17b6 Hardware Version Summit24 Explanation These messages indicate a configuration error. It occurs when something is misconfigured, such as specifying a port that does not belong to a particular VLAN. Action Check for any system configuration errors.
Free List Free List Trying to put block 19 in free list: out of range last message repeated 2 times Trying to put block 1f in free list: out of range Software Version ExtremeWare 6.1.x Hardware Version All except VDSL Explanation These messages indicate a problem with the hardware tables. Action Contact Technical Support to assist you with collecting switch information so that engineers can debug the problem.
Warning Messages GARP Event Event JoinIn with -1 l2ifp (oper 1) msg 0x8658b5f0 Event LeaveAll with -1 l2ifp (oper 32) msg 0x8658b610 Software Version ExtremeWare 4.1.11b2 Hardware Version All Explanation These messages indicate that a JoinIn and a LeaveAll event message arrived at the indicated memory addresses. This only occurs if GARP is enabled. Action No action is necessary.
Get EEPROM Error Get EEPROM Error stpdCreate: sysObjGetEEPROM returned error "x" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that STPD creation failed due to an EEPROM error. Action Retry STPD creation. If it repeatedly fails, contact Technical Support.
Warning Messages Get Failed, Port Not Found sysObjGetStpPort: stpPort Instance "x" not found Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the management “get” failed because the STP port was not found. Action Specify the correct STP port.
Incorrect State Incorrect State setPortState: Incorrect state "x" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the request to force a port state failed because the specified state is not legal. Action Specify a legal state.
Warning Messages Install STPD Tag Failed, Ignore BPDU Enabled configStpdFilters: Stpd tag is from a brigde that ingores BPDU Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the request to install an FDB entry for BPDU failed because the carrier VLAN has “ignore BPDU” enabled. Action Disable “ignore BPDU” for carrier VLAN.
Insufficient Memory, PIF Structure Insufficient Memory, PIF Structure stpPortAddOneToActive: Insufficient memory Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that there was insufficient memory when adding the port to the PIF structure. Action Retry STP port creation. If it repeatedly fails, contact Technical Support.
Warning Messages Insufficient Memory, Port Tree insertStpPort2Tree: Insufficient memory Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that there was insufficient memory when adding the port to the port tree. Action Retry STP port creation. If it repeatedly fails, contact Technical Support.
Invalid BPDU Invalid BPDU StpProcessBpdu: Port "x" Invalid "y" Bpdu type "z" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that there is a bad BPDU type in the received BPDU. Action Check the configuration of the peer device.
Warning Messages Invalid BPDU Header decode_bpdu, Port "x", Invalid bpdu header "3 bytes of BPDU" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that there is a BPDU format error in the received BPDU. Action Check the configuration of peer device.
Invalid EAPS Object ID Invalid EAPS Object ID eaps.c 5660: Warning! Error in nvramObjectGet. Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that there is an invalid EAPS object ID when reading the configuration from NVRAM. Action You could be using an incorrect software image. Contact Technical Support.
Warning Messages Invalid EAPS-VLAN Object ID eaps.c 5713: Warning! Error in nvramObjectGet. Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that there is an invalid EAPS-Vlan object ID when reading the configuration from NVRAM. Action You could be using an incorrect software image. Contact Technical Support.
Invalid PIF for Port Invalid PIF for Port stpPortChangeVpstState: Invalid pif for port "x" stpPort "y" "old state"->"new state" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that an invalid physical I/F (PIF) was found when setting the VPST state. Action If there are multiple messages, contact Technical Support.
Warning Messages Invalid Port Cost pifChangeStpPathCosts: Invalid cost for port 0x8e5b2b50(44) stpPortDefaultPathCost: Invalid port speed for pif 0x8e5b2b50 port 1:45 Software Version ExtremeWare 6.x Hardware Version All “i” series Explanation These messages indicate that there is some invalid port information. Even if STP is not enabled, the STP task still checks all of the port parameters.
Invalid Port Speed Invalid Port Speed stpPortDefaultPathCost: Invalid port speed for pif "x" port "y" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the path cost could not be calculated due to a bad port speed. Action If there are multiple messages, contact Technical Support.
Warning Messages Invalid Secondary Port eaps_runtime.c 2009: Warning! Invalid Secondary Port Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the secondary ring-port is not configured. Action Configure the secondary ring-port on the EAPS domain.
Invalid Time Values Invalid Time Values decode_bpdu, received time values out of range "max age" "hello time" "forward delay" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that there are invalid STP timer values in the received BPDU. Action 1 Capture the incoming STP BPDU and analyze the fields. 2 Check the STP timer configuration of the neighbor switches. 3 If the values are out of range, then correct the values.
Warning Messages IP FDB Entry IP FDB entry not added as no route is available Software Version ExtremeWare 6.1.5b20 Hardware Version All Explanation This message indicates that after an ARP resolution the pending packets in ARP are sent out on an unavailable route. Action Upgrade to ExtremeWare 6.1.7 or later.
IP Output (Slow Path) IP Output (Slow Path) ip_output.c 1039: moption(add): No space for mca ddr. (224.0.0.9/150.65.197.1). Software Version ExtremeWare 4.x Hardware Version All Explanation This message indicates a possible slow path issue from the IP option processing routine. Action Use the show log and show tech-support commands and contact Technical Support to isolate the slow path problem.
Warning Messages IPX Next Hop Interface IPX forward: next hop interface = input interface Software Version ExtremeWare 6.x Hardware Version All Explanation This message indicates a misconfiguration of IPX interface numbers. Action Use the show ipxstats command to determine the VLAN with the highest number of discards. Attach a sniffer to the VLAN to identify the specific problem. Check the configuration of switches and end-stations.
iQuery Message iQuery Message SLB 3DNS: SlaveProcessRequest: invalid iQuery message SLB 3DNS: IQMessageValidate: invalid iQuery message: len 96 failed: crc c9fd316a, iqm_checksum b03e Software Version ExtremeWare 6.x Hardware Version All Explanation These messages indicate that ExtremeWare supports a previous version of 3DNS (v2.0). The newer versions of 3DNS send an iQuery hello message that the switch does not recognize. The switch then sends an unrecognized message back to 3DNS.
Warning Messages Link Down Link Up ERROR: Slot 2 port 7 link DOWN, mac link up Software Version ExtremeWare 6.2.0 and earlier Hardware version All except VDSL Explanation This message appears during the switch reset time. It indicates that the remote switch might not drop the link. NOTE This is a known issue addressed in PR 1-5CIPQ and 13212. Action Upgrade to ExtremeWare 6.2.1 or manually unplug and plug the port back in.
Load Share Trunk Inactive Load Share Trunk Inactive last message repeated 51 times LRNDROP: LS Trunk inactive port 2 Software Version ExtremeWare 6.x Hardware Version All except VDSL Explanation These messages indicate that when trying to map the incoming load-sharing port (port 2) to the master port, the master port is not active; therefore, the traffic coming into the port will not be forwarded. Action Enable the master port in the load sharing group and re-send the traffic.
Warning Messages MAC Chip write content of VlanCmp table index 13 error on slot 2 port 24 MAC Chip of slot 6 port 18 is not ready read content of VlanCmp table index 2 error on 8 Software Version ExtremeWare 6.x Hardware Version Alpine and BlackDiamond “i” series Explanation These messages indicate that there might be a hardware problem. The I/O modules were not ready to receive packets.
MAC Type MAC Type unknown MAC type on port Mgmt Software Version ExtremeWare 6.1.7b2 and earlier Hardware Version All Explanation This message indicates that you are trying to configure jumbo frames on a port running ExtremeWare 6.1.7b2 or earlier. Action Upgrade to the latest software.
Warning Messages Maximum Block Allocation tBGTask: Reached maximum otp block allocation for MSM-A tBGTask: Reached maximum otp block allocation for slot 1 Software Version All ExtremeWare versions Hardware version All except VDSL Explanation These messages indicate that the system is out of PTAG blocks. This can happen if you configure a large number of multicast groups, VLANs, etc. NOTE The system can have a maximum of 6,000 PTAG blocks.
msgQSend Message Queue Full msgQSend Message Queue Full hfoDloadDatabases: msgQSend message queue full Software Version ExtremeWare 7.1.1 and later Hardware Version BlackDiamond with MSM-3 module Explanation This message indicates that the message queue, which sends configuration information from the master MSM-3 to the slave MSM-3 when Hitless Failover is enabled, is full. This means that some of the configuration did not get successfully transferred to the slave MSM-3.
Warning Messages MsgQ Send Error stpTimer: MsgQ send error Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that MsgQ was unable to send message to call timer function. Action If there are multiple messages, contact Technical Support.
MSM Module Type Mismatch MSM Module Type Mismatch Syslog: MSM module type mismatch has been detected. This configuration only supported while migrating from MSM64i's to MSM-3's. Console (after login): WARNING: An MSM module type mismatch has been detected. Slots MSM-A and MSM-B must both contain MSM-3's or MSM64i's. This module type mismatch is only supported while migrating from MSM64i's to MSM-3's.
Warning Messages ngRxFirst Failed ngRxFirst failed WTX1 - (2, 0, ffff) Software Version ExtremeWare 6.1.x Hardware Version Alpine and BlackDiamond Explanation This message indicates that a module was removed from the slot while the CPU was communicating with it. Action If you removed a module, no action is necessary. If you did not remove a module, and you see this message repeatedly in the log, the hardware might be faulty. Contact Technical Support.
No Associated STPD Port No Associated STPD Port bpduFilter: No associated Stpd Port for "x" vlanId "y" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the BPDU was received, but no corresponding STPD exists. Action Ensure that the STPD is configured and up.
Warning Messages No BIF for VLAN ID bindVlanPortToStpPort: No bif for vlan Id "x" port "y" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that a bridge I/f (BIF) was not found while binding the VLAN port to the STPD. Action Retry the port addition. If it repeatedly fails, contact Technical Support.
No EAPSD-Bridge Links Exist No EAPSD-Bridge Links Exist eaps.c 5156: Warning! No Eapsd-Bridge links exist Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that there are no VLANs added to EAPS yet. Action There are no VLANs to delete from EAPS domain.
Warning Messages No Matching FDB Entry deleteStpFilter: No matching emistp entry for VlanId "x" in fdb Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that an attempt was made to remove a non-existent FDB entry. Action If there are multiple messages, contact Technical Support.
No Message Buffer No Message Buffer bpduFilter: NULL mbuff Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that there is no MBuf for the received BPDU. Action If there are multiple messages, contact Technical Support.
Warning Messages No Protected VLANs Configured eaps_runtime.c 2115: Warning! No Protected Vlans configured in domain "eaps1" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that there are no protected VLANs in the EAPS domain. Action Ensure that all the data VLANs carrying traffic are added to EAPS as protected VLANs. Otherwise, there could be a loop in the network.
otpRamBusy otpRamBusy SYST: SYST: KERN: SYST: Port 12 link down Port 12 last message repeated 1 time otpRamBusyWait: slot=0 quake=0x1 reg=0x4000 FAILED2 set: 0 0220 -> 40000000 Software Version ExtremeWare 6.1 Hardware Version All Explanation These messages indicate that there is a problem accessing the port translation table. Action Reboot the switch. If the problem persists after the reboot, upgrade to the latest software. If problem persists, RMA the switch or module.
Warning Messages PDU Received on Wrong Port eaps_runtime.c 1498: Warning! Received on Primary port 1:1 for EAPS(eaps1) Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the primary port received an EAPS Health-check PDU. The Health-check PDUs must be received only on the secondary port. Action The EAPS task may have become unstable. Contact Technical Support.
Port Binding Failed, Bound to Another STPD Port Binding Failed, Bound to Another STPD bindStpPortToStpd: stpPort "x" PortId "y" bound to different Stpd "z" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the binding of the STP port to the STPD failed because the STP port is already bound to another STPD. Action If there are multiple messages, contact Technical Support.
Warning Messages Port Binding Failed, Bound to that STPD bindStpPortToStpd: stpPort "x" PortId "y" already bound to Stpd "z" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the binding of the STP port to the STPD failed because the STP port is already bound to that STPD. Action Ignore.
Port Creation Failed, Bad STPD Instance Port Creation Failed, Bad STPD Instance stpPortCreate: No stpd for stpd inst "x" stpPortInst "y" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the STP port creation failed due to a bad STPD instance. Action Retry the port addition. If it repeatedly fails, contact Technical Support.
Warning Messages Port Creation Failed, No PIF stpPortCreate: No pif for port "x" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the STP port creation failed because there is no physical I/f (PIF) structure. Action Retry the port addition. If it repeatedly fails, contact Technical Support.
Port Creation Failed, Not Enough Ports Port Creation Failed, Not Enough Ports stpPortCreate: Not enought stp port Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the STP port creation failed because the maximum number of STP ports exists. Action Reduce the number of STP ports in the configuration.
Warning Messages Port Deletion Failed, No Matching Port stpPortDelete: No matching stp port("x") Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the STP port deletion failed because the STP port does not exist. Action Retry the port deletion. If it repeatedly fails, contact Technical Support.
Port Deletion Failed, Not Bound to PIF Port Deletion Failed, Not Bound to PIF stpPortDelete: No pif-stp port("x") bindings Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the STP port deletion failed because the STP port is not bound to the Physical Interface (PIF). Action Retry the port deletion. If it repeatedly fails, contact Technical Support.
Warning Messages Port Mapping Failed processCardNmcConnectionDown: set nmc (11) channel (1) internal loop error port mapping failed on slot 12 internal port 2! port mapping failed on slot 12 internal port 2! processCardNmcConnectionDown: set nmc (10) channel (1) internal loop error port mapping failed on slot 11 internal port 2! port mapping failed on slot 11 internal port 2! Card removed from slot 2 Software Version Extr
Port Not Configured Port Not Configured eaps_runtime.c 1460: Warning! Received PDU() on an unconfigured port(1:1) for EAPS(eaps1) Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that an EAPS PDU was received by a port that has not been configured to be a ring-port. Action Configure the EAPS domain with the correct ring-ports, or configure the control VLAN with the correct ports and connections.
Warning Messages Port Not in VLAN eaps_runtime.c 1222: Warning! Port (1:1) not in vlan "v1" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the port selected to send out the EAPS PDU has not been added to the control VLAN. The PDU cannot be sent. Action Configure the EAPS control VLAN correctly by adding both the ring-ports to it as tagged ports.
Port Unbinding Failed, STP Not Disabled Port Unbinding Failed, STP Not Disabled unbindStpPortFromStpd: Stp still running on stpPort "x" PortId "y" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the unbinding of the STP port from the STPD failed because the STP is not disabled. Action Disable the STP on the STPD and retry.
Warning Messages Port Write Error stpPortWriteNv: Error "x" saving to nv Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that an error occurred while writing the port configuration to NVRAM. Action If there are multiple messages, contact Technical Support.
Power Consumption Exceeds Slot Threshold Power Consumption Exceeds Slot Threshold WARNING: PSU-[Internal | External] consumption of x.xW exceeds the x% threshold of x.xW for slot x Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that the total measured power exceeds the consumption set in the CLI. The default is 70%. Action Monitor the situation. If a message indicating the return to normal does not display, you may need to RMA board.
Warning Messages Power Consumption Exceeds System Threshold WARNING: PSU consumption of x.xW exceeds the x% threshold of x.xW for the system Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that the total measured power exceeds the consumption set in the CLI. The default is 70%. Action Monitor the situation. If a message indicating the return to normal does not display, you may need to RMA board.
Problem Stopping Domain Problem Stopping Domain eaps.c 3708: Problem in stopping domain "eaps1" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that an error occurred while attempting to stop an EAPS domain. Action The EAPS task may have become unstable. Contact Technical Support.
Warning Messages PTAG Error, List Tags ptagAdd: error - no free LIST tags Software Version ExtremeWare 4.1.19b2 Hardware Version Summit48 Explanation This message indicates that the system has run out of internal resources. Action Contact Technical Support to troubleshoot the problem.
PTAG Error, Memory Blocks PTAG Error, Memory Blocks tBGTask: Block 4010 on slot 7 is already free Software Version All ExtremeWare versions Hardware Version BlackDiamond Explanation This message indicates that you are trying to free PTAGs which are already freed. This is generally a configuration and environment related software problem. The error message can appear for a task other than tBGTask.
Warning Messages QoS Duplicate Port SNMP PORT QOS Trying to insert duplicate instance 1 Software Version ExtremeWare 6.x Hardware Version All “i”series Explanation This message indicates that there is an attempt to set up the same SNMP port twice in the QoS configuration. Action No action is necessary.
redirectServerList Not in Use redirectServerList Not in Use redirectServerListCb: 0 0 not inuse Software Version ExtremeWare 6.1.5b23 and earlier Hardware Version All “i” series Explanation This message indicates that a server failed health checking. The fix has been implemented in ExtremeWare 6.1.5b23 or later. Action Upgrade to the latest software.
Warning Messages Send BDPU Failed send_bpdu_packet: Can't send bpdu Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the send BPDU process failed. Action If there are multiple messages, contact Technical Support.
Send Message Failed Send Message Failed bpduFilter: Cannot send message to Stp task Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that bpduFilter could not send a message to the STP task. Action If there are multiple messages, contact Technical Support.
Warning Messages Slave Port Active Slot 2 port 3 slave port link active while master slot 2 port 1 active Slot 1 port 1 primary port link active Slot 1 port 4 redundant port link active Software Version ExtremeWare 6.2.0b60 and 6.2.1b20 Hardware Version Alpine, BlackDiamond, and Summit Explanation These messages indicate that there is a redundancy with load sharing on Gigabit TX ports (such as those on the Alpine G4Ti, BlackDiamond G8Ti, and Summit5i).
SNMP IP QoS ACL Missing SNMP IP QoS ACL Missing SNMP IPAQOS Could not find entry instance 5083 to delete Software Version All ExtremeWare versions Hardware Version All Explanation This message indicates that you tried to delete an ACL that does not exist, which can occur due to one of the following: • ACL has already been removed through CLI. • There is no ACL with that number. • Typographical or syntax error. Action No action is necessary.
Warning Messages Spurious Link State ERROR: Slot 1 port 5 lane 1 spurious int 8 ERROR: Slot 1 port 5 lane 1 spurious int 8 ERROR: Slot 2 port 5 lane 1 spurious int 8 Software Version ExtremeWare 6.1.5b20 Hardware Version BlackDiamond Explanation These messages indicate that the link state of the specified port is changing very quickly. Make sure that there is a stable connection to the switch. Action Upgrade to the latest software.
STP Disabled for Port STP Disabled for Port setPortState: Stp disabled for stpPort "x" PortId "y" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the attempt to change the port state failed because STP is not enabled on the STP port. Action Enable STP and retry.
Warning Messages STP Disabled for STPD setPortState: Stp disabled for Stpd "x" inst "y" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the attempt to change the port state failed because STP on the STPD is not enabled. Action Enable STP and retry.
STPD Instance Does Not Exist STPD Instance Does Not Exist Stpd instance nonexisting Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates an internal timer error. Action If there are multiple messages, contact Technical Support.
Warning Messages STPD Malloc Failed STPD malloc failed "x" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that STPD creation failed. Action Retry STPD creation. If it repeatedly fails, contact Technical Support.
STPD Table Malloc Failed STPD Table Malloc Failed STPD table malloc failed "x" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that STPD creation failed. Action Retry STPD creation. If it repeatedly fails, contact Technical Support.
Warning Messages STP Port Creation Failed stpPortParseNv: stpPortCreate err for stpd "x", portId "y" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that STP port creation failed. Action Retry STP port creation. If it repeatedly fails, contact Technical Support.
STP Port Does Not Exist STP Port Does Not Exist stp port nonexisting Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that there is an internal timer error. Action If there are multiple messages, contact Technical Support.
Warning Messages STP Port Malloc Failed Stp port malloc failed["port","port table"] "size" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that STP port creation failed because it was unable to allocate memory. Action Retry STP port creation. If it repeatedly fails, contact Technical Support.
STPD Tag Removal Failed STPD Tag Removal Failed unconfigStpdFilters: Stpd tag is from a brigde that ingores BPDU Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that a request to remove an FDB entry for the BPDU failed because the carrier VLAN has “ignore BPDU” enabled. Action Disable “ignore BPDU” for carrier VLAN.
Warning Messages SuperBridge Error SuperBridge w3back, No ptag for Port 2 vlan 2005 Software Version ExtremeWare 6.x Hardware Version All Explanation This message indicates a configuration error. It can occur when you attempt to delete a non-existent super-VLAN on a switch configured with ESRP or VLAN aggregation. Action Check configurations. If you are unable to isolate the problem, contact Technical Support.
System Overheated System Overheated SYST: System is overheated. (65532 C) SYST: System is overheated. (65532 C) Software Version ExtremeWare 4.x and 6.x Hardware Version All Explanation This message indicates that the system temperature is over the limit. Action Contact Technical Support for assistance as this problem has been fixed in newer versions. Upgrade to the latest software.
Warning Messages Stuck Interrupt ERROR: Slot 1 indicates a stuck interrupt, disabling interrupts to the blade Software Version ExtremeWare 6.1.9 and later Hardware Version BlackDiamond Explanation This message indicates that on the slot there is no interrupt between the MSM and the module; therefore, stuck interrupt occurs. The software disables the further interrupts and brings the module down. Action Re-insert the particular module in that slot.
Task Exceeded Stack Boundary Task Exceeded Stack Boundary Task 0xyyyyyyyy has exceeded its own stack boundry. Contact Extreme Technical Support Software Version ExtremeWare 720bx Hardware Version All “i” series Explanation This message indicates that stack corruption occurred for specified task. Action Contact Extreme Technical Support.
Warning Messages Task Failed stpInit: taskSpawn failed Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates an STP initialization error. Action Reboot.
Timer Delay Exceeds Capacity Timer Delay Exceeds Capacity WARN: STP timer delay exceeds capacity, "x" "y" "z" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates an internal timer error. Action If there are multiple messages, contact Technical Support.
Warning Messages Timer Error, Non-Expired Bucket Expiry event for non-expired bucket "bucket" "current time" "next expiry" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates internal timer error. Action If there are multiple messages, contact Technical Support.
Timer Error, Wrong Bucket Timer Error, Wrong Bucket Stp timer expired in wrong bucket "bucket#" "bucket#" "timer type" "timer instance" "port instance" "previous timer" "next timer" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates internal timer error. Action If there are multiple messages, contact Technical Support.
Warning Messages tNetTask Panic tNetTask panic: m_freem Software Version ExtremeWare 6.1.x Hardware Version All Explanation This message indicates that the switch is attempting to free memory (tNetTask) that has already been freed. Action Use the show memory command and the top command to capture the detail and configuration. Check task utilization peaks and IPFDB, and check the log for any message indicating that allocated memory space is maxed out.
Trying to Put Block in Free List Trying to Put Block in Free List tDvmrpTask: Trying to put otp block f428 in free list: already free: Slot=9 Index=244 Owner=2 Software Version All ExtremeWare versions Hardware Version All except VDSL Explanation This message indicates that the software is trying to free already freed memory. Action Use the show tech-support and show log commands to capture the log and contact Technical Support.
Warning Messages Unable to Allocate PTAG stpInit: Unable to alloc ptag Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates an STP initialization error. Action Reboot.
Unable to Create Message Queue Unable to Create Message Queue stpInit: Unable to create msg Q Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates an STP initialization error. Action Reboot.
Warning Messages Unable to Locate MAC updateEdpFilter378: Unable to locate EDP MAC (VID=0xfff) Software Version ExtremeWare 6.1.9b22 Hardware Version Alpine Explanation This message indicates that the switch tried to delete an EDP destination MAC 00E02B000000 FDB entry that is not in the FDB table. This example is an invalid VLAN ID. You will see this error in the log after changing the VLAN tag. Action If you see this message once or twice in the log, no action is necessary.
Unable to Start Watchdog Timer Unable to Start Watchdog Timer Error: unable to start wd timer Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the watchdog timer could not be started. Action Reboot.
Warning Messages Unknown Message Type stpTask: Unknown message type %d Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that an unknown message was received by STP task. Action If there are multiple messages, contact Technical Support.
Unknown PDU Type Unknown PDU Type eaps_runtime.c 1654: Warning! Unknown pduType , EAPS="eaps1", [MAC=] Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that this version of the software does not recognize the EAPS PDU. Action You should probably upgrade to the newer release of the software.
Warning Messages Unknown TLV bpduFilter: Port "x" unknown TLV: type "y" length "z" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that there is a bad TLV in the received BPDU. Action Check the configuration of peer device.
Untagged Port Mismatch Untagged Port Mismatch sysObjSetStpPort: Active untagged stp port mismatch Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the management function failed to set the port mode of untagged port to something other than 802.1D. Action You must use a tagged port for encapsulations other than 802.1D.
Warning Messages Cannot Update ACL Rule Update can't be done atomically Node=211.133.249.128: chngs=5 np=211.133.249.128 L=0 R=0 par=158.20 ß 158.205.225.9 admin: create access-list acl041 ip destination any source 211.133.249.128 / 25 perm Software Version ExtremeWare 6.1.9b11 and 6.20b60 Hardware Version All “i” series Explanation These messages indicate that the newly configured ACL rule cannot be automatically synced on all hardware. ExtremeWare 6.
User Account Out of Range User Account Out of Range User account instance 65535 out of range Software Version All ExtremeWare versions Hardware Version All Explanation This message indicates that an invalid user name or password came via telnet or the console. This message appears in the log when the user name or password does not match. Action No action is necessary.
Warning Messages VLAN Already Controls Another Domain eaps.c 5025: Warning! vlan "v1"cannot control >1 EAPS domains. Already controls EAPS "eaps1" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the VLAN has already been added as a control VLAN to an EAPS domain. Action If a VLAN has been added as a control VLAN to an EAPS domain, it cannot be added as a control or protected VLAN to another EAPS domain.
VLAN Already Exists VLAN Already Exists eaps.c 5010: Warning! Vlan "v1"<->Eapsd "eaps1" exists Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that this VLAN has already been added to the EAPS as control/protected. Action Inform the user that this VLAN has already been added to an EAPS domain.
Warning Messages VLAN Bind Failed bindVlanPortToStpPort: configBifStpPort failed. Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that while attempting to bind the VLAN port to STPD, the bind failed. Action Retry the port addition. If it repeatedly fails, contact Technical Support.
VLAN Does Not Contain Port VLAN Does Not Contain Port eaps_runtime.c 1936: Warning! Protected vlan "v1" does not have port 1:1 added to it Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that there is nothing to block because the ring-ports have not been added to the protected VLAN. Action Configure the protected VLANs by adding the ring-ports to it.
Warning Messages VLAN ID Already Bound bindVlanPortToStpPort: vlan Id "x" port "y" is already bound to other instance. Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that while attempting to bind the VLAN port to STPD, the bind failed because the bridge interface (BIF) is already bound. Action Remove the STP port from the other STPD and retry.
VLAN ID No Longer in STPD VLAN ID No Longer in STPD Vlan Id "x" is no longer in the stpd with Id "x" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the STPD ID is set to a VLAN tag and that tag was removed from the STPD. Action Add the VLAN back to STPD or change the STPD ID.
Warning Messages VLAN Is Not Control VLAN eaps.c 4153: Warning! Vlan is not Control Vlan in EAPS "eaps1" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the specified VLAN is not an EAPS control VLAN. Action Use the correct control VLAN name to delete it from EAPS.
VLAN Is Not Protected VLAN VLAN Is Not Protected VLAN eaps.c 4279: Warning! Vlan is not Protected Vlan in EAPS "eaps1" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the specified VLAN is not an EAPS protected VLAN. Action Use the correct protected VLAN name to delete it from EAPS.
Warning Messages Port Number Out of Range port #<%d> from slot %d out of range Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The port number you have entered through CLI or selected in the Vista web page is out of range. Action If you have entered a wrong port number, enter or select the correct port number. Verify the log to confirm that the message does not appear again.
Slot Number Out of Range Slot Number Out of Range slot #<%d> out of range Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The slot number you have entered through CLI or selected in the Vista web page is out of range. Action If you have entered a wrong slot number, enter or select the correct slot number. Verify the log to confirm that the message does not appear again.
Warning Messages Too Many Announcements on Port port=<%d> has receive too many Announce Software Version ExtremeWare 7.3 and later Hardware Version Alpine, Summit300-24, Summit300-48, and Summit400-24p Explanation The switch has received too many announce messages from the access point (AP). If the switch receive too many announce messages from the access point, the access point will be moved to ERR state. This could be due to errors in the wireless configuration.
FDB Scan Entries Remapped FDB Scan Entries Remapped FDB Scan: entry 7489/3 marked 'remapped' FDB Scan: (8) sw/hw dpath mismatch M-BRD bucket 7489 entry 3 Software Version ExtremeWare 6.2 and later Hardware Version All “i” series Explanation Copies of software FDB and hardware FDB are compared when fdb-scan is enabled. If there is a mismatch between the two, the entries are marked as "remapped". The message shows the index of the bucket and the entry for the fdb entry with the discrepancy.
Warning Messages Problem with I/O Modules Diags detected 1 other i/o blade(s) with a transceiver problem. Problem may lie on MSM-A Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond Explanation Two or more I/O modules or MSM have problem with the ASICs. Enable transceiver-test and show diagnostics sys-health-check CLIs to verify the errors. Action Contact Technical Support.
Bridge and EAPSD Link Exists Bridge and EAPSD Link Exists EAPSD c-tky01-myg-1 - Vlan W1015 has already been added to EAPS domain. Software Version ExtremeWare 7.0 and later Hardware Version All Explanation The bridge and the EAPSD is already linked. Action Informational only. No action needed.
Warning Messages Changing QoS Policy Default Value qosPConfigQosP:Changing bw setting of default QosP: qp1 Software Version ExtremeWare 6.2 and later Hardware Version All Explanation You are changing the default value of the QoS Policy queue (qp1). This is the value used by all policies by default. Action Informational only. No action needed.
Netlogin VLAN: IP Address Not Configured Netlogin VLAN: IP Address Not Configured Network Login vlan %s has no routable interface Software Version ExtremeWare 7.3 and later Hardware Version All Explanation This message indicates that you have not configured an IP address for the netlogin VLAN. Action Configure IP address for the netlogin VLAN.
Warning Messages Write Error While Download in Progress • Attempt to write bootrom while a download is in progress • Attempt to write image while a download is in progress Software Version ExtremeWare 7.3 and later Hardware Version All Explanation These messages indicates that you are trying to download an image while another download is in progress. Action Check if another download is in progress. If another download is in progress, download the new image after the first image is downloaded.
Saving Configuration While Downloading an Image Saving Configuration While Downloading an Image Attempt to write config while a download is in progress Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that you are trying to save the configuration while an image download is in progress. Action Check if image download is in progress. If you are downloading an image, save the configuration after the download is complete.
Warning Messages Vendor Information Not Available • cgiGetVendorEmailAddr: Could not get vendor • cgiSelectRootPage: Could not get vendor • cgiSelectTopPage: Could not get vendor • cgiSelectVendorHelp: Could not get vendor Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that system was not able to find the vendor information of the switch. Action Contact Technical Support.
Bootstrap and Bootloader Not Configured Bootstrap and Bootloader Not Configured AP with 1.52 bootrom is connected to the port=1:1. Configure both bootstrap and bootloader.Sending out trap and moving port to ERR. Software Version ExtremeWare 7.6 Hardware Version Summit 300-48, Summit 300-24, Summit 400-24p, Alpine Explanation The bootstrap version of the access point (AP) connected to port 1:1 is 1.5.2. You are trying to upgrade either the bootstrap or the bootloader.
Warning Messages TFTP Errors on Port Too many TFTP tries made for port 1:1. Sending out trap and moving port to ERR state. Software Version ExtremeWare 7.
DVMRP PDU: Message Queue Send Error DVMRP PDU: Message Queue Send Error dvmrpPdu: msgQSend error Software Version ExtremeWare 7.3 and later Hardware Version All “i” series and Summit “e” series Explanation The message indicates that the switch received a DVMRP packet and while enqueuing the DMVP packet to the DVMRP message, the message queue failed. This error would occur when a DVMRP packet is received and enqueueing the DVMP packet to the DVMRP message queue fails.
Warning Messages DVMRP Watchdog Timer: Message Queue Send Error dvmrpWdTime: # msgQSend error Software Version ExtremeWare 7.3 and later Hardware Version All “i” series and Summit “e” series Explanation The message indicates that DVMRP message queue failed while the switch was queuing a timer message (timer tic) to the DVMRP message queue. Action 1 Disable DVMRP and enable it after some time.
Missed ESRP Hello From Neighbor Missed ESRP Hello From Neighbor edp.c 3080: VLAN=Mas05A, Missed ESRP Hello 1 from neighbor (00:e0:2b:84:ec:00) Software Version ExtremeWare 6.2.2 and later Hardware Version BlackDiamond Explanation This message indicates that the switch missed a hello from the neighbor. This message can be enabled or disabled on a per vlan basis using the debug-trace setting. Action Informational only. No action needed.
Warning Messages Network Connectivity to Switch Lost A300 lost network connectivity to Attachment switch, pls check topology for connectivity on %P Software Version ExtremeWare 7.5 Hardware Version All Explanation This message indicates that the switch did not receive the health check packets from the access point (AP). Action Verify the connection between the switch and the access point.
Too Many TFTP Attempts Too Many TFTP Attempts Too many TFTP tries made for port=%P. Sending out trap and moving port to ERR Software Version ExtremeWare 7.5 Hardware Version All Explanation This message indicates that the file transfer to the access point failed. Action Check whether: 1 TFTP server is reachable. 2 TFTP server contains the configured files. 3 Configured files in TFTP are of the correct Type. 4 Disable and enable the port. Check whether the problem occurs again.
Warning Messages DVMRP: Buffer Allocation Failed DVMRP: Failed to alloc memory to Tx GraftAck Software Version ExtremeWare 7.3 Hardware Version All “i” series Explanation This message indicates that the switch failed to allocate buffer for transmitting a DVMRP (Distance Vector Multicast Routing Protocol) graft acknowledgment. Action 1 Disable and Enable DVMRP. 2 Restart the switch.
PIM Checksum Failed PIM Checksum Failed PIM: chksum failure Software Version ExtremeWare 7.3 Hardware Version All “i” series and “e” series Explanation This message indicates that the checksum in the PIM header of the PIM packet received is incorrect. Action Informational only. No action needed.
Warning Messages PIM Packet Type Unknown PIM: unknown pim pkt with type Software Version ExtremeWare 7.3 Hardware Version All “i” series and “e” series Explanation This message indicates that the message type in the PIM packet received is not matching any of the message types defined in the RFC 2362. Action Informational only. No action needed.
PIM Version Failure PIM Version Failure PIM: version failure Software Version ExtremeWare 7.3 Hardware Version All “i” series and “e” series Explanation This message indicates that the PIM version number in the PIM packet received is not 2. Action Informational only. No action needed.
Warning Messages Bridge Learn Frame Dropped • LRNDROP: (da=%m, sa=%m) no SAK • LRNDROP: (da=%m, sa=%m) DA is rtr mac • LRNDROP: (da=%m, sa=%m) no bridge • LRNDROP: (da=%m, sa=%m, v=%d) not TLS vlan • LRNDROP: NO_VPST bucket=%x entry=%d ptag=%x • LRNDROP: SA(%m) is multicast Software Version ExtremeWare 7.3 Hardware Version All Explanation This message indicates that the bridge learn frame was dropped.
Malformed Packet Malformed Packet PKTDROP: malformed packet Software Version ExtremeWare 7.3 Hardware Version All Explanation This message indicates that the switch received a malformed packet and it was dropped. Action Informational only. No action needed.
Warning Messages Errors In SNMP Requests Received • Received an SNMP Request from …: Not Writable (non-leaf object) • Received an SNMP Request from …: Not Writable (Wrong Type) • Received an SNMP Request from …: ASN Parse Error • Received an SNMP Request from …: Bad Value • Received an SNMP Request from …: End of MIB • Received an SNMP Request from …: Read only • Received an SNMP Request from …: No Such Object Software Version ExtremeWare 7.3, Extreme ware 7.4, Extreme ware 7.
Active Untagged STP Port Mismatch Active Untagged STP Port Mismatch Active untagged STP port mismatch Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation This message indicates that the stpport is not associated in the stptree of the Pif in untagged format, but the port mode is configured as DOT1D Action 1 Delete the stpport. 2 Create the stpport. 3 Configure the port mode.
Warning Messages Another Active Dot1D Another dot1d is already active Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that you are trying to configure a dot1d while another dot1d is active. The Pif can have only one 802.1D capsulation mode. Action Remove the port from the second stp domain which is configured as 802.1D mode.
STP Domain Instance Does Not Exist STP Domain Instance Does Not Exist STP domain instance does not exist Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the time expiry function is unable to find the STP domain because the timer routine refers to an stpdomain already removed. Action Informational only. No action needed.
Warning Messages STP Port Does Not Exist STP port does not exist Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the time expiry function is unable to find the STP port because the timer routine refers to an STP port that was already removed. Action Disable the STP domain and enable it again.
VLAN ID Not in STP Domain VLAN ID Not in STP Domain Vlan ID %d is no longer in the STP domain with ID %d Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation This message indicates that the VLAN ID is not longer in the STP domain. You cannot use the VLAN ID in the selected STP domain. Action Change the dot1q tag on the stpd to other active vlan ID in the stp domain.
Warning Messages BPDU Carrier VLAN Not Auto-Bind BPDU carrier vlan %s must be Auto-Bind with stpd %s\n Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the selected VLAN does not have the default STP domains. Action Configure the default STPD domain to the bridge and then configure the dot1qtag.
STP Disabled STP Disabled • Stp disabled for stpPort 0x%x PortId %d • Stp disabled for Stpd 0x%x inst %d Software Version ExtremeWare 7.3, ExtremeWare 7.4, ExtremeWare 7.5 Hardware Version All Explanation • Stp disabled for stpPort 0x%x PortId %d—The STP is trying to change the port state; even though the STP is disabled on the port. • Stp disabled for Stpd 0x%x inst %d—The STP is trying to change the port state; but the STP domain is disabled.
Warning Messages DVMRP: Received Bad Metric DVMRP: Rx bad metric(). in the route>/ Nbr= Rte=
DVMRP: Prune Received From Non-DVMRP Neighbor DVMRP: Prune Received From Non-DVMRP Neighbor DVMRP: Rx Prune( / ) w/o nbr on vlan( ) Software Version ExtremeWare 7.3 Hardware Version All “i” series Explanation This message indicates that a prune is received from a source that is not a DVMRP (Distance Vector Multicast Routing Protocol) neighbor.
Warning Messages DVMRP: Received Short Prune NBR On VLAN DVMRP: Rx short prune ( / ) nbr on vlan() Software Version ExtremeWare 7.3 Hardware Version All “i” series Explanation This message indicates that the length of the DVMRP (Distance Vector Multicast Routing Protocol) prune packet received is lesser than the minimum prune packet length of 20 bytes.
DVMRP: Access Violation DVMRP: Access Violation DVMRP: Access violation. addr. in the IP header> RxRoute / from
Warning Messages DVMRP: Allocating Packet Memory On VLAN Failed DVMRP: Access violation. addr. in the IP header> RxRoute / from
DVMRP: Allocating Memory For NBR Failed DVMRP: Allocating Memory For NBR Failed DVMRP: Cannot alloc mem for Nbr () Software Version ExtremeWare 7.3 Hardware Version All “i” series Explanation This message indicates that the switch failed to allocate memory to add a new DVMRP neighbor. This message appears only if the debug-trace is configured to dvmrp-neighbor. Action Restart the switch.
Warning Messages DVMRP: No Route For Group DVMRP: dvmrpIfPruneTime: Task no route for addr.> cpt grp
DVMRP: Allocating Memory To Transmit Prune Failed DVMRP: Allocating Memory To Transmit Prune Failed DVMRP: Failed to alloc memory to Tx Prune ( / ) Software Version ExtremeWare 7.3 Hardware Version All “i” series Explanation This message indicates that the switch failed to allocate buffer to transmit a prune message. This message appears only if the debug-trace is configured to dvmrp-message. Action 1 Disable and Enable DVMRP; on the switch and on VLANs.
Warning Messages DVMRP: Group And Source Does Not Match In Graft DVMRP: Group/Src does not match in Graft ( / )!=( / ) Software Version ExtremeWare 7.
DVMRP: NBR With Same IP Address Rejected DVMRP: NBR With Same IP Address Rejected DVMRP: Reject nbr with same IP addr () Software Version ExtremeWare 7.3 Hardware Version All “i” series Explanation This message indicates that the source IP address in the probe packet received is same as the IP address .of the interface on which the packet was received This message appears only if the debug-trace is configured to dvmrp-neighbor. Action Informational only. No action needed.
Warning Messages Support Login Access Disabled • user %s: Support-login access is disabled • user %s: Support-login access is enabled Software Version ExtremeWare 7.5 Hardware Version All Explanation • user %s: Support-login access is disabled—The message indicates that the support login account access is disabled for the user. • user %s: Support-login access is enabled—The message indicates that the support login account access is enabled for the user. Action Informational only. No action needed.
Bridge Entry Not Found Bridge Entry Not Found CANNOT FIND BRIDGE ENTRY Software Version ExtremeWare 7.3 Hardware Version All Explanation This message indicates that the switch was not able to find the bridge ID while sending out an MPLS encapsulated packet over the wire. Action Informational only. No action needed.
Warning Messages Freed MBUF WARNING!!!: THIS IS A FREED MBUF!!! Software Version ExtremeWare 7.3 Hardware Version All Explanation This message indicates that the switch is trying to access the memory buffer that was already been freed. Action Informational only. No action needed.
Corrupted Buffer Detected Corrupted Buffer Detected free(0x%08x) - buffer corruption detected on return by task: 0x%08x\n Software Version ExtremeWare 7.3 Hardware Version All Explanation This message indicates that the switch was not able to free the memory block because it has detected a corrupted buffer. Action Informational only. No action needed.
Warning Messages Accessing Memory Block Failed free(0x%08x) - no such buffer allocated (in task 0x%08x) Software Version ExtremeWare 7.3 Hardware Version All Explanation This message indicates that you are trying to free a memory block that is not allocated. Action Informational only. No action needed.
Operation Blocked Operation Blocked <<>> Software Version ExtremeWare 7.3 Hardware Version All Explanation The message indicates that the ExtremeWare has blocked the operation. Action Informational only. No action needed.
Warning Messages Deleting Bridge Interface for VLAN Failed EAPS Shared-port 1:1 - Cannot delete bridge interface for vlan %s, segment-port 2:1. Value is NULL Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the bridge interface associated to the segment port 2:1 is NULL. Action 1 Delete the VLAN. VLAN will be removed from the EAPS super domain (ESD) and EAPS. 2 Configure the VLAN again.
Adding EAPS Domain Failed Adding EAPS Domain Failed EAPS Shared-port 1:1 - Cannot add EAPS domain EAPS1. Domain EAPS1 with same ring-ports has already been added\n Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that you are trying to add an EAPS domain which has already been added to the EAPS super domain (ESD). You cannot add the EAPS domain already added to the shared port.
Warning Messages Configure EAPS Shared-port On Port Please configure EAPS Shared-port on port 1:1 Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the port should be configured as an EAPS shared port. The port 1:1 belongs to two or more EAPS domains with different ring port or different physical rings. In other words, this port is a common ring port for two or more EAPS domains with different physical rings.
Reached Maximum Limit of ESD Instance Reached Maximum Limit of ESD Instance Reached maximum limit of ESD instances. Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the switch has reached the maximum number of EAPS super domain (ESD) instance. You can configure a maximum of two shared ports on a switch. Action 1 Check the shared port configuration. You can create a maximum of two shared ports per switch.
Warning Messages EAPS Task Not Running EAPS Shared-port 1:1 - EAPS task is not running Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the EAPS task is not running. Action Check whether tEapsTask is running. If tEapsTask is running, then reconfigure the shared port. If tEapsTask is not running, then restart the switch.
PDU Type Unknown PDU Type Unknown EAPS Shared-port 1:1 - Unknown PDU type (%d), [MAC=00:01:30:FB:99:F0] Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the switch has received an unknown EAPS super domain (ESD) PDU from another switch.
Warning Messages Neighbor’s Mode EAPS Shared-port 1:1 - Neighbor's modes must be different from one another Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the you have configured the same mode for the EAPS shared port for the switch and the neighbor. You must use different modes on EAPS shared link. For example, if one end of the shared link is configured as Controller, then the other end should be configured as Partner.
Neighbor Unreachable Neighbor Unreachable EAPS Shared-port 1:1 - Neighbor unreachable Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the EAPS super domain (ESD) controller and the partner do not recognize one another. The message appears if the ESD does not receive segment health PDU and the neighbor state is up. The neighbor state is set to down. Action Check the link status in the EAPS segment.
Warning Messages Segment-Timer Exists for Segment Port EAPS Shared-port 1:1 - Segment-timer already exists for segment-port 2:1 Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the segment-timer exists for segment-port 2:1. Action Informational only. No action is needed.
Shared-port-timer Exists Shared-port-timer Exists EAPS Shared-port 1:1 - Shared-port-timer already exists Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the shared-port-timer already exists. Action Informational only. No action is needed.
Warning Messages EAPS: Port Not Added For Protected VLAN EAPS: Protected vlan u93 does not have port 4:2 added to it Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS domain has the information about a port on the bridge; but the port has already been removed from the bridge. Action 1 Check whether user has removed the port from the bridge. 2 Disable and enable the EAPS domain again.
EAPS: Shared-Port Not Configured EAPS: Shared-Port Not Configured EAPS: Please configure EAPS Shared-port on port 5:1 Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation The message indicates that you need to configure the port as shared port in EAPS. If multiple EAPS domains are sharing a port, configured as secondary and primary, then you must configure the port as a shared port in EAPS to avoid loops. Action Configure the port as a shared port.
Warning Messages EAPSD: Deleting VLAN Interface Failed EAPS: EAPSD eaps1a - Could not delete vlan emistp2a interface from EAPS domain Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS domain cannot delete the interface to the VLAN. EAPS maintains an interface for the VLANs added to the domain. This interface is created when a VLAN is added to the EAPS domain. Action 1 Delete the EAPS Domain.
EAPSD: Protected VLAN Not Added to EAPS Domain EAPSD: Protected VLAN Not Added to EAPS Domain EAPS: EAPSD eaps2a - No Protected Vlans have been added to the EAPS domain Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation The message indicates that the EAPS domain has a control VLAN, but you have not configured a protected VLAN. Protected VLANs and Controls VLAN are part of the EAPS domain.
Warning Messages EAPS: Already The Control VLAN on the Domain EAPS: Vlan cont1a is already the Control Vlan on EAPS domain eaps1a Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the VLAN you are trying to add as a control VLAN is already configured as a control VLAN in another EAPS domain. Control VLAN can be part of only one EAPS domain. To make the EAPS domain functional, you need to configure control VLAN and protected VLAN.
EAPSD: VLAN Already Part of Another EAPS Domain EAPSD: VLAN Already Part of Another EAPS Domain EAPS: EAPSD eaps-up - Vlan verup has already been added to EAPS domain Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation The message indicates that the VLAN has already been added to another EAPS domain. To make the EAPS domain functional, you need to configure a control VLAN and protected VLAN.
Warning Messages 766 ExtremeWare Error Message Decoder
6 Notice Messages Notices are informational messages and do not require corrective action. Check the “Issues Resolved In” sections in the latest ExtremeWare Installation and Release Notes to see if the error message indicates an issue that has been corrected in a recent software release. Current Below Specification NOTICE: Port x:x under current Software Version ExtremeWare 7.
Notice Messages Current Over Specification NOTICE: Port x:x over current Software Version ExtremeWare 7.2 and later Hardware Version FM32P modules only Explanation This message indicates that the measured current is over specification. Action Monitor for more messages. If more messages occur, RMA the board.
Port Cannot Power Port Cannot Power NOTICE: Port x:x cannot power Software Version ExtremeWare 7.2 and later Hardware Version FM32P modules only Explanation This message indicates that the port cannot supply power to the device requesting power. Action Try another port. If no other port available, then RMA blade.
Notice Messages 770 ExtremeWare Error Message Decoder
7 Informational Messages Informational messages do not require corrective action. Check the “Issues Resolved In” sections in the latest ExtremeWare Installation and Release Notes to see if the error message indicates an issue that has been corrected in a recent software release. Bad PoE Hardware Slot X has bad PoE hardware, disabling PoE system Software Version ExtremeWare 7.2.
Informational Messages Calibration Data Updated Slot X updated PoE calibration data to device Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that the blade has old calibration data stored and it is being updated to new values. Action Informational only. No action needed.
Cannot Allocate Memory Buffer Cannot Allocate Memory Buffer can not alloc mbuf for internal EDP diag. Software Version ExtremeWare 6.1.6b19 Hardware Version All “i” series Explanation This message indicates that ExtremeWare ran out of memory buffers that are used to build internal EDP diagnostic packets which are sent out as part of the health-check routines. Running out of memory buffers can be caused by a broadcast flood to the CPU which can exceed available memory buffers.
Informational Messages Disabling EAPS 10.4.2.161 admin: disable eaps Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the user initiated a command to disable EAPS. Action Informational only. No action needed.
EEPROM Read Retried EEPROM Read Retried EEPROM read retried: blade 2 retry count = 2 rc = 1 Software Version ExtremeWare 7.1.1 and later Hardware Version BlackDiamond Explanation This message indicates that the read on an I/O module EEPROM from an MSM had to be retried due to a read error. If the retry count is less than 10, the read was eventually successful. Action This message could indicate a hardware problem. Run diagnostics on the I/O module and the MSM.
Informational Messages Enabling EAPS 10.4.2.161 admin: enable eaps Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the user initiated a command to enable EAPS. Action Informational only. No action needed.
Fail Timer Flag Cleared, EAPS=E05B Fail Timer Flag Cleared, EAPS=E05B eaps_runtime.c 613: EAPS="E05B", Fail-timer-exp flag cleared Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the fail timer expiry flag, which had been set earlier, is now cleared. Action Informational only. No action needed.
Informational Messages Fail Timer Flag Cleared, EAPS=VLAN1 eaps_runtime.c 613: EAPS="VLAN1", Fail-timer-exp flag cleared Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the situation causing the master to miss its health check PDUs has been fixed, or that there is an actual break in the ring. In either case, it is safe to clear the fail timer expiry flag. Action Informational only. No action needed.
Fail Timer Flag Set Fail Timer Flag Set eaps_runtime.c 597: EAPS="VLAN1", Fail-timer-exp flag set Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the fail timer flag is set. This occurs when the fail timer expires, but the fail timer should not expire. If there is an actual break in the ring, the master should receive a Link-Down message from the Transit.
Informational Messages Fast Age Out fast age out: remote(203.133.93.15:1406) local(210.59.224.126:80) fast age out: remote(203.71.154.214:1509) local(210.59.224.126:80) Software Version ExtremeWare 6.x Hardware Version All Explanation These messages indicate that there are too many pending TCP connections to the switch. The switch assumes that it is under a “sync flooding” attack. These pending connections are closed in order to defeat the attack.
Firmware Revision Firmware Revision Slot X - PoE firmware rev = x.x Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message reports the revision number of the PoE firmware on the blade. Action Informational only. No action needed.
Informational Messages Firmware Update Required Slot X requires PoE firmware update Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that the firmware requires updating. Action Informational only. No action needed.
Flush PDU Flush PDU eaps.c 1548: Received Flush_Pdu sent by self ("E38A"). Drop it Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that a flush PDU was sent by this switch to itself. Hence, drop the packet. Action Informational only. No action needed.
Informational Messages High CPU Utilization, mportTask task mportTask cpu utilization is 91% PC: 8063b23 c Software Version All ExtremeWare versions Hardware Version All “i” series Explanation This message indicates the possibility of either a broadcast storm or high number of packets entering the Management port, which is consuming CPU time and could affect other processes. mportTask handles the Management port interrupts.
Log Cleared Log Cleared SYST: Log cleared Software Version All ExtremeWare versions Hardware Version All Explanation This message indicates that someone cleared the log. Action No action is necessary.
Informational Messages Master Domain State Changed to Idle eaps_runtime.c 2858: State Change, Complete => Idle, EAPS="E04B" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the EAPS Master domain has stopped running due to user action, such as “disable eaps”. The domain state is set to Idle. Action Informational only. No action needed.
Master Domain Stopped, Primary Port Status Unknown Master Domain Stopped, Primary Port Status Unknown eaps_runtime.c 2848: Primary Port Change, Up => Unknown Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the EAPS Master domain has stopped running due to a user action, such as “disable eaps”. The port status is set to Unknown. Action Informational only. No action needed.
Informational Messages Master Node State Changed to Complete eaps_runtime.c 2561: State Change, Failed => Complete, EAPS="E05B" Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the master node received its health check PDU, and detected that the ring is healed. It transitions from the Failed state to Complete, and blocks the secondary port. Action Informational only. No action needed.
Master Node State Changed to Failed Master Node State Changed to Failed eaps_runtime.c 2619: State Change, Complete => Failed, EAPS="E05B" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the EAPS master node detected a failure in the ring. This causes its state to transition from Complete to Failed, and opens its secondary port. Action Restore the link on the port that caused the master to go into Failed state.
Informational Messages Master Node State Changed to Init eaps_runtime.c 2600: State Change, Idle => Init, EAPS="E04B" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the EAPS master node has started running. It transitioned from Idle state to Init state because both of its ring-ports are Up. Action Informational only. No action needed.
Master State Changed to Complete Master State Changed to Complete eaps_runtime.c 2904: State Change, Init => Complete, EAPS="E04B" Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the master transitioned from the Init state to the Complete state. While in Init state, the EAPS master receives its health check PDU. This ensures that the ring is Complete. Action Informational only. No action needed.
Informational Messages Memory Allocation Memory has been allocated for gBif Memory has been allocated for gPif Memory has been allocated for gBridge Memory has been allocated for gSystem Finish running diagnostic test Start running diagnostic test ... Software Version ExtremeWare 4.1.15b4 Hardware Version Summit48 Explanation These messages indicate proper memory allocation. Action No action is necessary.
Old Power Supplies Old Power Supplies PWR MGMT: System is using Old AC 220 power values: 480, 518, 3, 1001 Software Version ExtremeWare 6.1.x Hardware Version BlackDiamond Explanation This message indicates that ExtremeWare implemented power supply checking as part of the initialization routines. Messages similar to the above will appear in the startup sequence depending on the type of PSU detected by the system.
Informational Messages PoE Firmware Download Completed Slot X PoE firmware completed successfully Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This log message indicates that the firmware download is complete. Action Informational only. No action needed.
PoE Initialized PoE Initialized Slot X PoE system initialized Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that the PoE system initialized. Action Informational only. No action needed.
Informational Messages PoE Power Supply Unit State Change Detected PoE PSU change on slot X Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that there was a PoE power supply change for the slot. Action Informational only. No action needed.
Port Power State Change Port Power State Change Port x:x power state from to Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that there was a PoE state change for the port. Action Informational only. No action needed.
Informational Messages Port Status Changed to Up eaps_runtime.c 1640: Pdu="Link-Up-Pdu", EAPS="E05B" [MAC=00:01:30:18:45:50] Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the master node received a message from the Transit node indicating that a previously down port has come up. (In this example, the Transit's MAC=00:01:30:18:45:50.) Action Informational only. No action needed.
Power Is Up for Slot Power Is Up for Slot External 48V on slot x is up and running Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates which PoE power supply is up for the slot. Action Informational only. No action needed.
Informational Messages Power Supply Failure, Switching to Backup External 48V Supply failure on slot x, switching to internal 48V Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates a loss of the external PoE power supply and that is it switching to the backup for the slot. All ports will be brought down and then brought back up. Action Informational only. No action needed.
Preforward Timer Expired, EAPS=E38A Preforward Timer Expired, EAPS=E38A eaps_runtime.c 2463: EAPS "E38A" Preforward Timer expired. Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the Transit’s preforward timer expired. In general, the timer should not expire. The timer is usually cancelled after receiving a Ring-Up-FlushFDB message from master.
Informational Messages Preforward Timer Expired, EAPS=VLAN1 eaps_runtime.c 2463: EAPS "VLAN1" Preforward Timer expired. Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the Transit's preforward timer expired. In general, the timer should not expire. The timer is usually cancelled after receiving a Ring-Up-FlushFDB message from master. By default if does not receive a message from the master for six seconds, this timer will expire.
Primary Port Status Changed to Blocked Primary Port Status Changed to Blocked eaps_runtime.c 897: Primary Port Change, Down => Blocked Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the primary port on this Transit node has come up, and is blocked because the domain's state is set to Preforwarding. Action Informational only. No action needed.
Informational Messages Primary Port Status Changed to Down eaps_runtime.c 970: Primary Port Change, Up => Down Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the primary ring-port went down. Action Restore link on primary port.
Primary Port Status Changed to Up, from Blocked Primary Port Status Changed to Up, from Blocked eaps_runtime.c 2523: Primary Port Change, Blocked => Up Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the primary port was being blocked due to preforwarding state. It is now safe to put this port to forwarding state, and mark the port as Up. Action Informational only. No action needed.
Informational Messages Primary Port Status Changed to Up, from Unknown eaps.c 719: Primary Port Change, Unknown => Up Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the EAPS domain is now coming up and is initializing the status of primary ring port. Action Informational only. No action needed.
QoS Profile, Invalid QoS Configuration QoS Profile, Invalid QoS Configuration testBifCreate: Port 28 qos profile QP1 failed admission control CACTestQosP: port 28 qp QP1 minBw(20) testfailed Software Version ExtremeWare 2.x and 4.x Hardware Version All Summit chipset products Explanation This message indicates an invalid QoS configuration. For example, if you configure QP1 to use 50% and QP2 to use 100% (which adds up to 150% of the bandwidth), you will receive this message.
Informational Messages Reached G1 Limitation Reached resource limitation for G1 module support can not support more G1 modules; Check cpu-transmi Software Version ExtremeWare 6.1.x Hardware Version BlackDiamond and Alpine Explanation This error indicates you have installed too many Summit-chipset (G1) modules. You will see this message on a BlackDiamond only if it has Summit-chipset modules. If you get this message on an Alpine, it is a not a problem as the Alpine does not have G1 module.
RIP, MBZ Field RIP, MBZ Field ripInput: REQ pkt from 10.34.1.2 MBZ field of RTE not zero ripInput: RSP pkt from 10.34.1.2 MBZ field of RTE not zero Software Version ExtremeWare 4.x and 6.x Hardware Version All Explanation These messages indicate that the RIP packet failed the sanity check. Must Be Zero (MBZ) indicates that the field in RIPv1 and RTE is not zero on the router. Action Check the RIP version on the routers. Make sure they are using the same version.
Informational Messages Ring Break, Flush Transit FDB eaps_runtime.c 1590: Pdu="RingDown-FlushFdb-Pdu", EAPS="VLAN1" [MAC=xx:xx:xx:xx:xx:xx] Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the master node has detected a break in the ring and sends out a message “RingDown-Flush-Fdb”. This causes all the Transits to flush their FDBs. Action Restore the link on the Transit that caused the break in the ring.
Ring Down, Flush Domain FDB Ring Down, Flush Domain FDB eaps_runtime.c 3433: Received EAPS RingDown FlushFDB on "E16A" Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This EAPS Transit domain has received a message from the EAPS Master that the ring went down and to flush its FDB. Action Informational only. No action needed.
Informational Messages Ring State Complete eaps_runtime.c 3496: Received Health-Pdu, Ring state Complete. EAPS="VLAN1", State Link-Down Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the master thinks the ring is Complete, but a Transit is reporting one of its links to be down. Action If there is one message, it can be treated as an informational item, and no action is required.
Ring Up, Flush FDB on Domain Ring Up, Flush FDB on Domain eaps_runtime.c 3415: Received EAPS RingUp FlushFDB on domain "E15B" Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the EAPS Transit domain received a message from the EAPS Master indicating that the ring came up and to flush its FDB. Action Informational only. No action needed.
Informational Messages Ring Up, Flush FDB on Transits eaps_runtime.c 1590: Pdu="RingUp-FlushFdb-Pdu", EAPS="E15B" [MAC=00:01:30:fe:82:90] Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the master node detected that the ring is healed and sends out a message “RingUp-Flush-Fdb”. This causes all the Transits to flush their FDBs. Also, the Transits in Preforwarding state will unblock their blocked ports, and go into Links-Up state.
Ring-Port State Changed to Link-Down Ring-Port State Changed to Link-Down eaps_runtime.c 975: State Change, Links-Up => Link-Down, EAPS="E16A" Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that a ring-port on this Transit node went down causing the domain to enter the Link-Down state. Action Restore the link on the ring-port that went down.
Informational Messages Secondary Port Status Changed to Blocked eaps_runtime.c 897: Secondary Port Change, Down => Blocked Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the Secondary port on this Transit node had just come up and is blocked because the domain's state is set to Preforwarding. Action Informational only. No action needed.
Secondary Port Status Changed to Down, from Blocked Secondary Port Status Changed to Down, from Blocked eaps_runtime.c 802: Secondary Port Change, Blocked => Down Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the secondary port on master went down and its status changed from Blocked to Down. Action Restore link on Secondary port.
Informational Messages Secondary Port Status Changed to Down, from Up eaps_runtime.c 970: Secondary Port Change, Up => Down Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the secondary ring-port went down and its status changed from Up to Down. Action Restore link on secondary port.
Secondary Port Status Changed to Init Secondary Port Status Changed to Init eaps_runtime.c 2600: State Change, Failed => Init, EAPS="VLAN1" Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the secondary ring-port came up on the master and caused it to transition from Failed state to Init state. The secondary port is blocked immediately. Action Informational only. No action needed.
Informational Messages Secondary Port Status Changed to Preforwarding eaps_runtime.c 903: State change, Link-Down => Preforwarding, EAPS="E16A" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the secondary ring-port came up on this Transit node. The port is blocked and the domain goes into Preforwarding state. Action Informational only. No action needed.
Secondary Port Status Changed to Unknown, from Blocked Secondary Port Status Changed to Unknown, from Blocked eaps_runtime.c 2853: Secondary Port Change, Blocked => Unknown Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the EAPS master domain has stopped running due to a user action, such as “disable eaps”. The port status is set to Unknown. Action Informational only. No action needed.
Informational Messages Secondary Port Status Changed to Unknown, from Up eaps_runtime.c 3311: Secondary Port Change, Up => Unknown Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that this EAPS Transit domain has stopped running due to a user action, such as “disable eaps”. The port status is set to Unknown. Action Informational only. No action needed.
Secondary Port Status Changed to Up, from Blocked Secondary Port Status Changed to Up, from Blocked eaps_runtime.c 2534: Secondary Port Change, Blocked => Up Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the secondary port was being blocked due to preforwarding state. It is now safe to put this port to the Forwarding state and mark the port as Up. Action Informational only. No action needed.
Informational Messages Secondary Port Status Changed to Up, from Down eaps_runtime.c 756: Secondary Port Change, Down => Up Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the secondary port on the master came up and the status changed from Down to Up. Action Informational only. No action needed.
Secondary Port Status Changed to Up, from Unknown Secondary Port Status Changed to Up, from Unknown eaps.c 738: Secondary Port Change, Unknown => Up Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the EAPS domain is now coming up and is initializing the status of the secondary ring port. Action Informational only. No action needed.
Informational Messages SSH Cipher SSH Negotiated algorithms: cipher: 3des-cbc mac: hmac-md5 compression none Software Version ExtremeWare 6.1.x Hardware Version All Explanation This message indicates the supported cipher for the Secure Shell (SSH) session. Action No action is necessary.
System Rebooted System Rebooted SYST: System rebooted Software Version All ExtremeWare versions Hardware Version All Explanation This message indicates that the switch has been rebooted. Action No action is necessary; however, notify the network administrator(s).
Informational Messages Transit Domain State Changed to Idle eaps_runtime.c 3316: State Change, Links-Up => Idle, EAPS="E04B" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that the EAPS Transit domain stopped running due to a user action, such as “disable eaps”. The domain state is set to Idle. Action Informational only. No action needed.
Transit Domain Stopped, Primary Port Status Unknown Transit Domain Stopped, Primary Port Status Unknown eaps_runtime.c 3306: Primary Port Change, Up => Unknown Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the EAPS Transit domain has stopped running due to user action, such as “disable eaps”. The port status is set to Unknown. Action Informational only. No action needed.
Informational Messages Transit Node State Changed to Down eaps_runtime.c 1573: Pdu="Link-Down-Pdu", EAPS="E05B" [MAC=00:01:30:18:45:50] Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that a port went down on the Transit node. In this example, MAC=00:01:30:18:45:50 and will cause the master to go into Failed state. Action Restore the link on the port that went down on the Transit that sent the “Link-Down-Pdu.
Transit Node State Changed to Links-Up Transit Node State Changed to Links-Up eaps_runtime.c 2541: State Change, Preforwarding => Links-Up, EAPS="E16B" Software Version ExtremeWare 6.2.2 and later Hardware Version All Explanation This message indicates that the Transit node transitioned from the Preforwarding state to the Links-Up state. This could be due to receiving a RingUp-Flush-Fdb message from the master, or its preforwarding timer has expired. Action Informational only.
Informational Messages Transit Node State Changed to Links-Up, from Idle eaps_runtime.c 3247: State Change, Idle => Links-Up, EAPS="E04A" Software Version ExtremeWare 6.2.2 or later Hardware Version All Explanation This message indicates that an EAPS Transit node just started running. Because both of its ports are already up, it transitions its state from Idle to Links-Up. Action Informational only. No action needed.
Updating PoE Calibration Updating PoE Calibration Slot X updating PoE calibration data from device Software Version ExtremeWare 7.2.0bx Hardware Version FM32P modules only Explanation This message indicates that the calibration on the blade is newer than what is stored on the blade. Action Informational only. No action needed.
Informational Messages User Logged Out from Telnet User ~5 ~8p logged out from telnet (209.213.212.126) User pjorgensen logged out from telnet (209.75.2) Software Version All ExtremeWare versions Hardware Version All Explanation These messages indicate that a telnet connection was opened to a switch and then closed without entering the user name.
Index Position Index Position Index Position Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates the position of the object ID in the object ID list. Action Informational only. No action needed.
Informational Messages SNMP Object Identification This Object in WLM Object List value is . Software Version ExtremeWare 7.3 and later Hardware Version All Explanation The message indicates that the specified SNMP object ID exists and displays the value of the SNMP object. Action Informational only. No action needed.
Initializing GPP Module Initializing GPP Module gppDisp: Beginning Init! Software Version ExtremeWare 7.3 and later Hardware Version Alpine and Black Diamond (MPLS and PoS modules). Explanation This message is displayed when the general purpose processor (GPP) module is being initialized. The GPP module is responsible for the communication between the executive processor (XP) and the general purpose processor (GPP) of the network process blade. Action Informational only. No action needed.
Informational Messages Aborted Cable Diagnostics in Auto Mode Cable Diagnostics Aborted: Mode [Auto] Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation This message indicates that the user has stopped the cable diagnostics that was running in auto mode. Action Informational only. No action needed.
Started Cable Diagnostics in Manual Mode Started Cable Diagnostics in Manual Mode Manual-Mode Cable Diagnostics Started Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation This message indicates that the cable diagnostics module was started in manual mode. Action Informational only. No action needed.
Informational Messages BootROM image: Bad CRC BOOT ROM image, bad crc Software Version ExtremeWare 7.3 and 7.4 Hardware Version All Explanation The Cyclic Redundancy Check (CRC) of the downloaded file is different from the CRC stored in the image header that was transferred. Action Download the BootROM image again and check whether the problem exists with the new image. If you see the problem again, contact Technical Support.
Updating BootROM Image Updating BootROM Image Updating BOOT ROM image Software Version ExtremeWare 7.4 and later Hardware Version All Explanation This message is logged before the switch starts updating the Flash with the BootROM image downloaded from the TFTP server. Action Informational only. No action needed.
Informational Messages BootROM Image: Wrong Magic BOOT ROM image, wrong magic Software Version ExtremeWare 7.4 and 7.5 Hardware Version All Explanation The switch expected a number at a particular offset of the BootROM image. But the downloaded image contains a different number at that offset. This could be due to one of the following reasons: • You have downloaded a wrong BootROM image. • You have downloaded a corrupt BootROM image. Action Confirm that you have downloaded a BootROM image.
PSU Output Ready PSU Output Ready PSU-x output failure recovered Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond and Alpine Explanation The power cable is inserted properly into PSU. Typically this message is displayed after a PSU output failure is fixed. Action Informational only. No action needed.
Informational Messages Binding IP Address Information Binding IP address 10.0.0.13 to vlan Default server: 10.0.0.1 Software Version ExtremeWare 6.0 and later Hardware Version All Explanation The IP address received from the BOOTP server is bound to the default VLAN. Action Informational only. No action needed.
No Wireless Interface No Wireless Interface Num wireless intfs=0, no AgentX requests sent Software Version ExtremeWare 7.3 and later Hardware Version Altitude 350, Altitude 350-2, and Summit WM series Explanation This message indicates that while creating or processing the MAC filters, the switch could not find any interface configured for wireless. Action Configure interfaces for wireless and then run the command.
Informational Messages File Type Mismatch Image Transfer failed for Wireless port type. Resetting the wireless port . Reason: Image sent is not of A300 Software Version ExtremeWare 7.6 Hardware Version Summit 300-48, Summit 300-24, Summit 400-24p, Alpine Explanation The configured wireless port mode is ExtremeWare, but the file sent is of an unknown type. Action Copy the proper image to the TFTP server.
Latest Image Present in AP Latest Image Present in AP No upgrade required from the network. AP connected to wireless port v:1 has latest runtime image. Loading image from AP FLASH Software Version ExtremeWare 7.6 Hardware Version Summit 300-48, Summit 300-24, Summit 400-24p, Alpine Explanation The latest image is present in the flash. You do not need to upgrade the image. Whenever the access point (AP) is reset, it checks the version of the image installed with the version of the image on the switch.
Informational Messages TFTP Error on Wireless Port Wireless port 1:3. Bootloader transfer failed. Reason : Resetting the wireless port. TFTP Error string can be: • Unknown host • Server not reachable • TFTP general error • Checksum failed Software Version ExtremeWare 7.
TFTP Error – Failed to clear Image on Flash TFTP Error – Failed to clear Image on Flash Clearing AP's flash image failed for port v:10.Error in TFTP. Falling to runtime in flash Software Version ExtremeWare 7.6 Hardware Version Summit 300-48, Summit 300-24, Summit 400-24p, Alpine Explanation This message indicates that the access point failed to clear the runtime image on the Flash because of issues in the TFTP transfer. The access point boots up from the image in the Flash.
Informational Messages Wireless Port Version Conflict Wireless port Version conflict found in transferred . Proceeding to next file type. filetype : bootstrap (or) bootloader Software Version ExtremeWare 7.6 Hardware Version Summit 300-48, Summit 300-24, Summit 400-24p, Alpine Explanation The Flash has the latest image. The access point (AP) proceeds to next file type.
Writing Runtime Image to Flash Writing Runtime Image to Flash A300 connected to wireless port started writing runtime onto flash. DO NOT DISCONNECT A300 or REMOVE ITS POWER until upgrade completes. Software Version ExtremeWare 7.6 Hardware Version Summit 300-48, Summit 300-24, Summit 400-24p, Alpine Explanation The access point (AP) has started to write the runtime image to its flash. Disconnecting the AP or removing the power supply while writing the image to the flash can corrupt the AP.
Informational Messages Wireless Port Version Mismatch: TFTP Failed TFTP failed : Version mismatch for wireless port .But since image type is , proceeding to next file type filetype : bootstrap (or) bootloader Software Version ExtremeWare 7.6 Hardware Version Summit 300-48, Summit 300-24, Summit 400-24p, Alpine Explanation This message indicates that the version information sent by the switch and the version information of the image found in the TFTP server does not match.
PSU-x Output Failed PSU-x Output Failed PSU-x output failure Software Version ExtremeWare 6.2 and later Hardware Version All Explanation The PSU is installed on the chassis, but the power cable is not connected properly. Action Insert the power cable properly.
Informational Messages PSU-A Installed PSU-A installed Software Version ExtremeWare 6.2 and later Hardware Version All Explanation The message indicates that a power supply unit has been installed on the switch. Action Informational only. No action needed.
MAC Address Found In MAC Filter Table MAC Address Found In MAC Filter Table findMACFilterEntry: mac add , stored mac , Software Version ExtremeWare 7.3 and later Hardware Version Altitude 350, Altitude 350-2, and Summit WM series Explanation The mac filter allows you to specify a group of MAC addresses. The filter can be applied to one or more ports and permit or deny action can be specified for the filter.
Informational Messages Card In Blank State BLANK state: Card(%d) msgType=%d arg0=%d arg1=%d Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the card is in BLANK state. Action Informational only. No action needed.
Card Type Not Supported Card Type Not Supported This cardtype not supported in 3802. Leaving powered down Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the card is not supported. The card is left in powered down state. Action Contact Technical Support.
Informational Messages Power Up Card Power up card Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the card is being powered up. Action Informational only. No action needed.
No Power To Support Card No Power To Support Card System does not have enough power left to support card Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the system is not able to power up the card because the available power is not adequate to power up the card. Action 1 Check the power supply. 2 If necessary, replace power supply units. 3 If the problem persists, contact Technical Support.
Informational Messages Power Down Card Power down card Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the card is being powered down due to one of the following reasons: • No power in the switch. • Card incompatible with the current configuration. • Health check failed for the card and the health check action is configured to move the card state to power down. Action Reboot the switch.
Card In Prestart State Card In Prestart State PRESTART state: Card(%d) msgType=%d arg0=%d arg1=%d Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the card is in PRESTART state. Action Informational only. No action needed.
Informational Messages Card Set To Fail State Set card to FAIL Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the card is moved to failed state because the diagnostics failed or the card is not compatible. Action Reboot the switch. If the error appears again, contact Technical Support.
Card Set To Power Down Card Set To Power Down Set card to POWERDOWN Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the card has been removed from the switch and the card state is moved to power down. Action Informational only. No action needed.
Informational Messages Slot Disabled Slot is disabled Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the user has disabled the slot. Action Informational only. No action needed.
Total Number of Cards Powered UP Total Number of Cards Powered UP Set card to START total power up cards: Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that a new card has been inserted in the switch. The message also provides information on the total number of cards that are powered up. Action Informational only. No action needed.
Informational Messages Upgrading Bootstrap: Do Not Remove Power Upgrading bootstrap on wireless port %P. DO NOT DISCONNECT A300 or REMOVE ITS POWER until the bootstrap and bootloader upgrade completes Software Version ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the access point has started upgrading the bootstrap. You should not disconnect A300 or remove power until the upgrade is complete. Action Do not disconnect A300 or remove power until the upgrade is complete.
Upgrading Bootloader: Do Not Disconnect Power Upgrading Bootloader: Do Not Disconnect Power Upgrading bootloader on wireless port %P. DO NOT DISCONNECT A300 or REMOVE ITS POWER until the bootloader upgrade completes. Software Version ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the access point has started upgrading the bootloader. You should not disconnect A300 or remove power until the upgrade is complete.
Informational Messages Operating With Reserve Power The system is operating with reserve power Software Version ExtremeWare 7.5 Hardware Version BlackDiamond Explanation The message indicates that the switch is operating on reserve power. Action Informational only. No action needed.
Bridge Learning: New Entry for Frame Bridge Learning: New Entry for Frame LRNNEW: MAC=%M vid=%d PTAG=%x NPMi=%d Software Version ExtremeWare 7.3 Hardware Version All Explanation The message indicates that the switch is adding a new entry in the bridge table for the current bridge-learning frame. Action Informational only. No action needed.
Informational Messages Bridge Learning: Changing Static Entry Failed LRNCHG: Can't change static entry %d Software Version ExtremeWare 7.3 Hardware Version All Explanation The message indicates that a static entry for this bridge learning frame already exists. The switch ignores the frame. Action Informational only. No action needed.
Bridge Learning: Updating Frame Entry Bridge Learning: Updating Frame Entry LRNCHG: MAC=%M vid=%d PTAG=%x Software Version ExtremeWare 7.3 Hardware Version All Explanation The message indicates that an entry for this bridge learning frame already exists and the switch is updating the entry. Action Informational only. No action needed.
Informational Messages Switch Configuration Changed Using SNMP Switch Configuration changed using SNMP Software Version ExtremeWare 7.5 Hardware Version All Explanation The message indicates that the switch has received a successful SNMP set request. Action Informational only. No action needed.
Output Not in Mirror-card Output Not in Mirror-card outport is not in the mirrorCard exit! 0 Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation This message indicates that the mirror-port is not in the same slot as the mirrored port. Typically such a configuration will be prevented by the CLI interface. Action Reboot the system. If the error appears again, contact Technical Support.
Informational Messages Setting Card State Delayed Delay Delay Delay Delay setting setting setting setting card card card card to to to to REMOVAL POWERDOWN INSERTION DISABLE Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the state transition will be delayed because the card diagnostics is in progress. Action Informational only. No action needed.
Card State Set To Mismatch Card State Set To Mismatch Set card to MISMATCH Software Version ExtremeWare 7.3 Hardware Version BlackDiamond, “i” series Explanation The message indicates the card is moved to MISMATCH state due to one of the following reasons: • Operational parameters of the stack does not match. Operational parameters include; License information, Software Versions and Platform type. • The card type does not match the configured card type.
Informational Messages Card State Set To Unknown Set card to UNKNOWN Software Version ExtremeWare 7.3 Hardware Version BlackDiamond Explanation The message indicates that the card has failed due to one of the following reasons: • Card is not recognized. • Hardware error. The card is placed in unknown state. Action Restart the switch. If the error appears again, contact Technical Support.
Converting Serial EEPROM To New Format Converting Serial EEPROM To New Format Converting serial EEPROM to new format Software Version ExtremeWare 7.5 Hardware Version BlackDiamond Explanation The message indicates that the switch is converting the EEPROM format while initializing the platform. Action Informational only. No action needed.
Informational Messages EEPROM: Wrong Backplane Number Backplane Number %d is wrong Software Version ExtremeWare 7.5 Hardware Version BlackDiamond Explanation This message indicates that the EEPROM backplane number is out of range. Action Informational only. No action needed.
Output Not in Mirror-Card Output Not in Mirror-Card ERROR: The buffer is not pdownload buffer in %s Software Version ExtremeWare 7.5 Hardware Version BlackDiamond Explanation The message indicates that the switch has received a wrong pointer to the download buffer. Action Reboot the system. If the error appears again, contact Technical Support.
Informational Messages ESD Stopped Already stopped Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that the EAPS super domain (ESD) has already been stopped. You can change the shared ports domain mode from controller to partner or from partner to controller. When you change the mode or change the link-id, the ESD should be stopped and restarted. Action If the ESD is running, ignore this message.
ESD Started ESD Started Already started Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the EAPS super domain (ESD) has already been started. You can change the shared ports domain mode from controller to partner or from partner to controller. When you change the mode or change the link-id, the esd domain should be stopped and restarted. Action If the EAPS shared port domain is running, ignore this error message.
Informational Messages ESD Segment Timer Flag Set Segment 2:1 - Seg-timer-failed-flag is Set Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation This message indicates that EAPS super domain (ESD) segment timer flag is set because the segment port could not receive segment health check PDU. Action Check the link status in the EAPS ring topology.
ESD Segment Timer Flag Cleared ESD Segment Timer Flag Cleared Segment 2:1 - Seg-timer-failed-flag is Clear Software Version ExtremeWare 7.2 and later Hardware Version Version Explanation This message indicates that the EAPS super domain (ESD) segment timer flag is cleared because the EAPS received a segment health check message. Action Informational only. No action needed.
Informational Messages Neighbor Reachable Neighbor reachable Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the EAPS super domain (ESD) controller and partner have recognized each other. Action Informational only. No action needed.
Link Down PDU Not Processed Link Down PDU Not Processed Not processing Link-Down-Pdu, because linkId %d matches our own Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the link-down-pdu was not processed because the link-id of the link-down-pdu matches the link-id of the EAPS super domain (ESD) instance. This also indicates that the link-down-pdu is from a neighbor and the shared port of the neighbor is down.
Informational Messages Processing Link Down PDU Processing Link-Down-Pdu on segment-port 2:1 Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the switch is processing the link-down-pdu from the segment because the link-id does not match the link-id of the EAPS super domain (ESD) instance. The link-down-pdu will not be processed if the link-id of the link-down-pdu matches the link-id of the ESD instance.
Segment Timer Expired Segment Timer Expired EAPS Shared Port : Segment timer expired for segment 2:1 Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the segment timer has expired for the segment 2:1. The controller and partner exchanges segment health check messages to inform each other that the segment is alive. This timer expires if the segment health check message does not reach the controller or partner.
Informational Messages ESD Domain Blocked EAPS domain blocking on segment port 2:1, while the Shared-port segment status is up. Setting port to forwarding. (Check neighbor) Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the EAPS super domain (ESD) is blocked on segment port 2:1 while the shared port segment status is up. The port is set to forwarding state. Action Check the neighbor switch. Check whether any segment port link is down.
Shared Port Status Changed to Blocking, from Ready Shared Port Status Changed to Blocking, from Ready EAPS Shared-port 1:1 - State transition from Ready => Blocking Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the shared port state has changed from ready to blocking. This could be because the shared port link is down. Action Check the status of the shared link.
Informational Messages Shared Port Status Changed to Preforwarding, from Blocking EAPS Shared-port 1:1 - State transition from Blocking => Preforwarding Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the port status has been moved from blocking to preforwarding. When the common link is up after a down state, the controller moves from blocking state to preforwarding state. While in preforwarding state, the ports will be blocked.
Shared Port Status changed to Ready, from Preforwarding Shared Port Status changed to Ready, from Preforwarding EAPS Shared-port 1:1 - State transition from Preforwarding => Ready Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the port status has been changed from preforwarding to ready. When the common link is up after a down state, the controller moves from blocking state to preforwarding state.
Informational Messages Shared Port Status Changed to Ready, from Idle EAPS Shared-port 1:1 - State transition from Idle => Ready Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the shared port state has changed from idle to ready. Initially the shared port will be in idle state. After the controller and partner recognize each other, the state changes to ready. Action Informational only. No action needed.
Shared Port Status Changed to Ready, from Blocking Shared Port Status Changed to Ready, from Blocking EAPS Shared-port 1:1 - State transition from Blocking => Ready Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the shared domain state has changed from blocking to ready. This might occur when the shared port link status changed to up, from down. Action Check the shared port link status.
Informational Messages Segment Port Status Changed to Down, from Up EAPS Shared-port 1:1 - Segment-port 2:1 state transition from Up => Down Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation The message indicates that the ESP segment port state has changed to down, from up. This could be due to any of the following reasons: • The segment port is down. • The segment has not received the EAPS share port message. Action Check the status of the shared port segment.
Segment Port Status Changed to Up, from Down Segment Port Status Changed to Up, from Down EAPS Shared-port 1:1 - Segment-port 2:1 state transition from Down => Up Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation ESP Segment port status has changed to up, from down. The port state change could be due to one of the following reasons: • The segment port state has changed to up, from down. • The segment has started receiving the messages. Action Informational only.
Informational Messages Shared Port Status Changed to Up, from Down EAPS Shared-port 1:1 - Shared-port state transition from Down => Up Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation EAPS Shared port status has changed to up, from down. Action Informational only. No action needed.
Shared Port Status Changed to Down, from Up Shared Port Status Changed to Down, from Up EAPS Shared-port 1:1 - Shared-port state transition from Up => Down Software Version ExtremeWare 7.2 and later Hardware Version All “i” series Explanation EAPS Shared port status has changed to down, from up. Action Check the link state of shared port.
Informational Messages EAPSD: Received PDU RingDown Flush FDB PDU EAPS: EAPSD eaps2a - Received PDU RingDown-FlushFdb-Pdu , [MAC=00:01:30:3b:27:00] Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the switch is a transit node and the master node has detected an EAPS ring failure. EAPS master node sends a FlushFDB PDU when it detects a ring failure; all the transit nodes receive and process this PDU.
EAPSD: Received Ring UP Flush FDB PDU EAPSD: Received Ring UP Flush FDB PDU EAPS: EAPSD eaps2a - Received PDU RingUp-FlushFdb-Pdu , [MAC=00:01:30:3b:27:00 Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the switch is a transit node and the master node has detected an EAPS ring up. The master node sends a FlushFDB PDU when it detects that the ring is up. All the transit nodes receive and process the PDU.
Informational Messages EAPSD: Received Link Up PDU EAPS: EAPSD eaps2a - Received PDU Link-Up-Pdu , [MAC=00:01:30:3b:27:00] Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS node, master or transit, has received a link up PDU from another node. EAPS nodes send Linkup-PDU to its neighbors when the EAPS ports, primary or secondary, are up. Action Verify whether the EAPS port is coming up in EAPS ring.
EAPSD: Received Link Down PDU EAPSD: Received Link Down PDU EAPS: EAPSD eaps2a - Received PDU Link-Down-Pdu , [MAC=00:01:30:3b:27:00] Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS node, master or transit, has received a link down PDU from another node. EAPS node sends Linkdown-PDU to the neighbor nodes if the EAPS ports, primary or secondary, are down. Action Check if EAPS port is going down in EAPS ring.
Informational Messages EAPSD: Received Query Link Status PDU EAPS: EAPSD eaps2a - Received PDU Query-Link-Status-Pdu , [MAC=00:01:30:3b:27:00] Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the transit node has received a query link status PDU from the neighbor switches. The EAPS master node sends this PDU to find the status of the links in the ring when the failtimer expires.
EAPSD: Received Health PDU, Ring State Complete EAPSD: Received Health PDU, Ring State Complete EAPS: EAPSD eaps1a - Received Health-Pdu, Ring state Complete. State is Link-Down Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that one of the EAPS port, primary or secondary, is down but the ring is complete through the other port.
Informational Messages EAPSD: Received Health PDU on Primary Port EAPS: EAPSD eaps1a - Received Health-Pdu on Primary port (1:1) Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS Master has received a health check PDU on the primary port. Usually EAPS Master sends Health check PDU on the primary port and receives on the secondary port if the ring is complete.
EAPSD: State Transition to Down, from Up EAPSD: State Transition to Down, from Up EAPS: EAPSD eaps-up - 1:1 state transition from Up => Down Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS ports, primary or secondary, has moved to down, from up. Action Check the link status of the EAPS port.
Informational Messages EAPSD: State Transition to Unknown, from UP EAPS: EAPSD eaps-up - 1:1 state transition from Up => Unknown Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS domain is in disabled state. If you disable an active EAPS domain, the primary and secondary port status will be set to unknown. Action Informational only. No action needed.
EAPSD: State Transition to Up, from Down EAPSD: State Transition to Up, from Down EAPS: EAPSD eaps1a - 1:1 state transition from Down => Up Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS ports, primary or secondary, are getting started. Action Check the link status of EAPS ports.
Informational Messages EAPSD: State Transition to Blocked, from Down EAPS: EAPSD eaps1b - 6:1 state transition from Down => Blocked Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS port came up but found that other EAPS ports are already in up state. To avoid a loop, the port is blocked. Action 1 Check the link status of EAPS ports. 2 Make sure one port is in up state and other ports are in blocking state.
EAPSD: State Transition to Unknown, from Blocked EAPSD: State Transition to Unknown, from Blocked EAPS: EAPSD eaps-up - 4:2 state transition from Blocked => Unknown Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS domain is disabled. If you have disabled the EAPS domain, the primary and secondary port status is set to unknown. The port moves from blocking state to unknown state. Action Informational only.
Informational Messages EAPSD: State Transition to Up, from Blocked EAPS: EAPSD eaps2a - 1:1 state transition from Blocked => Up Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation The message indicates that the port has moved from the blocking state to UP. In EAPS master node, if the primary and secondary ports are up, the secondary port will be in blocking state.
EAPSD: State Transition to Up, from Unknown EAPSD: State Transition to Up, from Unknown EAPS: EAPSD eaps-up - 1:1 state transition from Unknown => Up Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS domain is enabled. Initially, the port state will be in unknown state and the state moves to UP after the EAPS domain is enabled and the physical link status is UP. Action Check the state of EAPS domain.
Informational Messages EAPSD: State Transition to Link Down, from Links Up EAPS: EAPSD eaps1a - State transition from Links-Up => Link-Down Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that in the EAPS transit node, the physical link status of the EAPS port is being moved to down from the up state. This message appears on EAPS transit node only. Action Check the link status on transit eaps node.
EAPSD: State Transition to Preforwarding, from Link Down EAPSD: State Transition to Preforwarding, from Link Down EAPS: EAPSD eaps1a - State transition from Link-Down => Preforwarding Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that in the EAPS transit node, the EAPS port is transitioning from the link down (physical link down) to the UP state.
Informational Messages EAPSD: State Transition to Links Up, from Preforwarding EAPS: EAPSD eaps1a - State transition from Preforwarding => Links-Up Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS port is transitioning to Up state from the link down (physical link down) state. The EAPS transit node has received a FLUSH PDU from the EAPS master, and the node is moving the port state from preforwarding to link up.
EAPSD: State Transition to Idle, from Complete EAPSD: State Transition to Idle, from Complete EAPS: EAPSD eaps-up - State transition from Complete => Idle Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that EAPS master domain was disabled. EAPS master will move to Idle state from complete state.
Informational Messages EAPSD: State Transition to Failed, from Complete EAPS: EAPSD eaps-up - State transition from Complete => Failed Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS master domain has failed. EAPS master is moved to failed state if any of the port on the EAPS ring is down and the EAPS master is not able to receive the health check PDU on the secondary port.
EAPSD: State Transition to Init, from Idle EAPSD: State Transition to Init, from Idle EAPS: EAPSD eaps-up - State transition from Idle => Init Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS master domain is enabled and the port ring ports are in up state. The EAPS master can be in any of the following states: • INIT • IDLE • FAILED • COMPLETE Action Informational only. No action needed.
Informational Messages EAPSD: State Transition to Failed, from Idle EAPS: EAPSD eaps1a - State transition from Idle => Failed Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS master domain is enabled and one of the port ring port is down or both the ports are down. The EAPS master can be in any of the following states: • INIT • IDLE • FAILED • COMPLETE Action Check the ring ports status on EAPS master node.
EAPSD: State Transition to Links Up, from Idle EAPSD: State Transition to Links Up, from Idle EAPS: EAPSD eaps2a - State transition from Idle => Links-Up Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS transit domain is enabled and both the ring ports are up. The EAPS transit can be in any of the following states: • IDLE • LINK-UP • LINK-DOWN • PREFORWARDING Action Informational only. No action needed.
Informational Messages EAPSD: State Transition to Complete, from Init EAPS: EAPSD eaps-up - State transition from Init => Complete Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS master has moved to complete state. The EAPS master moves to complete state when the EAPS master is in Init state, both the ring ports are up, and the EAPS master receives the health check PDU on the secondary port.
EAPSD: State Transition to Failed, from Init EAPSD: State Transition to Failed, from Init EAPS: EAPSD eaps-up - State transition from Init => Failed Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS master has moved to Failed state from Init state. EAPS master moves to failed state from init state if: • The EAPS master receives Link-Down PDU from the Transit switches.
Informational Messages EAPSD: State Transition to Init, from Failed EAPS: EAPSD eaps1a - State transition from Failed => Init Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation The message indicates that the EAPS master has moved to Init state from failed state. The EAPS master moves to init state if both the ring ports are up, but the health check PDU is not received on the secondary port.
EAPSD: State Transition to Complete, from Failed EAPSD: State Transition to Complete, from Failed EAPS: EAPSD eaps1a - State transition from Failed => Complete Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS master has moved to complete state from failed state. The EAPS master moves to complete state when both the ring ports are up and it receives health check PDU on the secondary port.
Informational Messages EAPSD: State Transition to Idle, from Failed EAPS: EAPSD eaps1a - State transition from Failed => Idle Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation The message indicates that the EAPS master has moved to idle state from failed state. The EAPS master moves to idle state when the user stops the EAPS domain.
EAPSD: Link Down State Not Changed EAPSD: Link Down State Not Changed EAPS: EAPSD eaps1a - Link-Down State unchanged Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS transit domain has moved to link-down state. The EAPS transit domain moves to link-down state if any of the ring port is down. The message appears if any port is moving to down state while another ring port is already down.
Informational Messages EAPSD: Preforward Timer Expired EAPS: EAPSD eaps1b - Preforward-timer expired Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the preforwarding timer has expired and the port is about to open. The EAPS port is moving to up state from link-down (physical link down) state.
EAPSD: Fail Timer Expiry Flag Set EAPSD: Fail Timer Expiry Flag Set EAPS: EAPSD eaps-up - Fail-timer-exp flag set Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS master domain has set the fail timer expiry flag. The flag is set if the fail timer expired; if the EAPS ring is broken and it is not able to receive the health check PDU. Action Check the link status in EAPS ring.
Informational Messages EAPSD: Fail Timer Expiry Flag Cleared EAPS: EAPSD eaps-up - Fail-timer-exp flag cleared Software Version ExtremeWare 7.2 and later Hardware Version All “i” and “e” series Explanation This message indicates that the EAPS Master domain has cleared the fail timer flag. The message appears when the EAPS ring link is restored and the EAPS master starts receives the health check PDU on the secondary port.
Bootloader Upgrade Complete Bootloader Upgrade Complete bootloader upgrade done. New image will be loaded when AP reboots Software Version ExtremeWare 7.7 Hardware Version All Explanation The message indicates that the bootloader was upgraded successfully. Action This is informational only. No action needed.
Informational Messages Bootloader Upgrade Failed Upgrade bootloader failed. AP has the latest version. Software Version ExtremeWare 7.7 Hardware Version All Explanation The message indicates that upgrading the bootloader, while the access point is online, failed because the AP already has the latest version. Action This is informational only. No action needed.
Stack Reconverged Stack Reconverged Stack Reconverged : IP 00:04:96:1f:1f:e6 0.0.0.0 Current mac 00:04:96:1f:1f:e7 Prev mac Software Version ExtremeWare 7.7 Hardware Version All Explanation The message indicates that the stack manager failed and the stack has reconverged with the new stack manager. Action Check the reason for the failure. Contact Technical Support if the failure is due to watch dog reboot or a system crash.
Informational Messages Secondary Radius Server Selected Secondary Radius server selected at Software Version ExtremeWare 7.8 Hardware Version All Explanation This message informs that the secondary radius server selected for authentication is at . Similarly, in case of Radius Accounting server, the message is displayed as: Secondary Accounting server selected at Action This is informational only. No action needed.
Primary Radius Server Selected Primary Radius Server Selected Primary Radius server selected at Software Version ExtremeWare 7.8 Hardware Version All Explanation This message informs that the primary radius server selected for authentication is at . Similarly, in case of Radius Accounting server, the message is displayed as: Primary Accounting server selected at Action This is informational only. No action needed.
Informational Messages Radius Receive Time Out RADIUS: Receive timed out %d times, retrying Software Version ExtremeWare 7.8 Hardware Version All Explanation This message indicates the number of times the radius server has timed out to respond to the switch. Similarly, in case of Radius Accounting server, the message is displayed as: RADIUS: Receive timed out %d times, retrying Action This is informational only. No action needed.
Invalid Message Authenticator Invalid Message Authenticator Invalid Message Authenticator Software Version ExtremeWare 7.8 Hardware Version All Explanation This message informs that the message authenticator value received is an invalid and the user is not authenticated. Action Verify whether the radius server is configured correctly and then retry.
Informational Messages User Authenticated by Radius Server RADIUS: User session mac was successfully authenticated by radius Software Version ExtremeWare 7.8 Hardware Version All Explanation This message informs that the radius server at authenticated the user whose mac is and the session ID successfully Action This is informational only. No action needed.
Nonexistent Radius User or Wrong Password Nonexistent Radius User or Wrong Password RADIUS: User %s does not exist or incorrect password Software Version ExtremeWare 7.8 Hardware Version All Explanation This message shows that the user does not exist in the users list at the radius server or the password is incorrect. Action Check if the username and password is correct at the user end. If the user name and password is correct, then verify whether the user is listed in the radius server.
Informational Messages 938 ExtremeWare Error Message Decoder
8 Debug Messages Debug messages are informational only to track software defects and does not require corrective action. Check the “Issues Resolved In” sections in the latest ExtremeWare Installation and Release Notes to see if the error message indicates an issue that has been corrected in a recent software release. 100 Messages Queued 100 messages queued Software Version ExtremeWare 4.1.
Debug Messages Failed to Add Address Failed to add 224.0.1.35/139.78.97.27/f7 to ipmc fdb Software Version ExtremeWare 6.1.x Hardware Version All “i” series Explanation This message indicates that the maximum limit of 256K entries in the FDB has been met. There is no available space to add the multicast flow for the multicast address (224.0.1.35) coming from the source address (139.78.97.27) in the VLAN ID hex F7. Action Verify the size of the FDB tables.
Invalid Destination Invalid Destination invalid dest 172.25.42.227 of route from 172.25.42.185 (af 2) Software Version ExtremeWare 2.x and 4.x Hardware Version All Summit chipset products Explanation This message (af 2) indicates that it is a normal internal debug message. Anything other than af 2 indicates a problem. Action No action is necessary.
Debug Messages MAC Based VLAN MACVLAN_STATE_CHANGE: Port 3:14--> MEMBER_VLAN MACVLAN_ADDPORT: adding port 3:14 to vlantechnical Software Version All ExtremeWare versions Hardware Version All Explanation These messages indicate that a port (port 3:14) was removed from a VLAN (MACVLANDiscover) and has been added to another VLAN (vlantechnical). This occurs because the port is enabled to use the MAC-based VLAN algorithm. Action No action is necessary.
pqmWaitKill Failed pqmWaitKill Failed pqmWaitKill Failed. Card 1CntlReg=0xff. killPacket: HW pqmWaitRx failed Software Version All ExtremeWare versions Hardware Version BlackDiamond Explanation These messages indicate that an I/O module was removed while the CPU was trying to read packets from it. Action No action is necessary.
Debug Messages PTAG Error, NGDelCard last message repeated 8 times ptagNGDelCard: ngotp.c 490 Software Version ExtremeWare 4.x Hardware Version BlackDiamond Explanation These messages indicate that the MSM(s) are not able to communicate with the I/O module(s). Action Check the system and look for any other log messages. Contact Technical Support to help isolate the problem.
QuakeWaitPbut2CacheXfer Failed QuakeWaitPbut2CacheXfer Failed quakeWaitPbuf2CacheXfer Failed. Card 0 Ctl=0x20000. Software Version ExtremeWare 6.1.7b9 Hardware Version Summit5i Explanation This message indicates that there is a transient failure in the driver. If this indicated a hardware problem, the log message would be: quakeWaitPbuf2CacheXfer Failed. Card 0 is removed. Without the second part of message, the failure is just temporary.
Debug Messages Recv Buffers Not Empty Recv buffers not empty on slot 3 port 18 mask 13d Software Version ExtremeWare 4.x Hardware Version BlackDiamond and Summit Explanation This message indicates that the switch was not able to remove frames from the MAC hardware. You can see this message when a port comes up or if the link transitions. The symptom might accompany connectivity loss on the ports. Action Check the log to see if there are link transitions.
RIP/VLSM RIP/VLSM ripSupply: Error 51 sending sendto: S_errno_ENETUNREACH ripSupply: Error 51 sending sendto: S_errno_ENETUNREACH msg dst 150.43.246.127 msg dst 150.43.246.31 Software Version All ExtremeWare versions Hardware Version All Explanation These messages indicate that you are trying to implement VLSM with RIP1. Action Check network topology and ensure that the network is reachable. Configure interfaces for RIPv2 support.
Debug Messages Failed to Send IP FDB Age Message Failed to send ip fdb age message Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation The message indicates that the switch failed to send the IP FDB age message because of an error in the ageing process. Action If you see the message repeatedly, reboot the switch. If the reboot does not fix the problem, contact Technical Support.
Failed to Send FDB Age Message Failed to Send FDB Age Message Failed to send fdb age message Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation The message indicates that the switch failed to send the FDB age message because of an error in the ageing process. Action If you see the message repeatedly, reboot the switch. If the reboot does not fix the problem, contact Technical Support.
Debug Messages MAC Address Authenticated RpFinishUrlSearch: mac already authenticated Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation Before a requested URL or path is matched with a predefined URL or path in the switch and the corresponding redirect page is sent to the supplicant, the switch verifies whether the supplicant, identified by the MAC address, is already authenticated or not.
RpSearchNetLoginRomObjectList: Searching for URL Path RpSearchNetLoginRomObjectList: Searching for URL Path RpSearchNetLoginRomObjectList: Searching for Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation This message indicates the path specified by the supplicant will be matched with the paths or pages predefined in the switch. Action Informational only. No action needed.
Debug Messages Requested URL Not Found Did not find the requested URL RpSearchNetLoginRomObjectList Software Version ExtremeWare 7.3 Hardware Version All “i“ series and “e“ series Explanation The URL specified in the supplicant does not match any of the URLs predefined on the switch. The value of the index in the message indicates the number of predefined pages with which the requested URL has been matched. Action Check the URL or path specified in the supplicant.
Associated MAC Not Found Associated MAC Not Found MAC Not found on slot 3 port 1 - val010000000 val1 10000000 Software Version ExtremeWare 6.2 and later Hardware Version BlackDiamond and Alpine Explanation The switch could not find the MAC associated to port on slot 3. Action Run diagnostics to isolate the issue in the hardware. Reboot the system. If problem persists, contact Technical Support.
Debug Messages Conflicting IP Address – Route Ignored Next Hop 172.31.128.254 in route 0.0.0.0 from 172.31.128.170 is a local next hop addr. Ignoring this route Software Version ExtremeWare 7.3 and later Hardware Version All Explanation If the next hop address of a route is same as that of the incoming interface IP address, the route will be ignored. Action Check if the next hop address of this route is same as that of the incoming interface IP address.
Card State Information Card State Information the current card state is Operational the prev card state is Operational Software Version ExtremeWare 7.3 and later Hardware Version BlackDiamond Explanation The message indicates that the card state before handling card hardware failure due to control message timeout. Action Run diagnostics on the hardware. Contact Technical Support, if required.
Debug Messages Set Request Failed on OID Internal error. Unknown request of type %d for function %s Software Version ExtremeWare 7.3 and later Hardware Version Altitude 350, Altitude 350-2, and Summit WM series Explanation This message indicates that a set request failed on the object ID. Action Verify that the set request being set is correct.
Invalid Learn from NMC Card Invalid Learn from NMC Card LRNDROP: Invalid learn from NMC %d (%d) Software Version ExtremeWare 7.3 and later Hardware Version BlackDiamond Explanation The message indicates that the switch failed to read from the network management controller (NMC) card. Action 1 Run diagnostics to identify the issues with NMC 2 Correct the issues with NMC. 3 Contact Technical Support, if required.
Debug Messages Access Violation: Packet Rejected DVMRP: pkt rejected for Access violation Software Version ExtremeWare 7.3 and later Hardware Version All “i” series Explanation The message indicates that the source address in the DVMRP packet received either matches a configured trusted gateway entry with the action as deny/drop; or does not match any of the entries in the configured trusted gateway list on that interface.
IP DA installed In Hardware FDB Table IP DA installed In Hardware FDB Table ipfdbLpmIpdaAdd: IPDA= nhIP= Software Version ExtremeWare 7.3 Hardware Version All “i” series Explanation This message indicates that an IP DA is installed in the hardware FDB tables. NOTE This message is logged only when the debug logging is turned on. This message does not indicate an error. Action Informational only. No action needed.
Debug Messages No Matching Filter For VLAN-Port Combination no matching filter for this vlan/port combo exit! Software Version ExtremeWare 7.3 Hardware Version All “i” series and “e” series switches Explanation This message indicates that the switch encountered an error while updating the FDB on a port for which mirroring was enabled. Action Restart the switch. If the problem appears again, contact Technical Support.
FDB Updated On Port FDB Updated On Port port (port-no) otp vlan mac: Software Version ExtremeWare 7.3 Hardware Version All “i” series and “e” series switches Explanation This message indicates that there was an event on the switch that updated the FDB on a port for which mirroring was enabled. NOTE This message is logged only when the debug logging is turned on. This message does not indicate an error. Action Informational only. No action needed.
Debug Messages Updating FDB On Port With Mirroring Enabled running out of ptags exit! 0 Software Version ExtremeWare 7.3 Hardware Version All “i” series Explanation This message indicates that the switch encountered an error while updating the FDB on a port for which mirroring was enabled. Action Restart the switch. If the problem appears again, contact Technical Support.
Radius Authentication Request Sent Radius Authentication Request Sent Radius authenticate request sent to for session Software Version ExtremeWare 7.
Debug Messages Radius Unreachable or Incorrect Radius IP Radius@ unreachable, incorrect radius IP or shared secret Software Version ExtremeWare 7.
Packet Header Packet Header : Code%d:%s, Identifier %d, Length %d, Authenticator %s Software Version ExtremeWare 7.8 Hardware Version All Explanation This message is the header of the packet that is sent or received Action Informational only. No action needed.
Debug Messages Attributes in the Packet : Attribute: Type%d:%s, Length %d, Value %s Software Version ExtremeWare 7.8 Hardware Version All Explanation This message displays each attribute that is present in the packet. Action Informational only. No action needed.
Index Numerics 100 messages queued 3DNS version problem 802.
no interface structure no PTAG for port unable to allocate memory unassociated name broadcast storms Btree insert failed buckets non-expired wrong Buffer corrupted bugs invalid situation runtime 293 674 304 308 71, 598, 773, 784 561 680 681 747 107 106 C Cable Diagnostics failed on port cabling problems cache problems calibration data checksum error data illegal data updated required on slot required, programming failure cards auto polling, disable auto polling, enable blank,state cannot send Error gettin
manual diagnostics memory allocation failed missed packets, CPU Diffserv Examination resources rules per port DLCS DNS AP server configuration domains already exists flush FDBs Master, state changed to Idle Master, stopped maximum limit problem stopping ring Up, flush FDB Transit, state changed to Idle Transit, stopped DOSprotect filter precedence, conflicts remove ACL timeout, restarting ACL timer Dot1D active dot1dStpPortEntry dropped bytes condition clear condition set DVMRP access violation bad metric b
port,configure preforwarding ready ring port root-blocker, state segment and bridge,status segment interface segment port interface, removing segment port interface,adding segment port,port segment timer segment timer,expiry segment-port,unknown segment-port-timer shared port domain state task not running timer creation failure up EAPSD disabling domain ESD instance fail timer expiry, flag set fail timer expiry,flag cleared health PDU, received Health-Pdu received link down,state unchanged Link-Down-Pdu,rec
configuration error delete entry delete failed Delete L2 FDB entry enabling entry flags entry not added entry not found error accessing information failed to add address install failed IPDA subnet lookup memory test no matching entry permanent entry table port,updated registration failed restoring permanent FDB MAC entries ring break, flush transit ring Down, flush domain ring Up, flush domain ring Up, flush Transit scan entries remapped send age message, failed send IP FDB age message, failed session timeo
IP SA allocation failed IPDA NP card subnet lookup IPX interface iQuery, invalid message 224 449 377, 449 622 623 J jumbo frames 627 L L2 FDB link speed, invalid link transitions blizzard error connectivity loss down port up, MAC down spurious state change load-sharing port not present port speed invalid redundancy on ports trunk inactive log cleared Log Filter associated log target copy delete does not exist exceeds maximum length factory default insufficient memory match parameter maximum configured m
1403 1424 1460 1498 1548 1573 1590 1640 1654 1936 1937 2009 2115 2429 2451 2463 2523 2534 2561 2600 2619 2639 2799 2848 2853 2858 2904 3247 3306 3311 3316 3396 3413 3415 3433 3496 3502 3604 3708 3797 384 397 407 4095 4153 4192 421 4279 4450 453 4853 4886 4946 5010 5025 5043 5063 5156 5217 5230 5660 5713 597 613 ExtremeWare Error Message Decoder 74 103 649 640 783 830 810, 814 798 689 697 84 618 638 67, 68 831 801, 802 805 823 788 790, 819 789 64 568 787 821 786 791 832 829 822 828 78 93 813 811 812 591 75
memory problems missed packets module type mismatch MSM-B, Master no communication programming FLASH rebooted by slave seating problems spoofing attack Multicast ptagIndex threshold 39 61 631 201 569, 944 359 169 102 108 170 N netJob error network connectivity checking loss next hop interface ngRxFirst failed NMC slave not alive node state change Master, Complete Master, Failed Master, Init Transit Down Transit, Links-Up Transit, to Links-Up Note icon, meaning notice messages NVRAM running configuration n
EDP checksum failed external checksum error flapping incorrect state insufficient memory internal checksum error invalid path cost invalid PIF invalid secondary port invalid speed link down link speed link state mapping failed message send failed mismatch, delete failed no trunk ID not configured not in VLAN not ready power state change primary, status changed to Blocked primary, status changed to Down primary, status changed to Unknown primary, status changed to Up secondary, status changed to Blocked seco
delete Route Blackhole ignored interface not specified IP address, conflicts unicast route-map maximum configured router, out of resources RTIF instance,invalid rule does not exist Rx Buffer allocation failed 362, 363 200 954 366 954 200 239 44 440 549 157 S seating ACK error I/O modules MSM or I/O module Secure Shell session cipher server not in use SFLOW configuration parse failed configuration parsing slave configuration error port active slot disabled slots calibration required checksum error clear lo
Boot ROM flooding incompatible version system chunk NULL diagnostic failure flash memory error initialization failed overheated power consumption too high rebooted system initialization minimum mode system recovery action 276 780 281 178 wrong bucket TLV, unknown type transient failure Transit domain state changed to Idle stopped Transit nodes flush FDBs state changed to Down state changed to Links-Up trunk inactive Twister access timeout typographical conventions 175 U 110 946 43 285 675 654 827 T T
No memory available no protected configured none added to EAPS not configured as control not configured for EAPS not control VLAN not found not in STPD not protected VLAN renaming default VLAN translation flush mask wrong index in set request VLAN-Port no matching filter VLSM, implementing with RIP1 VRRP enabling on interface initialization memory allocation failure message task multicast no buffer null interface queue creation failed task spawn failed virtual router instance WD timer VRRP Table no memory a
