Overview of OOB Connections and Addressing Modes Configuring OOB Connection Destination Transparency Configuring OOB Connection Full Transparency Destination transparency Full transparency The two options differ in which source IP address and TCP port are used. For details see Configuring OOB Connection Destination Transparency and Configuring OOB Connection Full Transparency.Figure 3‑15 shows TCP/IP packet headers when OOB connection destination transparency is enabled.Figure 3‑15. OOB Connection Destination TransparencyClient-side SteelHead IP address and an ephemeral port number chosen by the client-side SteelHead + server IP address and port number. SteelHeads use the server IP address and port number from the first optimized connection. Connect to the CLI on the client-side SteelHead and enter the following commands: Connect to the Riverbed CLI on the client-side SteelHead and enter the following commands: Figure 3‑16 shows TCP/IP packet headers when OOB connection full transparency is enabled.Figure 3‑16. OOB Connection Full TransparencyClient IP address and client-side SteelHead predetermined port number 708 + server IP address and port number. Use OOB connection full transparency if your network is unable to route between SteelHead in-path IP addresses or in-path VLANs, or you do not want to see SteelHead IP addresses used for the OOB connection.You must first configure WAN visibility full address transparency for OOB connection full transparency to function correctly. For details, see Full Address Transparency.Connect to the CLI on the client-side SteelHead and enter the following commands: Connect to the CLI on the client-side SteelHead and enter the following commands: