ERI-DNX-NEST-SYS-MIB: View SNMP OID List / Download MIB

This trap is used to notify a NMS that a user has updated the configuration for a given slot entry.

This trap is used to notify a NMS that due to an alarm condition or system state change, the N+1 Redundancy Groups have been modified. This means the one or more devices have been removed or added to the actual N+1 Redundancy Groups and this will affect which cards will be protected (switched) in the event of a failure.

This trap is used to notify a NMS that a user has updated the configuration for a given nest entry.

This trap is used to notify a NMS that the system has either started or just completed the Database synchronization process.

A list of the device cards in this node with the static and dynamic type information. The maximum number of entries depends on the number of slots in the system plus 3 default entries for the system manager cards and the Protection Switch.

The conceptual row of the Slot Configuration table. A row in this table can not be created or deleted. A row in this table can be modified by providing valid values for either the Slot Name, Configured Device Type, Device Redundancy, or Slot Command Status. Deleting the Slot Configuration using the Slot Command Status value of 'delete-slot-config' will result in the removal of all configured connections associated with that slot number. The slotConfigCmdStatus field must be included as a variable in a SET PDU for the action to take effect. If the slotConfigCmdStatus is missing from the SET PDU, the GET RESPONSE will contain the SNMP error status of 'genErr' for and an error index equal to the last variable.

The slot number in the node.

This is the slot type configured by the user. The value, slot(0) is the default type for an unconfigured device. If slot(0) is used in a Set Request, the agent will return an error status of 'badValue'. The slot entries representing the System Manager Cards and the Protection Switch device cannot be used in a Set Request since their device type is static.

This is the actual slot type sent back by the card.

The current machine state of the device. not-present (0) Indicates no hardware detected in the slot. online (1) Device is present and is considered primary operational. offline (2) Device is present but currently not operational. disabled (3) Applies to the Protection Switch box if system cannot support redundancy. standby (4) Device is present but considered as secondary. defective (5) Device is present but could not be activated. bus-error (6) Device is present and reporting a bus connection error. out-of-serv (7) Operator has placed device in Out of Service mode.

The current slot device alarm condition level that indicates it's severity. Enumeration: 'critical-level': 4, 'no-alarm': 0, 'minor-level': 1, 'major-level': 2, 'major-minor': 3, 'unknown': 99, 'critical-major-minor': 7, 'critical-minor': 5, 'critical-major': 6.

The user defined name for this slot/device.

The software version release identification number for this device.

The configured N+1 Redundancy state of the device. The slot entries representing the System Manager Cards and the Protection Switch device cannot be used in a Set Request since N+1 Redundancy does not apply to them. disable (0) Device is not configured as part of the Redundancy Group. enable (1) Device is configured as part of the Redundancy Group. n/a (2) Device does not support Redundancy. Enumeration: 'notApplicable': 2, 'enable': 1, 'disable': 0.

The current slot/device miscellaneous state conditions. none (0) no misc condition errors (1) errors reported on device test (2) device is in test mode errors-test (3) errors reported on device while in test mode clockSrc (4) device is the source for the system clock errors-clockSrc (5) device is the source for the system clock and errors found test-clockSrc (6) device is the source for the system clock and is in test mode errors-test-clockSrc (7) device is the source for the system clock and is in test mode and errors were found Enumeration: 'errors-test': 3, 'none': 0, 'errors': 1, 'errors-clockSrc': 5, 'clockSrc': 4, 'errors-test-clockSrc': 7, 'test': 2, 'test-clockSrc': 6.

