UNSOLVED

pmilano1

updated

22 years ago

P

pmilano1

6 Posts

0

12969

June 25th, 2004 01:00

IT Assistant Discovery Problem

Greetings-

I am trying to institute IT Assist on our install base. The system count is significant, although

I am trying to put this in only in our main datacenter at this point.

 

The discovery seems to only pick up one machine, which is a Linux Box with the OM apps

installed. I cannot seem to get it to discover anything else. Has anyone seen issue with this,

and if so, how was it rectified? I'm running a discovery on about 30 boxes... I'm a bit perplexed.

 

Also: Has anyone used the MOM extension to integrate OM?

 

Please advise.

 

Peter J. Milanese

  • MichelleT

    2 Intern

    •

    127 Posts

    446

    0

    Posted June 28th, 2004 14:00

    Please be sure that all of the systems to be discovered have the snmp service installed and configured with a read-write community string, and the ITA platform ip address listed as a trap destination.   You should also have Server Administrator loaded on the 30 systems to be discovered.

    Then open IT Assistant and navigate to the Options -> Discovery Cycle window and be sure the community strings match on the Protocol settings tab.  Also check Options -> Set Discovery Range and be sure that the correct community strings are listed for the appropriate ranges.  Then force a discovery.

  • pmilano1

    6 Posts

    446

    0

    Posted June 30th, 2004 12:00

    For some odd reason, I have everything setup on two machines identically, and one is discovered. It's not network, as the one that is discovered is on

    a different subnet. The one that is not discovered is on the same subnet as the ITA server. Both are running 2k3.

     

     

  • MichelleT

    2 Intern

    •

    127 Posts

    446

    0

    Posted July 2nd, 2004 12:00

    On the remote server, please be sure that your snmp community string is set to read-write and that it matches what is in the discovery range in IT Assistant.  If any modifications are made to the snmp service please restart it.  Verify that the Secure Port Server service and the snmp service are both running on the remote server.

    Then from the IT Assistant platform, try to open Server Administrator on the remote server.  To do this, open a browser on the IT Assistant platform and type in the ip address of the remote server at port 1311 and verify that you are able to log into Server Administrator.  Then you might try setting up an individual discovery range for that single ip address and forcing discovery.

    I hope this information is helpful!  Have a great 4th of July!

  • MichelleT

    2 Intern

    •

    127 Posts

    446

    0

    Posted July 2nd, 2004 14:00

    I am glad to hear the good news!

    The snmp community name should be changed in 4 places.

    On the remote server (client?) it should be changed in 2 places on the security tab and the traps tab (make sure to remove the old string from the dropdown).

    On the ITA platform it needs to be changed on the edit filter window that contains that server and on the Protocol Settings tab on the Discovery Cycle option.

    Then I would restart both the snmp service on the remote server and the IT Assistant services on the IT Assistant platform.

    That should synchronize your community string changes.

     

  • pmilano1

    6 Posts

    446

    0

    Posted July 2nd, 2004 14:00

    Yay

    It seems to have worked now in cases where it had not.

     

    I want to set the read/write to another community string. Do I just change it in the 'Set Community' field and allow it on the clients?

     

    Thanks!

     

  • 446

    0

    Posted September 22nd, 2004 13:00

    Michelle said that the SNMP community name needs to be changed on the ITA on the "edit filter window that contains that server".  Where exactly is that?

    Thanks,

    Ade.