Professional Documents
Culture Documents
The following figure depicts a typical multi-homed host. Keep this picture in mind when we discuss multi-homing.
App-2 App-3
App-1
OS
NI-1
NI-2
NI-3
160.15.82.20 161.10.8.221
SCTP Tutorial, Ottawa 7/2004
10.1.61.11
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
Multi-homed Considerations
When a peer is multi-homed, a primary destination address will be selected by the SCTP endpoint. By default, all data will be sent to this primary address. When the primary address fails, the sender will select an alternate primary address until it is restored or the user changes the primary address. SACK's may also require some special handling, consider the following:
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
IP-1 IP-2
EP-1
IP-3
IP Network
IP-4
EP-2
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
Special Considerations
If IP-2 was EP-2's primary address, then the association may still fail even though EP-1 has multiple addresses. [more on association failures later] In the preceding drawing imagine that EP-1 is sending packets with source address IP-2. If EP-2 always sends SACKs back to IP-2, EP-1 will never receive a SACK. To prevent this, a receiver will generally alter the destination address of a SACK if it receives duplicate data.
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
An unreachable peer
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
NI-1
IP Network
IP Network
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
To an SCTP endpoint, both cases appear to be the same failure event (network failure or machine failure). In cases of a software failure if the peers SCTP stack is still alive the association will be shutdown either gracefully or with an ABORT message.
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
NI-1
IP Network
X
SCTP Tutorial, Ottawa 7/2004
IP Network
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
NI-1
IP Network
IP Network
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
A destination address is idle if no chunks that can be used for RTT updates have been sent to it
e.g. usually DATA and HEARTBEAT
The heartbeat period timer is reset any time a DATA or HEARTBEAT are sent
The peer responds with a HEARTBEAT-ACK
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
10
11
Unreachable Destination II
If a primary destination is marked unreachable, an alternate is chosen (if available). Heartbeats will continue to be sent to unreachable addresses. If a Heartbeat is ever answered, the Error count is cleared and the destination is marked reachable.
If it was the primary destination and no user intervention has occurred, it is restored as the primary destination.
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
12
Unreachable Peer I
In addition to the Destination Error count, an overall Association Error count is also maintained. Each time a Destination Error count is incremented, so is the Association Error count. Each time a Destination Error count is cleared, so is the Association Error count. If the Association Error count exceeds a threshold (usually 8), the peer is marked as unreachable and the association is torn down.
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
13
Unreachable Peer II
Note that the two control variables are seperate and unrelated (i.e. Destination Error threshold and the Association Error threshold). It is possible that ALL destinations are unreachable and yet the Association Error count has not exceeded its threshold for association tear down.
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
14
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
15
Address Confirmation
All addresses added to an association via INIT or INIT-ACK's address lists that were NOT supplied by the user or used to exchange the INIT and INIT-ACK are considered to be suspect. These address are marked unconfirmed and CANNOT be marked as the primary address.
A Heartbeat with a 64-bit nonce must be sent and an Heartbeat-Ack with the proper nonce returned before an address can leave the unconfirmed state.
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
16
Endpoint-1 Endpoint-2
IP-X
IP-Z IP-B
IP Network Init(IP-A,IP-B)
Evil-3
IP-A
IP Network
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
17
Heartbeat Controls
Heartbeats can be turned on and off. Heartbeats have a default interval of 30 seconds. This can also be adjusted. The Error thresholds can be adjusted:
Each Destination's Error threshold
Care must be taken in making any adjustments as false failure detections may occur.
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
18
Heartbeat Controls II
All heartbeats have a random delta (jitter) added to them to prevent synchronization. The heartbeat interval will equate to
RTO + HB.Interval + (delta).
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
19
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
20
Endpoint-1
Endpoint-2
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
21
Endpoint-1
Endpoint-2
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
22
Asymmetric Multi-homing
In some cases, one side will be multi-homed while the other side is singly-homed. In this configuration, a single failure on the multihomed side may still disable the association. This failure may occur even when an alternate route exists. Consider the following picture:
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
23
Aysmmetric Multi-Homing
1.1
Endpoint-1
2.1
3.1
Endpoint-2
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
24
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
25
Solution 1
1.1
Endpoint-1
2.1
3.1/4.1
Endpoint-2
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
26
A Simpler Solution
A simpler solution can be made by the assitance of the multi-homed hosts routing table. It first must be setup to allow duplicate routes at any level in its routing table. Support must be added to query the routing table for an alternate route. When SCTP hits a set error threshold, it asks for an alternate route then the previously cached one .
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
27
Solution 2
1.1
Endpoint-1
2.1
3.1
Endpoint-2
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
28
ADD-IP Extensions
The ADD-IP draft allows dynamic changes to an address set of an endpoint without restart of the association.
2004 Randall Stewart (Cisco Systems), Phill Conrad (University of Delaware). All rights reserved.
29