The command status for this slot configuration row/record. The value used in a SET will be replaced by a response value in the GET RESPONSE indicating success or failure. Default Response State used in GET RESPONSE Command ready-for-command (0) initial default status for a row Slot Device Commands used in SET Command (1..99) update-slot-config (1) change an aspect of current slot configuration delete-slot-config (2) remove existing Slot Configuration. Deleting the Slot Configuration using the Slot Command Status will result in the removal of all configured connections associated with that slot number. ndr-switchover (10) force a switchover to the Standby device ndr-restore (11) force a restore back to the original device Response States used in GET RESPONSE Command (100..199) update-successful (101) slot data has been successfully changed delete-successful (102) slot data has been successfully removed switch-successful (110) Slot N+1 Redundancy device has been successfully switched over to Standby device restore-successful (111) Slot N+1 Redundancy device has been successfully restored back to Primary device Slot Config Error Codes used in GET RESPONSE Command (200..799) err-general-slot-config-error (200) Unknown slot configuration error occurred. err-invalid-slot-type (201) Configured slot type not in valid range err-invalid-slot-command (202) Unrecognized slot command-action err-invalid-slot-name (203) Configured slot name too long err-redundancy-disabled (204) Redundancy disabled on this system or does not apply to device type err-cannot-chg-sys-device (205) System Device type does not support configuration change err-invalid-redundancy-state (207) Redundancy state does not apply or invalid err-cannot-delete-online-device (208) Device cannot be present when deleting configuration err-data-locked-by-another-user (450) Another administrative user is making changes to this part of the system via a terminal session. Check Event Log for user name err-snmp-parse-failed (500) Agent could not parse variable err-invalid-snmp-type (501) Variable ASN type does not match Agent defined type err-invalid-snmp-var-size (502) Variable size is too big Enumeration: 'err-invalid-slot-command': 202, 'err-invalid-snmp-type': 501, 'err-general-slot-config-error': 200, 'delete-slot-config': 2, 'err-invalid-slot-type': 201, 'err-invalid-slot-name': 203, 'err-snmp-parse-failed': 500, 'err-invalid-redundancy-state': 207, 'switch-successful': 110, 'err-data-locked-by-another-user': 450, 'err-cannot-chg-sys-device': 205, 'err-invalid-snmp-var-size': 502, 'restore-successful': 111, 'err-redundancy-disabled': 204, 'ndr-restore': 11, 'update-successful': 101, 'ndr-switchover': 10, 'ready-for-command': 0, 'update-slot-config': 1, 'delete-successful': 102, 'err-cannot-delete-online-device': 208.

This is the number of slots in the node.

In the form Release x.xx where x.xx is the release number.

Indicates the system's capability of supporting the N+1 Device Redundancy functionality. The user should configure this variable based on the existence of the Protection Switch Box (PSX) Device. The ndrState will reflect the actual status of N+1 Redundancy. no (0) No PSX attached, N+1 Redundancy disabled. yes (1) PSX attached, N+1 Redundancy enabled.

This is the current N+1 Device Redundancy state. disabled (1) N+1 Redundancy disabled by the user. frozen (2) N+1 Redundancy is not active due to missing hardware components. delayed (3) N+1 Redundancy is delayed due to switchover. enabled (4) N+1 Redundancy enabled and ready. Enumeration: 'disabled': 1, 'frozen': 2, 'enabled': 4, 'delayed': 3.

Indicates the user's desired N+1 Device Redundancy automatic Switchover setting when a primary card fails. manual (0) Failed cards will not be switched automatically by the system. User is required to go to Node Summary Console screen and force a manual switchover of the failed card to the Redundant. automatic (1) The system will automatically switch out failed cards for either NDR Group with the Redundant card. narrowband-auto (2) The system will automatically switch out a failed card for the NDR Narrowband Group with the Redundant. broadband-1-auto(3) The system will automatically switch out a failed card for the NDR Broadband Group 1 with the Redundant. broadband-2-auto(4) The system will automatically switch out a failed card for the NDR Broadband Group 2 with the Redundant. Enumeration: 'broadband-2-auto': 4, 'automatic': 1, 'narrowband-auto': 2, 'manual': 0, 'broadband-1-auto': 3.

Indicates the system's N+1 Device Redundancy automatic Restore setting when a protected card becomes operational. manual (0) Protected cards that become operational will not be restored automatically by the system. User is required to go to Node Summary Console screen and force a manual switchover of the Redundant card back to the Primary card. automatic (1) The system will automatically restore protected cards that become operational for either NDR Group. narrowband-auto (2) The system will automatically restore protected cards that become operational for the NDR Narrowband Group. broadband-1-auto(3) The system will automatically restore protected cards that become operational for the NDR Broadband Group 1. broadband-2-auto(4) The system will automatically restore protected cards that become operational for the NDR Broadband Group 2. Enumeration: 'broadband-2-auto': 4, 'automatic': 1, 'narrowband-auto': 2, 'manual': 0, 'broadband-1-auto': 3.

This is a 2 byte bit field reflecting the slots that are part of the current active NDR Broadband Group 1. The first 11 bits represent each of the slot numbers. If any of the bits are set, those slots are currently part of the Group 1 N+1 Redundancy Group.

This is a 2 byte bit field reflecting the slots that are part of the current active NDR Narrowband Group. The first 11 bits represent each of the slot numbers. If any of the bits are set, those slots are currently part of the Narrowband N+1 Redundancy Group.

This is a slot number that indicates which device card from the active NDR Broadband Group 1 has been currently switched over. Valid Protected slots for NDR Broadband Group1 are 8 through 10. If a zero value is returned, no device card is currently protected.

This is a slot number that indicates which device card from the active NDR Narrowband Group has been currently switched over. Valid Protected slots for NDR Narrowband Group are 2 through 11. If a zero value is returned, no device card is currently protected.

This indicates which type of device is currently occupying the status of active NDR Broadband Group 1. Only one type of broadband device can be supported by N+1 Redundancy at one time. Whichever type is selected as the active Broadband Group 1 type should match the device type of the card in Slot 11, which is the designated Broadband Group 1 NDR Redundant slot. Enumeration: 'sts1': 18, 'hds3': 21, 'ds3': 8, 'e3': 31.

This indicates which type of device is currently occupying the status of active NDR Narrowband Group. Only one type of Narrowband device can be supported by N+1 Redundancy at one time. Whichever type is selected as the active Narrowband type should match the device type of the card in Slot 1, which is the designated Narrowband NDR Redundant slot. Enumeration: 'gr303': 22, 'octalT1E1': 13.

Indicates the system's capability of supporting the N+1 Device Redundancy Dual Broadband Group functionality. The user should configure this variable based on the existence of the Upgraded PSX Hardware. no (0) PSX Dual Broadband Groups disabled or not supported. yes (1) PSX Dual Broadband Groups enabled.

This is a 2 byte bit field reflecting the slots that are part of the current active NDR Broadband Group 2. The first 11 bits represent each of the slot numbers. If any of the bits are set, those slots are currently part of the Group 2 N+1 Redundancy Group.

This is a slot number that indicates which device card from the active NDR Broadband Group 2 has been currently switched over. Valid Protected slots for NDR Broadband Group2 are 1 through 6. If a zero value is returned, no device card is currently protected.

This indicates which type of device is currently occupying the status of active NDR Broadband Group 2. Only one type of broadband device can be supported by N+1 Redundancy at one time. Whichever type is selected as the active Broadband Group 2 type should match the device type of the card in Slot 7, which is the designated Broadband Group 2 NDR Redundant slot. Enumeration: 'sts1': 18, 'hds3': 21, 'ds3': 8, 'e3': 31.

This indicates which type of Protection Switch Chassis Hardware has been detected. In order to run with Dual Broadband Group configuration, this value should be set to psx5300. Enumeration: 'psx5300': 1, 'psx5200': 0.

A Table listing the files one could download from smc to a device card using TFTP

An entry in the Device Download Table

The index of the program file available for download

The name of the program file available for download

The size in bytes of the program file available for download

The load status of the program file Enumeration: 'loadingProgramFile': 1, 'swDownloadNotReady': 3, 'readyForProgramLoad': 2.

The name of the user who initiated the program file download

The number of bytes sent in the current program file download

The slot number to which a program file is to be downloaded

The command to change the load status of the program file, or an error returned from a command. Enumeration: 'err-invalid-snmp-type': 501, 'err-invalid-slot-nbr': 6, 'err-data-locked-by-another-user': 450, 'loadProgramFile': 1, 'err-invalid-nest-nbr': 13, 'loadProgramToAll': 2, 'programFileBusy': 8, 'programFileIdle': 12, 'readyForCommand': 5, 'err-invalid-snmp-var-size': 502, 'noProgramFile': 7, 'slotNotReady': 10, 'noError': 9, 'err-snmp-parse-failed': 500, 'deleteProgramFile': 4, 'err-invalid-command': 414.

The Nest number to which a program file is to be downloaded. If this field is not included in the SET PDU, the file will be downloaded to the specified slot in the First Nest (nest1). Enumeration: 'allNests': 10, 'nest8': 7, 'nest7': 6, 'nest6': 5, 'nest5': 4, 'nest4': 3, 'nest3': 2, 'nest2': 1, 'nest1': 0.

A list of the Configured and Unconfigured Nests in this node with the static and dynamic type information. The maximum number of entries is 8 nests but if this is an Stand-Alone DNX-11 system, only 1 nest entry will be returned.

The conceptual row of the Nest Configuration table. A row in this table can not be created or deleted. A row in this table can be modified by providing valid values for either the Nest Name, Configured Nest Type, NDR Capability, Alarm Contacts, Dual SMCs, Dual XLCs or XCCs, or Nest Command Status. Deleting the Nest Configuration using the Nest Command Status value of 'delete-nest-config' will result in the removal of all configured slots, ports, & connections associated with that nest number. The xNestCmdStatus field must be included as a variable in a SET PDU for the action to take effect. If the xNestCmdStatus is missing from the SET PDU, the GET RESPONSE will contain the SNMP error status of 'genErr' for and an error index equal to the last variable.

