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

----- Original Message ----- From: "Alexander Shikoff" <minot...@crete.org.ua>
To: <juniper-nsp@puck.nether.net>
Sent: Tuesday, May 15, 2012 9:25 AM
Subject: [j-nsp] Destination Class Accounting: counters are zero


Hello List,

I have MX240 router (10.0 R4.7) with two peering links and two upstream links.
I need separate accounting of customer's traffic: to/from upstreams and
to/from peerings.
I configured an SCU input accounting on peering and upstream links,
DCU and SCU output accounting on customer's link:

minot...@br1-gdr.ki# show interfaces ae0 unit 753
vlan-id 753;
family inet {
   accounting {
       source-class-usage {
           output;
       }
       destination-class-usage;
   }
   no-redirects;
   filter {
       output bw-100M-U;
   }
   address 109.68.41.133/30;
}


Then I applied export policy to forwarding table, now every route
has an assigned class, for example:

minot...@br1-gdr.ki# run show route juniper.net table Salt extensive | match class
Destination class: to-Upstream
Source class: from-Upstream


Now let's check extensive information about customer's interface:
minot...@br1-gdr.ki# run show interfaces ae0.753 extensive
 Logical interface ae0.753 (Index 97) (SNMP ifIndex 197) (Generation 168)
   Description: Downstream: Digital Screens Kurenevka
   Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.753 ]  Encapsulation: ENET2
   Statistics        Packets        pps         Bytes          bps
   Bundle:
       Input :    1355645712      10824 1744298393787    125788672
       Output:     676249013       3535   50730352637      1954232
   Link:
     ge-2/0/5.753
       Input :    1355645712      10824 1744298393787    125788672
       Output:     676249013       3535   50730352637      1954232
   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, SCU-out
                                              Packets                Bytes
     Destination class            (packet-per-second)    (bits-per-second)

                        to-Other              1966210            997515326
( 9) ( 4129)
                      to-Peering               904424           1216778711
( 2932) ( 32529971)
                     to-Upstream                    0                    0
( 0) ( 0)
                                              Packets                Bytes
     Source class                 (packet-per-second)    (bits-per-second)

                      from-Other                88128              5568059
( 0) ( 53)
                    from-Peering               534506             37189579
( 1136) ( 664770)
                   from-Upstream                16017              1066310
( 97) ( 49421)
     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__


Why 'to-Upstream' counters are zeroes?
Thanks in advance!

--
MINO-RIPE
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


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

Reply via email to