HP 6125G HP 6125G & 6125G/XG Blade Switches Network Management and Mon - Page 66

Configuring the SNMP agent to send traps to a host, configuration of the module. For more information

Page 66 highlights

To generate linkUp or linkDown traps when the link state of an interface changes, you must enable the linkUp or linkDown trap function globally by using the snmp-agent trap enable [ standard [ linkdown | linkup ] * ] command and on the interface by using the enable snmp trap updown command. After you enable a trap function for a module, whether the module generates traps also depends on the configuration of the module. For more information, see the configuration guide for each module. To enable traps: Step 1. Enter system view. 2. Enable traps globally. 3. Enter Layer 2 Ethernet interface view, or VLAN interface view. 4. Enable link state traps. Command Remarks system-view N/A snmp-agent trap enable [ bgp | configuration | default-route | flash | ospf [ process-id ] [ ifauthfail | ifcfgerror | ifrxbadpkt | ifstatechange | iftxretransmit | lsdbapproachoverflow | lsdboverflow | maxagelsa | nbrstatechange | originatelsa | vifcfgerror | virifauthfail | virifrxbadpkt | virifstatechange | viriftxretransmit | virnbrstatechange ] * | pim [ candidatebsrwinelection | electedbsrlostelection | interfaceelection | invalidjoinprune | invalidregister | neighborloss | rpmappingchange ] * | standard [ authentication | coldstart | linkdown | linkup | warmstart ] * | system | vrrp [ authfailure | newmaster ] ] By default, all traps are enabled. interface interface-type interface-number N/A enable snmp trap updown By default, the link state traps are enabled. Configuring the SNMP agent to send traps to a host The SNMP module buffers the traps received from a module in a trap queue. You can set the size of the queue, the duration that the queue holds a trap, and trap target (destination) hosts, typically the NMS. To successfully send traps, you must also perform the following tasks: • Complete the basic SNMP settings and verify that they are the same as on the NMS. If SNMPv1 or SNMPv2c is used, you must configure a community name. If SNMPv3 is used, you must configure an SNMPv3 user and MIB view. • Make sure the device and the NMS can reach each other. To configure the SNMP agent to send traps to a host: Step 1. Enter system view. Command system-view Remarks N/A 59

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157

59
To generate linkUp or linkDown traps when the link state of an interface changes, you must enable the
linkUp or linkDown trap function globally by using the
snmp-agent trap enable
[
standard
[
linkdown
|
linkup
] * ] command and on the interface by using the
enable snmp trap updown
command.
After you enable a trap function for a module, whether the module generates traps also depends on the
configuration of the module. For more information, see the configuration guide for each module.
To enable traps:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enable traps
globally.
snmp-agent
trap
enable
[
bgp
|
configuration
|
default-route
|
flash
|
ospf
[
process-id
] [
ifauthfail
|
ifcfgerror
|
ifrxbadpkt
|
ifstatechange
|
iftxretransmit
|
lsdbapproachoverflow
|
lsdboverflow
|
maxagelsa
|
nbrstatechange
|
originatelsa
|
vifcfgerror
|
virifauthfail
|
virifrxbadpkt
|
virifstatechange
|
viriftxretransmit
|
virnbrstatechange
] * |
pim
[
candidatebsrwinelection
|
electedbsrlostelection
|
interfaceelection
|
invalidjoinprune
|
invalidregister
|
neighborloss
|
rpmappingchange
] * |
standard
[
authentication
|
coldstart
|
linkdown
|
linkup
|
warmstart
] * |
system
|
vrrp
[
authfailure
|
newmaster
] ]
By default, all traps are
enabled.
3.
Enter Layer 2
Ethernet interface
view, or VLAN
interface view.
interface
interface-type interface-number
N/A
4.
Enable link state
traps.
enable snmp trap updown
By default, the link
state traps are
enabled.
Configuring the SNMP agent to send traps to a host
The SNMP module buffers the traps received from a module in a trap queue. You can set the size of the
queue, the duration that the queue holds a trap, and trap target (destination) hosts, typically the NMS.
To successfully send traps, you must also perform the following tasks:
Complete the basic SNMP settings and verify that they are the same as on the NMS. If SNMPv1 or
SNMPv2c is used, you must configure a community name. If SNMPv3 is used, you must configure
an SNMPv3 user and MIB view.
Make sure the device and the NMS can reach each other.
To configure the SNMP agent to send traps to a host:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A