CXDSP-MIB: View SNMP OID List / Download MIB

VENDOR: MEMOTEC COMMUNICATIONS


 Home MIB: CXDSP-MIB
Download as:   

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 dspSapTable 1.3.6.1.4.1.495.2.1.6.57.1 no-access
A table containing configuration information about all the service access point.
     dspSapEntry 1.3.6.1.4.1.495.2.1.6.57.1.1 no-access
The parameters for a particular service access point.
         dspSapNumber 1.3.6.1.4.1.495.2.1.6.57.1.1.1 sapindex read-only
Identifies the service access point by a numerical value. This value is used as a index in the saps table. Values are unique per service access point.
         dspSapRowStatus 1.3.6.1.4.1.495.2.1.6.57.1.1.2 dsprowstatus read-write
Indicates whether the particular service access point is configured within the MIB Service access point entries (rows) may be created by setting this object value to 'valid', or deleted by changing this object value to 'invalid'. Whether or not the row actually disappears is left to the implementation so this object may actually read as 'invalid' for some arbitrary length of time.
         dspSapType 1.3.6.1.4.1.495.2.1.6.57.1.1.3 integer read-write
Identifies the service access point by type:'lower' identifies a SAP leading to a physical X25 port. 'Upper' identifies a SAP acting as an internal inter-layer logical port. Enumeration: 'upper': 2, 'lower': 1.
         dspSapAlias 1.3.6.1.4.1.495.2.1.6.57.1.1.4 alias read-write
Identifies the service access point by a textual name. Names are unique per service access point.
         dspSapCompanionAlias 1.3.6.1.4.1.495.2.1.6.57.1.1.5 alias read-write
