LMS 3.2 Unconnected devices

Hi all,
I'm facing some problem using the topology function in LMs 3.2.
I able to discover all my devices .however, some links are not shown in the topology service and some off the devices discovered under "unconnected device".
i attached 2 screenshot here .
the first one showing the black color links (correct and appeared) and the purple links (should have appear ).
then second screenshot showing the unconnected device but they are all in cdp neighbours list.
I need help to solve this issue.
- i tried re initiate the db
-checked all the snmp credential all are correct.
Please forgive if my explanation is very worst.
thank you very much.

Hi ,
when devices do go to the Unconnected View, it is usually one of two situations:
1. CDP information is not propagating properly or configured
CDP is vital for the device to show up on your Layer 2 View. Campus Manager
in LMS queries the CDP table from each Cisco device and see if there's a
matching entry on another Cisco device. When that is confirmed, then and
only then that device shows up in your Layer 2 view.
2. SNMP issue: either timeouts or not configured
SNMP timeouts are a very common problem when dealing with a network of a
large scale and/or a network with many switches. At times, when the SNMP
queries a Cisco Device, the request times out trying to respond.
try only deleting and re-adding on the problenmatic device from common service and then run a new data collection followed by user tracking acquisition.
once data collection and user tracking get finished then run the topology and check the issue.
Thanks-
Afroz
***Ratings Encourages Contributors ***

Similar Messages

Campusmanager 3.1, unconnected devices are reachable and CDP works fine

Hi,
our customer has the following installation: CD-One 4th-edition on Win2000-Server.
The campusmanager does not show all cat2950 wich are connected to cat 3550-12G with enhanced image. Each uplink to the 2950 is configured as "switchport mode access" and one (same) vlan is assigned on both side. I can see the cdp neighbors completely on both switches. But it is impossible to integrate the 2950 into the campusmanager.
Tese devices are presente as unconnected devices with status reachable.
Where is the failure.
Best regards.
Volker

Since you're using Campus 3.1, are the Cat2950 and 3550-12G showing up with the correct icon on the map?. Since, I don't see these listed in the Supported Device List at:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/camp_mgr/sup_dev/dev_spt.htm

Routers are showing as unconnected devices in LMS 4.2

Dear All,
I am using LMS to monitor my branch routers. I have discoved my routers but they are showing as un connected device in the topoloty Map. But my data center switches are showing as the connected devices. My routers are connected through the MPLS cloud. Does routers connected through MPLS cloud as connected devices ???
Thanks in advance,
Selva...

Hi Selva,
Currently Campus topology is supporting CDP for Topology computation. MPLS is unfortunately not supported
Thanks-
Afroz
[Do rate the useful post]

LMS 4.2.3 device and system update failing

I have upgraded to prime LMS 4.2.2 (from 4.0.1) and can not perform system or device upgrade. Using wireshark I can see why. it looks like LMS is trying to go to this old web link http://cco.cisco.com/cgi-bin/login to get software. I believe this was fixed years ago in bug CSCto46927.
Can I reapply bug fix CSCto46927 on 4.2.3 or is there another fix?
Thanks.

"It is fixed now and the issue should resolve for all the LMS server's."
Are you sure?
The error message is missed, so I asume the web page is answered correctly,
but something is wrong with package checking.
For example, at my LMS 4.2.3 the ASA package is 7.0. After checking it shows there is no package to update (Popup - "No updates available in Cisco.com for selected products")
Tcpdump shows:
            284259296
            Cisco Prime LAN Management Solution 4.2
                    283418817
                    LMS Inventory Config And Image Management Device Package Updates
                            ASA(7-1)
                            ASA(7-1)
                                7
                                4.2.2
                                1
So there is an update to 7.1. Same problem with NAM (my ver is 6.0) and the newswest at cisco.com is NAM 6.1,
On the other hand the " 4.2.2" is weird.
If a have a newer (patched) version, the packages are not available to me??
Dont understand...

LMS 4.2.3 Device pack update

