Cisco IOS XR System Error Reference Guide for XR1200 Series Platform Specific Messages, Release 3.3
High Availability (HA) Messages
Downloads: This chapterpdf (PDF - 166.0KB) The complete bookPDF (PDF - 2.03MB) | Feedback

High Availability (HA) Messages

Table Of Contents

High Availability (HA) Messages

LRD_inv Messages

PSARB Messages

PSARBLC Messages


High Availability (HA) Messages


This section contains all High Availability related System Error Messages. The following facility codes are represented in this module:

LRD_inv Messages

PSARB Messages

PSARBLC Messages

LRD_inv Messages

Error Message     
 
    
    
   

%HA-LRD_inv-3-BAG_REGISTRATION Unable to register LRd's bag structures. '[chars]'

Explanation    LRd was unable to register bag structures.

Recommended Action    Contact support.

Error Message     
 
    
    
   

%HA-LRD_inv-3-MEM_ALLOC_FAIL Failed to allocated [dec] bytes of memory: [chars]

Explanation    The requested operation could not be accomplished because of a low memory condition.

Recommended Action    Contact TAC.

Error Message     
 
    
    
   

%HA-LRD_inv-3-MSG_CERR_REGISTER_DLL Could not register dll with error services: [chars]

Explanation    The call register the dll using cerr_register_dll failed.

Recommended Action    Contact support.

Error Message     
 
    
    
   

%HA-LRD_inv-3-MSG_INVENTORY_FWD Error forwarding inventory: '[chars]'

Explanation    LRd was unable to read or write information needed to forward inventory in Admin space to the LR Plane.

Recommended Action    Contact support.

Error Message     
 
    
    
   

%HA-LRD_inv-3-REDUNDANCY_STATE Unrecognized redundancy state [dec]

Explanation    LRd doesn't recognize redundancy state.

Recommended Action    Contact support.

Error Message     
 
    
    
   

%HA-LRD_inv-3-SYSDB_ITEM_ERROR sysdb_item_[chars]([chars]) returned '[chars]'

Explanation    SysDB returned an error to LRd.

Recommended Action    Contact support.

Error Message     
 
    
    
   

%HA-LRD_inv-4-CANT_FIND_DSC LR Daemon library could not find the dSC.

Explanation    LRdlib could not find the dSC.

Recommended Action    Collect system log information. No action is required.

Error Message     
 
    
    
   

%HA-LRD_inv-4-UNEXPECTED Unexpected: [chars]: [chars]: [hex]

Explanation    An unexpected condition encountered. This is not necessarily an error, but may help with debugging other problems elsewhere!

Recommended Action    Collect system log information. No action is required.

Error Message     
 
    
    
   

%HA-LRD_inv-6-RESET_CARD_FOR_PAIRING LRd has reset the DRP '[dec]' to accomodate new pairing configuration.

Explanation    The DRP pairing configuration was changed. The card entering or leaving the pair needs to be reset in order to accomodate the new configuration.

Recommended Action    None.

Error Message     
 
    
    
   

%HA-LRD_inv-6-RESET_CARD_LR_CHANGE LRd has reset the card in slot '[dec]' because it was assigned to a new LR.

Explanation    The DRP pairing configuration was changed. The card entering or leaving the pair needs to be reset in order to accomodate the new configuration.

Recommended Action    None.

PSARB Messages

Error Message     
 
    
    
   

%HA-PSARB-1-WRONG_SLOT Rebooting RP in slot [dec] because it conflicts with an already operational RP in slot [dec].

Explanation    Card pairing requires primary/standby cards in specific slots and active RP's need to be in seperate LR's. Adjacency is defined by RP pairing rules (e.g. 0-1, 2-3, 4-5, 6-7). If it's intended to use the conflicting RP as a standby partner, please move the RP adjacent to the active. Or, if the RP is meant to be used in another logical router, please ensure it is assigned to the other LR. %d - indicates the wrong slot number the RP is inserted %d - indicates the slot number of the operational RP

Recommended Action    Move standby RP card to correct slot in chassis, or assign to distinct LR.

Error Message     
 
    
    
   

%HA-PSARB-2-MSG_HEARTBEAT_LOST Slot [dec] heartbeat lost. Resetting card.

