Visara LINCS Features - Manual (Page 137)

127
Chapter 10. Management Features
707021-001
Network elements (the SNMP agent) may inform the network management station (the SNMP
client) of asynchronous events (such as a link going down or coming up) that occur by issuing
a “trap”.
MIB Support
LINCS supports the following MIB object groups:
• System
• Interfaces - includes the CHP, SCC, HSC, ETH, and TRC boards
• Address Translation (AT)
• Internet Protocol (IP)
• Internal Control Message Protocol (ICMP)
• Transmission Control Protocol (TCP)
• User Datagram Protocol (UDP)
LINCS does not support the following MIB object groups:
• Transmission
• Exterior Gateway Protocol (EGP)
There are three methods for MIB implementations. First there are single stack, single interface
data bases. Second there are single stack, multiple interface methods used by TCP/IP hosts
that accept traffic from multiple segments of the same network. Third there are multiple interface,
multiple stack methods used by most router type boxes. The method used by the LINCS platform
is most similar to the router implementation. To some SNMP managers with automatic
discovery, a two-interface machine may appear as 2 two-interface machines. System
administrators should take this into account when designing a network topology that includes
a LINCS device with two TCP/IP interfaces on the same network.
LINCS provides support from a single interface MIB to a machine specific, multiple interface
MIB. The MIB II will include all other interfaces installed in the machine. In addition, the
LINCS provides SNMP agents that contain no enterprise or private MIBs. SNMP MIB II
support on a LINCS device is available if TCP/IP is configured on at least one line. Trap
support is enabled if the SNMP Trap IP Address is configured for at least one line.
The MIB II feature provides machine-wide SNMP support for all interfaces in a LINCS
platform. No configuration information will be required, however it should be noted that only
one interface is necessary to support an IP trap address, because traps will now be sent for
machine-wide events.
SNMP Traps
The following SNMP traps (asynchronous) are supported:
• authentication - Authentication traps will be sent when an SNMP manager fails to utilize
appropriate authentication for community names. An authentication trap will be sent from
the board that detected the failure if an IP trap address is configured on that board, otherwise
no trap will be sent.
• cold start - ColdStart traps will be sent at completion of IML. One coldStart trap will be
sent from each board with a Trap IP address configured.