Enterprise Manager on virtual server

[MitelScott]

Having a problem with the enterprise manager discovering nodes. I add the node in the node discovery but no luck. I think it may be because it is a virtual server. this is the first time I have tried to use a virtual server. Has anyone has success with discovering 3300 nodes on a virtual server?

 

[MitelInMyBlood]

Virtual Server (Win2K3 under VMWare) works fine with Emgr 4.0/UR3

Make sure "Discover" is selected
Enter the IP address & subnet mask of the new node
Enter the Community & SNMP port for the node
Select the SNMP version
click ADD
Note the tip in the manual.... it sez "if the node discovery dialog window disappears from view, then select the ALT+TAB keys then click on the JAVA icon for the window to bring it to the forefront

 

[MitelScott]

Yea, got all that. I have deployed several EMS but never had this issue. I am getting EMS events that say...

Cannot add this node XXX.XXX.XXX.XXX Check seed file configuration

Seen this before?

 

[MitelInMyBlood]

No.. what the heck is a seed file? I assume you're seeing this in the server event viewer? Do you have any nodes working or is this a new (from scratch) installation?

 

[MitelInMyBlood]

The term "seed file" normally refers to DHCP discovery. I've never seen this error in an Emgr installation. Sorry, have no clue.

 

[UKMitel]

The seedfile records information relating to synchronization between the topology database and the
Discovery Configurator - according to the handbook, maybe worth checking that the settings in the discovery config have been set correctly

 

[Mitelpassion]

MitelScott,

You've come to the right place. Have had this on my last 4 installastions.

Logged this will Mitel a while ago. After much trying they to produced the fault. 3rd line told me they added more memmory and it worked after that. Not convinced this is the fix though.

I've installed once on VMWare and worked.

How are you adding your nodes. Single or entire network?

I tried adding them one by one. don't like the network discovery if it's only a couple of systems.

I then got the error. I deleted my singe discoveries one by one and turned on the network discovery. This has worked for me every single time. Have no idea what the issue is but I'm working around it every single time.

 

[MitelScott]

I am using single node discovery. I added 1 3300 manually and then deleted it. As soon as I did that, the 3300 appeared as auto discovered... I tried this for the next system and it never showed up. All my SNMP settings on the 3300's are identical across the board. Go figure.

The ticket is with design now and I am waiting to hear back from them.

I am not a huge fan of EMS, seems like it is more a pain in the $#% than a useful tool.

 

[MitelInMyBlood]

Just me, but EMGR was another one of those solutions to a problem that didn't exist and the way to force it down customer's throats was to tie OPS into it as a required blade then M/D standalone OPS. To us Emgr is a genuine PITA that causes more issues than it solves.

 

[Mitelpassion]

MitelScott,

Please keep us posted as to the outcome of the design answer.
Like I said, I raised this a while ago too and I was told to put in more memmory.

thanks

 

[Mitelpassion]

just had another one of those.

auto discovery was blank on any level, in other words no subnets or nodes discovered

added nodes under node discovery, all of them, and looked at the event file
event file said for all the nodes, check seed file
deleted all the node discovery entries, went to network discovery and disovered NOT the whole subnet but set of nodes starting from 172.20.1.1 to 172.20.1.50. Also unticked the discover local subnet box.

ALL 6 of the controllers have been auto disovered.
Hope this helps in a way.

Thanks

Ps like I've said, I've had to do this to probably 6 installs already and without fail this method has worked. good luck!