in-path peering oobtransparency mode
Enables out-of-band (OOB) connection destination transparency. The OOB connection is a single, unique TCP connection that is established by a pair of SteelHeads that are optimizing traffic. The pair of SteelHeads use this connection strictly to communicate internal information required by them to optimize traffic.
For details about WAN visibility, see
in-path rule auto-discover and the
SteelHead Deployment Guide.
Syntax
[no] in-path peering oobtransparency mode {none | destination | full [port <port>]}
Parameters
none | Specifies correct addressing. The OOB connection is established between the two SteelHeads, without any TCP/IP header manipulation. This is the default setting. |
destination | Specifies destination mode. In this mode, the OOB connection has the form C-SHip:C-SHport<->Sip:Sport, where C-SHip is the client-side SteelHead IP address, C-SHport is an ephemeral port chosen by C-SH, Sip is the server IP address, and Sport is the server port number. The Sip and Sport parameters are taken from the first connection optimized by the pair of SteelHeads. |
full | Specifies full mode. In this mode, the OOB connection has the form Cip:C-SHfixed<->Sip:Sport, where Cip is the client IP address, C-SHfixed is a pre-determined port chosen by the client-side SteelHead, Sip is the server IP address, and Sport is the server port number. The Cip, Sip, and Sport parameters are taken from the first connection optimized by the pair of SteelHeads. |
port <port> | Changes the predetermined port in full mode (C-SHfixed). The default value is 708. |
Usage
With RiOS 5.0.x or later, and if you use WAN visibility full address transparency, you have the following transparency options for the OOB connection: OOB connection destination transparency and OOB connection full transparency.
You configure OOB transparent addressing on the client-side SteelHead (where the connection is initiated). By default, the OOB connection uses correct addressing. Correct addressing uses the client-side SteelHead IP address, port number, and VLAN ID, and the server-side SteelHead IP address, port number, and VLAN ID.
If you are using OOB connection correct addressing and the client-side SteelHead cannot establish the OOB connection to the server-side SteelHead, OOB connection transparency can resolve this issue. For example, if you have a server on a private network that is located behind a NAT device. You configure OOB connection transparency so that the client-side SteelHead uses the server IP address and port number as the remote IP address and port number. SteelHeads route packets on the OOB connection to the NAT device. The NAT device then translates the packet address to that of the server-side SteelHead.
If both of the OOB connection transparency options are acceptable solutions, OOB connection destination transparency is preferable. OOB connection destination transparency mitigates the slight possibility of port number collisions which can occur with OOB connection full transparency.
When OOB connection transparency is enabled and the OOB connection is lost, the SteelHeads reestablish the connection using the server IP address and port number from the next optimized connection.
OOB connection destination transparency uses the client-side SteelHead IP address and an ephemeral port number chosen by the client-side SteelHead, plus the server IP address and port number in the TCP/IP packet headers in both directions across the WAN
SteelHeads use the server IP address and port number from the first optimized connection.
Use OOB connection destination transparency if the client-side SteelHead cannot establish the OOB connection to the server-side SteelHead.
For details about configuring in-path IP addresses and OOB connections for WAN visibility, see the SteelHead Deployment Guide.
Example
amnesiac (config) # in-path peering oobtransparency mode none
Product
SteelHead CX, SteelHead EX, SteelHead-v, SteelHead-c
Related Commands