The nest index number in the node. Nests are indexed 0 through 7 but correspond to Nests 1 to 8.

The user defined name for this nest.

This is the nest type configured by the user. The value, notConfig(0), is the default type for an unconfigured device. Note, if notConfig(0) or stm1X-oc3X(3) is used in a Set Request, the agent will return an error status of 'badValue'. Virtual stm1X-oc3X Nests are configured automatically by the system whenever the user Assigns an available Nest to an STM1X or OC3X Device pair. This can be done via the opticalDevConfigTable after a STM1X or OC3X card has been configured in a Even numbered slot. Enumeration: 'notConfig': 0, 'dnx4': 1, 'stm1X-oc3X': 3, 'dnx11': 2.

The current machine state of the Nests. mismatch (2) Nest is configured as wrong type. notPresent (8) Nest is unconfigured. missing (12) Nest is configured but communications are down. online (16) Nest is present and operational. offline (32) Nest is present but currently not operational. Enumeration: 'notPresent': 8, 'online': 16, 'mismatch': 2, 'offline': 32, 'missing': 12.

The current nest device alarm condition level that indicates it's severity. Enumeration: 'critical-level': 4, 'no-alarm': 0, 'minor-level': 1, 'major-level': 2, 'major-minor': 3, 'unknown': 99, 'critical-major-minor': 7, 'critical-minor': 5, 'critical-major': 6.

The number of device cards presently active in the nest.

The configured N+1 Redundancy state of the Nest. no (0) N+1 Redundancy is not available in the Nest. yes (1) N+1 Redundancy is available in the Nest.

Determines the type of desired response from the rear SMC/XNM Alarm Contact switches during an alarm event. Enumeration: 'localAudio1': 1, 'localAudio2': 2, 'standard': 0.

The number of SMCs configured for the Nest. If running with only a single SMC, this should be set to 'no' in order to suppress unecessary alarms. no (0) Only 1 SMC resides in the Nest. yes (1) Both SMCs reside in the Nest.

The number of XCC devices configured for the Node Manager or number of XLC devices configured for the Nest Manager depending on Type of Nest. Nest #1 is considered the Node Manager and all other Nests are considered as Nest Managers. If running with only a single XCC or XLC, this should be set to 'no' in order to suppress unecessary alarms. no (0) Only 1 XCC/XLC resides in the Nest. yes (1) Both XCCs/XLCs reside in the Nest.

The command status for this nest configuration row/record. The value used in a SET will be replaced by a response value in the GET RESPONSE indicating success or failure. Default Response State used in GET RESPONSE Command ready-for-command (0) initial default status for a row Nest Device Commands used in SET Command (1..99) update-nest-config (1) change an aspect of current nest configuration delete-nest-config (2) remove existing Nest Configuration. Deleting the Nest Configuration using the Nest Command Status will result in the removal of all configured connections associated with that nest number. switch-mgr-cards (3) Perform Switchover to Standby SMC/XNM card in associated Nest reset-device-cards (4) Reset all device cards in associated Nest clear-device-errors (5) Clear error counters for all channel cards in associated Nest switch-xcc-cards (6) Perform Switchover to Standby XCC card in associated Nest switch-xlink-cards (7) Perform Switchover to Standby XLC card in associated Nest. Response States used in GET RESPONSE Command (100..199) update-successful (101) nest data has been successfully changed delete-successful (102) nest data has been successfully removed switch-mgr-successful (103) nest system managers has been successfully switched reset-successful (104) nest device cards have been issued reset requests clear-successful (105) nest device cards have been issued clear error requests switch-xcc-successful (106) nest xcc's has been successfully switched switch-xlink-successful (107) nest xlink cards has been successfully switched Nest Config Error Codes used in GET RESPONSE Command (200..799) err-general-nest-config-error (200) Unknown nest configuration error occurred. err-invalid-nest-type (201) Configured nest type not in valid range err-invalid-nest-command (202) Unrecognized nest command-action err-invalid-nest-name (203) Configured nest name too long err-invalid-nest-alrm (204) Configured nest alarm contacts not in valid range err-invalid-nest-ndr (205) N+1 Redundancy not supported for nest err-invalid-nest-option (206) Dual XCC/XLC or Dual SMC option not valid err-cannot-delete-online-nest (207) Nest cannot be online when deleting configuration err-nest-not-present (208) Nest not ready for command err-data-locked-by-another-user (450) Another administrative user is making changes to this part of the system via a terminal session. Check Event Log for user name err-snmp-parse-failed (500) Agent could not parse variable err-invalid-snmp-type (501) Variable ASN type does not match Agent defined type err-invalid-snmp-var-size (502) Variable size is too big Enumeration: 'switch-xcc-successful': 106, 'err-snmp-parse-failed': 500, 'switch-xlink-successful': 107, 'err-general-nest-config-error': 200, 'delete-nest-config': 2, 'reset-successful': 104, 'clear-device-errors': 5, 'err-invalid-nest-option': 206, 'err-invalid-nest-command': 202, 'err-invalid-snmp-type': 501, 'err-invalid-nest-type': 201, 'err-invalid-nest-alrm': 204, 'switch-xcc-cards': 6, 'switch-xlink-cards': 7, 'err-invalid-nest-name': 203, 'err-invalid-snmp-var-size': 502, 'update-successful': 101, 'delete-successful': 102, 'ready-for-command': 0, 'err-cannot-delete-online-nest': 207, 'err-nest-not-present': 208, 'err-invalid-nest-ndr': 205, 'err-data-locked-by-another-user': 450, 'update-nest-config': 1, 'switch-mgr-cards': 3, 'clear-successful': 105, 'switch-mgr-successful': 103, 'reset-device-cards': 4.

