Enabling 8021.Q VLAN Tagging in Zero Data Loss Recovery Appliance Over Ingest Networks
(Doc ID 2047411.1)
Last updated on JULY 07, 2022
Applies to:
Zero Data Loss Recovery Appliance X5 Hardware - Version All Versions and laterZero Data Loss Recovery Appliance Software - Version 12.1.1.1.1 and later
Linux x86-64
Goal
Enable 8021.Q VLAN Tagged Interfaces in Zero Data Loss Recovery Appliance for Ethernet ingest networks.
There are currently two scenarios for VLAN configuration on the ZDLRA.
- Scenario 1: Pre-install VLAN Configuration (The OEDA install.sh script was not run, for instance if this is a new installation)
- Scenario 2: Post-install VLAN Configuration (ZDLRA is in production and one or more tagged VLAN's are to be added)
IMPORTANT!!!
Please follow ALL naming conventions as suggested by ORACLE.
- Listeners => LIST_<VLAN_ID>
Sample VLAN IP Information
Verify the needed ip addresses: (use nslookup)
Checking Host: <HOST>ingest01-v3101.DOMAIN (<IP_ADDRESS>) ..
Checking Host: <HOST>ingest01-vip-v3101.<DOMAIN> (<IP_ADDRESS>) ..
Checking Host: <HOST>ingest02-v3101.<DOMAIN> (<IP_ADDRESS>) ..
Checking Host: <HOST>ingest02-vip-v3101.<DOMAIN> (<IP_ADDRESS>) ..
Checking Host: <HOST>ingest-scan1-v3101.<DOMAIN>
(<IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>) ..
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| Scenario 1: Pre-install VLAN Configuration: Converting an Untagged Ingest Network to Tagged Before Install |
| Prerequisites |
| 1. Create the tagged interface names for the ingest network |
| 2. Copy the untagged interface files to a tagged interface file |
| 3. Edit ingest network ifcfg-bondeth0 |
| 4. Edit the tagged interface ifcfg-bondeth0.VLAN_ID file to reflect the interface name |
| 5. Rename the untagged rule file to be tagged |
| 6. Rename the untagged route file to be tagged |
| 7. Edit the tagged route file to reflect the tagged interface |
| 8. Edit the /etc/sysconfig/network file to reflect the tagged interface name |
| 9. Restart the network by rebooting the host |
| 10. Edit the XML file to reflect the new tagged interface |
| 11. Continue with the install starting with OEDA install.sh step 1 |
| Scenario 2: Post-Install VLAN Configuration: Adding an Additional Tagged Ingest Network After Install |
| VLAN Information |
| 1. Stage the VLAN script in /home/oracle (ALL Compute nodes) |
| 2. Add the interface to Oracle Cluster Registry |
| 3. Start the VIPs (oracle user) |
| 4. Check the status of the VIPs (oracle user) |
| 5. Add and Start the DB Listener and SCAN Listener (oracle user) |
| 6. Add the database service that is associated with the network |
| 7. Add the Dispatcher Entry |
| 8. Run the following sql commands to address a known bug for listener networks: |
| 9. Restart ZDLRA Database: |
| 10. Reboot the All the Compute Nodes |
| 11. Add the interface to host table ( as rasys/ra ) |
| 12. Configure Protected Databases (Performed on the Client/Protected DB System!) |
| 13. Create or update the Wallet on all nodes in the cluster |
| 14. Now add the vpcuser wallet credential |
| 15. Register the Protected Database in the ZDLRA |
| 16. Configure the Backup Devices |
| 17. Run a Test Backup |
| 18. Configuring Real-Time Redo Transport |
| 19. Bounce the Protected Database |