Home |
Managed Objects |
Managed ObjectsThe managed objects are divided into groups. Each group consists of variables and tables. The following groups are supported: System GroupProvides information about the managed group including location, contact person, etc. Interface GroupProvides information about the hardware interfaces. This group includes the interface table. Address Translation GroupProvides information about the ARP cache. This group consists of the Address Translation Group. It is a subset of the IP Address Translation Table and is included in MIB-II to be compatible with MIB-I. IP GroupProvides IP statistics and other information. This group contains three tables: the IP Address Table, the IP Routing Table and the IP Address Translation Table. ICMP GroupProvides ICMP statistic information. TCP GroupProvides TCP statistic and other information including TCP connections. This group contains the TCP Connection Table. UDP GroupProvides UDP statistic and other information including UDP connections. This group contains the UDP Listener Table. SNMP GroupProvides SNMP statistics as well as the capability to enable SNMP traps. The default is trap reporting disabled. Transmission GroupProvides device driver statistic and other information. This group contains RS232-like MIB and Ethernet-like MIB. The Ethernet-like MIB contains the Ethernet Statistics Table. The RS232-like MIB contains the RS232 Port Table and the RS232 Asynchronous Port Table, the Input Signal Table and the Output Signal Table. The following groups are only supported by SNMPv2: USEC Basic GroupContains information relevant to the user-based security model for SNMPv2. Contains variables describing the agent (AgentID, AgentTime, etc.) as well as statistic variables for SNMPv2u (usecStatsNotInWindows, usecStatsUnknownUserNames, etc.). The following tables are supported: Interface TablePart of the Interface Group. This table accesses entries from the Device Table, and from the interface table. The capability to open and close interfaces is provided through this table. SNMP uses the same parameters (i.e. interrupt number, COM port, etc.) set by the last call to open and set IP (see xn_interface_open, xn_attach, and xn_set_ip); therefore, the application must do the first open and set the IP addresses. When traversing the Interface Table via GetNextRequest commands, entries are returned in the same order as in the Device Table starting at offset 0. Address Translation TablePart of the Address Translation Group. This table accesses entries from the ARP cache. When traversing the Address Translation Table via GetNextRequest commands, the entries are returned in lexical order of the IP addresses starting with the first interface; i.e. the first entry in the interface table. IP Address TablePart of the IP Group. This table accesses the Interface Table. When traversing the IP Address Table via GetNextRequest commands, the entries are returned in lexical order based on their IP addresses. IP Routing TablePart of the IP Group. This table accesses the Routing Table. The capability to modify and delete routes is provided throughout this table. When traversing the IP Routing Table via GetNextRequest commands, the entries are returned in lexical order based on their network IP addresses. IP Address Translation TablePart of the IP Group. This table is a superset of the Address Translation Table. It provides the additional capability to delete entries from the ARP cache. TCP Connection TablePart of the TCP Group. This table accesses the pool of TCP sockets. It provides the capability to set connections to the closed state. All further API calls will return errors, at which time the application needs to call closesocket or xn_abort to free the resources. When traversing the TCP Connection Table via GetNextRequest commands, the entries are returned in lexical order of their IP source address, source port, IP destination address, and destination port. UDP Listener TablePart of the UDP Group. This table accesses the pool of UDP sockets. When traversing the UDP Listener Table via GetNextRequest commands, the entries are accessed in lexical order of their IP source address and source port.
|