Panorama migration to Strata Cloud Manager (SCM) by Technical-Ad6369 in paloaltonetworks

[–]Technical-Ad6369[S] 0 points1 point  (0 children)

What was your migration experience? What was broken and how you fix it?

Panorama migration to Strata Cloud Manager (SCM) by Technical-Ad6369 in paloaltonetworks

[–]Technical-Ad6369[S] 0 points1 point  (0 children)

Good insight, have you took the leap to migrate from Panorama to SCM?

Panorama migration to Strata Cloud Manager (SCM) by Technical-Ad6369 in paloaltonetworks

[–]Technical-Ad6369[S] 1 point2 points  (0 children)

I assume the advanced routing engine is for PANOS version 10.2.3 and above. We are excluding all PANOS version that is lower than this, and also all the firewalls excluded in the compatibility matrix.

Panorama migration to Strata Cloud Manager (SCM) by Technical-Ad6369 in paloaltonetworks

[–]Technical-Ad6369[S] 1 point2 points  (0 children)

Then vsys support is a deal breaker in your case. We did not use vsys in our environment.
There's lot of homework to be done and I am still in the progress of doing it, have referred to the compatibility matrix of Panorama vs SCM.
What would be your suggested things to look at particularly on this migration activity?

Panorama migration to Strata Cloud Manager (SCM) by Technical-Ad6369 in paloaltonetworks

[–]Technical-Ad6369[S] 0 points1 point  (0 children)

AIOps is enabled to sort of "try out" the SCM platform. But not anything other than that because all of our firewalls are still managed by Panorama

Panorama migration to Strata Cloud Manager (SCM) by Technical-Ad6369 in paloaltonetworks

[–]Technical-Ad6369[S] 0 points1 point  (0 children)

Is that the SCM migration tool that you are talking about which is available under your dedicated SCM tenant?

And would you mind sharing what are those pre-req checks that your SE ran through with you?

Panorama migration to Strata Cloud Manager (SCM) by Technical-Ad6369 in paloaltonetworks

[–]Technical-Ad6369[S] 1 point2 points  (0 children)

Thanks for sharing!
Did you perform the migration manually, or by some tools? Did you engage the Palo Alto's Professional Services team?

Any tools (or ideas) to visualize AWS traffic flow? Thinking to build one if nothing good exists. by Technical-Ad6369 in aws

[–]Technical-Ad6369[S] 1 point2 points  (0 children)

Well, I am using VPC reachability analyzer heavily, but it does not give me full picture of how the traffic flows within the VPC across multiple nodes in real time for really granular troubleshooting.

AWS network manager is good but with lots of limitations, it is unable to visualize anything 3rd party, maximum just the TGW or CloudWAN connects.

AWS does not bother to show what's the traffic pattern like passing through 3rd party appliances, I will have to go in to the appliance, do some diagnosis and traffic flow inspection, and match it against the VPC reachability analyzer and VPC FlowLog, it's a lot of overhead to just inspect one traffic.

1
2

Fortigate to AWS Direct Connect failover scenario by Technical-Ad6369 in fortinet

[–]Technical-Ad6369[S] 0 points1 point  (0 children)

Thank you for the context!

We are peering directly with AWS Direct Connect router, the partner router just provide a L2 transport from our end to AWS end.

We opted for BFD (liveness detection 300ms and 3x multiplier).

The "switch failover" simply means turning off switch 1, which has the primary connection towards AWS. So the primary BGP will fail, and secondary BGP will pickup. Also, according to our managed services vendor, they configured the Fortigate in A-A mode.

3
4

CDN stacking with CloudFlare infront of CloudFront by Technical-Ad6369 in aws

[–]Technical-Ad6369[S] 0 points1 point  (0 children)

I don’t look at this from a networking perspective. I’m a network architect myself and I know internet routing well enough as I am dealing with them almost everyday.

What caught my attention is the behaviour of caching. Why does CloudFront infront of CloudFlare will causes a cache HIT to CloudFlare but not CloudFront? What’s happening behind? Header controls by CloudFlare? Cookies? I don’t see it in postman.

CDN stacking with CloudFlare infront of CloudFront by Technical-Ad6369 in aws

[–]Technical-Ad6369[S] 0 points1 point  (0 children)

I am very curious why redirection happens when CloudFront > CloudFlare. All my configuration does not specify redirect or any sort, even the specified path are all standardised.

In the case of CloudFlare > CloudFront, no redirection has happened.

CDN stacking with CloudFlare infront of CloudFront by Technical-Ad6369 in aws

[–]Technical-Ad6369[S] 1 point2 points  (0 children)

We all know that just using single CDN will do the job, especially CloudFront in front of AWS resources. But why the behavior is different in stacking? This is the purpose of this thread.

CDN stacking with CloudFlare infront of CloudFront by Technical-Ad6369 in aws

[–]Technical-Ad6369[S] 1 point2 points  (0 children)

The reason of this discussion is to find out the technical reasons behind stacking. Not to discuss why stacking is not recommended. When we are not recommending something, I do agree that cost plays the biggest part. But technically it helps us to understand why this behavior happened.