This object holds the status of a card in a particular shelf-slot.
The possible values are :
nocard(1) : card not present.
standby(2) : card in standby state. The card is in ready state
and will be ready to take over the service if
the corresponding active card(redundant)
fails.
active(3) : card in active state. The card is providing
the service.
failed(4) : card in failed state. The card can come out
of this state only after user intervention
(Reset or running some CLI commands).
selfTest(5) : online diagnostics is being run in card.
heldInReset(6) : The card configuration is being cleared.
No requests can be serviced.
boot(7) : card in boot state.
mismatch(8) : card is not compatible with the current
configuration. Card was correctly provisioned
earlier, however the card was replaced by
an incompatible card. This state can be
resolved by clearing the configuration, or
replacing with the appropriate card.
unknown(9) : could not determine the state
coreCardMisMatch(10) : Controller Card(PXM/ASC etc)
and SRM(Service Resource Module)
combination does not match.
blocked(11) : In case of 1:N redundancy configuration
the secondary card(backup card) is covering
one of the primary card and can not cover
any other card in the group if there is a failure.
Redundancy is blocked.
hold(13) : The standby controller card assumes the hold
state during PXM upgrades. In this state,
the standby PXM will be running a different
software but will be receiving all standby
updates(BRAM and Database). This state is
applicable only for MGX8250 Platform.
notResponding(14): Response from the Service Module has become
slow probably due to overloading of CPU.
No recovery action is required on user part.
At present, this state is applicable only
for Router Blade(RPM).
cardinit(17) : When the physical presence of card has been
detected but the communication hasn't yet
been established between the controller card
(PXM) and Service Module.
Parsed from file BASIS-GENERIC-MIB.mib
Module: BASIS-GENERIC-MIB
This object holds the status of a card in a particular shelf-slot.
The possible values are :
nocard(1) : card not present.
standby(2) : card in standby state. The card is in ready state
and will be ready to take over the service if
the corresponding active card(redundant)
fails.
active(3) : card in active state. The card is providing
the service.
failed(4) : card in failed state. The card can come out
of this state only after user intervention
(Reset or running some CLI commands).
selfTest(5) : online diagnostics is being run in card.
heldInReset(6) : The card configuration is being cleared.
No requests can be serviced.
boot(7) : card in boot state.
mismatch(8) : card is not compatible with the current
configuration. Card was correctly provisioned
earlier, however the card was replaced by
an incompatible card. This state can be
resolved by clearing the configuration, or
replacing with the appropriate card.
unknown(9) : could not determine the state
coreCardMisMatch(10) : Controller Card(PXM/ASC etc)
and SRM(Service Resource Module)
combination does not match.
blocked(11) : In case of 1:N redundancy configuration
the secondary card(backup card) is covering
one of the primary card and can not cover
any other card in the group if there is a failure.
Redundancy is blocked.
hold(13) : The standby controller card assumes the hold
state during PXM upgrades. In this state,
the standby PXM will be running a different
software but will be receiving all standby
updates(BRAM and Database). This state is
applicable only for MGX8250 Platform.
notResponding(14): Response from the Service Module has become
slow probably due to overloading of CPU.
No recovery action is required on user part.
At present, this state is applicable only
for Router Blade(RPM).
cardinit(17) : When the physical presence of card has been
detected but the communication hasn't yet
been established between the controller card
(PXM) and Service Module.
This object holds the status of a card in a particular shelf-slot.
The possible values are :
nocard(1) : card not present.
standby(2) : card in standby state. The card is in ready state
and will be ready to take over the service if
the corresponding active card(redundant)
fails.
active(3) : card in active state. The card is providing
the service.
failed(4) : card in failed state. The card can come out
of this state only after user intervention
(Reset or running some CLI commands).
selfTest(5) : online diagnostics is being run in card.
heldInReset(6) : The card configuration is being cleared.
No requests can be serviced.
boot(7) : card in boot state.
mismatch(8) : card is not compatible with the current
configuration. Card was correctly provisioned
earlier, however the card was replaced by
an incompatible card. This state can be
resolved by clearing the configuration, or
replacing with the appropriate card.
unknown(9) : could not determine the state
coreCardMisMatch(10) : Controller Card(PXM/ASC etc)
and SRM(Service Resource Module)
combination does not match.
blocked(11) : In case of 1:N redundancy configuration
the secondary card(backup card) is covering
one of the primary card and can not cover
any other card in the group if there is a failure.
Redundancy is blocked.
hold(13) : The standby controller card assumes the hold
state during PXM upgrades. In this state,
the standby PXM will be running a different
software but will be receiving all standby
updates(BRAM and Database). This state is
applicable only for MGX8250 Platform.
notResponding(14): Response from the Service Module has become
slow probably due to overloading of CPU.
No recovery action is required on user part.
At present, this state is applicable only
for Router Blade(RPM).
cardinit(17) : When the physical presence of card has been
detected but the communication hasn't yet
been established between the controller card
(PXM) and Service Module.
Parsed from file BASIS-GENERIC-MIB.my.txt
Company: None
Module: BASIS-GENERIC-MIB
This object holds the status of a card in a particular shelf-slot.
The possible values are :
nocard(1) : card not present.
standby(2) : card in standby state. The card is in ready state
and will be ready to take over the service if
the corresponding active card(redundant)
fails.
active(3) : card in active state. The card is providing
the service.
failed(4) : card in failed state. The card can come out
of this state only after user intervention
(Reset or running some CLI commands).
selfTest(5) : online diagnostics is being run in card.
heldInReset(6) : The card configuration is being cleared.
No requests can be serviced.
boot(7) : card in boot state.
mismatch(8) : card is not compatible with the current
configuration. Card was correctly provisioned
earlier, however the card was replaced by
an incompatible card. This state can be
resolved by clearing the configuration, or
replacing with the appropriate card.
unknown(9) : could not determine the state
coreCardMisMatch(10) : Controller Card(PXM/ASC etc)
and SRM(Service Resource Module)
combination does not match.
blocked(11) : In case of 1:N redundancy configuration
the secondary card(backup card) is covering
one of the primary card and can not cover
any other card in the group if there is a failure.
Redundancy is blocked.
hold(13) : The standby controller card assumes the hold
state during PXM upgrades. In this state,
the standby PXM will be running a different
software but will be receiving all standby
updates(BRAM and Database). This state is
applicable only for MGX8250 Platform.
notResponding(14): Response from the Service Module has become
slow probably due to overloading of CPU.
No recovery action is required on user part.
At present, this state is applicable only
for Router Blade(RPM).
cardinit(17) : When the physical presence of card has been
detected but the communication hasn't yet
been established between the controller card
(PXM) and Service Module.
functionModuleState OBJECT-TYPE SYNTAX INTEGER{ nocard (1), standby (2), active (3), failed (4), selfTest (5), heldInReset (6), boot (7), mismatch (8), unknown (9), coreCardMisMatch (10), blocked (11), reserved (12), hold (13), notResponding (14), cardinit (17) } ACCESS read-only STATUS mandatory DESCRIPTION "This object holds the status of a card in a particular shelf-slot. The possible values are : nocard(1) : card not present. standby(2) : card in standby state. The card is in ready state and will be ready to take over the service if the corresponding active card(redundant) fails. active(3) : card in active state. The card is providing the service. failed(4) : card in failed state. The card can come out of this state only after user intervention (Reset or running some CLI commands). selfTest(5) : online diagnostics is being run in card. heldInReset(6) : The card configuration is being cleared. No requests can be serviced. boot(7) : card in boot state. mismatch(8) : card is not compatible with the current configuration. Card was correctly provisioned earlier, however the card was replaced by an incompatible card. This state can be resolved by clearing the configuration, or replacing with the appropriate card. unknown(9) : could not determine the state coreCardMisMatch(10) : Controller Card(PXM/ASC etc) and SRM(Service Resource Module) combination does not match. blocked(11) : In case of 1:N redundancy configuration the secondary card(backup card) is covering one of the primary card and can not cover any other card in the group if there is a failure. Redundancy is blocked. hold(13) : The standby controller card assumes the hold state during PXM upgrades. In this state, the standby PXM will be running a different software but will be receiving all standby updates(BRAM and Database). This state is applicable only for MGX8250 Platform. notResponding(14): Response from the Service Module has become slow probably due to overloading of CPU. No recovery action is required on user part. At present, this state is applicable only for Router Blade(RPM). cardinit(17) : When the physical presence of card has been detected but the communication hasn't yet been established between the controller card (PXM) and Service Module. " ::= { cardInformation 7 }
functionModuleState OBJECT-TYPE SYNTAX INTEGER { nocard(1), standby(2), active(3), failed(4), selfTest(5), heldInReset(6), boot(7), mismatch(8), unknown(9), coreCardMisMatch(10), blocked(11), reserved(12), hold(13), notResponding(14), cardinit(17) } ACCESS read-only STATUS mandatory DESCRIPTION "This object holds the status of a card in a particular shelf-slot. The possible values are : nocard(1) : card not present. standby(2) : card in standby state. The card is in ready state and will be ready to take over the service if the corresponding active card(redundant) fails. active(3) : card in active state. The card is providing the service. failed(4) : card in failed state. The card can come out of this state only after user intervention (Reset or running some CLI commands). selfTest(5) : online diagnostics is being run in card. heldInReset(6) : The card configuration is being cleared. No requests can be serviced. boot(7) : card in boot state. mismatch(8) : card is not compatible with the current configuration. Card was correctly provisioned earlier, however the card was replaced by an incompatible card. This state can be resolved by clearing the configuration, or replacing with the appropriate card. unknown(9) : could not determine the state coreCardMisMatch(10) : Controller Card(PXM/ASC etc) and SRM(Service Resource Module) combination does not match. blocked(11) : In case of 1:N redundancy configuration the secondary card(backup card) is covering one of the primary card and can not cover any other card in the group if there is a failure. Redundancy is blocked. hold(13) : The standby controller card assumes the hold state during PXM upgrades. In this state, the standby PXM will be running a different software but will be receiving all standby updates(BRAM and Database). This state is applicable only for MGX8250 Platform. notResponding(14): Response from the Service Module has become slow probably due to overloading of CPU. No recovery action is required on user part. At present, this state is applicable only for Router Blade(RPM). cardinit(17) : When the physical presence of card has been detected but the communication hasn't yet been established between the controller card (PXM) and Service Module." ::= { cardInformation 7 }
Vendor: Stratacom
Module: BASIS-GENERIC-MIB
[Automatically extracted from oidview.com]
functionModuleState OBJECT-TYPE SYNTAX INTEGER{ nocard (1), standby (2), active (3), failed (4), selfTest (5), heldInReset (6), boot (7), mismatch (8), unknown (9), coreCardMisMatch (10), blocked (11), reserved (12), hold (13), notResponding (14), cardinit (17) } ACCESS read-only STATUS mandatory DESCRIPTION "This object holds the status of a card in a particular shelf-slot. The possible values are : nocard(1) : card not present. standby(2) : card in standby state. The card is in ready state and will be ready to take over the service if the corresponding active card(redundant) fails. active(3) : card in active state. The card is providing the service. failed(4) : card in failed state. The card can come out of this state only after user intervention (Reset or running some CLI commands). selfTest(5) : online diagnostics is being run in card. heldInReset(6) : The card configuration is being cleared. No requests can be serviced. boot(7) : card in boot state. mismatch(8) : card is not compatible with the current configuration. Card was correctly provisioned earlier, however the card was replaced by an incompatible card. This state can be resolved by clearing the configuration, or replacing with the appropriate card. unknown(9) : could not determine the state coreCardMisMatch(10) : Controller Card(PXM/ASC etc) and SRM(Service Resource Module) combination does not match. blocked(11) : In case of 1:N redundancy configuration the secondary card(backup card) is covering one of the primary card and can not cover any other card in the group if there is a failure. Redundancy is blocked. hold(13) : The standby controller card assumes the hold state during PXM upgrades. In this state, the standby PXM will be running a different software but will be receiving all standby updates(BRAM and Database). This state is applicable only for MGX8250 Platform. notResponding(14): Response from the Service Module has become slow probably due to overloading of CPU. No recovery action is required on user part. At present, this state is applicable only for Router Blade(RPM). cardinit(17) : When the physical presence of card has been detected but the communication hasn't yet been established between the controller card (PXM) and Service Module. " ::= { cardInformation 7 }
functionModuleState OBJECT-TYPE SYNTAX INTEGER{ nocard (1), standby (2), active (3), failed (4), selfTest (5), heldInReset (6), boot (7), mismatch (8), unknown (9), coreCardMisMatch (10), blocked (11), reserved (12), hold (13), notResponding (14), cardinit (17) } ACCESS read-only STATUS mandatory DESCRIPTION "This object holds the status of a card in a particular shelf-slot. The possible values are : nocard(1) : card not present. standby(2) : card in standby state. The card is in ready state and will be ready to take over the service if the corresponding active card(redundant) fails. active(3) : card in active state. The card is providing the service. failed(4) : card in failed state. The card can come out of this state only after user intervention (Reset or running some CLI commands). selfTest(5) : online diagnostics is being run in card. heldInReset(6) : The card configuration is being cleared. No requests can be serviced. boot(7) : card in boot state. mismatch(8) : card is not compatible with the current configuration. Card was correctly provisioned earlier, however the card was replaced by an incompatible card. This state can be resolved by clearing the configuration, or replacing with the appropriate card. unknown(9) : could not determine the state coreCardMisMatch(10) : Controller Card(PXM/ASC etc) and SRM(Service Resource Module) combination does not match. blocked(11) : In case of 1:N redundancy configuration the secondary card(backup card) is covering one of the primary card and can not cover any other card in the group if there is a failure. Redundancy is blocked. hold(13) : The standby controller card assumes the hold state during PXM upgrades. In this state, the standby PXM will be running a different software but will be receiving all standby updates(BRAM and Database). This state is applicable only for MGX8250 Platform. notResponding(14): Response from the Service Module has become slow probably due to overloading of CPU. No recovery action is required on user part. At present, this state is applicable only for Router Blade(RPM). cardinit(17) : When the physical presence of card has been detected but the communication hasn't yet been established between the controller card (PXM) and Service Module. " ::= { cardInformation 7 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.351.110.2.1.7.0 | functionModuleState | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.351.110.2.1.1 | moduleSlotNumber | 1 | 1 | Slot number this card is present |
| 1.3.6.1.4.1.351.110.2.1.2 | functionModuleType | 1 | 1 | This object holds the type of the card. The card can type is for Processor module as well as service module. |
| 1.3.6.1.4.1.351.110.2.1.3 | functionModuleDescription | 1 | 1 | Describes the card |
| 1.3.6.1.4.1.351.110.2.1.4 | functionModuleSerialNum | 1 | 1 | Serial number of the function Module. |
| 1.3.6.1.4.1.351.110.2.1.5 | functionModuleHWRev | 1 | 1 | Hardware revision number for function Module. |
| 1.3.6.1.4.1.351.110.2.1.6 | functionModuleFWRev | 1 | 1 | Firmware revision number of the function Module. |
| 1.3.6.1.4.1.351.110.2.1.8 | functionModuleResetReason | 1 | 1 | Last reason for card to reset. The possible values are : powerUp(1) : power up parityError(2) : parity error watchDog(3) … |
| 1.3.6.1.4.1.351.110.2.1.9 | lineModuleType | 1 | 1 | This object contains the Line Module(back card) type. Physically it is behind the backplane, normally with connectors for physica… |
| 1.3.6.1.4.1.351.110.2.1.10 | lineModuleDescription | 1 | 1 | This object contains description of the line module. |
| 1.3.6.1.4.1.351.110.2.1.11 | lineModuleSerialNum | 1 | 1 | This object contains Serial number of the line module. |
| 1.3.6.1.4.1.351.110.2.1.12 | lineModuleHWRev | 1 | 1 | This object contains Hardware revision for line module. |
| 1.3.6.1.4.1.351.110.2.1.13 | lineModuleFWRev | 1 | 1 | Firmware revision for line module. The current version does not have any firmware, hence will always contains zero length octet st… |
| 1.3.6.1.4.1.351.110.2.1.14 | lineModuleState | 1 | 1 | line module status. |
| 1.3.6.1.4.1.351.110.2.1.15 | moduleTrapAlarmSeverity | 1 | 1 | This object is sent to managers as part of all Trap PDUs, to determine the module alarm severity. An implementation may not suppo… |
| 1.3.6.1.4.1.351.110.2.1.16 | mibVersionNumber | 1 | 1 | MIB version number. Updated when any part of the MIB changes. |
| 1.3.6.1.4.1.351.110.2.1.17 | configChangeTypeBitMap | 1 | 1 | Configuration change Type BitMap bit 0 set = Card Configuration Change bit 1 set = Line Configuration Change bit 2 set = Port Conf… |
| 1.3.6.1.4.1.351.110.2.1.18 | configChangeObjectIndex | 1 | 1 | Configuration change object index, could be line number or port number or channel number depends on the type bitmap, for port res… |
| 1.3.6.1.4.1.351.110.2.1.19 | configChangeStatus | 1 | 1 | This object is applicable only for traps. The SNMP operation may not be meaningful. The value contained in this object is same as… |
| 1.3.6.1.4.1.351.110.2.1.20 | cardIntegratedAlarmBitMap | 1 | 1 | Bit position represents the different types of alarm for ASC: bit 0: ShelfFunctionModuleState (BNM only) (failed/boot/mismatch/hel… |
| 1.3.6.1.4.1.351.110.2.1.21 | cleiCode | 1 | 1 | Common Language Equipment(CLEI) Code. |
| 1.3.6.1.4.1.351.110.2.1.22 | macAddress | 1 | 1 | Ethernet address (base address) stored in NVRAM, entered by manfacturing. |
| 1.3.6.1.4.1.351.110.2.1.23 | macAddrBlkSize | 1 | 1 | The MAC address block size, entered by manufacturing. |
| 1.3.6.1.4.1.351.110.2.1.24 | finalTestTechnician | 1 | 1 | The Final Test Technician Employee Identification Number. |
| 1.3.6.1.4.1.351.110.2.1.25 | hwFailures | 1 | 1 | Hardware failure code. |
| 1.3.6.1.4.1.351.110.2.1.26 | hwHistory | 1 | 1 | RMA Test History - RMA Failure Code. |
| 1.3.6.1.4.1.351.110.2.1.27 | secLineModuleType | 1 | 1 | This object contains the type of secondary line module(back card). Physically it is the bottom card behind the backplane. Normally… |
| 1.3.6.1.4.1.351.110.2.1.28 | secLineModuleDescription | 1 | 1 | Description of the Secondary line module. This Object is applicable only to selected MGX switches. |
| 1.3.6.1.4.1.351.110.2.1.29 | secLineModuleSerialNum | 1 | 1 | Serial number of the secondary(bottom) line module. This object is applicable only to selected MGX switches. |
| 1.3.6.1.4.1.351.110.2.1.30 | secLineModuleHWRev | 1 | 1 | Hardware revision for secondary (bottom) line module This object is applicable only to selected MGX switches. |
| 1.3.6.1.4.1.351.110.2.1.31 | secLineModuleFWRev | 1 | 1 | Firmware revision for Secondary line module This object is applicable only to selected MGX switches. If there is no Firmware revi… |
| 1.3.6.1.4.1.351.110.2.1.32 | secLineModuleState | 1 | 1 | line module status of secondary (bottom) back card. This object is applicable only to selected MGX switches. |
| 1.3.6.1.4.1.351.110.2.1.33 | configChangeParentObjectIndex | 1 | 1 | Parent object index, could be - line index - port index This object will indicate the index of the immediate higher level object (l… |
| 1.3.6.1.4.1.351.110.2.1.34 | configChangeGrandParentObjectIndex | 1 | 1 | Grand Parent object index, could be - line index This object will indicate the index of the immediate higher level object (line) o… |
| 1.3.6.1.4.1.351.110.2.1.35 | configChangeSMSpecificObject | 1 | 1 | configChangeSMSpecificObject is a generic object which is Service Module Specific. It can be used for different purposes in diffe… |
| 1.3.6.1.4.1.351.110.2.1.36 | transId | 1 | 1 | Per card transaction ID. This object is used to keep track of configuration change on the card. The transId will be incremented b… |