16/24-Port PoE Switch
©.-------------------'
( 3) Select the port whose connection status is green, and then click Bind button. See
Mll'Hllatll<: PortMa.::Binding POIIMICFillrV'lg
8
BBB Ill 1111
"'
iltl Ill l!ll l!ll 1!11
UIIJIUU 0Ql6llll Ql l!l!FJJQJ
l!IJl!ll jq l"J
Figure 6-23
6.5.3 Port Mac Filtering
Ml( Al.at6" T6Dk: Poo1 MK IM'lt:llng Port Mac Filterin
IEIIBBB
11!11111
,i,
'1;1 '1ilSZIIIIISl
±
UIIJIU U 0111161111 Ql�lllQ1
dllll "'1"1
'
i
'ii
,
____ ,_
Figure 6-24
As it is shown in Figure 6-24 that the function is used to restrict allowed MAC packet under
port, which can prevent counterfeit attack. After the port is configured with the function,
when the port receives packet, it will check if the source MAC address of packet is the
same as the allowed MAC address:
• If it is same, then the packet is considered as legal, and it will continue to implement
follow-up processing;
• If it is different, then the packet is considered as illegal, and it will be discarded.
6.6 SNMP Settings
SNMP network includes two elements: NMS and Agent.
• NMS ( Network Management System) is the SNMP network administrator. It provides
user-friendly interactive interface. It is suitable for the network administrator to complete
the most management work.
• Agent is the object to be managed in the SNMP network. It is to receive, process the
NMS query message. In some urgent situation such as the port status has changed,
Agent can auto send out the alarm information to the NMS.
When NMS manages the device, it pays great attention on some parameters such as port
status, CPU usage rate and etc. All these parameters together are called the Management
Information Base (MIB). These parameter are called the nodes in the MIB. MIB defines the
layers of these nodes and the properties of these objects such as object name, access
rights, data type and etc. Each Agent has its own MIB. All managed devices have their
own MIB file, and compiling these MIB files on the NMS can generate the MIB of each
device. The NMS reads and writes the nodes of the MIB according to the access rights
setup so that it can manage the Agent. Refer to the following figure for the relationship
among NMS, Agent and MIB.
NIIS
Get/Set requests
Get/Set respan•••
end Traps
Figure 6-19
Agent
MIB adopts the tree organization, it consists of many nodes. Each node represents one
managed object. The managed object can use an unique number representing the path
beginning from the root. This number is called Object Identifier (01D). Refer to the following
figure for detailed information. The managed object B can use a series number {1.2.1.1}
to identify. This is the 01D of the managed object.
Root
2
2
1 B
2
5
Figure 6-20
SNMP provides three basic operations to realize the interactive between the NMS and the
Agent:
• Get: NMS uses it to search the value of one or more nodes of the Agent MIB.
• Set: NMS uses it to set the value of one or more nodes of the Agent MIB.
• Trap: NMS uses it to send Trap information to the NMS. The Agent does not require the
NMS to send the responding message and NMS does not respond the Trap information.
SNMPv1 ,SNMPv2 and SNMPv3 all support Trap operation.
SNMP protocol version
Right now, the Agent supports SNMPv1 ,SNMPv2 and SNMPv3.
• SNMPv1 adopts community name to certify. The community name is just like a password,
it Is to restrict the communication between the NMS and Agent. If the NMS community
name and the managed device community name are not the same, the NMS and the
Agent cannot establish the SNMP connection, which means the NMS cannot access the
Agent and the NMS discards the warning information from the Agent.
