cisco switch login

[cestarik]

hi,

Task (2 / 596) Status

-------------- ----------------------------------------------------------------------

10.0.xx.xx Scan failed: SSH: {seNoError}; VMWARE: Port open, but protocol skipped

 

user name and password correct too but if i`am do new connection from putty need to accept the protocol. Can be this problem when TNI try`s login?

 

 

snmp 

Task (4 / 1276) Status

--------------- -----------------------------------------------------------------------------------------------------------------------------------------------------------

    10.0.99.40 Scan failed: SNMP: Incorrect v1/v2 communities, but v3 protocol is available; SSH: Port open, but protocol skipped; VMWARE: Port open, but protocol skipped

 

Community for read is OK from cacti i can read V1 or V2 but from TNI no 

[Alex]

Hi, cestarik.
Thanks for your message.

SSH:

There should be no problem with the Security alert message. TNI accepts it automatically. The problem may be related to the shell of the OS that you are trying to scan or the scanning agent.

Please try to scan this system manually. You can find instructions on how to do this here:

https://docs.softinventive.com/tni/user-manual/scanning-using-agents/manual-scan/

Let us know if the local scan returns the same error.

SNMP:

First of all, please check if the name of the community is specified correctly in the SNMP column. There may be a typo.
It is also possible that access to some OIDs of the remote device is restricted. In this case, you will receive the same error "Incorrect v1/v2 communities", and TNI will not be able to collect other OIDs and perform an SNMPwalk.

[cestarik]

hi ,

can't do it manually because is a cisco switch. 

SNMP

was a restricted access problem 😉

[Alex]

Hi,

Thanks for your message.

Please let us know the model of the Cisco switch. Most likely that it cannot be scanned via the SSH protocol. You can try scanning it via SNMP.

[cestarik]

hi

still problem with snmp. community looks like this  Tr4Ps.2020 and is version 2c

Task (38 / 1725) Status

---------------- -----------------------------------------------------------------------------------------------------------------------------------------------------------

    Done

    Scan failed: SNMP: Incorrect v1/v2 communities, but v3 protocol is available; SSH: Port open, but protocol skipped; TELNET: Port open, but protocol skipped

 

cisco 3750E

 

    

[Alex]

Hi,

Please check if you can collect the data from the following OID using the same community:

OID 1.3.6.1.2.1.1.0

Send us a screenshot, if possible.

The incorrect communities error may still be related to the restrictions set on the switch.

[cestarik]

walk from MIB browser

[Alex]

Thank you for the information.

There is one more thing that we can try.

Please close the program and temporarily remove the netsnmp.dll file from the TNI installation folder (move it to another folder). Start the program and try scanning this switch.

Let us know the result.

[cestarik]

On 9/18/2020 at 3:11 PM, Alex said:

Thank you for the information.

There is one more thing that we can try.

Please close the program and temporarily remove the netsnmp.dll file from the TNI installation folder (move it to another folder). Start the program and try scanning this switch.

Let us know the result.

Task (8 / 1327) Status

--------------- ---------------------------------------------------------------------------------------------------------------------

               Scan failed: SNMP: System scan failure; SSH: Port open, but protocol skipped; VMWARE: Port open, but protocol skipped

[Alex]

We apologize for the delay.

Please restore the netsnmp.dll file. Check the following:

1. Once again, make sure that you are using the Tr4Ps.2020 community when you scan this device.

2. Make sure that the UPD 161 port is not blocked by Windows on the system where TNI is installed.

3. Since SNMP v1 and v2 utilize the UPD protocol, it is possible that some packets are lost in your network. Please try to ping this switch using the ping -t command. Let us know the percentage of the packet loss.

[cestarik]

sorry for delay

it will not be a problem but until the end of the week. 😄 

it will not be a problem but until the end of the week