Re: [nsp] Config Options.

From: Gert Doering (gert@greenie.muc.de)
Date: Fri Apr 27 2001 - 08:20:24 EDT


hi,

On Fri, Apr 27, 2001 at 11:38:41AM +0100, Desmarais, Jonathan wrote:
> There are two ways to configure a PVC on an ATM interface.
>
> "atm pvc" or just "pvc". WHat is the diffence.
> I have found that using just "pvc" to define the circuit and then
> configuring oam etc, the interface link state changes correctly.
> When I use the atm pvc command and add oam to the end the link state does
> not change. Do I need to configure oam on the physical interface too.
> Or is this just the way it is?

This seems to be the way it is.

But while we're on it: I use ATM subinterfaces, with "pvc" style syntax:

interface ATM2/0.32 point-to-point
 bandwidth 2000000
 ip unnumbered Loopback0
 pvc sp1 15/32
  ubr 2000
  oam-pvc manage
  encapsulation aal5mux ip

and nearly everything works nicely, that is:

 - everything in order -> line is "up/up".
 - line is broken, remote end disconnected -> OAM fails -> line is "down/down"

what I would like to see is:

 - line is looped back -> OAM detects loop -> line is "up/up (looped)"

but that doesn't happen right now, the loopback condition is not
recognized and the Interface just stays "up/up", which is bad for
dial-backup etc.

Does this ring a bell for anyone? Is there a workaround, or is it
"bug your sales droid"...?
   
gert

-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de



This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:35 EDT