| OID | 1.3.6.1.2.1.6.19.1.7 |
| Module | TCP-MIB (CISCO) |
| Nom | tcpConnectionState |
| Acces | readwrite |
| Status | current |
| Description | The state of this TCP connection.
The value listen(2) is included only for parallelism to the
old tcpConnTable and should not be used. A connection in
LISTEN state should be present in the tcpListenerTable.
The only value that may be set by a management station is
deleteTCB(12). Accordingly, it is appropriate for an agent
to return a `badValue' response if a management station
attempts to set this object to any other value.
If a management station sets this object to the value
deleteTCB(12), then the TCB (as defined in [RFC793]) of
the corresponding connection on the managed node is
deleted, resulting in immediate termination of the
connection.
As an implementation-specific option, a RST segment may be
sent from the managed node to the other TCP endpoint (note,
however, that RST segments are not sent reliably). |
| Syntaxe | Enumeration (1-closed, 2-listen, 3-synSent, 4-synReceived, 5-established, 6-finWait1, 7-finWait2, 8-closeWait, 9-lastAck, 10-closing, 11-timeWait, 12-deleteTCB) |
| Module | TCP-MIB (ietf) |
| Nom | tcpConnectionState |
| Acces | readwrite |
| Status | current |
| Description | The state of this TCP connection.
The value listen(2) is included only for parallelism to the
old tcpConnTable and should not be used. A connection in
LISTEN state should be present in the tcpListenerTable.
The only value that may be set by a management station is
deleteTCB(12). Accordingly, it is appropriate for an agent
to return a `badValue' response if a management station
attempts to set this object to any other value.
If a management station sets this object to the value
deleteTCB(12), then the TCB (as defined in [RFC793]) of
the corresponding connection on the managed node is
deleted, resulting in immediate termination of the
connection.
As an implementation-specific option, a RST segment may be
sent from the managed node to the other TCP endpoint (note,
however, that RST segments are not sent reliably). |
| Syntaxe | Enumeration (1-closed, 2-listen, 3-synSent, 4-synReceived, 5-established, 6-finWait1, 7-finWait2, 8-closeWait, 9-lastAck, 10-closing, 11-timeWait, 12-deleteTCB) |
| Module | TCP-MIB (Alcatel) |
| Nom | tcpConnectionState |
| Acces | readwrite |
| Status | current |
| Description | The state of this TCP connection.
The value listen(2) is included only for parallelism to the
old tcpConnTable and should not be used. A connection in
LISTEN state should be present in the tcpListenerTable.
The only value that may be set by a management station is
deleteTCB(12). Accordingly, it is appropriate for an agent
to return a `badValue' response if a management station
attempts to set this object to any other value.
If a management station sets this object to the value
deleteTCB(12), then the TCB (as defined in [RFC793]) of
the corresponding connection on the managed node is
deleted, resulting in immediate termination of the
connection.
As an implementation-specific option, a RST segment may be
sent from the managed node to the other TCP endpoint (note,
however, that RST segments are not sent reliably). |
| Syntaxe | Enumeration (1-closed, 2-listen, 3-synSent, 4-synReceived, 5-established, 6-finWait1, 7-finWait2, 8-closeWait, 9-lastAck, 10-closing, 11-timeWait, 12-deleteTCB) |
| Module | TCP-MIB (Force10-9.14.2.1) |
| Nom | tcpConnectionState |
| Acces | readwrite |
| Status | current |
| Description | The state of this TCP connection.
The value listen(2) is included only for parallelism to the
old tcpConnTable and should not be used. A connection in
LISTEN state should be present in the tcpListenerTable.
The only value that may be set by a management station is
deleteTCB(12). Accordingly, it is appropriate for an agent
to return a `badValue' response if a management station
attempts to set this object to any other value.
If a management station sets this object to the value
deleteTCB(12), then the TCB (as defined in [RFC793]) of
the corresponding connection on the managed node is
deleted, resulting in immediate termination of the
connection.
As an implementation-specific option, a RST segment may be
sent from the managed node to the other TCP endpoint (note,
however, that RST segments are not sent reliably). |
| Syntaxe | Enumeration (1-closed, 2-listen, 3-synSent, 4-synReceived, 5-established, 6-finWait1, 7-finWait2, 8-closeWait, 9-lastAck, 10-closing, 11-timeWait, 12-deleteTCB) |