Table Of Contents

PM622 Messages

PNNI Messages

POS Messages

POSDW Messages

POT1E1 Messages

POWERMGR Messages

PRP Messages

PRP2 Messages

PM622 Messages

The following are 8xOC3 Enhanced ATM LC driver messages.

Error Message    

%PM622-1-BAD_CARDTYPE : [chars] [int]

Explanation    An internal software error has occurred. PM622 initialization routines were invoked for a line card that is not a PM622 line card.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem. Copy the resulting logged error and debug messages exactly as they appear and report the problem to your Cisco technical support representative.

Error Message     

%PM622-1-CHUNK : [chars]

Explanation    A chunk could not be created for the SAR event and acknowledgment queues. This condition renders the line card as unusable. The queues are required for all communication with the component that processes SAR operations. This condition is caused by a memory allocation problem.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     

%PM622-3-CONN_ID : [chars] - [chars]: vcid = [dec]!\n

Explanation    A mapping operation to the CONN_ID component has failed. This condition may be due to an invalid VC ID being obtained from the RP.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-CPK24_GET_ERROR : Cannot read [chars] bit

Explanation    A CPK24 FPGA read error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error, to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-CPK24_INTR : [chars]. Port [dec]: number of occurance = [int] intr_status = [hex]\n

Explanation    A CPK24 FPGA interrupt operation has occurred.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-CPK_CONN_ADD : ([int]/[int]) VC:[int] [chars]

Explanation    A connection into the CPK24 FPGA could not be added. This failure may be caused by a problem with the resource used for the cell packing connection, policing being over the configured limit of 508, or a problem with the CPK24 FPGA.

Recommended Action    Ensure that the total number of connections that are used for cell packing (both VP and VC), plus the number of connections that are used with the input service policy, are not more than 508.

Error Message     

%PM622-3-CPK_CONN_MOD : ([int]/[int]) VC:[int] [chars]

Explanation    A connection into the CPK24 FPGA could not be modified. This failure may be caused by a problem with the resource used for the cell packing connection, policing being over the configured limit of 508, or a problem with the CPK24 FPGA.

Recommended Action    Ensure that the total number of connections that are used for cell packing (both VP and VC), plus the number of connections that are used with the input service policy, are not more than 508.

Error Message    

%PM622-3-CPK24_SET_ERROR : Cannot set [chars] bit

Explanation    A CPK24 FPGA set error occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error, to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-CPK24_SN_CDTYPE_ERROR : Sequence Number processing not supported in FPGA for card type [dec]

Explanation    CPK24 FPGA Sequence Number processing is not supported.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card that reported the error, to gather data that may help identify the nature of the error. Copy the resulting logged error and debug messages exactly as they appear. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-CPK24_SN_DONE_ERROR : Sequence Number done BIT NOT SET ABORTING for slot [dec] and slotunit [dec] \n

Explanation    The CPK24 FPGA sequence number done bit is not set.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error, to gather data that may help identify the nature of the error. Copy the resulting logged error and debug messages exactly as they appear. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-ERROR : [chars]

Explanation    PM622 SAR internal error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-4-FRMROP : ([dec]/[dec]) [chars] (value=[hex])

Explanation    Line card ATM driver framer operation errors have occurred.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-1-HWDB_ALLOC : [chars]

Explanation    The line card failed to allocate memory for essential hardware interface data structures. This condition renders the card non-operational.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-4-IFIFO_DROP : [chars]: [chars] [int] [chars] [int]

Explanation    An invalid event was received from the SAR. The length of the event was invalid, so all SAR events in the queue were dropped.

Recommended Action    Enter the show control atm 0 anaramsave command on the line card. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     

%PM622-4-IFIFO_RESOURCE : [chars]

Explanation    An I_FIFO resource error has occurred. An internal queue between the SAR and the line card CPU lost a message due to a chunk memory allocation failure.

Recommended Action    Enter the show control atm 0 anaramsave command on the line card. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-IF_SHUTDOWN : Interface shutdown error: ([int]/[int]) [chars]

Explanation    The component that processes SAR operations has returned an error while data structures were being closed. As a result, the shutdown command on the interface has failed.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-ILLEGAL_TX_PRIORITY : ([dec]/[dec]) VC [dec] failed to set tx priority [dec]

Explanation    A channel was opened with a default priority because illegal parameters were being passed to the component that processes SAR operations.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-IOB_INTR : [chars]