The number of DNX Power Supplies configured for the Nest. If running with only a single Power Supply, this should be set to 'no' in order to suppress unecessary alarms. no (0) Only 1 Power Supply resides in the Nest. yes (1) Both Power Supplies reside in the Nest.

A list of the Configured device cards in this node with the static and dynamic type information. The maximum number of entries depends on the number of nests times the number of slots in the system plus 3 default entries for the system manager cards and the Protection Switch.

The conceptual row of the Slot Configuration table. A row in this table can not be created or deleted. A row in this table can be modified by providing valid values for either the Slot Name, Configured Device Type, Device Redundancy, or Slot Command Status. Deleting the Slot Configuration using the Slot Command Status value of 'delete-slot-config' will result in the removal of all configured connections associated with that slot number. The xnmSlotCfgCmdStatus field must be included as a variable in a SET PDU for the action to take effect. If the xnmSlotCfgCmdStatus is missing from the SET PDU, the GET RESPONSE will contain the SNMP error status of 'genErr' for and an error index equal to the last variable.

This number uniquely identifies an Device's Nest-Slot Address. This number will be used throughout the system to identify a unique slot. The format is represented using an IP address syntax (4 byte string). The 1st byte represents the Nest Number (0..7) The 2nd byte represents the Slot Number (1..11) The 3rd byte unused The 4th byte unused

This is the slot type configured by the user. The value, slot(0) is the default type for an unconfigured device. If slot(0) is used in a Set Request, the agent will return an error status of 'badValue'. The slot entries representing the System Manager Cards and the Protection Switch device cannot be used in a Set Request since their device type is static.

This is the actual slot type sent back by the card.

The current machine state of the device. not-present (0) Indicates no hardware detected in the slot. online (1) Device is present and is considered primary operational. offline (2) Device is present but currently not operational. disabled (3) Applies to the Protection Switch box if system cannot support redundancy. standby (4) Device is present but considered as secondary. defective (5) Device is present but could not be activated. bus-error (6) Device is present and reporting a bus connection error. out-of-serv (7) Operator has placed device in Out of Service mode.

The current slot device alarm condition level that indicates it's severity. Enumeration: 'critical-level': 4, 'no-alarm': 0, 'minor-level': 1, 'major-level': 2, 'major-minor': 3, 'unknown': 99, 'critical-major-minor': 7, 'critical-minor': 5, 'critical-major': 6.

The user defined name for this slot/device.

The software version release identification number for this device.

The configured N+1 Redundancy state of the device. The slot entries representing the System Manager Cards and the Protection Switch device cannot be used in a Set Request since N+1 Redundancy does not apply to them. disable (0) Device is not configured as part of the Redundancy Group. enable (1) Device is configured as part of the Redundancy Group. n/a (2) Device does not support Redundancy. Enumeration: 'notApplicable': 2, 'enable': 1, 'disable': 0.

The current slot/device miscellaneous state conditions. none (0) no misc condition errors (1) errors reported on device test (2) device is in test mode errors-test (3) errors reported on device while in test mode clockSrc (4) device is the source for the system clock errors-clockSrc (5) device is the source for the system clock and errors found test-clockSrc (6) device is the source for the system clock and is in test mode errors-test-clockSrc (7) device is the source for the system clock and is in test mode and errors were found Enumeration: 'errors-test': 3, 'none': 0, 'errors': 1, 'errors-clockSrc': 5, 'clockSrc': 4, 'errors-test-clockSrc': 7, 'test': 2, 'test-clockSrc': 6.

