Description

In this example, we will show how to poll the Multicast Bits Per Second rate for a Juniper multicast group

 

{master}

root@Juniper-Router> show multicast route instance jtac extensive   

Instance: jtac Family: INET

 

Group: 235.1.1.1

  Source: 10.1.3.152/32

  Upstream interface: xe-0/0/0.0

  Number of outgoing interfaces: 0

  Session description: Unknown

  Statistics: 23 kBps, 500 pps, 139793 packets

  Next-hop ID: 0

  Upstream protocol: PIM

  Route state: Active

  Forwarding state: Pruned

  Cache lifetime/timeout: 3660 seconds

  Wrong incoming interface notifications: 0

  Uptime: 00:09:19

Solution

The MIB to poll the multicast Bps is called ipMcastRouteBps 1.3.6.1.2.1.168.1.5.1.24

https://apps.juniper.net/mib-explorer/navigate?software=Junos%20OS&release=23.1R1&name=ipMcastRouteBps&oid=1.3.6.1.2.1.168.1.5.1.24

 

To Poll this OID, we can simply perform an snmpwalk to the ipMcastRouteBps MIB. In this example, the group is part of a routing instance called jtac so we can perform the snmpwalk as follows:

 

juniper@snmp-server:~$ snmpwalk -v2c -c jtac@test1234 10.10.10.15 1.3.6.1.2.1.168.1.5.1.24 

iso.3.6.1.2.1.168.1.5.1.24.1.4.235.1.1.1.32.1.4.10.1.3.152.32 = Counter64: 23001 <<<<<<<<<<<23KBps

 

Here is the snmp configuration on the device:

 

{master}

root@Juniper-Router> show configuration snmp community test1234 

routing-instance jtac {

  clients {

    10.10.10.10/32;

  }

}

 

Here is the multicast route Bps stats for the jtac group:

 

{master}

root@Juniper-Router> show multicast route instance jtac extensive   

Instance: jtac Family: INET

 

Group: 235.1.1.1

  Source: 10.1.3.152/32

  Upstream interface: xe-0/0/0.0

  Number of outgoing interfaces: 0

  Session description: Unknown

  Statistics: 23 kBps, 500 pps, 318568 packets

  Next-hop ID: 0

  Upstream protocol: PIM

  Route state: Active

  Forwarding state: Pruned

  Cache lifetime/timeout: 3660 seconds

  Wrong incoming interface notifications: 0

  Uptime: 00:15:16

 

The snmp polling statistics for the multicast route for 235.1.1.1 will not refresh on its own and it can only be refreshed if the cli command "show multicast route instance jtac extensive" issued. Therefore, if the snmp polling is needed periodically, then wee need to configure a simple event option to issue the cli command at the desired interval. In this example, we will configure an event option to issue the cli command every 60 second so the snmp polling can update every 60 second as well

 

{master}

root@Juniper-Router> show configuration event-options          

generate-event {

  pps-per-minute-event time-interval 60;

}

policy pps-reporting {

  events pps-per-minute-event;

  then {

    execute-commands {

      commands {

        "show multicast route instance 3002 extensive | no-more";

      }

    }

  }

}

 

juniper@snmp-server:~$ snmpwalk -v2c -c jtac@test1234 10.10.10.15 1.3.6.1.2.1.168.1.5.1.24;date 

iso.3.6.1.2.1.168.1.5.1.24.1.4.235.1.1.1.32.1.4.10.1.3.152.32 = Counter64: 23000

Tue Apr 11 07:51:00 AM PDT 2023

juniper@snmp-server:~$ snmpwalk -v2c -c jtac@test1234 10.10.10.15 1.3.6.1.2.1.168.1.5.1.24;date 

iso.3.6.1.2.1.168.1.5.1.24.1.4.235.1.1.1.32.1.4.10.1.3.152.32 = Counter64: 23023

Tue Apr 11 07:52:01 AM PDT 2023

juniper@snmp-server:~$ snmpwalk -v2c -c jtac@test1234 10.10.10.15 1.3.6.1.2.1.168.1.5.1.24;date 

iso.3.6.1.2.1.168.1.5.1.24.1.4.235.1.1.1.32.1.4.10.1.3.152.32 = Counter64: 22968

Tue Apr 11 07:53:05 AM PDT 2023

 

Modification History

04-18-2023 initial version