InfoScale™ 9.0 Storage Foundation for Oracle® RAC Administrator's Guide - Linux
- Section I. SF Oracle RAC concepts and administration
- Overview of Storage Foundation for Oracle RAC
- Component products and processes of SF Oracle RAC
- Communication infrastructure
- Cluster interconnect communication channel
- Cluster Volume Manager (CVM)
- About Flexible Storage Sharing
- Cluster File System (CFS)
- Cluster Server (VCS)
- Oracle RAC components
- Oracle Disk Manager
- RAC extensions
- About Virtual Business Services
- Administering SF Oracle RAC and its components
- Administering SF Oracle RAC
- Starting or stopping SF Oracle RAC on each node
- Administering VCS
- Administering I/O fencing
- About the vxfentsthdw utility
- About the vxfenadm utility
- About the vxfenswap utility
- Administering the CP server
- Administering CFS
- Administering CVM
- Changing the CVM master manually
- Administering Flexible Storage Sharing
- Backing up and restoring disk group configuration data
- Administering SF Oracle RAC global clusters
- Administering SF Oracle RAC
- Overview of Storage Foundation for Oracle RAC
- Section II. Performance and troubleshooting
- Troubleshooting SF Oracle RAC
- About troubleshooting SF Oracle RAC
- Troubleshooting I/O fencing
- Troubleshooting CP server
- Troubleshooting server-based fencing on the SF Oracle RAC cluster nodes
- Issues during online migration of coordination points
- Troubleshooting Cluster Volume Manager in SF Oracle RAC clusters
- Troubleshooting CFS
- Troubleshooting interconnects
- Troubleshooting Oracle
- Troubleshooting ODM in SF Oracle RAC clusters
- Prevention and recovery strategies
- Tunable parameters
- Troubleshooting SF Oracle RAC
- Section III. Reference
Configuring aggregated interfaces under LLT
If you want to configure LLT to use aggregated interfaces after installing and configuring VCS, you can use one of the following approaches:
Edit the /etc/llttab file
This approach requires you to stop LLT. The aggregated interface configuration is persistent across reboots.
Run the lltconfig command
This approach lets you configure aggregated interfaces on the fly. However, the changes are not persistent across reboots.
To configure aggregated interfaces under LLT by editing the /etc/llttab file
- If LLT is running, stop LLT after you stop the other dependent modules.
# systemctl stop llt
- Add the following entry to the
/etc/llttab
file to configure an aggregated interface.link tag device_name systemid_range link_type sap mtu_size
tag
Tag to identify the link
device_name
Device name of the aggregated interface.
systemid_range
Range of systems for which the command is valid.
If the link command is valid for all systems, specify a dash (-).
link_type
The link type must be ether.
sap
SAP to bind on the network links.
Default is 0xcafe.
mtu_size
Maximum transmission unit to send packets on network links
- Restart LLT for the changes to take effect. Restart the other dependent modules that you stopped in step 1.
# systemctl start llt
To configure aggregated interfaces under LLT using the lltconfig command
- When LLT is running, use the following command to configure an aggregated interface:
lltconfig -t devtag -d device [-b linktype ] [-s SAP] [-m mtu]
devtag
Tag to identify the link.
device
Device name of the aggregated interface.
link_type
The link type must be ether.
sap
SAP to bind on the network links.
Default is 0xcafe.
mtu_size
Maximum transmission unit to send packets on network links.
See the lltconfig(1M) manual page for more details.
You need not reboot after you make this change. However, to make these changes persistent across reboot, you must update the
/etc/llttab
file.See “To configure aggregated interfaces under LLT by editing the /etc/llttab file”.