The command status for this slot configuration row/record. The value used in a SET will be replaced by a response value in the GET RESPONSE indicating success or failure. Default Response State used in GET RESPONSE Command ready-for-command (0) initial default status for a row Slot Device Commands used in SET Command (1..99) update-slot-config (1) change an aspect of current slot configuration delete-slot-config (2) remove existing Slot Configuration. Deleting the Slot Configuration using the Slot Command Status will result in the removal of all configured connections associated with that slot number. ndr-switchover (10) force a switchover to the Standby device ndr-restore (11) force a restore back to the original device Response States used in GET RESPONSE Command (100..199) update-successful (101) slot data has been successfully changed delete-successful (102) slot data has been successfully removed switch-successful (110) Slot N+1 Redundancy device has been successfully switched over to Standby device restore-successful (111) Slot N+1 Redundancy device has been successfully restored back to Primary device Slot Config Error Codes used in GET RESPONSE Command (200..799) err-general-slot-config-error (200) Unknown slot configuration error occurred. err-invalid-slot-type (201) Configured slot type not in valid range err-invalid-slot-command (202) Unrecognized slot command-action err-invalid-slot-name (203) Configured slot name too long err-redundancy-disabled (204) Redundancy disabled on this system or does not apply to device type err-cannot-chg-sys-device (205) System Device type does not support configuration change err-invalid-redundancy-state (207) Redundancy state does not apply or invalid err-cannot-delete-online-device (208) Device cannot be present when deleting configuration err-data-locked-by-another-user (450) Another administrative user is making changes to this part of the system via a terminal session. Check Event Log for user name err-snmp-parse-failed (500) Agent could not parse variable err-invalid-snmp-type (501) Variable ASN type does not match Agent defined type err-invalid-snmp-var-size (502) Variable size is too big Enumeration: 'err-invalid-slot-command': 202, 'err-invalid-snmp-type': 501, 'err-general-slot-config-error': 200, 'delete-slot-config': 2, 'err-invalid-slot-type': 201, 'err-invalid-slot-name': 203, 'err-snmp-parse-failed': 500, 'err-invalid-redundancy-state': 207, 'switch-successful': 110, 'err-data-locked-by-another-user': 450, 'err-cannot-chg-sys-device': 205, 'err-invalid-snmp-var-size': 502, 'restore-successful': 111, 'err-redundancy-disabled': 204, 'ndr-restore': 11, 'update-successful': 101, 'ndr-switchover': 10, 'ready-for-command': 0, 'update-slot-config': 1, 'delete-successful': 102, 'err-cannot-delete-online-device': 208.

The current raw bitmask form of the state of the slot/device.

A list of the Nests with N+1 Redundancy capability in this node. The maximum number of entries depends on the number of nests that have a Protection Switch Device.

The conceptual row of the N+1 Redundancy table. A row in this table can not be created or deleted. A row in this table can be modified by providing valid values for any of the configurable N+1 Redundancy fields. The xNdrCmdStatus field must be included as a variable in a SET PDU for the action to take effect. If the xNdrCmdStatus is missing from the SET PDU, the GET RESPONSE will contain the SNMP error status of 'genErr' for and an error index equal to the last variable.

The nest index number in the node. Nests are indexed 0 through 7 but correspond to Nests 1 to 8.

This is the current N+1 Device Redundancy state. disabled (1) N+1 Redundancy disabled by the user. frozen (2) N+1 Redundancy is not active due to missing hardware components. delayed (3) N+1 Redundancy is delayed due to switchover. enabled (4) N+1 Redundancy enabled and ready. Enumeration: 'disabled': 1, 'frozen': 2, 'enabled': 4, 'delayed': 3.

Indicates the user's desired N+1 Device Redundancy automatic Switchover setting when a primary card fails. manual (0) Failed cards will not be switched automatically by the system. User is required to go to Node Summary Console screen and force a manual switchover of the failed card to the Redundant. automatic (1) The system will automatically switch out failed cards for either NDR Group with the Redundant card. narrowband-auto (2) The system will automatically switch out a failed card for the NDR Narrowband Group with the Redundant. broadband-1-auto(3) The system will automatically switch out a failed card for the NDR Broadband Group 1 with the Redundant. broadband-2-auto(4) The system will automatically switch out a failed card for the NDR Broadband Group 2 with the Redundant. Enumeration: 'broadband-2-auto': 4, 'automatic': 1, 'narrowband-auto': 2, 'manual': 0, 'broadband-1-auto': 3.