Hi
Im trying to update the device pack for LMS 4.2.3, since the existing pack doesnt include 3850s. I went to Device update -> clicked inventory config and image management -> check for updates. It gives me the following error:
A PSU Task is currently been executed by another user.Only one PSU Task can be executed at a time.Please wait for the current Task to complete. The details of the currently running PSU Task are as below:
PSU Task :
Device Updates
Task Started at:
Wed Mar 05 14:16:09 EST 2014
Task Started by:
admin
NOTE : If you are sure no other download is happening , please delete the file D:\CISCOW~1\Psu.Lock
If im doing the manual way, I went to CCO and downloaded this file:
Inventory Config and Image Management Device Package version 2.12.9 for SharedSwimIOS Over LMS 4.2.3
SharedSwimIOS.RME523.v2-12-9.zip
but there is no documentation on how to manually install this ? can someone help me solve this please ?
Raj

What is the exact model of 3850 switch you're trying to monitor?
Following are the supported models :
Device Name
sysObjectID
Supported Software Version
Support Type
Device Name
sysObjectID
Supported Software Version
Support Type
Cisco Catalyst 3850-48P-E Switch
1.3.6.1.4.1.9.1.1641
Device Update
Cisco Catalyst 3850-48P-S Switch
1.3.6.1.4.1.9.1.1643
Device Update
Cisco Catalyst 3850-24P-E Switch
1.3.6.1.4.1.9.1.1642
Device Update
Cisco Catalyst 3850-24P-S Switch
1.3.6.1.4.1.9.1.1644
Device Update
Cisco Catalyst 3850-24U-E Switch
1.3.6.1.4.1.9.1.1767
03.11.35.EMP
Device Update
Cisco Catalyst 3850-48U-E Switch
1.3.6.1.4.1.9.1.1768
03.11.35.EMP
Device Update
If it is 3850-24p-L, it can be :
CSCuj61704 No support for 3850-24p-L in LMS 4.2.3
Try updating your mdf device package as well. Device package for Common Services.
For current Nexus device package issue, each device package is not individual, but has some dependant packages. Without which they are tend to fail during installation check.
You can select all the available device packages and try to install. It seems you dont have SharedDcmaIOS (3.1.7) installed and hence the package is failng due to pre-requisite.
You have to install each package which fails which consistancy check on other packages.
For mdf package update, you can select common service as well and check for update.
There may be some 3850 device packages already available, please share output of following command for us to see :
NMSROOT/bin/psucli -p rme -q -all
-Thanks
Vinod
**Rating Encourages contributors, and its really free. **

Lms 4.2 adding devices questions

Hi All,
I´m new in Prime LMS and trying to add some my network devices on cisco lms 4.2 and getting stuck on this stage.
First I tried to use the "Discovery" way and got follow messages
Total Devices Discovered: 16
Reachable Devices: 1
Unreachable Devices: 15
Devices Newly Added to DCR: 0
Devices Updated to DCR: 1
Went on "Unreachable Devices" got a list of devices saying stauts : Unreachable
any idea what could be the problem ?
AB

I found the problem was an snmp configuration missmatch on unreachable devices :/

LMS 4.2 Network Devices configuration requirement

I have install LMS 4.2 and nat ip to discover found WS-6513 but cannot polling inventory.
I serch for document about configuration on Network Devices such as switch, router, asa etc. to support LMS.
But I cannot find it, anyone have example configuration or document about this ?

Given that you have verified the SNMP RO community string and assuming you have a Supervisor 720 as noted in the compatibility matrix, you should be able to pull inventory.
As a next step I would check what is going on when you actually try to retrieve inventory.
Go into Device Center for your switch and select Tools > Packet Capture. Create a capture using the IP address of your switch and choose application SNMP (udp161). Give it adequate time, say 10 minutes (600 seconds). then go back into Device Center and choose Tools, Update Inventory. Once the Job Browser indicates the job is done )or failed), go back into the Packet Capture Window and examine the traffic captured (the jet file can be opened in Wireshark).
A successful Inventory update consists of a series of get and get-bulk requests and associated get responses from the managed device. If it's failing, there should be some response early on in one of the frames from the capture.

