Our main result of this project is that it is difficult to get the information needed to get the statistics from the VLANs over the ATM network.
We have some interesting secondary results, however. Here are the VLANs in operation at SomeLondonISP:
vtpVlanEntry.vtpVlanName.1.1 = default vtpVlanEntry.vtpVlanName.1.100 = Some Customer vtpVlanEntry.vtpVlanName.1.101 = Some Other Customer vtpVlanEntry.vtpVlanName.1.102 = Some Group vtpVlanEntry.vtpVlanName.1.350 = SomeLondonISP vtpVlanEntry.vtpVlanName.1.351 = Yet Another Customer vtpVlanEntry.vtpVlanName.1.352 = uunet_via_LH vtpVlanEntry.vtpVlanName.1.353 = Some College vtpVlanEntry.vtpVlanName.1.354 = Some .com Company vtpVlanEntry.vtpVlanName.1.356 = Bovine Business Centres vtpVlanEntry.vtpVlanName.1.1002 = fddi-default vtpVlanEntry.vtpVlanName.1.1003 = token-ring-default vtpVlanEntry.vtpVlanName.1.1004 = fddinet-default vtpVlanEntry.vtpVlanName.1.1005 = trnet-default
We were able to locate the statistical data for the switch ports within the MIBs.
(.1.3.6.1.2.1.2.2.1.10.1) interfaces.ifTable.ifEntry.ifInOctets.1 = 411136429 interfaces.ifTable.ifEntry.ifInOctets.2 = 155343636 interfaces.ifTable.ifEntry.ifInOctets.3 = 7948227 (.1.3.6.1.2.1.2.2.1.16.1) interfaces.ifTable.ifEntry.ifOutOctets.1 = 3744645298 interfaces.ifTable.ifEntry.ifOutOctets.2 = 313172733 interfaces.ifTable.ifEntry.ifOutOctets.3 = 7882521
From deeper digging and some hex to binary to decimal conversions, we were able to determine that VLAN 100 is on switch port 1, vlan 101 is on switch port 2, and VLAN 102 is on switch port 3. The other VLANs are not associated with switch ports.
We configured MRTG to monitor the VLANs which corresponded to switch ports. Here are some examples of our early results.
Until our computer is recovered from SomeLondonISP, live data from MRTG is available.
We could only obtain overall data for the ATM interface; we were unable to determine how to separate it into VLANs in the time we had available.
Next: The Conclusions