cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
508
Views
0
Helpful
3
Replies

CU OM 2.1 with virtual Communications Manager 7.0

azeindler
Level 1
Level 1

I try to discover with CUOM 2.1 an CM 7.0 on a VMWare-ESX server in our showroom. The Communications Manager state is unreachable. SNMP and HTTP Username/Pwd is correct configured in the CM and in the OM.

Do anybody has an idea?

Thanks for any input.

Kind regards

3 Replies 3

irisrios
Level 6
Level 6

Devices may go into the Unreachable state due to the following reasons:

• SNMP timeout

• Data Collector timeout

If an SNMP timeout occurs, verify the SNMP access credentials provided during discovery.

If a data collector timeout occurs, verify that the SNMP management interface is not a serial or a generic interface (such as Framerelay with the subnet mask 255.255.255.252). You should always access SNMP details using an Ethernet interface.

jedellerby
Level 1
Level 1

Did you ever resolve this issue? I've just built CUOM 2.2 running against a 7.0.2.

CUOM discovers the Publisher and Subscriber but the service view shows the publisher as unreachable, which I don't understand as it's the same config as the subscriber.

Jed

No workaround for this problem, sorry.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: