The MPLS WG Archive

[Nurit Sprecher <nurit.sprecher@SeabridgeNetworks.com>]

Hi Adrian,

Thanks for your response.

Finally I could find the MIB you are talking about (it does not appear in the WG page).

What about notifications? Do you think of defining Traps?

Thanks, Nurit.

 

-----Original Message-----
From: Adrian Farrel [mailto:adrian@olddog.co.uk]
Sent: Monday, October 27, 2003 12:26 AM
To: Nurit Sprecher; cheenu@bloomberg.net; arunv@force10networks.com; tnadeau@cisco.com
Cc: 'mpls@uu.net'
Subject: Re: mplsTunnelDown Trap

 

Please see the work we are doing on the 'next generation' of these MIBs in the CCAMP WG.

 

Cheers,

Adrian

----- Original Message -----

From: Nurit Sprecher

To: 'cheenu@bloomberg.net' ; 'arunv@force10networks.com' ; 'tnadeau@cisco.com'

Cc: 'mpls@uu.net'

Sent: Sunday, October 26, 2003 10:24 AM

Subject: mplsTunnelDown Trap

 

Hi,

I have a question regarding the mplsTunnelDown Trap. The objects that are defined for the Trap are as follows:

       mplsTunnelDown NOTIFICATION-TYPE

          OBJECTS     {

             mplsTunnelAdminStatus,

             mplsTunnelOperStatus

          }

STATUS      current

   DESCRIPTION

        "This notification is generated when a mplsTunnelOperStatus object for one of the

configured tunnels is about to enter the down state from some other state (but not from the notPresent        state).  This other state is indicated by the

          included value of mplsTunnelOperStatus."

   ::= { mplsTeNotifications 2 }

There is no indication (also no in the mplsTunnleTable) on the cause to the error.

The PathErr messages contain details on the cause to the error (error code and error value).

 

How can this information be exposed to the administrator?

 

Thanks, Nurit.