2003-05-04
This MIB allows management of redundancy of CPU and switch cards for the Catalyst 8540 switch, and other products with similar implementations. The Catalyst 8540 is an ATM switch. It has 13 (or, in some models, 14) slots, of which 2 slots can hold CPU cards, and 3 (or, in some models, 4) slots can hold switch cards. A switch card is one that contains the ATM switching fabric. Two switch cards are combined to operate in 20Gbps switching mode. For CPU cards, 1+1 redundancy is supported. For switch cards, 2+1 redundancy is supported.
Download CISCO-C8500-REDUNDANCY-MIB.txt Open CISCO-C8500-REDUNDANCY-MIB.txt in a new tab
SCALARS (11) · TABLES (2) · TRAPS (3)
| Name | OID |
|---|---|
| ccrCpuTable | 1.3.6.1.4.1.9.9.105.1.1.1 |
| ccrSwitchTable | 1.3.6.1.4.1.9.9.105.1.2.1 |
| Name | OID |
|---|---|
| ccrCpuStatusChange | 1.3.6.1.4.1.9.9.105.2.0.1 |
| ccrSwitchStatusChange | 1.3.6.1.4.1.9.9.105.2.0.2 |
| ccrSwitchModeChange | 1.3.6.1.4.1.9.9.105.2.0.3 |
END OF TOC
1.3.6.1.4.1.9.9.105.1.1.2
BITS
The device's running-configuration and startup-configuration both reside on the active CPU card. This object indicates whether these configurations should be copied from the active CPU to the standby CPU whenever they change. It is acceptable to copy either, both, or neither.
1.3.6.1.4.1.9.9.105.1.1.3
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This object is used to allow or disallow the execution of the enable exec command on the secondary CPU. When set to 'true', the enable exec command can be executed on secondary CPU, and the user may enter enable mode after keying in the password configured. When set to 'false', the enable exec command cannot be executed; thus, no user may enter enabled mode.
1.3.6.1.4.1.9.9.105.1.1.4
INTEGER (0..65535) · Integer32 · seconds
The time taken for the most recent CPU switchover.
1.3.6.1.4.1.9.9.105.1.1.5
INTEGER1 = forcesync2 = noop · Integer32
This object is used to force the synchronization of counters from primary CPU to secondary CPU. It should generally be set just before a controlled Route Processor Switchover. When this object is retrieved, the value 'noop' is returned. When this object is set to 'noop' no operation is performed.
1.3.6.1.4.1.9.9.105.1.1.6
INTEGER (0..1440) · Integer32 · minutes
This object configures the periodicity of interface counter synchronization from primary CPU to secondary CPU. Setting this object to 0 will disable counter synchronization.
1.3.6.1.4.1.9.9.105.1.1.7
INTEGER (0..1440) · Integer32 · minutes
This object configures the periodicity of Virtual Circuit (VC) counter synchronization from primary CPU to secondary CPU. Setting this object to 0 will disable counter synchronization.
1.3.6.1.4.1.9.9.105.1.1.8
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
This object configures the synchronization of ATM Signalling Statistics from primary CPU to secondary CPU. When this object is set to 'true', sychronization is enabled. When this object is set to 'false', synchronization is disabled.
1.3.6.1.4.1.9.9.105.1.2.2
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of sysUpTime at the last switchover of the switch cards. The value is zero if there was no switchover since agent initialization.
1.3.6.1.4.1.9.9.105.1.2.3
INTEGER1 = none2 = notKnown3 = userInitiated4 = cardFailed5 = cardRecovered6 = cardRemoved7 = cardInserted · Integer32
The reason for the last switch card switchover. The value is none(1) if there was no switchover since agent initialization.
1.3.6.1.4.1.9.9.105.1.2.4
INTEGER1 = tenGbps2 = twentyGbps · Integer32
The switching capacity (i.e., bandwidth) of the switch fabric. tenGbps(1) - 10 Gigabits/sec twentyGbps(2) - 20 Gigabits/sec.
1.3.6.1.4.1.9.9.105.1.2.5
INTEGER1 = tenGbps2 = twentyGbps · Integer32
The desired switching capacity (i.e., bandwidth) of the switch fabric. tenGbps(1) - 10 Gigabits/sec twentyGbps(2) - 20 Gigabits/sec If the value configured by writing to this object is supported by the device, it will be applied at the next reboot. The speed at which the switch fabric is currently operating is reflected by the value of ccrSwitchBw.
1.3.6.1.4.1.9.9.105.1.1.1
Index: ccrCpuSlotIndex
There is an entry in this table for each slot that can hold a CPU card.
1.3.6.1.4.1.9.9.105.1.1.1.1.1
RedundancySlotIndexA value that identifies a physical slot in the chassis. For a chassis with slots that are numbered left to right, the leftmost slot has value 1. For a chassis with slots that are numbered top to bottom, the topmost slot has value 1. (1..65535) · Unsigned32
Identifies a chassis slot.
1.3.6.1.4.1.9.9.105.1.1.1.1.2
RedundancyMode1 = active2 = standby3 = unused4 = notPresentThe redundancy mode of a card. The redundancy mode of a card is part of the state of the redundancy machine (i.e., the hardware or software that implements redundancy). The redundancy modes of all the cards in a redundancy group together represent the state of the redundancy machine for that redundancy group. The inputs to the redundancy machine that cause the redundancy mode of a card to transition from one value to another are events like card failure, card removal, user configuration, etc. Objects defined using this TC have a MAX-ACCESS of read-write or read-create. This allows a user to force the redundancy machine to transition to a desired state. The following values may be written: active(1) - Make this card an active member of the redundancy group. standby(2) - Make this card a standby member of the redundancy group. unused(3) - Do not use this card. Writing the above values may cause a switchover. When read, the values mean: active(1) - This card is an active member of the redundancy group. standby(2) - This card is a standby member of the redundancy group. unused(3) - This card is not being used at present. notPresent(4) - There is no card in the slot. · Integer32
The redundancy mode of this CPU card.
1.3.6.1.4.1.9.9.105.1.1.1.1.3
RedundancyStatus1 = notPresent2 = ok3 = faultThe operational status of a card. · Integer32
The operational status of this CPU card.
1.3.6.1.4.1.9.9.105.1.2.1
Index: ccrSwitchSlotIndex
There is an entry in this table for each slot that can hold a switch card. A 'switch card' is a card that contains the ATM switch fabric.
1.3.6.1.4.1.9.9.105.1.2.1.1.1
RedundancySlotIndexA value that identifies a physical slot in the chassis. For a chassis with slots that are numbered left to right, the leftmost slot has value 1. For a chassis with slots that are numbered top to bottom, the topmost slot has value 1. (1..65535) · Unsigned32
Identifies a chassis slot.
1.3.6.1.4.1.9.9.105.1.2.1.1.2
RedundancyMode1 = active2 = standby3 = unused4 = notPresentThe redundancy mode of a card. The redundancy mode of a card is part of the state of the redundancy machine (i.e., the hardware or software that implements redundancy). The redundancy modes of all the cards in a redundancy group together represent the state of the redundancy machine for that redundancy group. The inputs to the redundancy machine that cause the redundancy mode of a card to transition from one value to another are events like card failure, card removal, user configuration, etc. Objects defined using this TC have a MAX-ACCESS of read-write or read-create. This allows a user to force the redundancy machine to transition to a desired state. The following values may be written: active(1) - Make this card an active member of the redundancy group. standby(2) - Make this card a standby member of the redundancy group. unused(3) - Do not use this card. Writing the above values may cause a switchover. When read, the values mean: active(1) - This card is an active member of the redundancy group. standby(2) - This card is a standby member of the redundancy group. unused(3) - This card is not being used at present. notPresent(4) - There is no card in the slot. · Integer32
The redundancy mode of this switch card.
1.3.6.1.4.1.9.9.105.1.2.1.1.3
RedundancyStatus1 = notPresent2 = ok3 = faultThe operational status of a card. · Integer32
The operational status of this switch card.
1.3.6.1.4.1.9.9.105.2.0.1
This notification is generated when the value of ccrCpuStatus changes for a CPU card. The varbind indicates the current status of the affected card.
1.3.6.1.4.1.9.9.105.1.1.1.1.3
RedundancyStatus1 = notPresent2 = ok3 = faultThe operational status of a card. · Integer32
The operational status of this CPU card.
1.3.6.1.4.1.9.9.105.2.0.2
This notification is generated when the value of ccrSwitchStatus changes for a switch card. The varbind indicates the current status of the affected card.
1.3.6.1.4.1.9.9.105.1.2.1.1.3
RedundancyStatus1 = notPresent2 = ok3 = faultThe operational status of a card. · Integer32
The operational status of this switch card.
1.3.6.1.4.1.9.9.105.2.0.3
This notification is generated when the value of ccrSwitchMode changes from active(1) to either standby(2) or unused(3) or notPresent(4). The varbind indicates the current mode of the affected card.
1.3.6.1.4.1.9.9.105.1.2.1.1.2
RedundancyMode1 = active2 = standby3 = unused4 = notPresentThe redundancy mode of a card. The redundancy mode of a card is part of the state of the redundancy machine (i.e., the hardware or software that implements redundancy). The redundancy modes of all the cards in a redundancy group together represent the state of the redundancy machine for that redundancy group. The inputs to the redundancy machine that cause the redundancy mode of a card to transition from one value to another are events like card failure, card removal, user configuration, etc. Objects defined using this TC have a MAX-ACCESS of read-write or read-create. This allows a user to force the redundancy machine to transition to a desired state. The following values may be written: active(1) - Make this card an active member of the redundancy group. standby(2) - Make this card a standby member of the redundancy group. unused(3) - Do not use this card. Writing the above values may cause a switchover. When read, the values mean: active(1) - This card is an active member of the redundancy group. standby(2) - This card is a standby member of the redundancy group. unused(3) - This card is not being used at present. notPresent(4) - There is no card in the slot. · Integer32
The redundancy mode of this switch card.