Explanation    The active RP has lost the heartbeat of the indicated slot. This error happens after a certain number of messages are lost between the active and the indicated card. %d - indicates the slot number of the card experiencing the problem.

Recommended Action    The system will automatically reset the card. If this error repeatedly occurs, try to shut down the card by configuring 'hw-module location shutdown' in admin mode. 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.

Error Message     
 
    
    
   

%HA-PSARB-3-INIT_ERR Process initialization failed: ([chars]%s)

Explanation    The psarb process failed to initialize. This process is responsible for providing a high level of availability on the GSR router by having a pair of active and standby RPs in the system. When an active RP fails, another RP can take over the functionality of the failed RP. %s - indicates the reason for the failure. %s - the decoded error reason.

Recommended Action    The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. 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.

Error Message     
 
    
    
   

%HA-PSARB-3-TWO_PRIMARY_DETECTED Two primary RPs detected (message from slot [dec])

Explanation    There appear to be two PRIMARY RP's in the system. This is due to messaging error when the other RP didn't receive the BID message. %d indicates the primary slot number displaying the message

Recommended Action    The two primary RPs will be automatically reset.

Error Message     
 
    
    
   

%HA-PSARB-4-PARTNER_NOT_IN_LR This node's partner (slot [dec]) is in a different LR. The standby node will be reset.

Explanation    Adjacent RPs must be in the same LR unless if they are both to be booted with an RP image. It is, however, permissable to boot a DRP in one of these slots. Adjacency is defined by RP pairing rules (e.g. 0-1, 2-3, 4-5, 6-7). %d - indicates the slot number of the partner RP

Recommended Action    Do not boot RP images in adjacent slots when they are in different LRs. Adjacency is defined by RP pairing rules (e.g. 0-1, 2-3, 4-5, 6-7).

Error Message     
 
    
    
   

%HA-PSARB-5-IOS_RP_DETECTED Detected an RP in slot [dec] is running IOS. Configured it as IOS non-participant.

Explanation    PSARB sends an mbus message to all RP running IOS on the chassis, to configure the RP as an IOS non-participant router, therefore, does not interfere with IOX running on this RP. %d - indicates the slot number of the RP that is running IOS on the chassis

Recommended Action    Power up the RP that is running IOS with an IOX image. If not, shut down the RP using 'hw-module location shutdown' in admin mode.

Error Message     
 
    
    
   

%HA-PSARB-6-GO_ACTIVE Card is going active.

Explanation    When an RP initially boots up, it can take the active role if no other active RP is present. Also a failure on active or a force switch over could cause the standby RP to change state to active. This message is displayed when the PRP card is going active.

Recommended Action    This is an informational message only.

Error Message     
 
    
    
   

%HA-PSARB-6-GO_STANDBY Card is going standby.

Explanation    When an RP initially boots up, it can take the standby role if an active RP is present. Also a failure on active or a force switch over causes the active RP to change state to standby. This message is displayed when the RP card is going standby.

Recommended Action    This is an informational message only.

Error Message     
 
    
    
   

%HA-PSARB-6-ROLE_LOCKED (slot [dec]) failover prevented - card role is locked

Explanation    The role of this card has been locked - failover was prevented. %d - indicates the slot number of the PRP which it's role is locked

Recommended Action    No action is required.

PSARBLC Messages

Error Message     
 
    
    
   

%HA-PSARBLC-3-INIT_ERR Process initialization failed: ([chars]%s)

Explanation    The psarb-lc process failed to initialize. This process is responsible for monitoring the arbitration messages between the primary and standby RPs and determining which slot contains the primary RP. %s - indicates the reason for the failure. %s - the decoded error reason.

Recommended Action    The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. 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.

Error Message     
 
    
    
   

%HA-PSARBLC-3-SELF_RESET_DLRSC_DOWN Resetting myself ([dec]), as DLRSC ([dec]) is not present anymore in my LR.

Explanation    PSARB knows when a DLRSC (primary RP) in its LR is down and there is no backup DLRSC (secondary RP). PSARB then needs to reset itself as the LR is headless.

Recommended Action    Bringup the DLRSC that has gone down in this LR. 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.