Communities Are the Lifeblood of Technology

Jun 03, 2015
3 minutes

Communities help us draw upon the collective insight to help build a greater awareness and understanding of just about any topic you can think of, including technology.  According to the social media publication, Socialnomics, 78 percent of consumers trust peer recommendations, whereas only 14 percent trust advertisements. Communities where peer recommendations are easily shared are quite powerful.

At Palo Alto Networks we believe in building real value through collaborative, open, and innovative peer-to-peer exchanges.  To that end, we support a number of ways for our customers to talk to us and each other, and we support building a community that offers significant value to its members.

The Palo Alto Networks Live Community Discussion Forum is a place where you can connect with your peers, ask questions, solve technology issues, exchange ideas, and share best practices, experiences and knowledge. This community is intended as a resource for our customers to engage with each other.

I wanted to offer a simple example of some of the great information you may find when you take part in the community.  Here is a recent post aimed at offering personal experience to benefit the entire community:

My Experience Using the Migration Tool 3.0 for an APP-ID Migration from Panorama Log
Posted Apr 10, 2015

I did an APP-ID migration from Panorama using the Migration Tool 3.0.

Here are the details of my setup:

  1. All policies configured/pushed through Panorama DG, the firewall did not have a local policy.
  2. All log were forwarded to Panorama and Panorama can see the traffic logs.
  3. The firewall is a PA-7050 and Panorama is M-100.

Here are some caveats I learned: 

  • Make sure you are using the latest version of the Migration Tool 3.0.  The older version still had some issues reading logs from Panorama, the latest is best.
  • In the log connector section and for the connected device chose the actual firewall, not Panorama.
  • The log source should be Panaroma.
  • If possible, the machine running Migration Tool 3.0 should have local connectivity to Panorama to reduce the latency.
  • In my previous experiences with the tool I was using VPN to connect Panorama, which caused the tool to get stuck during the APP-ID migration process.
  • Start the log period with small intervals to make sure it works first, then switch to a longer time frame such as 30 days.

Please let me know if you have any questions about my experience using the tool! 


Thanks to Jimmy for sharing his experience with all of us and if you’d like to read similar entries, you can visit our Live Community Blog.

Please let me know in the comments if you have any questions, or contact me via Twitter anytime at @CicconeScott.

Subscribe to the Newsletter!

Sign up to receive must-read articles, Playbooks of the Week, new feature announcements, and more.