10-Extended OAM Configuration
Chapters Download (143.13 KB)
Table of Contents
Configuring Extended OAM Basic Functions
Configuring Extended OAM Discovery Timeout Time
Configuring OUI and extended OAM version number list
Displaying and Maintaining OAM about an ONU
Configuring Extended OAM Alarms
Configuring Alarms on an OLT Port
Configuring Alarms on an ONU Port
Displaying and Maintaining Alarm Configurations
When configuring the Ethernet OAM function, go to these sections for information you are interested in:
l Configuring Extended OAM Basic Functions
l Configuring Extended OAM Alarms
Ethernet OAM (operation, administration, and maintenance) is a tool monitoring Layer-2 link status by sending OAM protocol data units (OAMPDUs) between devices. It helps network administrators manage their networks effectively. Extended OAM adds OAMPDU types based on the Ethernet OAM technology. With the extended OAMPDUs, an OLT and ONUs can send connection requests and responses to each other and the OLT can remotely manage the ONUs.
Throughout this document, a port with Ethernet OAM enabled is called an Ethernet OAM entity or an OAM entity.
Figure 1-1 shows the formats of different types of OAMPDUs.
Figure 1-1 Formats of different types of Ethernet OAMPDUs
The fields in an OAMPDU are described as follows:
Table 1-1 Description of the fields in an OAMPDU
|
Field |
Description |
|
Dest addr |
Destination MAC address of the Ethernet OAMPDU. It is a slow protocol multicast address 0180c2000002. As slow protocol packet cannot be forwarded by bridges, Ethernet OAMPDUs cannot be forwarded. |
|
Source addr |
Source MAC address of the Ethernet OAMPDU. It is the bridge MAC address of the sending side and is a unicast MAC address. |
|
Type |
Type of the encapsulated protocol in the Ethernet OAMPDU. The value is 0x8809. |
|
Subtype |
The specific protocol being encapsulated in the Ethernet OAMPDU. The value is 0x03. |
|
Flags |
Status information of an Ethernet OAM entity. |
|
Code |
Type of the Ethernet OAMPDU |
Table 1-2 shows the function of the three types of OAMPDUs.
Table 1-2 Functions of different types of OAMPDUs
|
OAMPDU type |
Function |
|
Information OAMPDU |
Used for transmitting state information of an Ethernet OAM entity (including the information about the local device and remote devices, and customized information) to the remote Ethernet OAM entity and maintaining OAM connections |
|
Event Notification OAMPDU |
Used by link monitoring to notify the remote OAM entity when it detects problems on the link in between. |
|
Loopback Control OAMPDU |
Used for remote loopback control. By inserting the information used to enable/disable loopback to a loopback control OAMPDU, you can enable/disable loopback on a remote OAM entity. |
Extended OAM adds an Organization Specific Information TLV to the information OAMPDU. For details about information OAMPDUs, refer to Types of OAMPDUs. An information OAMPDU containing this TLV is called an extended information OAMPDU.
The Organization Specific Information TLV contains the following contents:
l Local Organizationally Unique Identifier (OUI): Identifies the vendor of the local device.
l Supported OUI addresses: Specifies the vendors whose devices can interoperate with the local OLT or ONU device.
l OAM version number: Indicates the version of the OAM protocol used by the local OLT or ONU device.
Organization Specific OAMPDU is a newly added OAMPDU type. It is identified by the 0xFE field, as shown in Figure 1-2.
Figure 1-2 Organization Specific OAMPDU format
When you remotely manage ONUs on an OLT device, extended OAM can encapsulate various operation and acknowledgement information in the Data field. The data field consists of the following sub-fields:
l OUI: The OUI address of the transmitting device.
l Ext.Opcode: Extended operation code. Extended OAM uses different codes for identifying the operation types of OAMPDUs, as described in Table 1-3.
Table 1-3 Description on the extended operation codes
|
Code |
Operation type |
Description |
|
0x01 |
Extended Variable Request |
Sent from an OLT to an ONU, carrying the user's query instructions. |
|
0x02 |
Extended Variable Response |
Sent from the ONU to the OLT in response to a query request, carrying the requested information. |
|
0x03 |
Set Request |
Sent from the OLT to the ONU, carrying the user's configuration instructions for the ONU. |
|
0x04 |
Set Response |
Sent from the ONU to the OLT after the ONU finishes the configuration instructed by the user. |
|
0x0A |
DBA (Dynamic Bandwidth Allocation) |
Used for performing DBA configuration and query. |
l Payload: Carries the function codes and configuration contents corresponding to the user’s query or configuration instructions. An OLT can configure the functions shown in Extended OAM management for ONUs.
Extended OAM has two functions: extended OAM discovery and extended OAM management.
First, the OLT and the ONU use standard OAM to judge whether the link in between is normal. If the link is normal, the OLT and the ONU exchanges Extended Information OAMPDUs to inform each other of their OUI addresses, supported OUI addresses, and OAM version numbers. If the OUI address and OAM version of each end can be supported by the other end, the extended OAM discovery process finishes and data transmission starts. Otherwise, the two ends cannot communicate normally.
After finishing extended OAM discovery, the OLT device can remotely configure the ONU by sending Organization Specific OAMPDUs.
The OLT can configure the following functions for the ONU:
l Basic port configurations, including duplex mode, rate, and traffic control.
l VLAN management and configuration
l Multicast
l QoS
l DBA
The OLT can query and configure the functions mentioned above. You can use the related query commands to query the status of a function on the ONU. You can also configure parameters for a function on the OLT, and the OLT will issue the configured parameters to the ONU automatically. The query or configuration command is identified by the Ext.Opcode field in the Organization Specific OAMPDUs. The codes and configurations to be queried or configured are encapsulated in the payload field. For details, refer to Organization Specific OAMPDU.
The extended OAM alarm mechanism falls into sampling and alarming:
l Sampling means the system retrieves statistics data at the sampling interval
l At the alarm monitor interval, the system samples the alarm variables and will trigger an alarm if the value of a variable exceeds its alarm threshold. Alarm information can be output to the network management system or alarm buffer by configuring the information center.
Ethernet OAM is defined in IEEE 802.3h.
On an S3600 Series EPON OLT switch, you need not enable extend OAM manually; instead, extended OAM is enabled on a port automatically when you enable Ethernet OAM on the port.
Extended OAM discovery timeout time refers to the timeout time of extended OAM messages exchanged between an OLT and its ONU during an extended OAM discovery process.
Follow these steps to configure the extended OAM discovery timeout time:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter FTTH view |
ftth |
— |
|
Configure the extended OAM discovery timeout time |
oam-discovery-timeout value slot slot-number |
Optional The unit of measure for this parameter is 100 ms. The default value of this parameter is 30, that is, 3 seconds. |
l You are recommended to use the default value of this parameter.
l If an OLT stays down after being bundled with an ONU port, you can change the extended OAM discovery timeout time to a larger value.
Configuring OUI and extended OAM version number list
Follow these steps to configure OUI and extended OAM version number list.
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter FTTH view |
ftth |
— |
|
Configure OUI and extended OAM version number list |
epon-parameter ouilist { oui oui-value oam-version version-value } &<1-9> slot slot-number |
Optional By default, the OUI and extended OAM version number must be configured as 111111 and 1 respectively. |
|
Display the OAM information about an ONU |
display epon-oam interface interface-type interface-number |
Available in any view |
When the OUI and OAM version number list changes due to addition or removal of user-defined list entry, all ONUs under the board will re-register
|
To do… |
Use the command… |
Remarks |
|
Display the OAM information about an ONU |
display epon-oam interface interface-type interface-number |
Available in any view |
The alarms can be global alarms, OLT port alarms, or ONU port alarms.
l When an alarm configuration command is executed in FTTH view, the command takes effect on all the OLT ports and all the ONUs attached to the OLT ports.
l When an alarm configuration command is executed in OLT port view, the command takes effect on the current OLT port and all the ONUs attached to the OLT port.
When an alarm configuration command is executed in ONU port view, the command takes effect only on the ONU corresponding to the current ONU port.
Complete the following tasks to configure alarms:
|
Task |
Remarks |
|
|
Optional |
||
|
Alarm configuration |
Optional |
|
|
Optional |
||
|
Optional |
||
|
Optional |
||
Alarm monitoring function takes effect only when statistics sampling function is enabled. This is because no alarm information can be generated without the average value of sampled statistics.
Follow these steps to enabling sampling and alarm monitoring function:
|
To do... |
Use the command... |
Remarks |
|
|
Enter system view |
system-view |
— |
|
|
Enter FTTH view |
ftth |
— |
|
|
Configure the statistics sampling function |
Enable the statistics sampling function |
sample enable |
Optional Enabled by default |
|
Configure the statistics sampling interval |
timer sample seconds |
Optional 4 seconds by default |
|
|
Configure the alarm monitoring function |
Enable alarm monitoring function for the system |
monitor enable |
Optional Enabled by default |
|
Configure the alarm monitor period |
timer monitor seconds |
Optional 80 seconds by default |
|
Follow these steps to configure global alarms:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter FTTH view |
ftth |
— |
|
Enable the software error alarm function |
alarm software-error enable |
Optional The system generates a software error alarm when a signal error, Data Access (DA) error, or memory allocation failure occurs. By default, this function is enabled. |
|
Enable the bit error rate alarm function |
alarm bit-error-rate enable |
Optional When the total number of error bits or bit error rate of the data transferred between the OLT and ONUs exceeds the alarm threshold, a bit error rate alarm occurs. By default, this function is enabled. |
|
Configure the monitor direction and threshold for bit error rate alarms |
alarm bit-error-rate { direction { uplink | downlink | up-down-link} | threshold threshold }* |
Optional By default, the monitor direction is up-down-link, and the alarm threshold of bit error rate is 10 (the unit is 10-9). |
|
Enable the port bit error rate alarm function |
alarm port bit-error-rate enable |
Optional When both the total number of error bits and bit error rate of the data transferred between the OLT and ONUs exceed the alarm thresholds, a port bit error rate alarm occurs. By default, this function is enabled. |
|
Enable the device fatal error alarm function |
alarm device-fatal-error enable |
Optional By default, this function is enabled. |
|
Enable the frame error rate alarm function |
alarm frame-error-rate enable |
Optional When the total number of error frames or the error frame rate of the data transferred between the OLT and ONUs exceeds the alarm threshold, a frame error rate alarm occurs. By default, this function is enabled. |
|
Configure the monitor direction and threshold for frame error rate alarms |
alarm frame-error-rate { direction { uplink | downlink | up-down-link} | threshold threshold } * |
Optional By default, the monitor direction is up-down-link, and the threshold of frame error rate alarms is 1 (the unit is 10-9). |
|
Enable the LLID mismatch frame alarm function |
alarm llid-mismatch enable |
Optional The system generates an LLID mismatch frame alarm when the time slots are used in disorder, that is, an ONU uses another ONU's time slot to forward data. By default, this function is disabled. |
|
Configure the threshold for LLID mismatch frame alarms |
alarm llid-mismatch threshold threshold |
Optional By default, the threshold of LLID mismatch alarms is 5000 frames. |
|
Enable the local stable alarm function |
alarm local-stable enable |
Optional The system generates a local stable alarm when an ONU misuse occurs in the system, for example, when an OAM 2.0 ONU and an OAM 3.3 ONU are mixed in the same system. (All ONUs in the same system must adopt the same OAM version). This alarm is generated at the OLT side. By default, this function is enabled. |
|
Enable the critical event alarm function |
alarm oam critical-event enable |
Optional The system generates a critical event alarm when one of the following critical events occurs: local link fault and dying gasp. |
|
Enable the dying gasp alarm function |
alarm oam dying-gasp enable |
Optional The system generates a dying gasp alarm when a system error, a data loading error, or any other nonreversible errors occur. |
|
Enable the error frame period alarm function |
alarm oam error-frame-period enable |
Optional The system generates an error frame period alarm when the number of error frames in a specific period (that is, the window size) exceeds the corresponding predefined threshold. By default, this function is enabled. |
|
Configure the window size and threshold for error frame period alarms |
alarm oam error-frame-period { window window | threshold threshold } * |
Optional When the alarm threshold is set to 0, a lot of alarms are generated immediately. Since alarm events are carried in the OAM packets, a lot of OAM packets are generated. In this case, OAM packets may be lost. By default, the window size is 1 second, and the alarm threshold is 20 frames. |
|
Enable the error frame alarm function |
alarm oam error-frame enable |
Optional The system generates an error frame alarm when the number of error frames in a specific time period (that is, the window size) exceeds the corresponding predefined threshold. By default, this function is enabled. |
|
Configure the window size and threshold for error frame alarms |
alarm oam error-frame { window window | threshold threshold } * |
Optional When the alarm threshold is set to 0, a lot of alarms are generated immediately. Since alarm events are carried in the OAM packets, a lot of OAM packets are generated. In this case, OAM packets may be lost. By default, the window size is 10 seconds, and the alarm threshold is 20 frames. |
|
Enable the error frame seconds summary alarm function |
alarm oam error-frame-seconds-summary enable |
Optional The system generates an error frame seconds summary alarm when the number of error frame seconds (in an error frame second, at least one error frame occurs) in a specific time period (for example, 1 minute) exceeds the corresponding predefined threshold. By default, this function is enabled. |
|
Configure the window size and threshold for error frame seconds summary alarms |
alarm oam error-frame-seconds-summary { window window | threshold threshold } * |
Optional By default, the window size is 600 (in unit of 100 ms), and the alarm threshold is 1 second. |
|
Enable the error symbol period alarm function |
alarm oam error-symbol-period enable |
Optional The system generates an error symbol period alarm when the number of error frames in a specific period (that is, the window size) exceeds the corresponding predefined threshold. By default, this function is enabled. |
|
Configure the window size and thresholds for error symbol period alarms |
alarm oam error-symbol-period { window-high windowhigh | window-low windowlow | threshold-high thresholdhigh | threshold-low thresholdlow } * |
Optional When both the upper limit and the lower limit of the alarm threshold are set to 0, a lot of alarms are generated immediately. Since alarm events are carried in the OAM packets, a lot of OAM packets are generated. In this case, OAM packets may be lost. The window size and threshold values specified in this command comprise two parts, the significant part and the insignificant part, both of which are 16 bits in length. By default, the window size is 1 second, and the alarm threshold is 20 bytes. |
|
Enable the local link fault alarm function |
alarm oam local-link-fault enable |
Optional The system generates a local link fault alarm when the inbound direction of the local data terminal becomes faulty. |
|
Enable the registration error alarm function |
alarm registration-error enable |
Optional The system generates a registration error alarm when an error occurs during the registration of an ONU. By default, this function is enabled. |
|
Enable the remote stable alarm function |
alarm remote-stable enable |
Optional The system generates a remote stable alarm when an ONU misuse occurs in the system, for example, when an OAM 2.0 ONU and an OAM 3.3 ONU are mixed in the same system. (All ONUs in the same system must adopt the same OAM version). This alarm is generated at the ONU side and will be reported to the OLT. By default, this function is enabled. |
|
Enable the OAM vendor-specific alarm function |
alarm oam-vendor-specific enable |
Optional This alarm is customized by vendors. By default, this function is enabled. |
|
Enable the ONU over limitation alarm function |
alarm onu-over-limitation enable |
Optional The system generates an ONU over limitation alarm when the total number of ONUs connected with the OLT exceeds the limit. By default, this function is enabled. |
Follow these steps to configure alarms on an OLT port:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter OLT port view |
interface olt interface-number |
— |
|
Enable the bit error rate alarm function |
alarm bit-error-rate enable |
Optional The system generates a bit error rate alarm when the total number of error bits or bit error rate of the data transferred between the OLT and ONUs exceeds the alarm threshold. By default, this function is enabled. |
|
Configure the monitor direction and threshold for bit error rate alarms |
alarm bit-error-rate { direction { uplink | downlink | up-down-link} | threshold threshold }* |
Optional By default, the monitor direction is up-down-link, and the threshold of bit error rate alarms is 10 (the unit is 10-9). |
|
Enable the port bit error rate alarm function |
alarm port bit-error-rate enable |
Optional When both the total number of error bits and bit error rate of the data transferred between the OLT and ONUs exceed the alarm thresholds, a port bit error rate alarm occurs. By default, this function is enabled. |
|
Enable the device fatal error alarm function |
alarm device-fatal-error enable |
Optional By default, this function is enabled. |
|
Enable the frame error rate alarm function |
alarm frame-error-rate enable |
Optional When the total number of error frames or the error frame rate of the data transferred between the OLT and ONUs exceeds the alarm threshold, a frame error rate alarm occurs. By default, this function is enabled. |
|
Configure the monitor direction and threshold for frame error rate alarms |
alarm frame-error-rate { direction { uplink | downlink | up-down-link } | threshold threshold } * |
Optional By default, the monitor direction is up-down-link, and the threshold of frame error rate alarms is 1 (the unit is 10-9). |
|
Enable the LLID mismatch frame alarm function |
alarm llid-mismatch enable |
Optional The system generates an LLID mismatch frame alarm when the time slots are used in disorder, that is, when an ONU uses another ONU's time slot to forward data. By default, this function is disabled. |
|
Configure the threshold of LLID mismatch frame alarms |
alarm llid-mismatch threshold threshold |
Optional 5000 frames by default |
|
Enable the local stable alarm function |
alarm local-stable enable |
Optional The system generates a local stable alarm when an ONU misuse occurs in the system, for example, when an OAM 2.0 ONU and an OAM 3.3 ONU are mixed in the same system. (All ONUs in the same system must adopt the same OAM version). A local stable alarm is generated by the OLT side. By default, this function is enabled. |
|
Enable the critical event alarm function |
alarm oam critical-event enable |
Optional The system generates a critical event alarm when one of the following critical events occurs: local link fault and dying gasp. |
|
Enable the dying gasp alarm function |
alarm oam dying-gasp enable |
Optional The system generates a dying gasp alarm when a system error, a data loading error or any other nonreversible error occurs. |
|
Enable the error frame period alarm function |
alarm oam error-frame-period enable |
Optional The system generates an error frame period alarm when the number of error frames in a specific period (that is, the window size) exceeds the corresponding predefined threshold. By default, this function is enabled. |
|
Configure the window size and threshold for error frame period alarms |
alarm oam error-frame-period { window window | threshold threshold } * |
Optional When the alarm threshold is set to 0, a lot of alarms are generated immediately. Since alarm events are carried in the OAM packets, a lot of OAM packets are generated. In this case, OAM packets may be lost. By default, the window size is 1 second, and the alarm threshold is 20 frames. |
|
Enable the error frame alarm function |
alarm oam error-frame enable |
Optional The system generates an error frame alarm when the number of error frames in a specific time period (that is, the window size) exceeds the corresponding predefined threshold. By default, this function is enabled. |
|
Configure the window size and threshold for error frame alarms |
alarm oam error-frame { window window | threshold threshold } * |
Optional When the alarm threshold is set to 0, a lot of alarms are generated immediately. Since alarm events are carried in the OAM packets, a lot of OAM packets are generated. In this case, OAM packets may be lost. By default, the window size is 10 seconds, and the alarm threshold is 20 frames. |
|
Enable the error frame seconds summary alarm function |
alarm oam error-frame-seconds-summary enable |
Optional The system generates an error frame seconds summary alarm when the number of error frame seconds (in an error frame second, at least one error frame occurs) in a specific time period (for example, 1 minute) exceeds the corresponding predefined threshold. By default, this function is enabled. |
|
Configure the window size and threshold for error frame seconds summary alarms |
alarm oam error-frame-seconds-summary { window window | threshold threshold } * |
Optional By default, the window size is 600 (in unit of 100 ms), and the alarm threshold is 1 second. |
|
Enable the error symbol period alarm function |
alarm oam error-symbol-period enable |
Optional The system generates an error symbol period alarm when the number of error frames in a specific period (that is, the window size) exceeds the corresponding predefined threshold. By default, this function is enabled. |
|
Configure the window size and thresholds for error symbol period alarms |
alarm oam error-symbol-period { window-high windowhigh | window-low windowlow | threshold-high thresholdhigh | threshold-low thresholdlow } * |
Optional When both the upper limit and the lower limit of the alarm threshold are set to 0, a lot of alarms are generated immediately. Since alarm events are carried in the OAM packets, a lot of OAM packets are generated. In this case, OAM packets may be lost. The window size and threshold values specified in this command comprise two parts, a significant part and an insignificant part, both 16 bits in length. By default, the window size is 1 second, and the alarm threshold is 20 bytes. |
|
Enable the local link fault alarm function |
alarm oam local-link-fault enable |
Optional The system generates a local link fault alarm when the inbound direction of the local data terminal becomes faulty. |
|
Enable the registration error alarm function |
alarm registration-error enable |
Optional The system generates a registration error alarm when an error occurs during the registration of an ONU. By default, this function is enabled. |
|
Enable the remote stable alarm function |
alarm remote-stable enable |
Optional The system generates a remote stable alarm when an ONU misuse occurs in the system, for example, when an OAM 2.0 ONU and an OAM 3.3 ONU are mixed in the same system. (All ONUs in the same system must adopt the same OAM version). This alarm is generated at the ONU side and will be reported to the OLT. By default, this function is enabled. |
|
Enable the OAM vendor-specific alarm function |
alarm oam-vendor-specific enable |
Optional This alarm is customized by vendors. By default, this function is enabled. |
|
Enable the ONU over limitation alarm function |
alarm onu-over-limitation enable |
Optional The system generates an ONU over limitation alarm when the total number of ONUs connected with the OLT exceeds the limit. By default, this function is enabled. |
Follow these steps to configure alarms on an ONU port:
|
To do... |
Use the command... |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter ONU port view |
interface onu interface-number |
— |
|
Enable the error symbol period alarm function |
alarm oam error-symbol-period enable |
Optional The system generates an error symbol period alarm when the number of error frames in a specific period (that is, the window size) exceeds the corresponding predefined threshold. By default, this function is enabled. |
|
Enable the error frame period alarm function |
alarm oam error-frame-period enable |
Optional The system generates an error frame period alarm when the number of error frames in a specific period (that is, the window size) exceeds the corresponding predefined threshold. By default, this function is enabled. |
|
Configure the window size and threshold for error frame period alarms |
alarm oam error-frame-period { window window | threshold threshold } * |
Optional When the alarm threshold is set to 0, a lot of alarms are generated immediately. Since alarm events are carried in the OAM packets, a lot of OAM packets are generated. In this case, OAM packets may be lost. By default, the window size is 1 second, and the alarm threshold is 20 frames. |
|
Enable the error frame alarm function |
alarm oam error-frame enable |
Optional The system generates an error frame alarm when the number of error frames in a specific time period (that is, the window size) exceeds the corresponding predefined threshold. By default, this function is enabled. |
|
Configure the window size and threshold for error frame alarms |
alarm oam error-frame { window window | threshold threshold } * |
Optional When the alarm threshold is set to 0, a lot of alarms are generated immediately. Since alarm events are carried in the OAM packets, a lot of OAM packets are generated. In this case, OAM packets may be lost. By default, the window size is 10 second, and the alarm threshold is 20 frames. |
|
Enable the error frame seconds summary alarm function |
alarm oam error-frame-seconds-summary enable |
Optional The system generates an error frame seconds summary alarm when the number of error frame seconds (in an error frame second, at least one error frame occurs) in a specific time period (for example, 1 minute) exceeds the corresponding predefined threshold. By default, this function is enabled. |
|
Configure the window size and threshold for error frame seconds summary alarms |
alarm oam error-frame-seconds-summary { window window | threshold threshold } * |
Optional By default, the window size is 600 (in unit of 100 ms), and the alarm threshold is 1 second. |
|
Enable the port bit error rate alarm function |
alarm port bit-error-rate enable |
Optional When both the total number of error bits and the bit error rate of the data transferred between the OLT and ONUs exceed the alarm threshold, a port bit error rate alarm occurs. By default, this function is enabled. |
|
To do... |
Use the command... |
Remarks |
|
Display the configuration information in FTTH view, OLT port view, or ONU port view |
display current-configuration [configuration ftth | interface interface-type interface-number ] |
Available in any view |
|
Display the configuration information in the current view |
display this |
Available in the current view |
|
Display alarm event records |
display trapbuffer [ reverse ] [ size buffersize ] |
Available in any view |
l Use the display this command to display the configuration in the current view. To display the alarm configurations in FTTH view, OLT port view, or ONU port view, you need to enter the corresponding view.
l Table 1-4 shows the relations between the views in which alarms are configured and the views in which alarm configurations are displayed.
l For details about the display trapbuffer command, see the part discussing information center in the command manual.
Table 1-4 Relations between the alarm command configuration views and alarm configuration display views
|
Alarm command configuration view |
Alarm configuration display view |
Remarks |
|
l FTTH view l OLT port view l ONU port view |
ONU port view |
For an alarm configuration command available in any of the three views, you can use the display this command in ONU port view to display the alarm configuration. |
|
l FTTH view l OLT port view |
OLT port view |
l For an alarm configuration command available in FTTH view and OLT port view, you can use the display this command in OLT port view to display the alarm configuration. l For an alarm configuration command available in OLT port view only, you can use the display this command in OLT port view to display the alarm configuration. |
|
OLT port view |
||
|
FTTH view |
FTTH view |
For an alarm configuration command available in FTTH view only, you can use the display this command in FTTH view to display the alarm configuration. |
