Applies To:
Show VersionsBIG-IP LTM
- 13.1.0, 13.0.1, 13.0.0
Overview: SCTP multistreaming
Unlike Transmission Control Protocol (TCP), Stream Control Transmission Protocol (SCTP) includes the ability to support multistreaming functionality, which permits several streams within an SCTP connection. While a TCP stream refers to a sequence of bytes, an SCTP stream represents a sequence of data messages. Each data message (or chunk) contains an integer ID that identifies a stream, an application-defined Payload Protocol Identifier (PPI), a Stream sequence number, and a Transmit Serial Number (TSN) that uniquely identifies the chunk within the SCTP connection. Chunk delivery is acknowledged using TSNs sent in selective acknowledgements (ACKs) so that every chunk can be independently acknowledged. This capability demonstrates a significant benefit of streams, because it eliminates head-of-line blocking within the connection. A lost chunk of data on one stream does not prevent other streams from progressing while that lost chunk is retransmitted.
Task list
Creating an SCTP profile for multistreaming
Configuring an SCTP virtual server
Overview: SCTP multihoming
Stream Control Transmission Protocol (SCTP) includes the ability to support multihoming functionality, which provides path redundancy for an SCTP connection by enabling SCTP to send packets between multiple addresses owned by each endpoint. SCTP endpoints typically configure different IP addresses on different network interfaces to provide redundant physical paths between the peers. For example, a client and server might be attached to separate VLANs. The client and server can each advertise two IP addresses (one per VLAN) to the other peer. If either VLAN is available, then SCTP can transport packets between the peers.
Task list
Creating an SCTP profile for multihoming
Configuring IP addresses for multihoming connections
Creating a SNAT pool for SCTP
Creating an SCTP pool for multihoming
Configuring an SCTP virtual server for multihoming
- A SNAT Pool containing the server-side IP addresses for the virtual server
- A Node Pool with one node per server-IP address