Specifications

Appendix B SNMP Management Installation and Operation Manual
B-4 Handling the Management Traffic FCD-E1LC Ver. 1.0
When an SNMP message is received by the addressed entity, first it checks the
originator's community. If the community name of the message originator differs
from the community name specified for that type of message in the agent, the
message it discarded (SNMP agents of managed entities report this event by
means of an authentication failure trap).
FCD-E1LC Communities
The SNMP agents of FCD-E1LC are programmed to recognize the following
community types:
Read SNMP community that has read-only authorization, i.e., the
SNMP agent will accept only getRequest and getNextRequest
commands from management stations using that community.
Write SNMP community that has read-write authorization, i.e., the
SNMP agent will also accept setRequest commands from
management stations using that community.
Trap SNMP community that the SNMP agent will send within trap
messages.
B.2 SNMP Traps
The FCD-E1LC SNMP agent supports the standard MIB-II traps.
B.3 Handling the Management Traffic
The FCD-E1LC management subsystem includes an SNMP agent.
The SNMP agent receives the management traffic through an internal router. This
router fulfills two main requirements:
• Ensures that the SNMP agent can receive and transmit management traffic
through all the inband and out-of-band management ports of the FCD-E1LC,
in accordance with user’s selections.
• Provides paths that enable management traffic received through one of the
FCD-E1LC ports to reach equipment connected to the other ports, as
explained below.
The following sections explain the way management traffic is handled by the
FCD-E1LC.
The management traffic handling capabilities described below are also applicable
to Telnet traffic.
Configuring the Out-of-Band Communication Mode
Out-of-band management communication uses the CONTROL DCE port.
Note