Yea. If they tell you they want a specific firmware protocol and version on the lab. No problem. sh flash. Copy and paste to notepad, Only put in the TFTP commands for the protocol(s) and version(s) they want. There is troubleshooting on the lab. They may "forget" a tftp command, case-sensitivity issue, typo a dash, forget an alias, etc.
Now I'm not sure if it will be quicker to kill all the tftp commands and put them back in or try to stare and compare. ________________________________ From: Nara Shikamaru [[email protected]] Sent: Monday, October 12, 2009 9:55 PM To: Michael Ciarfello Cc: Aamir Panjwani; Vik Malhi; OSL Group Subject: Re: [OSL | CCIE_Voice] How to approach CME basic install I tried it like Vik mentioned, of course it works - but, yes, I'm concerned that they may specify a specific type of firmware download (CME, not CUCM). A two-step would be a pretty rough thing to have to deal with in this context. Maybe I should just work on sorting out the tftp-server syntax in notepad. The long way may end up being the short way if I'm careful. On Mon, Oct 12, 2009 at 5:22 PM, Michael Ciarfello <[email protected]<mailto:[email protected]>> wrote: How are they going to know that? And the CCM version will probably be different than the CCME version so you will be upgrading again. We know all the phones are 7965's. Is there the upgrade issues that were described before? The 65's are new enough that they should be able to have a decent firmware on them and not have the two-step conversion, etc problems? I do a show flash. Copy and paste to notepad and be quick with the highlights and deletes. Shut down the ports, config everything then turn it back up as was stated. What I keep forgetting to do is check the CCM auto registration protocol!! But if the phones upgrade twice, there is plenty of other stuff to do while the phones are doing their things. It might keep me out of the phone configs so I don't have to go back in TOO many times. ________________________________ From: [email protected]<mailto:[email protected]> [[email protected]<mailto:[email protected]>] On Behalf Of Aamir Panjwani [[email protected]<mailto:[email protected]>] Sent: Monday, October 12, 2009 7:02 PM To: Nara Shikamaru; Vik Malhi Cc: OSL Group Subject: Re: [OSL | CCIE_Voice] How to approach CME basic install Yes we can do that UNLESS question specifically says to perform firmware conversion locally on CME From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Nara Shikamaru Sent: Tuesday, 13 October 2009 9:58 AM To: Vik Malhi Cc: OSL Group Subject: Re: [OSL | CCIE_Voice] How to approach CME basic install WHAT?! YOU CAN DO THAT?!?!?!?!?! My brain hurts. On Mon, Oct 12, 2009 at 3:43 PM, Vik Malhi <[email protected]<mailto:[email protected]>> wrote: I think by far and away the quickest and best way is to not do firmware uploads on CME- do it on UCM. That means you set your TFTP to be the PUB and add the device in the UCM db wth the correct protocol. When registered point option 150 back to CME. Do not have any TFTP statements in your CME config. Do not put the “load” command within voice register global/telephony-s since you do not want to change the firmware during the registration back to CME. -- Vik Malhi – CCIE #13890 Senior Technical Instructor - IPexpert, Inc. Telephone: +1.810.326.1444 Fax: +1.810.454.0130 Mailto: [email protected]<http://[email protected]/> Join our free online support and peer group communities: http://www.IPexpert.com/communities<http://www.ipexpert.com/communities> IPexpert - The Global Leader in Self-Study, Classroom-Based, Video-On-Demand and Audio Certification Training Tools for the Cisco CCIE R&S Lab, CCIE Security Lab, CCIE Service Provider Lab , CCIE Voice Lab and CCIE Storage Lab Certifications. From: Nara Shikamaru <[email protected]<http://[email protected]/>> Date: Mon, 12 Oct 2009 14:52:03 -0700 To: OSL Group <[email protected]<http://[email protected]/>> Subject: [OSL | CCIE_Voice] How to approach CME basic install I've gotten into the habit of copying the tftp-server syntax from CME-7-0-full-readme-v.1.0.txt, but this doesn't solve everything since the example syntax doesn't seem to have SIP loads. So, those have to be added manually. I still find the process lengthy and prone to error. If there's a mistake along the way, an SCCP phone could download a SIP load and you'll lose valuable time unscrewing it. Does anyone have a better way of doing this, or is it a matter of practive and getting REALLY good with notepad? -- -Shikamaru -- -Shikamaru ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ -- -Shikamaru
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
