Partial Collection Failure - on 3750 Switch stack

[John Palmason]

Hello, I am looking for some help discovering two switch stacks, I have discovered most of my network with problems including other 3750 Stacks.  But I have two stacks that don't seem to want to get entered into APIC-EM and show partial collection.  I have done the usual troubleshooting like, deleting and re-adding, trying no profile discoveries, CDP discover, single port range discovers and still nothing.  The discoveries show as successful but the topology maps are showing the access switches all over the map not connected the the collapsed core stack.  I have opened a TAC case and provided the RCA logs to TAC but they don't have any finding yet and I wanted to know if the communities would have any suggestions.

Here it the error message the pops up next to the status of partial collection:

All information from the device could not be collected successfully. It may be a temporary reachability problem or credentials are not correct. Please re-run the discovery for the device and if that does not resolve the problem, please get in touch with Cisco TAC to resolve your problem    

John Palmason

[aradford]

Hi John,

How are you trying to discover?

Are you using ssh and it is ssh2?

Adam

Sent from my iPhone

[John Palmason]

I am using SSH V2 for discovery method of connecting, it has worked on the majority of my install base just two switches are being problematic.  Any suggestions?

JP

[aradford]

can you verify that the devices are working with sshv2?

$ ssh -2 <your device>

Discovery only works with ssh v2.  The error message is not being displayed at present if this is the problem.  This is my theory about your problem

Adam

[John Palmason]

Here is the output of the ssh'ing from the APIC-EM vm, it seems to connect fine:

$ ssh -v2 APIC-Admin@X.X.X.X

OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014

debug1: Reading configuration data /etc/ssh/ssh_config

debug1: /etc/ssh/ssh_config line 19: Applying options for *

debug1: Connecting to X.X.X.X [X.X.X.X] port 22.

debug1: Connection established.

debug1: identity file /home/grapevine/.ssh/id_rsa type 1

debug1: identity file /home/grapevine/.ssh/id_rsa-cert type -1

debug1: identity file /home/grapevine/.ssh/id_dsa type -1

debug1: identity file /home/grapevine/.ssh/id_dsa-cert type -1

debug1: identity file /home/grapevine/.ssh/id_ecdsa type -1

debug1: identity file /home/grapevine/.ssh/id_ecdsa-cert type -1

debug1: identity file /home/grapevine/.ssh/id_ed25519 type -1

debug1: identity file /home/grapevine/.ssh/id_ed25519-cert type -1

debug1: Enabling compatibility mode for protocol 2.0

debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.6

debug1: Remote protocol version 2.0, remote software version Cisco-1.25

debug1: no match: Cisco-1.25

debug1: SSH2_MSG_KEXINIT sent

debug1: SSH2_MSG_KEXINIT received

debug1: kex: server->client aes128-cbc hmac-md5 none

debug1: kex: client->server aes128-cbc hmac-md5 none

debug1: sending SSH2_MSG_KEXDH_INIT

debug1: expecting SSH2_MSG_KEXDH_REPLY

debug1: Server host key: RSA d9:86:7e:1d:8b:0b:90:c3:ec:88:07:5e:a2:73:c7:1e

debug1: Host 'X.X.X.X' is known and matches the RSA host key.

debug1: Found key in /home/grapevine/.ssh/known_hosts:2

debug1: ssh_rsa_verify: signature correct

debug1: SSH2_MSG_NEWKEYS sent

debug1: expecting SSH2_MSG_NEWKEYS

debug1: SSH2_MSG_NEWKEYS received

debug1: SSH2_MSG_SERVICE_REQUEST sent

debug1: SSH2_MSG_SERVICE_ACCEPT received

debug1: Authentications that can continue: keyboard-interactive,password

debug1: Next authentication method: keyboard-interactive

Password:

debug1: Authentication succeeded (keyboard-interactive).

Authenticated to X.X.X.X ([X.X.X.X]:22).

debug1: channel 0: new [client-session]

debug1: Entering interactive session.

debug1: Sending environment.

debug1: Sending env LANG = en_US

                       * * * *   N O T I C E   * * * *

This system is for authorized personnel ONLY. Only specifically authorized

personnel may log into and use this system.  Any unauthorized use of the system

is unlawful, and may be subject to civil and/or criminal penalties.  Any use of

this system may be logged or monitored without further notice, and the resulting

logs may be used as evidence in court.

switch#

[johnny.achladi]

Can you please provide TAC Case #?  We can look into RCA.

[John Palmason]

Hello Janardhana here is the TAC details SR 680826744, so far we have collected inventory logs but nothing else has been resolved yet.

I look forward to what you might find.

Thank you.

[johnny.achladi]

Based on the case log, I see this is a 3750G stack switch.  is that right?  We are failing here in collecting host inventory.

Unfortunately, We do not support 3750G on APIC-EM.  This is a EOL product.

End-of-Sale and End-of-Life Announcement for the Cisco Catalyst 3750G, 3560G, 3750-E, and 3560-E Series Switches - Cisco

Even if any  3750G switch goes into "managed" state, you would run into issues with applications EasyQOS, Path Trace.

You had also mentioned that you were running into ISR issue. is that still the case?

FYI, Below is the complete list of hardware models supported with  APIC-EM 1.2.1 release.

Supported Platforms for the Cisco Application Policy Infrastructure Controller Enterprise Module, Release 1.2.0.x - Cis…

[John Palmason]

Janardhana, thank you for this information we have a project to replace all our EOL products with 3850's which will happen in the next few months.  Based off this information I will close the ticket and wait until we have completed this work and try again.

All our ISR/2 routers have been discovered correctly and are working in APIC-EM, so I am not sure of the issue you are referring to?  Do you a ticket I can track?

Thank you for your time and knowledge on this issue.

John P

[johnny.achladi]

John,

I was referring to same case (SR 680826744)  and I see in the description it says, you had a problem with ISR as well.

"question about topology for APIC-EM, 2 devices aren't discovering properly including ISR FHKXXXXF1NJ"

If you no longer see problem with this ISR, we are good to close this thread.

Cheers

[John Palmason]

I have successfully discovered all my ISR's, it is just a single 3750 switch which isn't being collect properly out of 208 devices.  Sadly this switch isn't supported and will be replaced in a project to update old hardware this year.  Lets close this thread.

Thank you.