I'm currently testing out OME 1.2.1 in my environment & currently there are 2 scenarios that are bugging me.
1) Assuming that I have 5 switches (10.1.200.1 - 5). The first 4 have SNMP community name "public" while the last (10.1.200.5) uses "testlab".
I started a "Add Discovery Range Group" with the IP range of 10.1.200.1-5 & SNMP community name "public" which returned me 4 switches & another unknown device. So far so good.
Next, I initiated a "Add Discovery Range" for the last remaining switch (10.1.200.5) with SNMP community name "testlab" & now I have all 5 switches identified. However, this last switch still remained in the "unknown" list as well which is definitely a duplicate after I have the IP checked & matched.
Question: Is this intentional / working as per design? If yes, may I know what's the logic behind it? Shouldn't OME identify that this switch has been categorized correctly & should no longer appear in the "unknown" list?
2) I was able to have OME identify & classify most of my Dell servers except for the Win 2K8 DC (a PE610). Pretty sure there's nothing with the steps since I was able to get the other servers working but just to be safe, these are what I've done:
a) OMSA installed
b) SNMP Services' Security tab updated with SNMP community name & accept packet from any hosts
c) Firewall turned off
d) Troubleshooting Tool on the DC via SNMP only returned 2 lines (MIB-II System Name & MIB-II Mac) whereas the other servers showed OMSA versions as well.
I'm pretty sure (d) itself is a problem but I have no problem accessing the DC's OMSA page (https://<DC_IP>:1311) from my OME server.
I still have ESXi hosts that I've yet to touch on but I think it's much safer to tackle these issues 1 at a time for now. Thank you very much in advance for attending to my queries.