Brocade Communications Systems Layer 3 Routing Configuration ICX 6650 - Manual (Page 227)

Brocade ICX 6650 Layer 3 Routing Configuration Guide 209
53-1002603-01
Configuring OSPF
To later re-enable the trap feature, enter snmp-server trap ospf.
To disable a specific OSPF trap, enter the command as no snmp-server trap ospf ospf-trap.
These commands are at the OSPF router level of the CLI.
Here is a summary of OSPF traps supported on Brocade routers, their corresponding CLI
commands, and their associated MIB objects from RFC 1850:
• interface-state-change-trap – [MIB object: OspfIfstateChange]
• virtual-interface-state-change-trap – [MIB object: OspfVirtIfStateChange]
• neighbor-state-change-trap – [MIB object:ospfNbrStateChange]
• virtual-neighbor-state-change-trap – [MIB object: ospfVirtNbrStateChange]
• interface-config-error-trap – [MIB object: ospfIfConfigError]
• virtual-interface-config-error-trap – [MIB object: ospfVirtIfConfigError]
• interface-authentication-failure-trap – [MIB object: ospfIfAuthFailure]
• virtual-interface-authentication-failure-trap – [MIB object: ospfVirtIfAuthFailure]
• interface-receive-bad-packet-trap – [MIB object: ospfIfrxBadPacket]
• virtual-interface-receive-bad-packet-trap – [MIB object: ospfVirtIfRxBadPacket]
• interface-retransmit-packet-trap – [MIB object: ospfTxRetransmit]
• virtual-interface-retransmit-packet-trap – [MIB object: ospfVirtIfTxRetransmit]
• originate-lsa-trap – [MIB object: ospfOriginateLsa]
• originate-maxage-lsa-trap – [MIB object: ospfMaxAgeLsa]
• link-state-database-overflow-trap – [MIB object: ospfLsdbOverflow]
• link-state-database-approaching-overflow-trap – [MIB object: ospfLsdbApproachingOverflow
Example
To stop an OSPF trap from being collected, use the CLI command: no trap ospf-trap, at the OSPF
router level of the CLI. To disable reporting of the neighbor-state-change-trap, enter the following
command.
Brocade(config-ospf-router)#no trap neighbor-state-change-trap
Example
To reinstate the trap, enter the following command.
Brocade(config-ospf-router)#trap neighbor-state-change-trap
Syntax: [no] trap ospf-trap
Specifying the types of OSPF Syslog messages to log
You can specify which kinds of OSPF-related Syslog messages are logged. By default, the only
OSPF messages that are logged are those indicating possible system errors. If you want other
kinds of OSPF messages to be logged, you can configure the Brocade device to log them.
For example, to specify that all OSPF-related Syslog messages be logged, enter the following
commands.
Brocade(config)#router ospf
Brocade(config-ospf-router)#log all