Adding or Modifying
SNMP Community Options
SNMP includes a default community named "public." The public
community is assigned write-read-trap access by default. You should change public access
to read-trap and add at least one other community with write-read-trap access.
You can set Community views using the CLI. See Creating and Managing Community MIB Views.
Procedure:
Step |
Action |
1 |
Enter a community name, if a name is not
already there. Use up to 32 alphanumeric characters, not including spaces, tabs, or
Escape key sequences. |
2 |
Select the type of access for the
community:
- Set, Get and Trap: for read and write access and trap generation
- Get and Trap: for read access and trap generation
- Trap: for trap generation only
|
3 |
Select traps to enable for the community:
- Cold Start
- Warm Start
- Link UP
- Link Down
- Auth, Fail
- EGP
- Enterprise
For a description of the traps, see the Field Descriptions.
You can enable zero, one, or more traps for each community.
The UDP port to which traps are sent needs to be set before enabling these traps for
the community. Setting the trap port is accomplished through the CLI. See Setting the Trap Port. |
4 |
Click Apply for community options to take effect. |
Field Descriptions
Community
Name |
Name of the community you want to add or
modify. The community name can contain up to 32 alphanumeric characters and cannot
include spaces, tabs, or Escape key sequences. |
Access |
Type of access for the communmity. You
can assign one of three access types to a community.
Set, Get and Trap sets write and read access and trap generation for the
specified community.
Get and Trap sets read access and trap generation for the specified community.
Trap sets trap generation for the specified community. |
Traps
|
Traps generated for the community. You
can enable no traps, one trap, or more than one trap for a community from those that
follow. |
Cold Start |
Trap generated when the transmitting device
is reinitializing and the agent's configuration or the protocol entity implementation may
be altered. |
Warm Start |
Trap generated when the transmitting device
is reinitializing and the agent's configuration or the protocol entity implementation does
not change. |
Link Up |
Trap generated when a previously inactive network link becomes
active. |
Link Down |
Trap generated when a failure occurs in one of the communication
links represented in the agent's configuration. |
Auth. Fail |
Authentication failure trap. Trap generated when the sending entity
is the addressee of a protocol message that is not properly authenticated. |
EGP |
EGP neighbor loss trap. Traps generated when an EGP neighbor and
peer are marked down and no longer a peer. The egpNeighborLoss trap-PDU contains the
name and value of the egpNeighAddr instance for the affected neighbor as the first element
of its variable bindings. |
Enterprise |
Enterprise-specific trap. Traps generated vary depending on the
event. The Enterprise specific-trap field identifies the particular trap that occurs. |
|