Enabling the logging of neighbor state changes, Configuring ospfv3 network management – H3C Technologies H3C S5560 Series Switches User Manual
Page 394

378
Step Command
Remarks
3.
Disable interfaces from
receiving and sending
OSPFv3 packets.
silent-interface { interface-type
interface-number | all }
By default, the interfaces are able
to receive and send OSPFv3
packets.
This command disables only the
interfaces associated with the
current process. However, multiple
OSPFv3 processes can disable the
same interface from receiving and
sending OSPFv3 packets.
Enabling the logging of neighbor state changes
With this feature enabled, the router delivers logs about neighbor state changes to its information center,
which processes logs according to user-defined output rules (whether to output logs and where to output).
For more information about the information center, see Network Management and Monitoring
Configuration Guide.
To enable the logging of neighbor state changes:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter OSPFv3 view.
ospfv3 [ process-id | vpn-instance
vpn-instance-name ] *
N/A
3.
Enable the logging of
neighbor state changes.
log-peer-change
By default, this feature is enabled.
Configuring OSPFv3 network management
This task involves the following configurations:
•
Bind an OSPFv3 process to MIB so that you can use network management software to manage the
specified OSPFv3 process.
•
Enable SNMP notifications for OSPFv3 to report important events.
•
Configure the SNMP notification output interval and the maximum number of SNMP notifications
that can be output at each interval.
SNMP notifications are sent to the SNMP module, which outputs SNMP notifications according to the
configured output rules. For more information about SNMP notifications, see Network Management and
Monitoring Configuration Guide.
The standard OSPFv3 MIB provides only single-instance MIB objects. For SNMP to correctly identify
OSPFv3 management information in the standard OSPFv3 MIB, you must configure a unique context
name for OSPFv3. If multiple OSPFv3 processes exist, you must assign a unique context to each process.
Context is a method introduced to SNMPv3 for multiple-instance management. For SNMPv1/v2c, you
must specify a community name as a context name for protocol identification.
To configure OSPFv3 network management: