HP 6125XLG R2306-HP 6125XLG Blade Switch Network Management and Monitoring Con - Page 81

Configuring the SNMP agent to send notifications to a host, Configuration guidelines

Get HP 6125XLG PDF manuals and user guides View all HP 6125XLG manuals
Add to My Manuals
Save this manual to your list of manuals

Page 81 highlights

Step 4. Enable link state notifications. Command enable snmp trap updown Remarks By default, link state notifications are enabled. Configuring the SNMP agent to send notifications to a host You can configure the SNMP agent to send notifications as traps or informs to a host, typically an NMS, for analysis and management. Traps are less reliable and use fewer resources than informs, because an NMS does not send an acknowledgement when it receives a trap. Configuration guidelines When network congestion occurs or the destination is not reachable, the SNMP agent buffers notifications in a queue. You can configure the queue size and the notification lifetime (the maximum time that a notification can stay in the queue). A notification is deleted when its lifetime expires. When the notification queue is full, the oldest notifications are automatically deleted. You can extend standard linkUp/linkDown notifications to include interface description and interface type, but must make sure that the NMS supports the extended SNMP messages. To send informs, make sure: • The SNMP agent and the NMS use SNMPv2c or SNMPv3. • If SNMPv3 is used, you must configure the SNMP engine ID of the NMS when you configure SNMPv3 basic settings. Also, specify the IP address of the SNMP engine when you create the SNMPv3 user. Configuration prerequisites Configure the SNMP agent with the same basic SNMP settings as the NMS. If SNMPv1 or SNMPv2c is used, you must configure a community name. If SNMPv3 is used, you must configure an SNMPv3 user, a MIB view, and a remote SNMP engine ID associated with the SNMPv3 user for notifications. The SNMP agent and the NMS can reach each other. Configuration procedure To configure the SNMP agent to send notifications to a host: Step 1. Enter system view. Command system-view Remarks N/A 75

  • 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
75
Step
Command
Remarks
4.
Enable link state
notifications.
enable snmp trap updown
By default, link state
notifications are
enabled.
Configuring the SNMP agent to send notifications to a host
You can configure the SNMP agent to send notifications as traps or informs to a host, typically an NMS,
for analysis and management. Traps are less reliable and use fewer resources than informs, because an
NMS does not send an acknowledgement when it receives a trap.
Configuration guidelines
When network congestion occurs or the destination is not reachable, the SNMP agent buffers
notifications in a queue. You can configure the queue size and the notification lifetime (the maximum time
that a notification can stay in the queue). A notification is deleted when its lifetime expires. When the
notification queue is full, the oldest notifications are automatically deleted.
You can extend standard linkUp/linkDown notifications to include interface description and interface
type, but must make sure that the NMS supports the extended SNMP messages.
To send informs, make sure:
•
The SNMP agent and the NMS use SNMPv2c or SNMPv3.
•
If SNMPv3 is used, you must configure the SNMP engine ID of the NMS when you configure
SNMPv3 basic settings. Also, specify the IP address of the SNMP engine when you create the
SNMPv3 user.
Configuration prerequisites
Configure the SNMP agent with the same basic SNMP settings as the NMS. If SNMPv1 or SNMPv2c is
used, you must configure a community name. If SNMPv3 is used, you must configure an SNMPv3 user,
a MIB view, and a remote SNMP engine ID associated with the SNMPv3 user for notifications.
The SNMP agent and the NMS can reach each other.
Configuration procedure
To configure the SNMP agent to send notifications to a host:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A