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

Configuring SNMP notifications

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 80 highlights

and the log buffer. The total output size for the node field (MIB node name) and the value field (value of the MIB node) in each log entry is 1024 bytes. If this limit is exceeded, the information center truncates the data in the fields. For more information about the information center, see "Configuring the information center." To configure SNMP logging: Step 1. Enter system view. 2. Enable SNMP logging. Command system-view snmp-agent log { all | get-operation | set-operation } Remarks N/A By default, SNMP logging is disabled. Configuring SNMP notifications The SNMP Agent sends notifications (traps and informs) to inform the NMS of significant events, such as link state changes and user logins or logouts. Unless otherwise stated, the trap keyword in the command line includes both traps and informs. Enabling SNMP notifications Enable an SNMP notification only if necessary. SNMP notifications are memory-intensive and may affect device performance. To generate linkUp or linkDown notifications when the link state of an interface changes, you must enable linkUp or linkDown notification 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 notification for a module, whether the module generates notifications also depends on the configuration of the module. For more information, see the configuration guide for each module. To enable SNMP traps: Step 1. Enter system view. 2. Enable notifications globally. 3. Enter interface view. Command Remarks system-view N/A snmp-agent trap enable [ bgp | configuration | ospf [ authentication-failure | bad-packet | config-error | grhelper-status-change | grrestarter-status-change | if-state-change | lsa-maxage | lsa-originate | lsdb-approaching-overflow | lsdb-overflow | neighbor-state-change | nssatranslator-status-change | retransmit | virt-authentication-failure | virt-bad-packet | virt-config-error | virt-retransmit | virtgrhelper-status-change | virtif-state-change | virtneighbor-state-change ] * | standard [ authentication | coldstart | linkdown | linkup | warmstart ] * | system ] By default, all the traps are enabled globally. interface interface-type interface-number N/A 74

  • 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
74
and the log buffer. The total output size for the node field (MIB node name) and the value field (value of
the MIB node) in each log entry is 1024 bytes. If this limit is exceeded, the information center truncates
the data in the fields. For more information about the information center, see "
Configuring the
information center
."
To configure SNMP logging:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enable SNMP logging.
snmp-agent log
{
all
|
get-operation
|
set-operation
}
By default, SNMP logging is
disabled.
Configuring SNMP notifications
The SNMP Agent sends notifications (traps and informs) to inform the NMS of significant events, such as
link state changes and user logins or logouts. Unless otherwise stated, the
trap
keyword in the command
line includes both traps and informs.
Enabling SNMP notifications
Enable an SNMP notification only if necessary. SNMP notifications are memory-intensive and may affect
device performance.
To generate linkUp or linkDown notifications when the link state of an interface changes, you must
enable linkUp or linkDown notification 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 notification for a module, whether the module generates notifications also depends
on the configuration of the module. For more information, see the configuration guide for each module.
To enable SNMP traps:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enable
notifications
globally.
snmp-agent
trap
enable
[
bgp
|
configuration
|
ospf
[
authentication-failure
|
bad-packet
|
config-error
|
grhelper-status-change
|
grrestarter-status-change
|
if-state-change
|
lsa-maxage
|
lsa-originate
|
lsdb-approaching-overflow
|
lsdb-overflow
|
neighbor-state-change
|
nssatranslator-status-change
|
retransmit
|
virt-authentication-failure
|
virt-bad-packet
|
virt-config-error
|
virt-retransmit
|
virtgrhelper-status-change
|
virtif-state-change
|
virtneighbor-state-change
] * |
standard
[
authentication
|
coldstart
|
linkdown
|
linkup
|
warmstart
] * |
system
]
By default, all the
traps are enabled
globally.
3.
Enter interface
view.
interface
interface-type interface-number
N/A