LMS 3.0.1 SNMP working.

Hi all.
After i upgraded my MDF to 1.50 the SNMP is not working.
I alread applied the fix to bug CSCsl00042-0 but still not working.
The SO is solaris 9.
Follow the package details.
1. CiscoWorks Common Services 3.1.1
2. CiscoView 6.1.7
3. LMS Portal 1.0.1
4. CiscoWorks Assistant 1.0.1
5 Resource Manager Essentials 4.1.1
root@AL-GR-SV-RL # cd /opt/CSCOpx/bin/
root@AL-GR-SV-RL # ls -lh
-rw-r--r-- 1 root other 7.3K May 27 17:09 CSCsl00042-0.pl
Thank you.

Here is the information you are looking for:
CiscoWorks LAN Management Solution (WINDOWS OS) 3.2
https://cisco.mediuscorp.com/market/networkers/productView.se.work?/nxt/rcrs/proieidentity/=17651
Prerequisites
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/3.2/install/guide1/prereq.html
Data Migration Guide for LAN Management Solution 3.2
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/3.2/data_migration/guide/lms32_dmg.html

Similar Messages

LMS 3.2 with SNMP v3 not working

Hi ,
My network is currently running with SNMP v2 configured in easch devices. With snmp v2 our LMS 3.2 server is working fine. However we have planned to migrate our network to snmp v3 . I have configured my few devices for SNMP v3 and added them to my LMS server.
Except DFM module these new SNMP v3 devices are working fine in all other modules. In DFM these devices are reflecting under "snmp timeout" group.
I checked with device center -> management station to device; where the SNMP v3 connections are showing "okey"
following are tyhe configuration i have done in my devices.
snmp-server group v3g v3 priv read testr write testw
snmp-server user v3u v3g v3 auth md5 test123
snmp-server view testr iso in
snmp-server view testw iso in
snmp-server host 10.X.X.38 version 3 priv v3u
snmp-server user v3u v3g v3 auth md5 test1234 priv des56 test4321
snmp-server group v3g v3 priv read testr write testw
snmp-server user v3u v3g v3 auth md5 test123
snmp-server view testr iso in
snmp-server view testw iso in
snmp-server host 10.X.X.38 version 3 priv v3u
snmp-server user v3u v3g v3 auth md5 test1234 priv des56 test4321
followinfg are my module details.
LMS      : 3.2
CM        : 5.2
CV          :6.1.9
CS          :3.3.0
DFM     : 3.2.0
IPM     : 4.2.0
RME     : 4.3.0

DFM behaves different than the other modules.
DES56 is not a supported privacy algorithm for DFM. You can use DES or AES128.
Supported Algorithms in DFM
The details of the algorithms supported in DFM are:
•AuthNoPriv Mode — Supported Auth Algorithm: MD5 and SHA
•AuthPriv Mode
–Supported Auth Algorithm: MD5 and SHA
–Supported Privacy Algorithm: DES and AES128
–Unsupported Privacy Algorithm: 3DES, AES192, and AES256
For more details check :
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_device_fault_manager/3.2/user/guide/useDevMg.html#wp1483766
-Thanks
Vinod

Can't get SNMP working

I've turned on SNMP in Server Admin and the snmpd (daemon) is running as verifed in Activity Monitor. The snmpd.conf file is located at /usr/share/snmp and everything looks as it should. But, I can not access the snmp data from a client. When I use InterMapper I get the error "NO SNMPv1response" error. I did a port scan on port 161 and it's not showing. However I have an Airport Extreme on the same network and it is providing SNMP data to InterMapper, so I assume my router isn't blocking port 161 on the LAN. To test this I removed the host and client from the router and connected them to a hub- still no SNMP data.
I must be missing something because it should work the way I have it setup. Any help is appreciated.
Thanks!

