Modifying Ospf Standard Compliance Setting - HP ProCurve 6200yl Multicast And Routing Manual

N o t e
OSPF Trap Name
originate-lsa-trap
originate-maxage-lsa-trap
link-state-database-overflow-trap
link-state-database-approaching-overflow-trap
Examples:
1. To stop an OSPF trap from being collected, use the following CLI
command:
ProCurve(ospf)# no trap < ospf-trap >
2. To disable reporting of the neighbor-state-change-trap, enter the following
command:
ProCurve(ospf)#no trap neighbor-state-change-trap
3. To reinstate the trap, enter the following command:
ProCurve(ospf)# trap neighbor-state-change-trap
Syntax: [no] snmp-server trap ospf < ospf-trap >

Modifying OSPF Standard Compliance Setting

All routes in an AS should be configured with the same compliance setting. If
any routers in a domain support only RFC 1583, then all routers must be
configured with 1583 compatibility.
If all the routers support RFC 2178 or RFC 2328, you should disable RFC 1583
compatibility on all the routers in the domain, since these standards are more
robust against routing loops on external routes.
The switch is configured, by default, to be compliant with the RFC 1583 OSPF
V2 specification.
To configure a switch to operate with the latest OSPF standard, RFC 2328,
enter the following commands:
ProCurve(config)# router ospf
ProCurve(ospf)# no rfc1583-compatibility
Syntax: [no] rfc1583-compatibility
IP Routing Features
Configuring OSPF
MIB Object
ospfOriginateLsa
ospfMaxAgeLsa
ospfLsdbOverflow
ospfLsdbApproachingOverflow
5-53