[nsp] oam-pvc manage packet loss

[Kevin Gannon]

If your ATM provider is anything like our ATM team
then the line:

  vbr-nrt 2048 2048 32

Should read:

    vbr-nrt 2000 2000 32

They take the engineering version of mega rather
than the computer one. On 34Mb/s pvc its a lot of
bandwidth that they save.

Regards,
Kevin

-----Original Message-----
From: sthaug@nethelp.no [mailto:sthaug@nethelp.no]
Sent: 07 September 2002 06:59
To: birsen.ozturk@turk.net
Cc: cisco-nsp@puck.nether.net
Subject: Re: [nsp] oam-pvc manage packet loss


>      For some purpose I am using "oam-pvc manage" command under the ATM
subinterface. I am surprised to see that it causes packet loss. What can be
the reason/solution? I will appreciate any idea.

Why do you think it's the OAM configuration that causes packet loss?

> This configuration has 5% packet loss:     
> !
> interface ATM8/0/0.205 point-to-point
>  ip address x.x.x.x 255.255.255.252
>  ip ospf network point-to-point
>  pvc 0/205
>   oam-pvc manage
>   encapsulation aal5snap
>  !
> When I make it this way the packet loss dissapears:
> !
> interface ATM8/0/0.205 point-to-point
>  ip address x.x.x.x 255.255.255.252
>  ip ospf network point-to-point
>  atm pvc 13 0 205 aal5snap 2048 2048 32

If you really mean exactly what you have written here: Try specifying
a traffic class for the first configiuration, ie.

interface ATM8/0/0.205 point-to-point
 ip address x.x.x.x 255.255.255.252
 ip ospf network point-to-point
 pvc 0/205
  vbr-nrt 2048 2048 32
  oam-pvc manage
  encapsulation aal5snap

Steinar Haug, Nethelp consulting, sthaug@nethelp.no
_______________________________________________
cisco-nsp mailing list  real_name)s@puck.nether.net
http://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/