The ESN of a new model (-X3/-X8/-X16) is generated based on the barcode on the backplane. Aftera slave MPU is replaced, the ESN of the new model remains unchanged. Therefore,the original license can still be used.
The ESN of an old model is generated based on the BarCode on the MPU. After the MPU is replaced, the ESN changes.To resolve this problem, apply for a new license file for the new master MPU.
In this situation:
- If the MPU whose ESN mismatches that in the license file always functions as the slave MPU, the device can run normally, and all its services will not be affected.
- If the slave MPU becomes the master MPU after a master/slave MPU switchover, when the device reactivates the license, the license will go into a 60-day keepalive period because the new master's MPU ESN mismatches that in the license file. Within the keepalive period, an alarm is reported every day, but the service will not be interrupted.
- If the ESN-mismatch MPU still functions as the master MPU before the keep alive period expires, the license will become invalid. All the services controlled by the license cannot be used.
Summary:
MPU replacement on a new model (-X3/-X8/-X16) does not affect the validity of the license.
MPU replacement on an old model (-8/-16) requires you to obtain a new ESN for new license application.
Special situations:
- If the ESN on the backplane of a new model fails to be obtained, the ESN on an MPU is obtained. If you change the MPU, the ESN changes. Therefore, you are advised to obtain the device ESN and compare it with the one in the license file before and after MPU replacement for both new and old models. If the ESN remains unchanged, no new license is required. If the ESN changes, apply for a new license or troubleshoot the problem.
- Since V600R006C00, new NE40E-X3s that support the binding between the ESN and the backplane are delivered. This function is the same as that on the X8/X16. Note that the binding applies only to the new NE40E-X3s.