Thanks Camelot you got me pointed in the right direction... that snmpconf file. I've now got SNMP working and Intermapper see's the data. Here is what I did (in case anyone else runs into this):
1) Delete all your previous snmpconf files. Look in the root of your user folder- if there is one there delete it. Then use Terminal and go to /usr/share/snmp/ and delete that one too.
2)Still in Terminal, run
sudo /usr/bin/snmpconf -i
Hint: I was following the instructions here <http:docs.info.apple.com/article.html?artnum=107012> which was good up until you get to the "You will then see a series of text menus. Make these choices in this order:" Instead of doing those suggested settings, here is what I entered:
I can create the following types of configuration files for you.
Select the file type you wish to create:
(you can create more than one as you run this program)
1: snmpd.conf
2: snmptrapd.conf
3: snmp.conf
Other options: quit
Select File: 1
The configuration information which can be put into snmpd.conf is divided
into sections. Select a configuration section for snmpd.conf
that you wish to create:
1: Access Control Setup
2: Extending the Agent
3: Monitor Various Aspects of the Running Host
4: Agent Operating Mode
5: System Information Setup
6: Trap Destinations
Other options: finished
Select section: 5
Section: System Information Setup
Description:
This section defines some of the information reported in
the "system" mib group in the mibII tree.
Select from:
1: The [typically physical] location of the system.
2: The contact information for the administrator
3: The proper value for the sysServices object.
Other options: finished, list
Select section: 1
Configuring: syslocation
Description:
The [typically physical] location of the system.
arguments: location_string
The location of the system: <ENTER YOUR TEXT HERE-NO SPACE>
Finished Output: syslocation <THE TEXT YOU ENTERED WILL SHOW HERE>
Section: System Information Setup
Description:
This section defines some of the information reported in
the "system" mib group in the mibII tree.
Select from:
1: The [typically physical] location of the system.
2: The contact information for the administrator
3: The proper value for the sysServices object.
Other options: finished, list
Select section: f
The configuration information which can be put into snmpd.conf is divided
into sections. Select a configuration section for snmpd.conf
that you wish to create:
1: Access Control Setup
2: Extending the Agent
3: Monitor Various Aspects of the Running Host
4: Agent Operating Mode
5: System Information Setup
6: Trap Destinations
Select section: 1
Section: Access Control Setup
Description:
This section defines who is allowed to talk to your running
snmp agent.
Select from:
1: a SNMPv3 read-write user
2: a SNMPv3 read-only user
3: a SNMPv1/SNMPv2c read-only access community name
4: a SNMPv1/SNMPv2c read-write access community name
Other options: finished, list
Select section: 3
Configuring: rocommunity
Description:
a SNMPv1/SNMPv2c read-only access community name
arguments: community [default|hostname|network/bits] [oid]
The community name to add read-only access for: public <MOST AGENTS USE "PUBLIC" AS A DEFAULT- LIKE INTERMAPPER>
The hostname or network address to accept this community name from [RETURN for all]:
The OID that this community should be restricted to [RETURN for no-restriction]:
Finished Output: rocommunity public
Section: Access Control Setup
Description:
This section defines who is allowed to talk to your running
snmp agent.
Select from:
1: a SNMPv3 read-write user
2: a SNMPv3 read-only user
3: a SNMPv1/SNMPv2c read-only access community name
4: a SNMPv1/SNMPv2c read-write access community name
Other options: finished, list
Select section: f
The configuration information which can be put into snmpd.conf is divided
into sections. Select a configuration section for snmpd.conf
that you wish to create:
1: Access Control Setup
2: Extending the Agent
3: Monitor Various Aspects of the Running Host
4: Agent Operating Mode
5: System Information Setup
6: Trap Destinations
Other options: finished
Select section: 4
Section: Agent Operating Mode
Description:
This section defines how the agent will operate when it
is running.
Select from:
1: Should the agent operate as a master agent or not.
2: The system user that the agent runs as.
3: The system group that the agent runs as.
4: The IP address and port number that the agent will listen on.
Other options: finished, list
Select section: 1
Configuring: master
Description:
Should the agent operate as a master agent or not.
Currently, the only supported master agent type for this token
is "agentx".
arguments: (on|yes|agentx|all|off|no)
Should the agent run as a AgentX master agent?:
invalid answer! It must match this regular expression: ^(on|yes|agentx|all|off|no)$
Should the agent run as a AgentX master agent?: y <THIS IS CRITICAL>
invalid answer! It must match this regular expression: ^(on|yes|agentx|all|off|no)$
Should the agent run as a AgentX master agent?: yes
Finished Output: master yes
Section: Agent Operating Mode
Description:
This section defines how the agent will operate when it
is running.
Select from:
1: Should the agent operate as a master agent or not.
2: The system user that the agent runs as.
3: The system group that the agent runs as.
4: The IP address and port number that the agent will listen on.
Other options: finished, list
Select section: 4
Configuring: agentaddress
Description:
The IP address and port number that the agent will listen on.
By default the agent listens to any and all traffic from any
interface on the default SNMP port (161). This allows you to
specify which address, interface, transport type and port(s) that you
want the agent to listen on. Multiple definitions of this token
are concatenated together (using ':'s).
arguments: [transport:]port[@interface/address],...
Enter the port numbers, etc that you want the agent to listen to:
Finished Output: agentaddress
Section: Agent Operating Mode
Description:
This section defines how the agent will operate when it
is running.
Select from:
1: Should the agent operate as a master agent or not.
2: The system user that the agent runs as.
3: The system group that the agent runs as.
4: The IP address and port number that the agent will listen on.
Other options: finished, list
Select section: f
The configuration information which can be put into snmpd.conf is divided
into sections. Select a configuration section for snmpd.conf
that you wish to create:
1: Access Control Setup
2: Extending the Agent
3: Monitor Various Aspects of the Running Host
4: Agent Operating Mode
5: System Information Setup
6: Trap Destinations
Other options: finished
Select section: f
I can create the following types of configuration files for you.
Select the file type you wish to create:
(you can create more than one as you run this program)
1: snmpd.conf
2: snmptrapd.conf
3: snmp.conf
Other options: quit
Select File: q
The following files were created:
snmpd.conf installed in /usr/share/snmp
*If these steps are wrong please feel free to correct me.

LMS 3.2 - unknow SNMP error for Cisco XR12406

Hi ,
I got a RME job alert which describes SNMP RW community verification failure in Device Credentials Verification for Cisco XR12406 router, I have double checked on the credential configured in LMS and it is correct.
The configuration that i tried in XR12406:
snmp-server community T3lBruRW RW <acl>   ---> not working
snmp-server community T3lBruRW RW SystemOwner <acl> ---> not working
Anyone can help!!!

Hi Nael, here it is:
#sh ver
Sun Nov 28 15:43:14.648 BNT
Cisco IOS XR Software, Version 3.8.2[00]
Copyright (c) 2009 by Cisco Systems, Inc.
ROM: System Bootstrap, Version 12.0(20060713:113510) [sunnaik-31s5th 1.16dev(0.1)] DEVELOPMENT SOFTWARE
Copyright (c) 1994-2006 by cisco Systems, Inc.
CRTH uptime is 8 weeks, 2 days, 20 hours, 45 minutes
System image file is "disk0:c12k-os-mbi-3.8.2/mbiprp-rp.vm"
cisco 12406/PRP (7457) processor with 2097152K bytes of memory.
7457 processor at 1266Mhz, Revision 1.2
3 Cisco 12000 Series SPA Interface Processor-601/501/401
2 Cisco 12000 Series Performance Route Processors
6 Management Ethernet
12 PLIM_QOS
4 TenGigE
15 GigabitEthernet/IEEE 802.3 interface(s)
1018k bytes of non-volatile configuration memory.
1998M bytes of compact flash card.
2048800k bytes of disk0: (Sector size 512 bytes).
65536k bytes of Flash internal SIMM (Sector size 256k).
Boot device on node 0/0/CPU0 is mem:
Package active on node 0/0/CPU0:
c12k-k9sec, V 3.8.2[00], Cisco Systems, at disk0:c12k-k9sec-3.8.2
    Built on Wed Oct 28 19:00:47 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-lc, V 3.8.2[00], Cisco Systems, at disk0:c12k-lc-3.8.2
    Built on Wed Oct 28 16:27:50 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-fwdg, V 3.8.2[00], Cisco Systems, at disk0:c12k-fwdg-3.8.2
    Built on Wed Oct 28 16:26:44 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-admin, V 3.8.2[00], Cisco Systems, at disk0:c12k-admin-3.8.2
    Built on Wed Oct 28 16:25:55 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-base, V 3.8.2[00], Cisco Systems, at disk0:c12k-base-3.8.2
    Built on Wed Oct 28 16:24:15 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-os-mbi, V 3.8.2[00], Cisco Systems, at disk0:c12k-os-mbi-3.8.2
    Built on Wed Oct 28 16:19:12 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
Boot device on node 0/1/CPU0 is mem:
Package active on node 0/1/CPU0:
c12k-k9sec, V 3.8.2[00], Cisco Systems, at disk0:c12k-k9sec-3.8.2
    Built on Wed Oct 28 19:00:47 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-lc, V 3.8.2[00], Cisco Systems, at disk0:c12k-lc-3.8.2
    Built on Wed Oct 28 16:27:50 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-fwdg, V 3.8.2[00], Cisco Systems, at disk0:c12k-fwdg-3.8.2
    Built on Wed Oct 28 16:26:44 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-admin, V 3.8.2[00], Cisco Systems, at disk0:c12k-admin-3.8.2
    Built on Wed Oct 28 16:25:55 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-base, V 3.8.2[00], Cisco Systems, at disk0:c12k-base-3.8.2
    Built on Wed Oct 28 16:24:15 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-os-mbi, V 3.8.2[00], Cisco Systems, at disk0:c12k-os-mbi-3.8.2
    Built on Wed Oct 28 16:19:12 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
Boot device on node 0/2/CPU0 is mem:
Package active on node 0/2/CPU0:
c12k-k9sec, V 3.8.2[00], Cisco Systems, at disk0:c12k-k9sec-3.8.2
    Built on Wed Oct 28 19:00:47 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-lc, V 3.8.2[00], Cisco Systems, at disk0:c12k-lc-3.8.2
    Built on Wed Oct 28 16:27:50 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-fwdg, V 3.8.2[00], Cisco Systems, at disk0:c12k-fwdg-3.8.2
    Built on Wed Oct 28 16:26:44 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-admin, V 3.8.2[00], Cisco Systems, at disk0:c12k-admin-3.8.2
    Built on Wed Oct 28 16:25:55 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-base, V 3.8.2[00], Cisco Systems, at disk0:c12k-base-3.8.2
    Built on Wed Oct 28 16:24:15 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-os-mbi, V 3.8.2[00], Cisco Systems, at disk0:c12k-os-mbi-3.8.2
    Built on Wed Oct 28 16:19:12 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
Configuration register on node 0/4/CPU0 is 0x2102
Boot device on node 0/4/CPU0 is disk0:
Package active on node 0/4/CPU0:
c12k-k9sec, V 3.8.2[00], Cisco Systems, at disk0:c12k-k9sec-3.8.2
    Built on Wed Oct 28 19:00:47 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-rout-3.8.2.CSCti62211, V 1.0.0[SMU], Cisco Systems, at disk0:c12k-rout-3.8.2.CSCti62211-1.0.0
    Built on Sat Aug 28 15:36:26 BNT 2010
    By edde-bld1 in /vws/afz/builds/smu_r38x_3_8_2/workspace for c4.2.1-p0
c12k-rout, V 3.8.2[00], Cisco Systems, at disk0:c12k-rout-3.8.2
    Built on Wed Oct 28 16:28:36 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-lc, V 3.8.2[00], Cisco Systems, at disk0:c12k-lc-3.8.2
    Built on Wed Oct 28 16:27:50 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-fwdg, V 3.8.2[00], Cisco Systems, at disk0:c12k-fwdg-3.8.2
    Built on Wed Oct 28 16:26:44 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-admin, V 3.8.2[00], Cisco Systems, at disk0:c12k-admin-3.8.2
    Built on Wed Oct 28 16:25:55 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-base, V 3.8.2[00], Cisco Systems, at disk0:c12k-base-3.8.2
    Built on Wed Oct 28 16:24:15 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-os-mbi, V 3.8.2[00], Cisco Systems, at disk0:c12k-os-mbi-3.8.2
    Built on Wed Oct 28 16:19:12 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
Configuration register on node 0/5/CPU0 is 0x2102
Boot device on node 0/5/CPU0 is disk0:
Package active on node 0/5/CPU0:
c12k-k9sec, V 3.8.2[00], Cisco Systems, at disk0:c12k-k9sec-3.8.2
    Built on Wed Oct 28 19:00:47 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-rout-3.8.2.CSCti62211, V 1.0.0[SMU], Cisco Systems, at disk0:c12k-rout-3.8.2.CSCti62211-1.0.0
    Built on Sat Aug 28 15:36:26 BNT 2010
    By edde-bld1 in /vws/afz/builds/smu_r38x_3_8_2/workspace for c4.2.1-p0
c12k-rout, V 3.8.2[00], Cisco Systems, at disk0:c12k-rout-3.8.2
    Built on Wed Oct 28 16:28:36 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-lc, V 3.8.2[00], Cisco Systems, at disk0:c12k-lc-3.8.2
    Built on Wed Oct 28 16:27:50 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-fwdg, V 3.8.2[00], Cisco Systems, at disk0:c12k-fwdg-3.8.2
    Built on Wed Oct 28 16:26:44 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-admin, V 3.8.2[00], Cisco Systems, at disk0:c12k-admin-3.8.2
    Built on Wed Oct 28 16:25:55 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-base, V 3.8.2[00], Cisco Systems, at disk0:c12k-base-3.8.2
    Built on Wed Oct 28 16:24:15 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
c12k-os-mbi, V 3.8.2[00], Cisco Systems, at disk0:c12k-os-mbi-3.8.2
    Built on Wed Oct 28 16:19:12 BNT 2009
    By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0

How LMS 3.1 uses SNMP passwords

Hi
We are currently in the process of changing our SNMP RO passwords on devices via using groups in DCR. As this is to be a stage by stage excercise (i.e 20 devices one week, 20 devices the following week), does the SNMP need to be changed as a default within Ciscoworks and where do you do this and any problems this could cause ?
As far as I can see the SNMP RO password from ciscoworks is used to verify device info in the DCR and not for device config retrieval that is performed from RME. Is this correct ?
Many Thanks

AFAIK, the SNMP RO string gets used in IPM and CiscoView for reading certain configurations (and SNMP RW is used for writing configuraitons). And after seeing this thread: https://supportforums.cisco.com/thread/2003225?tstart=0, it seems Campus Manager might use the RW too, which is news to me.
If you're not using those LMS components, you can probably get away with leaving obsolete SNMP strings in DCR.

LMS 4.0.1, stops working.

Hello at all.
Another issue with CiscoWorks LMS 4.0.1 running on Windows 2008 EE SP2 64bit.
After some hours, It stops working: Device Management, or any other application, does not show devices.
We need to restart the server.
Any ideas?
Thanks.
Regards.
Andrea

Without logging or additional details it is hard to guess. However, if things stop working unexpectedly, chances are something is tampering with the LMS services (anti-virus or such). Take a look at this DOC and make sure the server is following steps 1 and 2. Those would be usual culprits for similar behavior. You can get a good idea on how to figure out problems in LMS when processes are down using that DOC as well.

LMS 4.0 no longer working after reboot

I have LMS v4.0 installed and was it working fine (Windows Server 2008R2 Std).
However, I had call to reboot the physical server last week (it had been up for over 6 months) and I am now having problems with most options under the Inventory menu.
I have attached screenshots of the errors I am getting and the end of the DCRServer.log file which indicates that the DCR server has started ok.
I have disabled the DHCP Client service as I saw in another post that this has been known to cause the issue I am seeing, but that has not made any difference.
I have exhausted everything I can think of and am hoping that someone on here can give me some advice or ideas as to where to look next.
Thanks
Steve

Do all the 'connection refused' lines in stdout.log mean anything....
=30000. Reason: java.net.ConnectException: Connection refused: connect, Feb 10 11:16:37
LTGateway.run(): Could not connect to Message Queue, javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:42351?wireFormat.maxInactivityDuration=0&wireFormat.maxInactivityDurationInitalDelay=30000. Reason: java.net.ConnectException: Connection refused: connect, Feb 10 11:16:38
LTGateway.run(): Could not connect to Message Queue, javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:42351?wireFormat.maxInactivityDuration=0&wireFormat.maxInactivityDurationInitalDelay=30000. Reason: java.net.ConnectException: Connection refused: connect, Feb 10 11:16:39
LTGateway.run(): Could not connect to Message Queue, javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:42351?wireFormat.maxInactivityDuration=0&wireFormat.maxInactivityDurationInitalDelay=30000. Reason: java.net.ConnectException: Connection refused: connect, Feb 10 11:16:40
LTGateway.run(): Could not connect to Message Queue, javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:42351?wireFormat.maxInactivityDuration=0&wireFormat.maxInactivityDurationInitalDelay=30000. Reason: java.net.ConnectException: Connection refused: connect, Feb 10 11:16:41
LTGateway.run(): Could not connect to Message Queue, javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:42351?wireFormat.maxInactivityDuration=0&wireFormat.maxInactivityDurationInitalDelay=30000. Reason: java.net.ConnectException: Connection refused: connect, Feb 10 11:16:42
LTGateway.run(): Could not connect to Message Queue, javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:42351?wireFormat.maxInactivityDuration=0&wireFormat.maxInactivityDurationInitalDelay=30000. Reason: java.net.ConnectException: Connection refused: connect, Feb 10 11:16:43
LTGateway.run(): Could not connect to Message Queue, javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:42351?wireFormat.maxInactivityDuration=0&wireFormat.maxInactivityDurationInitalDelay=30000. Reason: java.net.ConnectException: Connection refused: connect, Feb 10 11:16:44
LTGateway.run(): Could not connect to Message Queue, javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:42351?wireFormat.maxInactivityDuration=0&wireFormat.maxInactivityDurationInitalDelay=30000. Reason: java.net.ConnectException: Connection refused: connect, Feb 10 11:16:45
LTGateway.run(): Could not connect to Message Queue, javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:42351?wireFormat.maxInactivityDuration=0&wireFormat.maxInactivityDurationInitalDelay=30000. Reason: java.net.ConnectException: Connection refused: connect, Feb 10 11:16:46
LTGateway.run(): Could not connect to Message Queue, javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:42351?wireFormat.maxInactivityDuration=0&wireFormat.maxInactivityDurationInitalDelay=30000. Reason: java.net.ConnectException: Connection refused: connect, Feb 10 11:16:47
LTGateway.run(): Could not connect to Message Queue, javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:42351?wireFormat.maxInactivityDuration=0&wireFormat.maxInactivityDurationInitalDelay=30000. Reason: java.net.ConnectException: Connection refused: connect, Feb 10 11:16:48
LTGateway.run(): Could not connect to Message Queue, javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:42351?wireFormat.maxInactivityDuration=0&wireFormat.maxInactivityDurationInitalDelay=30000. Reason: java.net.ConnectException: Connection refused: connect, Feb 10 11:16:49
LTGateway.run(): Could not connect to Message Queue, javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:42351?wireFormat.maxInactivityDuration=0&wireFormat.maxInactivityDurationInitalDelay=30000. Reason: java.net.ConnectException: Connection refused: connect, Feb 10 11:16:50
LTGateway.run(): Could not connect to Message Queue, javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:42351?wireFormat.maxInactivityDuration=0&wireFormat.maxInactivityDurationInitalDelay=30000. Reason: java.net.ConnectException: Connection refused: connect, Feb 10 11:16:51
LTGateway.run(): Could not connect to Message Queue, javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:42351?wireFormat.maxInactivityDuration=0&wireFormat.maxInactivityDurationInitalDelay=30000. Reason: java.net.ConnectException: Connection refused: connect, Feb 10 11:16:52

