15
Table of Contents
Linksys
STEP 3 Input the unique community string in the Community String field
STEP 4 Optionally, define a notification filter(s) by using the Notification
Filter page
STEP 5 Configure the notification recipients on the Notification Recipients
SNMPv1,2 page
If you decide to use SNMPv3:
STEP 1 Define the SNMP engine by using the Engine ID page Either create a
unique Engine ID or use the default Engine ID Applying an Engine ID
configuration clears the SNMP database
STEP 2 Optionally, define SNMP view(s) by using the Views page This limits
the range of OIDs available to a community or group
STEP 3 Define groups by using the Groups page
STEP 4 Define users by using the SNMP Users page, where they can be
associated with a group If the SNMP Engine ID is not set, then users
may not be created
STEP 5 Optionally, define a notification filter(s) by using the Notification
Filter page
STEP 6 Define a notification recipient(s) by using the Notification Recipients
SNMPv3 page
Model OIDs
The following are the device model Object IDs (OIDs):
Mode Name Description
Object ID
LGS308
8-Port Smart Gigabit Switch
enterprises(1) linksys(3955)
smb(1000) 3 8 1
LGS318
18-PortSmartGigabit Switch
enterprises(1) linksys(3955)
smb(1000) 3 18 1
LGS326
24-Port Smart Gigabit Switch
enterprises(1) linksys(3955)
smb(1000) 3 26 1
LGS308P
8-Port Smart Gigabit PoE Switch enterprises(1) linksys(3955)
smb(1000) 3 8 2
LGS318P
16-Port Smart Gigabit PoE Switch enterprises(1) linksys(3955)
smb(1000) 3 18 2
LGS326P
24-Port Smart Gigabit PoE Switch enterprises(1) linksys(3955)
smb(1000) 3 26 2
The private Object IDs are placed under:
enterprises(1) linksys(3955) smb(1000) switch01(201)
Feature Configuration
The Engine ID is used by SNMPv3 entities to uniquely identify them An SNMP
agent is considered an authoritative SNMP engine This means that the agent
responds to incoming messages (Get, GetNext, GetBulk, Set) and sends trap
messages to a manager The agent’s local information is encapsulated in fields
in the message
Each SNMP agent maintains local information that is used in SNMPv3 message
exchanges The default SNMP Engine ID is comprised of the enterprise
number and the default MAC address This engine ID must be unique for the
administrative domain, so that no two devices in a network have the same
engine ID
Local information is stored in four MIB variables that are read-only
(snmpEngineId, snmpEngineBoots, snmpEngineTime, and
snmpEngineMaxMessageSize)
CAUTION:
When the engine ID is changed, all configured users and groups are erased
To configure SNMP:
STEP 1 Click Configuration > System Management > Feature Configuration
STEP 2 Enter the following fields:
•
SNMP—Select to enable SNMP
•
Authentication Notification—Select to enable SNMP authentication
failure notification
•
SNMP Notification—Select to enable SNMP notifications
•
Local SNMPv3 Engine ID—Configure the engine The options are:
•
Use Default—Select to use the device-generated engine ID The
default engine ID is based on the device MAC address, and is defined
per standard as:
