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

Preparing a server for being added to eSight

Publication Date:  2018-01-30 Views:  81 Downloads:  0
Issue Description

A server cannot be added to eSight.


Solution

On the server side, there are several places in iBMC/iMana where you can check configuration settings related to SNMP that could prevent a server for being added in eSight.

For troubleshooting issues, it's a good idea to retrace the initial configuration and check that all the parameters are correct.


Preparing a server for being added to eSight

  

1.   iBMC

 

1.1.   Go to the Configure Tab, Local Users and create an eSight user, in order to prevend root account lockout

  

1.2.   Go to the Configure Tab, to Service Settings and check that the SNMP agent is on and that the port is 161

 

1.3.   Go to the Configure Tab, System Settings and check that the SNMP version is correctly configured

( use V3, SHA1 and AES unless there are specific requirements to do otherwise)

           

1.4.   Go to the Alarm & SEL Tab, Alarm Settings and check the trap alarm notification settings

 

 

2.   iMana

 

2.1.   Go to the Configuration/User tab and create an eSight user, in order to prevend root account lockout

  

2.2.   Go to the Configuration/Service Tab and check that the SNMP agent is enabled and that the port is 161

  

2.3.   Go to the Configuration/Service Tab, SNMP Configuration and check that the SNMP version is correctly configured

( use V3, SHA and AES unless there are specific requirements to do otherwise)

  

         2.4.   Go to the Configuration/Detailed Configuration Tab, Trap and Check the trap alarm notification settings

              

END