customer could see U2000 occurred more than 31000 communication alarms every day , that is abnormal.As per customer have to check if the device is down when communication alarm occur ,so their jobs are affected by so many alarms appeared in the same time suddenly, job for them became very diffcult. and U2000 system became slowly because of those alarms.
Communication with the device failed.
we have to increase 'PingTimeouts' and 'NumOfPerSyncSend' so if there is delay on the network As the network is so large so that we can overcome that delay Please use the isql login the Sybase and execute the command as follows
Please use the isql login the Sybase and execute the command as follows
update BMSDB..bms_cfg_tab set CfgValue = '40' where CfgName = 'PingTimeouts'
update BMSDB..bms_cfg_tab set CfgValue = '3' where CfgName = 'PingRetries'
update BMSDB..bms_cfg_tab set CfgValue = '40' where CfgName = 'NumOfPerSyncSend'
Then reboot the Access Device Manager_9661 Process. And check whether you still have problem.
1. checking the decvice alarm history we foumd that device have no problem at that time at all.
2. checking the device SNMP confurgation no problem found
3. checking U2000 NMS alarm found no alarm on it .
4. On the UA5000, send large ping packets to the U2000 . It is found that packet loss occurs and the delay is 50-60 ms.
so it is confirmed that there is delay on the network from UA5000 devices to U2000.