APTIS-ACTIONS-MIB: View SNMP OID List / Download MIB

The following variables describe the administrative actions that may be invoked through SNMP.

slot control

This is the structure of entries in the slotControlTable.

Each invocation of this action will have a unique instance number, assigned by the switch.

like, did it work, or what? This is the standard actionStatus enum used for all actions. Enumeration: 'started': 0, 'failed': 2, 'errParam': 4, 'succeeded': 1.

like, did it work, or what? If the generalStatus is err-param or failed, this will hold a more specific error number. Enumeration: 'inappropriate': 5, 'unknown': 0, 'inUse': 4, 'badSlot': 3, 'noCard': 1, 'notAllowed': 2.

The physical slot number.

The action requested for this slot. Enumeration: 'slotReset': 4, 'slotDownTimed': 5, 'slotNoChange': 0, 'slotDown': 1, 'slotDownPend': 2, 'slotAbortDry': 6, 'slotUp': 3.

This action allows a remote manager to terminate an active session.

This is the structure of entries in the sessionTerminateTable.

Each invocation of this action will have a unique instance number, assigned by the switch.

This is the standard actionStatus enum used for all actions. Enumeration: 'started': 0, 'failed': 2, 'errParam': 4, 'succeeded': 1.

If generalStatus is err-param or failed, this will hold a more specific error number. Enumeration: 'badSignature': 1, 'noError': 0, 'badSession': 2, 'genFail': 3.

An input parameter to the session-terminate action. Together with the sessionID, uniquely identifies the session to terminate. If a value is provided, it must match the current value of bootEra, so this field is only provided as a safeguard to ensure that sessions from the wrong boot era can't be terminated accidentally.

An input parameter to the session-terminate action, naming the session which should be terminated.

An input parameter to the session-terminate action, providing a cryptographically secure verification that the manager requesting the termination has the appropriate credentials to do so. NOTE: the exact algorithm for generating the signature has not yet been determined.

T1 Testing Control.

This is the structure of entries in the t1TestTable.

T1 Test Instance.

type of test to run. Enumeration: 'ones': 1, 'zeros': 2, 'fives': 3, 'qrss': 4.

ID of the slot to run the test on. Enumeration: 'slot11': 11, 'slot13': 13, 'slot12': 12, 'slot15': 15, 'slot14': 14, 'slot17': 17, 'slot16': 16, 'slot18': 18, 'slot8': 8, 'slot1': 1, 'slot3': 3, 'slot2': 2, 'slot5': 5, 'slot4': 4, 'slot7': 7, 'slot6': 6.

ID of the DS1 to run the test on. Enumeration: 'ds130': 30, 'ds131': 31, 'ds132': 32, 'ds133': 33, 'ds134': 34, 'ds135': 35, 'ds136': 36, 'ds137': 37, 'ds138': 38, 'ds139': 39, 'ds156': 56, 'ds118': 18, 'ds119': 19, 'ds152': 52, 'ds153': 53, 'ds150': 50, 'ds151': 51, 'ds112': 12, 'ds113': 13, 'ds110': 10, 'ds111': 11, 'ds116': 16, 'ds117': 17, 'ds114': 14, 'ds115': 15, 'ds155': 55, 'ds154': 54, 'ds127': 27, 'ds126': 26, 'ds125': 25, 'ds124': 24, 'ds123': 23, 'ds122': 22, 'ds121': 21, 'ds120': 20, 'ds129': 29, 'ds128': 28, 'ds145': 45, 'ds144': 44, 'ds147': 47, 'ds146': 46, 'ds141': 41, 'ds140': 40, 'ds143': 43, 'ds142': 42, 'ds149': 49, 'ds148': 48, 'ds11': 1, 'ds12': 2, 'ds13': 3, 'ds14': 4, 'ds15': 5, 'ds16': 6, 'ds17': 7, 'ds18': 8, 'ds19': 9.

number of bytes of data to send.

percentage of data received with errors.

current state of test. Enumeration: 'loopingDown': 5, 'failed': 7, 'complete': 6, 'initializing': 1, 'cancelled': 8, 'loopingUp': 2, 'sendingData': 3, 'checkingResults': 4.

This action causes a portion of the configuration subtree to be written out to a text file on one of the CVX system's local flash cards.

This is the structure of entries in the flashWriteTable.

Each invocation of this action will have a unique instance number, assigned by the switch.

This is the standard actionStatus enum used for all actions. Enumeration: 'started': 0, 'failed': 2, 'errParam': 4, 'succeeded': 1.

If generalStatus is err-param or failed, this will hold a more specific error number. Enumeration: 'lackOfResources': 2, 'genFail': 3, 'noError': 0, 'badArgs': 1.

The starting node in the configuration tree. The contents of all the nodes under this node will be written out to the text file.

The relative file name to hold the text config. The CVX file system uses drive C: to refer to the bottom flash card, and D: to refer to the top flash card. If the drive letter is not specified, then C: is assumed. If this file exists, it will only be overwritten with a complete copy of the output from this action. NOTE that the file CONFIG.CVX is not accessible through this action. To save the config to flash where it will be used at the next reboot, use the flashSave action instead.

On success, the total number of bytes written to flash.

Setting this field to TRUE requests that the output file contain all configuration values, otherwise only those that differ from the default values.

This action causes the configuration subtree to be read to one of the CVX system's local flash cards.

This is the structure of entries in the flashReadTable.

Each invocation of this action will have a unique instance number, assigned by the switch.

This is the standard actionStatus enum used for all actions. Enumeration: 'started': 0, 'failed': 2, 'badFile': 4, 'succeeded': 1, 'genFail': 5.

The relative file name to hold the text config. The CVX file system uses drive C: to refer to the bottom flash card, and D: to refer to the top flash card. If the drive letter is not specified, then C: is assumed.

On success, the total number of lines read from flash.

This action saves the configuration to the flash file CONFIG.CVX. It is equivalent to the 'write' command in the CLI.

This is the structure of entries in the flashSaveTable.

Each invocation of this action will have a unique instance number, assigned by the switch.

This is the standard actionStatus enum used for all actions. Enumeration: 'started': 0, 'failed': 2, 'errParam': 4, 'succeeded': 1.

If generalStatus is err-param or failed, this will hold a more specific error number. Enumeration: 'lackOfResources': 2, 'genFail': 3, 'noError': 0.

CVX Chassis Options.

This is the structure of entries in the resetTable.

Each invocation of this action will have a unique instance number, assigned by the switch.

This is the standard actionStatus enum used for all actions. Enumeration: 'started': 0, 'failed': 2, 'errParam': 4, 'succeeded': 1.

Select the type of reset requested. Enumeration: 'cold': 2, 'hard': 1, 'warm': 3.