7210 SAS-MXP, R6, R12, S, SX, T BASIC SYSTEM
CONFIGURATION GUIDE RELEASE 22.9.R1
System management
Use the following syntax to abort or commit changes made to a timing reference.
config>system>sync-if-timing
abort
commit
6.16.6 Forcing a specific reference
You can force the system synchronous timing output to use a specific reference.
Note:
The debug sync-if-timing force-reference command should only be used to test and debug
problems. After the system timing reference input has been forced, it will not revert to another
reference unless explicitly reconfigured, or if the forced reference fails, or if the received QL code
is QL-DNU/DUS and QL selection is enabled.
When the debug sync-if-timing force-reference command is run, the current system synchronous timing
output is immediately referenced from the specified reference input. The reference must be qualified.
Debug configurations are not saved between reboots.
Use the following syntax to reference the current system synchronous timing output from the specifies
reference input.
debug>sync-if-timing
force-reference {ref1 | ref2}
Example
The following example shows the command usage to reference the current system synchronous timing
output from the specifies reference input.
debug>sync-if-timing# force-reference
6.17 Configuring system monitoring thresholds
This section describes how to configure system monitoring thresholds.
6.17.1 Creating events
The event command controls the generation and notification of threshold crossing events configured
with the alarm command. When a threshold crossing event is triggered, the rmon event configuration
optionally specifies whether an entry in the RMON-MIB log table will be created to record the event. It can
also specify whether an SNMP notification (trap) will be generated for the event. There are two notifications
for threshold crossing events; a rising alarm and a falling alarm.ping-address.
Creating an event entry in the RMON-MIB log table does not create a corresponding entry in the 7210 SAS
event logs. However, when the event is set to trap, the generation of a rising alarm or falling alarm
notification creates an entry in the event logs and that is distributed to the configured log destinations,
including console, session, memory, file, syslog, or SNMP trap destination. The logger message includes a
3HE 18197 AAAB TQZZA
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com/terms/.
324
SPACER TEXT
To Next Page
Loading...