Site-to-Site VPN VR-to-VR | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
Test Case ID | Test Case Name | Steps to be performed to test | Verification steps | XEN | KVM | VMWARE | VMWARE |
VR-to-VR passive mode | | | | XS 6.2 | RHEL 6.3 | VCenter 5.5 ESX | VCentger 5.1 ESXi 5.1 |
S2S_Monitor_001 | Bring down vpn connection | 1.Bring up CS in advanced zone
2. User creates VPC A and VPC B.
3. User enables VPN gateway on VPC A, and VPC B.
4. User creates VPN customer gateway for VPC A and VPC B.
5. User enables VPN connection on VPC A with customer gateway pointed to VPC B, as "passive". VPN connection would be shown in "Disconnected" state.
6. User enables VPN connection on VPC B with customer gateway pointed to VPC A, thus initiate VPN connection.
7.Bring down vpn connection | 1.After step 6 check vpn connection status in s2s_vpn_connection table in db. It should be in connected state
2.After step 7 connection status should be in Disconnected state and verify an event is generated when the connection goes down. Check the same in UI events page and even in events table in cloud db. | https://issues.apache.org/jira/browse/CLOUDSTACK-5407
https://issues.apache.org/jira/browse/CLOUDSTACK-5424
PASS | https://issues.apache.org/jira/browse/CLOUDSTACK-5407
https://issues.apache.org/jira/browse/CLOUDSTACK-5424
PASS | | https://issues.apache.org/jira/browse/CLOUDSTACK-5407
https://issues.apache.org/jira/browse/CLOUDSTACK-5424
PASS |
S2S_Monitor_002 | Bring up vpn connection | 1.Bring up CS in advanced zone
2. User creates VPC A and VPC B.
3. User enables VPN gateway on VPC A, and VPC B.
4. User creates VPN customer gateway for VPC A and VPC B.
5. User enables VPN connection on VPC A with customer gateway pointed to VPC B, as "passive". VPN connection would be shown in "Disconnected" state.
6. User enables VPN connection on VPC B with customer gateway pointed to VPC A, thus initiate VPN connection.
7.Bring down vpn connection
8.Bring up vpn connection. Both VPN connection would show "Connected" after a while(in 30 seconds by default). | 1.After step 6 check vpn connection status in s2s_vpn_connection table in db. It should be in connected state
2.After step 7 connection status should be in Disconnected state and verify an event is generated when the connection goes down. Check the same in UI events page and even in events table in cloud db.
3.After step 8 vpn connection should be in connected state and an event should be genearted. Verify the same in UI events page and even in events table in db. | PASS | PASS | | PASS |
S2S_Monitor_003 | Reboot vpc VR | 1.Bring up CS in advanced zone
2. User creates VPC A and VPC B.
3. User enables VPN gateway on VPC A, and VPC B.
4. User creates VPN customer gateway for VPC A and VPC B.
5. User enables VPN connection on VPC A with customer gateway pointed to VPC B, as "passive". VPN connection would be shown in "Disconnected" state.
6. User enables VPN connection on VPC B with customer gateway pointed to VPC A, thus initiate VPN connection.
7.Reboot VPC VR | 1.After step 6 check vpn connection status in s2s_vpn_connection table in cloud db. It should be in connected state.
2.After step 7 vpn connection will go down and when the vr comes back connection will be reinitiated. Verify that an event will be generated in both the cases. | PASS | PASS | | PASS |
S2S_Monitor_004 | Restart Network | 1.Bring up CS in advanced zone
2. User creates VPC A and VPC B.
3. User enables VPN gateway on VPC A, and VPC B.
4. User creates VPN customer gateway for VPC A and VPC B.
5. User enables VPN connection on VPC A with customer gateway pointed to VPC B, as "passive". VPN connection would be shown in "Disconnected" state.
6. User enables VPN connection on VPC B with customer gateway pointed to VPC A, thus initiate VPN connection.
7.Restart network | 1.After step 6 check vpn connection status in s2s_vpn_connection table in cloud db. It should be in connected state.
2.After step 7 vpn connection will go down and will be reinitiated when network comes back. Verify that an event will be generated in both the cases. | PASS
| PASS | | PASS |
S2S_Monitor_005 | Restart Network
with clean up | 1.Bring up CS in advanced zone
2. User creates VPC A and VPC B.
3. User enables VPN gateway on VPC A, and VPC B.
4. User creates VPN customer gateway for VPC A and VPC B.
5. User enables VPN connection on VPC A with customer gateway pointed to VPC B, as "passive". VPN connection would be shown in "Disconnected" state.
6. User enables VPN connection on VPC B with customer gateway pointed to VPC A, thus initiate VPN connection.
7.Restart network with clean up option true | 1.After step 6 check vpn connection status in s2s_vpn_connection table in cloud db. It should be in connected state.
2.After step 7 vpn connection will go down and will be reinitiated when network comes back. Verify that an event will be generated in both the cases. | PASS | PASS | | PASS |
S2S_Monitor_006 | Modify router.check.interval | 1.Bring up CS in advanced zone
2. User creates VPC A and VPC B.
3. User enables VPN gateway on VPC A, and VPC B.
4. User creates VPN customer gateway for VPC A and VPC B.
5. User enables VPN connection on VPC A with customer gateway pointed to VPC B, as "passive". VPN connection would be shown in "Disconnected" state.
6. User enables VPN connection on VPC B with customer gateway pointed to VPC A, thus initiate VPN connection.
7.Bringdown vpn connection | 1.After step 6 check vpn connection status in s2s_vpn_connection table in db. It should be in connected state.
2.After step 7 vpn connection will go down and verify that in 5secs event will be generated. | PASS | PASS | | PASS |
S2S_Monitor_007 | Invalid router.check.interval | 1.Bring up CS in advanced zone
2.Set router.check.interval to invalid value say negative numbers/special characters | Setting router.check.interval to a non numeric value should not be allowed | PASS | PASS | | PASS |
S2S_Monitor_008 | Monitoring status with more than one vpn connection | 1.Bring up CS in advanced zone
2. Do step 2 to 6 S2S_Monitor_006 3 times to add 3 customer VPN gateways
3.Create vpn connections from vpn gateway to all customer gateways
4.Bringdown all vpn connections. Both VPN connection would show "Connected" after a while(in 30 seconds by default). | After step 4 make sure that all vpn connections status shows Disconnected in db and events will be generated for each vpn connection | PASS | PASS | | PASS |
S2S_Monitor_009 | Status change in one of the vpn connections | 1.Bring up CS in advanced zone
2. Do step 2 to 6 S2S_Monitor_006 3 times to add 3 customer VPN gateways
3.Create vpn connections from vpn gateway to all customer gateways
4.Bringdown all vpn connections
5.Bring up one of the vpn connections back | 1.After step 4 make sure that all vpn connections status shows Disconnected in db and events will be generated for each vpn connection
2.After step 5 an event should be generated for the connection which comes back to Connected state. No event should be generated for the remaining connections for which there is no state change. | PASS | PASS | | PASS |
S2S_Monitor_010 | Vpn connection in Error state | 1.Bring up CS in advanced zone
2. Do step 2 to 6 S2S_Monitor_006 to add 1 customer VPN gateway
3. Simulate Create vpn connections from vpn gateway to customer gateways failure by providing wrong customer vpn gateway | 1.After step 3 connection should be in Error state.
2.Verify that no events are generated when the connection is in Error state. |
https://issues.apache.org/jira/browse/CLOUDSTACK-5448
PASS
| https://issues.apache.org/jira/browse/CLOUDSTACK-5448
https://issues.apache.org/jira/browse/CLOUDSTACK-5394
PASS | | https://issues.apache.org/jira/browse/CLOUDSTACK-5448
https://issues.apache.org/jira/browse/CLOUDSTACK-5394
PASS |
S2S_Monitor_011 | Vpn connection in Error state | 1.Bring up CS in advanced zone
2. Do step 2 to 6 S2S_Monitor_006 to add 1 customer VPN gateway
3. Simulate Create vpn connections from vpn gateway to customer gateways failure by providing wrong CIDR | 1.After step 3 connection should be in Error state.
2.Verify that no events are generated when the connection is in Error state. |
https://issues.apache.org/jira/browse/CLOUDSTACK-5448
PASS
| https://issues.apache.org/jira/browse/CLOUDSTACK-5448
PASS | | https://issues.apache.org/jira/browse/CLOUDSTACK-5448
https://issues.apache.org/jira/browse/CLOUDSTACK-5394
PASS |
S2S_Monitor_012 | UI: admin setup vpn connections for other accounts | 1.Bring up CS in advanced zone
2. User creates VPC A and VPC B.
3. User enables VPN gateway on VPC A, and VPC B.
4. User creates VPN customer gateway for VPC A and VPC B.
5. User enables VPN connection on VPC A with customer gateway pointed to VPC B, as "passive". VPN connection would be shown in "Disconnected" state.
6. User enables VPN connection on VPC B with customer gateway pointed to VPC A, thus initiate VPN connection.
7.Bring down vpn connection
8.Bring up vpn connection. Both VPN connection would show "Connected" after a while(in 30 seconds by default). | 1.After step 6 check vpn connection status in s2s_vpn_connection table in db. It should be in connected state
2.After step 7 connection status should be in Disconnected state and verify an event is generated when the connection goes down. Check the same in UI events page and even in events table in cloud db.
3.After step 8 vpn connection should be in connected state and an event should be genearted. Verify the same in UI events page and even in events table in db. | PASS | PASS | | PASS |
S2S_Monitor_13 | VPN connection across multiple zones in 1 MS | Repeat test S2S_Monitor_012
with VPCs across multiple zones | 1.After step 6 check vpn connection status in s2s_vpn_connection table in db. It should be in connected state
2.After step 7 connection status should be in Disconnected state and verify an event is generated when the connection goes down. Check the same in UI events page and even in events table in cloud db.
3.After step 8 vpn connection should be in connected state and an event should be genearted. Verify the same in UI events page and even in events table in db. | PASS | PASS | | PASS |
S2S_Monitor_14 | VPN connection across multiple Management Servers | Repeat test S2S_Monitor_012
with VPCs across multiple Management Servers | 1.After step 6 check vpn connection status in s2s_vpn_connection table in db. It should be in connected state
2.After step 7 connection status should be in Disconnected state and verify an event is generated when the connection goes down. Check the same in UI events page and even in events table in cloud db.
3.After step 8 vpn connection should be in connected state and an event should be genearted. Verify the same in UI events page and even in events table in db. | PASS | PASS | | PASS |
S2S_Monitor_15 | upgrade
CP 3.0.7 patch C-4 ->
4.3 | 1. CS 3.0.7 patch C-4: create VPC networks, site-to-site VPN gateways
2. upgrade 4.3
3. create s2s VPN VR2VR connections for existing VPC networks.
4. Create new VPN connections | | PASS | PASS | | |
| | | | | | | |
VR-to-Cisco ISR or Juniper
J-Series Routers | | | | | | | |
S2S_Monitor_021 | Bring down vpn connection | 1.Bring up CS in advanced zone
2.Create vpc and vpn gateway
3.Add customer vpn gateway
4.Create vpn connection from vpn gateway to customer vpn gateway
5.Bringdown vpn connection | 1.After steup 4 check vpn connection status in s2s_vpn_connection table in cloud db. It should be in connected state
2.After step 5 connection status should be in Disconnected state and verify an event is generated when the connection goes down. Check the same in UI events page and even in events table in cloud db. | | | | |
S2S_Monitor_022 | Bring up vpn connection | 1.Bring up CS in advanced zone
2.Create vpc and vpn gateway
3.Add customer vpn gateway
4.Create vpn connection from vpn gateway to customer vpn gateway
5.Bringdown vpn connection
6.Bring up vpn connection | 1.After steup 4 check vpn connection status in s2s_vpn_connection table in cloud db. It should be in connected state
2.After step 5 connection status should be in Disconnected state and verify an event is generated when the connection goes down. Check the same in UI events page and even in events table in cloud db.
3.After step 6 vpn connection should be in connected state and an event should be genearted. Verify the same in UI events page and even in events table in cloud db. | | | | |
S2S_Monitor_023 | Reboot vpc VR | 1.Bring up CS in advanced zone
2.Create vpc and vpn gateway
3.Add customer vpn gateway
4.Create vpn connection from vpn gateway to customer vpn gateway
5.Reboot VPC VR | 1.After step 4 check vpn connection status in s2s_vpn_connection table in cloud db. It should be in connected state.
2.After step 5 vpn connection will go down and when the vr comes back connection will be reinitiated. Verify that an event will be generated in both the cases. | | | | |
S2S_Monitor_024 | Restart Network | 1.Bring up CS in advanced zone
2.Create vpc and vpn gateway
3.Add customer vpn gateway
4.Create vpn connection from vpn gateway to customer vpn gateway
5.Restart network | 1.After step 4 check vpn connection status in s2s_vpn_connection table in cloud db. It should be in connected state.
2.After step 5 vpn connection will go down and will be reinitiated when network comes back. Verify that an event will be generated in both the cases. | | | | |
S2S_Monitor_025 | Restart Network with clean up | 1.Bring up CS in advanced zone
2.Create vpc and vpn gateway
3.Add customer vpn gateway
4.Create vpn connection from vpn gateway to customer vpn gateway
5.Restart network with clean up option true | 1.After step 4 check vpn connection status in s2s_vpn_connection table in cloud db. It should be in connected state.
2.After step 5 vpn connection will go down and will be reinitiated when network comes back. Verify that an event will be generated in both the cases. | | | | |
S2S_Monitor_026 | Modify router.check.interval | 1.Bring up CS in advanced zone
2.Create vpc and vpn gateway
3.Add customer vpn gateway
4.Set router.check.interval to a small value say 5 sec.
4.Create vpn connection from vpn gateway to customer vpn gateway
5.Bringdown vpn connectio | 1.After step 4 check vpn connection status in s2s_vpn_connection table in cloud db. It should be in connected state.
2.After step 5 vpn connection will go down and verify that in 5secs event will be generated. | | | | |
S2S_Monitor_027 | Invalid router.check.interval | 1.Bring up CS in advanced zone
2.Set router.check.interval to invalid value say negative numbers/special characters | Setting router.check.interval to a non numeric value should not be allowed | | | | |
S2S_Monitor_028 | Monitoring status with more than one vpn connection | 1.Bring up CS in advanced zone
2.Create vpc and vpn gateway
3.Add two or more customer vpn gateways
4.Create vpn connections from vpn gateway to all customer gateways
5.Bringdown all vpn connections | After step 5 make sure that all vpn connections status shows Disconnected in db and events will be generated for each vpn connection | | | | |
S2S_Monitor_029 | Status change in one of the vpn connections | 1.Bring up CS in advanced zone
2.Create vpc and vpn gateway
3.Add two or more customer vpn gateways
4.Create vpn connections from vpn gateway to all customer gateways
5.Bringdown all vpn connections
6.Bring up one of the vpn connections back | 1.After step 5 make sure that all vpn connections status shows Disconnected in db and events will be generated for each vpn connection
2.After step 6 an event should be generated for the connection which comes back to Connected state. No event should be generated for the remaining connections for which there is no state change. | | | | |
S2S_Monitor_030 | Vpn connection in Error state | 1.Bring up CS in advanced zone
2.Create vpc and vpn gateway
3.Add customer vpn gateway
4.Simulate vpn connection failure by providing wrong customer vpn gateway details at step 3 | 1.After step4 connection should be in Error state.
2.Verify that no events are generated when the connection is in Error state. | | | | |
| | | | | | | |