Explanation    An error interrupt has occurred on the IOB FPGA.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-4-IPC_OP : [chars] [int]

Explanation    Line card ATM driver general operation errors have occurred.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-2-LC_FATAL_ERR : ([int]/[int]): SAR Fatal event occured during configuration

Explanation    A fatal event has occurred on one of SARs during system configuration.This condition may result in an inconsistent configuration. The line card has been reset.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-LOST_IF : [chars] command failed, [chars]

Explanation    The RP command specified an interface that cannot be found.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-4-LOST_WRED_PACK : ([int]/[int]) VCID [dec]: [chars] failed, [chars]

Explanation    An internal error occurred the line card driver while a VC was being torn down. A WRED pack could not be removed from the database, because the WRED pack could not be found. This condition is not a problem in itself, but it is likely to be a symptom of another problem.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-MAC_LEN : ([int]/[int]) VC:[int] [chars] failed, [chars]([int])

Explanation    A VC was setting up its MAC string on the TBM, but the size of the MAC string was either too large or too small. If the length is zero, this condition might indicate that an adjacency removal operation was processed incorrectly.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-MAC_TYPE : ([int]/[int]) VC:[int] [chars] failed, [chars]([int])

Explanation    A VC was setting up its MAC string on the TBM, but the size of the output_info field of the MAC string was either too large or too small. This condition indicated an internal software error.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-MAX_VP_TUNNEL : ([int]/[int]) VPI:[int] [chars] failed, [chars]

Explanation    The maximum number of VP tunnels has already been configured.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-4-MAX_WRED_PACK : ([int]/[int]) VC:[int] Warning: [chars].

Explanation    SAR WRED packs have been exhausted on this interface. There are a limited number of WRED packs available per interface. This condition means that the "random-detect" feature has been configured on a service policy attached to this VC, at least one set of WRED values is unique, and the total number of WRED packs required to satisfy this VC along with the all other open VCs is greater than the number of WRED packs available to an interface. Since there were not enough WRED packs available to satisfy your request, the VC will be opened using per-VC early packet discard instead of WRED. This condition does not indicate any problems with the system.

Recommended Action    Configure this VC to use existing "random-detect" values by using the same service policy that is in use by a VC that has been successfully opened.

Error Message     

%PM622-4-MAX_WRED_PACK : ([int]/[int]) VC:[int] Warning: [chars].

Explanation    No more SAR WRED packs are available on the specified interface. There are a limited number of WRED packs available per interface. "Random-detect" is configured on a service policy attached to this VC, at least one set of WRED values is unique, and the total number of WRED packs needed to satisfy this VC along with the all other open VCs is greater than the number of WRED packs available to an interface. Since there were not enough WRED packs available to satisfy your request, the VC will be opened using the per-VC early packet discard method, rather than WRED. This condition is not an error.

Recommended Action    Configure this VC to use existing "random-detect" values by using the same service policy in use by a VC that has been successfully opened.

Error Message    

%PM622-3-MDRR_L2TRANSPORT : ([int]/[int]) VC:[int] [chars]

Explanation    A Modified Deficit Round Robin VC cannot be opened for Layer 2 transport. If a policy map has bandwidth or priority commands that have been configured, it cannot be attached to a PVC that has Layer 2 transport configured.

Recommended Action    Remove either the Layer 2 transport configuration or the bandwidth or priority configuration.

Error Message    

%PM622-3-MICKEY_INTR : [chars]. Interrupt pending register:[hex] Interrupt mask register: [hex]

Explanation    An error interrupt has occurred on the Mickey FPGA.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-MODIFY : ([int]/[int]) VC:[int] hasn't been setup

Explanation    PM622 ATM Internal error. The engine tried to modify an L2FWD connection that was not active.

Recommended Action    As a workaround, tear down the affected connection and set it up again. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-MOUSE_INTR : [chars]. Interrupt pending register:[hex] Interrupt mask register: [hex]

Explanation    An error interrupt has occurred on the Mouse FPGA.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-PCI_BRIDGE_INTR : [chars]. Interrupt pending register:[hex] Interrupt mask register: [hex]

Explanation    An error interrupt has occurred on the PCI Bridge device.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-2-PCI_INIT : [chars]

Explanation    The line card was unable to initialize one of the PCI FPGAs. These devices are critical to the operation of the line card. This condition probably indicates a hardware error.