LMS 4.2 - DFM devices stuck in "Learning" state

Hi,
Does anybody know why this same kind of bug/error/software fault exist in LMS 4.2 as it was in LMS 3.2 ? Why after a while after discovery of devices (state is "Known") DFM drops the state of devices to "Learning" and it stucks forever. Restarting of daemon manager helps for a short time. It looks like the processing of faults stops a while after discovery is complete.
LMS 4.2 is running on Solaris 10, connected to other LMS in DCR Slave configuration.

The connection between the ciscoworks GUI and the DFM repository is not 'optimal', or something like that. It's complicated.
What could cause the behavior you mention however, is either someone rediscovering devices that are still in learning state, or the presence of multiple active rediscovery schedules.
You may even delete all schedules excepts the default redisovery schedule which you can/should suspend. If the problem then stays away you know what caused it.
At this stage any device that really changes must be rediscoverd in DFM manually.
I think Admin -> Fault takes you to a page showing the schedule, if not lookup 'fault rediscovery schedule' in the help.
Cheers,
Michel

Ciscoworks LMS 4.0 – Fault Device Details Issue

       We currently use Ciscoworks LMS 4.0 but when I go into, Monitor > Fault Settings > Setup > Fault Device Details
       I get the following message (see attached document with screenshot) and being a LMS newbie am unsure what to do? As have tried to search for this
       file but no luck.
       So thanks in advance for any advice.

Check if the fault management rediscovery page shows device as discovered and known or does it have any errors?
Are you able to generate any fault management reports and view other pages?
Just try to reboot the server/restart daemon to see if it is goes away.
Else it is mostly corrupt FM DB. Which would need to be re-initialized.
Fault Mgmt reinitialize is very simple task, which doesnt removes a lot of data, except past 31 days of FM history and custom notifications, if configured.
Thanks
Vinod
**Rating Encourages contributors, and its really free. **

LMS 3.2 some devices appear by IP not hostname

dears
i've problem in LMS 3.2 that some devices appear in RME by ip not hostname although they are in HOSTS file !
i tried to use resolver.pl tool and it can fetch the host name when typing the ip but devices still appearing by ip !
i'm using Comon Services 3.3

The device which are already in LMS DCR would stay as it is, if they are added by IP already.
If you are sure all the devices are in hosts file, than you should modify your scheduled discovery job for Update DCR Display Name check box.
Select this checkbox if you want to update the display name of the devices that already exist in DCR, in the next Device Discovery cycle.
For example, consider a device which is discovered by Common Services Device Discovery, exists in DCR with the display name as its hostname.
If you change the Preferred DCR Display Name as IP Address for the next Device Discovery, Common Services Device Discovery will update the display name of the device as its IP Address in DCR after the next Device Discovery.
The display name of devices are not overwritten in the future Device Discovery cycles if you have not selected this option.
For more details check :
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_common_services_software/3.3/user/guide/dcr.html#wp1469536
-Thanks

LMS 4.2.2 Device Interface Monitoring

HI,
On LMS 3.2 there was a way to disable the monitoring of Device Interfaces.
Examples are ISDN30 Channels, which go up and down during calls. I could disable the channel monitor on the relevant device and only monitor the Circuit as this is the main device to monitor.
I can not find the same option in 4.2.2
Could some provide the link.
Thanks

Monitor -> Fault settings -> Setup -> Fault Device Details
From there you select the device you want do modify.
To be more precise...
https://yourservername/dfm/deviceReports.do?navid=DDV_Asset

LMS 4.2 fails Device Package Update

Hallo,
Device Package Update fails with this error:
Error while downloading package information from Cisco.com for the selected products. See the d:/CSCOpx/log/psu.log file for details.
PSU.log shows:
ERROR [RemoteRepSync : downloadPsuHeadersAsXml] : VDSException thrown com.cisco.nm.xms.vds.VDSException: CcoDownloadAdapter::getXmlFileList():IOException:connect timed out
best regards
Alex

What is the exact model of 3850 switch you're trying to monitor?
Following are the supported models :
Device Name
sysObjectID
Supported Software Version
Support Type
Device Name
sysObjectID
Supported Software Version
Support Type
Cisco Catalyst 3850-48P-E Switch
1.3.6.1.4.1.9.1.1641
Device Update
Cisco Catalyst 3850-48P-S Switch
1.3.6.1.4.1.9.1.1643
Device Update
Cisco Catalyst 3850-24P-E Switch
1.3.6.1.4.1.9.1.1642
Device Update
Cisco Catalyst 3850-24P-S Switch
1.3.6.1.4.1.9.1.1644
Device Update
Cisco Catalyst 3850-24U-E Switch
1.3.6.1.4.1.9.1.1767
03.11.35.EMP
Device Update
Cisco Catalyst 3850-48U-E Switch
1.3.6.1.4.1.9.1.1768
03.11.35.EMP
Device Update
If it is 3850-24p-L, it can be :
CSCuj61704 No support for 3850-24p-L in LMS 4.2.3
Try updating your mdf device package as well. Device package for Common Services.
For current Nexus device package issue, each device package is not individual, but has some dependant packages. Without which they are tend to fail during installation check.
You can select all the available device packages and try to install. It seems you dont have SharedDcmaIOS (3.1.7) installed and hence the package is failng due to pre-requisite.
You have to install each package which fails which consistancy check on other packages.
For mdf package update, you can select common service as well and check for update.
There may be some 3850 device packages already available, please share output of following command for us to see :
NMSROOT/bin/psucli -p rme -q -all
-Thanks
Vinod
**Rating Encourages contributors, and its really free. **

LMS 3.2 Adding Devices Manually

Can anyone tell me if I need a seed devices to add devices manually or can I just bypass this portion of the setup since I'm NOT going to be discovering anything with Ciscoworks.(My envoronment is to complex to perform and discovering) Or do I need a seed device anyhow for functionality of Ciscoworks and other processes?
Please advaise & thank you in advance,
Erick

If you are adding devices manually, there is no need for a seed device. The whole purpose of seed devices is to use it as staging for discovering neighboring devices.
There is a great document written on the CSDiscovery process in LMS by Joe.
https://supportforums.cisco.com/docs/DOC-9005

Where is LMS 4.0 Detailed Device View ?

Can someone tell me how to get the Detailed Device View in LMS 4.0 please?
From what I have been able to find out I should be able to go do Monitor> Fault Settings> Setup> Fault Device Details, select a device, click View and then click the device name link.
Unfortunatly the device name(s) displayed are not links, just text.
I need to get the the Detailed Device View so that I can block certain interfaces/events from generating alarms, specifically ISDNB channels when voice calls are made.
Steve

I just checked mine and following the navigation you noted above it works for me - I can navigate down to unmanage individual interfaces. See the screenshot below.
FWIW, I am running LMS 4.2.2 on soft appliance and am logged in as admin.

Cisco Prime LMS 4.2 DFM Devices Missing

Hi Everybody
Having manually added a device into the DCR and confirmed that it's in a managed state I cannot get added into DFM. Within Device Centre, it's collector status against "Data Collection", "Inventory", and "Fault Discovery" are all Success.
My Device Allocation Policy (Inventory > Device Administration: Device Allocation Policy) is currently set to Manage All Devices.
Running "geti Router" from within dmctl -s DFM returns all but the device in question.
I have manually deleted and readded and have also restarted service CRMDmgtd.
Many Thanks in anticipation.

Hi,
can you try to remove it from DB as below ::
NMSROOT/Objects/smarts/bin/dmctl -s DFM invoke <Class>::<Instance> remove
Class => Switch or Router,
Instance => Device IP or Name.
dmctl> invoke Switch::X.X.X.X remove
then add the device back in LMS and see if it makes any difference.
Also try to increase the SNMP timeout and retry for DFM:
Admin > Network > Timeout and RetrySettings> FaultManagement SNMP Timeouts and Retries
Thanks-
Afroz
***Ratings Encourages Contributors ***

LMS 3.2 Unconnected devices

Similar Messages

Maybe you are looking for