Troubleshooting & resolution
Palo Alto Networks
technical support.
Engineered around you.
When technology gets in the way, you need people who can work through the problem. Our engineers help investigate security platform issues, evaluate configuration changes, and coordinate technical escalations.
What we help with
A defined scope.
A useful outcome.
Get hands-on help with complex issues, configuration changes, and vendor escalations from U.S.-based engineers.
- Technical investigation and root-cause analysis
- Configuration and change-management support
- Vendor escalation coordination
- Documented resolutions and practical follow-up
Where engagements usually start
Engineers on call
when the ticket is not enough.
Technical support is for the problems that outlast a vendor case: the change that has to happen this week, the issue nobody on the team has seen before, the escalation that needs someone who knows the platform and your environment.
Complex troubleshooting
Traffic that should pass and does not, sessions that drop under load, decryption and identity issues, and HA behavior that only appears at the worst time. We work from packet captures and logs, not guesses.
Configuration changes with a safety net
Rule-base changes, upgrades, certificate rollovers, and policy additions performed in a change window with a tested rollback and documented outcome.
Vendor escalations
We open, manage, and push the vendor case, provide the diagnostics the vendor asks for, and translate the answer into a fix in your environment.
Knowledge transfer
Every support engagement ends with a written summary of what was found, what was changed, and what to watch, so the customer team learns the platform as it is supported.
What we get called for
The Palo Alto Networks
problems that stall a team.
Most support requests fall into a handful of patterns. Each one is easier to fix with an engineer who has seen it before and can read the logs that explain it.
GlobalProtect connection issues
Users who cannot connect, connect slowly, or lose access to internal apps, traced through portal, gateway, certificate, and client logs.
Decryption breaking applications
SSL decryption that stops an application from working, resolved with targeted exclusions instead of turning decryption off.
User-ID gaps
Policy that should match a user and does not, caused by missing mappings, agent problems, or identity source changes.
HA and failover behavior
Pairs that fail over unexpectedly, will not fail over when tested, or come back out of sync.
PAN-OS upgrade problems
An upgrade that stalled partway, changed behavior after reboot, or needs a planned path across several releases.
Panorama commit and push failures
Template and device group pushes that fail or produce unexpected results on managed firewalls.
How a request runs
From the first call
to a written resolution.
Intake
What is affected, when it started, and what changed recently. We agree how we will access the environment before anything else.
Diagnose
Logs, packet captures, and configuration review to find the cause, not just the symptom.
Fix safely
Changes made in an agreed window with a rollback ready, or handed to your team as tested steps if you prefer to make them.
Write it up
A short summary of the cause, the fix, and what to watch, so the same issue is faster to recognize next time.
Where the work begins
Start with the
right questions.
The environment and the business context determine the right next step. These questions help shape the engagement.
- What is affected, and what changed recently?
- What troubleshooting and configuration history is available?
- Who owns the affected systems and any vendor escalation?
Our platform specialty
Palo Alto Networks
engineering depth.
Bring the right technical expertise to the platforms already supporting your environment.
Who delivers the work
U.S.-based engineers.
Clear responsibilities.
Your engineering work is handled by a team based entirely in the United States. We define the scope, technical responsibilities, and handoff around the needs of your internal team.
Engagements are architect-designed and engineer-delivered, with a written scope, defined change windows, and documentation your team can operate after handoff.
Get to know RheniumQuestions
Technical support questions.
Do you replace our Palo Alto Networks vendor support?
No. Keep your vendor support contract. We work alongside it: we open and manage cases, gather the diagnostics the vendor asks for, and apply the answer in your environment.
Can you help with an urgent issue if we do not have an agreement?
Yes. Emergency work outside an agreement is scoped and quoted on the first call.
How do your engineers access our environment?
Access is agreed with your team at the start of each engagement, using the method your security policy allows. Please do not send credentials or configuration exports through the contact form.
Will you make changes on our firewalls?
Only when you approve them. Changes are made in an agreed window with a rollback plan, or delivered as tested steps for your team to apply.
How is technical support sold?
As a monthly block of engineering hours with defined response times, or as prepaid hours for teams that cannot yet commit to a term agreement.
Move forward with confidence
Make the next step
a well-defined one.
Understand the environment, agree on the scope, and put the right engineering expertise behind the work.