07-08-2008 03:44 AM
I have just finished setting up auto-deployment in my CMS system, and I'm waiting for my WXC250's to arrive at the sites.. however, I noticed something that got me a bit worried. My WXC250's are delivered with OS 18.104.22.168, and the CMS system says 5.4+ compatible to be able to auto-deploy. Do I actually have to update the OS before being able to auto-deploy? That would be a major setback since my sites are offshore vessels.
07-08-2008 11:33 AM
You need to define a new deployment group under Management -> Auto Deployment -> Deployment Groups. In the task menu, select 'New (5.2/5.3 Compatible)' and click on 'Go'.
Hope this helps!
07-09-2008 12:44 AM
Hello oyvindha ,
The option bugeater refers to was in CMS 5.5.1. This version of code had the ability to 'downgrade' configs as it supported also 5.2 WXOS deployments. Since CMS5.5.2 this version only goes back as far as WXOS 5.4.x
Technical Marketing Manager - Access and Acceleration Business Unit
07-09-2008 12:53 AM
Thanks for clearing that up DannyJ, that was what I was afraid off.
So my options will be to reinstall an older CMS version, or have them update the OS on-site?
If they connect LOCAL to a switch (w/ dhcp) without configurating anything.. will the web interface be accessible for configuration/OS upgrade? I'm fairly new at this and have allways started with setting up IP's in CLI before setting the box in-path.. so forgive my ignorance.
07-23-2008 02:15 AM
We have trunking installed at one client so we cannot use auto deployment. What we do is to ask the engineer just to add the IP address details then plug the device inline so that we can https to it. Soon as we can browse to the device we upgrade the WXOS and push out our global and partial configs.
Hope this helps