snmp-server host
Defines hosts to which SNMP traps and informs should be sent.
snmp-server host <address>
[ traps | informs ]
[ version {1 | 2c} ]
<community-string>
[ udp-port <port> ]
[ <family> ... ]
no snmp-server host <address> <community-string>
- address--hostname or IP address in dotted decimal format (a.b.c.d) of destination
- community-string--access string on host
- port--UDP port on host
- family--trap family; can be one or more of the following:
- ifmib
- v2mib
- pcmib
- pcmib-verbose
Must be in configuration (config) mode, which requires privileged-level access.
Available for use multiple times in the configuration.
No notifications unless configured.
If informs keyword not specified, traps is assumed.
version 1
port--162
If family is not specified, all trap families that have been enabled are sent to the specified host
The snmp-server host command works in conjunction with the snmp-server enable traps and snmp-server informs commands to send traps and informs to remote hosts.
If community-string is set to a value that has not been defined with the snmp-server contact command, it will be defined automatically by CNA.
Multiple family values can be specified, but only one host address per command. You specify which traps are to be sent by naming one or more families. You cannot set individual traps.
Traps (and their descriptions) are:
- v2mib family:
- authenticationFailure--CNA’s SNMP agent has received a request without proper authentication; Avaya has disabled access to the standard MIB variable snmpEnableAuthenTraps to prevent users from turning off the authenticationFailure trap.
- coldStart--The CNA SNMP agent has been re-initialized, signifying a potential change in the configuration.
- ifmib family:
- linkUp--An ethernet interface configured on CNA has been brought up; in this context, link does not refer to a service provider link as used elsewhere in Avaya terminology, but is any configured ethernet interface.
- linkDown--An ethernet interface configured on CNA has been brought down, either by physically disconnecting it or by configuration command; in this context, link does not refer to a service provider link as used elsewhere in Avaya terminology, but is any configured ethernet interface.
- pcmib family:
- rsBgpPeerDown--an CNA-configured BGP peering has gone down.
- rsBgpPeerUp--an CNA-configured BGP peering has been established.
- rsConfigurationChangeTrap--an CNA CLI user has entered config mode.
- rsDeviceShutdownTrap--CNA is being shut down.
- rsEnvMonVoltageTrap--A voltage threshold has been crossed on a module. See snmptrapd in Appendix A: Diagnostics of the CNA Appendices Guide.
- rsEnvonTemperatureTrap--A temperature threshold has been crossed on a module. See snmptrapd in Appendix A: Diagnostics of the CNA Appendices Guide.
- rsImageCopyCompletionTrap--Conveys status at the completion of an image-copy operation; see the copy command.
- rsLinkMeasurementTimeoutTrap--No measurements have been received by a link for the interval specified by the link-measurement-timeout command.
- rsLinkSnmpTrap--The CNA event-manager process has received a service provider link status update from the link polling process. See Chapter 4: Polling Routers of the CNA Advanced Monitoring Guide.
- rsMedicCpuTrap--A CPU resource threshold has been crossed. See host-resources in Appendix A: Diagnostics of the CNA Appendices Guide.
- rsMedicHardDiskTrap--A threshold for hard disk usage has been crossed. See host-resources in Appendix A: Diagnostics of the CNA Appendices Guide.
- rsMedicMemoryTrap--A RAM usage threshold has been crossed. See host-resources in Appendix A: Diagnostics of the CNA Appendices Guide.
- rsMedicRamDiskTrap--A threshold for RAM disk usage has been crossed. See host-resources in Appendix A: Diagnostics of the CNA Appendices Guide.
- rsMedicServiceTrap--A service of the CNA Medic process has received a utilization-threshold trap or is attempting a restart.
- rsStateTransitionTrap--CNA has changed state to or from route-assert mode. Can be due to user configuration, a BGP status failure as defined in Link Outage Control of Chapter 3: Adaptive Path Control in the CNA Adaptive Path Controller Guide, or lack of load data as defined by the polling usage unknown-threshold command.
- pcmib-verbose family:
- rsPrefixLinkActiveProbeBasedOutage--A prefix outage has been detected by the CNA active-probe-based outage-detection process or a previously detected prefix outage has been cleared; see the outage-detection active-probe command.
- rsPrefixLinkSilenceBasedOutageDetectionTrap--A prefix outage has been detected on one of the configured links by the CNA outage-detection process or a previously detected prefix outage has been cleared; see the outage-detection on (deprecated) command.
- rsPrefixTotalSilenceBasedOutageDetectionTrap--A prefix outage has been detected over all links by the CNA outage-detection process or a previously detected prefix outage has been cleared; see the outage-detection total-silence command.
The traps in the v2mib and ifmib families are defined in standard MIBs, RFC1213-MIB-2.txt and interfaces-MIB.txt files respectively. The traps in the pcmib and pcmib-verbose family are defined in the Avaya enterprise MIBs.
The no form of the command disables CNA traps to the specified host.
See the CNA Appendices Guide for more information about SNMP:
