Cisco :: LMS 4.2 - DFM Devices Stuck In Learning State
Apr 15, 2012
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 works 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.
I'm having problem with DFM under LMS 3.2. For some reason it periodically loses discovered devices and put all of them into "Learining" state. Sometimes restarting daemon manager useful but now it doesn't. I tried rediscovery few times but it doesn't work at all.
Ages ago I was shadowing someone making a change on the network. I cannot remember which spanning tree version was running and cannot remember the config of any port either. What I do remember is that every switch port on the 2960 switch went orange and an outage occured, where the ports went into listening / learning mode. I assume that the STP was just the default ieee 802.1D.
I have this one device that is stuck in DFM Questioned state. The device is correctly discovered in CS and I have collected its configuration through ConfigMgmt (RME).I run Device Troubleshooting against it:
Cisco Prime 4.2. My device is stuck in Questioned state in Fault Management. The device though can be pinged from the server. Actually, I can already manage the device and have archived its configuration. Problem is, on Fault Monitoring Device Administration, its on Questioned state even though I already tried to rediscover the device several times.Do I need to configure something on the server like put in the IP address and hostname of the device in the host file of Windows Server 2008?
I am working on LMS 3.2 . Tried to stop the daemon service with " net stop crmdmgtd ". It stuck on stopping state since few hours now. I can still open the application. How to terminate the previous command and restart the daemon service.
We did an upgrade from NX-OS 5.1.5 to 5.2.4 and found all M1 line card interfaces were stuck in initializing state for long time.'show module' status says ok. And we cannot execute shut/no shut command under the interface. N7K-M108X2-12L & N7K-M148GT-11 are the two M series cards. Only option was to downgrade back for the time being.
N7K01# sh int e1/1 | in down Ethernet1/1 is down (initializing)
User is connecting to 5508, running 7.0.116.0. Previously worked on another AP. TV (client) is set to use dhcp. As other posts have mentioned, "DHCP Addr. Assignment" checkbox is not checked for this wlan, but I also switched it to Required for this wlan but it did not make any difference. Seems to be a problem with just this client as many other clients are on this AP with no problems.
Users have to register their MAC to get on our wireless system, but there is no encyption or security enabled once the device has been registered.
With LMS4.0.0 and upgraded to LMS4.0.1 all devices keeps in questioning state, also after some Rediscovers.We've got SNMPv3 and v2 devices, Windows Firewall is off, RME inventory works for most of devices.All DFM processes except of DFMCTMStartup are running, its also not possible to start DFMCTM Startup using pdexec, in DFMLogServer.log you will see a lot of "ogs_server_urn" not found.
What can we do to get the devices also running in DFM?
I have enabled auto mode and manually included but when I run a data collection some devices don't take part in the process. When I click in show included devices I can see 19 devices in Not Managed state.
Trying to find out if a switch learns a mac address of a connected device which only sends broadcasts to the switch port (no unicasts). For example one type of attendance terminal...
Can you set the ASA 5500 series to learn the rule itself? I am talking about putting it into learning mode for first few weeks. I have done this with Zone Alarm software, but not sure this is available in Cisco 5500 series.
I have a 6500 serious switch that one port (portfast enabled) hold a server .This server has sort of a Cluster configured for high availability .
During primary server failure the failover server acquires the cluster IP address (ie virtual IP).
Cluster IP 192.168.10.1
Primary server =192.168.10.2 Failover server =192.168.10.3
when failover happen , i am unable to learn arp. need to reboot the server for arp . After reboot i am getting different mac address(secondary) with cluster IP.
query:-normal clustering how mac address generating(means logicaly any mac address will be created or LAN card mac address)? Is ther any issue with portfast configuration(with out portfast configuration TCN will generate and max age timeout decrease 15 second from 300second) ?
Note : we checked a scenario same ip address with two system(ipconflit) and removed arp learned system from network and same thing happen we need to clear the arp manually in L3switch
I find E1200 cannot update its ARP information by received ARP Request which is sent by the wireless station connected to it, although E1200 has reply an correct ARP response to wireless station, and this will cause VoIP drop off when roaming from E1200 to another wireless AP which is bridge to it , so is there any way to enable the ARP request learning funtion of Linksys series?
I want to configure an access RNIS with a router Cisco 1603.When I plug a cable in interface ISDN BRI with the command "ALL DEBUG EVENTS" start, I have this message : "BRI0 : changing state to F5", and after nothing. How the interface BRI 0 can arrive to State F7?
About 1-5 times per week I will find the jrm process showing as "Administrator has shut down this server". I have written a script that 2/day checks the status of the jrm process and if it is down, restarts it (pdexec jrm). About 25% of the time the jrm process will then show a status of "waiting to initialize". The only way I have found to recover it to shut down CiscoWorks and restart it (takes about 25 minutes). Why it would shutdown or how to get it restarted after the initializing state?
We have a Cisco 886 configured with two WAN's (ATM0 connected to a DSL line and Fa3 connected to a CMTS modem).We're running DMVPN over the Cable network and GetVPN over the DSL line. When the DSL line is down we see a lot of CPU peaks up to 90%.The CPU peaks are caused by the process "DSL state machine". As soon as the DSL line has sync and the ATM0 interface goes UP the CPU peaks disappear. What we'd like to know is if this constant extra CPU load will have an impact on other resources like normal routing & switching or more specific IPSEC handling. Is it for example possible that establishing an IPSEC tunnel will fail because of the CPU peaks?
I would like to request assistance from all the gurus here for an issue i have with a Cisco 7513MX PSU. There probably arent many people who are aware of 7500 chassis as they are quite old.Isse: PSU 1 failed in chassis and we tried to replace it. Once replaced, we are getting the following output for it:
1#sh env all Arbiter type 2, backplane type 7513MX (id 2) Power supply #1 is TBD (id 0), Power supply #2 is 1200W AC (id 1)
We have been researching on the internet for answers but unfortunately due to the age of this model, there is very limited information available. We did find information which suggested to have BOTH PSU 1 & 2 with same revision. Right now the chassis is running only on PS2, we dont want to take down the chassis just to confirm the revision number on the PSU and there is no way to see that on the CLI. What we can do is get another pair of same revision PSUs, insert PSU1 first THEN take out PSU2 and then insert the same revision as PS1 in PSU2 slot but the moment we insert PSU1 in we get that TBD state which is not normal status and raises our doubts about putting the same revision PSUs with the method above, there is a chance that after we insert PSU1 in, the moment we take out PSU2, the chassis might not run on PSU1 due to its abnormal state.
1. net start crmdmgtd did start correctly, so we use resetcasuser.exe and it works some minutes then this issue came back again. I ask the customer to put the casuser in the local administrator group, then customer was able to execute net start crmdmgtd.
2. but some process doesn't start see pdshow.txt.When trying to launch ciscoview, we have this error :Error in communicating with DCRServer. DCR Server may be down. Please start the DCRServer and then refresh the page.At RME home page, I have a error message about jrm, but I don't remerber it.
In the pdshow, we can see that DCRServer is in Waiting to initialize state.We have installed the fix for CSCte49301 bug, but the issue still exist you will find dcrserver.log and dcrclient.log.
i have an Issue with my cisco 2801.in the logs shown me the interface FE0/0 cames up some times but never show the down state, I receive my internet service on this interface but never lost the conection, just this logs information
Oct 7 18:39:32.412: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up Oct 7 18:39:41.448: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up Oct 7 21:57:20.775: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up Oct 8 02:29:31.350: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up Oct 8 02:55:12.362: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up
When opening LMS dashboard some histograms are in an open state .This is happening intermittently on supported versions of firefox and IE. LMS version 4.2.2.
I setup one location (business retail shopping center) in maryland (using swann dvr/cameras- will switch to qsee) with no internet available.I setup another location (business auto shop) in virginia (using qsee dvr/cameras) with internet through verizon fios.I have internet through cox at home in virginia which I can view cameras remotely only to one location in virginia.
I'm having trouble getting my evga 680i to wake on lan from a powered off state. I've done it before but for some reason now it doesn't seem to work. I have formatted since the last time I used wake on lan.
I've got all the settings right in the bios and everything. WOL is enabled in the networking properties on the adapter and in the bios. I can wake from a sleep or hibernate state - just not powered off. Using a WOL test client it confirms it is receiving the magic packet.
When my comp is off I dont see the network port light up with the LEDs. I imagine this has something to do with it -- i just dont know what had to go to power management on the configure tab of my network adapter and uncheck the box "allow windows to power off this device to save power" even though I also had under that checkbox "allow wake on lan" checked.
Currently my home network is being switched via TrendNet TEGs80G unmanaged gig switches. I have been using them for about a year now with no issues. As my home network becomes more advanced, I recently just added a Cisco ASA5505, I am thinking about swapping those unmanaged devices, 4 of them, to managed. I was looking at the Cisco SG300-10 for upstairs, and a 16 port variant for my main core. These devices do not support full Cisco IOS cli, but they are manageable with a rich feature set nonetheless. My question is, should I swap the unmanaged devices with the more expensive Cisco devices, or just keep what works and save the money until I really need to spend it. As previously stated, my home LAN works just fine as it is, however my WiFi, NTV550s, server and workstations are all on the same network. Probably not the most secure but it is what it is without VLAN support.
Running ASA5585’s in active/standby across a local campus MPLS network. Supported design, leading practice etc. Specifically our design is that two ASA5585 are configured as active/standby through a local campus MPLS network over 10gig links through ASR9k etc. The ASA’s are providing inter-vrf routing capability only with p2p l2vpn circuits configured for each logical interface between the ASA over MPLS etc.The failover link is via a direct fibre and the state link will be through a p2p l2vpn (option for direct fibre also)Is this a supported design to begin with?
I am having some issues with a 861W router connected to a cable modem. Traffic is passing fine but my SNMP monitoring tool is showing continual changes to the ifLastChage mib. [code]
We apply a new anyconnect mobile license to our primary asa 5520 and the failover feature went into an off state. WE have now applied a second purchased anyconnect mobile to our secondary asa but the failover is still inactive/off.
bcoh1fw50# sh failover state State Last Failure Reason Date/Time This host - Primary Disabled Ifc Failure 14:43:21 EST Jan 30 2013
I installed a 1941 router with an encrypted GRE tunnel yesterday. The router has ipbasek9 and securiyk9 licensed. Initially the router was running the image c1900-universalk9-mz.SPA.150-1.M5.bin and was working fine. The tunnel was up and passing traffic. I then upgraded the IOS to c1900- universal k9-mz.SPA.151-2.T2.bin and when I reloaded the router the tunnel was stuck in a reset/down state. I tried doing shut/no shut on the interface and reloading the router again, no change. Being under some time pressure to get the device back into production I rolled back to the previous IOS image and the tunnel worked fine again. Is there a known bug that causes this behavior? I have searched cisco.com but have not found one. [code]
I have two Cisco 6500 switches connected via fiber, this is my small network. One end goes to a provider, and the other end goes to a server. My IT department wants some sort of link state propagation since the provider keeps going down, but the IT team is unaware until they contact me.
We provide a Layer2 point-to-point circuit, access ports at the ends. We use V LAN's to transport the traffic. Please let me know if there is anything I could do to support link state propagation.
We have two 3845 routers set up using HSRP at two locations (4 routers total) connecting inside to a pair of ASA 5520 (Active/Passive failover) on each side. These links are used for internet access and they work great under normal operating conditions - they fail over and fail back without issue. How ever, two weeks ago our operations guys started a new data replication procedure going across these links via an IPSec tunnel created between the ASAs. This seems to have created a situation where the IP SLA tracking is not be able to receive the ping back from the upstream router on the originating side. [code]
I have our SIEM set up to notify me whenever the router logs a State change and I got about 10 a day
