charSessIndex OBJECT-TYPE
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The session index in the context of the port, a
non-zero positive integer. Session indexes within a
port need not be sequential. Session indexes may be
reused for different ports. For example, port 1 and
port 3 may both have a session 2 at the same time.
Session indexes may have any valid integer value,
with any meaning convenient to the agent
implementation."
View at oid-info.com
The session index in the context of the port, a
non-zero positive integer. Session indexes within a
port need not be sequential. Session indexes may be
reused for different ports. For example, port 1 and
port 3 may both have a session 2 at the same time.
Session indexes may have any valid integer value,
with any meaning convenient to the agent
implementation.
Parsed from file rfc1658-Character-Stream-Devices.mib.txt
Company: None
Module: CHARACTER-MIB
The session index in the context of the port, a
non-zero positive integer. Session indexes within a
port need not be sequential. Session indexes may be
reused for different ports. For example, port 1 and
port 3 may both have a session 2 at the same time.
Session indexes may have any valid integer value,
with any meaning convenient to the agent
implementation.
Parsed from file MRVINREACH.mib
Module: MRVINREACH
Automatically extracted from RFC1658
charSessIndex OBJECT-TYPE SYNTAX INTEGER (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "The session index in the context of the port, a non-zero positive integer. Session indexes within a port need not be sequential. Session indexes may be reused for different ports. For example, port 1 and port 3 may both have a session 2 at the same time. Session indexes may have any valid integer value, with any meaning convenient to the agent implementation." ::= { charSessEntry 2 }
charSessIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "The session index in the context of the port, a non-zero positive integer. Session indexes within a port need not be sequential. Session indexes may be reused for different ports. For example, port 1 and port 3 may both have a session 2 at the same time. Session indexes may have any valid integer value, with any meaning convenient to the agent implementation." ::= { charSessEntry 2 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.19.3.1.1 | charSessPortIndex | 0 | 0 | The value of charPortIndex for the port to which this session belongs. |
| 1.3.6.1.2.1.19.3.1.3 | charSessKill | 0 | 0 | A control to terminate the session. In response to a get-request or get-next-request, the agent always returns 'ready' as the va… |
| 1.3.6.1.2.1.19.3.1.4 | charSessState | 0 | 0 | The current operational state of the session, disregarding flow control. 'connected' indicates that character data could flow on… |
| 1.3.6.1.2.1.19.3.1.5 | charSessProtocol | 0 | 0 | The network protocol over which the session is running. Other OBJECT IDENTIFIER values may be defined elsewhere, in association … |
| 1.3.6.1.2.1.19.3.1.6 | charSessOperOrigin | 0 | 0 | The session's source of establishment. |
| 1.3.6.1.2.1.19.3.1.7 | charSessInCharacters | 0 | 0 | This session's subset of charPortInCharacters. |
| 1.3.6.1.2.1.19.3.1.8 | charSessOutCharacters | 0 | 0 | This session's subset of charPortOutCharacters. |
| 1.3.6.1.2.1.19.3.1.9 | charSessConnectionId | 0 | 0 | None |
| 1.3.6.1.2.1.19.3.1.10 | charSessStartTime | 0 | 0 | The value of sysUpTime in MIB-2 when the session entered connecting state. |