Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

NPM - Juniper Class of Service Monitoring

We recently deployed a large Juniper based MPLS network. A feature missing from NPM is the ability to see Interface class of service statistics for Junos devices.

We run a large number of SRX550's, EX4300's, MX5 and SRX1400 devices. Each of which as access to mib-jnx-cos.txt

https://www.juniper.net/techpubs/en_US/junos12.3/topics/concept/mib-cos-junos-overview.html

https://www.juniper.net/techpubs/en_US/junos12.3/topics/reference/general/jnxcosinvqstattable-nm-mib.html

http://www.juniper.net/techpubs/en_US/junos12.3/topics/reference/mibs/mib-jnx-cos.txt

I'd like to see this added as a trend analysis feature to NPM to allow us to see class based statistics per interface;

- Queued packets/bytes

- Transmitted packets/bytes

- pps transmit rate

- bps transmit rate

- Total tail drops

- Total RED packet/byte drops

- Per drop-precedence packet/byte RED drops

Attached is an SNMP walk from each device model we have for the entire jnxCos structure (1.3.6.1.4.1.2636.3.15)

http://www.oidview.com/mibs/2636/JUNIPER-COS-MIB.html

Cheers

Donald

Find more posts tagged with

Status: None

Comments

ctmidnight

Thanks for your information on this subject.

We are being tasked to begin polling Tail Drop Packet metrics on some of our Juniper devices, and I've built a couple pollers to record stats on jnxCosIfqTailDropPkts and jnxCosIfqTailDropPktRate.

The jnxCosIfqTailDropPkts poller is not behaving as I expected, since the target device it is deployed to has been confirmed to have tail drop packet counters with very high values at present; yet the poller fails to return other than zero.

The jnxCosIfqTailDropPktRate OID shows more promise from use in alerting, since it returns the expected table of interfaces and their current rate at which packets belonging to the specified forwarding class were taildropped at the output on the given interface.

My plan at this point is to create and alert to notify when the rate of taildrop for any managed interface on the Juniper device exceeds 10 (packets/second).

I welcome your input on the efficacy of this solution.

johnsond

Sorry for the long time to reply. I've not progressed this at all myself. The main problem (if I recall) was that Junos across mutliple chassis can change the ifIndex of an interface. This can make it difficult to implement a common custom poller that can be applied to all hosts of the same chassis type.

The real solution I think is for this to become a native element of NPM.

-Donald

sja

Hi ctmidnight

Just run into that problem with IPTV (MC) transport with tail drop on Juniper MX960

We lost alot of time troubleshooting other stuff ....

Do you still monitor that poller jnxCosIfqTailDropPkts ?

Can you share your experience ?

/SJA

johnsond

Hi All,

Today I created some customer pollers which can be found here JuniperCoS.UnDP

Search for 508 and that relates to the ifIndex

On my network 508 relates to Ge-0/0/0 on SRX550 devices.

Below is a script I created to scan through a list of devices and output the desired interfaces ifIndex. It takes a list of device names or IP addresses stored in a txt file and interates through them to return the cli output. All that is required is net-snmp which can be installed on an Ubuntu OS with 'sudo apt install snmp'

usage is ./ifIndex-scan.sh filename interface community where <filename> is the file with the list of hostnames or IPs and <interface> is the interface you wish to look for in the output. Note: The output will filter out logical-interfaces of the physical interface.

#!/bin/bash

# author: donald@it-ninja.xyz

# description: scans ifName OID in IF-MIB and returns interface name objects

# usage:

# ./ifIndex-scan.sh <filename> <interface> <community>

FILE=$1

INTERFACE=$2

COMMUNITY=$3

# setup formatting

divider===============================

divider=$divider$divider

header="\n %-15s %30s\n"

format=" %-15s %30s\n"

width=55

# print the stdout headers

printf "$header" "DEVICE" "${INTERFACE^^} IFINDEX"

printf "%$width.${width}s\n" "$divider"

while read line; do

data=`snmpwalk -c $COMMUNITY -v 2c $line 1.3.6.1.2.1.31.1.1.1.1 | grep $INTERFACE | grep -v -E 'ge-[0-9]/[0-9]/[0-9].[0-9{1,4}]+' | awk -F "\." '{print $12}' | awk '{print $1}'`

printf "$format" $line\

$data

done < $FILE