Indicates the system's N+1 Device Redundancy automatic Restore setting when a protected card becomes operational. manual (0) Protected cards that become operational will not be restored automatically by the system. User is required to go to Node Summary Console screen and force a manual switchover of the Redundant card back to the Primary card. automatic (1) The system will automatically restore protected cards that become operational for either NDR Group. narrowband-auto (2) The system will automatically restore protected cards that become operational for the NDR Narrowband Group. broadband-1-auto(3) The system will automatically restore protected cards that become operational for the NDR Broadband Group 1. broadband-2-auto(4) The system will automatically restore protected cards that become operational for the NDR Broadband Group 2. Enumeration: 'broadband-2-auto': 4, 'automatic': 1, 'narrowband-auto': 2, 'manual': 0, 'broadband-1-auto': 3.

This is a 2 byte bit field reflecting the slots that are part of the current active NDR Broadband Group 1. The first 11 bits represent each of the slot numbers. If any of the bits are set, those slots are currently part of the Group 1 N+1 Redundancy Group.

This is a 2 byte bit field reflecting the slots that are part of the current active NDR Narrowband Group. The first 11 bits represent each of the slot numbers. If any of the bits are set, those slots are currently part of the Narrowband N+1 Redundancy Group.

This is a slot number that indicates which device card from the active NDR Broadband Group 1 has been currently switched over. Valid Protected slots for NDR Broadband Group1 are 8 through 10. If a zero value is returned, no device card is currently protected.

This is a slot number that indicates which device card from the active NDR Narrowband Group has been currently switched over. Valid Protected slots for NDR Narrowband Group are 2 through 11. If a zero value is returned, no device card is currently protected.

This indicates which type of device is currently occupying the status of active NDR Broadband Group 1. Only one type of broadband device can be supported by N+1 Redundancy at one time. Whichever type is selected as the active Broadband Group 1 type should match the device type of the card in Slot 11, which is the designated Broadband Group 1 NDR Redundant slot. Enumeration: 'sts1': 18, 'hds3': 21, 'ds3': 8, 'e3': 31.

This indicates which type of device is currently occupying the status of active NDR Narrowband Group. Only one type of Narrowband device can be supported by N+1 Redundancy at one time. Whichever type is selected as the active Narrowband type should match the device type of the card in Slot 1, which is the designated Narrowband NDR Redundant slot. Enumeration: 'gr303': 22, 'octalT1E1': 13.

Indicates the system's capability of supporting the N+1 Device Redundancy Dual Broadband Group functionality. The user should configure this variable based on the existence of the Upgraded PSX Hardware. no (0) PSX Dual Broadband Groups disabled or not supported. yes (1) PSX Dual Broadband Groups enabled.

This is a 2 byte bit field reflecting the slots that are part of the current active NDR Broadband Group 2. The first 11 bits represent each of the slot numbers. If any of the bits are set, those slots are currently part of the Group 2 N+1 Redundancy Group.

This is a slot number that indicates which device card from the active NDR Broadband Group 2 has been currently switched over. Valid Protected slots for NDR Broadband Group2 are 1 through 6. If a zero value is returned, no device card is currently protected.

This indicates which type of device is currently occupying the status of active NDR Broadband Group 2. Only one type of broadband device can be supported by N+1 Redundancy at one time. Whichever type is selected as the active Broadband Group 2 type should match the device type of the card in Slot 7, which is the designated Broadband Group 2 NDR Redundant slot. Enumeration: 'sts1': 18, 'hds3': 21, 'ds3': 8, 'e3': 31.

This indicates which type of Protection Switch Chassis Hardware has been detected. In order to run with Dual Broadband Group configuration, this value should be set to psx5300. Enumeration: 'psx5300': 1, 'psx5200': 0.

