Re: SG view of the ASP

"Brian F. G. Bidulock" <[email protected]>
Newsgroups gmane.ietf.sigtran
Organization http://www.openss7.org/
Message-ID <[email protected]>
Krishna,

Munnaluru, Krishna wrote:                    (Thu, 09 Feb 2006 13:51:56)
> The ASP is currently sending the ASP UP message with the same ASP Id to
> both SGPs. 
> 
> As per the SG guys suggestion we temporarily changed the ASP trafficmode
> in the ASP ACTIVE message to loadsharing and this problem goes away. But
> we see another problem.
> 
> The administrator on the ASP side decides to take down the SCTP
> association with SGP2. The ASP sends ASP DOWN message to the SGP2. Then
> the SGP2 responds with ASP DOWN ACK. So far everything looks good. But
> then immediately the SGP1 sends a NOTIFY with the status=ASP Failure and
> includes the Routing Context value. Why is the SGP1 sending this NOTIFY
> and what is the expected behavior of the ASP upon receiving the NOTIFY
> from the SGP1? The SG is sending the NOTIFY because it treats the ASP as
> two separate ASPs and so it thinks that it is notifying to the other
> ASP.
> 
> I think it came down to the way SG was designed - "The SG treating each
> association as a separate ASP as supposed to just one ASP with two
> associations".  Is this the general way a SG behaves (or designed)?
> Should it not treat an ASP as just one rather than two?

In the override case, did the SG send NTFY("Alternate ASP Active") when
SGP1 marked the ASP ASP Inactive?  If not, the SG is not behaving consistent
with the view that there are two ASPs.

--brian

> 
> Please provide some input so that I can confirm my understanding of the
> M3UA protocol.
> 
> Thanks,
> Krishna
> 

-- 
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.