When to request a Support Event

This document details what a Support Event is, lists any requirements for creating an event, and discusses when an event should NOT be requested.

 

What is an event?

An event is a scheduled session with a support engineer where all parties will join a bridge at a predetermined time to conduct whatever troubleshooting or maintenance has been agreed upon.

How to request for an event?

Support events are requested by updating the case notes in advance. A minimum of  48-hour advance notice  is required. For emergency situations call support directly (see Support Phone Numbers on the support portal)

When should an event be requested?

• Failed upgrade attempts
• Maintenance windows associated to a support case with an existing technical issue
• Troubleshooting session to resolve an ongoing technical issue

 

When should an event NOT be requested?

• Regular maintenance
• Software upgrades (unless previous attempt was unsuccessful)
• New or initial feature configuration.
• Configuration validation and review.
• Performance tuning.
• New hardware deployment (i.e. cutover or migration).
• Network changes.

NOTE: If an event for one of the above activities is required, please contact your account team for assistance options.
NOTE: Standard Support Customers are not entitled to request "events." 

 

Remote meeting requirements

Palo Alto Networks Support needs some required and optional information to service all requests. Several pieces of information are critical to ensure an effective interaction with support. This required information will assist our engineers in understanding the scope, time, and requirements of the requested event in advance.

 

Any optional information will aid in further improving the effectiveness of a planned event and are greatly encouraged where possible. 

 

Required information

• Start date and time, including local time zone
• Scheduled duration of the window
• Meeting details if hosted by a party other than Palo Alto Networks
• Production or lab environment
• Primary and backup contact person:
  1. Name
  2. Email address
  3. Phone / cell phone number
• Addition stakeholders where relevant
• Description problem to be addressed and intended activities
• Release of PAN-OS, and if applicable, the target release
• Roll back plan and cut-off time in case of event window constraints

 

Optional information

• Network diagrams (logical and physical)
• Contact details of all technical stakeholders (such as routing, switching or datacenter teams where applicable).
• Potential impact to services, if known

 

Weekend activities

Scheduled weekend events are available only for urgent matters where it is not possible to perform the activities outside business hours on weekdays.

All weekend events that are requested will be evaluated and approved on a per-case basis.

Please contact support for any questions about scheduling events.