Server Management - Systems Insight Manager
1836762 Members
2617 Online
110109 Solutions
New Discussion

SW column showing blank status

 
SOLVED
Go to solution
Steven Laux
Frequent Advisor

SW column showing blank status

Hello,
I have a new install of SIM 5.0. I imported my servers from a host file. After running for a day, I noticed that the SW status column is blank on almost all servers. There are a few with a status of (I). I know that means the trust relationship is not working, but what about the servers showing nothing in that column? I tried importing the certificate on some servers, then running a software status poll. The poll completes instantaneously, like it didn't even try. The status in the SW column is still blank. Anyone see this before?
Thanks in advance.
Steve
4 REPLIES 4
Harry Galanos
Frequent Advisor

Re: SW column showing blank status

Steve this could be many things.

1. Are they supported systems? Novell shows up blank as SW is not supported.
2. Does the username/password you are using have access to those servers in order to 'probe' them for details?
3. Have you deployed the 'initial proliant support pack'? This is installs the agents required to determin the SW status, this will also correct your trust issues.

Good luck.
Steven Laux
Frequent Advisor

Re: SW column showing blank status

Thanks for the response, Harry.

These servers are being migrated from our SIM 4.2 to the new 5.0 server. I expected to see the (?) Trust issue but not a blank status.
The account I am using has administrator access on all servers. These servers are Windows 2000 or Windows 2003 and have either PSP 7.1 or 7.3.

Thanks again,
Steve
jim goodman
Trusted Contributor
Solution

Re: SW column showing blank status

If you have run the device identification and sw status poll and come up empty.....

I am wondering if your SNMP Security is set to allow packets from the new 5.0 CMS and also if the Global Protocol Settings are matching those strings.

- Jim
Steven Laux
Frequent Advisor

Re: SW column showing blank status

Thanks, Jim! I checked the Global Protocol Settings. Sure enough, I had the community read string set but the default write string was set incorrectly.
Great answer. You rock!