Scope: All accounts and Account Delivery Leaders that utilize HPE Continuity Services Littleton, MA recovery center for mainframe recovery.
Effective Date: Immediate
Group Name: Disaster Recovery DRC Services, ITSCM services, HPE Continuity Services Delivery (Littleton recovery site)
Affected Locations: Charlotte, Plano, Tulsa
Summary: Each account and client subscribing to mainframe Disaster Recovery services at the HPECS Littleton recovery site that provisions client network into the Littleton site, and utilizes dedicated or shared firewall services, is responsible for managing and upgrading the firewalls as part of normal change control.
Justification: Ability to recover HPE clients in the event of a disaster, mitigate issues encountered in annual exercises
Benefits to Users:
Ability to recover business applications in the event of a disaster within the Recovery Time Objective
Ensure timely recovery of network components and user connectivity
Less confusion and effort at time of disaster or DR exercise
Details:
As communicated in past User Comms, accounts should initiate a project if firewall changes are required. This may include, but not limited to, opening the standard network or firewall request (NetSRM / FRCR or other current network services process) to affect changes to the firewall for a DR exercise or for DR readiness. The network / firewall request should include a request to assign a network / firewall engineer, admin or appropriate staff to accomplish the necessary change.
If the account is not sure if changes are required or not, it is standard practice to have a firewall resource from Managed Firewall Services standing by to assist if needed. If a mainframe account utilizes the HPECS ITSCM service (dedicated ITSCM planner assigned), they should ensure the ITSCM lead is aware of any changes so that the DR plan can be updated and restricted on a need-to-know basis.
If a mainframe account utilizes the DRC Services service (annual exercise management only), the account is responsible to initiate and track firewall changes, as the layer 3 networking into Littleton is an extension of the clients network. These changes are typically sensitive network information and should not be published accept on a need-to-know basis (DRC Services is not responsible for keeping the network DR plan, it is an exercise management service only).
Primary Contact: Mike Berkland Littleton Site Mgr. - michael.t.berkland@hpe.com
Secondary Contact: Tom Bowman DRC Services - tom.bowman@hpe.com
Tertiary Contact: Rich Dillon HPECS Americas Site Mgr. - richard.dillon@hpe.com
|
Usercomm - DR User Comm Account Network Firewall Support