Since its release we've seen an uptick in folks deploying 8.1.0 to their firewalls, and that's a great thing. I just want to throw out a word of caution before doing so however; while 8.1.0 is one of the most stable base releases Palo Alto Networks has published, you need to do your homework before deploying this in any environment.
If you have access to any sort of LAB equipment, this is where you should be installing 8.1.0. Start testing your configuration in a LAB environment so that you can have a knowledgeable estimate of when you feel comfortable deploying 8.1 to your production equipment.
If you happen to utilize your LAB equipment in a Change Management process, take note that you are running a different version of PAN-OS when you actually test changes. Something that didn't work in your 8.1.0 LAB may work perfectly fine on 8.0.8 that you have running on your production equipment. On the other hand, something that works out perfectly fine on 8.1.0, may not function on 8.0.8 due to a bug being patched between versions.
If you do not have access to LAB equipment to verify that your production configuration will actually fully function on 8.1.0, I would personally highly advise you to keep 8.1.0 off your production equipment.
Limitations of 8.1.0 are fairly small, however there are 13 pages of known issues within 8.1.0 along with 3 known issues specific to a WF-500 appliance. Before you contend with loading 8.1.0 on production equipment you should take the time to go through all of these known issues and decide if your environment would actually experience them and if you can work around them until they are patched in future maintenance releases. Causing an outage because you want to utilize the awesome SSL Decryption Broker, or the awesome new hit counters, is likely not going to go well.
Generally this boils down to following Palo Alto's recommended upgrade procedure and just doing your own due diligence before upgrading to 8.1. I think there are a few people that are getting wrapped up in the truly amazing feature improvements of 8.1, and throwing best practices out the window. If you don't have LAB equipment to properly test things out, let those of us that do find all of the bugs before causing an outage due to wanting a new software upgrade quickly.
If you truly want 8.1 and just simply can't wait to upgrade, I'd at least make a post here about what your configuration looks like prior to upgrading. We have a lot of people within these forums that have been running 8.1.0 since the beta was released on LAB equipment and home deployments that can likely take a glance at what you are doing and at least give you some real-world experience on what you should expect.
Great Advice of course. Management at my company is chomping at the bit for a more secure Linux deployment of Global Protect. My test device has it working well, removing the need for the X-Auth PSK and implementing a Public Certificate authentication mechanism was key. Unfortunately, that part isn't supported on the pre 8.1 OS as "Linux" isn't a valid OS option on the Portal Config.
PS, use spell check! Some people in management see misspelling and the author's credibility is instantly diminished regardless of the years of experience.
I really wish spellcheck on Live was automatic like most other message boards. I've sent the original post through Word, so hopefully the spelling is at least somewhat correct. Honestly though, I don't think many management personnel are visiting the Live forums.
I've been playing with PAN-OS 8.1 on a PA-200 and a PA-220 of which there is a site-to-site VPN tunnel between them. The upgrade went well overall (from 8.0.8 to 8.1.0) however I have run into two things, one more troubling than the other:
There are the two issues that I have expereince so far. The VPN issue is troubling and I may have to revert to 8.0.8 if i cant figure this one out. If anyone has any ideas, I would gladly listen to them.
After talking to support there were several other cases open against the same SMB issues. Myself and others tried many workarounds, including application override, which did not to resolve the issue. I ended up downgrading to PAN OS 8.0.8 and the issue was resolved.
While I know this is the initial release of a new version, it seems that a bug in something as widely used as SMB would be caught early on in internal and beta testing. Most people using 8.1 as an edge firewall (where SMB is not used) or are not using a VPN would probably have no issues with this release. I still feel like Palo Alto should pull this, it's a pretty big issue in my opinion.
It's a noted issue and those that discuss upgrading to 8.1.0 should be alerted to this issue if the SE is decent. This actually has been kicking around in the Beta forums for a while now, so it was a known issue that for some reason doesn't appear to have been documented in the release documentation.
It's important to note here that Palo Alto Networks isn't recommending people actually upgrade to 8.1.0; that's an important aspect that I think people need to be more mindful of. It is currently not a recommended release.
I 100% agree with what you are saying that customers should engage their SE and be cautious with brand new releases, but on the flip side Palo Alto themselves are equally responsible for media blasting "NEW PAN-OS 8.1... GET IT NOW!" and "LOOK AT THESE NEW FEATURES" in which I there aren't a bunch of caution signs displayed. It's almost like Palo Alto is doing the "LOOK AT US, WE ARE BETTER THEN OUR COMPETITION" but then in small fine print it says "... but really don't install this until 8.1.3". Don't get me wrong, I love our Palo Alto products and woulnd't recommend anything else, but maybe they should adopt an early development title or something.
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 LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!