Veritas InfoScale™ 7.3.1 Release Notes - Linux
- Introduction
- Changes introduced in 7.3.1
- Changes related to installation and upgrades
- Changes related to the Cluster Server engine
- Changes related to Cluster Server agents
- Changes related to InfoScale in cloud environments
- Changes related to Veritas Volume Manager
- Changes related to Veritas File System
- Changes related to replication
- Changes related to Dynamic Multipathing
- System requirements
- Fixed Issues
- Known Issues
- Issues related to installation and upgrade
- Issues related to Veritas InfoScale Storage in Amazon Web Services cloud environments
- Storage Foundation known issues
- Dynamic Multi-Pathing known issues
- Veritas Volume Manager known issues
- Virtualization known issues
- Veritas File System known issues
- Replication known issues
- Cluster Server known issues
- Operational issues for VCS
- Issues related to the VCS engine
- Issues related to the bundled agents
- Issues related to the VCS database agents
- Issues related to the agent framework
- Cluster Server agents for Volume Replicator known issues
- Issues related to Intelligent Monitoring Framework (IMF)
- Issues related to global clusters
- Issues related to the Cluster Manager (Java Console)
- VCS Cluster Configuration wizard issues
- LLT known issues
- I/O fencing known issues
- Operational issues for VCS
- Storage Foundation and High Availability known issues
- Storage Foundation Cluster File System High Availability known issues
- Storage Foundation for Oracle RAC known issues
- Oracle RAC known issues
- Storage Foundation Oracle RAC issues
- Storage Foundation for Databases (SFDB) tools known issues
- Storage Foundation for Sybase ASE CE known issues
- Application isolation feature known Issues
- Cloud deployment known issues
- Issues related to installation and upgrade
- Software Limitations
- Virtualization software limitations
- Storage Foundation software limitations
- Dynamic Multi-Pathing software limitations
- Veritas Volume Manager software limitations
- Veritas File System software limitations
- SmartIO software limitations
- Replication software limitations
- Cluster Server software limitations
- Limitations related to bundled agents
- Limitations related to VCS engine
- Veritas cluster configuration wizard limitations
- Limitations related to the VCS database agents
- Cluster Manager (Java console) limitations
- Limitations related to LLT
- Limitations related to I/O fencing
- Limitations related to bundled agents
- Storage Foundation Cluster File System High Availability software limitations
- Storage Foundation for Oracle RAC software limitations
- Storage Foundation for Databases (SFDB) tools software limitations
- Storage Foundation for Sybase ASE CE software limitations
When you execute the unit service file (RHEL 7 or SLES 12 onwards) or the LSB file to load the LLT module, the syslog file may record messages related to kernel symbols associated with Infiniband (3136418)
When you execute the unit service file (RHEL 7 or SLES 12 onwards) or the LSB file to start the LLT module on some Linux kernel versions, the syslog file may display the following messages for multiple such symbols:
kernel: llt: disagrees about version of symbol ib_create_cq kernel: llt: Unknown symbol ib_create_cq
The LLT module is shipped with multiple module *.ko files, which are built against different kernel versions. If the kernel version on the node does not match the kernel version against which the LLT module is built, the LLT module fails to load and logs RDMA-related messages in the syslog file. In this case, the kernel logs these messages. The modinst script loads the compatible module on the system and starts LLT without any issues.
Workaround: Rearrange the kernel versions in the /opt/VRTSllt/kvers.lst
file such that the first line displays the kernel version that is most likely to be compatible with the kernel version on the node. This rearrangement allows the modinst script to load the best possible kernel module first. Therefore, the warning message is less likely to appear.