I have LMS 3.0 running on a single server currently. I have s second server and recently received the LMS 3.1 upgrade media. I want to install 3.1 (clean install) on the new server (minus DFM), migrate the 3.0 devices to the 3.1 server and install the new DFM on the original server. Is this "do-able" or would I be better off letting the new 3.1 do it's own discovery, etc.. and start from scratch?
DFM played havoc with the 3.0 install so we uninstalled it - I was told having it on it's own server was the way to go. Any and all comments/suggestions welcomed.
What you want to do is fine. You can install LMS 3.1 on the new server, then follow the LMS 3.1 remote upgrade procedure to restore your 3.0 to your new server. Once you have it working the way you want, you can remove LMS from the old server, and install Common Services 3.2 and DFM 3.1 on it.
Once you have both servers up, you can configure the DFM server to be a DCR and SSO slave to the new LMS server master.
The migration went very well following the steps in the migration guide.
Only 1 issue is outstanding - device discovery shows all of the router loopback interfaces (which I configured discovery to use for management) as unreachable. Not sure why since all devices are reachable and "green" on topology map, etc. and config collection jobs (and others) are successful. I can ping the loopbacks from the LMS server and vice-versa. The seed devices I configured for CDP, GLobal and Routing Table are the loopback addresses (which is how I had them in the previous version. Please advise on how to troubleshoot this one.
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.