text
stringlengths 78
3.17k
|
|---|
<｜begin▁of▁sentence｜>
### Instruction:
NVGEN-3-INVALIDTEMPLATE
### Response:
(Severity: 3), (Category: MGBL), (Description: 'The template in this file is invalid or wrong version'), (Recommended Action: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
MXPDRVR-3-NCS1K_SDK_INIT_FAILURE
### Response:
(Severity: 3), (Category: PLATFORM), (Description: SDK initialization for the specified coherentDSP device has failed on the specified slice. No configuration and manageability data retrieval is possible on the coherentDSP port.), (Recommended Action: The casue for the failure has to be analyzed. Collect the show tech logs by running 'show tech-support ncs1k detail' and forward the logs to the TAC. Provide the details about any relevant system events/operations before this failure.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
DIAG-3-INVALID_TEST
### Response:
(Severity: 3), (Category: DIAG), (Description: A test for diagnostics that does not exist was requested.), (Recommended Action: Ensure the specified test name is supported by the line card. The list of available tests can be retrieved using show diagnostic content.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
BGP-3-SRV6_SIDMGR_API_FAIL
### Response:
(Severity: 3), (Category: ROUTING), (Description: An SRv6 sidmgr API returned an error.), (Recommended Action: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
UDPSNMP-3-SYSTEM
### Response:
(Severity: 3), (Category: SNMP), (Description: Failed to execute a system call. This could be due to low memory condition or an internal software error.), (Recommended Action: Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
LIBSYSDB-3-INVALID_REQUEST
### Response:
(Severity: 3), (Category: SYSDB), (Description: A client process requested access or registration with non-empty relative item/area name on a connection bound to an item), (Recommended Action: *SUPPORT*)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
LDP-3-INTERNAL_INCONSISTENCY
### Response:
(Severity: 3), (Category: ROUTING), (Description: LDP has detected an internal inconsistency. Please capture a core file for analysis.), (Recommended Action: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
exec-3-TTY_MGMT_DEREGISTER
### Response:
(Severity: 3), (Category: MGBL), (Description: The call to tty_mgmt_deregister_tty_options() failed), (Recommended Action: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
MKA-5-TX_SECURE_CHANNEL_TERMINATED
### Response:
None
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
FSDB_FADB-4-SHM_FILE_TRUNCATE_FAIL
### Response:
(Severity: 4), (Category: FABRIC), (Description: FSDB FADB encountered an error while attempting to truncate the FADB shared memory file), (Recommended Action: Search the event logs for events/errors related to the failure reason. Shared Memory Management and disk access is part of overall system. If there are failures here then other processes may also exhibit similar problems. Collect all the event logs (show logging) output of the following command. 'admin show process fsdb_fadb location <loc>' Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
EGRESSQ_HW_DLL-3-IMDR_MAP_ERROR
### Response:
(Severity: 3), (Category: L2), (Description: There is a discrepancy between the egressq configuration before and after IMDR. The egressq configuration after IMDR should normally be the same as before. This could indicate an internal software error.), (Recommended Action: Watch for potential drop in the egress traffic. If the router misbehaves or traffic is dropped, please collect the information from the following commands for the line card that reported the error: show tech show controller egressq trace all show controller egressq interface all show controller egressq port all show controller egressq group all show controller egressq queue all show qos ea trace all Call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
IFMGR-3-CAPS_DELETE
### Response:
(Severity: 3), (Category: PKT_INFRA), (Description: IM has implicitly removed some caps nodes as part of an interface delete. These caps nodes should have been removed prior to the interface delete.), (Recommended Action: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
RSP_CPUCTRL-2-PCB_VERSION_ERROR
### Response:
(Severity: 2), (Category: PLATFORM), (Description: RSP CPU controller driver version is not compatible with the current Board.), (Recommended Action: Please try to correct the problem by reloading the board using command: 'reload location <>'. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
DSC-4-WARNING_HB_THRESHOLD
### Response:
(Severity: 4), (Category: PLATFORM), (Description: Heartbeats over control-ethernet from the node in question are being missed. This usually indicates a CE transport issue. Please check control ethernet connections to and from the node in question. Note, these messages are expected if node in question is going down due to a user trigger such as OIR, failover), (Recommended Action: Check the control ethernet connectivity to the node. (Check if the cables are okay and also if the switch is operating normally).If the connectivty is fine and none of the mentioned conditions are there,Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
NPUXBAR_BRIDGE-1-RSPI_PROT_BURST_ERR
### Response:
(Severity: 1), (Category: PLATFORM), (Description: RxSPI protocol burst error.), (Recommended Action: None.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
FIA-1-SKT_SP1_INTR_SLICE_ERR_0_0
### Response:
(Severity: 1), (Category: FABRIC), (Description: SKT_SP1_INTR_SLICE_ERR_0 interrupt on FIA), (Recommended Action: Wait a few minutes. If it doesn't recover, please reload the board using command 'reload location <>'. Make sure board is seated properly. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
umass_enum-3-FAILED_TO_OPEN_PATH
### Response:
(Severity: 3), (Category: PLATFORM), (Description: Wait for dlls to get loaded since usb pkg is loaded before infra/watchdog (wdsysmon).And it wait for the disk to be mounted. This error message will get printed when it unable to open path to register for diskspace monitoring.), (Recommended Action: If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
SMS-7-RESTARTING
### Response:
(Severity: 7), (Category: SYSDB), (Description: The SysDB server is unable to function due to a problem with a piece of infrastructure. The only hope of recovery is to restart. If the problem persists, the card will be automatically reloaded.), (Recommended Action: If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
CANB_SERVER-3-IDPROM_CACHE_OVERFLOW
### Response:
(Severity: 3), (Category: PLATFORM), (Description: This is an error message related to the Canbus Controller processing the received UART message.), (Recommended Action: Do EP soft/hard OIR, or restart canb-server.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
FIA-1-TEMP_TOO_HIGH_0
### Response:
(Severity: 1), (Category: FABRIC), (Description: Crossbar fabric interface ASIC-0 is reporting a very high temperature.), (Recommended Action: Check if board is reporting temperature alarm. If not, it is due to Crossbar fabric interface heatsink not being installed properly. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
LDP-4-RX_PKT_MALFORMED
### Response:
(Severity: 4), (Category: ROUTING), (Description: Packet received was malformed.), (Recommended Action: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
CLNS-3-CONFIG_INIT
### Response:
(Severity: 3), (Category: ROUTING), (Description: CLNS could not initialize its configuration mechanism, and all future CLNS configuration will fail.), (Recommended Action: Please contact cisco-support with required information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
CPAK-2-LANE_5_LOW_TEMP_ALARM
### Response:
(Severity: 2), (Category: PLATFORM), (Description: Environmental monitoring has detected a CPAK laser temperature less than or equal to the low temperature alarm threshold. The CPAK is the pluggable optics on the line cards. The temperature threshold values are read from the CPAK.), (Recommended Action: The system detected a low temperature threshold crossing which normally won't affect any service. Monitor the system to see if the condition clears. Generally no action needs to be taken for this condition and is more informational. If any service is affected, check the device is properly inserted. Replace the CPAK with working one (if any). Check all the FPDs are upto date using 'show hw-module fpd location all'. If the issue persists then copy the error message exactly as it appears, and report it to your technical support representative. If possible, also provide the output of the commands 'show tech-support ethernet interface location <loc>', 'show hw-module fpd location all', 'admin show inventory', 'show environment temperatures' and 'admin show environment fans'.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
RSP_CPUCTRL-2-SLOTID_PAR_ERROR
### Response:
(Severity: 2), (Category: PLATFORM), (Description: RSP CPU controller has detected slot id parity. This could be possible if RSP is not seated properly.), (Recommended Action: Check to see if the RSP is seated properly. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
FIA-1-SKT_SMC0_INTR_DISP_ERROR_LANE_INDICATE_15_0
### Response:
(Severity: 1), (Category: FABRIC), (Description: SKT_SMC0_INTR_DISP_ERROR_LANE_INDICATE_15 interrupt on FIA), (Recommended Action: Wait a few minutes. If it doesn't recover, please reload the board using command 'reload location <>'. Make sure board is seated properly. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
DOT1X-4-NO_AUTHENTICATION_METHOD
### Response:
(Severity: 4), (Category: L2), (Description: There is no 'aaa authentication dot1x ' configuration, to direct dot1x authentication request to remote AAA server. Neither there is complete eap profile hooked under authenticator dot1x profile to enable local authentication), (Recommended Action: For remote autheticaton, configure 'aaa authentication dot1x default group <>' , or to use local eap server, configure a complete eap profile and attach it to authenticator sub mode under dot1x profile.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
RS232-4-API_LOCATE_ERROR
### Response:
(Severity: 4), (Category: MGBL), (Description: The RS232 DLL was unable find the details required from a DLL it had loaded.), (Recommended Action: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
REPLICATOR-7-UPDATE_FAILED
### Response:
(Severity: 7), (Category: LIBRARY), (Description: The client returned an error when trying to apply an update. The replicator library will try to recover by requesting a replay of the update. If this condition persists, data may be lost on failover.), (Recommended Action: If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
OBFLMGR-7-UPTIME_CONT_TOO_LARGE
### Response:
(Severity: 7), (Category: OS), (Description: A continuous record too large, or internal parameter might be corrupted.), (Recommended Action: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
CT_DSP-1-ALARM_RX_LOSS_OF_CHANNEL
### Response:
(Severity: 1), (Category: PLATFORM), (Description: '.'), (Recommended Action: --)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
CPAK-3-LANE_9_HIGH_RX_POWER_WARNING
### Response:
(Severity: 3), (Category: PLATFORM), (Description: Environmental monitoring has detected a CPAK Rx power greater than or equal to the high Rx power warning threshold. The CPAK is the pluggable optics on the line cards. The Rx power threshold values are read from the CPAK.), (Recommended Action: Verify that the device is properly inserted. Verify that the input signal has the necessary attenuation. Replace the attenuator with working one (if any) to isolate bad attenuator. Replace the optics with working one (if any) to isolate bad optics. If the issue persists then copy the error message exactly as it appears, and report it to your technical support representative. If possible, also provide the output of the commands 'show tech-support ethernet interface location <loc>', 'show hw-module fpd location all' and 'admin show inventory'.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
FSDB-0-BARRIER_STALL_RACK_RELOAD
### Response:
(Severity: 0), (Category: FABRIC), (Description: Rack is brought down if RPs on the rack are detected stalling on fabric barriers. If the rack is isolated from fabric via CLI, then this is expected. If this message occurs otherwise, it could be due to a software error or an unexpected hw error.), (Recommended Action: If fabric links, fabric cards or fabric chassis connecting to the rack are brought down via CLI, then this is expected. If the problem happens otherwise, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
IGPTE_LIB-3-ERR_SYSDB_BIND
### Response:
(Severity: 3), (Category: ROUTING), (Description: An error occurrred when accessing the system database), (Recommended Action: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. The process must be restarted before it can function correctly.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
INSTMGR-6-INSTALL_RUN_PHASE_FINISHED
### Response:
(Severity: 6), (Category: INSTALL), (Description: The run phase of an ISSU operation has finished successfully.), (Recommended Action: No action is required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
ETNA-1-ALARM_LOS_PORTT4
### Response:
(Severity: 1), (Category: PLATFORM), (Description: 'Tx CAUI LOS'), (Recommended Action: Check/replace cable. Check/replace optics module.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
BRIDGE-3-NPU_1_PKT_MINLEN_ERR_2
### Response:
(Severity: 3), (Category: PLATFORM), (Description: Packet minimum length error on NPU-1 interface on bridge instance-2.), (Recommended Action: If the error persists, please reload the board using the command 'reload location <>'. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
BM-6-MLACP_BUNDLE_MAC_ARBITRATION
### Response:
(Severity: 6), (Category: L2), (Description: Each mLACP peer specifies a MAC address for a bundle. If the MAC addressess are different, arbitration must occur. However, if the peer that has supplied the value selected through arbitration disconnects, there will be a flap in the bundle state.), (Recommended Action: If the alarm is set, the user should ensure that all peers have the same MAC address for the bundle.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
CFM-3-WL_QUEUE_FAILED
### Response:
(Severity: 3), (Category: L2), (Description: The CFM MA failed to schedule an operation required to modify Maintenance Point configuration for an interface. This is likely to be a system resource issue.), (Recommended Action: Attempt to resolve any memory issues before attempting to solve this problem. After system resource issues have been resolved, issue 'process restart cfmd' on the affected node. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
FIA-1-SKT_SMC1_INTR_CRC_TRANS_ERR_0
### Response:
(Severity: 1), (Category: FABRIC), (Description: SKT_SMC1_INTR_CRC_TRANS_ERR interrupt on FIA), (Recommended Action: Wait a few minutes. If it doesn't recover, please reload the board using command 'reload location <>'. Make sure board is seated properly. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
SSRP-4-ERR_LOOPED
### Response:
(Severity: 4), (Category: L2), (Description: An SSRP message has been received containing the local magic number. This makes it highly likely that the SSRP TCP channel is connected to itself. In the unlikely event that both ends select the same magic number, a new random number is chosen locally, so the situation will recover itself.), (Recommended Action: Check that the SSRP configuration for the network is correct. The most likely problem is that the peer IPv4 address specified in the SSRP Profile configuration is a local IPv4 address - so the TCP packets that are being sent are simply arriving back on the same router.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
What is the purpose of the 'default-information originate' command in OSPF?
### Response:
The 'default-information originate' command is used to generate a default external route into an OSPF routing domain. This is commonly used when redistributing routes from another protocol into OSPF and you want OSPF to propagate a default route.
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
SSHD_CONF_PRX-3-ERR_SYSDB_SET
### Response:
(Severity: 3), (Category: SECURITY), (Description: Internal error.), (Recommended Action: 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.')
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
FSDB_AGG-6-PPU_START
### Response:
(Severity: 6), (Category: FABRIC), (Description: FSDB aggregator has started Calvados plane by plane upgrade. Please avoid disrupting the router by doing OIRs, link/plane shutdowns till it completes), (Recommended Action: If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
LPTS_PREIFIB-4-SYSDB
### Response:
(Severity: 4), (Category: OS), (Description: An internal sysdb function failed.), (Recommended Action: Please collect the output of the following commands: - show tech-support lpts - show tech-support sysdb - show logging)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
SMART_LIC-6-CONSOLE_MSG
### Response:
(Severity: 6), (Category: LICENSE), (Description: Smart Agent console message logging.), (Recommended Action: None.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
SFE_DRVR-3-ASIC_DMA_FAILURE
### Response:
(Severity: 3), (Category: FABRIC), (Description: DMA write failed), (Recommended Action: Collect the output of the following commands executed from the CLI of the active RP from sysadmin VM and reload the card to recover. 1. 'show processes sfe_driver location <loc>' 2. show tech-suport ctrace 3. show tech-support fabric 4. dmesg from host and sysadmin VM 5. /var/log/messages from host and sysadmin VM If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
DISCOVERY-3-RAM_ECC_2BIT
### Response:
(Severity: 3), (Category: PLATFORM), (Description: Two or more bit ECC error (Uncorrectable) found in a RAM Access.), (Recommended Action: This is a critical error which will cause board-reset. Check if the board comes up fine after reload. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
rewrite-1-DB_VERSION_CHANGE
### Response:
(Severity: 1), (Category: L2), (Description: The rewrite database is unreadable following a version change caused by a SMU being installed.), (Recommended Action: Remove the SMU which was just installed. If the problem persists, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
VIC-3-MAC_NOT_CONFIGURED
### Response:
(Severity: 3), (Category: PLATFORM), (Description: This message provides information about the mac configuration.), (Recommended Action: Collect console log and the following information. Contact your technical support representative. - sh platform - sh processes vic location <> - show tech-support ethernet interface)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
What is the purpose of the MPLS VPN extranet feature?
### Response:
The MPLS VPN extranet feature allows MPLS VPN service providers to distribute routes across VPN boundaries. It enables a VPN to share common routes with other VPNs, providing controlled access between VPNs. Extranet VPNs are implemented by configuring route targets to be imported and exported between VPNs that need to share routes.
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
FR_VCM_EA-3-NO_STATS
### Response:
(Severity: 3), (Category: L2), (Description: The FR VCM EA subinterface stats collection initialization failed. The statsd server process might be too busy to listen to the bind/registration request.), (Recommended Action: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
CHKPT_MESSAGING-7-EVENT_MANAGER
### Response:
(Severity: 7), (Category: HA), (Description: A call to an event manager function failed.), (Recommended Action: Collect system log information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
OTNLC_FPD-6-UPG_NOT_SUPPORTED
### Response:
None
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
IP_EA-3-BLOCKAGE
### Response:
(Severity: 3), (Category: IP), (Description: The ipv4/ipv6 EA is trying to program FIB or the platform and a delay was noticed. This delay could lead to other undesirable side effects such as failing to apply configuration etc.), (Recommended Action: Monitor the affected node to see whether any processses are blocked.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
SFE_DRVR-3-ASIC_PON_RESET
### Response:
(Severity: 3), (Category: FABRIC), (Description: The device failed due to the above mentioned error. The device is being reset (PON) to recover from failure), (Recommended Action: Collect all the event logs and the output of the following commands executed from the CLI of the active RP if the asic is continuously reset and recovery does not take place after device reset: 1. 'show processes sfe_driver location <loc>' 2. Collect all traces: 'show controller sfe trace all location <loc>' 3. dmesg and /var/log/messages from host and sysadmin VM If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
FABRICQ-5-MI_BPDECODE
### Response:
(Severity: 5), (Category: FABRIC), (Description: Fabricq ASIC encountered a MI Unicast/Multicast BP Decode error), (Recommended Action: *SUPPORT*)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
CE_TFTP-6-INVALID_PKT
### Response:
(Severity: 6), (Category: IP), (Description: Received an invalid packet from Ethserver due to the specified reason in the message,hence dropping the packet.), (Recommended Action: This is an informational message. No action is required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
PLAT_FIB-6-VERSION_INFO
### Response:
(Severity: 6), (Category: PLATFORM), (Description: PLATFORM FIB, Information), (Recommended Action: The message is just for information. No action is needed.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
PLAT_NVSAT_EA_LTRACE-6-ERR_INFO_VERBOSE
### Response:
(Severity: 6), (Category: PLATFORM), (Description: Failed to initialize the the platform NVSAT EA LTRACE component.), (Recommended Action: No action is required. Platform software will correct itself if this happens.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
PLAT_THOR_L2FIB_LOCSW-7-LTRACE_WARNING
### Response:
(Severity: 7), (Category: PLATFORM), (Description: Failed to initialize the ltrace module in the platform L2FIB LOCSW component.), (Recommended Action: None, platform software will correct itself if this happens.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
OSPFv3-3-SYSMGR
### Response:
(Severity: 3), (Category: ROUTING), (Description: A specified system manager request failed.), (Recommended Action: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Copy the error message exactly as it appears on the console or in the system log. Issue the <CmdBold>show tech-support<noCmdBold> command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the <CmdBold>show tech-support<noCmdBold> output, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
CPUCTRL-3-HW_DETECTED_ERROR_PCIX
### Response:
(Severity: 3), (Category: PLATFORM), (Description: The cpuctrl driver HW error interrupt handler was invoked and found valid PCIX error registers.), (Recommended Action: If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
ELO-3-EVENT_HANDLER_ERROR
### Response:
(Severity: 3), (Category: L2), (Description: The Ethernet Link OAM EA failed to process an event and will now exit. It should be restarted by SysMgr, allowing it to resynchronise its internal state.), (Recommended Action: If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
HTTP-7-DEBUGGING
### Response:
(Severity: 7), (Category: MGBL), (Description: A Debugging operation carried out by the HTTP Server returned unexpected results.), (Recommended Action: If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
10GE_PLIM-4-RX_RF
### Response:
(Severity: 4), (Category: L2), (Description: The PLIM received a remote fault on the given interface which will result in a link flap.), (Recommended Action: No action is required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
CT_DSP-1-ALARM_LOS_PORTR9
### Response:
(Severity: 1), (Category: PLATFORM), (Description: 'Tx CAUI LOS'), (Recommended Action: Check/replace cable. Check/replace optics module.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
flash_platform-3-FAIL_TO_OPEN_FILE
### Response:
(Severity: 3), (Category: PLATFORM), (Description: Device stale bytes must be cleaned to get the free space. This error message will be displayed when the device open has failed during the cleaning of stale bytes.), (Recommended Action: If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
NP-4-INVMGR_SLICE_INFO_MISMATCH
### Response:
(Severity: 4), (Category: PLATFORM), (Description: The NP driver received slice data diff than existing value), (Recommended Action: No action is required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
PLAT_FIB_RP-3-UPDATE_ERR
### Response:
(Severity: 3), (Category: PLATFORM), (Description: During initialization of the Forwarding-Information-Base of the CRS platform, an unexpected error has occurred during an update operation. The running software should automatically recover if it isn't a hardware error.), (Recommended Action: If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
MPLS_TE-5-LSP_SOFT_PREEMPT
### Response:
(Severity: 5), (Category: ROUTING), (Description: The specified interface, with the specified LSP Id, has been soft \ preempted at specified IP address or local node. The first %s refers to \ the signalled tunnel name and the second %s refers to the interface name \ where the preemption was signalled. The third %s refers to the address of \ the signalling interface. The fourth and fifth %s are filled out if frr \ rewrite is done during soft preemption. The fourth %s is a message stating \ the traffic has been moved to a backup tunnel and fifth %s is the name of \ the backup tunnel.), (Recommended Action: None.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
VIF_MA-2-EMA_INIT_ERR
### Response:
(Severity: 2), (Category: L2), (Description: Failed to connect to open a connection channel to initialize the Ethernet MAC Allocation library. This prevents the process from getting MACs dynamically. Configuring static MACs under the interface is still possible.), (Recommended Action: *support*)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
QOS_MA-3-DPC_REM
### Response:
(Severity: 3), (Category: QOS), (Description: The QoS MA process encountered the specified error while trying to send a critical operation to the EA.), (Recommended Action: Contact TAC with required_info.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
What is the purpose of the metric-style command in IS-IS?
### Response:
The metric-style command is used to configure the type of metric used by IS-IS. The options are narrow (old-style 6-bit metrics), wide (new-style 24-bit or 32-bit metrics), and transition (both metrics during a transition period). Wide metrics provide a larger range of values and are useful in large networks. Narrow metrics are compatible with older implementations.
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
MULTILINK_UV-3-SYSMGR
### Response:
(Severity: 3), (Category: L2), (Description: The process was initialized successfully but was unable to inform System Manager of the success.), (Recommended Action: If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
PPPOE_MA-4-WARN_ACC_IF_SES_THRESHOLD_EXCD
### Response:
(Severity: 4), (Category: SUBSCRIBER), (Description: The number of PPPoE sessions on the access interface has exceeded the configured threshold.), (Recommended Action: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
SERDES-3-RX_ERR
### Response:
(Severity: 3), (Category: PLATFORM), (Description: A receive error occurred at the physical layer of the port. It can be a transient self-clearing error when a port is admin shutdown or enabled. Else, it is an indication of a fault on the line. In most cases, the fault would bring the port link down and cause complete traffic drop. In case the link is still up, there may be intermittent packet drops due to encoding errors in packets received.), (Recommended Action: The fault can be ignored if it is self-clearing during the process when the port is admin shutdown and then enabled. If the fault remains for an extended period then please check the presence of the module and proper fiber connectivity. If module and fiber connectivity is verified then contact Cisco support with the output of the commands: 'show controllers tenGigE <i/f> all'. 'show serdes trace configuration location <>' 'show serdes trace periodic location <>' 'show serdes trace interrupt location <>' 'show tech-support ethernet interface location <loc>' 'show hw-module fpd location all' 'admin show inventory')
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
SSE_QOSEA-3-BANDWIDTH_REMAINING_RATIO
### Response:
(Severity: 3), (Category: QOS), (Description: The bandwidth remaining ratio is invalid at this level. The message will provide further details on the error.), (Recommended Action: Please adjust the bandwidth remaining parameters in the policy map.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
PLAT_CLIENT-2-UPGRADE_LICENSE_PENDING_STATE
### Response:
(Severity: 2), (Category: LICENSE), (Description: Upgrade License status couldn't be obtained.), (Recommended Action: The customer should check the connection to the backend Smart Licensing server.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
QNET-3-WRITE_QNET_PAK_ERR
### Response:
(Severity: 3), (Category: OS), (Description: %d- Number of particles %d- Maximum IOV parts valid %d- Length of the packet %d- Maximum MTU size supported), (Recommended Action: Ignore the message if it only appears once otherwise contact TAC)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
What is the purpose of the 'bgp confederation identifier' command in IOS XR BGP configuration?
### Response:
The 'bgp confederation identifier' command is used to configure the BGP confederation identifier. A confederation is a technique used to reduce the iBGP mesh inside an AS. The AS is divided into multiple sub-AS, each identified by a confederation identifier. Each sub-AS has a full iBGP mesh, and an eBGP session is used between the sub-AS. To external peers, the confederation still appears as a single AS.
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
DNX_SPAN_EA-4-CFG_OVERRIDE
### Response:
(Severity: 4), (Category: PLATFORM), (Description: monitor-session is already configured on the bundle member interface and configuring monitor-session on bundle-ether will override the old monitor-session config.), (Recommended Action: To avoid confusion, user should remove monitor-session config from bundle member interface which is no longer active.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
DAPS-5-POOL_UTIL_HIGH
### Response:
(Severity: 5), (Category: IP), (Description: Utilization exceeded high threshold for specified pool. Pool may deplete very soon and so it would be good to add more address ranges for allocation to new clients. Otherwise new address allocation requests will fail. Pool utilization can be monitored using the command 'show pool ipv4/ipv6 name <pool_name>'.), (Recommended Action: Add more address ranges for the specified pool. For details regarding related configurations, please refer 'Address Pool Service Commands' chapter in Cisco IOS XR software configuration guide.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
FR_INARP-3-UNKNOWN_IDB
### Response:
(Severity: 3), (Category: L2), (Description: A set of IDBs are kept with information on each InARP interface. Somehow this information has become inconsistent with the system.), (Recommended Action: Restart the main process (containing the InARP DLL) If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
PPPOE_MA-4-ERR_IMC
### Response:
(Severity: 4), (Category: SUBSCRIBER), (Description: PPPoE MA encountered an error communicating with Interface Manager. The error message describes what operation has failed and why it failed. The most likely reason for this is a temporary connection problem with the Interface Manager Control Server, but the error could also be caused by low memory resource or programming error.), (Recommended Action: In many cases, PPPoE MA will recover by itself. If it does not then restarting the process may help. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
OTN_FRAMER-3-CONFIG_OOS_FAILURE
### Response:
(Severity: 3), (Category: OS), (Description: Maximum retries of OOS Message are reached. Discarding this message.), (Recommended Action: None. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
SM-3-COMMUNICATION
### Response:
(Severity: 3), (Category: INSTALL), (Description: The communications infrastructure may not yet be initialised. If this problem persists, seek guidance.), (Recommended Action: The communications infrastructure may not be up yet. Please retry the operation. If the message recurs continuously, please contact support.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
SHELFMGR-3-FAILEDPOWERUP
### Response:
(Severity: 3), (Category: PLATFORM), (Description: This message indicates the board in named slot failed to power up. The node will be reloaded automatically.), (Recommended Action: If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
PMIPV6-3-NOT_AUTHORIZED_FOR_IPV6_MOBILITY_SERVICE
### Response:
(Severity: 3), (Category: IP), (Description: Service configured for the MN or Logical-MN in the MN profile in domain configuration is IPv4-only; however, HNP option is received in the PBU.), (Recommended Action: Configure IPv4-only service on the MAG. Alternatively, configure service on the LMA in the MN profile to match with that on he MAG. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
B_SHIM_PARTNER-3-CAP_ADD_ERR
### Response:
(Severity: 3), (Category: L2), (Description: 'There is an error when adding batched channelized interface caps.'), (Recommended Action: Perform below steps and see if error goes away: 1) SPA process restart by executing CLI: 'process restart <spa_process_id> location <> 2) Netio process restart by executin CLI: 'process restart netion location <>' 3) SPA reload by executing CLI: 'hw-module subslot <> reload')
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
CERR_LIB-7-SETSPECIFIC
### Response:
(Severity: 7), (Category: OS), (Description: The infrastructure library was unable to set a threadspecific data pointer for thread private data storage.), (Recommended Action: Check to see if sufficient memory resources remain for normal operations. Add memory if necessary.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
BGP-5-VRF_CLEANUP_DELAY
### Response:
(Severity: 5), (Category: ROUTING), (Description: BGP is taking more than usual time to cleanup the VRF. This normally happens due to improper config or overflowing supported scale limitations), (Recommended Action: This message is for information purpose only. Request to revisit config and scale)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
IP_TUNNEL-3-IF_CREATE_RETRIES_EXHAUSTED
### Response:
(Severity: 3), (Category: FORWARDING), (Description: An error was encountered while creating the tunnel interface. It was retried a number of times, but all reties exhausted. This occurs when interface manager is not ready to create interface state in at least one LC or RP.), (Recommended Action: Configure the tunnel interface again after a minute or two. If the error persists, then do the following action. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
RDS-7-ENS_PRODUCER_RELEASE
### Response:
(Severity: 7), (Category: OS), (Description: RDS library uses ENS/GSP services to read/write data. While using ens API , it returned failure. ens_producer_release failed.), (Recommended Action: If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
SHELFMGRV2-2-INDUCED_QNET_DOWN
### Response:
(Severity: 2), (Category: PLATFORM), (Description: This message indicates that shelfmgr was induced to send out a qnet node-down notification for the given node by the user.), (Recommended Action: No action is required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
ITAL-3-MEM_ALLOC_FAILURE
### Response:
(Severity: 3), (Category: OS), (Description: A memory allocation operation failed.), (Recommended Action: Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
INSTMGR-2-SYSTEM_RELOAD_INFO
### Response:
(Severity: 2), (Category: INSTALL), (Description: Specified message provides info that the entire system will be reloaded as part of the specified install operation.), (Recommended Action: No action is required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
EIGRP-5-NBRCHANGE
### Response:
(Severity: 5), (Category: ROUTING), (Description: An EIGRP neighbor has gone UP or DOWN.), (Recommended Action: No action is required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
SONET_APS-7-ERROR
### Response:
(Severity: 7), (Category: L2), (Description: A general failure occured while executing the function in question. The message contains info about the cause of the failure and possibly anticipated actions/effects.), (Recommended Action: Verify continued correct operation of SONET APS.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
OBFLINFRA_CLI-7-SYMBOL_NOT_FOUND
### Response:
(Severity: 7), (Category: OS), (Description: A symbol notified from a process is not found), (Recommended Action: If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
SIM_SE-3-SYS_INIT_FAILURE
### Response:
(Severity: 3), (Category: PLATFORM), (Description: TBD.), (Recommended Action: Please collect the output of 'show logging' and contact TAC.)
<|EOT|>
|