networkadmin wrote: ksemenov wrote: After an afternoon of playing with 4.0.1 I found enough "bugs" that we decided to go back to 3.1.7 for now. Can you expand a little please? We're on 3.1.7 now and I was debating whether to go to 3.1.8 or just jump to 4.0.1 - can't say that 4.0.1 brings anything to the table that for us is like "We must have that", but equally I don't see too much in the way of solid guidance from Palo Alto of when to use a given version of PAN OS the same as Juniper do. It was a combination of factors, really. We actually really like a lot of 4.0 offers, not the least of which are some of the GUI enhancements (especially in the policy edit view, such as hiding the menu, better support for editing / viewing object, drag'n'drop, etc.) as well as the ability to share more of the configuration aspects from Panorama (e.g. Authentication Profiles) than was previously possible. 4.0 is definitely a move in the right direction. So we upgraded our entire pre-production environment (Panorama + several HA f/w instances) just to see how it looks. Unfortunately, we didn't get a good enough feeling to stay with it. There were a few basic interface bugs (such as reporting the disk space incorrectly - I already posted about this) as well a problem specifying an email recipient for alert notification. Combined with the fact that the original release was pulled almost immediately and re-released, it didn't inspire confidence in the level of QA that PAN put into the 4.0 release. These factors multiplied by the amount of new functionality introduced in 4.0 led us to conclude that it would not be prudent for us to put it into production yet. Perhaps we were unfair or hasty in our assessment, but we can't gamble with the stability of our environment and had to make a decision fairly quickly. We are going to look at 3.1.8 for now and hope that PAN works out the bugs from 4.0 in short order. Hope this helps.
... View more
