Storage Foundation for Sybase ASE CE 7.4 Administrator's Guide - Linux
- Overview of Storage Foundation for Sybase ASE CE
- About Storage Foundation for Sybase ASE CE
- How SF Sybase CE works (high-level perspective)
- About SF Sybase CE components
- About optional features in SF Sybase CE
- How the agent makes Sybase highly available
- About Veritas InfoScale Operations Manager
- Administering SF Sybase CE and its components
- Administering SF Sybase CE
- Setting the environment variables for SF Sybase CE
- Starting or stopping SF Sybase CE on each node
- Applying operating system updates on SF Sybase CE nodes
- Adding storage to an SF Sybase CE cluster
- Recovering from storage failure
- Enhancing the performance of SF Sybase CE clusters
- Verifying the nodes in an SF Sybase CE cluster
- Administering VCS
- Viewing available Veritas device drivers
- Starting and stopping VCS
- Environment variables to start and stop VCS modules
- Adding and removing LLT links
- Configuring aggregated interfaces under LLT
- Displaying the cluster details and LLT version for LLT links
- Configuring destination-based load balancing for LLT
- Enabling and disabling intelligent resource monitoring for agents manually
- Administering the AMF kernel driver
- Administering I/O fencing
- About administering I/O fencing
- About the vxfentsthdw utility
- General guidelines for using the vxfentsthdw utility
- About the vxfentsthdw command options
- Testing the coordinator disk group using the -c option of vxfentsthdw
- Performing non-destructive testing on the disks using the -r option
- Testing the shared disks using the vxfentsthdw -m option
- Testing the shared disks listed in a file using the vxfentsthdw -f option
- Testing all the disks in a disk group using the vxfentsthdw -g option
- Testing a disk with existing keys
- About the vxfenadm utility
- About the vxfenclearpre utility
- About the vxfenswap utility
- Enabling or disabling the preferred fencing policy
- About I/O fencing log files
- Administering CVM
- Establishing CVM cluster membership manually
- Changing the CVM master manually
- Importing a shared disk group manually
- Deporting a shared disk group manually
- Verifying if CVM is running in an SF Sybase CE cluster
- Verifying CVM membership state
- Verifying the state of CVM shared disk groups
- Verifying the activation mode
- Administering CFS
- Administering the Sybase agent
- Sybase agent functions
- Monitoring options for the Sybase agent
- Using the IPC Cleanup feature for the Sybase agent
- Configuring the service group Sybase using the command line
- Bringing the Sybase service group online
- Taking the Sybase service group offline
- Modifying the Sybase service group configuration
- Viewing the agent log for Sybase
- Administering SF Sybase CE
- Troubleshooting SF Sybase CE
- About troubleshooting SF Sybase CE
- Restarting the installer after a failed network connection
- Installer cannot create UUID for the cluster
- Troubleshooting I/O fencing
- The vxfentsthdw utility fails when SCSI TEST UNIT READY command fails
- Node is unable to join cluster while another node is being ejected
- System panics to prevent potential data corruption
- Cluster ID on the I/O fencing key of coordinator disk does not match the local cluster's ID
- Fencing startup reports preexisting split-brain
- Registered keys are lost on the coordinator disks
- Replacing defective disks when the cluster is offline
- Troubleshooting Cluster Volume Manager in SF Sybase CE clusters
- Restoring communication between host and disks after cable disconnection
- Shared disk group cannot be imported in SF Sybase CE cluster
- Error importing shared disk groups in SF Sybase CE cluster
- Unable to start CVM in SF Sybase CE cluster
- CVM group is not online after adding a node to the SF Sybase CE cluster
- CVMVolDg not online even though CVMCluster is online in SF Sybase CE cluster
- Shared disks not visible in SF Sybase CE cluster
- Troubleshooting interconnects
- Troubleshooting Sybase ASE CE
- Prevention and recovery strategies
- Prevention and recovery strategies
- Verification of GAB ports in SF Sybase CE cluster
- Examining GAB seed membership
- Manual GAB membership seeding
- Evaluating VCS I/O fencing ports
- Verifying normal functioning of VCS I/O fencing
- Managing SCSI-3 PR keys in SF Sybase CE cluster
- Identifying a faulty coordinator LUN
- Starting shared volumes manually
- Listing all the CVM shared disks
- I/O Fencing kernel logs
- Prevention and recovery strategies
- Tunable parameters
- Appendix A. Error messages
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.
For RHEL 7, SLES 12, and supported RHEL distributions:
# systemctl stop llt
For earlier versions of RHEL, SLES, and supported RHEL distributions:
# /etc/init.d/llt stop
- 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.
For RHEL 7, SLES 12, and supported RHEL distributions:
# systemctl start llt
For earlier versions of RHEL, SLES, and supported RHEL distributions:
# /etc/init.d/llt start
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”.