![SMC Networks 7824M/FSW - annexe 1 Management Manual Download Page 434](http://html.mh-extra.com/html/smc-networks/7824m-fsw-annexe-1/7824m-fsw-annexe-1_management-manual_1300676434.webp)
SNMP C
OMMANDS
20-8
• 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 20-2).
2.
Allow the switch to send SNMP traps; i.e., notifications
(page 20-9).
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 20-13).
5.
Create a group that includes the required notify view (page 20-15).
To send an inform to a SNMPv3 host, complete these steps:
1.
Enable the SNMP agent (page 20-2).
2.
Allow the switch to send SNMP traps; i.e., notifications
(page 20-9).
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 20-13).
5.
Create a group that includes the required notify view (page 20-15).
6.
Specify a remote engine ID where the user resides (page 20-10).
7.
Then configure a remote user (page 20-18).
• The switch can send SNMP Version 1, 2c or 3 notifications to a host
IP address, depending on the SNMP version that the management
station supports. If the
snmp-server host
command does not specify
the SNMP version, the default is to send SNMP version 1
notifications.
• If you specify an SNMP Version 3 host, then the community string is
interpreted as an SNMP user name. If you use the V3 “auth” or “priv”
options, the user name must first be defined with the
snmp-server
Summary of Contents for 7824M/FSW - annexe 1
Page 2: ......
Page 24: ...TABLE OF CONTENTS xxiv ...
Page 28: ...TABLES xxviii ...
Page 32: ...FIGURES xxxii Figure 16 3 DNS Cache 16 7 ...
Page 34: ...GETTING STARTED ...
Page 46: ...SYSTEM DEFAULTS 1 12 ...
Page 62: ...SWITCH MANAGEMENT ...
Page 74: ...CONFIGURING THE SWITCH 3 12 ...
Page 112: ...BASIC MANAGEMENT TASKS 4 38 ...
Page 168: ...USER AUTHENTICATION 6 30 ...
Page 223: ...SHOWING PORT STATISTICS 9 33 Figure 9 12 Port Statistics ...
Page 230: ...ADDRESS TABLE SETTINGS 10 6 ...
Page 304: ...CLASS OF SERVICE 13 16 ...
Page 316: ...QUALITY OF SERVICE 14 12 ...
Page 338: ...MULTICAST FILTERING 15 22 ...
Page 346: ...DOMAIN NAME SERVICE 16 8 ...
Page 348: ...COMMAND LINE INTERFACE IP Interface Commands 35 1 ...
Page 362: ...OVERVIEW OF COMMAND LINE INTERFACE 17 14 ...
Page 494: ...USER AUTHENTICATION COMMANDS 21 48 ...
Page 514: ...CLIENT SECURITY COMMANDS 22 20 ...
Page 540: ...ACCESS CONTROL LIST COMMANDS 23 26 ...
Page 558: ...INTERFACE COMMANDS 24 18 ...
Page 576: ...MIRROR PORT COMMANDS 26 4 ...
Page 582: ...RATE LIMIT COMMANDS 27 6 ...
Page 616: ...SPANNING TREE COMMANDS 29 28 ...
Page 644: ...VLAN COMMANDS 30 28 ...
Page 664: ...CLASS OF SERVICE COMMANDS 31 20 ...
Page 678: ...QUALITY OF SERVICE COMMANDS 32 14 ...
Page 720: ...APPENDICES ...
Page 726: ...SOFTWARE SPECIFICATIONS A 6 ...
Page 730: ...TROUBLESHOOTING B 4 ...
Page 746: ...INDEX Index 6 ...
Page 747: ......