Configuring OSPFv3 Traps
You can use the traps command to specify OSPFv3 traps. This command enables you to specify all or any number of the following trap settings:
- ospfv3IfStateChange—To indicate a state change on a nonvirtual OSPFv3 interface
- ospfv3VirtIfStateChange—To indicate a state change
on an OSPFv3 virtual interface
Note: This trap is not supported because virtual links are not supported for OSPFv3. A warning message is displayed when this trap is enabled.
- ospfv3NbrStateChange—To indicate a state change on a nonvirtual OSPFv3 neighbor
- ospfv3VirtNbrStateChange—To indicate a state change
on a virtual OSPFv3 neighbor
Note: This trap is not supported because virtual links are not supported for OSPFv3. A warning message is displayed when this trap is enabled.
- ospfv3IfConfigError—To indicate that a packet has been received on a nonvirtual interface from a neighboring router whose configuration parameters conflict with that of the router containing the nonvirtual interface
- ospfv3VirtIfConfigError—To indicate that a packet
has been received on a virtual interface from a neighboring router
whose configuration parameters conflict with that of the router containing
the virtual interface
Note: This trap is not supported because virtual links are not supported for OSPFv3. A warning message is displayed when this trap is enabled.
- ospfv3IfRxBadPacket—To indicate that an OSPFv3 packet that cannot be parsed has been received on a nonvirtual interface
- ospfv3VirtIfRxBadPacket—To indicate that an OSPFv3
packet that cannot be parsed has been received on a virtual interface
Note: This trap is not supported because virtual links are not supported for OSPFv3. A warning message is displayed when this trap is enabled.
- ospfv3LsdbOverflow—To indicate that the number of LSAs in the router's link state database has exceeded ospfv3ExtAreaLsdbLimit
- ospfv3LsdbApproachingOverflow—To indicate that the number of LSAs in the router's link state database has exceeded ninety percent of ospfv3ExtAreaLsdbLimit
- ospfv3NssaTranslatorStatusChange—To indicate a change in the router's ability to translate OSPFv3 NSSA LSAs into OSPFv3 External LSAs
- ospfv3RestartStatusChange—To indicate a change in the graceful restart state of the router
- ospfv3NbrRestartHelperStatusChange—To indicate a change in the graceful restart helper state of the neighbor
- ospfv3VirtNbrRestartHelperStatusChange—To indicate
a change in the graceful restart helper state of the virtual neighbor
Note: This trap is not supported because virtual links are not supported for OSPFv3. A warning message is displayed when this trap is enabled.
traps
- You can use the traps command to specify traps for OSPFv3.
- Example:host1(config-router-rn)#traps all
- Use the no version to delete
the specified trap, group of traps, or all traps.
Note: The following traps are not supported because virtual links are not supported by OSPFv3:
- ospfv3VirtIfStateChange
- ospfv3VirtNbrStateChange
- ospfv3VirtIfConfigError
- ospfv3VirtIfRxBadPacket
- ospfv3VirtNbrRestartHelperStatusChange
A warning message is displayed when these traps are enabled.
- See traps