Alarms related to the J0 byte


The J0_MM alarm is related to the J0 byte. If only the J0_MM alarm is reported, there is no impact on services. The cause of the J0_MM alarm is an inconsistency between the J0 byte received and the J0 byte to be received.

Other related questions:
Cause why OSN 6800 NEs report license-related alarms
Question: A customer provides feedback that all system control boards of 48 OSN 6800 NEs report the SYSTEM_DEF_RUNNING alarm one day. One of the NEs also reports the VERIFY_LCS_ERROR alarm. Analysis: 1. A dedicated ASON license file must be loaded to an OSN 6800 NE to enable ASON for the NE. 2. The OSN 6800 NE periodically checks whether the license has been loaded on the system control board. If the ASON license has not been loaded, the SYSTEM_DEF_RUNNING alarm is reported. 3. If the ASON license has been loaded but is about to expire, the NE reports the LICENSE_GOINGTO_EXPIRT alarm. 4. If an incorrect ASON license has been loaded, the NE reports both the SYSTEM_DEF_RUNNING and VERIFY_LCS_ERROR alarms. Root cause: None Answer: 1. Because ASON has not been enabled for the NEs, directly suppress the alarm. If ASON is required later, load a correct license file. 2. Run the license-show-file command to query license information. Suggestion and conclusion: When ASON is not enabled, you are advised to set license-related alarms to be not monitored to avoid customer misunderstanding.

Functions of the RES and GCC bytes in the ASON domain
The OSPF and RSVP protocols transmit messages through the GCC or RES bytes in OTN overhead. Control links and control channels for the ASON are created in OTN overhead (electrical-layer ASON uses RES_ODU or GCC bytes) and DCC channels (optical-layer ASON uses D4 to D12 bytes).

OTN overheads
The OTN optical-layer overheads include OTS, OMS, and OCh overheads and are transmitted through the OSC. OTN electrical-layer overheads include OPUk, ODUk, OTUk overheads, and the frame alignment overheads.

Related services
Related Services: Virtual Private Cloud (VPC) VPC enables you to configure a logically isolated network for your BMSs and to configure security groups, VPN, IP address segments, and bandwidth. With a VPC, you can manage and configure internal networks and change network configurations in a safe and swift way. You can also customize access rules to control BMS access within a security group and across different security groups to enhance BMS security. Elastic Volume Service (EVS) EVS enables you to attach EVS disks to a BMS and expand their capacity. Image Management Service (IMS) IMS enables you to use public images to create BMSs, improving BMS deployment efficiency.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top