I like to save the page as HTML or just export the Device Defaults using BAT->Import/Export. Nice thing with BAT is you can just import right after finishing the firmware install on the publisher.
On Mon, Sep 11, 2017 at 5:32 PM, Lelio Fulgenzi <[email protected]> wrote: > Thanks Dave. All good points. > > > > I just wish that the device defaults page would actually show the WHOLE > firmware information rather than me having to click on the box and press > “end” key to see it. Sometimes, those last two characters are the most > important. > > > > That being said, what I typically do is use an auto-scroll capture tool, > e.g. FastStone Capture, to scroll and capture the page to an image based > PDF. > > Then I go to each box that pertains to my deployment and click the end > key, then capture again. > > > > The things we have to do. L > > > > --- > > Lelio Fulgenzi, B.A. > > Senior Analyst, Network Infrastructure > > Computing and Communications Services (CCS) > > University of Guelph > > > > 519-824-4120 Ext 56354 <(519)%20824-4120> > > [email protected] > > www.uoguelph.ca/ccs > > Room 037, Animal Science and Nutrition Building > > Guelph, Ontario, N1G 2W1 > > > > *From:* Dave Goodwin [mailto:[email protected]] > *Sent:* Monday, September 11, 2017 5:21 PM > *To:* Ryan Huff > *Cc:* Lelio Fulgenzi; voyp list, cisco-voip ([email protected]) > > *Subject:* Re: [cisco-voip] firmware COP files - TFTP server only? or all > nodes? > > > > In some cases the device definitions (e.g. support for new model or new > product specific configuration settings) need to be updated. I believe that > is another reason that *some* devpacks need to be installed on all nodes > rather than just TFTP nodes. > > > > If you are concerned about the Device Defaults being updated when you > install the devpack on the publisher (a good thing to be thinking about), > one thing you could consider doing is as follows. Prior to doing anything, > take a snip of the Device Defaults and then stop Cisco TFTP on the TFTP > nodes (or de-activate under Service Activation, since these installs > sometimes call for a reboot in the docs). Then after your devpack install > is complete, go to Device Defaults and change anything back to the > pre-devpack state if that is your wish. Then you can start up Cisco TFTP > again. After that, you may wish to initiate an all-devices restart by hand > or through BAT. Especially if any of the devpack updates affects your > existing devices. > > > > Just keep in mind, sometimes the product specific configuration updates > that are provided with devpacks actually require new device firmware to be > installed. So you could get into a state where you try to configure > something in UCM with a setting in there, but you can't make the config > take effect if you prevent the phone from actually updating to a firmware > version that recognizes the new setting flag. > > > > -Dave > > > > On Mon, Sep 11, 2017 at 2:57 PM, Ryan Huff <[email protected]> wrote: > > The only reason I add to all nodes for firmware (versus just tftp) is > because and in case, you decide to change how the nodes are used or > function in the cluster at some point; then you don't have to worry about > what is or is not on the node; just activate the service and go :). > > Thanks, > > > > Ryan > > > > On Sep 11, 2017, at 2:37 PM, Lelio Fulgenzi <[email protected]> wrote: > > This was my understanding from the last couple of times. We don’t have any > alternate TFTP servers so they just attempt to grab it from the one server. > > > > I don’t even like adding it to the publisher since it updates the device > defaults page. And we want to do that in a controlled way. > > > > --- > > Lelio Fulgenzi, B.A. > > Senior Analyst, Network Infrastructure > > Computing and Communications Services (CCS) > > University of Guelph > > > > 519-824-4120 Ext 56354 <(519)%20824-4120> > > [email protected] > > www.uoguelph.ca/ccs > > Room 037, Animal Science and Nutrition Building > > Guelph, Ontario, N1G 2W1 > > > > *From:* [email protected] [mailto:[email protected] <[email protected]>] > *On Behalf Of *Brian Meade > *Sent:* Monday, September 11, 2017 2:33 PM > *To:* Lelio Fulgenzi > *Cc:* voyp list, cisco-voip ([email protected]) > *Subject:* Re: [cisco-voip] firmware COP files - TFTP server only? or all > nodes? > > > > That's correct. If you don't install the COP file on the publisher, > you'll need to manually update the Device Defaults as well. Otherwise, you > just need this on servers running the TFTP service. > > > > On Mon, Sep 11, 2017 at 2:24 PM, Lelio Fulgenzi <[email protected]> wrote: > > > Just checking the documentation for COP files for firmware and it says to > install to all nodes. > > I recalled that if the COP file was just for firmware, we only needed to > install it on the TFTP server. > > It's only the devpaks that need to be installed on all nodes since they > may likely make database changes. > > Thoughts? > > --- > Lelio Fulgenzi, B.A. > Senior Analyst, Network Infrastructure > Computing and Communications Services (CCS) > University of Guelph > > 519-824-4120 Ext 56354 > [email protected] > www.uoguelph.ca/ccs > Room 037, Animal Science and Nutrition Building > Guelph, Ontario, N1G 2W1 > > > _______________________________________________ > cisco-voip mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/cisco-voip > > > > _______________________________________________ > cisco-voip mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/cisco-voip > > > _______________________________________________ > cisco-voip mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/cisco-voip > > > > _______________________________________________ > cisco-voip mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/cisco-voip > >
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
