Telnet access problem

[OrenChen]

I came across an issue where "telnet" doesn't working ("Login Type: telnet").

Wireshark sniffing shows no signs of telnet packets beeing transmited or what so ever.

Then i relized, the issue is with the telnet feauture that doesn't exists in our windows server,

(http://lkhill.com/imc-backups-telnet/)

so I enabled the "telnet" feauture, however, the iMc still not sending any "telnet" packets.

Any ideas?

Thanks

[OrenChen]

I also saw this thread:

http://h30499.www3.hp.com/t5/IMC/Help-with-IMC/td-p/5952971#.UuaqDRD8LIU

Well, i have the "telnet" under C:\Program Files\iMC\server\bin, so maybe its not the

issue of telnen being missing ? i really conused now *-*

[LindsayHill]

Can you be more specific about under which specific circumstances Telnet doesn't work?

Is it:

A) When you try to back up a device, and you have Telnet set as the login type

B) When you click on "Telnet" link on the Device Details page?

C) When you click on the "Telnet/SSH Proxy" link on the Device Details page?

Or some other case?

There are different possible fixes for each of the above scenarios.

[OrenChen]

When i add a new device and select "telnet" for Login Type , iMc doesn't send any

telnet request, and then the "device model" become "ICMP" instead of switch.

[LindsayHill]

Ah.

IMC is not going to try and Telnet to the device when you first add it - it has no reason to.

When you add a device, it does two things:

1/ Ping it to see if it is reachable. (You can force it to add non-pingable devices)

2/ Query it with SNMP using the configured SNMP community string. It will query for sysObjectID, to attempt to identify the device type. It will use that information to classify it, e.g. as a Cisco 3560, or HP 2930, etc. 

Assuming that works, IMC will do further discovery using SNMP, to discover hostname, interfaces, IOS version, etc.  It will not try and Telnet to the device at this point. 

If the device is listed as "ICMP", this means that SNMP is not working. This could be because you have the incorrect community string, or misconfigured ACLs. 

Fix those, and then see if the device gets discovered properly.

[OrenChen]

Now it works, thank you very much!

[LindsayHill]

Glad to help, and thank you for letting us know that it's working.