Logging neighbor state changes, Configuring ospf network management – H3C Technologies H3C SecPath F1000-E User Manual
Page 436
411
are preferred; if not, the routes in the non-backbone area are preferred to reduce the burden of the
backbone area.
To make them compatible:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter OSPF view.
ospf [ process-id | router-id router-id
| vpn-instance vpn-instance-name ] *
N/A
3.
Enable compatibility with RFC
1583.
rfc1583 compatible
Optional.
Enabled by default.
NOTE:
To avoid routing loops, H3C recommends configuring all the routers to be either compatible or
incompatible with RFC 1583.
Logging neighbor state changes
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter OSPF view.
ospf [ process-id | router-id router-id
| vpn-instance vpn-instance-name ] * N/A
3.
Enable the logging of neighbor
state changes.
log-peer-change
Optional.
Enabled by default.
Configuring OSPF network management
With trap generation enabled, OSPF generates traps to report important events. Traps fall into the
following levels.
•
Level-3—Fault traps
•
Level-4—Alarm traps
•
Level-5—Normal but important traps
•
Level-6—Notification traps
The generated traps are sent to the information center of the device. The output rules of the traps such as
whether to output the traps and the output direction are determined according to the information center
configuration. (For information center configuration, see System Management and Maintenance
Configuration Guide.)
To configure OSPF network management:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Bind OSPF MIB to an OSPF
process.
ospf mib-binding process-id
Optional.
The OSPF process with the
smallest process-id is bound
with OSPF MIB by default.