[no] snmp-trap-group log-id
config>log
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure a group of SNMP trap receivers and their operational parameters for a specific log-id.
A group specifies the types of SNMP traps and the log ID that will receive the group of SNMP traps. A trap group must be configured for SNMP traps to be sent.
To suppress the generation of all alarms and traps, see the event-control command. To suppress alarms and traps that are sent to this log-id, see the filter command. When alarms and traps are generated, they can be directed to one or more SNMP trap groups. Logger events that can be forwarded as SNMP traps are always defined on the main event source.
The no form of this command deletes the SNMP trap group.
Specifies the log ID value of a log configured in the log-id context. Alarms and traps cannot be sent to the trap receivers until a valid log-id exists.
snmp-dying-gasp primary trap-target-group-num trap-target-name [secondary {trap-target-group-num trap-target-name} [tertiary {trap-target-group-num trap-target- name}]]
no snmp-dying-gasp
config>log
Supported on all 7210 SAS platforms as described in this document, except the 7210 SAS-Dxp 16p and 7210 SAS-Dxp 24p
This command notifies the SNMP trap server about node power failure. On power failure, the system sends dying gasp traps to the configured SNMP trap servers. Up to three SNMP trap servers can be configured to receive the trap. The traps are sent in the following order:
primary SNMP trap receiver
Secondary SNMP trap receiver
tertiary SNMP trap receiver
When this command is enabled, the node does not generate EFM OAM dying gasp message even if EFM OAM is enabled. That is, generation of an SNMP dying gasp trap is mutually exclusive to the use of an EFM OAM dying gasp message.
By default, the system generates an EFM OAM dying gasp message to remain compatible with earlier versions of the software releases. The user must explicitly configure the system to send out an SNMP trap on loss of power to the node using this command.
Typically, SNMP traps are generated only if the user configures a log to direct the system log events to SNMP. For an SNMP dying gasp trap, it is not required to do so. The DSCP value used by a SNMP dying gasp packet is AF (Assured Forwarding class, value 22).
The system IP address must be configured. The node uses this address to generate dying gasp traps. If It is not configured, SNMP dying gasp traps are not generated.
When sending out SNMP dying gasp traps, one of the available routes in either the management routing instance or the base routing instance is used to resolve the next-hop gateway IP address to reach the trap-server destinations configured under primary, secondary, and tertiary trap targets. The route to the destination is always searched first in the management routing instance and if not found, the routes in the base routing instance is looked up. Configuration of route preference does not change this behavior (that is, the order of route lookup does not change).
The no form of this command disables generation of SNMP trap messages. It enables generation of EFM OAM dying gasp on access-uplink ports, if EFM OAM is enabled on those ports. The generation of SNMP dying gasp traps is disabled by default.
no snmp-dying-gasp
Specifies the primary SNMP trap receiver to which the system addresses the SNMP trap. The trap-target-group-num must correspond to one of the SNMP trap groups configured in the config>log>snmp-trap-group trap-num command. The trap-target-name must correspond to one of the SNMP trap receiver targets configured under config>log>snmp-trap-group trap-num trap-target target-name.
Specifies the secondary SNMP trap receiver to which the system addresses the SNMP trap. The trap-target-group-num must correspond to one of the SNMP trap groups configured under config>log>snmp-trap-group trap-num. The trap-target-name must correspond to one of the SNMP trap receiver target configured under config>log>snmp-trap-group trap-num trap-target target-name.
Specifies the tertiary SNMP trap receiver to which the system addresses the SNMP trap. The trap-target-group-num must correspond to one of the SNMP trap group configuration under config>log>snmp-trap-group trap-num. The trap-target-name must correspond to one of the SNMP trap receiver target configured under config>log>snmp-trap-group trap-num trap-target target-name.
Specifies the trap target group number, expressed as a decimal integer.
Specifies the trap target name, up to 28 characters.
trap-target name [address ip-address] [port port] [snmpv1 | snmpv2c | snmpv3] notify-community communityName | snmpv3SecurityName [security-level {no-auth-no-privacy | auth-no-privacy | privacy}] [replay]
no trap-target name
config>log>snmp-trap-group
Supported on all 7210 SAS platforms as described in this document
This command adds or modifies a trap receiver and configures the operational parameters for the trap receiver. A trap reports significant events that occur on a network device such as errors or failures.
Before an SNMP trap can be issued to a trap receiver, the log-id, snmp-trap-group, and at least one trap-target must be configured.
The trap-target command is used to add or remove a trap receiver from an snmp-trap-group. The operational parameters specified in the command include the following:
IP address of the trap receiver
UDP port used to send the SNMP trap
SNMP version
SNMP community name for SNMPv1 and SNMPv2c receivers
security name and level for SNMPv3 trap receivers
A single snmp-trap-group log-id can have multiple trap receivers. Each trap receiver can have different operational parameters.
An address can be configured as a trap receiver more than once, as long as a different port is used for each instance.
To prevent resource limitations, only configure a maximum of 10 trap receivers.
If the same trap-target name port port parameter value is specified in more than one SNMP trap group, each trap destination should be configured with a different notify-community value. This allows a trap receiving an application, such as NMS, to reconcile a separate event sequence number stream for each 7210 SAS event log when multiple event logs are directed to the same IP address and port destination.
The no form of this command removes the SNMP trap receiver from the SNMP trap group.
Specifies the name of the trap target up to 28 characters.
Specifies the IP address of the trap receiver in dotted decimal notation. Only one IP address destination can be specified per trap destination group.
Specifies the destination UDP port used to send traps to the destination, expressed as a decimal integer. Only one port can be specified per trap-target statement. If multiple traps must be issued to the same address, multiple ports must be configured.
Specifies the SNMP version format to use for traps sent to the trap receiver.
The keyword snmpv1 selects the SNMP version 1 format. When specifying snmpv1, the notify-community must be configured for the correct SNMP community string that the trap receiver expects to be present in alarms and traps messages. If the SNMP version is changed from snmpv3 to snmpv1, the notify-community parameter must be changed to reflect the community string instead of the security-name that is used by snmpv3.
The keyword snmpv2c selects the SNMP version 2c format. When specifying snmpv2c, the notify-community must be configured for the correct SNMP community string that the trap receiver expects to be present in alarms and traps messages. If the SNMP version is changed from snmpv3 to snmpv2c, the notify-community parameter must be changed to reflect the community string instead of the security-name that is used by snmpv3.
The keyword snmpv3 selects the SNMP version 3 format. When specifying snmpv3, the notify-community must be configured for the SNMP security-name. If the SNMP version is changed from snmpv1or snmpv2c to snmpv3, the notify-community parameter must be changed to reflect the security-name instead of the community string used by snmpv1 or snmpv2c.
The following pre-existing conditions are checked before the snmpv3SecurityName is accepted.
The username must be configured.
The v3 access group must be configured.
The v3 notification view must be configured.
Specifies the community string for the snmpv1, snmpv2c, or snmpv3 security-name. If no notify-community is configured, no alarms nor traps are issued for the trap destination. If the SNMP version is modified, the notify-community must be changed to the correct form for the SNMP version.
Specifies the community string as required by the snmpv1 or snmpv2c trap receiver. The community string can be an ASCII string up to 31 characters in length.
Specifies the security-name as defined in the config>system>security>user context for SNMPv3. The security-name can be an ASCII string up to 31 characters.
Specifies the required authentication and privacy levels required to access the views configured on this node when configuring an snmpv3 trap receiver.
The keyword no-auth-no-privacy specifies that no authentication and no privacy (encryption) are required.
The keyword auth-no-privacy specifies that authentication is required, but no privacy (encryption) is required. When this option is configured the security-name must be configured for authentication.
The keyword privacy specifies that both authentication and privacy (encryption) is required. When this option is configured the security-name must be configured for authentication and privacy.
Enables replay of missed events to target. If replay is applied to an SNMP trap target address, the address is monitored for reachability. Reachability is determined by whether there is a route in the routing table by which the target address can be reached. Before sending a trap to a target address, the SNMP module asks the PIP module if there is either an in-band or out-of-band route to the target address.
If there is no route to the SNMP target address, the SNMP module saves the sequence ID of the first event that is missed by the trap target. When the routing table changes again so that there is now a route by which the SNMP target address can be reached, the SNMP module replays (for example, retransmits) all events generated to the SNMP notification log while the target address was removed from the route table.
The route table changes the convergence time so it is possible that one or more events may be lost at the beginning or end of a replay sequence.