[j-nsp] Destination Class Accounting: counters are zero

Alexander Shikoff minotaur at crete.org.ua
Tue May 15 15:48:32 EDT 2012


Hello!

On Tue, May 15, 2012 at 03:17:36PM +0100, Alex Arseniev wrote:
> Hello there,
> This might help
> http://www.juniper.net/techpubs/en_US/junos12.1/topics/concept/source-class-usage-guidelines-solution.html
> <quote>
> A source or destination class is applied to a packet only once during the 
> routing table lookup. When a network prefix matches a class-usage policy, 
> SCU is assigned to packets first; DCU is assigned only if SCU has not been 
> assigned. Be careful when using both class types, since misconfiguration can 
> result in uncounted packets.
> </quote>
> Rgds
> Alex

I believe that there is no misconfiguration.
http://www.juniper.net/techpubs/en_US/junos12.1/topics/concept/source-class-usage-options-junos-nm.html
"Source class usage (SCU) counts packets sent to customers by performing 
lookups on the IP source address and the IP destination address. SCU makes it 
possible to track traffic originating from specific prefixes on the provider 
core and destined for specific prefixes on the customer edge. You must enable 
SCU accounting on both the inbound and outbound physical interfaces.

Destination class usage (DCU) counts packets from customers by performing 
lookups of the IP destination address. DCU makes it possible to track traffic 
originating from the customer edge and destined for specific prefixes on the 
provider core router."

Thus I configured SCU input on upstream's interface:
minotaur at br1-gdr.ki# show interfaces ge-2/0/0 unit 200 family inet accounting 
source-class-usage {
    input;
}

... and SCU output and DCU on customer's interface:
minotaur at br1-gdr.ki# show interfaces ae0 unit 753 family inet accounting                                
source-class-usage {
    output;
}
destination-class-usage;

I tried to remove source-class-usage output from customer's interface
but this does not help, counters are zeroes:
minotaur at br1-gdr.ki# run show interfaces ae0.753 extensive               
  Logical interface ae0.753 (Index 97) (SNMP ifIndex 197) (Generation 168)
    Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.753 ]  Encapsulation: ENET2
    Statistics        Packets        pps         Bytes          bps
    Bundle:
        Input :    2130221797      20055 2875832668346    232302248
        Output:     911861056       7149   65210099204      3518416
    Link:
      ge-2/0/5.753
        Input :    2130221797      20055 2875832668346    232302248
        Output:     911861056       7149   65210099204      3518416
    Marker Statistics:   Marker Rx     Resp Tx   Unknown Rx   Illegal Rx
      ge-2/0/5.753               0           0            0            0
    Protocol inet, MTU: 1500, Generation: 198, Route table: 6
      Flags: No-Redirects, DCU
                                               Packets                Bytes
      Destination class            (packet-per-second)    (bits-per-second)

                         to-Other                17433              1679155
                                  (                 19) (              9556)
                       to-Peering             20064858          29583263192
                                  (              24066) (         282133926)
                      to-Upstream                    0                    0
                                  (                  0) (                 0)
      Output Filters: bw-100M-U-ae0.753-o,
      Addresses, Flags: Is-Preferred Is-Primary
        Destination: 109.68.41.132/30, Local: 109.68.41.133, Broadcast: 109.68.41.135, Generation: 177
    Protocol multiservice, MTU: Unlimited, Generation: 199, Route table: 6
      Policer: Input: __default_arp_policer__

-- 
MINO-RIPE


More information about the juniper-nsp mailing list