Recommended Action    Enter the show control atm 0 anaramsave command on the line card. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-PCI_IO_ERR : [chars] [dec] [chars] [hex]

Explanation    An error occurred while writing to or reading from PCI address space.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-PCI_MEM : [chars] [dec]

Explanation    An error occurred while the line card attempted to set the PCI memory window.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-PLIM : PLIM Error on 8xOC3 ATM line card

Explanation    An error occurred in the PLIM. The error is either a framer, SAR, or SOP error.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-POLICE_CONFIG : [chars] - [chars] \n

Explanation    A policing configuration failure has occurred while a CPK was being programmed.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-POLICE_FAIL : [chars] [dec]

Explanation    Policing parameters could not be installed on the VC or VP because of a hardware failure.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-4-POLL_INCOMPLETE_CMD_ACK : SAR:[dec] [chars]

Explanation    An invalid acknowledgment message has been dropped.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-RESOURCE_ALLOC_ERROR : Failed to allocate [chars].

Explanation    A required resource could not be allocated.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-4-RP_CMD : [chars] command error: [chars]

Explanation    Line card ATM driver handle RP command errors have occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-SAF24_INTR : [chars]. Base addr:[hex]. level1: ISR:[hex] mask:[hex] level2: ISR:[hex] mask:[hex]

Explanation    An error interrupt has occurred on the SAF24 FPGA.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-4-SAR_BAD_EVENT : SLOT:[int] SAR:[dec] [chars] Event: [hex] [hex] [hex] [hex]

Explanation    An invalid event was received from the SAR.

Recommended Action    Enter the show control atm 0 anaramsave command on the line card. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-2-SAR_BAD_SIGNATURE : SAR:[dec] [chars] [chars] [dec] Event: [hex] [hex] [hex] [hex]

Explanation    While the line card is initialized, firmware is downloaded to the component that processes SAR operations. After the firmware download is complete, the Cisco IOS software requests that the component return a signature stating that the firmware download was successful. The component returned a signature indicating an invalid status. This condition indicates a likely hardware failure.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-SAR_CLOSE_COSQ_ERR : SAR:([int]/[int]) [chars] [chars] [int] Event: [hex] [hex] [hex] [hex]

Explanation    The component that processes SAR operations encountered an error while a CoSQ channel was attempted to be closed.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-SAR_CLOSE_VC_ERR : SAR:([int]/[int]) [chars] [chars] [int] Event: [hex] [hex] [hex] [hex]

Explanation    The component that processes SAR operations encountered an error while a VC was attempted to be closed.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-SAR_CLOSE_VP_TUNNEL_ERR : SAR:([int]/[int]) [chars] [chars] [dec] Event: [hex] [hex] [hex] [hex]

Explanation    The component that processes SAR operations encountered an error while a VP tunnel was attempted to be closed.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-2-SAR_CONFIG_ERR : SAR:[dec] [chars] [chars] [dec] Event: [hex] [hex] [hex] [hex]

Explanation    An configuration attempt involving the component that processes SAR operations has failed.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-2-SAR_CONTINUOUS_ERR : ([int]/[int]): Rate of errors detected on the [chars] SAR is above the normal threshold

Explanation    The rate of errors on one of the SAR devices is above the normal range. This condition indicates a hardware problem.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-4-SAR_COUNTER_IND_ERR : SLOT:[int] SAR:[dec] [chars] Event: [hex] [hex] [hex] [hex]

Explanation    The component that processes SAR operations has returned a message indicating that a counter has wrapped in an invalid manner. The message has been ignored.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-2-SAR_FATAL_ERR : SLOT:[int] SAR:[dec] [chars] [chars] [int] Event: [hex] [hex] [hex] [hex]

Explanation    A fatal event has occurred on one of the SARs.

Recommended Action    If this error occurs frequently, enter the exec slot slot-number show cont atm port-number sardump command, with slot-number being the slot number of the affected card and port-number being the affected port number. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-SAR_FREE_CHANNEL_ERR : SAR:([int]/[int]) [chars] [chars] [dec] Event: [hex] [hex] [hex] [hex]

Explanation    The component that processes SAR operations encountered an error while a channel was being freed.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-4-SAR_GET_CHANNEL_STATS_ERR : SAR:([int]/[int]) [chars] [chars] [int] Event: [hex] [hex] [hex] [hex]

Explanation    The component that processes SAR operations encountered an error while channel statistics were being obtained.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-4-SAR_GET_PORT_STATS_ERR : SAR:([int]/[int]) [chars] Event: [hex] [hex] [hex] [hex]

Explanation    The component that processes SAR operations encountered an error while port statistics were being obtained.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-SAR_MODIFY_VP_TUNNEL_ERR : SAR:([int]/[int]) [chars] [chars] [dec] Event: [hex] [hex] [hex] [hex]

Explanation    The component that processes SAR operations encountered an error while a VP tunnel was being modified.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-SAR_MODIFY_WRED_PACK_ERR : SAR:([int]/[int]) [chars] Event: [hex] [hex] [hex] [hex]

Explanation    The component that processes SAR operations encountered an error while a WRED pack was being modified. A new WRED pack could not be allocated for a VC that is about to be opened. The only known reason this could happen is if invalid parameters were passed to the SAR operation (if the status was equal to 3).

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-SAR_MULTIBIT_ECC_ERR : ([int]/[int]): Multi-bit ECC Uncorrectable error in [chars] SAR SDRAM address: [hex]. Syndrome [hex]. Resseting the port

Explanation    An error was detected in the SAR memory. Memory errors may result from natural phenomena such as cosmic rays, and occasional errors are normal

Recommended Action    In most cases, no action is required. In rare cases, this message may indicate faulty hardware. If this message recurs within one week, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-4-SAR_NON_FATAL_ERR : SLOT:[int] SAR:[dec] [chars] [chars] [int] Event: [hex] [hex] [hex] [hex]

Explanation    The component that processes SAR operations encountered a recoverable ECC error.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-1-SAR_NO_SIGNATURE : SAR:[dec] timed out waiting for signature after firmware download.

Explanation    While the line card is being initialized (booted), firmware is downloaded to the component that processes SAR operations. After the firmware download is complete, Cisco IOS requests the component to return a signature stating that the firmware download was successful. In this case, the component did not return a signature in the required time. This condition likely indicates a hardware failure.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-SAR_OPEN_COSQ : SAR:([int]/[int]) [chars] [chars] [int] Event: [hex] [hex] [hex] [hex]

Explanation    The component that processes SAR operations encountered an error while a CoSQ channel was being opened.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-SAR_OPEN_VC_ERR : SAR:([int]/[int]) [chars] [chars] [int] Event: [hex] [hex] [hex] [hex]

Explanation    The component that processes SAR operations encountered an error while a VC was being set up.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-SAR_OPEN_VP_TUNNEL_ERR : SAR:([int]/[int]) [chars] [chars] [int] Event: [hex] [hex] [hex] [hex]

Explanation    The component that processes SAR operations encountered an error while a VP tunnel was being opened.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-2-SAR_POLL_TIMEOUT : SAR:[dec] - [chars] error: [chars]

Explanation    The SAR did not reply to the driver command.

Recommended Action    If this error occurs frequently, enter the exec slot slot-number show cont atm port-number sardump command, with slot-number being the slot number of the affected card and port-number being the affected port number. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-SAR_RESERVE_CHANNEL_ERR : SAR:([int]/[int]) [chars] [chars] [dec] Event: [hex] [hex] [hex] [hex]

Explanation    The component that processes SAR operations encountered an error while a channel was being reserved.

Recommended Action    Enter the exec slot slot-number debug lc atm event command, with slot-number being the slot number of the line card with the error. Reproduce the problem if possible. Copy the resulting logged error and debug messages exactly as they appear on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-SAR_SEVERE_ERR : ([int]/[int]): [chars] SAR Fatal Event: [hex] [hex] [hex] [hex]. Resetting the Port.

Explanation    A fatal error occurred during a SAR operation.

Recommended Action    If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-6-SAR_SINGLE_BIT_ECC_ERR : ([int]/[int]): ECC corrected an error in [chars] SAR SDRAM address: [hex]. Syndrome: [hex]

Explanation    A single-bit error has occurred and has been corrected. This error should have no effect on system traffic.

Recommended Action    In most cases, no action is required. In rare cases, this message may indicate faulty hardware. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%PM622-3-SAR_SRAM_PARITY_ERR : ([int]/[int]): Parity error in [chars] SAR SRAM address: [hex].Resetting the port

Explanation    An error was detected in the SAR memory. Memory errors may result from natural phenomena such as cosmic rays, and occasional errors are normal.

Recommended Action    In most cases, no action is required. In rare cases, this message may indicate faulty hardware. If this message recurs within one week, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at