DURABLE: { 0:all }
The TCP window size used for all TCP data connections in this
iFCP remote connection, in KBytes. The value configured here
is rounded up to the next multiple of 8 KBytes internally.
The TCP window size specifies how much outstanding data (data
not yet acknowledged by the receiver) may be sent on one TCP
connection. The window size is also the receive buffer size
for each TCP connection.
The recommended TCP window size is the expected bandwidth
multiplied by the round-trip time (RTT). For example, the
optimal window size for a 100 Mbit/sec connection with a
5 msec RTT is 100Mbit/sec * .005 sec = 0.5Mbits or about
65 KBytes.
The value 0 is a special value meaning 'Auto'. In Auto mode,
the switch selects the optimal receive window size for each
TCP connection independently. The window size is based on
the TCP stack measured round-trip times. Each connection is
adjusted dynamically as the connection's RTT changes. In the
case of oversubscription, buffering resources are distributed
fairly across connections to the extent possible. In the auto
mode, each connection has a minimum window size of 128 KB
and a maximum window size of 8184 KB.
The TCP window size may be manually changed at any time by setting
this MIB variable. The new value begins taking effect immediately.
Large changes may take a few seconds to become fully effective, as
the window size changes gradually. TCP window size changes do not
interrupt the remote gateway traffic.
Parsed from file NISHAN-GTWY.mib.txt
Company: brocade
Module: NISHAN-GTWY
Vendor: Brocade
Module: NISHAN-GTWY (NISHAN-GTWY.mib)
Type: TABULAR
Access: read-create
Syntax: INTEGER
(
0..8184 )
Automatically extracted from www.mibdepot.com
rmtPeerTcpWindowSize OBJECT-TYPE SYNTAX INTEGER ( 0 .. 8184 ) MAX-ACCESS read-create STATUS current DESCRIPTION "DURABLE: { 0:all } The TCP window size used for all TCP data connections in this iFCP remote connection, in KBytes. The value configured here is rounded up to the next multiple of 8 KBytes internally. The TCP window size specifies how much outstanding data (data not yet acknowledged by the receiver) may be sent on one TCP connection. The window size is also the receive buffer size for each TCP connection. The recommended TCP window size is the expected bandwidth multiplied by the round-trip time (RTT). For example, the optimal window size for a 100 Mbit/sec connection with a 5 msec RTT is 100Mbit/sec * .005 sec = 0.5Mbits or about 65 KBytes. The value 0 is a special value meaning 'Auto'. In Auto mode, the switch selects the optimal receive window size for each TCP connection independently. The window size is based on the TCP stack measured round-trip times. Each connection is adjusted dynamically as the connection's RTT changes. In the case of oversubscription, buffering resources are distributed fairly across connections to the extent possible. In the auto mode, each connection has a minimum window size of 128 KB and a maximum window size of 8184 KB. The TCP window size may be manually changed at any time by setting this MIB variable. The new value begins taking effect immediately. Large changes may take a few seconds to become fully effective, as the window size changes gradually. TCP window size changes do not interrupt the remote gateway traffic." DEFVAL { 0 } ::= { rmtPeerEntry 21 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.4369.1.11.2.1.1.1 | rmtPeerPrimaryIPAddress | 0 | 0 | The external IP Address of the primary remote peer gateway that this entry corresponds to. |
| 1.3.6.1.4.1.4369.1.11.2.1.1.2 | rmtPeerFailoverIPAddress | 0 | 0 | The IP Address of the failover remote peer gateway used to backup the primary peer gateway. If no backup has been configured the… |
| 1.3.6.1.4.1.4369.1.11.2.1.1.3 | rmtPeerLocalGigeIndex | 0 | 0 | The Gigabit Ethernet port index being used for this connection on the switch. |
| 1.3.6.1.4.1.4369.1.11.2.1.1.4 | rmtPeerHoldTime | 0 | 0 | The hold time, measured in seconds, used between the local and remote peers. |
| 1.3.6.1.4.1.4369.1.11.2.1.1.5 | rmtPeerExpZoneListBitMap | 0 | 0 | A bit map indicating the zones requested to be exported from the local peer to the remote peer indicated. Zone 1 is represented… |
| 1.3.6.1.4.1.4369.1.11.2.1.1.6 | rmtPeerAction | 0 | 0 | This connection is enabled by setting the remotePeerAction status to Enabled. |
| 1.3.6.1.4.1.4369.1.11.2.1.1.7 | rmtPeerConnectionStatus | 0 | 0 | This indicates the current status of the connection. down(0) - Connection is not operating. standby(1) - This value is not used. p… |
| 1.3.6.1.4.1.4369.1.11.2.1.1.8 | rmtPeerConnectionDesc | 0 | 0 | A string describing the connection. Used for management purposes. |
| 1.3.6.1.4.1.4369.1.11.2.1.1.9 | rmtPeerRmtSanID | 0 | 0 | The SAN ID of the remote SAN. The format is a 4-Byte unsigned value. This is determined throught inter-gateway communication. |
| 1.3.6.1.4.1.4369.1.11.2.1.1.10 | rmtPeerRcvBytes | 0 | 0 | The total number of bytes received from the remote gateway since the connection was first established, including MAC headers and… |
| 1.3.6.1.4.1.4369.1.11.2.1.1.11 | rmtPeerXmtBytes | 0 | 0 | The total number of bytes transmitted by this gateway since the connection was first established, including MAC headers and CRC. |
| 1.3.6.1.4.1.4369.1.11.2.1.1.12 | rmtPeerConnections | 0 | 0 | The current number of initiator/target pair data connections, between the local and remote gateway, using the iFCP link. For exam… |
| 1.3.6.1.4.1.4369.1.11.2.1.1.13 | rmtPeerLatency | 0 | 0 | The round trip time (RTT) between the local and remote gateways, measured in milliseconds, of the most recent connection keep-ali… |
| 1.3.6.1.4.1.4369.1.11.2.1.1.14 | rmtPeerLostConnections | 0 | 0 | The number of initiator/target pair data connections, between the local and remote gateway, that had to be abnormally terminated… |
| 1.3.6.1.4.1.4369.1.11.2.1.1.15 | rmtPeerLostPackets | 0 | 0 | The number of TCP segments sent by this gateway that had to be retransmitted. |
| 1.3.6.1.4.1.4369.1.11.2.1.1.16 | rmtPeerTotalPackets | 0 | 0 | The number of TCP segments transmitted by this gateway. This does not recount a segment that was retransmitted. |
| 1.3.6.1.4.1.4369.1.11.2.1.1.17 | rmtPeerUpTime | 0 | 0 | The time, in hundredths of a second, since the current control connection to the remote gateway was established. This is the len… |
| 1.3.6.1.4.1.4369.1.11.2.1.1.18 | rmtPeerDiscoveredPathMtuSize | 0 | 0 | The Discovered Path Maximum Transmission Unit (MTU) Size, in bytes, is the MTU size that was discovered for the path used by thi… |
| 1.3.6.1.4.1.4369.1.11.2.1.1.19 | rmtPeerMaxMtuSize | 0 | 0 | The maximum value, in bytes, that can be used for the Maximum Transmission Unit (MTU) Size for the connection. This variable ref… |
| 1.3.6.1.4.1.4369.1.11.2.1.1.20 | rmtPeerRowStatus | 0 | 0 | This indicates the status of this entry. The row status is for creating the row entry. It does not show the status of the conne… |