Log Reference for SwitchBlade® x3100 and iMAP Series Switches - Release 15.0 - Issue 1 Log Reference for SwitchBlade® x3100 and iMAP Series Switches - Release 15.
Acknowledgments This product includes software developed by the University of California, Berkeley and its contributors. Copyright ©1982, 1986, 1990, 1991, 1993 The Regents of the University of California. All rights reserved. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). Copyright ©1998-2008 The OpenSSL Project. All rights reserved.
Table of Contents 1 Overview of Logs / Alarms System - - - - - - - - - - - - - - - - - - -1-1 1 Interfaces for Communicating with Devices - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1.1 The Command Line Interface (CLI)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1.2 The AlliedView Network Management System (NMS) - - - - - - - - - - - - - - - - - - - - - 1.
2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.1.11 PSE Device Fault- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -2-9 2.1.12 PSE High Temp Detected - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-10 2.1.13 PSE Power Failed - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-10 2.1.14 SD Card Failed - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-10 2.1.
2.3.2 ARP Filtering Configuration Not Supported - - - - - - - - - - - - - - - - - - - - - - - - - 3-8 2.3.3 ARP Filtering Resources Exceeded - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-8 2.3.4 Boot Failed - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-9 2.3.5 Card Diags Failed- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-10 2.3.
2.15 IGMP004 - mcMACLimitPerPortExceeded - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-31 2.15.1 Not Applicable - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-31 2.16 IGMP005 - mcFirstRouterDetected - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-31 2.16.1 Not Applicable - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-31 2.
2.29 RMON002 - fallingAlarm - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2.29.1 Not Applicable- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2.30 SHLF001 - atnShelfFaultRaised - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2.30.1 Port Outage Threshold- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2.30.2 VLAN has no NETWORK facing interface - - - - - - - - - - - - - - - - - - - - - - 2.
2.11 ADSL033 - adslAturPerfUasLThreshTrap - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-14 2.11.1 Not Applicable - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-14 2.12 ADSL034 - adslAtucFailedFastRThreshTrap - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-15 2.12.1 Not Applicable - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-15 2.
2.15.5 Sync Card Clock Error - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2.16 CARD046 - ATNCARDFDBMGMTOVERFLOW - - - - - - - - - - - - - - - - - - - - - 2.16.1 Not Applicable- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2.17 CUC001 - atnCUCFaultRaised - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2.17.1 Not Present - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2.17.
2.22.11 Below Min Upstream Aggregate Rate - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-50 2.22.12 Downstream Differential Rate Exceeded - - - - - - - - - - - - - - - - - - - - - - - - - 4-51 2.22.13 Some ASM Links Down - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-51 2.22.14 Some Parent Interfaces Down - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-51 2.22.
2.31.3 Transmit Degraded - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2.31.4 Downstream Bandwidth Resources Exceeded - - - - - - - - - - - - - - - - - - - - - 2.31.5 Bandwidth Priority Category Resources Exceeded - - - - - - - - - - - - - - - - - - 2.31.6 Link Threshold Exceeded - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2.32 PORT005 - Linkdown - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2.32.
2.47 XDSL004 - HDSL2SHDSLPERFSESTHRESH - - - - - - - - - - - - - - - - - - - - - - - - - 4-78 2.47.1 Not Applicable - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-78 2.48 XDSL005 - HDSL2SHDSLPERFUASTHRESH- - - - - - - - - - - - - - - - - - - - - - - - - 4-78 2.48.1 Not Applicable - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-78 2.49 XDSL006 - HDSL2SHDSLPERFLOSWSTHRESH - - - - - - - - - - - - - - - - - - - - - - 4-79 2.49.
4.8 Cannot create directory for directory copy - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-4 5 Status Poll - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5.1 At least one Node in failure state - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5.2 Interface Failure - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5.
TOC-12 Log Reference for SBx3100 and iMAP Series Switches (Table of Contents)
The Command Line Interface (CLI) Interfaces for Communicating with Devices 1. Overview of Logs / Alarms System 1 Interfaces for Communicating with Devices To receive event and alarm indicators from the Allied Telesis devices, interfaces must have been configured so that these indicators are sent to the proper place and are filtered when necessary. This Section provides an overview of these interfaces.
Interfaces for Communicating with Devices The AlliedView Network Management System officer SEC> PING 172.16.17.18 (172.16.17.18) 64 bytes from 172.16.17.18 (172.16.17.18): icmp_seq=1 --- 172.16.17.18 ping statistics --1 packets transmitted, 1 packets received, 0% packet loss TABLE 1-1 PING command Noun Verb Syntax Description PING PING PING={ ipaddress | hostname } [ FROM { INTERFACE={ type:id | id | ifname } | IPADDRESS=ipaddress } ] [ DELAY=1..900 ] [ LENGTH=1..8192 ] [ NUMBER={ 1..
The AlliedView Network Management System (NMS) Interfaces for Communicating with Devices The traps are then forwarded to the Event Parser, where administrators can change and add various attributes of the trap such as severity or the text message, as well as provide further parsers. Also sent to the Event Parser are information only events about the activity of the AlliedView NMS.
Interfaces for Communicating with Devices The AlliedView Network Management System • System Logs System logs are stored in the NMS database as they are received. The actual logs stored depend on the log types that are enabled and the log filters applied to each managed device. You can view all of the logs received on your network from the System Log Events subview of the Network Events view.
AlliedView NMS Messages for the NMS Configuration Types of Alarm Indicators 1.3 AlliedView NMS Messages for the NMS Configuration There is a set of messages that the NMS produces when there is a problem with the NMS itself. These can be divided into the following areas: • • • • Status Polling of Devices Discovery of Devices NMS Backup Device Backup These messages are included in Section 4 and are listed as messages with the Category NMS.
Types of Alarm Indicators Port Outage Threshold Configuration Location: Slot: 5 Port: 1 Description: Port Fault Set Reason Code: Loss Of Link 2.1.3 Minor Minor is the lowest level of alarm. An alarm with a severity level of minor means that system service is not affected. However, this alarm condition could lead to a major or critical alarm condition; therefore, the user should investigate the alarm. When a minor alarm conditions is raised, the MINOR LED on the CFC faceplate will be illuminated.
Port Outage Threshold Configuration MAJOR CRITICAL Info (010017): Operation Successful Types of Alarm Indicators 32 96 SETDEFAULTS ALARMS THRESHOLD Threshold Mark -------------------------------------MINOR 1 MAJOR 24 CRITICAL 128 Info (010017): Operation Successful officer SEC>> SHOW ALARMS THRESHOLD Threshold Mark -------------------------------------MINOR 1 MAJOR 24 CRITICAL 128 Note that the system will default to known thresholds if they have not been configured.
Types of Alarm Indicators TABLE 1-2 Logs Port Outage Thresholds commands Noun Verb Syntax Description ALARMS THRESHOLD SET SET ALARMS THRESHOLD [ MINOR=value ] [ MAJOR=value ] [ CRITICAL=value ] The alarm thresholds control when the MINOR, MAJOR, and CRITICAL Port Outage Threshold alarms are raised. The values must be non-zero and satisfy the condition of MINOR, MAJOR, or CRITICAL. These signify the lowest number of ports for that alarm to be raised.
Relationship of Logs and Traps with Device Interfaces Log Formats 2.5 Relationship of Logs and Traps with Device Interfaces Since there are multiple ways to report a device status as well as multiple interfaces to display them, the following summarizes how they are related: Traps are produced and associated with: • Standard (RFC-based) MIBs • Allied Telesis products All traps produce logs, and these logs have associated log messages, reason codes, and severities.
Log Formats Log Messages from the CLI A B C D ** PORT003 2010-07-30 07:06:54 Location: Slot: 8 Port: 11 Description: Port Fault Set F Reason Code: Loss of Link 3106 FAULT A = Severity C = Date and time E = Log Type B = Category D = Sequence F = Message FIGURE 1-3 E Sample Log Produced by the Allied Telesis Product (SBx3112) 3.1 Log Messages from the CLI Use the SHOW LOG command to filter logs immediately in the output, for example to show only logs that have a severity of CRITICAL.
Examples Log Message Reference 3.2.2 Fault logs These are the logs that have associated traps as well as reason codes and are the ones included in this document. Refer to Figure 1-3. 3.2.3 Other logs Logs of the type OTHER are for events such as a change of state and are useful for monitoring system activity as the system goes through changes in configuration. Some logs can have associated traps and these are included in this document.
Network Loops Examples 5 Network Loops Network loops may be indicated by service degradations, connectivity problems on a link(s), etc. If the user suspects the presence of a network loop, they should attempt to find the loop and correct it. Some things that the user should look at are recent port and interface provisioning, recent EPSR provisioning, recent STP provisioning, and recent wiring and connections made within their network or connections external to their network.
Listing of Logs and Traps Overview 2. SBx3112 Logs with Traps 1 Overview This section lists the logs that apply to the SBx3112 product only. For logs that apply to both the SBx3112 and iMAP devices, refer to the Section 3. 1.1 Listing of Logs and Traps This is a table that lists the log category / trap text that is the entry point for log descriptions. Each entry is a live link to the section that includes all of the reason codes. 1.
Overview Log and Trap Listing by Reason Code 2 Listing of Logs and Traps Use the following table to locate the Log Category and then the specific Reason Code TABLE 2-1 Logs and Traps for the SBx3112 Log and Trap Text CARD005 - atnCardDefectRaised Reason Code 1.0v Power Failed 2.5V Power Failure 3.
Log and Trap Listing by Reason Code TABLE 2-1 Overview Logs and Traps for the SBx3112 Log and Trap Text Reason Code PORT003 - atnPortDefectRaised Insufficient Shelf PoE Power PD Overload PD Short Circuit PD Thermal Protection PD Underload Detected POE Device Fault PORT005 - atnPortDefectRaised Insufficient Card PoE Power MAC Thrashing Limit Exceeded PSU001 - atnPSUFaultRaised PSU Card Not Present PSU General Fault PSU Hardware Not Recognized PSU High Temperature PSU Input Voltage Fault PSU No Com
Overview Log and Trap Listing by Reason Code Alarms The following components are affected: • • Component Status Alarm CFC200 Degraded Critical CFC200 Failed Major Note: For a simplex system, the alarm is critical since all data traffic could be dropped. 2.1.2 2.5V Power Failure Message 2.5V Power Failure Severity Critical Explanation A problem has been detected with the 2.5v power output on the CFC200, affecting data packet processing. The CFC200 card is probably defective.
Log and Trap Listing by Reason Code Note: Overview For a simplex system, the alarm is critical since all data traffic could be dropped. 2.1.4 (Mate) Control Link Lost Message To Be Supplied Severity Major Explanation The internal control links between the CFCs are Ethernet based, and so there is a condition defined that indicates the loss of control plane links between CFCs. This alarm can be discovered by either CFC in a duplex system. Action Perform the following: Alarms 1.
Overview Log and Trap Listing by Reason Code Alarms 1. If the CFC slot is the active CFC, wait until a low traffic period and perform a switch of activity. Then perform the following steps that are for an inactive CFC. Perform the next step only if the current step does not resolve the problem. 2. Restart the SM. 3. Reseat the SM. 4. Restart the inactive CFC 5. Reseat the inactive CFC. 6. Replace the SM. 7. Replace the inactive CFC. 8.
Log and Trap Listing by Reason Code 8. Alarms Overview If this does not resolve the problem, contact Allied Telesis support. The following components are affected: • • • Component Status Alarm XE4 Degraded Major GE24POE Degraded Major GE24SFP Degraded Major 2.1.
Overview Log and Trap Listing by Reason Code 2.1.8 Datalink Lost (SM Side: Link Slot <4 or 5>) Message Card Failure Raised Severity Major Explanation There are two data (traffic) links between each SM and each CFC (two data links, A and B, to the CFC in slot 4 two data links, A and B, to the CFC in slot 5). The SM runs an interrupt audit on the links, and if communication is lost, the SM will report this and the message will include which link (A or B), and which slot (4 or 5) has been lost.
Log and Trap Listing by Reason Code 3. Alarms Overview If multiple components are showing a temperature change, check the FM4 and replace if necessary. The following components are affected: • • Component Status Alarm CFC200 Degraded Critical CFC200 Failed Critical Note: In a simplex system, the CFC200 will be in a DEGRADED state, but will not go out of service, since traffic would be affected. 2.1.
Overview Log and Trap Listing by Reason Code 2.1.12 PSE High Temp Detected Message To Be Supplied Severity Major Explanation The GP24POE card has exceeded the temperature threshold. Service could be affected. Action Perform the following: 1. Alarms Check the card and replace the GE24POE card. The following components are affected: • Component Status Alarm GE24POE Degraded Major 2.1.
Log and Trap Listing by Reason Code Overview 2.1.15 USB Failed Message To Be Supplied Severity Major Explanation The USB in the active CFC200 has failed, and so files cannot be written in or copied out. Action Perform the following: 1. Alarms Replace the USB device. The following components are affected: • • Component Status Alarm CFC200 Online Major CFC200 Online Major 2.2 CARD044 - Not Applicable 2.2.
Overview Log and Trap Listing by Reason Code Action Perform the following: 1. Alarms To Be Supplied The following components are affected: Component • Status Alarm None 2.4 LOG005 - atnMediaLogStreamError 2.4.1 I/O error writing to media card Message Failed to write management logs to storage media Severity Major Explanation The user has configured log streaming to a media card, but streaming can no longer occur because the card is full or is no longer present.
Log and Trap Listing by Reason Code Overview Explanation The user has configured log streaming to a media card, but streaming can no longer occur because the card is no longer present. The media card has been extracted from the unit. Action Perform the following: 1. Alarms Insert the media card back into the CFC200. The following components are affected: Component • Status Alarm None 2.5 PORT003 - atnPortDefectRaised 2.5.
Overview Log and Trap Listing by Reason Code 2.5.3 PD Short Circuit Message To Be Supplied Severity Major Explanation A subscriber device has caused a short circuit. Action Perform the following: 1. Replace the PD. Alarms The following components are affected: • Component Status Alarm GE24POE Port Degraded Major 2.5.4 PD Thermal Protection Message To Be Supplied Severity Major Explanation A port on the GP24POE card has had to throttle back its power because of the temperature.
Log and Trap Listing by Reason Code Overview Severity Major Explanation There is a fault on the subscriber end. Action Perform the following: 1. Replace equipment at the subscriber end.
Overview Log and Trap Listing by Reason Code 2.6 PORT005 - atnPortDefectRaised 2.6.1 Insufficient Card PoE Power Message To Be Supplied Severity Major Explanation There is not enough power to supply the GE24POE configuration. Action Perform the following: 1. Either add a PSU (if only one is configured) or lower port power limits. Alarms The following components are affected: Component • Status Alarm None 2.6.
Log and Trap Listing by Reason Code Overview 2.7 PSU001 - atnPSUFaultRaised 2.7.1 PSU Card Not Present Message PSU Failure Raised Severity Major Explanation One of the PSU units is not present in the shelf. The shelf can continue to function but there is no backup if the remaining unit fails. Action Perform the following: 1. Alarms Replace the PSU. The following components are affected: • Component Status Alarm PSU Failed Major 2.7.
Overview Log and Trap Listing by Reason Code • Alarms Remove the System PSU and place it in the correct slot. The following components are affected: • Component Status Alarm PSU Failed Major 2.7.4 PSU High Temperature Message PSU Failure Raised Severity Major Explanation This is caused when the temperature sensor on the PSU detects a temperature above 50 degrees Celsius, and puts the PSU into a Failed state. Action Perform the following: Alarms 1.
Log and Trap Listing by Reason Code Overview 2.7.6 PSU No Communication Message PSU Failure Raised Severity Major Explanation A PoE PSU has been installed in one PoE PSU slot and a System PSU is installed in the other PoE PSU slot. (A Hardware Not Recognized log is also output.) Action Perform the following: 1. Alarms Remove the System PSU from the POE (A or B) slot and place it in the correct slot (C or D).
Overview Log and Trap Listing by Reason Code • 2-20 Shelf Degraded Info Log Reference for SBx3100 and iMAP Series Switches (SBx3112 Logs with Traps)
Listing of Logs and Traps Overview 3. Allied Telesis Product Logs with Traps 1 Overview This section is organized as follows. 1.1 Listing of Logs and Traps This is a table that lists the log category / trap text that is the entry point for log descriptions. Each entry is a live link to the section that includes all of the reason codes. 1.2 Log and Trap Listing by Reason Code This includes an overview of the log category / trap text and then a description for each Reason Code.
Overview Log and Trap Listing by Reason Code 2 Listing of Logs and Traps The following table lists the common logs and trap text that apply to the SBx3112 as well as other Allied Telesis NSP products.
Log and Trap Listing by Reason Code TABLE 3-1 Overview Logs and Traps for SBx3112 Log and Trap Text Reason Code (or Message) CARD043 - Not Applicable Not Applicable CFCP001 - atnRedundancyLost Not Applicable CFCP002 - atnRedundancyRestored Unknown CFCP014 - atnEpsrNodeTrap Not Applicable CHAS001 - entConfigChangeTrap Not Applicable FAN001 - atnFanFaultRaised Fan Module Not Present Fans Not Rotating Properly Hardware Not Recognized High Temperature No Communication IGMP000 - mcHighWaterMark
Overview Log and Trap Listing by Reason Code TABLE 3-1 Logs and Traps for SBx3112 Log and Trap Text Reason Code (or Message) INTF003 - (no Trap Message) Classifier Configuration Failed Classifier Configuration Not Supported Classifier Resources Exceeded IPIF001 - (To Be Supplied) IP Interface Configuration Failed LOG005 - atnMediaLogStreamError I/O error writing to compact flash Compact flash unit deactivated Compact flash media not present LOG006 - Not Applicable Not Applicable PORT003 - Linkd
Log and Trap Listing by Reason Code Overview TABLE 3-1 Logs and Traps for SBx3112 Log and Trap Text Reason Code (or Message) SYS004 - atnCardDefectRaised Database Audit Failure Database Transaction Failure Death of non-critical task Flash Write Failure SYS009 - atnShelfFaultRaised Cannot Read MAC Address TRAP003 - coldStartTrap Not Applicable TRAP004 - warmStart Not Applicable TRAP009 - entConfigChangeTrap Not Applicable 2.1 CARD001 - entConfigChangeTrap 2.1.
Overview Log and Trap Listing by Reason Code • • • • • • • • • FX10 Not installed Minor GE Card Not installed Major GE24POE Not Installed Major GE24SFP Not Installed Major NTE8 Not Installed Major POTS24 Not installed Minor SHDSL24 Not Installed Minor XE Card Not installed Major XE4 Not Installed Major Note: For the CFC200, when the inactive is UP-DN for any reason it is a Major alarm because of the shared switch fabrics; bandwidth is lost in this condition, which is different
Log and Trap Listing by Reason Code • • • • • • • • • Overview FX10 Not installed Minor GE Card Not installed Major GE24POE Not Installed Major GE24SFP Not Installed Major NTE8 Failed Major POTS24 Not installed Minor SHDSL24 Online Minor XE Card Not installed Major XE4 Not Installed Major Note: For both iMAP and SBx3112, GE and XE interfaces have an UP/DOWN severity of Major. 2.3 CARD005 - atnCardDefectRaised 2.3.
Overview Log and Trap Listing by Reason Code • • • SHDSL24 Failed Minor XE Card Failed Major XE4 Failed Major Note: Any time there is a card failure on the GE8 the alarm level is major due to service impact. 2.3.2 ARP Filtering Configuration Not Supported Message Card Failure Raised Severity Minor Explanation The reported card is not FILTER setting for ports reported card running an tionality may not behave Action Perform the following: 1.
Log and Trap Listing by Reason Code Overview Explanation The reported card has insufficient resources to support the provisioned ARPFILTER setting for ports on the card. ARPFILTER functionality may not behave correctly. Action Perform the following: 1.
Overview Log and Trap Listing by Reason Code • • • • • • • • • • • • ADSL Failed Minor CES8 Failed Major EPON2 Failed Major FE10 Failed Minor FX10 Failed Minor GE Card Failed Major GE24POE Failed Major GE24SFP Failed Major NTE8 Failed Major POTS24 Failed Minor SHDSL24 Online Minor XE4 Failed Major 2.3.5 Card Diags Failed Message Card Failure Raised Severity Major Explanation The card failed diagnostic testing. The card is probably defective.
Log and Trap Listing by Reason Code Overview be a problem with provisioning associated with the card, or the card may be defective. Action Alarms Perform the following: 1. Verify the load file preference settings. 2. Verify the provisioning data. 3. Disable and enable the card again. 4. Disable the card, reseat the card, enable it again. 5. Disable the card, replace the card, enable it again.
Overview Log and Trap Listing by Reason Code • • • • • • • • • • • • • • • • • Component Status Alarm ADSL Failed Minor CES8 Failed Major CFC12 Degraded Critical CFC200 Degraded Critical CFC200 Failed Major CFC24 Degraded Critical CFC24 Failed Minor CFC4 Degraded Critical CFC6 Degraded Critical CFC6 Failed Minor EPON2 Failed Major FE10 Failed Minor FE2 Failed Minor FX10 Failed Major NTE8 Failed Major POTS24 Failed Minor SHDSL24 Failed Minor Note: For
Log and Trap Listing by Reason Code • • • • • • • • • • • • • • • • • • Overview ADSL Failed Minor CES8 Failed Major CFC200 Failed Major CFC24 Failed Minor CFC6 Failed Minor EPON2 Failed Major FE10 Failed Minor FE2 Failed Minor FX10 Failed Minor GE Card Failed Major GE Virtual Card Failed Major GE24POE Failed Major GE24SFP Failed Major NTE8 Failed Major POTS24 Failed Minor SHDSL24 Online Minor XE Card Failed Major XE4 Failed Major 2.3.
Overview Log and Trap Listing by Reason Code • • • • • • • • • • • • • • • • • Component Status Alarm ADSL Failed Minor CES8 Failed Major CFC200 Failed Major CFC24 Failed Minor CFC6 Failed Minor EPON2 Failed Major FE10 Failed Minor FX10 Failed Minor GE Card Failed Major GE Virtual Card Failed Minor GE24POE Failed Major GE24SFP Failed Major NTE8 Failed Major POTS24 Failed Minor SHDSL24 Online Minor XE Card Failed Major XE4 Failed Major 2.3.
Log and Trap Listing by Reason Code Alarms Overview The following components are affected: • • • • • • • • • • • • • • Component Status Alarm ADSL Failed Minor CES8 Failed Major CFC12 Failed Minor CFC200 Failed Major EPON2 Failed Major FE10 Failed Minor FX10 Failed Minor GE Card Failed Major GE24POE Failed Major GE24SFP Failed Major NTE8 Failed Major POTS24 Failed Minor SHDSL24 Failed Minor XE4 Failed Major 2.3.
Overview Log and Trap Listing by Reason Code • • • • • • • • • • • FE10 Degraded Minor FE2 Degraded Minor FX10 Degraded Minor GE Card Degraded Minor GE Virtual Card Degraded Minor GE24POE Degraded Minor GE24SFP Degraded Minor NTE8 Degraded Minor SHDSL24 Degraded Minor XE Card Degraded Minor XE4 Degraded Minor 2.3.12 QOS Configuration Not Supported Message Card Failure Raised Severity Minor Explanation The user has pre-provisioned a system QoS setting (e.g.
Log and Trap Listing by Reason Code • • • • • Overview GE24SFP Degraded Minor NTE8 Degraded Minor SHDSL24 Degraded Minor XE Card Degraded Minor XE4 Degraded Minor 2.3.13 QOS Resources Exceeded Message Card Failure Raised Severity Minor Explanation The user has pre-provisioned a system QoS setting (e.g. via SET VLANQUEUEMAP) that the reported card cannot support. This may be due to the reported card running an older software revision. System QoS functions may not behave correctly.
Overview Log and Trap Listing by Reason Code • XE4 Degraded Minor 2.3.14 Rate Limiting Failed Message Card Failure Raised Severity Minor Explanation The reported card/interface has rejected the provisioned rate limiting value(s). Egress traffic from the interface(s) on the card may not be correctly limited. Action Perform the following: Alarms 1. Verify that the provisioned RATE and BURST values are supported by that type of interface. 2.
Log and Trap Listing by Reason Code Alarms Overview 1. Disable/enable the card. 2. Reseat the card if necessary. 3. Replace the card if necessary. 4. If the problem is still not resolved, contact Allied Telesis Support.
Overview Log and Trap Listing by Reason Code Alarms 2. For duplex systems, swap activity, then replace the faulty card. 3. If the problem is still not resolved, contact Allied Telesis Support. The following components are affected: • • • • • Component Status Alarm CFC12 Degraded Minor CFC200 Degraded Minor CFC24 Degraded Minor CFC4 Degraded Minor CFC6 Degraded Minor Note: For this alarm, it is possible to swap CFCs. 2.3.
Log and Trap Listing by Reason Code 1. Alarms Overview Verify load file preference settings. Most likely the load file doesn’t match the card type.
Overview Log and Trap Listing by Reason Code • • • • • • • • • • • • • CFC200 Failed Major CFC24 Failed Minor CFC6 Failed Minor EPON2 Failed Major FE10 Failed Minor FE2 Failed Minor FX10 Failed Minor GE Card Failed Major GE Virtual Card Failed Major NTE8 Failed Major POTS24 Failed Minor SHDSL24 Online Minor XE Card Failed Major 2.4 CARD023 - atnCardDefectRaised 2.4.
Log and Trap Listing by Reason Code Overview 2.4.2 File Corruption Message Card Failure Raised Severity Warning Explanation A CRC calculation check has failed on one or more software load files that are resident in the flash memory of the specified control module card. Action Perform the following: 1. Alarms Verify FLASH file integrity using the AUDIT FILES command and remove any corrupted files.
Overview Log and Trap Listing by Reason Code • • • • • • • GE Card Online Major GE24POE Online Major GE24SFP Online Major NTE8 Online Major POTS24 Card Online Minor SHDSL24 Online Minor XE4 Online Major 2.4.4 McastGroupLimit Message Card Info Failure Raised Severity Info Explanation More IGMP Reports have been received on one Service Module than the provisioned slot's group limit (GRPLIMIT). Action Perform the following: Alarms 1. Verify traffic engineering for card. 2.
Log and Trap Listing by Reason Code Overview Explanation The inactive Control Module has reached online status, but the data service protocols have not yet synchronized, therefore the system is not ready to support a swap of activity. Action Perform the following: 1. No action is required. Alarms The following components are affected: • • • Component Status Alarm CFC200 Online Info CFC24 Online Info CFC6 Online Info 2.5 CARD043 - Not Applicable 2.5.
Overview Log and Trap Listing by Reason Code Alarms The following components are affected: Component Status Alarm None • 2.7 CFCP002 - atnRedundancyRestored 2.7.1 Unknown Message Shelf Operating in duplex CFC mode Severity Info Explanation The system, configured for duplex mode, has restored the inactive control module to service as hot standby. Both control modules are in sync and redundant operation is restored. Explanation Action Perform the following: 1.
Log and Trap Listing by Reason Code Overview 2.9 CHAS001 - entConfigChangeTrap 2.9.1 Not Applicable Message Chassis Configuration Change Severity Warning Explanation A card in the chassis has been created or deleted. Action Perform the following: 1. Alarms No action is required. The following components are affected: Component • Status Alarm None 2.10 FAN001 - atnFanFaultRaised 2.10.
Overview Log and Trap Listing by Reason Code Alarms 1. Verify that the environmental temperature requires a fan. 2. If the temperature is high enough to require a fan(s), reseat the module. 3. Replace the module if necessary.
Log and Trap Listing by Reason Code 1. Alarms Overview Input SHOW SYSTEM COOLING to see which components have had a temperature change and the status of the FM4. 2. Check the affected component and replace if necessary. 3. If multiple components are showing a temperature change, check the FM and replace if necessary. The following components are affected: • Component Status Alarm FM4 Degraded Major 2.10.
Overview Log and Trap Listing by Reason Code Component • Status Alarm None 2.12 IGMP001 - mcChannelLimitPerShelfExceeded 2.12.1 Not Applicable Message Maximum Allowed Layer 2 MC Group limit reached Severity Major Explanation The number of concurrent multicast groups on the system has been reached. An IGMP Report is being dropped due to reaching the system's limit. Action Perform the following: 1. Alarms No action is required.
Log and Trap Listing by Reason Code Overview Severity Major Explanation The subscriber device is requesting more MC groups (channels) than allowed. Action Perform the following: 1. This could be an STB fault, so contact the subscriber. Alarms The following components are affected: Component • Status Alarm None 2.15 IGMP004 - mcMACLimitPerPortExceeded 2.15.
Overview Log and Trap Listing by Reason Code 2.17 IGMP006 - mcNewRouterDetected 2.17.1 Not Applicable Message Detected a router on VID on slot port Severity Info Explanation A MC router has been detected. IGMP Reports and Leaves will now be forwarded to this MC router Action Perform the following: 1. No action is required. Alarms The following components are affected: Component • Status Alarm None 2.18 IGMP007 - mcLastRouterAgedOut 2.18.
Log and Trap Listing by Reason Code Action Overview Perform the following: 1. No action is required. Alarms The following components are affected: Component • Status Alarm None 2.20 IGMP009 - (no Trap Message) 2.20.1 Not Applicable Message IGMP Report Discarded due to Reserved Multicast MAC Address Severity Info Explanation The IGMP code validates the requested multicast IP address to insure that it is not within the reserved multicast IP address range (224.0.0.0 - 224.0.0.255).
Overview Log and Trap Listing by Reason Code Component • Status Alarm None 2.22 INTF003 - (no Trap Message) 2.22.1 Classifier Configuration Failed Message Interface Degradation Set Severity Info Explanation The reported interface has rejected the provisioned classifier configuration for an unspecified reason. CLASSIFIER and/or ACCESSLIST functionality may not behave correctly. Action Perform the following: Alarms 1. Verify classifier provisioning. 2. Disable and enable the interface. 3.
Log and Trap Listing by Reason Code Alarms Overview The following components are affected: • • • • Component Status Alarm ATMBOND Degraded Info MLPPP Degraded Minor ONU Degraded Info PPP Degraded Minor 2.22.3 Classifier Resources Exceeded Message Interface Degradation Set Severity Info Explanation The reported interface has exceeded the maximum resources available for classifier configuration. CLASSIFIER and/or ACCESSLIST functionality may not behave correctly.
Overview Log and Trap Listing by Reason Code Action Alarms Perform the following: 1. Disable/enable the failed interface to make the system reattempt the configuration. 2. If failure persists contact Allied Telesis support. The following components are affected: • Component Status Alarm IP Interface Failed Minor 2.24 LOG005 - atnMediaLogStreamError 2.24.
Log and Trap Listing by Reason Code Overview Severity Major Explanation The user has configured log streaming to a compact flash card, but streaming can no longer occur because the card is no longer present. The CFLASH card has been extracted from the unit. Action Perform the following: 1. Alarms To Be Supplied The following components are affected: Component • Status Alarm None 2.25 LOG006 - Not Applicable 2.25.
Overview Log and Trap Listing by Reason Code 1. Check the wiring. Alarms The following components are affected: • • • Component Status Alarm FE Port Failed Info GE Port Failed Major XE Port Failed Major 2.26.2 BFD Session Failed Message Port Fault Set Severity Info Explanation For Bi-Directional Forwarding Detection (BFD), produced when an interface has not received BFD packets within the configured interval timer times the detection multiplier.
Log and Trap Listing by Reason Code • • • • • • • • • • Overview ADSL Port Failed Info SS1 Port Failed Major E1 Port Failed Major EPON Port Failed Major FE Port Failed Major FX Port Failed Major GE Port Failed Major POTS Port Failed Info SHDSL Port Failed Info XE Port Failed Major 2.26.4 Disable Failed Message Port Fault Set Severity Minor Explanation The port failed to respond to a disable request.
Overview Log and Trap Listing by Reason Code 2.26.5 Enable Failed Message Port Fault Set Severity Info Explanation The port failed to respond to an enable request. It could be due to high traffic through the card, or a problem with provisioning associated with the port. Action Perform the following: Alarms 1. Verify traffic capacity. 2. Verify load preferences. 3. Verify provisioning.
Log and Trap Listing by Reason Code • • • • • • Overview ADSL Port Degraded Info DS1 Port Failed Major E1 Port Failed Major GE Card Failed Major SHDSL Port Failed Info XE Port Failed Major 2.26.7 Loss of Link (LOL) Message Port Fault Set Severity Info Explanation Essentially the same as LOS. The only difference between the two is that LOS is preceded by a “last gasp” message where LOL does not. The connections or far-end equipment could be at fault.
Overview Log and Trap Listing by Reason Code Alarms 2. Verify far-end equipment. 3. Disable/enable port. The following components are affected: • • • • • • • Component Status Alarm ADSL Port Failed Info DS1 Port Failed Major E1 Port Failed Major EPON Port Failed Major GE Port Failed Major SHDSL Port Failed Info XE Port Failed Major 2.26.9 Loss of Sync (LOSY) Message Port Fault Set Severity Major Explanation The port has lost the sync source from the far end equipment.
Log and Trap Listing by Reason Code • • • Overview Component Status Alarm FE Port Failed Info GE Port Failed Major XE Port Failed Major 2.26.11 Reset Failed Message Port Fault Set Severity Info Explanation Port failed to respond to reset request. This could be due to high traffic through the card, or a problem with provisioning associated with the port. Action Perform the following: 1.
Overview Log and Trap Listing by Reason Code Severity Info Explanation This failing alarm is raised when a BPDU is received on an interface that has BPDU cop feature enabled. The BPDU cop feature protects the system from network loops and other threats where the symptom is reception of an unexpected BPDU. Action Perform the following: 1. Disable/enable the interface.
Log and Trap Listing by Reason Code Alarms Overview 1. Verify classifier provisioning. 2. Disable and enable the port. 3. Disable and enable the card. 4. If the problem still exists, contact Allied Telesis Support.
Overview Log and Trap Listing by Reason Code • • • • GE Port Degraded Minor IP Interface Degraded Minor SHDSL Port Degraded Minor XE Port Degraded Minor 2.27.3 Classifier Resources Exceeded Message Port Degradation Set Severity Minor Explanation The reported card/port has exceeded the maximum resources available for classifier configuration. CLASSIFIER and/or ACCESSLIST functionality may not behave correctly. Action Perform the following: Alarms 1. Verify classifier provisioning.
Log and Trap Listing by Reason Code Overview sample used (Change vs. Absolute), the current value of the statistic, and the provisioned threshold. The message is an alert to a user to indicate the presence or potential for problems on a specific interface. Since the threshold values are user defined, the message is considered informational. Action Perform the following: 1. Alarms To Be Supplied The following components are affected: Component • Status Alarm None 2.29 RMON002 - fallingAlarm 2.29.
Overview Log and Trap Listing by Reason Code Explanation The level of alarm depends on the number of downstream interfaces affected. (More than 128=Critical, 25 to 128=Major, Less than 24=Minor) Action Perform the following: Alarms 1. Restore the failed uplinks. 2. Restore any failed service modules.
Log and Trap Listing by Reason Code Overview Explanation A routine audit has discovered a discrepancy between the data running in RAM and the data stored in the system database. On a duplex system, if the failure is on the inactive CFC only, then the system automatically restarts the inactive CFC to cause a resync to fix the problem.
Overview Log and Trap Listing by Reason Code • • • • • • • • Component Status Alarm CFC12 Degraded Major CFC200 Degraded Major CFC200 Failed Major CFC24 Degraded Major CFC24 Failed Minor CFC4 Degraded Major CFC6 Degraded Major CFC6 Failed Minor Note: For an active CFC, the status is Degraded, since there is no backup CFC. 2.31.
Log and Trap Listing by Reason Code Overview Severity Major Explanation A failure to write to the flash memory has occurred while trying to write to the database. Action Perform the following: 1. Most likely this indicates a problem with the flash part on the card, the user probably needs to replace the card. Alarms The following components are affected: • • • Component Status Alarm CFC200 Online Major CFC24 Online Major CFC56 Online Major 2.32 SYS009 - atnShelfFaultRaised 2.32.
Overview Log and Trap Listing by Reason Code Component • Status Alarm None 2.34 TRAP004 - warmStart 2.34.1 Not Applicable Message Warm Start Trap Severity Major Explanation Warm start trap for an activity change. No management log generated. Action Perform the following: Alarms The following components are affected: 1. No action is required. Component • Status Alarm None 2.35 TRAP009 - entConfigChangeTrap 2.35.
Listing of Logs and Traps Overview 4. iMAP Logs with Traps 1 Overview This section is organized as follows. 1.1 Listing of Logs and Traps This is a table that lists the log category / trap text that is the entry point for log descriptions. Each entry is a live link to the section that includes all of the reason codes. 1.2 Log and Trap Listing by Reason Code This includes an overview of the log category / trap text and then a description for each Reason Code.
Overview Log and Trap Listing by Reason Code 2 Listing of Logs and Traps The following table lists the logs and trap text that apply to the iMAP product only.
Log and Trap Listing by Reason Code TABLE 4-1 Overview Logs and Traps for iMAP Log and Trap Text Reason Code (or Message) CARD005 - atnCardDefectRaised DSP Core Fault Power 18 Failed Power 25 Adj. Failed Power A Failed Power B Failed Power Fuse Failed SB 2.5v Power Failed SB CPU 2.5v Power Failed SB 2.5v ANALOG Power Failed SB 2.
Overview Log and Trap Listing by Reason Code TABLE 4-1 Logs and Traps for iMAP Log and Trap Text Reason Code (or Message) CARD005 - atnCardDefectRaised - Cont’d Unable to Load DNS Server Timed Out ARP Resolution Failed DNS resolution failed CFlash Failed AC Power A Failed AC Power B Failed AC Power A Fan Failed AC Power B Fan Failed 1.
Log and Trap Listing by Reason Code TABLE 4-1 Overview Logs and Traps for iMAP Log and Trap Text Reason Code (or Message) INTF001 - Linkdown All parents non-administratively down Config Failed Echo Request Timeout Loopback Detected Negotiation Failed Peer Disabled ONU Not Discovered Remote Tranmsit Failed Loading Firmware Waiting to Load Firmware Not Applicable All Links Failed Unexpected BPDU Received Report Timeout Links Not Discovered All ASM Links Down All Parent Interfaces Down Loss of Signal (L
Overview Log and Trap Listing by Reason Code TABLE 4-1 Logs and Traps for iMAP Log and Trap Text Reason Code (or Message) INTF003 - atnInterfaceDefectRaised Keep Alive Timeout Remote Loss of Signal (UNI) Remote Gate Timeout Remote Keep Alive Timeout Mismatched ONU Type Unsupported ONU Type No Response from BRAS Negotiation Failed Echo Request Timeout Below Min Downstream Aggregate Rate Below Min Upstream Aggregate Rate Downstream Differential Rate Exceeded Some ASM Links Down Some Parent Interfaces Do
Log and Trap Listing by Reason Code TABLE 4-1 Overview Logs and Traps for iMAP Log and Trap Text Reason Code (or Message) PORT003 - Linkdown CAS Thermal Shutdown SLIC Thermal Shutdown AC Fault DC Fault PCM Clock Failure Battery Failure No Peer Present (NPP) Loopback Failed Timing Reference Failed Link Quality Failed Loss of RTP Receive Stream Loss of RTP Transmit Stream Receiving AIS Receiving RAI Transmit Failed No Links Discovered Loading Firmware Interface Internal Failure Registration Failed DS3
Overview Log and Trap Listing by Reason Code TABLE 4-1 Logs and Traps for iMAP Log and Trap Text Reason Code (or Message) PORT005 - Not applicable Timing Reference Degraded PORT005 - atnPortDefectCleared Upstream Bandwidth Resources Exceeded PORT013 - Not applicable High priority queue overflow PORT013 - To Be Supplied Port AIS Received PORT017 - Not applicable Not Applicable Not Applicable PSPN003 - atnPSpanDefectRaised ARP Resolution Failed DNS resolution failed DNS Server Timed Out PSPAN
Log and Trap Listing by Reason Code TABLE 4-1 Overview Logs and Traps for iMAP Log and Trap Text Reason Code (or Message) XDSL002 HDSL2SHDSLPERFCRCANOMALIESTHR ESH Not Applicable XDSL003 - HDSL2SHDSLPERFESTHRESH Not Applicable XDSL004 HDSL2SHDSLPERFSESTHRESH Not Applicable XDSL005 HDSL2SHDSLPERFUASTHRESH Not Applicable XDSL006 HDSL2SHDSLPERFLOSWSTHRESH Not Applicable XDSL007 HDSL2SHDSLPERFCRCANOMALIESTHR ESH Not Applicable XDSL008 - HDSL2SHDSLPERFESTHRESH Not Applicable XDSL009 HDSL2SHDS
Overview Log and Trap Listing by Reason Code Explanation The interface is carrying a signal, but the ADSL card is unable to frame against the signal. As a result, all packets are being tossed. Action Perform the following: Alarms 1. Verify that the provisioning characteristics of the ADSL port match those of the device to which it is attached. 2. If there are any differences, correct them. 3.
Log and Trap Listing by Reason Code 1. Alarms Overview Check the far end equipment. The following components are affected: Component Status Alarm None • 2.4 ADSL025 - adslAtucPerfESsThreshTrap 2.4.1 Not Applicable Message Atuc (Near End) Errored Seconds TCA on port Severity Minor Explanation The number of errored seconds has existed exceeds the provisioned threshold for the current 15-minute period. Action Perform the following: 1. Alarms To Be Supplied.
Overview Log and Trap Listing by Reason Code Component Status Alarm None • 2.6 ADSL028 - adslAturPerfLprsThreshTrap 2.6.1 Not Applicable Message Atur (Far End) Loss of Power TCA on port Severity Minor Explanation The ATU-R Loss of Power (LPRS) Threshold Crossing Alert (TCA) trap provides an alert that a given ADSL interface has crossed its user provisioned LPRS threshold during a given 15-minute interval.
Log and Trap Listing by Reason Code Action Perform the following: 1. Alarms Overview To Be Supplied. The following components are affected: Component Status Alarm None • 2.8 ADSL030 - adslAtucPerfSesLThreshTrap 2.8.
Overview Log and Trap Listing by Reason Code minute interval. The alert indicates that a given interface has experienced a cumulative unavailable condition in excess of what is desired in a 15-minute interval. Unavailable seconds occur in response to the failure of an interface. It is possible to see this alert in conjunction with a LOS TCA. Typically, the alert is generated every fifteen minutes until the problem is corrected or until a user changes the threshold value. Action Perform the following: 1.
Log and Trap Listing by Reason Code Overview Severity Info Explanation The IGMP group limit per card has dropped below the high water mark. Action Perform the following: 1. Alarms To Be Supplied. The following components are affected: Component • Status Alarm None 2.12 ADSL034 - adslAtucFailedFastRThreshTrap 2.12.
Overview Log and Trap Listing by Reason Code ADSL48 card is provisioned in 2 slots and physically occupies 2 slots. The ADSL24SA card is provisioned in 1 slot but physically occupies 2 slots. With either card its possible to insert the card where it mismatches the pre-provisioning. For example, Slot 1 preprovisioned with FE10, slot 2-3 pre-provisioned with ADSL48. Plugging in the ADSL48 in slots 1-2 causes slot provisioning mismatch alarm in slot 1. Action Perform the following: 1. To Be Supplied.
Log and Trap Listing by Reason Code • • Overview Component Status Alarm ADSL Card Degraded Minor SHDSL24 Degraded Minor 2.14.2 Power 18 Failed Message Card Failure Raised Severity Critical Explanation A problem has been detected with the 1.8v power output on the CFC switch board, affecting data packet processing. The CFC card is probably defective. Action Perform the following: Alarms 1. For simplex systems, replace the CFC card. 2.
Overview Log and Trap Listing by Reason Code • CFC6 Failed Minor 2.14.4 Power A Failed Message Card Failure Raised Severity Minor Explanation A shelf power failure on power feed A has been detected by the control module card in the specified slot. The problem could be due to the external power feed to the shelf, a defective PEM, or the control module itself may be defective. Action Perform the following: Alarms 1. In a duplex system, if alarm is on only one card, then replace the card. 2.
Log and Trap Listing by Reason Code Alarms Overview 4. Replace CFC card. 5. If the problem is still not resolved, contact Allied Telesis Technical Support. The following components are affected: • • • • • • Component Status Alarm CFC12 Degraded Minor CFC24 Degraded Minor CFC24 Degraded Minor CFC4 Degraded Minor CFC6 Degraded Minor CFC6 Degraded Minor 2.14.
Overview Log and Trap Listing by Reason Code Explanation A problem has been detected with the 2.5v power output on the CFC24 switch board, affecting data packet processing. The CFC24 card is probably defective. Action Perform the following: Alarms 1. Replace the CFC card. 2. If the problem is still not resolved, contact Allied Telesis Technical Support The following components are affected: • • Component Status Alarm CFC24 Degraded Critical CFC24 Failed Minor 2.14.8 SB CPU 2.
Log and Trap Listing by Reason Code • CFC24 Overview Failed Minor 2.14.10 SB 2.5v DIGITAL Power Failed Message Card Failure Raised Severity Critical Explanation A problem has been detected with the 1.25v digital power output on the CFC24 switch board, affecting data packet processing. The CFC24 card is probably defective. Action Perform the following: 1.
Overview Log and Trap Listing by Reason Code Alarms The following components are affected: • Component Status Alarm POTS24 Degraded Major 2.14.13 Lost Communication with Call Server Message Card Failure Raised Severity Major Explanation Indicates that the MGCP entity on the card cannot communicate with the external call agent.
Log and Trap Listing by Reason Code 1. Alarms Overview To Be Supplied The following components are affected: • Component Status Alarm POTS24 Failed Minor 2.14.16 Hardware Unsupported Message Card Failure Raised Severity Info Explanation The hardware version of the card is not supported by the system software. Action Perform the following: 1. Alarms Replace the card with a newer version.
Overview Log and Trap Listing by Reason Code 2.14.18 Internal Oscillator Failure Message Card Failure Raised Severity Minor Explanation Not supported. [STILL TRUE?][To Be Supplied] Action Perform the following: 1. Alarms To Be Supplied The following components are affected: • • Component Status Alarm CES8 Degraded Major NTE8 Degraded Major 2.14.
Log and Trap Listing by Reason Code Action Perform the following: 1. Alarms Overview To Be Supplied The following components are affected: • Component Status Alarm POTS24 Degraded Minor 2.14.21 ARP Resolution Failed Message Card Failure Raised Severity Minor Explanation The IP protocol software on the card was not able to resolve the MAC address of the peer (or the gateway) using the ARP protocol.
Overview Log and Trap Listing by Reason Code Severity Minor Explanation The system failed to access the compact flash media on the card. The media is probably bad or missing. Action Perform the following: 1. Alarms To Be Supplied The following components are affected: Component • Status Alarm None 2.14.24 AC Power A Failed Message Card Failure Raised Severity Minor Explanation A shelf power failure on AC power feed A has been detected by the control module card in the specified slot.
Log and Trap Listing by Reason Code Alarms Overview 2. Otherwise, verify power feed to shelf. 3. Replace AC power module. 4. Replace CFC card. 5. If the problem is still not resolved, contact Allied Telesis Technical Support. The following components are affected: • Component Status Alarm CFC12 Degraded Minor 2.14.26 AC Power A Fan Failed Message Card Failure Raised Severity Minor Explanation The power module controlling the AC power feed A has a fan failure.
Overview Log and Trap Listing by Reason Code Explanation A problem has been detected with the 1.2v power output on the CFC12 switch board, affecting data packet processing. The CFC12 card is probably defective. Action Perform the following: Alarms 1. Replace the CFC card. 2.
Log and Trap Listing by Reason Code 1. Alarms Overview To Be Supplied The following components are affected: • • Component Status Alarm CES8 Degraded Major POTS24 Degraded Major 2.14.31 Power Input Incompatibility Message Card Failure Raised Severity Minor Explanation This degrading alarm indicates that the card is incompatible with the input power source supplied. For example, older iMAP card versions are only compatible with 48v power sources. Action Perform the following: 1.
Overview Log and Trap Listing by Reason Code • • • • POTS24 Degraded Minor SHDSL24 Degraded Minor XE Degraded Minor XE Degraded Minor 2.14.32 Inconsistent Flooding Message Card Failure Raised Severity Info Explanation When IGMP is enabled on an EPON interface, unknown Multicast is blocked. The EPON interface will not flood any unknown multicast on any VLAN, except 256 “well known” groups. This behavior is unlike other IGMP supporting interfaces on the iMAP.
Log and Trap Listing by Reason Code • POTS24 Overview Online Info 2.14.34 Protocol Mismatch Message Card Failure Raised Severity Info Explanation The PROTOCOL attribute on the POTS card (MGCP or SIP) doesn't match the load running on the card (POTS24 or POTS24S). Action Perform the following: Alarms 1. Change the prefload to match. 2. Or change the protocol attribute to match the load type. The following components are affected: • Component Status Alarm POTS24 Failed Minor 2.14.
Overview Log and Trap Listing by Reason Code • • SHDSL24 Failed Minor VDSL24 Failed Minor 2.14.36 Unsupported Hardware Message Card Failure Raised Severity Minor Explanation A card has been installed that is not supported by 15.0 software (e.g., ADSL16, ADSL8s, ADSL16B, SHDSL16). Action Perform the following: 1. Alarms To Be Supplied The following components are affected: • • Component Status Alarm ADSL Failed Minor SHDSL Failed Minor 2.15 CARD023 - atnCardDefectRaised 2.15.
Log and Trap Listing by Reason Code Overview Explanation The Primary Timing Source (from the Network through the FAN8 component) for the CFC6-C card is unavailable. (In a 7700, this network clock source terminates on both the active and inactive CFC-6 cards.) There is therefore only one clock source available for the timing references needed for correct AnnexC service. Action Perform the following: 1.
Overview Log and Trap Listing by Reason Code • Component Status Alarm CFC6 Online Major 2.15.5 Sync Card Clock Error Message Card Info Alarm Raised Severity Major Explanation The mezzanine card on the CFC6-C has failed and can no longer provide timing. As a result, the shelf cannot provide AnnexC service for the ADSL16C card. The inactive CFC-C (if present) may still be able to provide AnnexC service following a switchover. Action Perform the following: 1.
Log and Trap Listing by Reason Code Overview 2.17 CUC001 - atnCUCFaultRaised 2.17.1 Not Present Message Cooling Unit Controller Failure Raised Severity Critical Explanation The cooling unit controller is not present in the shelf. Action Perform the following: 1. Alarms To Be Supplied The following components are affected: • Component Status Alarm FC7 Not installed Major 2.17.
Overview Log and Trap Listing by Reason Code 2.18 FAN001 - atnCUCFaultRaised 2.18.1 Hardware Not Recognized Message Cooling Unit Controller Failure Raised Severity Critical Explanation The system does not recognize the hardware type that is physically present in the cooling unit controller slot. Action Perform the following: Alarms 1. Reseat the card. 2. If the alarm persists, replace the card. The following components are affected: • Component Status Alarm FC7 Failed Major 2.
Log and Trap Listing by Reason Code Overview Explanation All of the parent PPPs that are associated with the MLPPP are not available, and so all traffic on the MLPPP (a combining of two to eight DS1s/E1s) cannot be passed. Action Perform the following: 1. Alarms Check the status of the NTE8 card, DS1 interfaces, and the PPPs. The following components are affected: • Component Status Alarm MLPPP Failed Major 2.20.
Overview Log and Trap Listing by Reason Code Explanation The PPP/MLPPP protocol periodically checks its integrity by using echo requests, where it sends a message to the peer and expects the peer to reply. Consistent failure to receive the echo reply within a given time period will cause the interface to fail with this alarm. The echo request timeout value is configurable and can be changed using the SET INTERFACE command if desired. Action Perform the following: 1. Alarms To Be Supplied.
Log and Trap Listing by Reason Code • • Overview Component Status Alarm MLPPP Failed Major PPP Failed Major 2.20.6 Peer Disabled Message Interface Fault Set Severity Major Explanation The remote peer has gracefully taken the link down, but the local interface is still enabled. A common cause would be that the remote interface has been administratively disabled. Action Perform the following: 1. Alarms To Be Supplied.
Overview Log and Trap Listing by Reason Code Explanation This failing alarm is the result of the ONU failing to transmit on the EPON, and is triggered by hardware inputs from transceiver. The transmitted output does not input as reported by the EPON optics. This alarm may indicate a problem with the ONU or its connection to the fiber. Action Perform the following: 1. Alarms To Be Supplied. The following components are affected: • Component Status Alarm ONU Failed Info 2.20.
Log and Trap Listing by Reason Code Alarms Overview The following components are affected: • Component Status Alarm ONU Failed Info 2.20.11 Not Applicable Message New root trap Severity Info Explanation To Be Supplied. Action Perform the following: 1. Alarms To Be Supplied. The following components are affected: Component • Status Alarm None 2.20.
Overview Log and Trap Listing by Reason Code the iMAP from network loops and other threats where the symptom is reception of an unexpected BPDU. Action Perform the following: 1. Alarms To clear alarm, disable and re-enable the interface. The following components are affected: • • • • Component Status Alarm ATMBOND AutoDisabled Info MLPPP AutoDisabled Major ONU AutoDisabled Info PPP AutoDisabled Major 2.20.
Log and Trap Listing by Reason Code • Overview Component Status Alarm ONU Failed Info 2.20.16 All ASM Links Down Message Interface Fault Set Severity Info Explanation The ATMBOND is failed because all of the internal links for communicating Asynchronous Status Messages (ASM) are not functioning. Resolving this problem may involve any one or combination of the action listed below. Action Perform the following: Alarms 1. Reset the G.bond modem at the CPE. 2. Disable/Enable the ATMBOND.
Overview Log and Trap Listing by Reason Code 1. Alarms To Be Supplied. The following components are affected: • Component Status Alarm DS3 Failed Major 2.20.19 Alarm Indication Signal Message Interface Fault Set Severity Info Explanation An Alarm Indication Signal has been received by the DS3. This is sent from the remote peer to indicate that a transmission interruption has been detected in the network. One common reason for AIS is when the remote peer has been administratively disabled.
Log and Trap Listing by Reason Code Action Perform the following: 1. Alarms Overview To Be Supplied. The following components are affected: • Component Status Alarm DS3 Failed Major 2.20.22 Receive Loss of Lock Message Interface Fault Set Severity Info Explanation The DS3 has detected a Loss of Lock condition on its incoming signal, possibly due to problems with the incoming reference clock signal. Action Perform the following: 1. Alarms To Be Supplied.
Overview Log and Trap Listing by Reason Code Severity Minor Explanation One or more of the parent PPPs of the affected MLPPP is not passing traffic, but the MLPPP is still providing limited service because there is bandwidth available through the other PPPs. The DS1/E1 or corresponding PPP interface(s) may have failed, or may have been administratively disabled. Action Perform the following: 1. Alarms To Be Supplied.
Log and Trap Listing by Reason Code Overview 2.22.2 Remote Loss of Signal (UNI) Message Not Applicable Severity Info Explanation This degrading alarm against the ONU indicates a loss of signal condition on the UNI side of the ONU. Action Perform the following: Alarms 1. Make sure a device is connected to the UNI interface on the ONU. 2. If a device is connected to the UNI interface, make sure it is powered up. 3.
Overview Log and Trap Listing by Reason Code alarm from occurring due to mis-configuration. Therefore, presence of this alarm should be rare. Action Alarms Perform the following: 1. Disable/enable the ONU. 2. Disable/enable the EPON interface. 3. Disable/enable the EPON card. 4. Power reset the ONU. 5. Replace the ONU. 6. Replace the EPON card. The following components are affected: • Component Status Alarm ONU Degraded Info 2.22.
Log and Trap Listing by Reason Code Overview 2.22.7 No Response from BRAS Message Not Applicable Severity Info Explanation The PPPoE session cannot be established. A timeout has occurred while waiting for the PADO form the BRAS server. The associated alarm shows which VC is affected by the alarm. If the PADO is never received, the protocol handshake must begin again. Action Perform the following: 1. Alarms To Be Supplied.
Overview Log and Trap Listing by Reason Code VC is affected by the alarm. In this case, the session must begin again (transition to PADI state. Action Perform the following: 1. Alarms To Be Supplied. The following components are affected: • • • Component Status Alarm ADSL Port Degraded Info SHDSL Port Degraded Info VDSL Port Degraded Info 2.22.
Log and Trap Listing by Reason Code Overview 2.22.12 Downstream Differential Rate Exceeded Message Interface Degradation Set Severity Info Explanation One of the ADSL interfaces in the ATMBOND group has achieved a downstream rate that is less than 25% of the downstream rate achieved by the companion interface in the group. Action Perform the following: 1. Alarms To Be Supplied. The following components are affected: • Component Status Alarm ATMBOND Degraded Info 2.22.
Overview Log and Trap Listing by Reason Code Alarms The following components are affected: • Component Status Alarm ATMBOND Degraded Critical 2.22.15 Status Attribute Message To Be Supplied Severity Info Explanation To Be Supplied. Action Perform the following: 1. Alarms To Be Supplied. The following components are affected: • Component Status Alarm ATMBOND Degraded Info 2.22.
Log and Trap Listing by Reason Code • Overview Component Status Alarm DS3 Degraded Info 2.22.18 Bipolar Violation Message Interface Degradation Set Severity Info Explanation Bipolar violations have been detected on the incoming signal of the DS3. Action Perform the following: 1. Alarms To Be Supplied. The following components are affected: • Component Status Alarm DS3 Degraded Info 2.22.
Overview Log and Trap Listing by Reason Code • Component Status Alarm DS3 Degraded Info 2.23 INTF003 - Linkdown 2.23.1 Loss of Frame (LOF) Message Port Fault Set Severity Minor Explanation The port has lost the framing source from the far end equipment. Action Perform the following: Alarms 1. Verify framing source. 2. Verify far-end equipment. 3. Disable/enable port. The following components are affected: • Component Status Alarm DS3 Degraded Info 2.
Log and Trap Listing by Reason Code Overview Severity Minor Explanation The number of link errored seconds condition exceeds the provisioned threshold for the current 15-minute period. Action Perform the following: 1. Alarms To Be Supplied. The following components are affected: Component • Status Alarm None 2.26 PMON003 - atnDs1CurrentLOSThreshTrap 2.26.
Overview Log and Trap Listing by Reason Code 2.28 PMON005 - atnDs1DayUASThreshTrap 2.28.1 Not Applicable Message Not Applicable Severity Minor Explanation The number of Unavailable Seconds condition exceeds the provisioned threshold for the current 15-minute period. Action Perform the following: 1. Alarms To Be Supplied. The following components are affected: Component • Status Alarm None 2.29 PORT003 - Linkdown 2.29.
Log and Trap Listing by Reason Code Alarms Overview The following components are affected: • Component Status Alarm POTS Port Failed Minor 2.29.3 AC Fault Message Port Fault Set Severity Minor Explanation Indicates that external AC voltage has been detected on the line. Most likely the fault is due to an external stimulus (fault on the external line itself). Action Perform the following: 1.
Overview Log and Trap Listing by Reason Code 1. Alarms Replace card. The following components are affected: • Component Status Alarm POTS Port Failed Minor 2.29.6 Battery Failure Message Port Fault Set Severity Minor Explanation The battery that applies line voltages is defective. Action Perform the following: 1. Alarms Replace card. The following components are affected: • Component Status Alarm POTS Port Failed Minor 2.29.
Log and Trap Listing by Reason Code 1. Alarms Overview Set the loopback configuration back to "NONE" and try again. The following components are affected: • • Component Status Alarm DS1 Port Failed Major E1 Port Failed Major 2.29.9 Timing Reference Failed Message Port Fault Set Severity Minor Explanation Not supported in R5.0. [Still True?] [To Be Supplied] Action Perform the following: 1.
Overview Log and Trap Listing by Reason Code 2.29.11 Loss of RTP Receive Stream Message Port Fault Set Severity Minor Explanation The POTS card has detected that it is not receiving RTP packets as expected for the interface. The RTP packets have been interrupted or are not being sent from the call agent. Action Perform the following: Alarms 1. Check for an external network condition (failure or capacity). 2.
Log and Trap Listing by Reason Code 1. Alarms Overview To Be Supplied The following components are affected: • • Component Status Alarm DS1 Port Failed Major E1 Port Failed Major 2.29.14 Receiving RAI Message Port Fault Set Severity Major Explanation The physical interface is failed because it received a Remote Alarm Indication from its remote peer. RAI is sent from remote peer when it detects that it has lost the incoming signal. Action Perform the following: 1.
Overview Log and Trap Listing by Reason Code 2.29.16 No Links Discovered Message Port Fault Set Severity Major Explanation This alarm indicates that no logical links have been discovered for any ONU on the EPON interface. Action Perform the following: Alarms 1. Verify that fiber is connected to the EPON interface. 2. Verify that ONUs are connected to the fiber. 3. If ONUs are connected to the fiber, make sure they are powered up. 4. Check to see if the fiber is defective.
Log and Trap Listing by Reason Code 1. Alarms Overview Reset the OLT (enable/disable). The following components are affected: • Component Status Alarm EPON Port Failed Major 2.29.19 Registration Failed Message Port Fault Set Severity Info Explanation The registration failure alarm is set when a POTS PORT loses its registration status with the call agent, signaling that a port is out of service. The fault is cleared when the registration is restored. Action Perform the following: 1.
Overview Log and Trap Listing by Reason Code Explanation The port is having difficulty syncing with the far end equipment. Action Perform the following: Alarms 1. Verify far-end equipment. 2. Disable/enable port. The following components are affected: • Component Status Alarm SHDSL Port Degraded Info 2.31 PORT005 - atnPortDefectRaised 2.31.
Log and Trap Listing by Reason Code • • Overview SHDSL Port Degraded Info VDSL Port Degraded Info 2.31.3 Transmit Degraded Message Port State Change Severity Major Explanation This degrading alarm is the result of the OLT having errors transmitting on the EPON, and is triggered by hardware inputs from transceiver. The transmitted output has a high error level, but not so high as to cause failure. This alarm may indicate a problem with the EPON card or the SFP connecting with the fiber.
Overview Log and Trap Listing by Reason Code tivity. There are 3 categories: 1. delay sensitive 2. delay tolerant but non-zero minimum bandwidth 3. delay tolerant with zero minimum bandwidth (aka "best effort") Each category has limits on how many logical links can be included. Action Perform the following: 1. Alarms To Be Supplied The following components are affected: • Component Status Alarm EPON Port Degraded Major 2.31.
Log and Trap Listing by Reason Code Alarms Overview The following components are affected: • • Component Status Alarm ADSL Port Failed Info SHDSL Port Failed Info 2.33 PORT005 - Not applicable 2.33.1 Timing Reference Degraded Message Port Degradation Set Severity Minor Explanation The port's provisioned timing reference cannot provide a reliable timing reference. The interface is being timed from an alternate reference that is not known to be locked to the provisioned source.
Overview Log and Trap Listing by Reason Code 2.35 PORT013 - Not applicable 2.35.1 High priority queue overflow Message Port Information Severity Info Explanation Traffic mapped to high priority queue(s) by the provisioned QoS configuration is causing queue overflows, which results in dropped packets. To remedy this, map less traffic to high priority queues. Action Perform the following: 1. Alarms Verify the QOS/traffic configuration for the port.
Log and Trap Listing by Reason Code Overview Severity Info Explanation When configuring Service Module cards, users should be aware that certain attributes are not compatible with certain cards. When trying the change these attributes through commands at the CLI, the command is rejected. During upgrade or when an AutoProv profile is set so incompatible attributes will be applied, the system will change the attribute to ensure compatibility, and a log is produced.
Overview Log and Trap Listing by Reason Code Action Perform the following: 1. Alarms To Be Supplied The following components are affected: • Component Status Alarm PSPAN Failed Minor 2.38.2 DNS resolution failed Message Not Applicable Severity Minor Explanation The IP protocol software on the card was not able to resolve the domain name of the peer (or the gateway) using the DNS protocol.
Log and Trap Listing by Reason Code Overview Explanation The system failed to configure the hardware with provisioned PSPAN data. This will impact service provided by the PSPAN. Action Perform the following: 1. Alarms To Be Supplied The following components are affected: • Component Status Alarm PSPAN Failed Minor 2.38.5 PSPAN does not have a connection Message To Be Supplied Severity Minor Explanation The PSPAN is not connected to a DS1/E1 port.
Overview Log and Trap Listing by Reason Code Severity Minor Explanation This indicates that the PSPAN has not been able to send any packets into the network. This is a service impacting condition, and is most likely due to internal hardware failures. Action Perform the following: 1. Alarms To Be Supplied The following components are affected: • Component Status Alarm PSPAN Failed Minor 2.38.
Log and Trap Listing by Reason Code Alarms Overview The following components are affected: • Component Status Alarm PSPAN Failed Major 2.38.10 PSPAN Timing Reference Degraded Message To Be Supplied Severity Minor Explanation The PSPAN's provisioned timing reference cannot provide a reliable timing reference. The interface is being timed from an alternate reference that is not known to be locked to the provisioned source. Action Perform the following: 1.
Overview Log and Trap Listing by Reason Code Alarms 1. Search for a FAN log (e.g., ** FAN001 2003-11-14 17:06:37 8172 FAULT Description: Fan Module Failure Raised Reason Code: Fan Module Not Present). 2. Replace the CFC card. 3. Refer to Section 5. [STILL TRUE?][To Be Supplied] The following components are affected: • Component Status Alarm Shelf N/A Major 2.39.
Log and Trap Listing by Reason Code Overview Severity Major Explanation The Dry Contact fault has been raised for an open contact condition. The reason code and severity will depend on the user provisioning for the specific dry contact condition. Action Perform the following: 1. Alarms No action is required. The following components are affected: Component • Status Alarm None 2.41 SHLF009 - atnDryContactCleared 2.41.
Overview Log and Trap Listing by Reason Code 2.42 SYS004 - atnMediaLogStreamError 2.42.1 CFlash Failed Message Compact Flash Failed Severity Major Explanation To Be Supplied. Action Perform the following: 1. Alarms No action is required. The following components are affected: • • Component Status Alarm CFC24 Degraded Minor CFC24 Degraded Minor 2.43 SYS009 - atnShelfFaultRaised 2.43.
Log and Trap Listing by Reason Code Action Alarms Overview Perform the following: 1. Check to ensure the threshold has been set to the appropriate level. 2. If the threshold is appropriate, check the line facilities. The following components are affected: Component • Status Alarm None 2.45 XDSL002 - HDSL2SHDSLPERFCRCANOMALIESTHRESH 2.45.
Overview Log and Trap Listing by Reason Code Component • Status Alarm None 2.47 XDSL004 - HDSL2SHDSLPERFSESTHRESH 2.47.1 Not Applicable Message STU-C Severely Errored Seconds (SES) TCA Severity Info Explanation The threshold set for the statistic has been exceeded over the current 15 minute interval. Action Perform the following: Alarms 1. Check to ensure the threshold has been set to the appropriate level. 2. If the threshold is appropriate, check the line facilities.
Log and Trap Listing by Reason Code Overview 2.49 XDSL006 - HDSL2SHDSLPERFLOSWSTHRESH 2.49.1 Not Applicable Message STU-R Loss of Sync Word Seconds (LOSWS) TCA Severity Info Explanation The threshold set for the statistic has been exceeded over the current 15 minute interval. Action Perform the following: Alarms 1. Check to ensure the threshold has been set to the appropriate level. 2. If the threshold is appropriate, check the line facilities.
Overview Log and Trap Listing by Reason Code 2. Alarms If the threshold is appropriate, check the line facilities. The following components are affected: Component • Status Alarm None 2.51 XDSL008 - HDSL2SHDSLPERFESTHRESH 2.51.1 Not Applicable Message STU-R Errored Seconds (ES) TCA Severity Info Explanation The threshold set for the statistic has been exceeded over the current 15 minute interval. Action Perform the following: Alarms 1.
Log and Trap Listing by Reason Code Overview 2.53 XDSL010 - HDSL2SHDSLPERFUASTHRESH 2.53.1 Not Applicable Message STU-R Unavailable Seconds (UAS) TCA Severity Info Explanation The threshold set for the statistic has been exceeded over the current 15 minute interval. Action Perform the following: Alarms 1. Check to ensure the threshold has been set to the appropriate level. 2. If the threshold is appropriate, check the line facilities.
Overview Log and Trap Listing by Reason Code Severity Info Explanation The physical layer connection failed, so the xDSL port is disabled and enabled to retrain the link. Action Perform the following: 1. Alarms No action is required. The following components are affected: • • • Component Status Alarm ADSL Port Online None SHDSL Port Online None VDSL Port Online None 2.56 XDSL020 - xdslPortMinDownRateRetrain 2.56.
Log and Trap Listing by Reason Code 1. Alarms Overview No action is required.
Overview 4-84 Log and Trap Listing by Reason Code Log Reference for SBx3100 and iMAP Series Switches (iMAP Logs with Traps)
Device Backup Failed Overview 5. NMS Logs 1 Overview The AlliedView NMS allows network administrators to query and control both Allied Telesis and non-Allied Telesis devices in their network. Moreover, there are two types of NSM products available; • Service Provider - This includes all NMS features • Enterprise Edition - The Enterprise Edition is introduced primarily for the smaller enterprise customer managing a network of less than 100 devices.
Discovery SNMP Error Code 3 Discovery 3.1 SNMP Error Code Message (SNMP error code): Error fetching device information Some of the properties may be incorrect. Severity Major Explanation Verify SNMP to device and Rediscover Device. 3.2 Unable to Detect MO Message Unable to update MO (status = false) Severity Major Explanation If problem persists call Allied Telesis NMS support. 3.3 Max. Allowed Node Limit Reached Message Max. Allowed Node Limit of 4 Reached.
Cannot locate directory NMS backup 4 NMS backup 4.1 Cannot locate directory Message NMS Backup Failure -- Can't locate conf/AT_NmsBackupFiles.conf (no files backed up) Severity Major Explanation If problem persists call Allied Telesis NMS support. 4.2 Cannot create directory Message NMS Backup Failure -- Unable to create directory path needed for BACKUP_DESTINATION: -path- Severity Warning Explanation Verify that NMS process has write permissions for the directory. 4.
Status Poll Cannot complete backup Severity Major Explanation If problem persists call Allied Telesis NMS support. 4.7 Cannot complete backup Message NMS Backup Failure -- Database backup could not be completed (Check DB table sizes and see log for details) Severity Warning Explanation Check the database table sizes and see logs for details 4.
Upload Config Failed Other Severity Major Explanation Check the Failure Object in the Alarm view to see which device is affected. Then go to the Physical View and perform a View Chassis as well as a right click to select Alarms and Events. Go to the System Log Events view and sort by Source. Look at the associated logs and refer again to this Log Manual. 6 Other 6.1 Upload Config Failed Message Upload Config Failed! -error detail- Severity Major Explanation See error detail for steps to take.
Other 5-6 Upload Config Failed Log Reference for SBx3100 and iMAP Series Switches (NMS Logs)
