3 Apprentice

 • 

2.8K Posts

November 30th, 2011 11:00

Hi Bryan, a couple of questions...

1. How many discovery ranges did you create?

2. What protocols are enabled in your discovery ranges?

3. If you have more than one discovery range, do the IP address from #1 also appear in the #2 disc range? (or perhaps some subset of the range)

4. Are these modular (blade/chassis) or rack type servers?

Thanks,

Rob

3 Apprentice

 • 

2.8K Posts

November 30th, 2011 12:00

Hi Chris,

I'm actually not in the support group officially, so you'd probably have to open a trouble ticket with support and get it passed through them.  Sorry 'bout that.

Ok, so you have 40 separate ranges set up with one ip in each range?

Can you disable all but one?  I'd like to see if we can get *one* server discovered/inventoried and hanging around without getting deleted.

If that works, enable each one.  But don't do the blades until last.  It's possible there is a problem with one of the servers that is causing this.

I need to take off for a bit but will check back later.

Rob

1 Message

November 30th, 2011 12:00

Rob,

I work with BryanNate and I have recorded an avi through Snagit of what we are taking about. If you set me up a Dell Drop box I can upload the video for you.

4 Posts

November 30th, 2011 12:00

We have ~40 individual IPs with subnet 255.255.255.255

We are only using SNMP

There is a mix of blade servers and rack servers

1 Rookie

 • 

7 Posts

December 5th, 2011 13:00

We have the same problem with Server 2008 devices disappearing.  This event shows up in the log:  "Info" "12/2/2011 6:38:43 AM" "A duplicate device has been detected. Device (name: server_a.socogen.com, ip address: , internal ID: -1217723685) was deleted because the MAC Address: 0000000000000000 was discovered on another device (device name: server_b.socogen.com,  ip address: xxx.xxx.xxx.xxx, internal ID: -1022887162)."

3 Apprentice

 • 

2.8K Posts

December 5th, 2011 14:00

BTW, you will need to restart the OME services.  You can do this from services.msc or from the restart button in the OME console under Prefs.  

3 Apprentice

 • 

2.8K Posts

December 5th, 2011 14:00

Hi and thanks for the question,

Certain MACs are not valid to compare / correlate on – hence the list below. There is a list in a  config file you can update so the MAC  will be taken out of consideration.

Virtual MACS may have all zeros for the address.  If you look at dconfig.ini under the OME subdirectory, you can make a backup and then edit the original to look like this:

PRIVATE_MAC_EXCLUDE_LIST=127.0.0.1,0.0.0.0,005345000000,33506F453030,505054503030,0000FFFFFFFF,204153594EFF,000000000000,00000000000000e0,020054554e01,204153594eff,0000000000000000

I added the last entry. *count your zeros* :-)

Rob

1 Rookie

 • 

11 Posts

December 8th, 2011 11:00

I just encountered this issue.

Nearly all devices were deleted and the following was logged:

A duplicate device has been detected. Device (name: hostname-fqdn, ip address: , internal ID: -2102448854) was deleted because the MAC Address: 0000000000000000 was discovered on another device (device name: diferent-hostname-fqdn, ip address: 192.168.0.2, internal ID: -565025184).

3 Apprentice

 • 

2.8K Posts

December 8th, 2011 11:00

Hi Kevin,

Can you review the following post a bit earlier in this thread and let me know if that helps you?

Thanks,

Rob

Posted by DELL-Rob C on Mon, Dec 5 2011 4:43 PM

1 Rookie

 • 

11 Posts

December 8th, 2011 12:00

That update dconfig.ini appears to have resolved the issue following a new discovery.  Thanks, Rob.

I especially like the update feature of OME. Would be nice to see this type of functionality on the client side. I've never been able to get Dell Management Console and DCM working.

3 Apprentice

 • 

2.8K Posts

December 8th, 2011 12:00

Great.  Thanks for taking the time to post Kevin.  I will pass your request (client) on to our marketing team.

No Events found!

Top