Deployed the APIC-EM, it's working fine. After, performing many discoveries (using both cdp, and range discovery), when trying to take the Topology, there are devices with no links, ( 0 connections ), even though, they have few neighbors connected to them. So, in the map they are just sitting by themselves. These devices have cdp enabled, and sh cdp neigh confirms it. The path trace app errors out with this message:"Not able to locate unique interface or host for source ip address, Not able to locate unique interface or host for source ip address", since the trace goes nowhere from these devices.
Below is just one of few devices ( edge routers ) that have missing links ( no connection to their neighbors ).
1) Using APCI-EM ver: 1.4.0.1959
2) a show cdp neigh , show all the respective neighbors ( both direction ), however when tried debug cdp packets on the those troubled devices, no cdp debug data is returned ( which should be returned every 60 sec - default - ).
3) links affected: L2/L3. Devices: ASR, ISRs, Cat switches, two of our ASAs.
if you do a rediscovery of the device, it should rediscover the links. Are you doing a CDP based rediscovery, or an IP range... To tackle things better will see the answer to these questions..
1) Do you have CDP neighbour on both sides (show cdp ne)?
2) What is the type of the device that does not have a connection and it's version of code (is it supported)? e.g 2960X - 15.2.5e
3) How are the devices that do not have links connected? L2/L3/ Subinterface?
1) CDP is enabled on both sides. On the lab server, the same devices formed links between each other properly and path trace worked.
2) The 1st site consists of WS-C3560-24PS-E (12.2(55)SE6), WS-C2960G-48TC-L (15.0(2)SE7) switches and CISCO2911/K9 (15.4(3)M2) routers. While the switches are not in the support list, they did work properly on the lab server.
The second site has a 2960X switch stack(15.0.2-EX5), 887 and 2911 15.2(4)M3 routers.
All links are Layer 2, no sub interfaces.
Re-discovery didn't fix the missing links. tried CDP based, IP range based and even adding the devices one-by-one at the device inventory.
That's a path trace from the lab server at the same site:
All of the devices and the apic-em server are configured with a domain name.
You might want to look at the Cisco Network Visibility Application for APIC-EM Supported Platforms, document. found it helpful.
The devices that weren't forming links were in the supported devices' list: 2960X (15.0.2-EX5) and ISR2 2911 ( 15.2(4)M5).
Back-up APIC-EM, load the backup in a VMWare virtual machine and did a few changes, save the backup and load it back to the physical server. This seems to have forced the link re-calculation.
Currently all of the links in the Topology work and about 60% of path traces.
Comments
0 comments
Please sign in to leave a comment.