On eOMC(V100R004C10SPC300) ,quering ESN was CB4CAB7C129ACB4CAB7C1299CB4CAB7C129ACB4CAB7C1299,but this ESN could not found the historical license info in platform which caused license can not be combined with new license.we could found that the historical license application record used another ESN:CB4CAB7C129ACB4CAB7C1299CB4CAB7C1298CB4CAB7C1297
1.checked the current OMC network configuration using "ifconfig" command
we could found that bond0 bound eth0 ð2 ports and bond1 bound eth1& eth3 ports, and then caculated ESN by MAC address(34:B3:54:83:ED:65, 34:B3:54:83:ED:66, 34:B3:54:83:ED:65,34:B3:54:83:ED:65)and we can got the ESN:CB4CAB7C129ACB4CAB7C1299CB4CAB7C129ACB4CAB7C1299
2. quering network card MAC address before bond operation by "cat/proc/net/bonding/bond0" &"cat/proc/net/bonding/bond1" and get the MAC address as below:
eth0:34:B3:54:83:ED:65 / eth1:34:B3:54:83:ED:66 / eth2: 34:B3:54:83:ED:67 / eth3:34:B3:54:83:ED:68
the historical license application ESN(CB4CAB7C129ACB4CAB7C1299CB4CAB7C1298CB4CAB7C1297) which generated by eth0ð1ð1ð2.
bond operation will change MAC address which display by "ifconfig" command in OMC query and that direct caused it generating different ESN and finally the historical& new license combining failure.
1.the temporary method is getting the MAC address by network card directly and not query it by "ifconfig" command.
and then the ESN generating will not be influenced by bond operation.
2.the next eOMC version (spc800) will solve this issue.
we should check the bond operation implementation record and find the ESN changing or not before combine the historical and new licenses.