[j-nsp] ex-series: counters for transit traffic ?

[alain.briant at bt.com]

Hi Alexandre

Concerning the pps (paquets per second) or bps (bytes per second) counters they are not active
See doc :
http://www.juniper.net/techpubs/en_US/junos9.1/topics/reference/command-summary/show-interfaces-gigabit-ethernet-ex-series.html
(not enabled !)
But the counters are couting the number of packets and bytes going through the switch
You just cant see the instant througpought on the wire ...
You have to do some calculation to do that with your watch in your hand !

HTH
Alain


Extract from docs:
Traffic statistics 
 Number and rate of bytes and packets received and transmitted on the physical interface. 

Input bytes-Number of bytes received on the interface. 
Output bytes-Number of bytes transmitted on the interface. 
Input packets-Number of packets received on the interface 
Output packets-Number of packets transmitted on the interface. 
Note: The bandwidth bps counter is not enabled on this platform.
 
  

-----Message d'origine-----
De : juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-bounces at puck.nether.net] De la part de Alexandre Snarskii
Envoyé : vendredi 1 août 2008 16:39
À : Juniper-NSP Mailing list
Objet : [j-nsp] ex-series: counters for transit traffic ?


Hi!

It looks like ex-series switches does not count nor packets nor bytes, nor ingress nor egress, for transit traffic. 

For example, on physical interfaces all I can get is Local statistics: 

snar> show interfaces ge-0/0/0 detail statistics    
[...]
    Traffic statistics:
     Input  bytes  :               121945
     Output bytes  :               883419
     Input  packets:                 1248
     Output packets:                10316
    Local statistics:
     Input  bytes  :               121945
     Output bytes  :               883419
     Input  packets:                 1248
     Output packets:                10316
    Transit statistics:
     Input  bytes  :                    0                    0 bps
     Output bytes  :                    0                    0 bps
     Input  packets:                    0                    0 pps
     Output packets:                    0                    0 pps

and for logical interfaces situation is even worse: 

snar> show interfaces vlan.69 detail statistics
  Logical interface vlan.69 (Index 90) (SNMP ifIndex 90) (Generation 156)
    Description: Management
    Flags: SNMP-Traps 0x0 Encapsulation: Unspecified
    Traffic statistics:
     Input  bytes  :                    0
     Output bytes  :                    0
     Input  packets:                    0
     Output packets:                    0
    Local statistics:
     Input  bytes  :                    0
     Output bytes  :                    0
     Input  packets:                    0
     Output packets:                    0

however, attached filter (with counter and policer) shows that there were some transit traffic (from vlan.69 over ge-0/0/23 to vlan.901 over
ge-0/0/0): 

snar> show firewall filter inbound                  

Filter: inbound                                                
Counters:
Name                                                Bytes              Packets
v901-ingress-policer                             15480761                10191
Policers:
Name                                              Packets 
512k                                                 1461

Can anybody enlighten me, is it hardware limitation, software bug (running
9.1R2.10) or something other (like some feature not configured) ? 

Configuration is pretty straightforward: 

snar> show configuration vlans v69
description Management;
vlan-id 69;
interface {
    ge-0/0/23.0;
}
l3-interface vlan.69;

snar> show configuration interfaces ge-0/0/23        
unit 0 {
    family ethernet-switching {
        port-mode trunk;
        vlan {
            members all;
        }
    }
}

snar> show configuration interfaces vlan unit 69
description Management;
family inet {
    filter {
        input inbound;
    }
    address 10.0.88.231/24;
}

snar> show configuration firewall family inet filter inbound
term v901 {
    from {
        destination-address {
            10.1.89.0/24;
        }
    }
    then {
        policer 512k;
        count v901-ingress-policer;
    }
}
term final {
    then accept;
}

PS: snmp counters (both 32- and 64-bit ones) also shows zero. 

PS: yet another interesting feature of that platform/JunOS is that even firewall counters unable to count traffic destined to or generated by vlan.N interfaces.. 

_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp