The user finds that the status of the service port at the NMS side and the device are not the same. The network elements are synchronized, but the status is still not consistent. How to solve the problem?
Method I: Directly synchronize service ports, rather than network elements
Method II: Modify the configuration file. Take MA5600V3 as an example:
By manually modifying the configuration file, we can synchronize the network element operation by directly getting data from the host without comparing serial numbers: This can be done through the following steps:
1. Modify the resource change switch in /opt/n2000/server/conf/MA5600V3/bms_pvc.cfg file (change the PVC_RES_CHANGE_TRAP_SWITCH value from On to OFF).
2. Restart corresponding network element processes.
By modifying the file, when network element is synchronized, the effect of service port synchronization is the same as that of direct manual synchronization of service ports. If network elements are synchronized this way, the service port status is the same as that at the device side.
When synchronizing network elements, the NMS requests to synchronize the pvc module. Since the synchronization of network elements is very time-consuming, the NMS checks the serial number first to see if the data in NMS is already the same as the serial number in the host. If so, the synchronization is unnecessary.
It is only when the host side serial number is bigger than the NMS side serial number that the NMS reads data from the host (send a getall command to the host) and actually polls the pvc module. After that, the NMS side serial number is updated to be consistent with the host. Otherwise, the NMS deems the NMS side data is already the same as the host data (will NOT send a getall command to the host), and return directly, causing the inconsistency between the NMS side data and the host data.