Monitoring ATM PVC Traffic
Monitoring Control Engine CPU Utilization
Redback provides access to packet and octet counters on each ATM PVC configured on SMS platforms.
If you have a support contract with Redback, you may access a MIB FAQ they've published on their support site. You will need a username and password to access this site.
The configurations below have been tested on SMS1000 and 1800 platforms using AOS 3.1 or newer. While AOS 3.x provides the ability to query each PVC as a separate MIB-II ifIndex, this functionality was broken in the versions of code I tested in 2000 (3.1.4.11 through 3.2.3.17). Things seem to be much better on later 5.0 releases such as 5.0.6.26. I have not tested these configurations on SMS500 or SMS10000 boxes.
RedBack provides access to packet and octet counters on each ATM PVC
configured on SMS platforms through the rbnXAtmAal5Vcl[In|Out][Pkts|Octets]
OIDs which may be found in the RBN-X-ATM-AAL5-VCL-STAT-MIB.
1.3.6.1.4.1.2352.3.1.1.1.1.3 identifies the InOctets counter referenced
above.
1.3.6.1.4.1.2352.3.1.1.1.1.4 identifies the OutOctets counter referenced
above.
The next position identifies the MIB-II ifIndex of the physical port the PVC is configured on; in this case 11, which is the AAL5 layer interface on port 3/1 of my test box. Note that the ifIndex for your AAL5 layer interface may be different! To be sure, run an snmpwalk or equivalent program against the basic MIB-II tree on your target SMS.
The final two positions identify the VPI and VCI of the PVC respectively. In this case I'm looking at the octet traffic on VPI 1 / VCI 42.
In summary, the OIDs are built like this:
# ATM PVC monitoring
Target[a3-1-1-42.redback1]: -1.3.6.1.4.1.2352.3.1.1.1.1.3.11.1.42&1.3.6.1.4.1.2352.3.1.1.1.1.4.11.1.42:community@redback1
1.3.6.1.4.1.2352.3.1.1.1.1.3.[AAL5 ifIndex].[VPI].[VCI]
1.3.6.1.4.1.2352.3.1.1.1.1.4.[AAL5 ifIndex].[VPI].[VCI]
MaxBytes[a3-1-1-42.redback1]: 19375000
Title[a3-1-1-42.redback1]: ATM PVC - VPI 1, VCI 42
PageTop[a3-1-1-42.redback1]: <b>ATM PVC VPI 1, VCI 42</b><p>\n
AbsMax[a3-1-1-42.redback1]: 19375000
Options[a3-1-1-42.redback1]: bits
WithPeak[a3-1-1-42.redback1]: wmy
Directory[a3-1-1-42.redback1]: core/redback1/a3-1-1-42
XSize[a3-1-1-42.redback1]: 400
YSize[a3-1-1-42.redback1]: 200
Colours[a3-1-1-42.redback1]: GREEN#00eb0c,BLUE#0000ff,DARK GREEN#006600,VIOLET#ff00ff
YLegend[a3-1-1-42.redback1]: Bits/second
Monitoring Control Engine CPU Utilization
CPU stats may be found in the RBN-CPU-METER-MIB using the
rbnCpuMeter[FiveSecond|OneMinute|FiveMinute]Avg OIDs.
These respectively correspond to:
1.3.6.1.4.1.2352.2.6.1.1
1.3.6.1.4.1.2352.2.6.1.2
1.3.6.1.4.1.2352.2.6.1.3
A sample MRTG config maight look something like this:
Target[cpu.redback1]: 1.3.6.1.4.1.2352.2.6.1.3.0&1.3.6.1.4.1.2352.2.6.1.1.0:community@router
MaxBytes[cpu.redback1]: 100
Title[cpu.redback1]: redback1 - CPU Utilization
PageTop[cpu.redback1]: <b>redback1</b> RedBack SMS1800/CE3 - CPU Utilization\n
AbsMax[cpu.redback1]: 100
WithPeak[cpu.redback1]: wmy
Options[cpu.redback1]: absolute, gauge
Directory[cpu.redback1]: noc/network/rb-0.crane.pa/cpu
XSize[cpu.redback1]: 400
YSize[cpu.redback1]: 200
LegendI[cpu.redback1]: 5 min CPU Util:
LegendO[cpu.redback1]: 5 sec CPU Util:
Legend1[cpu.redback1]: 5 min CPU Util.
Legend2[cpu.redback1]: 5 sec CPU Util.
Colours[cpu.redback1]: GREEN#00eb0c,BLUE#0000ff,DARK GREEN#006600,DARK GREEN#006600
YLegend[cpu.redback1]: % Utilization
ShortLegend[cpu.redback1]: %
Redback does not provide memory statistics in their MIBs at present. There may be a way to get the utilization of a Forwarding Engine (FE), however I haven't found it yet.
updated 09/03/2003 Justin M. Streiner