Test Case ID | Test Case Name | Steps to be performed to test | Verification steps | Type | Is Automated | Is Automatable | Priority |
|---|
| Implementing a Guest Network | | | | | | |
F5-SRX- Inline-001 | As regular user , Deploying the first Vm using a network offering that has SRX-F5 in inline mode. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device.
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
Steps:
1. Add a user account.
2. Deploy the first VM using the above created NO. | In F5:
1. Private interface of F5 device will be configured to make it part of the virtual guest network by binding the interface to the VLAN and subnet allocated for the virtual guest network
2. Private interface should be associated with a self-ip from the guest subnet.
In SRX,
1. Private interface of F5 device will be configured to make it part of the virtual guest network by binding the interface to the VLAN and subnet allocated for the virtual guest network
2. Private interface should be associated with a self-ip from the guest subnet. | Functional | N | | |
F5-SRX- Inline-002 | As regular multiple users , Deploying the first Vm using a network offering that has SRX-F5 in inline mode. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
Steps:
1. Add a user account.
2. Deploy the first VM using the above created NO.
3. Add a user account.
4. Deploy the first VM using the above created NO. | For each of the account/network,
In F5:
1. Private interface of F5 device will be configured to make it part of the virtual guest network by binding the interface to the VLAN and subnet allocated for the virtual guest network
2. Private interface should be associated with a self-ip from the guest subnet.
In SRX,
1. Private interface of F5 device will be configured to make it part of the virtual guest network by binding the interface to the VLAN and subnet allocated for the virtual guest network
2. Private interface should be associated with a self-ip from the guest subnet. | Functional | N | | |
| Acquire public Ip addresses and create rules | | | | | | |
F5-SRX- Inline-003 | Lb rule on a public ip address | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create an LB rule for 2 vms in the network. | 1. In SRX , This will result in a Static NAT rule on the firewall to direct all traffic from public ip(which is used for load balancing to the guest ip that gets acquired from the guest pool.
2. In F5 , there should be a load balancing rule programmed using the guest ip as the source ip pointing to the guest Ip of the Vms.
3. Lb rules should work as expected. | Functional | N | | |
F5-SRX- Inline-004 | Lb rules on multiple public ip address | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create an LB rule.
3. Acquire another Ip address.
4. Create an LB rule in this acquire Ipaddress. | For each LB rule created:
1. In SRX , This will result in creating a Static NAT rule to direct all traffic from public ip(which is used for load balancing to the guest ip that gets acquired from the guest pool.
2. In F5 , there should be a load balancing rule programmed using the guest ip as the source ip pointing to the guest Ip of the Vms.
3. Both Lb rules should work as expected. | Functional | N | | |
F5-SRX- Inline-005 | Multiple Lb rules on a public ip address | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create multiple LB rules with different public port on the same Ip address. | For the first LB rule created on any acquired Ip address:
1. In SRX , This will result in creating a Static NAT rule to direct all traffic from public ip(which is used for load balancing) to the guest ip that gets acquired from the guest pool.
2. In F5 , there should be a load balancing rule programmed using the guest ip as the source ip pointing to the guest Ip of the Vms.
For the 2nd LB rule created on any acquired Ip address:
3. There will be no need to program the SRX.
4. In F5 , there should be a load balancing rule programmed using the guest ip( that already is assocaiated with public ipaddress) as the source ip pointing to the guest Ip of the Vms.
5. Both the LB rules should work as expected. | Functional | N | | |
F5-SRX- Inline-006 | PF rule on a public ip address | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create a PF rule for any vm in the network. | 1. PF rules and firewall rules should get programmed in SRX.
2. PF rules should work as expected. | Functional | N | | |
F5-SRX- Inline-007 | PF rules on multiple public ip address | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create a PF rule for vm1.
3. Acquire another Ip address.
4. Create a PF rule for vm2 in this acquire Ipaddress. | 1. Both PF rules and firewall rules should get programmed in SRX.
2. Both PF rules should work as expected. | Functional | N | | |
F5-SRX- Inline-008 | Multiple PF rules on a public ip address | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy the first VM using the above created NO.
Steps:
1. Acquire Ip address.
2. Create multiple PF rules on the same Ip address.
3. Acquire another Ip address.
4. Create multiple PF rules on the same Ip address. | 1. Multiple PF rules on the same public Ip address should work.
2. Also the PF rules from 2 different Ip adresses should work. | Functional | N | | |
F5-SRX- Inline-009 | Create Static NAT rule on a public ip address when there are no firewall rules existing. | PreReq:
1. Create a NO using SRX for Static NAT,Static NAT, Source Nat (Zone wide) and F5 for Static NAT and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create a Static NAT rule for vm1.
3. Create a firewall to allow for port 22. | After Step2:
There is no rule being sent to be programmed in SRX.
After Step 3:
1. Static NAT rule and firewall should gets programmed in SRX.
2. Static NAT rules should work as expected. We should be able to access this vm using port 22. | Functional | N | | |
F5-SRX- Inline-010 | Create Static NAT rule on a public ip address when there are no firewall rules existing.Then add multiple firewall rules. | PreReq:
1. Create a NO using SRX for Static NAT,Static NAT, Source Nat (Zone wide) and F5 for Static NAT and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create a Static NAT rule for vm1.
3. Create a firewall to allow for port 22.
4. Create a firewall to allow for port 80. | After Step2:
There is no rule being sent to be programmed in SRX.
After Step 3:
1. Static NAT rule and firewall should gets programmed in SRX.
2. Static NAT rules should work as expected. We should be able to access this vm using port 22.
After Step 4:
1. Firewall for port 80 should gets programmed in SRX.
2. Static NAT rules should work as expected. We should be able to access this vm using port 22 and port 80. | Functional | N | | |
F5-SRX- Inline-011 | Create Static NAT rule on a public ip address when there are firewall rules existing. | PreReq:
1. Create a NO using SRX for Static NAT,Static NAT, Source Nat (Zone wide) and F5 for Static NAT and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create a firewall to allow for port 22.
3. Create a Static NAT rule for vm1. | After Step2:
There is no rule being sent to be programmed in SRX.
After Step 3:
1. Static NAT rule and firewall should gets programmed in SRX.
2. Static NAT rules should work as expected. We should be able to access this vm using port 22. | Functional | N | | |
F5-SRX- Inline-012 | Create Static NAT rule on a public ip address when there are multiple firewall rules existing. | PreReq:
1. Create a NO using SRX for Static NAT,Static NAT, Source Nat (Zone wide) and F5 for Static NAT and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create a firewall to allow for port 22.
3. Create a firewall to allow for port 80.
4. Create a Static NAT rule for vm1. | After Step2 and 3:
There is no rule being sent to be programmed in SRX.
After Step 4:
1. Static NAT rule and firewall rules should gets programmed in SRX.
2. Static NAT rules should work as expected. We should be able to access this vm using port 22 ad port 80. | Functional | N | | |
F5-SRX- Inline-013 | Static NAT rule on a public ip address - CIDR check on firewall | PreReq:
1. Create a NO using SRX for Static NAT,Static NAT, Source Nat (Zone wide) and F5 for Static NAT and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create a Static NAT rule for vm1.
3. Create a firewall to allow for port 22 on CIDR1. | After Step1:
There is no rule being sent to be programmed in SRX.
After Step 2:
1. Static NAT rule and firewall should gets programmed in SRX.
2. Static NAT rules should work as expected.
We should be able to access this vm using port 22 from CIDR1 only.
We should NOT be able to access this vm using port 22 from any machine that does notbelong to CIDR1.
SorceNat for this VM should be set to this acquired public Ip address. | Functional | N | | |
F5-SRX- Inline-014 | Static NAT rules on multiple public ip address | PreReq:
1. Create a NO using SRX for Static NAT,Static NAT, Source Nat (Zone wide) and F5 for Static NAT and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create a Static NAT rule for vm1 and create a firewall rule to allow for port 22.
3. Acquire another Ip address.
2. Create a Static NAT rule for vm2 and create a firewall rule to allow for port 22. | 1. Both Static NAT and firewall rules should gets programmed in SRX.
2. Both Static NAT rules should work as expected. | Functional | N | | |
F5-SRX- Inline-015 | Lb rules for 2 different networks | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device.
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Add another user account.
7. Deploy few VMs using the above created NO.
Steps:
As each of these users,
1. Acquire public IpAddress and create Lb rules. | Lb rules created by each of the users should work as expected. | Functional | N | | |
F5-SRX- Inline-016 | Static NAT rules for 2 different networks | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for Static NAT and rest of the services are provided by VR.
2. Add SRX device.
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Add another user account.
7. Deploy few VMs using the above created NO.
Steps:
As each of these users,
1. Acquire public IpAddress and create Static NAT rules. | Static NAT rules created by each of the users should work as expected. | Functional | N | | |
F5-SRX- Inline-017 | PF rules for 2 different networks | PreReq:
1. Create a NO using SRX for PF,PF, Source Nat (Zone wide) and F5 for PF and rest of the services are provided by VR.
2. Add SRX device.
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Add another user account.
7. Deploy few VMs using the above created NO.
Steps:
As each of these users,
1. Acquire public IpAddress and create PF rules. | PF rules created by each of the users should work as expected. | Functional | N | | |
F5-SRX- Inline-018 | Create PF rule on an ipaddress that has an LB rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy the few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create an LB rule.
3. On the same acquired Ip address , create a PF rule. | ????--> Will this be allowed | Functional | N | | |
F5-SRX- Inline-019 | Create LB rule on an ipaddress that has a PF rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy the first VM using the above created NO.
Steps:
1. Acquire Ip address.
2. Create an PF rule.
3. On the same acquired Ip address , create an LB rule. | ????--> Will this be allowed | Functional | N | | |
F5-SRX- Inline-020 | Create Static NAT rule on an ipaddress that has a LB rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create an LB rule.
3. On the same acquire Ip address , try to create a Static NAT rule. | This shoud not be allowed. | Functional | N | | |
F5-SRX- Inline-021 | Create Static NAT rule on an ipaddress that has a PF rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create an PF rule.
3. On the same acquire Ip address , try to create a Static NAT rule. | This shoud not be allowed. | Functional | N | | |
F5-SRX- Inline-022 | Create a Static NAT rule for a Vm which already has a PF rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address - p1.
2. Create a PF rule for vm1 for port 22.
3. Acquire Ip address - p2.
4. Create a Static NAT rule for vm1. | Using p2 , We will be able to use port 22 to reach vm1 even without having to open the fire wall explicitly ??
On P1 , we should be able to use port 22 to reach vm1.
Once vm1 is reached make sure that the source NAT for this vm1 is P2. (Try to ssh to any other machine , and using tcpdump find the source with which the tcp packets come in). | Functional | N | | |
F5-SRX- Inline-023 | Create a Static NAT rule for a Vm which is already part of LB rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address - p1.
2. Create a LB rule for vm1 and vm2 for port 80.
3. Acquire Ip address - p2.
4. Create a Static NAT rule for vm1.
5. Create a firewall rule to open port 80 for this Static NAT rule. | After Step4 :
Using p2 (Static NAT rule), We will NOT be able to use port 80 to reach vm1.
After Step5 :
Using p2 (Static NAT rule), We will be able to use port 80 to reach vm1.
Using P1 (LB rule), access VM1. Make sure that source NAT for VM1 is set to p1.
Using P1 (LB rule), access VM2. Make sure that source NAT for VM1 is set to public ip address of the SRX device. | Functional | N | | |
| Releasing Ip address | | | | | | |
F5-SRX- Inline-024 | Release Ip address that has 1 Lb rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create an LB rule.
3. Release Ip address | After Step 2 ,
1. Make sure LB rule works.
After Step 3,
1. Make sure LB rule does not work.
2. In SRX, Static NAT rule created for this public Ip address to the guestIp needs to be removed.
3. Firewall rules that were auto generated as part of the LB rule needs to be removed.
4. This guestIp needs to be released back to the avaiable guest ip pool.
5. In F5 , the load balancing rule relating to this LB rule should get removed. | Functional | N | | |
F5-SRX- Inline-025 | Release Ip address that has multiple Lb rules. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create multiple LB rules.
3. Release Ip address | After Step 2 ,
1. Make sure LB rule works.
After Step 3,
1. Make sure LB rule does not work.
2. In SRX, Static NAT rule created for this public Ip address to the guestIp should be removed.
3. All Firewall rules that were auto generated as part of the LB rule needs to be removed.
4. This guestIp needs to be released back to the avaiable guest ip pool.
5. In F5 , all the load balancing rule pointing to this public Ip address should be removed. | Functional | N | | |
F5-SRX- Inline-026 | Release Ip address that has 1 PF rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create an PF rule.
3. Release Ip address | After Step 2 ,
1. Make sure PF rule works.
After Step 3,
1. Make sure PF rule does not work.
2. In SRX, PF rule created for this public Ip address should be removed. Firewall rules created as part of this PF rule shouls also be removed. | Functional | N | | |
F5-SRX- Inline-027 | Release Ip address that has multiple PF rules. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create multiple PF rules.
3. Release Ip address | After Step 2 ,
1. Make sure all PF rule works.
After Step 3,
1. Make sure all the PF rules does not work.
2. In SRX, all PF rule created for this public Ip address should be removed. Firewall rules created as part of this PF rule shouls also be removed. | Functional | N | | |
F5-SRX- Inline-028 | Release Ip address that has 1 Static NAT rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create an Static NAT rule.Create a firewall rule to open port 22.
3. Release Ip address | After Step 2 ,
1. Make sure Static NAT rule works for port 22 on the acquired Ip.
After Step 3,
1. Make sure Static NAT rule does not work.
2. In SRX, Static NAT rule created for this public Ip address should be removed.
3. In SRX ,Firewall rules created on this acuired Ip address shouls also be removed. | Functional | N | | |
F5-SRX- Inline-029 | Release Ip address that has pf and Lb rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create an LB rule.
3. On the same acquired Ip address , create a PF rule.
4. Release Ip address | Is this going to be supported? | Functional | N | | |
F5SRX- Inline-030 | Create a Static NAT rule for a Vm which already has a PF rule.
Release Ip address on which Static NAT rule is present. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Acquire Ip address - p1.
7. Create a PF rule for vm1 for port 22.
8. Acquire Ip address - p2.
9. Create a Static NAT rule for vm1.
Steps:
1. Release p2. | Is this going to be supported? | Functional | N | | |
F5-SRX- Inline-031 | Create a Static NAT rule for a Vm which already has a PF rule.
Release Ip address on which PF rule exists. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Acquire Ip address - p1.
7. Create a PF rule for vm1 for port 22.
8. Acquire Ip address - p2.
9. Create a Static NAT rule for vm1.
Steps:
1. Release p1. | Is this going to be supported? | Functional | N | | |
F5-SRX- Inline-032 | Create a Static NAT rule for a Vm which is already part of LB rule.
Release Ip address on which LB rule exists. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Acquire Ip address - p1.
7. Create a LB rule for vm1 and vm2 for port 80.
8. Acquire Ip address - p2.
9. Create a Static NAT rule for vm1.
10. Create a firewall rule to open port 80 for this Static NAT rule.
Steps:
1.Release p2 | Is this going to be supported? | Functional | N | | |
F5-SRX- Inline-033 | Create a Static NAT rule for a Vm which is already part of LB rule.
Release Ip address on which Static NAT rule exists. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Acquire Ip address - p1.
7. Create a LB rule for vm1 and vm2 for port 80.
8. Acquire Ip address - p2.
9. Create a Static NAT rule for vm1.
10. Create a firewall rule to open port 80 for this Static NAT rule.
Steps:
1.Release P2 | Is this going to be supported? | Functional | N | | |
| Deleting existing rule | | | | | | |
F5-SRX- Inline-034 | Delete the only LB rule in a public ip address. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create an LB rule.
3. Delete this LB rule. | After Step 2 ,
1. Make sure LB rule works.
After Step 3,
1. Make sure LB rule does not work.
2. In SRX, Static NAT rule created for this public Ip address to the guestIp needs to be removed.
3. This guesIp needs to be released back to the avaiable guest ip pool.
4. In F5 , the load balancing rule relating to this LB rule should get removed. | Functional | N | | |
F5-SRX- Inline-035 | Delete multiple LB rules in a public ip address. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create 2 LB rules.
3. Delete 1 LB rule.
4. Delete another LB rule. | After Step 2 ,
1. Make sure both the LB rule works.
After Step 3,
1. Make sure 1 LB rule that was deleted does not work and the other LB rule contibues to work.
2. In F5 , all the load balancing rule pointing to this public Ip address should be removed.
After Step 4,
1. Make sure both the LB rules work.
2. In SRX, Static NAT rule created for this public Ip address to the guestIp should be removed.
3. This guestIp needs to be released back to the avaiable guest ip pool.
4. In F5 , all the load balancing rule pointing to this public Ip address should be removed. | Functional | N | | |
F5-SRX- Inline-036 | Delete the only PF rule in a public ip address. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create an PF rule.
3. Delete the PF rule. | After Step 2 ,
1. Make sure PF rule works.
After Step 3,
1. Make sure PF rule does not work.
2. In SRX, PF rule created for this public Ip address should be removed. | Functional | N | | |
F5-SRX- Inline-037 | Delete multiple PF rules in a public ip address. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create multiple PF rules.
3. Delete all the PF rules one by one. | After Step 2 ,
1. Make sure all PF rule works.
2. When one of the PF rule is deleted , make sure that other PF rules continue to work.
After Step 3,
3. Make sure all the PF rules do not work.
4. In SRX, all PF rule created for this public Ip address should be removed. | Functional | N | | |
F5-SRX- Inline-038 | Disable the Static NAT rule in a public ip address. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create an Static NAT rule.Create Firewall rule for port 22.
3. Disable Static Nat rule.
4. Enable Static Nat rule. | After Step 2 ,
1. Make sure Static NAT rule works.
After Step 3,
1. Make sure Static NAT rule does not work.
2. In SRX, Static NAT rule created for this public Ip address should be removed.
do we expect the Firewall rules associated with this static NAT rule to be deleted from the SRX , but to be present in our DB ?
After Step 4,
1. Static NAT and Firewall gets programmed on the SRX.
2. Static NAT rule should now work for port22. | Functional | N | | |
F5-SRX- Inline-039 | Delete firewall that is opened up for a Static NAT rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create an Static NAT rule.Create Firewall rule for port 22.
3. Delete firewall rule.
4. Add firewall ule for port 22. | After Step 2 ,
1. Make sure Static NAT rule works.
After Step 3,
1. Make sure Static NAT rule does not work.
2. In SRX,
Do we expect the Static NAT rule and firewall rule created for this public Ip address to be removed as well ? But the STATIC NAT will continue to remain in the DB?
After Step 4,
1. Static NAT and Firewall gets programmed on the SRX.
2. Static NAT rule should now work for port22. | Functional | N | | |
F5-SRX- Inline-040 | Delete one of the firewalls that is opened up for a Static NAT rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create an Static NAT rule.
3. Create Firewall rules for port 22.
4. Create Firewall rule for port 80.
5. Delete firewall rule for port 22.
6. Delete firewall rule for port 80.
7. Add firewall rule for port 22. | After Step 4 ,
1. Make sure Static NAT rule works for port 22 and port 80.
After Step 5,
1. Make sure Static NAT rule does not work for port22. But continues to work for port 80.
After Step 6,
1. Make sure Static NAT rule does not work for port22 and port 80.
2. In SRX,
Do we expect the Static NAT rule and firewall rule created for this public Ip address to be removed as well ? But the STATIC NAT will continue to remain in the DB?
After Step 7,
1. Make sure Static NAT rule works for port22.
2. In SRX,
Static NAT rule and firewall rules should be programmed. | Functional | N | | |
F5-SRX- Inline-041 | Delete PF rule from an ipaddress that has PF and LB rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create an LB rule.
3. On the same acquired Ip address , create a PF rule.
4. Release Ip address | Is this going to be supported? | Functional | N | | |
F5-SRX- Inline-042 | Delete LB rule from an ipaddress that has PF and LB rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1. Acquire Ip address.
2. Create an LB rule.
3. On the same acquired Ip address , create a PF rule.
4. Release Ip address | Is this going to be supported? | Functional | N | | |
F5-SRX- Inline-043 | Create a Static NAT rule for a Vm which already has a PF rule.
Disable the Static NAT rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Acquire Ip address - p1.
7. Create a PF rule for vm1 for port 22.
8. Acquire Ip address - p2.
9. Create a Static NAT rule for vm1.
Steps:
1. Disable the Static NAT rule. | What would be the expected behaviour? | Functional | N | | |
F5-SRX- Inline-044 | Create a Static NAT rule for a Vm which already has a PF rule.
Delete PF rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Acquire Ip address - p1.
7. Create a PF rule for vm1 for port 22.
8. Acquire Ip address - p2.
9. Create a Static NAT rule for vm1.
Steps:
1. Delete PF rule. | What would be the expected behaviour? | Functional | N | | |
F5-SRX- Inline-045 | Create a Static NAT rule for a Vm which is already part of LB rule.
Delete LB rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Acquire Ip address - p1.
7. Create a LB rule for vm1 and vm2 for port 80.
8. Acquire Ip address - p2.
9. Create a Static NAT rule for vm1.
10. Create a firewall rule to open port 80 for this Static NAT rule.
Steps:
1. Delete LB rule. | What would be the expected behaviour? | Functional | N | | |
F5-SRX- Inline-046 | Create a Static NAT rule for a Vm which is already part of LB rule.
Disable the Static NAT rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Acquire Ip address - p1.
7. Create a LB rule for vm1 and vm2 for port 80.
8. Acquire Ip address - p2.
9. Create a Static NAT rule for vm1.
10. Create a firewall rule to open port 80 for this Static NAT rule.
Steps:
1. Disable the Static NAT rule. | What would be the expected behaviour? | Functional | N | | |
| Shutting down of Guest Network | | | | | | |
F5-SRX- Inline-047 | Delete an account that has LB,Static NAT and PF rules. | Pre-Req:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Acquire Ip address.
7. Create a PF rules on this ipaddress.
8. Acquire another Ip address.
9. Create a Static NAT on this ipaddress.
10. Acquire another Ip address.
11. Create a LB rule on this ipaddress.
12. Make sure PF, Static NAT and Lb rules work as expected.
Steps:
Delete this account. | This will result in the network being shutdown.
As part of network shutdown :
1. All the Lb rules for this account should get removed from the F5.
2. All PF and Static NAT rules for this account should get removed from SRX. | Functional | N | | |
F5-SRX- Inline-048 | Delete network. | Pre-Req:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Acquire Ip address.
7. Create a PF rules on this ipaddress.
8. Acquire another Ip address.
9. Create a Static NAT on this ipaddress.
10. Acquire another Ip address.
11. Create a LB rule on this ipaddress.
12. Make sure PF, Static NAT and Lb rules work as expected.
Steps:
Delete network. | This will result in the network being shutdown.
As part of network shutdown :
1. All the Lb rules for this account should get removed from the F5.
2. All PF and Static NAT rules for this account should get removed from SRX. |
Functional | N | | |
F5-SRX- Inline-049 | Stop all the Vms in a network. | Pre-Req:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Acquire Ip address.
7. Create a PF rules on this ipaddress.
8. Acquire another Ip address.
9. Create a Static NAT on this ipaddress.
10. Acquire another Ip address.
11. Create a LB rule on this ipaddress.
12. Make sure PF, Static NAT and Lb rules work as expected.
Steps:
1. Stop all the Vms in the network and wait for network to get shutdown by network scavenger thread. | This will result in the network being shutdown.
As part of network shutdown :
1. All the Lb rules for this account should get removed from the F5.
2. All PF and Static NAT rules for this account should get removed from SRX. |
Functional | N | | |
F5-SRX- Inline-050 | Stop all the Vms in a network.After network gets shutdown by network scavenger thread , start one of the user Vms. | Pre-Req:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Acquire Ip address.
7. Create a PF rules on this ipaddress.
8. Acquire another Ip address.
9. Create a Static NAT on this ipaddress.
10. Acquire another Ip address.
11. Create a LB rule on this ipaddress.
12. Make sure PF, Static NAT and Lb rules work as expected.
Steps:
1. Stop all the Vms in the network and wait for network to get shutdown by network scavenger thread.
2. Start one of the Vms. | As part of network shutdown :
1. All the Lb rules for this account should get removed from the F5.
2. All PF and Static NAT rules for this account should get removed from SRX.
When Vm is started , network is started again:
1. All the Lb rules for this account should get programmed in F5.
2. All PF and Static NAT rules for this account should get programmed in SRX.
All the existing LB,Static NAT and PF rules should continue to work. | Functional | N | | |
F5-SRX- Inline-051 | Restart network -> with cleanup option enabled | Pre-Req:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Acquire Ip address.
7. Create a PF rules on this ipaddress.
8. Acquire another Ip address.
9. Create a Static NAT on this ipaddress.
10. Acquire another Ip address.
11. Create a LB rule on this ipaddress.
12. Make sure PF, Static NAT and Lb rules work as expected.
Steps:
Restart network -> with cleanup option. | As part of network shutdown :
1. All the Lb rules for this account should get removed from the F5.
2. All PF and Static NAT rules for this account should get removed from SRX.
When network is started again:
1. All the Lb rules for this account should get programmed in F5.
2. All PF and Static NAT rules for this account should get programmed in SRX.
All the existing LB,Static NAT and PF rules should continue to work. | Functional | N | | |
F5-SRX- Inline-052 | Restart network -> without cleanup option enabled | Pre-Req:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Acquire Ip address.
7. Create a PF rules on this ipaddress.
8. Acquire another Ip address.
9. Create a Static NAT on this ipaddress.
10. Acquire another Ip address.
11. Create a LB rule on this ipaddress.
12. Make sure PF, Static NAT and Lb rules work as expected.
Steps:
Restart network without cleanup option. | All existing Lb rules get added again to the F5.
All existing Static NAT and LB rules should get added again to SRX. | Functional | N | | |
| F5 Down/Unreachable | | | | | | |
F5-SRX- Inline-053 | Have the F5 temporarily unreachable. Add an new LB rule. | 1. Have the F5 temporarily unreachable.
2. Add an new LB rule. | When the F5 is brought back up again, these LB rules should get configured. | Functional | N | | |
F5-SRX- Inline-054 | Have the F5 temporarily unreachable. Edit existing LB rules by adding/deleting Vms to this rule. | 1. Have the F5 temporarily unreachable.
2. Edit existing LB rules by adding/deleting Vms to this rule. | When the F5 is brought back up again, these LB rules should get configured. | Functional | N | | |
F5-SRX- Inline-055 | Have the F5 temporarily unreachable. Delete existing LB rule. | 1. Have the F5 temporarily unreachable.
2. Delete existing LB rule. | When the F5 is brought back up again, these LB rules should get configured. | Functional | N | | |
F5-SRX- Inline-056 | Deploy a VM in a existing network. | 1. Have the F5 temporarily unreachable.
2. Deploy a VM in an existing network. | Deploying a VM should fail ?? | Functional | N | | |
F5-SRX- Inline-057 | Deploy a VM in a new network. | 1. Have the F5 temporarily unreachable.
2. Deploy a VM in an new network. | Deploying a VM should fail ?? | Functional | N | | |
| SRX Down/Unreachable | | | | | | |
F5-SRX- Inline-058 | Have the SRX temporarily unreachable. Add an new LB rule and firewall rule. | 1. Have the SRX temporarily unreachable.
2. Add an new LB rule and firewall rule. | When the SRX is brought back up again, these LB rules and firewall rule should get configured. | Functional | N | | |
F5-SRX- Inline-059 | Have the SRX temporarily unreachable. Edit existing LB rules by adding/deleting Vms to this rule. | 1. Have the SRX temporarily unreachable.
2. Edit existing LB rules by adding/deleting Vms to this rule. | When the SRX is brought back up again, these LB rules should get configured. | Functional | N | | |
F5-SRX- Inline-060 | Have the SRX temporarily unreachable. Delete existing LB rule and firewall rule. | 1. Have the SRX temporarily unreachable.
2. Delete existing LB rule and firewall rule. | When the SRX is brought back up again, these LB rules and firewall rule should get configured. | Functional | N | | |
F5-SRX- Inline-061 | Have the SRX temporarily unreachable. Add an new PF rule and firewall rule. | 1. Have the SRX temporarily unreachable.
2. Add an new PF rule and firewall rule. | When the SRX is brought back up again, these PF rules and firewall rule should get configured. | Functional | N | | |
F5-SRX- Inline-062 | Have the SRX temporarily unreachable. Delete existing PF rule and firewall rule. | 1. Have the SRX temporarily unreachable.
2. Delete existing PF rule and firewall rule. | When the SRX is brought back up again, these PF rules and firewall rul should get configured. | Functional | N | | |
F5-SRX- Inline-063 | Have the SRX temporarily unreachable. Add an new Static NAT rule and firewall rule. | 1. Have the SRX temporarily unreachable.
2. Add an new Static NAT rule and firewall rule. | When the SRX is brought back up again, these Static NAT rules and firewall rule should get configured. | Functional | N | | |
F5-SRX- Inline-064 | Have the SRX temporarily unreachable. Delete existing Static NAT rule and firewall rule. | 1. Have the SRX temporarily unreachable.
2. Delete existing Static NAT rule and firewall rule. | When the SRX is brought back up again, these Static NAT rules and firewall rule should get configured. | Functional | N | | |
F5-SRX- Inline-065 | Deploy a VM in a existing network. | 1. Have the SRX temporarily unreachable.
2. Deploy a VM in an existing network. | Deploying a VM should fail ?? | Functional | N | | |
F5-SRX- Inline-066 | Deploy a VM in a new network. | 1. Have the SRX temporarily unreachable.
2. Deploy a VM in an new network. | Deploying a VM should fail ?? | Functional | N | | |
| | | | | | | |
F5-SRX- Inline-067 | Create multiple LB rules from the same public Ip acquired using same public port. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1.Acquire IP address - p1
2.Create a LB rule for vm1 and vm2 for port 80.
3.Try to create another LB rule for the same port 80 | We should not be allowed to create LB rule on a port that is already been assigned to another LB rule. | Functional | N | | |
F5-SRX- Inline-068 | Create multiple LB rules from the same public Ip acquired using different public port but same private port. Have same set of Vms assigned to both the LB rules. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps: - Acquire IP address - p1
- Create a LB rule for vm1 and vm2 for public port 22 and private port 2022
- Create another LB rule on p1 for vm1 and vm2 for public port 80 and private port 2022
| - Should be allowed to create multiple LB rules on the same public IP with different public ports but same private port. 2. Requests to all these LB rules should be serviced correctly.
| Functional | N | | |
F5-SRX- Inline-069 | Edit the name of the existing LB rule | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
Steps:
1.Acquire IP address -p1 and create multiple LB rules on it
2.Modify one of the LB rule name | When all the existing Lbrules are listed , we should see the edited name. | Functional | N | | |
F5-SRX- Inline-070 | Edit the public port/private port of the existing LB rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1.Acquire IP address -p1 and create LB rule for vm1 and vm2 for public port 22 and private port 22
2.Try to modify the public/private port for this rule | This should not be allowed | Functional | N | | |
F5-SRX- Inline-071 | Delete an existing LB rule and create exactly the same LB rule with only public Ip being different. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1.Acquire IP address -p1 and create LB rule for vm1 and vm2 for public port 22 and private port 22
2.Delete the LB rule created above.
3.Create LB rule with vm1 and vm2 for public port 23 and private port 22 | Requests to all the LB rules should be serviced correctly. | Functional | N | | |
F5-SRX- Inline-072 | Delete an existing LB rule and create exactly the same LB rule with only private Ip being different. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1.Acquire IP address -p1 and create LB rule for vm1 and vm2 for public port 23 and private port 22
2.Delete the LB rule created above.3.Create LB rule with vm1 and vm2 for public port 23 and private port 80 | Requests to all the LB rules should be serviced correctly. | Functional | N | | |
F5-SRX- Inline-073 | Add a new VM to an existing LB rule with round Robin | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1.Acquire IP address -p1 and create LB rule for vm1 and vm2 for public port 22 and private port 22
2. Deploy guest VM using NO created at PreReq step1 and add it to the existing LB rule | We should see the traffic being directed to the newly added Vm according to the "Round Robin" algorithm. | Functional | N | | |
F5-SRX- Inline-074 | Delete an existing VM from an existing LB rule . | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1.Acquire IP address -p1 and create LB rule for vm1 and vm2 for public port 22 and private port 22
2.Delete vm2 from LB rule | We should see the traffic NOT being directed to the deleted Vm. | Functional | N | | |
F5-SRX- Inline-075 | Delete an existing VM from an existing LB rule.Add this Vm back to this Lb rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1.Acquire IP address -p1 and create LB rule for vm1 and vm2 for public port 22 and private port 22
2. Delete vm2 from LB rule
3. Add vm2 back to the LB rule | - After step2 we should see the traffic NOT being directed to the deleted Vm.
- After step3 we should see traffic being sent to the new Vm as well.
| Functional | N | | |
F5-SRX- Inline-076 | Delete all existing VM from an existing LB rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1.Acquire IP address -p1 and create LB rule for vm1 and vm2 for public port 22 and private port 22
2.Delete both the vms vm1 and vm2 from the LB rule | When request is made to the public ipadress that was associated with this LB rule , we should see it error out. | Functional | N | | |
| Vm Releated Operations which is assocaited with a LB rule. | | | | | | |
F5-SRX- Inline-077 | Stop user VM that has an LB rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1.Acquire IP address -p1 and create LB rule for vm1 and vm2 for public port 22 and private port 22
2. Stop both the vms vm1 and vm2 | Any request coming to the Load Balancer , will not be sent to this VM.
In F5:
LB rules for this VM still remain configured.But it will be marked as being down. | Functional | N | | |
F5-SRX- Inline-078 | Stop user VM that has an LB rule. After a while , start the VM. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1.Acquire IP address -p1 and create LB rule for vm1 and vm2 for public port 22 and private port 22
2.Stop both the vms vm1 and vm2
3. After a while start one/both the vms | Any request coming to the Load Balancer , will not be sent to this VM, when this VM is stopped.
Once the user VM is started , we should see the requests being directed to this VM as well.
In F5:
LB rules for this VM still remain configured. | Functional | N | | |
F5-SRX- Inline-079 | Have a user VM that has an LB rule migrate to a different host. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1.Acquire IP address -p1 and create LB rule for vm1 and vm2 for public port 22 and private port 22
2. Migrate vm1 to another host in the cluster | Any request coming to the Load Balancer , will not be sent to this VM, when this VM is in the process of migrating.
Once the user VM is migrated successfully , we should see the requests being directed to this VM as well. | Functional | N | | |
F5-SRX- Inline-080 | Reboot user VM that has an LB rule. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1.Acquire IP address -p1 and create LB rule for vm1 for public port 22 and private port 222. Roboot the user vm | In F5:
LB rules for this VM still remain configured. | Functional | N | | |
F5-SRX- Inline-081 | Destroy user VM. | PreReq:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
Steps:
1.Acquire IP address -p1 and create LB rule for vm1 for public port 22 and private port 22
2.Destroy user VM vm1 | Until the time the Vm is in "Destroyed" state , the services relating to this Vm will be marked as "Down".
Once the Vm gets expunged , then the servers and services associated with this VM should get deleted and the LB rules should not be pointing to this Vm anymore. | Functional | N | | |
| | | | | | | |
F5-SRX- Inline-082 | Deploy Vm using password enabled templates | Pre-Req:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Deploy vm using password enabled templates. | Should be able to create a vm using password enabled template. SRX and F5 inline mode should not impact this. | Functional | N | | |
F5-SRX- Inline-083 | Reset password | Pre-Req:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Deploy first vm in the account using NO created at step1.
5. Reset guest vm password | Should be able to reset the guest vm password. | Functional | N | | |
F5-SRX- Inline-084 | Deploy Vm using ssh enabled templates | Pre-Req:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Deploy vm using ssh enabled templates and use the NO created at step1. | Should be able to deploy vm using ssh enabled templates. | Functional | N | | |
F5-SRX- Inline-085 | Reset ssh keys | Pre-Req:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode.
4. Deploy first vm in the account using NO created at step 1 and using ssh keys.
5. Reset ssh keys for the guest vm created at step4 | Should be able to reset ssh keys for the guest vm | Functional | N | | |
F5-SRX- Inline-086 | Deploy Vm using userdata | Pre-Req:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Deploy first vm in the account using NO created at step 1 and using user data. | Should be able to create guest vm using userdata. | Functional | N | | |
F5-SRX- Inline-087 | Fetch metadata for user VMS | Pre-Req:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode 4. Deploy couple of guest vms using NO created at step1 5. Fetch metadata for the user vms created at step4 | Should be able to fetch the metadata for the user VMs. | Functional | N | | |
| Network Usage Testing | | | | | | |
F5-SRX- Inline-088 | Network usage for LB rules. | Create an LB rule.
Use the public Ip address to excersize the Lb rule. | Verify that "current_bytes_received" and "current_bytes_sent" in user_statistics table matches with what is stated in F5. | Functional | N | | |
| Network usage for PF rules. | Create a PF rule.
Use the public Ip address to excersize the PF rule. | Verify that "current_bytes_received" and "current_bytes_sent" in user_statistics table matches with what is stated in SRX. | Functional | N | | |
F5-SRX- Inline-089 | Network usage for Static NAT rules. | Create a Static NAT rule.
Use the public Ip address to excersize the Static NAT rule. | Verify that "current_bytes_received" and "current_bytes_sent" in user_statistics table matches with what is stated in SRX. | Functional | N | | |
| Network usage when F5 is down and brough back up again. | Create an LB rule.
Use the public Ip address to excersize the Lb rule.
Have F5 down( or unreachable) when the Network usage task is run. | There should be no descrepancies In the network read/write bytes when F5 instance is up and the network usage task is able to query the device successfully. | | | | |
F5-SRX- Inline-090 | Network usage when SRX is down and brough back up again. | Create a PF rule.
Use the public Ip address to excersize the PF rule.
Create a Static NAT rule.
Use the public Ip address to excersize the Static NAT rule.
Have SRX down( or unreachable) when the Network usage task is run. | There should be no descrepancies In the network read/write bytes when SRX instance is up and the network usage task is able to query the device successfully. | Functional | N | | |
F5-SRX- Inline-091 | Network usage after Restart Network with clean up option. | Pre-Req:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Acquire Ip address.
7. Create a PF rules on this ipaddress.
8. Acquire another Ip address.
9. Create a Static NAT on this ipaddress.
10. Acquire another Ip address.
11. Create a LB rule on this ipaddress.
12. Exersize the PF, Static NAT and Lb rules so that network tarffic is created.
Steps:
Restart network with cleanup option.
13. Exersize the PF, Static NAT and Lb rules so that network tarffic is created. | There should be no descrepancies In the network read/write bytes after network was restarted. | Functional | N | | |
F5-SRX- Inline-092 | Network usage after Restart Network without clean up option. | Pre-Req:
1. Create a NO using SRX for PF,Static NAT, Source Nat (Zone wide) and F5 for LB and rest of the services are provided by VR.
2. Add SRX device
3. Add F5 device is "Inline" mode and with "Shared" LB isolation mode
4. Add a user account.
5. Deploy few VMs using the above created NO.
6. Acquire Ip address.
7. Create a PF rules on this ipaddress.
8. Acquire another Ip address.
9. Create a Static NAT on this ipaddress.
10. Acquire another Ip address.
11. Create a LB rule on this ipaddress.
12. Exersize the PF, Static NAT and Lb rules so that network tarffic is created.
Steps:
Restart network without cleanup option. | There should be no descrepancies In the network read/write bytes after network was restarted. | Functional | N | | |
1 Comment
Unknown User (yasker)
Feb 12, 2013Looks fine.