-
Notifications
You must be signed in to change notification settings - Fork 1
/
eud-diagnostics_viprion.txt
55 lines (47 loc) · 3.37 KB
/
eud-diagnostics_viprion.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
::::Use find/replace for each of the variables listed below pertaining to your specific scenario::::
$PS_DL = Proximity Services Team Email DL typically DC-PS however, for the Remote/Colo sites be sure to list all email contacts specific to that site
$PS_TEAM = Proximity Services Team
$VIPRION_NAME =
$TMM_PORTS = F5 TMM (traffic) ports from faulty/problematic blade
$TMM_PORTS = F5 TMM (traffic) ports from faulty/problematic appliance
$LB_NAME = Device name of the faulty/problematic appliance
$F5_TAC# = F5 Vendor TAC case#
$F5_TAC#_PASSWORD = F5 Vendor TAC case specific password provided on initial case creation email
$FAULTY_BLADE = Blade # that the EUD will be run on (ie blade2); if Blade 2 is the faulty blade then do not use the variable for $HEALTHY_BLADE2 - apply this to your scenario
$FAULTY_BLADE_SLOT = Slot # the $FAULTY_BLADE lives in (ie slot2); if Blade 2 in slot 2 is the faulty blade then do not use the variable for $HEALTHY_BLADE2_SLOT - apply this to your scenario
$HEALTHY_BLADE1 = Use this for the blade you want to make as primary
$HEALTHY_BLADE1_SLOT = Use this for the slot where blade lives that you want to make as primary
$HEALTHY_BLADE2 =
$HEALTHY_BLADE2_SLOT =
$HEALTHY_BLADE3 =
$HEALTHY_BLADE3_SLOT =
$HEALTHY_BLADE4 =
$HEALTHY_BLADE4_SLOT =
::::General Overview of work between NETWORK-SUPPORT and the Proximity Services Team::::
Note: $PS_TEAM team will make sure the cables are labelled
1.$PS_TEAM will remove blades from slot1 and slot3 from the chassis $VIPRION_HOSTNAME
2.$PS_TEAM will remove traffic links $TMM_PORTS from the $FAULTY_BLADE except management and console
3.NETWORK-SUPPORT will reboot the $FAULTY_BLADE --> select EUD from boot menu, do the EUD test by running all tests
4.NETWORK-SUPPORT will let $PS_TEAM team know once EUD test is done NOTE this can take up to ~30 minutes to complete, $PS_TEAM team will remove the $FAULTY_BLADE from $FAULTY_BLADE_SLOT
5.$PS_TEAM team will insert the blade on slot1 (to make slot1 as primary blade again)
6.NETWORK-SUPPORT will do the checks and let PS team know to insert blade on slot3
7.NETWORK-SUPPORT will make sure all the blades (at least slot 1 and slot3) come back to "available" and the CI is in Standby and In Sync with active unit (no guests on this unit as it is not running VCMP)
8.$PS_TEAM team will re-connect the traffic links per labeling
::::Detailed instructions for NETWORK-SUPPORT on how to run the EUD based on appropriate appliance model::::
VIPRION® B2000 Series Blades
https://techdocs.f5.com/content/kb/en-us/products/big-ip_ltm/releasenotes/related/eud-vf/_jcr_content/pdfAttach/download_0/file.res/eud-vf.pdf
All instructions are detailed on the document above, but in short:
- Ensure the $LB_NAME is the Standby unit, if not perform a failover and force $LB_NAME offline
- Plug a physical console cable
- Disconnect all network cables: $TMM_PORTS
- Power off the $LB_NAME and power it back on
- On the GRUB menu, select End User Diagnostics
- Choose option A - Run all tests
- This will take around 30 minutes
- After, select D - Display test report log
- Please save the displayed results to a file (for example, if using PuTTy, simply save the session as a log)
- Please attach to this service request the results (can send us the file to the Server as indicated below):
Server - supportfiles.f5.com
Username - $F5_TAC#
Password - $F5_TAC#_PASSWORD
::::Example past SNOW changes for reference::::