[j-nsp] Policed discards

Sean Clarke sean at clarke-3.demon.nl
Tue Feb 10 01:26:15 EST 2009


Hi Samit

Still sounds like a Layer 2 protocol thing, generally CDP or Spanning 
Tree BPDU's .. probably nothing to worry about, if you can get a sniffer 
on the cisco port it could tell you what it's sending out.

Not sure a "monitor traffic interface ge-x/y/z" will help as the Juniper 
probably discards it before it hits the RE (if it's supposed to)

There are ways to possibly see it on the Juniper but it takes a bit of 
work, as you need to reset the interface into ccc or something similar 
and use tap interfaces.
Not good on a production and disruptive to the customer, so maybe you 
don't want to go down that path

cheers
Sean


On 2/10/09 7:05 AM, Samit wrote:
> Hi Nilesh/Jeff
>
> My Cisco config
>
> spanning-tree portfast bpdufilter default
>
> interface GigabitEthernet0/1
>   description To Juniper ge-0/0/0 PE-1GE-SX-B
>   port-type nni
>   switchport access vlan 2
>   no keepalive
>   media-type sfp
>   speed nonegotiate
>   no cdp enable
>   spanning-tree portfast
> end
>
> interface GigabitEthernet0/5
>   description To Juniper ge-1/3/0 inbuilt
>   port-type nni
>   switchport access vlan 3
>   media-type sfp
>   speed nonegotiate
>   no cdp enable
>   no keepalive
>   spanning-tree portfast
> end
>
> The Police discards counter now increases by 1 in every 30-40secs
> interval in ge-0/0/0 but I still see it. But I don't think i really need
> to worry much, do I? because I don't see any packet loss.
>
> Regards,
> Samit
>
> Nilesh Khambal wrote:
>    
>> Please disable cdp and keepalives on Cisco port connected to this M7i.
>> Also, disable spanning tree on this port by configuring it as an access
>> port.
>>
>> Thanks,
>> Nilesh.
>>
>> Samit wrote:
>>      
>>> Hi, I just installed my first juniper M7i in the production couple of
>>> hour back and after resolving few routing issue so far it is running
>>> smoothly. I noticed that my PE-1GE-SX-B interface is showing only
>>> "Policed discards", the counter which increases by 1 in every 1-2 secs
>>> but the inbuilt GE is showing no errors. As I am not running any
>>> qos/policing in the interface I was wondering what does it means..and
>>> how to fix this error?  the router's both interface is connected with a
>>> Cisco 3400ME in different Vlan.
>>>
>>> interfaces {
>>>      ge-0/0/0 {
>>>          description " Cisco3400-ME Gi0/1 Vlan2";
>>>          unit 0 {
>>>              family inet {
>>>                  address 192.168.0.1/28;
>>>              }
>>>          }
>>>      }
>>>
>>>                                                            Delay: 1/0/1
>>> Interface: ge-0/0/0, Enabled, Link is Up
>>> Encapsulation: Ethernet, Speed: 1000mbps
>>> Traffic statistics:                                           Current
>>> delta
>>>    Input bytes:                3589144576 (34951312 bps)
>>> [26149611]
>>>    Output bytes:               4117970233 (36219936 bps)
>>> [27659648]
>>>    Input packets:                12654493 (15073 pps)
>>> [90668]
>>>    Output packets:               13058310 (15834 pps)
>>> [94510]
>>> Error statistics:
>>>    Input errors:
>>> 0                                [0]
>>>    Input drops:
>>> 0                                [0]
>>>    Input framing errors:
>>> 0                                [0]
>>>    Policed discards:
>>> 558                                [4]
>>>    L3 incompletes:
>>> 0                                [0]
>>>    L2 channel errors:
>>> 0                                [0]
>>>    L2 mismatch timeouts:
>>> 0                                [0]
>>>    Carrier transitions:                 0  Output
>>> errors:                [0]
>>>
>>>
>>>
>>> Regards,
>>> Samit
>>>
>>> _______________________________________________
>>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>>
>>>        
>>      
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>    



More information about the juniper-nsp mailing list