SCTP Validation

For SCTP, each endpoint advertises its reachable IP addresses to the far or remote end during the association formation. After SCTP signals that a candidate association has been formed, the Transport Manager validates the candidate.

Transport Manager has two methods of SCTP validation: Relax and Match. The effect of each validation method on the provisioning combinations versus the number of IP addresses exchanged by SCTP with the far end and any special action taken are described in Table 3-1.

Relax mode - One address in the incoming INIT/INIT-ACK received by an association must match either of the IP addresses provisioned for the Adjacent Node if two are provisioned. If only one is provisioned (the primary), one address must match it.
Match mode - if the incoming INIT/INIT-ACK has multiple addresses, the number of IP addresses must match the number provisioned and the addresses themselves must match those provisioned for the Adjacent Node with that Transport. If only one is provisioned (the primary), one address must match it. Also, if only one is provisioned for the Adjacent Node, the incoming INIT/INIT-ACK should contain one address.

Table 3-1 SCTP Transport Address Validation

IP Configured in Transport		Received in INIT/INIT-ACK	Transport Manager Behavior
Local Node	Remote Node	Received in INIT/INIT-ACK	Match Mode	Relaxed
1	1	1	Association is accepted	Association is accepted
1	1	2	Association rejected, refusal event generated	Association is accepted
2	2	1	Association rejected, refusal event generated	Association is accepted Operation Reason updated as Abnormal for that Transport Configured Adjacent IP status, which has not been received in INIT/INIT-ACK chunk, is displayed as Unavailable
2	2	2	Association is accepted	Association accepted
2	2	>2	Association rejected, refusal event generated	Association accepted
1	2	1	Association rejected, refusal event generated	Association accepted Operation Reason updated as Abnormal for that Transport Configured Adjacent IP status, which has not been received in INIT/INIT-ACK chunk is displayed as Unavailable
1	2	2	Association accepted Operation Reason updated as Abnormal for that Transport Configured Adjacent IP status, which has not been received in INIT/INIT-ACK chunk is displayed as Unavailable	Association accepted Operation Reason updated as Abnormal for that Transport Configured Adjacent IP status, which has not been received in INIT/INIT-ACK chunk is displayed as Unavailable
2	1	1	Association accepted	Association accepted
2	1	2	Association rejected, refusal event generated	Association accepted