Datatek IPv6 Transformer User Manual - Manual (Page 52)

S E C T I O N 8 W E B G U I S Y S T E M
52
8.10 SNMP Server
An enterprise MIB has been implemented on the Transformer that allows viewing translation-
specific configuration and statistics. Included with the Transformer’s SNMP implementation is a
standard MIB file named DATATEK.TXT that allows reading out many different system
parameters (IP addresses, performance measures, etc.) and their descriptions. An NMS that
supports custom MIBs should be able to display the list of available parameters. That MIB does
not support changing or clearing any parameters.
This DATATEK.TXT file does not get put on the Transformer. Instead, it is loaded on a
customer's NMS to merge with all the other MIB descriptors it is expected to find on systems
with SNMP agents. The NMS can use information in this file to direct formatted display of data
and some descriptive text. Without this file, an NMS can only display raw data and does not
display tables well.
Besides this MIB, there are other MIBs supported on the Transformer. Hundreds of data items
are supported. See e.g. mibII.
To generate a list, set up an NMS that supports loading additional MIBS. Tell it where to find the
DATATEK.txt file. Then have the NMS walk the system using a command-line snmp utility to
display everything. It has a list of standard MIBs (in /etc somewhere) and supports adding
extension MIBs in the user's $HOME/.snmp/mibs directory.
Some of the SNMP objects included in the Transformer’s MIB are: IPv4 and IPv6 addresses,
number of IPv4 packets mapped from host to network and vice versa, number of IPv4 packets
passed from host to network and vice versa, number of packets dropped from host, number of
IPv4 packets translated to IPv6 and vice versa, number of IPv6 packets translated to IPv4,
number of IPv6 packets not translated, number of IPv4 and IPv6 packets dropped, number of
packets with untranslatable protocol, number of packets with bad ICMP format, etc.