SNMP C
OMMANDS
4-145
multiple hosts, you must issue a separate
snmp-server host
command
for each host.
• The
snmp-server host
command is used in conjunction with the
snmp-server enable traps
command. Use the
snmp-server enable
traps
command to enable the sending of traps or informs and to specify
which SNMP notifications are sent globally. For a host to receive
notifications, at least one
snmp-server enable traps
command and the
snmp-server host
command for that host must be enabled.
• Some notification types cannot be controlled with the
snmp-server
enable traps
command. For example, some notification types are always
enabled.
• Notifications are issued by the switch as trap messages by default. The
recipient of a trap message does not send a response to the switch. Traps
are therefore not as reliable as inform messages, which include a request
for acknowledgement of receipt. Informs can be used to ensure that
critical information is received by the host. However, note that informs
consume more system resources because they must be kept in memory
until a response is received. Informs also add to network traffic. You
should consider these effects when deciding whether to issue
notifications as traps or informs.
To send an inform to a SNMPv2c host, complete these steps:
1.
Enable the SNMP agent (page 4-140).
2.
Allow the switch to send SNMP traps; i.e., notifications (page 4-146).
3.
Specify the target host that will receive inform messages with the
snmp-server host
command as described in this section.
4.
Create a view with the required notification messages (page 4-150).
5.
Create a group that includes the required notify view (page 4-152).
To send an inform to a SNMPv3 host, complete these steps:
1.
Enable the SNMP agent (page 4-140).
2.
Allow the switch to send SNMP traps; i.e., notifications (page 4-146).
3.
Specify the target host that will receive inform messages with the
snmp-server host
command as described in this section.
4.
Create a view with the required notification messages (page 4-150).
5.
Create a group that includes the required notify view (page 4-152).
6.
Specify a remote engine ID where the user resides (page 4-147).
Содержание 8724ML3 - annexe 1
Страница 2: ......
Страница 26: ...TABLE OF CONTENTS xxvi ...
Страница 64: ...MANAGING SYSTEM FILES 2 18 ...
Страница 366: ...CONFIGURING THE SWITCH 3 302 Web Click Routing Protocol RIP Statistics Figure 3 132 RIP Statistics ...
Страница 400: ...CONFIGURING THE SWITCH 3 336 ...
Страница 798: ...SOFTWARE SPECIFICATIONS A 6 ...
Страница 802: ...TROUBLESHOOTING B 4 ...
Страница 812: ...GLOSSARY Glossary 10 ...
Страница 818: ...INDEX Index 6 ...
Страница 819: ......