RME 3.3 Cannot Manage Catalyst 2950 Via Telnet / Enable
A customer is using CiscoWorks Small NMS Solution with the following components:
CWSNM-1.0-WIN CiscoWorks Small NMS Solution, Incl. WUG 7, CV 5.3, RME 3.3 S
While adding devices, we found RME couldn't manage Catalyst 2950 switches via Telnet / Enable. It said Telnet not supported and didn't check the Enable function. The 2950's IOS version is "12.1(12c)EA1, Release Software(fc1)".
Is this normal? What need be done to solve this problem? Please advise, thanks,
"Telnet" means Telnet connection without user name - which is used to connect to CatOS devices. So "Telnet not supported" for 2950 (i.e. IOS device) is correct.
To the Enable password:
Most people don't configure it at all on the IOS devices. It's recommended to use Enable Secret instead of it.
So the Enable password is only checked if you fill it in the "Change Device Attributes" dialog box. If you leave it empty and fill the Enable Secret password field only, everything is OK.
If you try RME -> Inventory -> Check Device Attributes and the output says Read Community, Write Community, Enable Secret and Local User are OK while Enable and Telnet "did not try", I'd be happy and RME works fine.
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...