Specifications

Introduction 1-18

NAM / Traffic Analyzer v3.5 Tutorial

Introduction 1-18

NAM / Traffic Analyzer v3.5 Tutorial

Network Performance Monitoring

Understanding MIBs – Protocol Directory Extensions

Network Performance Monitoring

Understanding MIBs – Protocol Directory Extensions

• Application Response Time (ART)

• Voice / Video

• Differentiated Services (DSMON)

• NBAR-PB MIB

• Switch Monitoring (SMON)

• Usage per Virtual link

• VLAN

• VLAN Priority

• VLAN ACL

Branch Router NM-NAM

Catalyst 6500 and 7600 Series NAM

Understanding MIBs – Protocol Directory Extensions

The NAM not only implements the full RMON2 specification, but also implements additional monitoring

features to support technologies in use today.

• Application Response Time (ART) - Stores response-time statistics on client/server requests and

responses

• Voice / Video – Monitoring voice and video protocols (SCCP, H.323, MGCP, SIP, RTP) for packet

loss, jitter, call or video stream details.

• DSMON (Differentiated Services Monitoring) – Equivalent to putting an RMON agent on each traffic

flow defined by differentiated services code point (DSCP) value. Allows a user to see which DSCP

group is putting the most traffic on the link, and which users within the DSCP group are consuming the

bandwidth. This data can be analyzed to "tune" DSCP allocations within a network, based on the

quality of service (QoS) policies for that network. Network managers can also guard against QoS

policy violations by monitoring DSCP usage by applications other than the designated ones.

• NBAR-PB (Specific to the NM-NAM) – Network-Based Application Recognition statistics. Statistics on

application traffic seen on each interface of the router is collected.

• SMON (Switch Monitoring – Specific to the Cat6500 NAMs) – Similar to RMON1 except for a switch

as opposed to a shared medium. Provides more visibility into traffic traversing a switch.

• Per Virtual Link Monitoring (Specific to the Cat6500 NAMs) Equivalent to putting an RMON agent on

the virtual entity itself allowing for more precise visibility into the consumption of a link. Not only which

virtual entity is consuming the most bandwidth, but also who within the virtual entity is responsible for

consuming bandwidth.