The MPLS WG Archive

[Jim Boyle <jboyle@Level3.net>]

pretend you are a service provider, a customer calls in and says he's
seeing errors on his service (in particular, bip violalations in POH). 

He is directly connected to your network via port A.
On the far end, he connects to a clec, which hands it off to you at port
Z.  He connects to a CLEC adm on port Z'.  His path terminating equipment
(maybe a router) is port Ac, and Zc, such that the service looks like:

Ac-A-[IP]-Z-CLEC-Z'-Zc

Looking at lines Ac-A and Z-CLEC shows clean lines.

How does the operator determine if his IP network is to blame, or the
CLECs network is to blame?

i'd recomend a few things:

o) Andy's draft should have some sort of way to determine if there are bit
errors hapenning across the IP network that affect the service
payload.  This would provide the same sort of delineation of where a
problem is occuring by looking at LOHs in more traditional transport
network.

o) your mib should include analogues to the SONET mib, such as bip-8
violations, errored seconds, etc... (working off memory here).

o) addition of a "reason for last down" might be nice.

This way, when you, as the service provider, replies that "it's not our
problem, must be the clec", they can say at least go look at it later to
see if they were telling the truth.

As usual, excellent attention paid to the configuration aspects.

regards,

Jim


On Fri, 23 Feb 2001, Thomas D. Nadeau wrote:

> 
> 	Hi,
> 
> 	FYI a new MIB for managing SONET/SDH Circuit Emulation
> Service Over MPLS has been posted. It should be available
> shortly via the IETF's web site. In the meantime, it is available
> at the following web/ftp link. As usual, comments are welcome.
> 
> ftp://anonymous@ftp-eng.cisco.com/ftp/tnadeau/draft-danenberg-sonet-ces-mpls-mib-00.txt
> 
> 	--Tom
>