| DnxSlotDeviceType |
|
| Determines the Device Card type in the slot. |
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
slot(0), octal-t1e1(1), quadHighSpeed(2), octalHighSpeed(3), quadOcu(4), smc(5), quad-t1(6), ds3(7), testAccess(8), octalVoice(9), powerSupply(14), psx(15), router(16), sts1(17), hds3(18), gr303(19), xcc(20), xlc(21), xnm(22), ds0dp(25), stm1(26), oc3(27), e3(28), xlc-ot1e1(29), stm1X(30), oc3X(31) |
|
| DnxSlotDeviceState |
|
| Determines state of the Device Card in the configured slot. |
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
not-present(0), online(1), offline(2), disabled(3), standby(4), defective(5), busError(6), outOfService(7), configError(8), online-online(11), online-offline(12), online-standby(13), online-defective(14), online-busError(15), online-oos(16), standby-online(17), standby-offline(18), standby-standby(19), standby-defective(20), standby-busError(21), standby-oos(22), online-cfgError(23), standby-cfgError(24) |
|
| XNdrEntry |
|
| SEQUENCE |
|
|
|
| |
xNdrNestIndex |
Integer32 |
|
| |
xNdrState |
INTEGER |
|
| |
xNdrAutoSwitchover |
INTEGER |
|
| |
xNdrAutoRestore |
INTEGER |
|
| |
xNdrBroadbandGroup1 |
Integer32 |
|
| |
xNdrNarrowbandGroup |
Integer32 |
|
| |
xNdrBroadbandGroup1Protected |
Integer32 |
|
| |
xNdrNarrowbandProtected |
Integer32 |
|
| |
xNdrBroadbandGroup1Type |
INTEGER |
|
| |
xNdrNarrowbandType |
INTEGER |
|
| |
xNdrDualBroadbandEnabled |
DecisionType |
|
| |
xNdrBroadbandGroup2 |
Integer32 |
|
| |
xNdrBroadbandGroup2Protected |
Integer32 |
|
| |
xNdrBroadbandGroup2Type |
INTEGER |
|
| |
xNdrPsxChassisType |
INTEGER |
|
| |
xNdrCmdStatus |
INTEGER |
|
| |
xNdrDualPowerSupply |
DecisionType |
|
| slotConfigEntry |
1.3.6.1.4.1.644.2.4.1.3.1 |
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SlotConfigEntry |
|
|
| slotConfigCmdStatus |
1.3.6.1.4.1.644.2.4.1.3.1.10 |
| 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 |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
ready-for-command(0), update-slot-config(1), delete-slot-config(2), ndr-switchover(10), ndr-restore(11), update-successful(101), delete-successful(102), switch-successful(110), restore-successful(111), err-general-slot-config-error(200), err-invalid-slot-type(201), err-invalid-slot-command(202), err-invalid-slot-name(203), err-redundancy-disabled(204), err-cannot-chg-sys-device(205), err-invalid-redundancy-state(207), err-cannot-delete-online-device(208), err-data-locked-by-another-user(450), err-snmp-parse-failed(500), err-invalid-snmp-type(501), err-invalid-snmp-var-size(502) |
|
| devDownloadEntry |
1.3.6.1.4.1.644.2.4.1.10.1.1 |
| An entry in the Device Download Table |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
DevDownloadEntry |
|
|
| programFileCommand |
1.3.6.1.4.1.644.2.4.1.10.1.1.8 |
| The command to change the load status of the program file, or an error returned from a command. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
loadProgramFile(1), loadProgramToAll(2), deleteProgramFile(4), readyForCommand(5), err-invalid-slot-nbr(6), noProgramFile(7), programFileBusy(8), noError(9), slotNotReady(10), programFileIdle(12), err-invalid-nest-nbr(13), err-invalid-command(414), err-data-locked-by-another-user(450), err-snmp-parse-failed(500), err-invalid-snmp-type(501), err-invalid-snmp-var-size(502) |
|
| xNestCfgEntry |
1.3.6.1.4.1.644.2.4.1.11.1.1 |
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
XNestCfgEntry |
|
|
| xNestCmdStatus |
1.3.6.1.4.1.644.2.4.1.11.1.1.11 |
| 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 |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
ready-for-command(0), update-nest-config(1), delete-nest-config(2), switch-mgr-cards(3), reset-device-cards(4), clear-device-errors(5), switch-xcc-cards(6), switch-xlink-cards(7), update-successful(101), delete-successful(102), switch-mgr-successful(103), reset-successful(104), clear-successful(105), switch-xcc-successful(106), switch-xlink-successful(107), err-general-nest-config-error(200), err-invalid-nest-type(201), err-invalid-nest-command(202), err-invalid-nest-name(203), err-invalid-nest-alrm(204), err-invalid-nest-ndr(205), err-invalid-nest-option(206), err-cannot-delete-online-nest(207), err-nest-not-present(208), err-data-locked-by-another-user(450), err-snmp-parse-failed(500), err-invalid-snmp-type(501), err-invalid-snmp-var-size(502) |
|
| xSlotEntry |
1.3.6.1.4.1.644.2.4.1.11.2.1 |
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
XSlotEntry |
|
|
| xSlotCmdStatus |
1.3.6.1.4.1.644.2.4.1.11.2.1.10 |
| 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 |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
ready-for-command(0), update-slot-config(1), delete-slot-config(2), ndr-switchover(10), ndr-restore(11), update-successful(101), delete-successful(102), switch-successful(110), restore-successful(111), err-general-slot-config-error(200), err-invalid-slot-type(201), err-invalid-slot-command(202), err-invalid-slot-name(203), err-redundancy-disabled(204), err-cannot-chg-sys-device(205), err-invalid-redundancy-state(207), err-cannot-delete-online-device(208), err-data-locked-by-another-user(450), err-snmp-parse-failed(500), err-invalid-snmp-type(501), err-invalid-snmp-var-size(502) |
|
| xNdrEntry |
1.3.6.1.4.1.644.2.4.1.11.3.1 |
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
XNdrEntry |
|
|
| xNdrCmdStatus |
1.3.6.1.4.1.644.2.4.1.11.3.1.16 |
| 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 |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
ready-for-command(0), update-ndr(1), update-successful(101), err-general-ndr-config-error(200), err-invalid-ndr-group-type(201), err-invalid-ndr-command(202), err-invalid-ndr-autoswitch(203), err-invalid-ndr-chassis(204), err-invalid-ndr-dual-bb(205), err-invalid-ndr-dual-psx(206), err-data-locked-by-another-user(450), err-snmp-parse-failed(500), err-invalid-snmp-type(501), err-invalid-snmp-var-size(502) |
|
| dbSyncCmdStatus |
1.3.6.1.4.1.644.2.4.1.12.1.2.4 |
| 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 |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
ready-for-command(0), update(1), startDBSync(2), update-successful(101), sync-start-successful(102), sync-completed-successful(120), err-gen-dbsync-cfg-error(200), err-standby-not-present(201), err-dbsync-failed(202), err-invalid-dbsync-command(203), err-invalid-dbsync-mode(204), err-data-locked-by-another-user(450), err-snmp-parse-failed(500), err-invalid-snmp-type(501), err-invalid-snmp-var-size(502) |
|
| deviceAboutEntry |
1.3.6.1.4.1.644.2.4.2.225.1 |
| The conceptual row of the Device About Information table.
A row in this table cannot be added or deleted, only modified. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
DeviceAboutEntry |
|
|