Ciscoworks LMS 2.5 don`t working software & devices updates

Terrible happened The old server with LMS on the Solaris operating system refused to work, but I have backup. I installed LMS 2.5 (CiscoView 6.1.2), RME 4.0.3. Posted all network objects that were in the old system from backup. But none of them can not do in the utility Netconfig, all the checkbox on the switches Cisco ME 3400-24TS-A inactive, butwith the Cisco 3750 is no such problem, it works. As I understand it, I must run Device Update, but the answer is a "No updates available in CCO for selected product (s)." The same problem with Software Update, I can not upgrade to LMS 2.6 and other products too. Tell me what to do? Some screenshots attached below.

Maybe Cisco has stopped maintaining the online update repositories for LMS 2.x. Alternatively, you can try finding the relevant RME/CiscoView/Campus Manager device updates at
http://www.cisco.com/cisco/software/navigator.html?mdfid=268439477&i=rp
For example, select RME, instead of LMS, to find if the RME device pkgs are available for download. Once downloaded, you can apply them on the LMS servers locally.

CiscoWorks LMS: not receveing certain SNMP traps

CiscoWorks LMS 4.0.1 (I know it's old and unsupported).
Problem: not receiving certain SNMP traps.
For example: I receive trap like "STP new root" but not like "port put to err-disabled" or my custom traps (produced by EEM scripts).
I've investigated my situation and found out that switch sends traps and they reach* LMS but somehow LMS ignores them (there's no trace of them in GUI). I've read that some traps just pass through LMS but my traps are very important and I need to know about them.
* I did Wireshark capture on LMS machine.
I'd like to know how to debug receiving of SNMP traps in LMS:
which specific debugs need to be enabled,
which specific log files need to be examined.

LMS uses DFM to process certain traps.
All traps it deems unimportant are dropped.
If you want to use the LMS GUI you can have you device send a SYSLOG message rather than a trap.
use logging source command to make the management interface send the message.
Then there is a GUI that allows you to launch an action on a message
Cheers,
Michel

Absorb LMS (Learning Management System), not working

I'm launching an online learning course that is implemented by Absorb LMS.
They seem to be using flash and JAVA for their online courses.
I installed the latest flash and JAVA runtime, but I can't hear any sound just
can see video in Safari.
I have OS X 10.8 and latest Safari browser.
Any help is appreciated.

From your Safari menu bar click Safari > Preferences then select the Security tab.
Make sure Allow Java and Allow all other plug-ins is selected.

CW LMS 3.0.1 not working after updating Campus manager to 5.0.6

Hi,
I upgraded my CW Campus Manager from 5.0.5 to 5.0.6, and now when I try to access CW I get :
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Any idea how to fix this?
Thanks in advance

Post the NMSROOT/MDC/Apache/logs/error.log and NMSROOT/MDC/tomcat/logs/stdout.log and stderr.log.

MPLS LDP Hello Adjacencies via SNMP (Working Sporadically)

Hi folks.
I'm having a problem trying to replicate the MPLS LDP hello adjacencies I see on the CLI by running 'show mpls ldp neighbor' with results from walking mplsLdpHelloAdjacencyType and other related OID's.
Here are some 'show mpls ldp neighbor' snippets:
Peer LDP Ident: 10.7.0.1:0; Local LDP Ident 10.7.2.1:0
TCP connection: 10.7.0.1.646 - 10.7.2.1.43828
State: Oper; Msgs sent/rcvd: 162371/161638; Downstream
Up time: 7w3d
LDP discovery sources:
Targeted Hello 10.7.2.1 -> 10.7.0.1, active, passive
Addresses bound to peer LDP Ident:
10.7.0.1 [etc]
Peer LDP Ident: 10.7.63.1:0; Local LDP Ident 10.7.2.1:0
TCP connection: 10.7.63.1.26327 - 10.7.2.1.646
State: Oper; Msgs sent/rcvd: 163080/163018; Downstream
Up time: 7w3d
LDP discovery sources:
Targeted Hello 10.7.2.1 -> 10.7.63.1, active, passive
Addresses bound to peer LDP Ident:
10.7.63.1 [etc]
In this case I'd like to add monitoring to ensure an adjacency exists between this router and 10.7.0.1 and 10.7.63.1. I walk mplsLdpHelloAdjacencyType:
[fgeueke@dev2:~ 11:53 AM]$ snmpwalk -Ob -v1 -c[snip] 10.7.2.1 mplsLdpHelloAdjacencyType |grep '\.10\.7\.$0\|63$\.1'
MPLS-LDP-STD-MIB::mplsLdpHelloAdjacencyType.10.7.2.1.0.0.168230913.10.7.0.1.0.0.1 = INTEGER: targeted(2)
Notice the absences of an entry for 10.7.63.1. The router in this example is a 7604 running c7600s72033-advipservicesk9-mz.122-33.SRE9 but I'm getting similar results for other 7600's and ASR's.
I've had a TAC case open for over a year on this with little success - so I figured I'd post to the group. Has anyone run into something similar? Thanks!

Hi,
Would it be possible to disable the functionality of the DPI (passthrough mode?) and test again?
MPLS labels or not on the packet should not make a difference wrt HTTPS only (in theory).
Since you mention corrupted frames, taking a packet capture should show you if this is true or not.
Thanks,
Luc

LMS 4.2 with Nexus C7010 Switch

Hi Guys,
I tried to add Nexus C7010 into my LMS 4.2, the SNMP work like charm but not for the archieve config.
It just show "Incorrect" under SSH, further checking I found this
"Failed to establish SSH connection to 10.152.xx.xx - Cause: Authentication failed on device 3 times."
I understand that Nexus is using Role-Based Account and there is no enable secret password anymore.
How do I add the Credential for Nexus? Other devices with IOS is no problem at all.
Please Help... Thank you.

Pls try this...
There is a legacy Button on top right corner, select DFM, then select Event sets and select the required triggering fields like flap, operationallydown etc... and make it as A (there is a tick mark available to group all these fields under 'A' group.
Secondly, go to email notification group and select all the devices which you want to monitor and select Alerts and over there select 'A', then select Critical, Warning etc, click next next...
For rest of it, pls go by the logic.
E-Mail Configuration Tasks
Managing E-Mail Notification Subscriptions
CiscoWorks LMS Portal > Device Fault Manager > Notification Services > E-Mail Configuration > E-Mail Notification
Admin > Network: Notification and Action Settings > Fault - Email notification
The E-Mail Notification Subscription page displays information about subscription, status and notification group.

Cisco LMS 4.2.3 - Nexus VDC - SNMP

Hi All,
I am having some trouble with getting inventory collection work for the VDC's of a Nexus 7k from LMS 4.2.3.
The collection works for the main VDC, just not any of the others.
I have verified (using SNMPWALK) from the LMS server that the snmp credentials in use on the LMS for these VDC's is correct.
We are using SNMP V3.
The error I am getting when trying to run an inventory collection is:
Device Collection Failed. Failed to fetch Containment details.
Does anyone have any experience with getting VDC's to work in LMS and may have seen this error before?
Thanks in advance.

Hi ,
You are hitting the below BUG:
LMS 4.2.3 Inventory collection is failing for some of Nexus 7k devices
CSCuh49814
Development team is still working on the fix.
Thanks-
Afroz
[Do rate the useful post]

LMS 4.2.4 -- Problem with UT & Inventory when using SNMP v3

Hello,
I have created a Credential-Set with SNMP v2 and SNMP v3 credentials and enabled at the discovery settings the fallback option from snmp v3 to v2. For the discovery this setting works but at the inventory collection and the UT it seems that the LMS just tries the snmp v3 credentials. Is there a way to enable also a fallback to snmp v2? Because now only our devices with snmp v3 get a success all other devices get a failed.
Using LMS 4.2.4
regards,
David

Hi David,
What type of credentials set you are using in DCR ?
there is no fall back mechnasim for Inventory collectio and User tracking .
Inventory collection and user tracking will get the credentials from the credentials that you are using in DCR .
Inventory should be sucessfull as long as you have correct credentils defied in DCR.
Thanks-
Afroz
[Do rate the useful post]

LMS 3.0.1 SNMP working.

Similar Messages

Maybe you are looking for