OPS Manager problem

[1973stu]

I've just installed OPs Man for administering a 3300 (6.1.5.4) and an SX2000 (Liteware 34).
Everything is OK with the SX2000 but I've got problems with the 3300.
I can backup the database and reach the ESM via ops man but cannot do an alarms audit or full collect.
There is one thing I've noticed which is quite odd on the 3300, the network element assignment shows the local element status as false?
Enterprise Man 3.0 and OPS Man 7.4
Any help would be great!

 

[Mitelpassion]

do you have the correct Ip addresses where applicable?
have you checked your logs. this usually give a very good indication of what could be wrong

 

[1973stu]

All IP Addresses seem OK.
I get the following error in the event viewer of the OPS Man server:

CPIPE C-345-CPIPE_No_Response_From PABX 192.168.2.2 CSMSG last error 0

This comes after trying a full collect.

 

[kwbMitel]

Sounds like the Networking OPtion in License and Option Selection is not enabled.

When the Full Collect fails, do you get a cannot setup pipe error?

 

[1973stu]

Networking Option is set to yes.

I'm on holiday at the moment so can't check the errors now but will try and reply next week.

Thanks for your reply.

 

[MitelTech]

Have you filled out the needed info in the Controller Registry Configuration form on the 3300?

 

[1973stu]

Yes I've put in the IP Address of the OPS server and ftp username and password. And given an account for the OPS Man to use and log on to the 3300 (mnms account).
I keep thinking something is wrong with the 3300 regarding the status of the network element assignment. It shows the local element as false when it is the only element and should automatically be put in the form and show true.

Will try to get more logs next week when I've finished my holiday.

 

[Lundah]

Not sure about what's hosing up the alarms audit, but something to check on the directory collect is to make sure the local directory entries don't contain charachters OpsMan doesn't like. I'm a bit suspicious that the NetElement Assignment form doesn't look right either; does the system name match up everywhere (ESM main screen, System Options form, etc.)?

 

[kwbMitel]

I had this problem last week with a system that was named incorrectly.

Does your name have a capital first letter (not a number) lower case for all the rest with no spaces?

 

[1973stu]

Thanks all,

I ended up getting Tech support remote access and they sorted it out.

The problem I had was when I put the system name in the network element assignment it didn't automatically save to the system options assignment.

For ops man to work correctly the system name must appear in the options assignment.

I've mailed tech support to find out what was done to resolve this. I'll post the answer when I get it.

 

[Lundah]

I've run into that before as well. Usually the way to fix that is to use the SX-2000-style Telnet interface and change the System Name in the System Options form there (since you can't change it in the ESM interface form). I'd be curious to find out why the name you programmed in NE Assignment didn't populate the SyOp form, it should.