ciscoworks lms3.2 continuous multicast to 184.108.40.206; is this necessary?
I was curious about what kind (and how much) network traffic LMS3.2 generates on a continuous basis, and found that it continually sends out multicasts to 220.127.116.11. In trying to dig up information regarding that multicast, it appears to have something to do with Microsoft Clustered Servers...... do i have something configured in CM, RME, DFM, IPM or HUM that is causing this? On the surface, it just doesnt seem necessary to me. I monitor only various cisco routers and switches...... I dont want to collect anything about any other type of machine on the network.
Re: ciscoworks lms3.2 continuous multicast to 18.104.22.168; is th
Actually, this traffic is part of the Apache ActiveMQ framework in LMS, and is there for inter-process communication, and not network discovery or device management. There are steps you can do to disable this, but it would be better to open a TAC Service request to do it as it involves modifying an XML file. If the file becomes corrupted, it can cause LMS processes to crash.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.