text
stringlengths 78
3.17k
|
|---|
<｜begin▁of▁sentence｜>
### Instruction:
EMA_TP-3-ETMM_EGF_FAILURE
### Response:
(Severity: 3), (Category: PKT_INFRA), (Description: Internal error has occured.), (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:
IMFPGA-3-SI5347_CLOCK_FAILURE
### Response:
(Severity: 3), (Category: PLATFORM), (Description: SI5347 clock failure/success detected on port), (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:
IMUX-3-CF_SBE_ERR_FIA11
### Response:
(Severity: 3), (Category: PLATFORM), (Description: Ingress MUX FPGA encountered FIA11 channel FIFO single bit error.), (Recommended Action: Ensure the ingress MUX FPGA version is latest. Reload the card if the fault is persistent. Contact support if reload of card does not clear the fault. 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:
SNMP_IPC-4-INTERNAL
### Response:
(Severity: 4), (Category: SNMP), (Description: SNMP library incurred an internal software error. This error indicates falied to create thread-specific or debug/ltrace initlization failed.), (Recommended Action: Restart process snmpd check again same senario. 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:
NVGEN-3-GENERAL_ERR
### Response:
(Severity: 3), (Category: MGBL), (Description: 'Nvgen server encountered an error, see message for more details'), (Recommended Action: Collect the show logging output, console logs and error trace. Collect the show nvgen trace output. And contact tac representative with this information.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
OSPF-7-TRACEBACK
### Response:
(Severity: 7), (Category: ROUTING), (Description: An error was encountered during OSPF operation and a traceback was produced.), (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. Please include the output of the following commands: - show logging - show ospf <process-name> - show ospf <process-name> trace all)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
BRIDGE-2-XAUI_1_LQ_FULL_0
### Response:
(Severity: 2), (Category: PLATFORM), (Description: Queue full error on XAUI 1 LQ on bridge instance-0.), (Recommended Action: If the error persists, please reload the board using the command 'hw-module location <> 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:
FABRIC_DRVR-5-POST_FPD_OP
### Response:
(Severity: 5), (Category: FABRIC), (Description: This message posts a notice to indicate that the FPD load operation is completed and a reset of the card is required to come up with the new PLD image.), (Recommended Action: No action is required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
MPLS_LSD-3-ERR_IDT_IM_IDB_ADD_FAIL_MSG
### Response:
(Severity: 3), (Category: ROUTING), (Description: During data transfer from active to standby LSD, standby failed to add interface to it's DB.), (Recommended Action: Please collect show tech for mpls_lsd for further investigation.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
TTY_DB-3-LOCK_BUSY
### Response:
(Severity: 3), (Category: MGBL), (Description: A system call for locking read-write lock failed because lock is busy.), (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:
CPA_INTF_SHELFMGR-3-CARD_REIMAGE_CFG_ERROR
### Response:
(Severity: 3), (Category: PLATFORM), (Description: Setting of the reimage attribute on the indicated card has 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:
FIA-1-SKT_SMC1_INTR_8B10B_DECODE_DISPARITY_ERROR_6_0
### Response:
(Severity: 1), (Category: FABRIC), (Description: SKT_SMC1_INTR_8B10B_DECODE_DISPARITY_ERROR_6 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:
CGN-3-STATPORT_MAP
### Response:
(Severity: 3), (Category: SERVICES), (Description: The static port mapping requested has succeeded.), (Recommended Action: This is a success message and used to inform the user about the outside ipaddress and port number mapped to the inside address and port number.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
ISIS-6-ATOMIC_RING_FULL
### Response:
(Severity: 6), (Category: ROUTING), (Description: The atomic ring for the indicated queue is full.), (Recommended Action: If the situation persists investigae whether there is resource starvation occurring.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
NETIO-7-DELETE_IDB_SUBINTF_FAILED
### Response:
(Severity: 7), (Category: PKT_INFRA), (Description: NetIO cannot delete a interface which still have subinterfaces under it. This could potentially cause issues with recreate of any interface, if the same interface handle is reused.), (Recommended Action: After the information is gathered, restart of netio/ifmgr should possibly bring them in sync with ifmgr & delete the main and subinterfaces. '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:
attestation_agent-2-IMA_DISK_CACHE_FULL
### Response:
(Severity: 2), (Category: MGBL), (Description: A failure occurred during IMA cache creation.), (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:
TAMSVCS-3-SHOW_ERR_DETAILS
### Response:
(Severity: 3), (Category: SECURITY), (Description: Generic Show TAM Error message - (Error Message - Error Detail - Error Description).), (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:
INTERFACE-4-ERR_SYSDB_BIND
### Response:
(Severity: 4), (Category: MGBL), (Description: Failed to bind to system database. Interface stats retrieval could fail because of this 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:
OPTICS-2-BREAKOUT_UNSUPPORTED_MODULE
### Response:
(Severity: 2), (Category: L2), (Description: The breakout mode is not supported on the optics inserted . The behavior of interfaces created is undeterministic.), (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:
NPUXBAR_BRIDGE-0-CPU_PKT_F0_FULL
### Response:
(Severity: 0), (Category: PLATFORM), (Description: IBS from CPU packet FIFO 0 full.), (Recommended Action: Reset the board.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
SYSDB-4-SC_MISMATCH
### Response:
(Severity: 4), (Category: SYSDB), (Description: A quoted token was not terminated with a quote character.), (Recommended Action: Re-enter the command. 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:
SMART_LIC-3-BAD_NOTIF
### Response:
(Severity: 3), (Category: LICENSE), (Description: An invalid notification type was received by the smart agent in the process of logging a syslog message.), (Recommended Action: This is a Smart Call Home internal error. Please report this to Cisco.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
PKG-7-OPEN_FILE
### Response:
(Severity: 7), (Category: INSTALL), (Description: Either the file system is in error, or the Package infrastructure is behaving incorrectly. A file required for carrying out the current request or operation could not be opened, so processing of the operation will halt.), (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:
FSYNC-6-SSM_SMC
### Response:
(Severity: 6), (Category: L2), (Description: The quality level of the source has been changed to or from SMC. Traceable condition occurs when the synchronization message quality level changes to SMC. The login node does not use the clock because the node cannot use any reference beneath its internal level, which is ST3.), (Recommended Action: None, this is an informational condition that does not require troubleshooting.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
OSPF-3-BADMSG
### Response:
(Severity: 3), (Category: ROUTING), (Description: An internal software error occurred.), (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. Please include the output of the following commands: - show ospf <process-name> trace all)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
FABRIC_400G_POD-3-LOW_TEMP
### Response:
(Severity: 3), (Category: FABRIC), (Description: The POD detects a low temperature. The POD might not be functioning properly, and can cause cell drops or corruption in the rx or tx link associated with the POD.), (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:
HA_WD-4-MEMORY_ALARM
### Response:
(Severity: 4), (Category: HA), (Description: Set: Free memory on this node is below the reported threshold. Clear: Free memory is above the MINOR theshold. In both cases, the amount of free memory in megabytes is reported.), (Recommended Action: Investigate memory usage on this node. It may be necessary to unconfigure some applications or move them to a different node. In the case of memory leaks, technical support may need to be contacted.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
VKG_IPV6_EA-3-ERR_INIT_STR
### Response:
(Severity: 3), (Category: PLATFORM), (Description: A runtime error occurred in IPv6 EA. Typically, this is an error where the software fails during initialization. Here is a list of possible reasons for this message (not all-inclusive). - Failed to initialize software. This condition indicates a problem with the software on the card where the error is seen. Typically, this occurs when the software tries to initialize invalid objects. - Invalid objects. This condition indicates a problem where the object being processed by the software is invalid during initialization. - Failed to program forwarding features. This condition indicates a problem where the software fails to program forwarding features to the hardware during initialization/ configuration.), (Recommended Action: Please collect the console log and the CLI output. <CLI> <RP> show cef ipv6 </RP> <LC> show cef ipv6 location <> show cef ipv6 trace location <> show cef platform trace all all location <> </LC> <TECH> show tech cef show version show install active summary </TECH> </CLI> Also notice if the error message is transient or persistent. Report to your technical support representative.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
How does IOS XR achieve infrastructure and service convergence?
### Response:
IOS XR enables infrastructure convergence by providing a single operating system that can run on different distributed platforms with a wide range of interface types and speeds. It enables service convergence by providing a rich set of QoS, virtualization, security, and management features to support different service types on a converged infrastructure.
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
AN-6-MASA_NOT_CONFIG
### Response:
(Severity: 6), (Category: SERVICES), (Description: 'The manufacturer authorised signing authority has ' 'not been configured, cannot do the verification of device'), (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:
CPUCTRLLIB-3-HW_DETECTED_ERROR_CDMA
### Response:
(Severity: 3), (Category: PLATFORM), (Description: CDMA ended in 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:
MPA_MGR-4-MPA_RELOAD
### Response:
(Severity: 4), (Category: PLATFORM), (Description: Reload command received for mpa), (Recommended Action: No action is required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
NPUXBAR_BRIDGE-1-TSPI_BUS_FRAME_ERR
### Response:
(Severity: 1), (Category: PLATFORM), (Description: TxSPI staus bus frame error.), (Recommended Action: --)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
BRIDGE-2-EGR_SGT2_FIFO_OFLOW_1_0
### Response:
(Severity: 2), (Category: PLATFORM), (Description: Egress sgt2 fifo overflow on xaui-1 bridge instance-0.), (Recommended Action: If the error persists, please reload the board using the command 'hw-module location <> 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:
EPM_SWITCH-3-DMAC_LINK_STATE_CHANGE
### Response:
(Severity: 3), (Category: PLATFORM), (Description: The internal link interface for the specified port is down.), (Recommended Action: The board would get reloaded. If users has auto reset option disabled in admin config, then the board would not get reloaded on its own. At this stage collect the output of (admin)'show tech support control ethernet location <nodeId>')
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
IOFPGA-3-BACKUP_FPD_LOADED
### Response:
(Severity: 3), (Category: DRIVER), (Description: The Backup Set of FPD images on IOFPGA Bootflash has been loaded on the indicated card. The output of 'show hw-module fpd' will show the affected images with BACK IMG state. This can happens when IOFPGA detects that one of the Primary image set is corrupted, so it fallback to load the backup image set to recover from the failure.), (Recommended Action: Although the system will continue to run, the backup image set might be of older version and it might have known issues that have been fixed on latest version. So it is critical to address the problem as soon as possible. The output of 'show hw-module location <loc> fpd' will identify the image with the problem with NEED UPGD state and it will have missing Programmed version. To correct the problem, use the 'upgrade hw-module location <loc> fpd <fpd_name>' command to re-program the FPD image and power-cycle the affected card for IOFPGA to load with the upgraded image.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
PIM-3-IDB_INIT
### Response:
(Severity: 3), (Category: ROUTING), (Description: Internal 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:
HFR_IPV4_MRIB-3-FGID_REMOVE_LC_FAIL
### Response:
(Severity: 3), (Category: ROUTING), (Description: The MRIB encountered error while removing LC from FGID), (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:
ETHER_CTRL-4-XCVR_WARNING
### Response:
(Severity: 4), (Category: PLATFORM), (Description: The particular operation mentioned in the message failed due to some reason. This is not a critical failure, the process can continue functioning as expected despite the failure.), (Recommended Action: Debug message only. No action is required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
FSTATSS-3-ERR_DEBUG_REGISTER
### Response:
(Severity: 3), (Category: FABRIC), (Description: Fabric statistics server process encountered an error while registering debug facility and hence failed to initialize. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.), (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:
PLATFORM-6-ERROR_THREAD_CREATE
### Response:
(Severity: 6), (Category: TOPOLOGY), (Description: System Admin Manager failed to allocate resource for the specified thread.), (Recommended Action: No action is required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
EVM-1-TIMEOUT
### Response:
(Severity: 1), (Category: OS), (Description: An Event Manager blocking call was made with an invalid timeout specification.), (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:
CARD_MGR-4-SENSOR_VALUE_SET_BY_TEST_TOOL
### Response:
None
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
MLAN-3-DRIVER_ERROR
### Response:
(Severity: 3), (Category: PLATFORM), (Description: The particular operation mentioned in the message failed due to some reason. This is not a critical failure, the process can continue functioning as expected despite the failure.), (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:
IPV4_MFWD-5-MCAST_DISABLED
### Response:
(Severity: 5), (Category: ROUTING), (Description: Most likely mfwd restarted and while it was down mcast was disabled. The other possibility is that mfwd retsarted while disabling mcast. In either case, when mfwd comes up, it will find that mcast is already disabled. Hence it will log this message and exit normally), (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:
SYSMGR-4-PROC_START_NAME
### Response:
None
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
OSPF-3-IFCHECK
### Response:
(Severity: 3), (Category: ROUTING), (Description: An internal consistency check has failed. An interface appears to be associated with more than one area.), (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. Please include the output of the following commands: - show ospf interface <intf name> - show running-config - show configuration failed - show configuration history last 5 - show commit changes <last 5> - show logging)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
NETFLOW-3-ERR_CFG_APPLY
### Response:
(Severity: 3), (Category: MGBL), (Description: This is an error message in the Netflow manager to indicate that due to specified reasons, it was unable to apply the configuration that it had previously verified and accepted. This errmsg usually means that the netflow running config and netflow operational state are out of sync.), (Recommended Action: This error message indicates that a configuration problem occurred. Try reapplying the configuration. If that fails, the try restarting the process that issued the error message with the command <CmdBold>process restart <name> location <node><NoCmdBold>.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
What is the purpose of the MPLS TE FRR auto-tunnel backup nhop-only feature?
### Response:
The MPLS TE FRR auto-tunnel backup nhop-only feature restricts auto-tunnel backup tunnels to only the next-hop (NHOP) router on the path to the tunnel destination. It does not allow creation of backup tunnels to the next-next-hop (NNHOP) router. This reduces the number of auto-backup tunnels created and the associated overhead, but may provide less protection coverage.
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
LICMGR-3-CHASSIS_MISMATCH
### Response:
(Severity: 3), (Category: LICENSE), (Description: The message displays the result of comparing the license database to the current state of the chassis. If the chassis and license database do not match, the license database will be cleared and implicit evaluation licenses will be available for 90 days. This alarm may occur if the route processor card has been moved from one chassis to another.), (Recommended Action: If a backup of the license database is available it can be restored with the 'license restore' command. Otherwise contact Cisco TAC to obtain a new set of licenses for this system.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
IPV4_MFWD-3-ERR_IFH_BIND
### Response:
(Severity: 3), (Category: ROUTING), (Description: Internal 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:
RS232-4-NO_PACKET_MODE
### Response:
(Severity: 4), (Category: MGBL), (Description: The TTY Server informed the RS232 DLL about a packet mode session, but we don't yet support packet mode.), (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:
IP_TUNNEL-4-EA_RETRY
### Response:
(Severity: 4), (Category: FORWARDING), (Description: The Tunnel-IP EA process has retried programming tunnel interface(s) because other processes are not ready.), (Recommended Action: If the retry does not succeeded in some time, remove and re-create the tunnel.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
MSDP-6-HA_INFO
### Response:
(Severity: 6), (Category: ROUTING), (Description: Information related to HA events like NSR readiness.), (Recommended Action: No action required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
LI-3-NETIO_INIT
### Response:
(Severity: 3), (Category: ACL), (Description: The LI Netio thread encountered the specified error during thread creation or during initialization of the specified facility. System will retry to start the process to recover.), (Recommended Action: If this message recurs, copy the System Message exactly as it appears on the console or in the system log, enter the <CmdBold>show process li_mgr<NoCmdBold> command and, if the line card was reloaded, collect <CmdBold>show context<NoCmdBold> output, contact Cisco technical support representative, and provide the representative with the required_info.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
HFR_IPV4_MRIB-3-CHKPT_XFORM_FAIL
### Response:
(Severity: 3), (Category: ROUTING), (Description: The MRIB encountered error while with chkpoint table xform.), (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_AIS_DEMD
### Response:
(Severity: 1), (Category: PLATFORM), (Description: '.'), (Recommended Action: --)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
IMAEDM-3-SYSMGR_PROC_READY_FAILED
### Response:
(Severity: 3), (Category: PKT_INFRA), (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:
CEPKI-3-CISCOSSH_HOSTKEY_ERR
### Response:
(Severity: 3), (Category: SECURITY), (Description: CEPKI error message for CISCOSSH hostkey.), (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:
SIM_SE-3-HA_DP_FAILED
### Response:
(Severity: 3), (Category: PLATFORM), (Description: HA Data path test failed, reloading ISM.), (Recommended Action: Please collect the output of 'show logging' and contact TAC.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
SRP-7-DEBUG_TRACEBACK
### Response:
(Severity: 7), (Category: L2), (Description: This is a debug message.), (Recommended Action: This message contains debugging information. Debug message only. No action is required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
NVRAM-3-ATTR_NVRAM_LOW_MEM
### Response:
(Severity: 3), (Category: MEDIA), (Description: Could not get enough memory while trying to initialize nvram.), (Recommended Action: 'Router running low in memory. Reboot if possible.')
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
ISIS-4-BFD_CREATE_FAIL
### Response:
(Severity: 4), (Category: ROUTING), (Description: IS-IS failed to create one or more sessions with the BFD server. Retry mechanism will preriodically try to create session.), (Recommended Action: This failure may due to lack of resources. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the failure is not due to a lack of resources seek support. 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:
PLIM_SERVICES-3-BABMI_RESET_FAIL
### Response:
(Severity: 3), (Category: PLATFORM), (Description: An error occurred in creating/accessing shared memory between Bambi server & MANS FPGA server. This error could result in communication loss between MSC and Services PLIM.), (Recommended Action: Do warm reload of the Services PLIM MSC. If the issue persists do a cold reboot of the same. 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:
SEIPC-3-INVALID_OBJECT
### Response:
(Severity: 3), (Category: OS), (Description: Encountered an error in debug module. This error should not impact the major functionality of the module. Here is a list of possible reasons for this message (not all-inclusive). - Invalid objects. This condition indicates a problem where the object being processed by the software is invalid.), (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:
PIM-3-NET_ERR
### Response:
(Severity: 3), (Category: ROUTING), (Description: Internal error. If the error is seen during transient system state, for instance during LC OIR, it is harmless and can be safely ignored.), (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:
CCC-4-ISO_INSTALL_STARTED
### Response:
None
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
ISSUDIR-1-OPERATION_ISSU_RUN_DONE
### Response:
(Severity: 1), (Category: INSTALL), (Description: The ISSU Run operation has completed successfully.), (Recommended Action: No action is required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
MFWD_MA-3-IDB_ERR
### Response:
(Severity: 3), (Category: ROUTING), (Description: A general 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:
PSE-3-INIT_ERROR_MSG
### Response:
(Severity: 3), (Category: L2), (Description: This is a debug message in the PSE Driver to indicate an operation or condition.), (Recommended Action: No action is required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
exec-3-SYSDB_REGISTER_EDM
### Response:
(Severity: 3), (Category: MGBL), (Description: Exec registers its EDM path for storing data. This registration of EDM has failed due to reasons mentioned in the error message. This failure could cause, exec session not to start up or could cause problem in entering configuration submodes.), (Recommended Action: Close the exec session and relogin. If the message recurs, copy and save the message and call your technical support representative for assistance.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
SHELFMGRV2-3-ALARM_ON_ISOLATED_RP
### Response:
(Severity: 3), (Category: PLATFORM), (Description: This message indicates that an alarm is received by shelfmgr when the RP is in isolated state. For critical alarm, reboot is followed.), (Recommended Action: *none*)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
VEEA-4-BCMDPA_L1_PORT_PFC_LLFC_UNSUPPORTED_COEXIST
### Response:
(Severity: 4), (Category: PLATFORM), (Description: PFC and Flowcontrol co-existance is not supported. If both are added together, we dont reject the config but the features are not enabled in Hw and dont work as desired.), (Recommended Action: Unsupported config, fix config. We need to remove both the config and re-add only the config required for the config to start working.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
PLU-4-TBM_INCONSISTENT
### Response:
(Severity: 4), (Category: PLATFORM), (Description: Errors were encountered trying to program hardware tables, forwarding on some entries may be affected, periodic error correction will be attempted.), (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:
PLAT_L2FIB_FXS-3-SECOND_TAG_ANY_NORMALIZATION_VLAN_ERR
### Response:
(Severity: 3), (Category: PLATFORM), (Description: Failed to create Attachment Circuit as second or inner normalization vlan is 4095. Second or inner vlan is 4095 because of following configuration under sub interface, [encapsulation <tag type> <tag id> second-dot1q any].), (Recommended Action: Please use one of the rewrite configuration to resolve 1. rewrite ingress tag push <tag type> <tag id> symmetric 2. rewrite ingress tag translate 1-to-2 <tag type> <tag id>)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
SMC-7-MULTI_NODE_TRANS
### Response:
(Severity: 7), (Category: SYSDB), (Description: An application tried to use a transaction to access multiple nodes; this is not supported currently.), (Recommended Action: *SUPPORT*)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
SNMP-3-DYING_GASP_VRF_REM
### Response:
(Severity: 3), (Category: SNMP), (Description: VRF config has been removed under which snmp dying gasp host was configured. Either re-configure vrf or remove snmp host), (Recommended Action: Reconfigure VRF or remove snmp host config under that VRF)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
PPP_MA-4-ERR_NCP_CAPS_STALE
### Response:
(Severity: 4), (Category: L2), (Description: PPP MA encountered an error when resyncing with IM and discovered an NCP caps where PPP is no longer expected to be running. The most likely reason for this is a connection problem with the IM service and is likely to be a transient issue, but the error could also be caused by low memory resources or programming error.), (Recommended Action: The error is likely to be harmles, if problems are encountered, consider restarting the PPP MA process. 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:
PLAT_CLIENT-2-FEATURE_NEEDED
### Response:
(Severity: 2), (Category: LICENSE), (Description: The specified feature is configured without the necessary license.), (Recommended Action: The customer should either purchase the license or disable the feature.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
GIRO-4-DUPLICATE_PLIM
### Response:
(Severity: 4), (Category: PKT_INFRA), (Description: The platform driver has provided invalid PLIM information that contains duplicated PLIMs.), (Recommended Action: If this is seen following a change in system configuration that results in the feature exceeding the supported scale then remove the configuration and restart this process. If the system has not been configured beyond the supported scale then seek support. 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:
PLATFORM_ASR9K_NETIO_LIB-4-GET_MYNODEID_FAIL
### Response:
(Severity: 4), (Category: PKT_INFRA), (Description: Unable to determine my node id using platform api.), (Recommended Action: Please capture show proc ouput and show logging output - '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:
JACKET-6-INFO
### Response:
(Severity: 6), (Category: L2), (Description: This is an informational message in the jacket driver to indicate an operation.), (Recommended Action: No action is required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
TTY-3-ABNORMAL_EXIT
### Response:
(Severity: 3), (Category: MGBL), (Description: Process exited abnormally by invoking exit().), (Recommended Action: Debug message only. No action is required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
GROUP_MEMBERSHIP-3-GROUP_FIND_ERR
### Response:
(Severity: 3), (Category: ROUTING), (Description: Internal error.), (Recommended Action: Copy the error message exactly as it appears on the console or in the system log. Issue the <CmdBold>show igmp trace error<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 igmp trace error<noCmdBold> output, 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 igmp trace group error<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 igmp trace group error<noCmdBold> output, call your Cisco technical support representative and provide the representative with the gathered information. 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-STDBY_RP_REBOOT_RECEIVED
### Response:
(Severity: 2), (Category: PLATFORM), (Description: Standby RP node notified shelfmgr about its software reboot with the reboot reason and cause code.), (Recommended Action: No action is required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
HFR_L2FIB_METRO_SHOW-7-INVALID_OPTION
### Response:
(Severity: 7), (Category: PLATFORM), (Description: Startup option supplied to l2fib metro show command is not valid.), (Recommended Action: Please re-enter the correct option as described in the usage message 'Usage: hfr_l2fib_metro_show [-N <node name>]' Example: sh controllers hfr int Ten0/2/0/0 loc 0/2/cpu0, or run hfr_l2fib_metro_show -N 33 If the issue is seen after taking the 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:
OBFLMGR-3-EVENT_CONN_CREATION_FAIL
### Response:
(Severity: 3), (Category: OS), (Description: Failed to create event connection. Event connection is necessary for OBFL to handle various events. This will restart the process.), (Recommended Action: If the issue is seen after restart then, collect the following data and contact support. 1. admin show logging onboard trace manager severity info location all 2. admin show logging onboard trace config severity info location all 3. admin show logging onboard trace lib severity info location all 4. show logging 5. show tech-support sysdb)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
FSYNC-4-OTN_FRAMER_DRIVER_CONNECT_FAILED
### Response:
(Severity: 4), (Category: PLATFORM), (Description: An error was encountered while the specified process was initializing. The error message contains details about the source of the error. Frequency synchronization on this line card is disabled.), (Recommended Action: The process will exit and will be restarted. 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:
FSYNC-6-UNKNOWN_BOARD_TYPE
### Response:
(Severity: 6), (Category: PLATFORM), (Description: This line card does is not known to work with the frequency synchronizatoin feature.), (Recommended Action: Report this message.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
What is the purpose of the install activate command in IOS XR?
### Response:
The 'install activate' command is used to make a previously added software package active on the router. It triggers the actual installation of the package and updates the active software set.
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
IFLX_LIB_MGR-3-INTF_DPC_REMOVE_ERR
### Response:
(Severity: 3), (Category: SERVICES), (Description: The Interflex Manager failed to completely clean up interface from the DPC queue after an interface creation failed. This will have left the system in an inconsistent state. The most likely reason for this error is memory exhaustion.), (Recommended Action: Look for ways to free up memory and restart the interflex_mgr process.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
OBFLMGR-7-ENV_STATE_UNKNOWN
### Response:
(Severity: 7), (Category: OS), (Description: An environment record has an unknown state.), (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:
QSDIR-1-QSDIR_RESTART
### Response:
(Severity: 1), (Category: INSTALL), (Description: Quickstart operation aborted because Quickstart Director restarted unexpectedly and the operation could not be resumed.), (Recommended Action: The reason for this operation failure has to be analyzed. Collect the show tech logs by running 'show tech-support qs' and forward the logs to the TAC. Provide the details about any relevant system events/operations before this failure.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
FCA-2-SFP_I2C_PHY_ACK_ERROR
### Response:
(Severity: 2), (Category: PLATFORM), (Description: Port controller driver detected I2C access error on PHY SFP port.), (Recommended Action: Ensure that the SFP plugged in is supported. If not, replace the SFP. 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:
SSM_LIB-7-DEBUG
### Response:
(Severity: 7), (Category: OS), (Description: Debug message), (Recommended Action: No action is required.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
INSTHELPER-4-SYSDB_BIND
### Response:
(Severity: 4), (Category: INSTALL), (Description: This may be because the communications infrastructure is not yet up. If this problem persists, the operations of the Install infrastructure may not be able to proceed.), (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:
SSHD_CONF_PRX-3-ERR_SYSDB_DATALIST
### 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:
AAA_BASE-3-ERROR
### Response:
(Severity: 3), (Category: SECURITY), (Description: Error encountered while running AAA Base), (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:
TURBOBOOT-7-DISK_INACCESSIBLE
### Response:
(Severity: 7), (Category: INSTALL), (Description: Install device could not be accessed and may be corrupt or missing.), (Recommended Action: Check if the boot device is installed correctly. Run disk checks using 'fsck' disk check CLI. Based on the outcome of disk check take corrective action and retry turboboot.)
<|EOT|>
|
<｜begin▁of▁sentence｜>
### Instruction:
ROMMON_BURNER-3-FILE_OP_ERR
### Response:
(Severity: 3), (Category: PLATFORM), (Description: Error occured with file operations.), (Recommended Action: No action is required..)
<|EOT|>
|