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.
Re: CU OM 2.1 with virtual Communications Manager 7.0
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.
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...