Problem Description

With the SSN1EMS4, SSN1EGS4 application is also more and more, the function is constantly enhanced, and the function of different versions of the difference is very big, so the configuration difference is also very big, so the correct configuration is very important.

Alarm messages

None

Processing

Configuration Notes:

1. Only EPL services support flow control;

2. The OSN3500SSN1EMS4 and SSN1EGS4 single boards only support the inner loopback of PHY, and do not support other loopbacks;

3. SSN1EMS4 and SSN1EGS4 single boards configured with BPS and PPS functions cannot be docked;

4, SSN1EMS4, SSN1EGS4 single-board maximum packet length setting only even number will work, if set to odd number will be larger than the actual setting of 1.

5、Single board test frame R4, R6 version supports GFP and MAC bearer mode. Subsequent versions support GFP bearer mode.

6, the single board only supports 2VBs, the attributes of the 2VBs must be the same, i.e., either both are pure bridges, or both are virtual bridges, and you can't have a bridge that is a pure bridge and another that is a virtual bridge.

7, BPS, PPS protection: full-duplex mode does not support the protection of single-fiber failure of the sending fiber, the FE port only supports 100mfull.

8、In the same multicast and broadcast domain, if the VB hooks up more than 48 ports, it will result in the sending rate of multicast and broadcast messages not reaching the line speed.

9, R7 and above versions added intelligent power management, single board to go online need to first request the host to enter the high power consumption. If the single board and the host do not match, it may lead to the single board can not go online, such as the R7 version of the single board software plugged into the use of R4 host on the network elements, the R4 host will not respond to the single board request to enter the high power request, resulting in the R7 version of the single board can not be started under the R4 host.

10, OSN3500 SSN1EMS4, SSN1EGS4 single-board minimum support for 64-byte packet length, and R6C02B012SP03 before the version does not do the short packet make-up function, and other devices docking, there may be a docking device to receive too small packets (less than 64-byte messages) resulting in loss of packets; if the above problems occur , in the replacement of If the above problem occurs, you need to hard reset the board after replacing R6C02B012SP03 and subsequent versions that support short packet completion.

Root Cause

None

Recommendations & Summary

None