No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

VIS6600T cannot be discovered by ISM

Publication Date:  2016-11-28 Views:  69 Downloads:  0
Issue Description
we getting the below error massage when trying to connec tto the VIS , The Communication with the device failed, check the system connection or is normal, But can ping all the IP address assigned on the VIS , And I can logon using putty system status information is normal
before we was able to logon but now is failing.




Alarm Information


Handling Process
checked the connectivity with the maitenance PC and it is ok
checked the version of java
uninstalled ISM software and java and downloaded from the page of the IP of the management
checked with another PC
when faced that issue still exist so the probability now is that the ISM agent access limitation
The max ISM agent limitation number is 32, when a user access success one time, the number will +1,  and when user logout, the number will -1. but when user is failed to access, the number +1. so the failed times reach 32, couldn't login by ISM .

we clear the access limitation number as following :

==

 

1.        Use putty to login VIS by admin user , and enter misisystem as bellow steps:

 

   

 

2.        After enter to minisystem, add “vim” command as bellow steps:

 


 

3.        After add vim, input “:she” and click enter key to enter the debug mode.

 

4.        Restart ISM Agent as bellow steps:

 


 

5.        input “exit” to exit debug mode.

 

6.         del the vim command as bellow steps:

    

 

7.        input “exit”  to exit minisystem and developer mode.

 

 


Root Cause

the ISM agent access limitation
The max ISM agent limitation number is 32, when a user access success one time, the number will +1,  and when user logout, the number will -1. but when user is failed to access, the number +1. so the failed times reach 32, couldn't login by ISM .

Solution
After clearing ISM agent limitation number, the issue was resolved.

END