cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 
cancel
668
Views
0
Helpful
1
Replies

LMS 3.2 /4.0 end hosts issues

Has someone come accross something like this.

I have 4 sites.

Each has at least 1 stack  and then 3 other Cisco Switches in the site each connected by fibre to make 4 devices per plant

LMS Reports 16 Devices which is correct.

Here is my issue

when reading the end hosts, instead of giving me the info on the end host on his specific switch, it will give me the end host info on 1 switch port 49 which is the fibre port.

This is what i would expect to see which i do not see.

00-50-ba-c9-60-18 a1649.velaninc.com 172.16.106.245 Inactive 172.16.104.0/21 P5SW2 1 0 28 inactive1 12/21/2010 10:00

=================================================================================================

Actual end host on the correct switch (Using Putty)

P5Sw2

1    0050.bac9.6018    DYNAMIC     Gi1/0/28

Using Putty on HO-SW1

   1    0050.bac9.6018    DYNAMIC     Gi1/0/49

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

This is what  LMS 3.2 Registered / 4.0 (Trial) gives me

LMS Reporting of the end host

00-50-ba-c9-60-18 a1649.velaninc.com 172.16.106.245 Inactive 172.16.104.0/21 HO-SW1 1 0 49 inactive1 12/21/2010 10:00

Does anyone have a fix for this.

J.P.

1 Reply 1

Joe Clarke
Cisco Employee
Cisco Employee

Is LMS only showing the end hosts on the uplink port, or is it showing the end hosts on the directly connected ports and the uplink port?  LMS will use two things to determine that a port is not the directly connected port.  The first is CDP.  If a port has a CDP neighbor that is also managed by LMS (i.e. shows up on the Campus topology map) then that port is ignored when looking for end hosts.  If the port is a trunk port and trunk port acquisition is disabled, then the port is ignored when looking for end hosts.

Other than those things, as long as each switch is managed by Campus (i.e. shows up with a green switch icon on the topology map) then UT should have no problem finding the end hosts on each of its access ports.