Re: : ASTN Layer Network Architecture- Co-ordiantion between Control & Mgt Planes

[Zhi-Wei Lin <zwlin@lucent.com>]

Hi Alan,

I agree with you. We should include this as an item for discussion next
week. If we cannot resolve, we have the upcoming June meeting to
continue, plus the email exchange...

Continuing the TCM discussion, I guess two scenarios could be
envisioned:

1) Control plane handles set up of TCM for control plane monitoring
2) Control coordinates with management plane for TCM set up. In this
case, two sub-scenarios are also possible:
  a) After TCM is set up by mgmt, control takes over monitoring (some
info exchange is needed between planes)
  b) After TCM is set up, mgmt monitors

Based on what Tammy stated that there will mostly likely always be a
mgmt plane in addition to control plane, and mgmt plane has TCM, do we
want to embark on defining monitoring/TCM setup using control? Which is
the better option: 1, 2a or 2b?

And if I were to be drastic (not that I would ;-), I might even state
that since we are designing this for a switched network where connection
could be set up quickly and state of a connection is measured with
different parameters (e.g., not just availability...??), maybe we can
even consider TCM as optional only for certain types of connections...

Regards,

Zhi



Alan J Weissberger wrote:
> 
> All
> 
> I agree with Tammy's remarks below regarding the jurisdiction of the control
> plane.  We do have a G.874 LL item on Interworking between Mgt and Control
> planes and this takes on more importance with soft PC's.  I see 3 critical
> interactions between these two planes:
> 
> 1.  SPCs: management plane initiates connection, control plane (NNI sig &
> Routing) executes, then informs mgt plane of outcome of connection setup request
> (see attached illustration).  PM and fault management done in management plane
> 
> 
> 2.  Resiliency/ self healing: Management plane sets up connection, but control
> plane is notified of the path to do restoration on a hard failure.  Conversely,
> control plane sets up the connection, but management plane notified to do
> protection on a SONET/SDH path or line layer basis
> 
> 3.  Control plane sets up an OTN connection, management plane is notified to
> activate G.709 TCM sessions (or they may be pre-allocated along predefined paths
> 
> There are others as well, but I believe the above three are most important
> 
> I suggest we address this "co-ordination between planes" issue on May 21-22,
> when we have the ASON discussions in Caracas.
> 
> rgds
> 
> alan W
> 
> Quoting Tammy.Ferris@mail.sprint.com:
> 
> > Shiva,
> > Traditionally, often different systems are responsible for different
> > management functions relating to the same resources.
> >
> > I think it is important to define and keep in mind scope.  For example,
> > as I currently understand it, the control plane is only required to
> > control path set-up within a single layer network (while interacting
> > with other layers as needed to do its job).
> >
> > Network/Service management (management plane) needs scope of all layers
> > and interfaces that cross administrative boundaries.
> >
> > My current view is that the control plane is mainly responsible for
> > connection set-up and tear-down (network engineering) and traffic
> > management for those resources it has been allocated.  If, for some
> > reason, it cannot do its' job (e.g. failure of a control channel), it
> > should be reporting such failures to the management plane.
> > Tammy
> > -----Original Message-----
> > From: ssnarayanan [mailto:ssnarayanan@lucent.com]
> > Sent: Thursday, May 17, 2001 08:47
> > To: zwlin
> > Cc: ssnarayanan; Tammy.Ferris; mvissers; ccamp; t1x15; tsg13q10;
> > tsg15q12; tsg15q14
> > Subject: Re: ASTN Layer Network Architecture
> >
> >
> > Tammy, Maarten and Zhi,
> >   Along the lines of Zhi's question, it is also fundamental to know
> > which plane "owns" the management responsibility for the connection,
> > e.g., if a SPC is setup, then is it the management plane which owns this
> > or the control plane.  The management plane initiates the request, but
> > the control plane executes the request via NNI signaling.  As far as I
> > see, if we resolve this issue, then we can get a better understanding of
> > what is meant by "migrating" a connection from the management plane to
> > the control plane control.
> >
> > Regards,
> > Shiva
> > ------------------
> > Sivakumar Sankaranarayanan
> > Member of Technical Staff
> > HO 3C-508A
> > Lucent Technologies,
> > 101 Crawfords Corner Road,
> > Holmdel, NJ 07733.
> >
> > Phone:        +1 732 949 5762
> > Fax:  +1 732 949 3210 (Attn: S. Sankaranarayanan)
> > Email:        ssnarayanan@lucent.com
> >
> 
> Alan J Weissberger
> DCT
> 2013 Acacia CT
> Santa Clara, CA 95050-3482
> 1 408 588 6493
> Home email: ajwdct@netgate.net
> 
>   ------------------------------------------------------------------------
>                Name: SPCs.ppt
>    SPCs.ppt    Type: Microsoft PowerPoint Show (application/vnd.ms-powerpoint)
>            Encoding: base64