The MPLS WG Archive

["Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>]

	Hi Tom! Thanks for your reply. I am still a little
	confused. I will appreciate, if you can clarify my
	understanding of your response.

	(A) Meaning of the mplsXCAdminStatus field

	Based on your response, 

	When a user sets 
	(i)mplsXCTable.1.10.100.2.mplsXCAdminStatus to down(2),
		=>user wants the switch to stop forwarding 
		on the out segment with mplsOutSegmentIndex =2
	where as, if the user sets 
	(ii) mplsXCTable.1.10.100.1.mplsXCAdminStatus to down(2)
		=> "overall" connection has been administrated to down
		and switch should not forward on ANY of the out 
		segments

	How do you know which of the two mplsXCAdminStatus fields
	represents the "overall" connection's admin status??
	
	[Similar questions arises for mp2p connections because
	of multiple AdminStatus fields in XC table]

	(B) This is a follow up question: Why didn't we use a 
	single XC entry in the mplsXCTable for each connection 
	(p2p/p2mp/mp2p)?

	Thanks,
	sanjay


-----Original Message-----
From: Thomas D. Nadeau [mailto:tnadeau@cisco.com]
Sent: Wednesday, January 03, 2001 2:32 PM
To: Choudhury, Sanjaya; mpls@UU.NET
Cc: cheenu Srinivasan; Arun Viswanathan
Subject: Re: Questions on creation of p2mp connection using LSR-MIB



         Sanjaya,

         Answers are in-line.

>         Hi! I have few questions related to establishment of
>point-to-multipoint
>         connections using LSR-MIB. Your comments / suggestions will be
>         appreciated.
>
>         Thanks,
>         sanjay
>
>         Consider the following example:
>         -------------------------------------
>         In mplsInSegmentTable :
>         {
>                 mplsInSegmentIfIndex    = 10
>                 mplsInSegmentLabel      = 100
>                 ...
>         }
>         In mplsOutSegmentTable:
>         {
>                 mplsOutSegmentIndex     = 1
>                 mplsOutSegmentIfIndex   = 11
>                 ...
>                 ----------------------------------
>                 mplsOutSegmentIndex     = 2
>                 mplsOutSegmentIfIndex   = 12
>                 ...
>         }
>
>         As per the current indexing scheme, I have to create the following
>         two rows in the mplsXCTable:
>         {
>                 (create a row in this table using the index: 1.10.100.1)
>                 mplsXCIndex             = 1
>                 mplsXCLSPId             = 999
>                 ....
>
>                 (create a row in this table using the index: 1.10.100.2)
>                 mplsXCIndex             = 1
(corrected a typo)
>                 mplsXCLSPId             = 999
>                 ....
>         }
>
>         Creation of the above mentioned row in the XC table will
>automatically
>         populate the mplsInSegmentXCIndex and mplsOutSegmentXCIndex.
>
>         Now the questions:
>         -----------------------
>         (a) mplsXCTable.1.10.100.2.mplsXCAdminStatus == down(2)
>         =>The desired operational status of this segment (outgoing) is
>         down and no packets should be forwarded on this segment.
>
>         Is my assumption correct ?

         If you are referring to the operational status of the
in/OutSegments,
remember that we no longer have operational status in the MPLS-LSR-MIB
for in/out segments as they do not make sense. Your assumption is correct
if you are assuming that the XCoperStatus = down(2) if the connection will
not forward traffic. The details of why it is not forwarding traffic
are not important in this context.


>         (b) Assume that mplsXCTable.1.10.100.1.mplsXCAdminStatus ==
down(2)
>
>         What does this mean ? Is this the adminStatus of the incoming
>segment
>         or the outgoing segment ? or Does it represent the overall admin
>Status of the point-to-multipoint connection ?

         It is meant to denote the overall status of the connection.
The specifics of whether or not the actual in/out label is "enabled"
are up to your implementation.

         --Tom