K-byte for 803 network elements:

// Startup K-byte when veneer is offline

1 14525 BD_OFFLINE 0x0002 2010-10-23 20:34:21 0x0477c6c2

1 14526 K_ON_OFF 0x0002 2010-10-23 20:37:07 0x041cc357

//0x1872K bytes sent in the direction of the 1903 network element, sent K bytes have remained unchanged for two hours since then

1 14532 K_SENDS 0x1872 2010-10-23 20:37:07 0x041d5fea

1 14533 K_DIR 0x0002 2010-10-23 20:37:07 0x041d5ff2

1 14536 K_RECEIVED 0x5782 2010-10-23 20:37:39 0x00d96d30

1 14537 K_DIR 0x0002 2010-10-23 20:37:39 0x00d96d3b

//Receive direction MSRDI, indicating that the 1903 receive direction is bad again

1 14543 K_RECEIVED 0x5786 2010-10-23 20:44:47 0x00cdad69

1 14544 K_DIR 0x0002 2010-10-23 20:44:47 0x00cdad75

//Short path received ring inversion

1 14545 K_RECEIVED 0xb786 2010-10-23 20:44:47 0x00cdb344

1 14546 K_DIR 0x0002 2010-10-23 20:44:47 0x00cdb34d

The //MSRDI disappeared, indicating that the SF in the direction of the 1903 receive was good at this time

1 14552 K_RECEIVED 0xb782 2010-10-23 20:44:58 0x01736ffa 1 14553 K_DIR 0x0002 2010-10-23 20:44:58 0x01737006

// Thereafter, no change until two hours later, when node 5 was interrupted with fiber to node 6

1 14556 K_RECEIVED 0xb56a 2010-10-23 22:30:34 0x00454d59

1 14557 K_DIR 0x0000 2010-10-23 22:30:34 0x00454d64

K byte of 1903 network element:

// Corresponding to 803 receiving MSRDI, 1903 receives direction SF and sends ring inverted K bytes normally

1 2024 SF_DETECTED 0x0000 2010-10-23 12:44:49 0x0146ba1b.

1 2025 K_SENDS 0xb782 2010-10-23 12:44:49 0x0146bad0

//SF disappeared

1 2032 SF_CLEARS 0x0000 2010-10-23 12:45:0 0x01ec7ee9

//Exception here, SF disappeared, but instead of receiving 0x1872 bytes sent by the 803 network element short path, it received 0xFFFF

1 2033 K_RECEIVED 0xffff 2010-10-23 12:45:0

Analyzing the 0xffff K byte, the three bytes after the K2 byte are 111 for MS_AIS alarm, analyzing the processing of the protocol at this time there is no abnormality. after the disappearance of SF, the line board reports the K byte, but the protocol thinks that it is still SF at this time, and does not carry out the relevant action. Since there is no change in the K bytes, the line board does not update the K bytes, and the multiplexing segment is consistently in the inverted state without recovery;

Analyze the reason for the generation of 0xffff K bytes, there are records showing that: 803 network element single board on-line, sent K_SENDS 0x1872K bytes, if it is 803 failure, sent the wrong 0xffff K bytes, then the normal processing of the 1903 network element should receive the MS_AIS alarm and SF_DETECTED, but the actual situation is not so,. Therefore, it can be ruled out that the 1903 receiving direction received the wrong K bytes; then there is only one possibility, the 1903 network element line board reading K bytes or reporting K bytes link has a fault, resulting in reporting the wrong K bytes.

When the software reports the K bytes, because the communication has a checksum mechanism, it is judged to be reading the K byte queue, due to a hardware failure, reading the wrong K byte 0xffff.