Identifies the `lower' service access point that will communicate with this service access point by a textual name. Names are unique per service access point. Used to bind the DSP Sap with the X25 sap.
         dspSapSnalcRef 1.3.6.1.4.1.495.2.1.6.57.1.1.6 integer read-write
Identifies which upper sap is associated to the lower sap within the DSP module. Applies only to lower DSP saps (X25 sap).
         dspSapEbcdicAsciiMode 1.3.6.1.4.1.495.2.1.6.57.1.1.7 integer read-write
Indicates the character set used by the device defined for this association. The character set could be a EBCDIC or ASCII. Enumeration: 'asciiMode': 2, 'encdicMode': 1.
         dspSapControl 1.3.6.1.4.1.495.2.1.6.57.1.1.20 integer read-write
Control associated with the specified service access point. Enumeration: 'clearStats': 1.
         dspSapOperationalMode 1.3.6.1.4.1.495.2.1.6.57.1.1.30 dspoperationalmode read-only
Identifies the service access point as being active or non-active with the new configuration.
 dspCuTable 1.3.6.1.4.1.495.2.1.6.57.2 no-access
A table containing configuration information about all the 3270 controller units.
     dspCuEntry 1.3.6.1.4.1.495.2.1.6.57.2.1 no-access
The parameters for a particular controller unit.
         dspCuSapNumber 1.3.6.1.4.1.495.2.1.6.57.2.1.1 sapindex read-only
Identifies the sap associated with this controller unit. Each controller unit has an address and the address has to be unique with one sap. However, the address is not required to be unique between saps This object is an index in the sap Table. Values are unique.
         dspCuAddress 1.3.6.1.4.1.495.2.1.6.57.2.1.2 dspcuaddress read-only
Identifies the address of this controller unit. The address has to be unique for a specified sap.
         dspCuRowStatus 1.3.6.1.4.1.495.2.1.6.57.2.1.3 dsprowstatus read-write
Indicates whether the particular service access point is configured within the MIB. Controller unit entries (rows) may be created by setting this object value to 'valid', or deleted by changing this object value to 'invalid'. Whether or not the row actually disappears is left to the implementation so this object may actually read as 'invalid' for some arbitrary length of time.
         dspCuType 1.3.6.1.4.1.495.2.1.6.57.2.1.4 integer read-write
Identifies the type of controller: either TIU or HIU. Enumeration: 'termInterfaceUnit': 1, 'hostInterfaceUnit': 2.
         dspCuCallingX25Address 1.3.6.1.4.1.495.2.1.6.57.2.1.5 x25address read-write
Identifies the X25 address of this sap. This address is unique for all devices attached to this sap, TIU side
         dspCuCalledX25Address 1.3.6.1.4.1.495.2.1.6.57.2.1.6 x25address read-write
Identifies the X25 address of the remote device.
         dspCuDSPCircuitType 1.3.6.1.4.1.495.2.1.6.57.2.1.8 dspcircuittype read-write
Identifies the connection as being either only one connection or multiple DSP connections per X.25 virtual circuit The valid values follow: singUsr-NoReq Circ - single user per X25 svc, no circuit request. The LCN is 0. singUsr-ReqCirc - single user per X25 svc, circuit request. The LCN is negociated during the connection establishment. multUser-ReqCirc - multiple user per X25 svc. Each user has a LCN and the LCN is negociated individually. MES-Usr-ReqCirc - Modified Bisync single user per X25 svc, circuit request. The LCN is negociated during the connection establishment.
         dspCuWindow 1.3.6.1.4.1.495.2.1.6.57.2.1.9 integer read-write
Defines the receive window size used for packets. At the source side, it defines the window for packets received from the source interface. At the destination side, it defines the window for packets transmitted to the the source side, it defines the window for packets transmitted to the source interface. At the destination side, it defines the window for packets received from the destination interface. Allowable value are '1'-'7' for modulo 8.
         dspCuUserData 1.3.6.1.4.1.495.2.1.6.57.2.1.10 displaystring read-write
The user data put in the call user data field of call request packets.
         dspCuFacility 1.3.6.1.4.1.495.2.1.6.57.2.1.11 octet string read-write
Specifies the facility codes and facility parameters put in the facilities field of the call call request packet during call set-up. The maximum number of facility codes and parameters that may be specified is 20.
         dspCuApplicationId 1.3.6.1.4.1.495.2.1.6.57.2.1.12 integer read-write
Indicates an application running on the host associated with the controller unit/device.
         dspCuReqMode 1.3.6.1.4.1.495.2.1.6.57.2.1.13 integer read-only
Identifies the connection request mode. The following modes are available : Fixed Class Crm : destination is selected automatically Specific Class Crm : select a destination by cu/dev addresses. Non-Specific Class Crm : select a destination by address and application ID. Associated Device Crm : associate a device with an existing connection. The terminal DSP uese the Only the 'fixedClassCrm' could be supported by this implementation. Enumeration: 'nonSpecificClassCrm': 3, 'fixedClassCrm': 1, 'specificClassCrm': 2, 'associateDeviceCrm': 4.
         dspCuPacketSize 1.3.6.1.4.1.495.2.1.6.57.2.1.14 packetsize read-write
The receive and transmit packet size.
         dspCuThroughput 1.3.6.1.4.1.495.2.1.6.57.2.1.15 thruputclass read-write
The receive and transmit throughput class across the line.
         dspCuPartner 1.3.6.1.4.1.495.2.1.6.57.2.1.16 dsppartner read-write
This object identifies the knowledge DSP has about its BSC partner layer and applies to the controllers acting as Terminal Interface. In normal conditions, the DSP and BSC layers are configured both having the same interface type (HIU or TIU). This is the default configuration and it enables the controller the be the initiator of the X25 connection. The host can't establish an X25 connection in this configuration. When the Host is the call establishment initiator, this object could be configured as Host (HIU) type and the local BSC as (TIU), meaning that the DSP will behave as a HIU during the call establishment. This object is used just during the call establishment. There are the following options available: terminal-terminal DSP and BSC layers are configured as hosts. host-terminal DSP is configured as host and behaves as a terminal. BSC is configured as a terminal.
         dspCuControl 1.3.6.1.4.1.495.2.1.6.57.2.1.25 integer read-write
Control associated with the specified service access point. Enumeration: 'clearStats': 1.
         dspCuState 1.3.6.1.4.1.495.2.1.6.57.2.1.30 integer read-only
Control associated with the specified service access point. Enumeration: 'x25-connected': 4, 'idle': 1, 'x25-connecting': 2, 'x25-wait-endtoend': 3, 'unknown': 5.
         dspCuOperationalMode 1.3.6.1.4.1.495.2.1.6.57.2.1.31 dspoperationalmode read-only
Identifies the controller unit as being active or non-active with the new configuration.
         dspCuX25CallRequest 1.3.6.1.4.1.495.2.1.6.57.2.1.40 counter read-only
Identifies the number of X25 Call Request packets received by this controller.
         dspCuX25CallAccept 1.3.6.1.4.1.495.2.1.6.57.2.1.41 counter read-only
Identifies the number of X25 Call Accept packets received by this controller.
         dspCuClears 1.3.6.1.4.1.495.2.1.6.57.2.1.42 counter read-only
Identifies the number of Clear Request received from the SNALC layer.
         dspCuClearsInd 1.3.6.1.4.1.495.2.1.6.57.2.1.43 counter read-only
Identifies the number of Clear Indications sent to the SNALC layer.
         dspCuInvToClear 1.3.6.1.4.1.495.2.1.6.57.2.1.44 counter read-only
Identifies the number of INVITATION TO CLEAR packets received by this controller.
 dspDevTable 1.3.6.1.4.1.495.2.1.6.57.3 no-access
A table containing configuration information about all the devices controlled by this module.
     dspDevEntry 1.3.6.1.4.1.495.2.1.6.57.3.1 no-access
The parameters for a particular controller unit.
         dspDevSapNumber 1.3.6.1.4.1.495.2.1.6.57.3.1.1 sapindex read-only
Identifies the sap to which this device is attached to.
         dspDevCuAddress 1.3.6.1.4.1.495.2.1.6.57.3.1.2 dspcuaddress read-only
Identifies the address of the controller unit to which this device is attached.
         dspDevAddress 1.3.6.1.4.1.495.2.1.6.57.3.1.3 dspdevaddress read-only
Identifies the address of this device. The address has to be unique for a specified for a controller unit.
         dspDevRowStatus 1.3.6.1.4.1.495.2.1.6.57.3.1.4 integer read-write
Indicates whether the particular service access point is configured within the MIB. Controller unit entries (rows) may be created by setting this object value to 'valid', or deleted by changing this object value to 'invalid'. Whether or not the row actually disappears is left to the implementation so this object may actually read as 'invalid' for some arbitrary length of time. Enumeration: 'valid': 2, 'invalid': 1.
         dspDevUCN 1.3.6.1.4.1.495.2.1.6.57.3.1.5 integer read-only
Identifies a specific connection.
         dspDevRemoteCuAddress 1.3.6.1.4.1.495.2.1.6.57.3.1.6 dspcuaddress read-write
Identifies the address of remote controller unit to which this device is connected. This object is set to 0 if no connection is established.
         dspDevRemoteDevAddress 1.3.6.1.4.1.495.2.1.6.57.3.1.7 dspdevaddress read-write
Identifies the address of remote controller unit to which this device is connected. This object is set to 0 if no connection is established.
         dspDevFormatSize 1.3.6.1.4.1.495.2.1.6.57.3.1.8 integer read-write
Describes the number of characters suported by the device. Enumeration: 'char1920': 3, 'char3440': 5, 'char3564': 6, 'charReserved2': 8, 'charReserved1': 7, 'char480': 1, 'char2560': 4, 'char960': 2.
         dspDevAttPrnt 1.3.6.1.4.1.495.2.1.6.57.3.1.9 integer read-write
Identifies wheather the device has a printer attached. The device could be a display in order to have a printer attached. Enumeration: 'noPrinterAttached': 1, 'printerAttached': 2.
         dspDevCharSet 1.3.6.1.4.1.495.2.1.6.57.3.1.10 integer read-write
Identifies the support of different character sets. Enumeration: 'noneCharSet': 1, 'aplTextCharSet': 4, 'textCharSet': 3, 'aplCharSet': 2.
         dspDevColour 1.3.6.1.4.1.495.2.1.6.57.3.1.11 integer read-write
Identifies wheather the device supports colours. Enumeration: 'noColourSuport': 2, 'colourSuport': 1.
         dspDevTTextSupport 1.3.6.1.4.1.495.2.1.6.57.3.1.12 integer read-write
Identifies whether it the device supports transparent text. Enumeration: 'nonTransparentText': 2, 'transparentText': 1.
         dspDevDPmode 1.3.6.1.4.1.495.2.1.6.57.3.1.13 integer read-write
Identifies wheather the device is a display or printer. Enumeration: 'printer': 2, 'display': 1.
         dspDevControl 1.3.6.1.4.1.495.2.1.6.57.3.1.20 integer read-write
Control associated with the specified service access point. Enumeration: 'clearStats': 1.
         dspDevOperationalMode 1.3.6.1.4.1.495.2.1.6.57.3.1.30 dspoperationalmode read-only
Identifies the controller unit as being active or non-active with the new configuration.
         dspDevState 1.3.6.1.4.1.495.2.1.6.57.3.1.31 integer read-only
Indicates the state of the conection. The state 'invalid' means there is no connection. The state 'conected' means the connection is established. Enumeration: 'x25-connected': 2, 'wait-status': 5, 'idle': 1, 'connected': 6, 'wait-circuit-enabled': 4, 'wait-circuit-request': 3, 'disconnecting': 7.
         dspDevStatus 1.3.6.1.4.1.495.2.1.6.57.3.1.32 integer read-only
This object contains the 'Status' byte, defined by the BSC protocol for 3270 controller unit family. This object and the 'bscDevSense ' contain the result of the last operations performed on the device. The controller unit is responsable to set properly this byte.
         dspDevSense 1.3.6.1.4.1.495.2.1.6.57.3.1.33 integer read-only
This object contains the 'Sense' byte, defined by the BSC protocol for 3270 controller unit family. This object and the 'bscDevSense ' contain the result of the last operations performed on the device. The controller unit is responsable to set properly this byte.
         dspDevCommand 1.3.6.1.4.1.495.2.1.6.57.3.1.41 counter read-only
Identifies the number of COMAMND packets sent/received by the device. Only the host sends the COMMAND packets. The host DSP counts the number of packets sent. The terminal DSP counts the number of packets received.
         dspDevResponse 1.3.6.1.4.1.495.2.1.6.57.3.1.42 counter read-only
Identifies the number of RESPONSE packets sent/received by the device. Only the termianl sends RESPONSE packets. The host DSP counts the number of packets received. The terminal DSP counts the number of packets sent.
         dspDevCmdRspUndel 1.3.6.1.4.1.495.2.1.6.57.3.1.43 counter read-only
Identifies the number of COMAMND/RESPONSE UNDELIVERED packets. This object notifies how many packets were rejected by this device. The host DSP counts the number of COMMAND ABORTED packets received. The terminal DSP counts the number of RESPONSE ABORTED packets received.. The error code of the last received packet (COMMAND/REPONSE) is kept by the object 'dspDevCmdRspUndelReason'.
         dspDevCmdRspUndelReason 1.3.6.1.4.1.495.2.1.6.57.3.1.44 integer read-only
This object keeps the error code of the last COMAMND/RESPONSE UNDELIVERED packet received. When conected to another Memotec device, only the 'wack' reason code could be received. All other error codes are managed locally by BSC. Enumeration: 'wack': 6, 'reserved': 7, 'ff': 3, 'nak': 5, 'rvi': 2, 'invalid': 8, 'ur': 9, 'timeout': 4, 'eot': 1.
         dspDevCmdRspAbort 1.3.6.1.4.1.495.2.1.6.57.3.1.45 counter read-only
Identifies the number of COMAMND/RESPONSE ABORTED packets. This object notifies how many packets were aborted by this device. The host DSP counts the number of COMMAND ABORTED packets received. The terminal DSP counts the number of RESPONSE ABORTED packets received.. The error code of the last received packet (COMMAND/REPONSE) is kept by the object dspDevCmdRspAbortReason.
         dspDevCmdRspAbortReason 1.3.6.1.4.1.495.2.1.6.57.3.1.46 integer read-only
This object keeps the error code of the last COMAMND/RESPONSE ABORTED packet received. When conected to another Memotec device, all the abort cases are managed locally by BSC. Enumeration: 'nak': 5, 'timeout': 4, 'ff': 3, 'ste': 10.
         dspDevStatStatus 1.3.6.1.4.1.495.2.1.6.57.3.1.47 counter read-only
Identifies the number of STATUS packets sent/received. Only the terminal sends this packet. The terminal DSP counts the number of packets sent. The host DSP counts the number of packets received.
         dspDevAck 1.3.6.1.4.1.495.2.1.6.57.3.1.48 counter read-only
Identifies the number of ACK packets sent by the device. Both host and terminal DSPs can sent ACK packets.
         dspDevInvToClear 1.3.6.1.4.1.495.2.1.6.57.3.1.49 counter read-only
Identifies the number of INVITATION TO CLEAR packets received by the device.
         dspDevInvClearReason 1.3.6.1.4.1.495.2.1.6.57.3.1.50 integer read-only
This object keeps the error code of the last COMAMND/RESPONSE ABORTED packet received. Enumeration: 'unidentPkt': 16, 'invDqFormat': 18, 'invStateTrans': 17, 'invDataFormat': 19, 'facility': 33, 'timeout': 32, 'userInitiated': 1.
         dspDevReset 1.3.6.1.4.1.495.2.1.6.57.3.1.51 counter read-only
Identifies the number of RESET packets received by the device.
         dspDevResetReason 1.3.6.1.4.1.495.2.1.6.57.3.1.52 integer read-only
This object keeps the error code of the last RESET packet received.. Enumeration: 'seqErr': 17, 'invDataFormat': 19, 'unidentDqPkt': 16, 'invDqFormat': 18.
         dspDevCircuitEnabled 1.3.6.1.4.1.495.2.1.6.57.3.1.53 counter read-only
Identifies the number of CIRCUIT ENABLED packets received by the device.
         dspDevCircuitRequest 1.3.6.1.4.1.495.2.1.6.57.3.1.54 counter read-only
Identifies the number of CIRCUIT REQUEST packets received by the device.
         dspDevCircuitDisconnect 1.3.6.1.4.1.495.2.1.6.57.3.1.55 counter read-only
Identifies the number of DISCONNECT packets received by the device.