You are on page 1of 6

06-12-2012 -- Disable vlan failsafe on F5 Vipron 3900

Load Balancers
Mouse over the text will show a description of each field. In all the text boxes you can use Wiki Notation, see the Full Notation Guide

Cloud Incubation MOP


Subject of MOP
(http://)

Disable VLAN
failsafe on F5 Vipron
3900 Load
Balancers

Date Scheduled
(http://)

06/12/2012

Risk Assessment
(http://)

Red

Author (http://)

Jerry Yuen

Manager (http://)

Debora Monteforte

Version (http://)

1.0

Status (http://)

Requested

Technical
Authorized by
(http://)

Insert after approval

ATTUID

Insert after approval

Technical
Authorized date

Insert after approval

Management
Authorized by
(http://)

Andrea Stebenne

ATTUID

Insert after approval

Management
Authorized date

Insert after approval

Postmortem
(http://)

N/A

Detailed Objective: (http://)


VLAN Failsafe still needs to be removed. It was never in-scope for ANY CaaS deployment. The developers are going to remove the enablement
of VLAN failsafe in a new code release. VLAN failsafe is causing undesired behavior on the VIPRIONS and could be the cause for problems with
proper failover.

Risk Assessment (http://)


Prerequisites (http://)
Deployment of SO Bridge code that disables VLAN Failsafe during orchestration

Maintenance Impact (http://)


AT&T Impact (http://)

None

AT&T Notification (http://)


None

Customer Impact (http://)


None - this does not require a restart of the hardware

Customer Notification (http://)


None

Maintenance Conflicts (http://)


None

Versions (http://)
1.0

Access Requirements (http://)


Read/Write access via GUI and SSH to the following load balancer devices
Ashburn
n118402f5vprn2001

10.19.8.68

Customer Load Balancer

n118402f5vprn2002

10.19.8.73

Customer Load Balancer

g218406f5vprn2001

10.43.228.68

Customer Load Balancer

g218406f5vprn2002

10.43.228.73

Customer Load Balancer

j118857f5vprn2001

10.13.24.68

Customer Load Balancer

j118857f5vprn2002

10.13.24.73

Customer Load Balancer

Webb Chapel

Redwood City

Repositories (http://)
N/A

Pre-Maintenance Checklists
Precautions (http://)
MOP Preparation

Step

Prior to Maintenance

Yes/No

Has an MR been Opened? http://wmis.web.a


tt.com

S17151AO/RQ00064

Has this passed QA Testing?

yes

Has this passed CTO Lab (Lab-C) Testing?

yes

Any potential conflicts with other


maintenance? Calendar

yes

Step

General Ask Yourself

Yes / No

Do I know why I'm doing this work?

yes

Have I identified and notified everybody


customers and internal groups who will be
directly affected by this work?

yes

Can I prevent or control service interruption?

yes

Is this the right time to do this work?

yes

Am I trained and qualified to do this work?

yes

Are the work orders, MOPs, and supporting


documentation current and error free?

yes

Do I have everything I need to quickly and


safely restore service if something goes
wrong?

yes

Have I walked through the procedure?

yes

Ask Yourself

Emergency / Support Contacts (http://)


Contacts that can be reached out to in case of failure.
Organization

Contact Name

Contact Number

Manager Name

Manager Number

CTO

Jerry Yuen

(732) 420-2338

Deborah Monteforte

(908) 234-6797

Implementation (http://)
Pre-Maintenance Steps (http://)
You can use Wiki Markup in this field
None

Packages to download

None

Alarms to Suppress
None

Implementation (http://)
You can use Wiki Markup in this field
Description of Change Request:

This SMOP is used to validate the MR 64 for creating VLAN with failsafe option disable in the cloud F5 Viprion. We need the following personnel:
1.
2.
3.
4.

Cloud engineer to deploy the new SO code to fix MR64 (CTO TALARI, RAMSATEESH)
Cloud tester to login the cloud and create VDC, vapp with 1 VM, and then 1 LB policy (ICO TIER 1)
The F5 Viprion network engineer will have to validate the failsafe option in F5 load balancer (MHO RESOURCE)
Remove existing VLAN Failsafe option from existing VLANS in all three IDC's (MHO or CTO RESOURCE)

Please note that we only need to validate one site in RWC.

RWC Site ID 18857 for Redwood City vcloud


The first F5 hostname and IP in RWC = j118857f5vprn2001.rwc1.attens.net, 10.13.24.68
The second F5 hostname and IP in RWC = j118857f5vprn2002.rwc1.attens.net, 10.13.24.73
Impact of Change Request:
There will not be any down time for any cloud services.

Parties Involved, Resources/Skills Required for Change Request Execution:


The execution of the SMOP will require participation by the following organizations and individuals:
Ops Tier 2 to Tier4 - change support with F5 administrative experience - MHO
Cloud tester to login the cloud and create VDC, vapp with 1 VM, and then 1 LB policy - ICO TIER 1

Back-Out Preparation Steps:

Create the F5 configuration archive for restore


1.
2.
3.
4.

Login the targeted F5 with you browser via https using the hosting jump server
Create configuration archive by clicking Systems -> Archives, and then click Create
Enter the File Name as $name_of_F5_$todaydate, and then click Finish
Click OK

Please note that you must apply the above instructions to all F5s.
Customer URLs to be Tested Prior to Start of AND After Completion of Change:
N/A.

Detailed Change Execution Steps:


Alarms suppression IS NOT required
To validate the provisioning, we need to execute the following:

1. Cloud engineer will need to deploy the new code into SO code for MR64 (TALARI, RAMSATEESH)

Processes / Ports (http://)


Processes:

TCP Ports Listening / Connected


Processes that are running after start
Ports that are used to connect / serve after start
Testing (http://)
1. ICO TIER 1 - Cloud production tester to need to create a new VDC with Load balancer option, vapp with 1 VM, and then create a new LB
policy in the site RWC (TBD)

1. MHO TIER2/3 - After the above step 6 is completed successfully, the F5 Viprion network engineer will need to validate the VLANs with
failsafe disable. The following is the instructions for the F5 VIprion network engineer:

1. Login the targeted F5 Configuration Utility via https using the browser from the hosting jump server
2. Identify the VLAN based on the cloud production LB policy name created in step 6
Click Local Traffic -> Virtual Servers, the last _$VLAN_ID of the LB policy name created in step 2 is the VLAN
1. Click Network -> VLANs, and then click the targeted VLAN you identified in step 6.
You need to ensure the option for failsafe is not check for the targeted VLAN as follows:

Please note that need to perform the above step 3 in the second F5, which should have the same LB policy and VLAN.
ICO TIER 1 - After the F5 network engineer complete the validation in step 3, the production cloud tester will need to remove LB policy, vapp and
VDC.
ICO Tier 1 must also perform a HEALTH CHECK for Redwood City IDC

Alarms to Un-Suppress
Rollback (http://)
Detailed Back-Out Steps:
Restore F5 from configuration archive
1.
2.
3.
4.
5.

Login the targeted F5 with you browser via https using the hosting jump server
Select Main>Systems>Archives
Click on the name of the configuration you saved in step 1 to be restored.
Click on the Restore button to start restoring the archive. Click OK to return to the "Archives" screen.
Click System->Configuration and then click reboot

Please note that you must apply the above instructions to all F5s.

Post-Mop Activities (http://)


None

Post-Mop Cleanup (http://)

You might also like