
FL SWITCH MM HS
4-42
PHOENIX CONTACT
6874_en_16
4.3
Simple Network Management Protocol (SNMP)
4.3.1
General function
SNMP is a manufacturer-independent standard for Ethernet management. It defines
commands for reading and writing information and defines formats for error and status
messages. SNMP is also a structured model, which comprises agents and their relevant
MIB (Management Information Base) and a manager. The manager is a software tool, which
is executed on a network management station. The agents are located inside switches, bus
terminals, routers, and other devices that support SNMP. The task of the agents is to collect
and provide data in the MIB. The manager regularly requests and displays this information.
The devices can be configured by writing data from the manager to the MIB. In the event of
an emergency, the agents can also send messages (traps) directly to the manager.
SNMP interface
All managed Factory Line components have an SNMP agent. This agent of an
FL SWITCH MM HS manages Management Information Base II (MIB 2) according to
RFC1213, RMON MIB, bridge MIB, If MIB, Etherlike MIB, Iana-address-family MIB,
IANAifType MIB, SNMPv2 MIB, SNMP-FRAMEWORK MIB, P bridge MIB, Q bridge MIB,
RSTP MIB, LLDP MIB, pnoRedundancy MIB, and private SNMP objects from Phoenix
Contact (FL-SWITCH-M MIB).
Network management stations, such as a PC with the Factory Manager, can read and
modify configuration and diagnostic data from network devices via the Simple Network
Management Protocol (SNMP). In addition, any SNMP tools or network management tools
can be used to access Factory Line products via SNMP. The MIBs supported by the
relevant device must be made available to the SNMP management tools.
On the one hand, these are globally valid MIBs, which are specified and described in RFCs
(Request for Comments). This includes, for example, MIB2 according to RFC1213, which
is supported by all SNMP-compatible network devices. On the other hand, manufacturers
can specify their own private SNMP objects, which are then assigned to a private
manufacturer area in the large SNMP object tree. Manufacturers are then responsible for
their own private (enterprise) areas, i.e., they must ensure that only one object is assigned
to an object ID (object name and parameters) and can be published. If an object is no longer
needed, it can be labeled as "expired", but it cannot be reused with other parameters under
any circumstances.
Phoenix Contact provides notification of ASN1 SNMP objects by publishing their
descriptions on the Internet.
All configuration modifications, which are to take effect after a MMS/MCS restart, must be
saved permanently using the "flWorkFWCtrlConfSave" object.
RSPSupply - 1-888-532-2706 - www.RSPSupply.com
http://www.RSPSupply.com/p-14178-Phoenix-Contact-2832357-FL-IF-2TX-VS-RJ-D-Media-Module-for-Modular-Switch.aspx