M3UA Loadsharing Case, Withdrawal of ASP
"Ambika Tripathy" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Message-ID | <[email protected]> |
Hi Folks,
I have a doubt in section 5.2.3 of rfc 4666.
*5.2.3. n+k Sparing, Loadsharing Case, Withdrawal of ASP*
* Following from the example in Section 5.1.4, ASP1 withdraws from
service:*
* SGP ASP1 ASP2 ASP3
| | | |
|<----ASP Inact.----| | |
|---ASP Inact Ack-->| | |
| | | |
|--NTFY(Ins. ASPs)->| | |
|---------------------------------------NOTIFY(Ins. ASPs)-->|
| | | |
| | | |
|<----------------------------------------ASP Act (Ldshr)---|
|------------------------------------------ASP Act (Ack)--->|
| | | |
|-NTFY(AS-ACTIVE)-->| | |
|-------------------NOTIFY(AS-ACTIVE)-->| |
|---------------------------------------NOTIFY(AS-ACTIVE)-->|
| | | |
| | | |*
* For the Notify message to be sent, the SG maintains knowledge of the
minimum ASP resources required (e.g., if the SG knows that "n+k" =
"2+1" for a Loadshare AS and "n" currently equals "1").*
* Note: If the SGP detects loss of the ASP1 M3UA peer (e.g., M3UA
heartbeat loss or detection of SCTP failure), the initial ASPs
Inactive message exchange (i.e., SGP-ASP1) would not occur.
*
Question>>
1. When ASP1 withdraw request from AS and ASP3 becomes active why SG will
notify ASP2 with AS-ACTIVE??? As per my understanding the state of ASP2 is
not changed.
--
Br,
Ambika Prasad Tripathy
Nethawk Networks
Cell: +91-94375 47730
_______________________________________________
Sigtran mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sigtran