RUNDOWN ACITIVTY FOR JUPITER ER-6

ACTIVITY : MAINTENANCE WINDOWS FOR REDUNDANCY TEST – JUPITER ER-6_HUB SYSTEM

Redundancy Test of Outroute Cluster

Procedure Expected Results P/F Time Result Comments
Duration Downtime
1. Verify that the JWE01SGW1F1W and the JWEORC0117 components Normal All the mentioned components
JWE01TSA11F1W is configured properly (JWE01SGW1F1B) and were showing as green
in Jovian and are displayed in Green in JWEORC0120 components
the Gateway Dashboard. (JWE01SGW1HMW) with the
JWE01TSA11F1B are green “Normal”
on Jovian
2. Verify that the RM’s are configured RM01 online and RM02 standby Normal The status was verified to be
properly and the status of the RM shows JWEORC0117 as according to the test
components are correct Operational and JWEORC0120 as
Available
3. Verify that traffic is flowing over the NOC Pings are successful Normal The pings from the Remote
by sending pings from Remote PC1 to the Pc Server : 192.168.14.100 PC to the FTP server were
FTP Server Pc Remote : 172.17.5.1 successful
Router Ent : 192.168.142.1
4. Click on the Gateway > Resource Verify from RM that the switchover Normal The switchover was
Manager > RM01 > Control Commands completed and JWEORC0120 is successful. And the remote
and Select command “Move ORC”. Set operational. 6 RTO recovered after switching to
Source Cluster Name = JWEORC0117 Pings are successful after switching. the
and Destination Cluster Name = JWEORC0120 cluster.
JWEORC0120. Click on Send to issue
the command
5. Click on the online Resource Manager > Verify from RM that the switchover Normal The switchover was
Control Commands and Select command completed and JWEORC0117 is successful. And the remote
“Move ORC”. Set Source Cluster Name = operational. recovered after switching to
JWEORC0120 and Destination Cluster 6 RTO JWEORC0117
Pings are successful after switching.
Name = JWEORC0117. Click on Send to
issue the command. Status Backup: Available
Status Main: Shutdown
Redundancy Test of Inroute Cluster
Procedure Expected Results P/F Time Result Comments
Duration
1. Verify that the IGMs and IDCs are configured JWEIRC0117 components P Normal All the components are
properly in Jovian and are displayed with the (JWE01IGM01R1 + JWE01IDC01R1) showing status as mentioned
correct status in the Gateway Dashboard. and JWEIRC0120 components in the procedure
(JWE01IGM01HM ) are green
“Normal” on Jovian. JWE01IDC01HM
will show yellow “minor”.
2. Verify that the RM’s are configured properly RM01 online and RM02 available P Normal The status was verified to be
and the status of the components are correct RM shows JWEIRC0117 as according to the test
Operational and JWEIRC0120 as
Available
3. Verify that traffic is flowing over the NOC by Pings are successful P Normal The pings from to the FTP
sending pings from Remote PC1 to the FTP server were successful
Server
4. Click on the online Resource Manager > Verify from RM that the switchover P Normal The switchover was
Control Commands and Select command completed and JWEIRC0120 is successful. And the remote
“Move IRC”. operational. Pings are successful after 12 RTO recovered after switching to
Set Source Cluster Name = JWEIRC0117 and switchover. Upto 20 the
Destination Cluster Name = JWEIRC0120. RTO JWEIRC0120 cluster.
Click on Send to issue the command

5. Click on the online Resource Manager > Verify from RM that the switchover P Normal The switchover was
Control Commands and Select command completed and JWEIRC0117 is successful. And the remote
“Move IRC”. operational. 12 RTO recovered after switching to
Set Source Cluster Name = JWEIRC0120 and Pings are successful after switchover. Upto 20 JWEIRC0117
Destination Cluster Name = JWEIRC0117. RTO
Click on Send to issue the command
Redundancy Test of Timing Generator
Time
Procedure Expected Results P/F Result Comments
Duration
1. Verify both TGU-A and TGU-B are powered TGU-A is Master. P Normal Verified OK for power status
on in Master/Slave mode TGU-B is Slave.
Back up check on TGU card

2. Verify that router on Backhaul Network can Pings are successful P Normal Pings are successful
PING to terminal

3. Physically power down Slave TGU-B Slave TGU-B is powered off. Master P Normal No ping drops observed.
TGU-A continues to serve the
network.

4. Power on the slave TGU-B
5. Physically power down the master TGU-A.
Slave TGU-B is powered on. P Normal No pings drops observed.
Master TGU-A is powered off. Slave P Network recovers within “5”
TGU-B continues to serve the 4 RTO seconds.
network.
Network recovers within 30 seconds
and pings are successful

6. Power on the master TGU-A.
Master TGU-A is powered on. P Normal Network recovers within “0”
Network recovers within 5 minutes seconds
and pings are successful. If it doesn’t
recover proceed to restart ORC and
IRC
Redundancy Test of NMS Vision

Procedure Expected Results P/F Time Result Comments

1. From a PC with access to the Firewall
VPN, navigate in a web
browser,https://jovian.nms.jww.jupiter.net/
GMWebA/GMDashBoard/welcome?gwID=
1&verID=6.0.1.2 and login
Duration
Jovian web GUI is launched and user P Normal User can login to the Jovian
is able to login using the preconfigured
credentials

2. Send pings from Remote PC1 to the FTP Verify the pings are successful P Normal
Server to validate traffic flow 10 RTO

3. Shutdown the primary NM Server NMS01 NMS01 shuts down and NMS02 takes P Normal
over without any loss of traffic. 10 RTO

4. Verify Jovian functionality by rebooting Remote 1 reboots P Remote Normal

Remote 1. status is
rebooting
Redundancy Test of NMS Vision
Procedure Expected Results P/F Time Result Comments
Duration
1. Verify that the IPGWs are configured properly configured and green in Jovian. P green in The status is verified to be correct
in Jovian and are displayed in Green in the Jovian. as per procedure.
Gateway Dashboard.
2. Verify that remote can ping by Router Pings are successful P No RTO Pings are successful

3. Login to the terminal and note down the Terminal is associated to JWESRS-xxxxxxxx P Normal Remote associated to specific IGW
associated IPGW
4. Change parameter on some Terminal for
associate IGW configuration (to other IGW)

5. Login to Jovian to verify that IPGW instances, Verify they are configured for the terminal P Normal The IPGWs are online and active
JWE01IGW11V1A001 and
JWE01IGW11V1A002 are configured in the
IPGW pool for the terminal.

6. Shutdown IGW for traffic to move to IPGW
instances of other IGW (that already makesure
the terminal pool for the terminal)
7. Power on the VM of IGW and verify there is no
interruption to traffic
8. Shutdown IGW (to switch/move back the
traffic to previous IGW instances)
Verify that IGW-VM of JWESRS-xxxxxx is P Normal Traffic move was successful to the
shutdown. respective IPGWs.
Verify that the terminal associates to
IPGW instances of redundant IGW=VM
and pings are successful again
Verify IGW of JWESRS-xxxxxx is normal P Normal No interruption in traffic.
and running properly (online and active),
before switch back to previous IGW (if
needed)
Verify that IGW-VM is shutdown. P Normal Traffic move was successful to the
Verify that the terminal associates to IGW respective IGWs.
instances of JWESRS-xxxxxx and pings are
successful again.