cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1645
Views
0
Helpful
10
Replies

Problem with Topology Services in LMS 4.0

merikatori08
Level 1
Level 1

Hi everybody!

I have a problem with topology view in LMS 4.0. I have three Nexus 7010 devices: DC-CORE-SWN7K01, DC-CORE-SWN7K02 and DR-CORE-SWN7K01, each connect to the others that form a triangle. DR-CORE-SWN7K01 connects to others via CWDM. when use show cdp neighbor, the output shows a device are connected to the others correctly. But in topology network view Layer 2, there is only one link connect from DR-CORE-SWN7K01 to DC-CORE-SWN7K02 as shown as in the figure below.

Links connect from DR-CORE-SWN7K01 to

topology.jpg

Some output of commands:

DC-CORE-SWN7K01

DC-CORE-SWN7K01# sh cdp nei

Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge

                  S - Switch, H - Host, I - IGMP, r - Repeater,

                  V - VoIP-Phone, D - Remotely-Managed-Device,

                  s - Supports-STP-Dispute

Device-ID             Local Intrfce Hldtme Capability  Platform      Port ID

DC-CORE-SWN7K02(JAF1528DLJD)

                            Eth3/1        141    R S I s   N7K-C7010     Eth3/1     

DC-CORE-SWN7K02(JAF1528DLJD)

                            Eth4/1        150    R S I s   N7K-C7010     Eth4/1           

DR-CORE-SWN7K01(JAF1529DFGH)

                            Eth7/1        137    R S I s   N7K-C7010     Eth3/1     

DC-CORE-SWN7K01# sh run interface e7/1

interface Ethernet7/1

  description <to DR-CORE-SWN7K01>

  ip address 10.64.124.129/30

  ip ospf authentication

  ip ospf authentication-key 3 ae7c0e0b3f4daa38

  ip ospf network point-to-point

  ip router ospf 10 area 0.0.0.0

  no shutdown

DC-CORE-SWN7K02

DC-CORE-SWN7K02# sh cdp nei

Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge

                  S - Switch, H - Host, I - IGMP, r - Repeater,

                  V - VoIP-Phone, D - Remotely-Managed-Device,

                  s - Supports-STP-Dispute

Device-ID             Local Intrfce Hldtme Capability  Platform      Port ID

DC-CORE-SWN7K01(JAF1527DPDM)

                            Eth3/1        158    R S I s   N7K-C7010     Eth3/1           

DC-CORE-SWN7K01(JAF1527DPDM)

                            Eth4/1        158    R S I s   N7K-C7010     Eth4/1         

DR-CORE-SWN7K01(JAF1529DFGH)

                            Eth7/1        130    R S I s   N7K-C7010     Eth3/2    

DC-CORE-SWN7K02# sh run inter e7/1

interface Ethernet7/1

  description <to DR-CORE-SWN7K01>

  ip address 10.64.124.133/30

  ip ospf authentication

  ip ospf authentication-key 3 ae7c0e0b3f4daa38

  ip ospf network point-to-point

  ip router ospf 10 area 0.0.0.0

  no shutdown

DR-CORE-SWN7K01

DR-CORE-SWN7K01# sh cdp nei

Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge

                  S - Switch, H - Host, I - IGMP, r - Repeater,

                  V - VoIP-Phone, D - Remotely-Managed-Device,

                  s - Supports-STP-Dispute

Device-ID             Local Intrfce Hldtme Capability  Platform      Port ID

DC-CORE-SWN7K01(JAF1527DPDM)

                            Eth3/1        124    R S I s   N7K-C7010     Eth7/1     

DC-CORE-SWN7K02(JAF1528DLJD)

                            Eth3/2        157    R S I s   N7K-C7010     Eth7/1

DR-CORE-SWN7K01# sh run interface e3/1

interface Ethernet3/1

  description < to DC-CORE-SWN7K01 E7/1 >

  ip address 10.64.124.130/30

  ip ospf authentication

  ip ospf authentication-key 3 ae7c0e0b3f4daa38

  ip ospf network point-to-point

  ip router ospf 10 area 0.0.0.0

  no shutdown

DR-CORE-SWN7K01# sh run inter e3/2

interface Ethernet3/2

  description < to DC-CORE-SWN7K02 E7/1 >

  ip address 10.64.124.134/30

  ip ospf authentication

  ip ospf authentication-key 3 ae7c0e0b3f4daa38

  ip ospf network point-to-point

  ip router ospf 10 area 0.0.0.0

  no shutdown

Can anybody tell me what problem is? What reason for missing link in topology view?

Thanks and Best Regards

Truong Ngoc Khanh

10 Replies 10

Michel Hegeraat
Level 7
Level 7

You can try to delete all links between the core devices and launch a datacollection for the core devices.

Sometimes campus gets it right when you do this.

If that fails you probably need to remove and re-add the core devices from the DCR.

Cheers,

Michel

Thanks for ur reply Michel,

It doesnt work.:(. When I shutdown the port on DR-CORE connecto to DC-CORE-SWN7K02, there is no link displayed on network topology view. Should I install patch for topology services?

Shut the port ???

No, I mean in campus, select the links between the core devices and delete them.

Then run a data collection.

Cheers,

Michel 

In Campus? I dont understand. You mean delete link directly on topology map and launch Data Collection

Thanks

Truong Ngoc Khanh

Yes, delete the links in the map.

Cheers,

Michel

merikatori08
Level 1
Level 1

It still doesnt work. Is it impossible that NX-OS cause the miss link on topology views. Would you like to provide the other information of devices? In addition, the SFPs we use are modules of CWDM with diffirent wave-length. I wonder whethre they are the reason that Topology map cannot draw this link?

Any ideas?

Thanks and Best Regards,

Truong Ngoc Khanh

Sorry to hear that.

As far as I know the campus topology is based on CDP info. And since you see all the links in the CDP tables, so should campus.

I've seen campus getting it wrong a few times, especially when there was some repatching done, but until now, when I delete the devices and re-add these devices, the next data collection gets the links correct.

Cheers,

Michel

Hi Michel!

I have deleted and re-added 3 devices a thousand times but the link connect from DR-CORE-SWN7K01 to DC-CORE-N7K01 have not appeared. Is it the bug of topology with nexus combines with CWDM? CDP neighbor table appears correctly. So disappoint

By the way, when I disable the port connect from DR-CORE-SWN7K01 to DC-CORE-SWN7K02, there is no link connect from two sites displayed on topology map??? What the hell?

Making the directory \program files\java\jre6\lib\endorsed writable is already a security risk.

Making the whole java directory under full control is overdoing it.

If you investigated then you know where it it tries to write the jar's. Not need to open up the rest.

Your IT security people should validate this.

Review Cisco Networking for a $25 gift card