Description of the problem

With the geometric growth of Ethernet services, the security and reliability requirements for Ethernet services are getting higher and higher. LCAS technology has been successfully launched and rapidly applied, which provides a method to smoothly change the bandwidth of virtual cascade signals in the transmission network to automatically adapt to the service bandwidth requirements. It can dynamically adjust (add, delete, change) the service bandwidth without affecting the availability of the original service, so it is important to correctly open the LCAS function.

Caution:

(1) The SSN2EMR0/SSN2EGR2/SSN1EFT8/SSR1EFT4/SSN1EGT2 boards of Huawei OSN1500 devices have target versions that support the LCAS V2.0 function in V1R3 and V1R6 versions, and can be upgraded to the corresponding host version or above as appropriate.

(2) Huawei OSN2500 devices SSN1EFS4 and SSN2EFS0 do not support LCAS V2.0 in version V1R6C01B01D and must be upgraded to version V1R6C02B012;

(3) If Huawei OSN3500 devices SSN1EFS4/SSN2EFS0 need to support LCAS V2.0, they can be directly and smoothly upgraded to version V1R3C02B054, or to version V1R6C02B012. If you upgrade to version V1R6C02B012, you also need to pay attention to the following points:

If you need to support LCAS V2.0 function, you must load the single board software of SSN2EFS4 and SSN4EFS0 (the supporting relationship has been verified), but the board types of N1EFS4 and N2EFS0 can be upgraded without any upgrading (avoiding the trouble of deleting the service required for board type upgrading); the single board software can be found in the V1R6C02B012 software package SSN2EFS4 and SSN4EFS0 folders, the single board version number is 4.13; if there is no need to support LCAS V2.0, you can directly use the single board software in the SSN1EFS4 and SSN2EFS0 folders in the V1R6C02B012 package;

If the SSN1EFS4 single board is to be upgraded to support the corresponding version of LCAS V2.0, the three configurations of SSN1EFS4 need to be checked before and after the upgrade:

COS configuration: if the CoS policy has been configured, the CoS configuration will be lost because the QoS model of the new version is different from that of the old version; if no CoS is configured, it will not be affected. It is recommended to delete the CoS configuration first and then upgrade;

P attribute port encapsulation configuration: If MoP encapsulation has been configured, you need to modify both the local end and the peer end to MoE or VMAN (Stack VLAN) encapsulation; if MoP encapsulation has not been configured, it is not affected;

J1 and J2 overhead setting: since the default mode and value of J1 and J2 bytes are different before and after the upgrade, you need to check the J1 and J2 overhead matching after the upgrade, and set the mode and value of the receivable and transmittable J1 and J2 bytes according to the actual receivable J1 and J2;

(4) The SSN1EFS4/SSN2EFS0 boards of NGSDH V1R6 supporting the network management version of LCAS V2.0 must be loaded with the patch of network management V2R4C01B01CSPC002 and the EMS.cfg configuration item must be modified;

(5), SSN1EFS0 does not support LCAS V2.0 in all versions, if you need to support it, you must replace and upgrade the board type to SSN2EFS0/SSN4EFS0, and upgrade the software to the version corresponding to this board type that supports LCAS V2.0;

(6) SSN1EGS2 cannot support LCAS V2.0 function, it must be replaced with SSN2EGS2 single board to support it, if the physical single board is SSN1EGS2 single board, you need to replace the single board;

(7) If you need to support LCAS V2.0 with OSN7500/3500/2500/1500A/1500B V1R6C02B012 versions of SSN1EFS4 and SSN2EFS0 boards, you need to patch SPC002 for T2000 network management and modify the LCAS configuration items in EMS.cfg file;

(8) SPC002 of T2000 network manager can only be installed on V2R4C01B01CSPC001, if the site is V1R4C01B01C version, you need to upgrade to SPC001 first;

(9) When the command is given to delete the cross-connection without first deleting the VCTRUNK binding, it will cause the original LCAS function to fail and service interruption to occur. Therefore, VCG should be deleted first before deleting the cross-connection;

(10) Docking between non-LCAS and LCAS modes is not supported. When docking between non-LCAS and LCAS modes, the negotiation result is uncertain and the service may not be available;

(11) Does not support LCAS with no damage to service, switching between LCAS enable/disable enable, adding/deleting channels, and packet loss for service when the channel fails and recovers;

(12) For Ethernet EFT8/EFT4 LCAS enable, deleting a channel has a recovery event reported by the neighboring channel. When LCAS is enabled, deleting the downstream or bidirectional of a channel at one end, waiting for a few seconds for the LCAS event to be reported, and then deleting the upstream or bidirectional of the corresponding channel at the other end will report the recovery event of the latter channel, and at the same time, there will be a small amount of packet loss. This problem occurs only when that channel is deleted for the first time after a hard reset of the veneer;

(13) For Huawei N2EGT boards, starting and stopping the LCAS protocol on one port may result in packet loss on the other port. Meanwhile, the EGT2 LCAS cannot block the VC4 channel that goes through the VC3 cross, and the VCTrunk binds the VC4 channel, with part of the channel going through the VC4 cross and part of the channel going through the VC3 cross. Because VC4 cannot be transmitted by VC3 crossover, that VC4 is not passable and should be blocked off that VC4 channel, but the LCAS of EGT2 can not block off that channel, in this configuration, the LCAS can not block off the not passable VC4 channel, and it can not play the role of auto-protection. So don't use VC3 level crossover to exchange VC4 level channel;

(14) For OSN3500 device N1EMS4,N4EGS4 board LCAS function Holdoff and WTR parameters are not supported to be set on the network management, only query is supported, holdoff time defaults to 2s, WTR time defaults to 5 minutes, if this parameter must be modified in some cases, then you can use the host command line. If you must change this parameter in some cases, then you can use the host command line. However, you must note that modifying the parameter for any port will take effect on all ports at the same time;

The technical information related to this chapter and the SDH equipment troubleshooting process are collected and organized by Shenzhen Optical Transmission Network Technology Co.( www.opticaltrans.com), please retain! Our company specializes in the sales of Huawei SDH optical transmission equipment, SDH transmission equipment.