Problem Deploying new content version to log collectors

Reply
Highlighted
L0 Member

Problem Deploying new content version to log collectors

Last weekend, I worked with a client to upgrade their Panorama (HA) from 8.1.6 to 9.0.6.  Everything went smoothly.  This weekend the plan was to upgrade the log collectors ( 2 M200s)  When installing 9.0.6 on the log collectors it complained that the log collectors needed to have a more current version of content then they currently had.  Unfortunately when I went to Device Deployment > Dynamic Updates, downloaded the most current version, and clicked install, the log collectors were no available in the list of devices to deploy to.  They do show up in the managed collectors list and they were available when clicking install for software, 9.0.6....  I feel like I'm missing something stupid here....  

 

Thoughts?


Accepted Solutions
Highlighted
Cyber Elite

Re: Problem Deploying new content version to log collectors

@mark.cloutier,

You kind of broke the mold if you let the Panorama appliance get in front of the log collector content version. You always want the Panorama instance to have the same or earlier content update than the log collector, so if your Panorama version is now ahead that could be causing your issue. 

I would simply attempt to update the log collectors manually, and once everything is on a level playing field again ensure that they are working as intended. When you are working with log collectors, when it comes to content releases, you always want to make sure that the log collector is at or ahead of Panorama; you don't want your Panorama being ahead of your log collectors. 

View solution in original post


All Replies
Highlighted
Cyber Elite

Re: Problem Deploying new content version to log collectors

@mark.cloutier,

You kind of broke the mold if you let the Panorama appliance get in front of the log collector content version. You always want the Panorama instance to have the same or earlier content update than the log collector, so if your Panorama version is now ahead that could be causing your issue. 

I would simply attempt to update the log collectors manually, and once everything is on a level playing field again ensure that they are working as intended. When you are working with log collectors, when it comes to content releases, you always want to make sure that the log collector is at or ahead of Panorama; you don't want your Panorama being ahead of your log collectors. 

View solution in original post

Highlighted
L0 Member

Re: Problem Deploying new content version to log collectors

Thank you, this was exactly the problem.  I was new to this client's environment.  To the client's credit, they figured out the solution quickly and fixed it on their own.

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!