The target-defined portion of the iSCSI Session ID.
Parsed from file ISCSI-MIB.mib.txt
Company: promisetech
Module: ISCSI-MIB
iscsiSsnTsid OBJECT-TYPE SYNTAX INTEGER (1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The target-defined portion of the iSCSI Session ID." ::= { iscsiSessionAttributesEntry 4 }
Internet Assigned Numbers Authority
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.3.1.1.1.1.3.3.1.1 | iscsiSsnIndex, iscsiSsnNodeIndex | 0 | 0 | An arbitrary integer used to uniquely identify a particular node within an iSCSI instance present on the local system. For normal… |
1.3.6.1.3.1.1.1.1.3.3.1.2 | iscsiSsnDirection | 0 | 0 | Direction of iSCSI session: InboundSession - session is established from an external initiator to a target within this iSCSI inst… |
1.3.6.1.3.1.1.1.1.3.3.1.3 | iscsiSsnTargetName | 0 | 0 | Name of the target, as described in iscsiTgtName. |
1.3.6.1.3.1.1.1.1.3.3.1.5 | iscsiSsnInitiatorName | 0 | 0 | Name of the initiator, as described in iscsiIntrName. |
1.3.6.1.3.1.1.1.1.3.3.1.6 | iscsiSsnTSIH, iscsiSsnIsid | 0 | 0 | The target-defined identification handle for this session. |
1.3.6.1.3.1.1.1.1.3.3.1.7 | iscsiSsnISID, iscsiSsnAlias | 0 | 0 | The initiator-defined portion of the iSCSI Session ID. |
1.3.6.1.3.1.1.1.1.3.3.1.8 | iscsiSsnUseR2t, iscsiSsnInitiatorAlias | 0 | 0 | Indicates whether the initiator and target have agreed to use the Ready To Transfer (R2T) protocol to control data flow for Data … |
1.3.6.1.3.1.1.1.1.3.3.1.9 | iscsiSsnBidirectionalUseR2t, iscsiSsnTargetAlias | 0 | 0 | Indicates whether the initiator and target have agreed to use the Ready To Transfer (R2T) protocol to contorl data flow for the w… |
1.3.6.1.3.1.1.1.1.3.3.1.10 | iscsiSsnInitialR2T, iscsiSsnImmediateData | 0 | 0 | Indicates whether the initiator and target have agreed to support immediate commands on this session. |
1.3.6.1.3.1.1.1.1.3.3.1.11 | iscsiSsnType | 0 | 0 | Type of iSCSI session: normalSession - session is a normal iSCSI session bootSession - session is being used to boot an i… |
1.3.6.1.3.1.1.1.1.3.3.1.12 | iscsiSsnMaxOutstandingR2t | 0 | 0 | The maximum number of outstanding request-to-transmit (R2T)s per task within this session. |
1.3.6.1.3.1.1.1.1.3.3.1.13 | iscsiSsnMaxDataPduLength, iscsiSsnMaxOutstandingR2T | 0 | 0 | The maximum data payload size supported for command or data PDUs within this session, in units of 512 bytes. |
1.3.6.1.3.1.1.1.1.3.3.1.14 | iscsiSsnFirstBurstSize, iscsiSsnFirstBurstLength | 0 | 0 | The maximum length supported for unsolicited data sent within this session. |
1.3.6.1.3.1.1.1.1.3.3.1.15 | iscsiSsnMaxBurstLength, iscsiSsnConnectionNumber | 0 | 0 | The maximum number of bytes that can be sent within a single sequence of Data-In or Data-Out PDUs. |
1.3.6.1.3.1.1.1.1.3.3.1.16 | iscsiSsnMaxConnections | 0 | 0 | The maximum number of connections that will be allowed within this session. |
1.3.6.1.3.1.1.1.1.3.3.1.17 | iscsiSsnHeaderIntegrity, iscsiSsnAuthIdentity | 0 | 0 | This object contains a pointer to a row in the IPS-AUTH MIB module that identifies the authentication method being used on this s… |
1.3.6.1.3.1.1.1.1.3.3.1.18 | iscsiSsnDataIntegrity, iscsiSsnDataSequenceInOrder | 0 | 0 | False indicates that iSCSI data PDU sequences may be transferred in any order. True indicates that data PDU sequences must be tr… |
1.3.6.1.3.1.1.1.1.3.3.1.19 | iscsiSsnAuthMethod, iscsiSsnDataPDUInOrder | 0 | 0 | False indicates that iSCSI data PDUs within sequences may be in any order. True indicates that data PDUs within sequences must b… |
1.3.6.1.3.1.1.1.1.3.3.1.20 | iscsiSsnErrorRecoveryLevel, iscsiSsnCommandReplay | 0 | 0 | If True, indicates that this session has command replay enabled. |
1.3.6.1.3.1.1.1.1.3.3.1.21 | iscsiSsnDiscontinuityTime, iscsiSsnDataOrder | 0 | 0 | The value of SysUpTime on the most recent occasion at which any one or more of this session's counters suffered a discontinuity. W… |
1.3.6.1.3.1.1.1.1.3.3.1.22 | iscsiSsnDataDeliveryOrder | 0 | 0 | False indicates that data PDUs can be in any order. True indicates that data PDUs have to be at continuously increasing addresses. |