The command status for this ndr configuration row/record. The value used in a SET will be replaced by a response value in the GET RESPONSE indicating success or failure. Default Response State used in GET RESPONSE Command ready-for-command (0) initial default status for a row NDR Device Commands used in SET Command (1..99) update-ndr (1) change an aspect of current nest N+1 Redundancy Response States used in GET RESPONSE Command (100..199) update-successful (101) ndr data has been successfully changed NDR Config Error Codes used in GET RESPONSE Command (200..799) err-general-ndr-config-error (200) Unknown ndr configuration error occurred. err-invalid-ndr-group-type (201) Configured NDR Group type not in valid range err-invalid-ndr-command (202) Unrecognized NDR command-action err-invalid-ndr-autoswitch (203) NDR Auto Switchover value not in valid range err-invalid-ndr-chassis (204) NDR Chassis Type value not in valid range err-invalid-ndr-dual-bb (205) NDR Dual Broadband Group value not in valid err-invalid-ndr-dual-psx (206) NDR Dual PSX Power Supply value not in valid err-data-locked-by-another-user (450) Another administrative user is making changes to this part of the system via a terminal session. Check Event Log for user name err-snmp-parse-failed (500) Agent could not parse variable err-invalid-snmp-type (501) Variable ASN type does not match Agent defined type err-invalid-snmp-var-size (502) Variable size is too big Enumeration: 'err-invalid-snmp-type': 501, 'err-data-locked-by-another-user': 450, 'err-invalid-ndr-autoswitch': 203, 'err-general-ndr-config-error': 200, 'err-invalid-snmp-var-size': 502, 'err-invalid-ndr-group-type': 201, 'err-snmp-parse-failed': 500, 'err-invalid-ndr-dual-psx': 206, 'update-ndr': 1, 'update-successful': 101, 'err-invalid-ndr-chassis': 204, 'ready-for-command': 0, 'err-invalid-ndr-command': 202, 'err-invalid-ndr-dual-bb': 205.

The number of N+1 Protection Switch Power Supplies configured for the Nest. If running with only a single PSX Power Supply, this should be set to 'no' in order to suppress unecessary alarms. no (0) Only 1 Power Supply resides in the PSX. yes (1) Both Power Supplies reside in the PSX.

Enables or disables the Automatic Database Synchronization.

The current status of the System DB Synchronization. Enumeration: 'notInSync': 2, 'autoSyncOff': 4, 'standByNotPresent': 5, 'inSync': 1, 'syncInProgress': 3.

The number of seconds elapsed since the DB Synchronization has been started.

The command status for this DB Synchronization. The value used in a SET will be replaced by a response value in the GET RESPONSE indicating success or failure. Default Response State used in GET RESPONSE Command ready-for-command (0) initial default status for a row DB Sync Commands used in SET Command (1..99) update (1) Change the auto sync mode startDBSync (2) Starts the DB synchronization process Response States used in GET RESPONSE Command (100..199) update-successful (101) Auto Sync data has been successfully changed sync-start-successful (102) DB Sync process has been successfully started sync-completed-successful (120) DB Sync process has been successfully finished DB Sync Error Codes used in GET RESPONSE Command (200..799) err-gen-dbsync-cfg-error (200) Unknown DB Sync configuration error occurred. err-standby-not-present (201) DB Synchronization cannot be started without standby systemManager Device. err-dbsync-failed (202) DB Synchronization process has failed err-invalid-dbsync-command (203, Unrecognized DB Sync command action err-invalid-dbsync-mode (204) Unrecognized auto sync setting err-data-locked-by-another-user (450) Another administrative user is making changes to this part of the system via a terminal session. Check Event Log for user name err-snmp-parse-failed (500) Agent could not parse variable err-invalid-snmp-type (501) Variable ASN type does not match Agent defined type err-invalid-snmp-var-size (502) Variable size is too big Enumeration: 'err-invalid-snmp-type': 501, 'err-data-locked-by-another-user': 450, 'err-dbsync-failed': 202, 'sync-start-successful': 102, 'update': 1, 'err-invalid-dbsync-command': 203, 'err-invalid-dbsync-mode': 204, 'err-snmp-parse-failed': 500, 'startDBSync': 2, 'err-gen-dbsync-cfg-error': 200, 'update-successful': 101, 'ready-for-command': 0, 'err-invalid-snmp-var-size': 502, 'err-standby-not-present': 201, 'sync-completed-successful': 120.

This is the Device About Information table which consists of an entry for each of the Actual device cards in this node with the module, board, revision and software release information. The maximum number of entries depends on the number of nests times the number of slots in each nest.

The conceptual row of the Device About Information table. A row in this table cannot be added or deleted, only modified.

This number uniquely identifies an Device's Nest-Slot Address. This number will be used throughout the system to identify a unique slot. The format is represented using an IP address syntax (4 byte string). The 1st byte represents the Nest Number (0..7) The 2nd byte represents the Slot Number (1..11) The 3rd byte unused The 4th byte unused

The release date of the software resident on the device card.

The checksum of the software resident on the device card.

The Hardware type of Front card for the device.

The Hardware revision number of the Front card.

The version of Xilinx Hardware on the device card.

The Hardware type of Rear card reported by the device.

The Hardware revision number of the Rear card.

The software version release identification number for this device.

The ERI Enterprise MIB Module for the DNX Nest System Admistration.