RMON GUI - Remote network MONitoring
Administrator handbook
|
|
RMON GUI - Remote network MONitoring
|
Table of contents |
|
The RMON GUI program is able to display the protocol table of the RMON 2 group 11.
This table lists the protocols that the RMON Probe agent has the capability to decode and count. There is one entry in this table for each such protocol. These protocols represent different network layer, transport layer, and higher-layer protocols. The RMON probe normally boots up with this table preconfigured with those protocols that it knows about and wishes to monitor.
To access the table "protocol table" click on the icon 
or select the menu option Protocol and Protocol List .
The table of "protocol table" contains the following columns:
| Column | Description |
|---|---|
Protocol mib object : protocolDirID |
Protocol description based on the unique identifier protocolDirID for a particular protocol. |
|
mib object : protocolDirLocalIndex |
The locally arbitrary, but unique identifier associated with this protocolDir entry. RMON GUI use this index to assign the Protocol name into other RMON table in the column Protocol. The value for each supported protocol remain constant at least from one re-initialization of the entity's network management system to the next re-initialization, except that if a protocol is deleted and re-created, it must be re-created with a new value that has not been used since the last re-initialization. The specific value is meaningful only within a given SNMP entity. A protocolDirLocalIndex must not be re-used until the next agent-restart in the event the protocol directory entry is deleted. |
The protocol table of the group 11 is indexed by the protocolDirID and protocolDirParameter snmp object.
The protocolDirID snmp object is a unique octet string for a specific protocol. This octets string is structured in tree hierarchy and the root of the tree is the MAC layer. The branches of this tree follow the OSI layer up to layer 7.
Example : ether2.ip.udp.snmp
The value of protocolDirID is composed of fields organized like this :
As example:
For the Ethernet 2 protocol only, protocolDirID is encoded : 4.0.0.0.1
The value 4 specifies that four bytes are used for the protocol identification and 0.0.0.1 value specifically identify the Ethernet 2 protocol
For IP protocol running over Ethernet 2, protocolDirID is encoded : 8.0.0.0.1.0.0.8.0
The value 8 specifies that height bytes are used for the protocol identification, 0.0.0.1 value specifically identify the Ethernet 2 protocol at the MAC layer and 0.0.8.0 value specifically identify the IP at the network layer.
For UDP protocol running over IP protocol running over Ethernet 2, protocolDirID is encoded : 12.0.0.0.1.0.0.8.0.0.0.0.17
The value 12 specify that twelve bytes are used for the protocol identification, 0.0.0.1 value specifically identify the Ethernet 2 at the MAC layer, 0.0.8.0 value specifically identify the IP at the network layer and 0.0.0.17 value specifically identify the UDP at the transport layer.
For the SNMP protocol running over the UDP protocol running over the IP protocol running over Ethernet 2, protocolDirID is encoded : 12.0.0.0.1.0.0.8.0.0.0.0.17.0.0.0.161
The value 16 specifies that sixteen bytes are used for the protocol identification, 0.0.0.1 value specifically identify the Ethernet 2 at the MAC layer, 0.0.8.0 value specifically identify the IP at the network layer and 0.0.0.17 value specifically identify the UDP at the transport layer and 0.0.0.161 specifically identify the snmp protocol at the application layer.
www.loriotpro.com |
|