Re: m3ua querry..

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

Devayya BOPAIAH wrote:                         (Wed, 07 Nov 2007 05:41:04)
> Hi,
> 
> We are testing the m3ua Implementation at the ASP side.(i.e MGC)
> Other side is the testing equipment.(Consider this as a AS)
> Also there is only one ASP in that AS. Traffic mode is loadshare.
> 
> 1) Suppose ASP is in DOWN state and If I send Notify with AS-INACTIVE 
> from test equipment, what should be the state of ASP ?

RFC 4666 4.3.1 ...

   ASP-DOWN: The remote M3UA peer at the ASP/IPSP is unavailable, and/or
   the related SCTP association is down.  Initially, all ASPs/IPSPs will
   be in this state.  An ASP/IPSP in this state SHOULD NOT be sent any
   M3UA messages, with the exception of Heartbeat, ASP Down Ack, and
   Error messages.

The ASP should stay in the ASP-DOWN state and send ERR(Unexpected Message).

> 
> 2) Suppose ASP is in DOWN state and if I send Notify with AS-ACTIVE from 
> test equipment, what should be the state of the ASP ?

The ASP should stay in the ASP-DOWN state and send ERR(Unexpected Message).

> 
> 3) Suppose ASP has recieved ASP-UP-ACK message and if I send a Notify 
> with AS-ACTIVE message from test equipment what should be the state of ASP ?


RFC 4666 4.3.1 ...

   ASP-INACTIVE: The remote M3UA peer at the ASP/IPSP is available (and
   the related SCTP association is up), but application traffic is
   stopped.  In this state, the ASP/IPSP SHOULD NOT be sent any DATA or
   SSNM messages for the AS for which the ASP/IPSP is inactive.

The ASP should stay in the ASP-INACTIVE state for the AS: the peer has
gone insane (it is sending AS-ACTIVE when no ASP is active for the AS),
so informing local management might be an idea.

--brian

-- 
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.