Disk and Volume Summary
+----------- Disk ------------+------------------- Volume --------------------+
| | LVM File System |
| Num Name Size Free | Name Size Size Usage |
+-----------------------------+-----------------------------------------------+
| 1 sda 41.78 0.00 | / 4.00 3.81 1.26 |
| | /home 4.00 3.81 0.05 |
| | /opt/Avaya 14.97 14.61 1.14 |
| | /tmp 2.81 2.71 0.01 |
| | /var 3.00 2.89 0.03 |
| | /var/log 2.00 1.91 0.00 |
| | /var/log/audit 3.00 2.89 0.00 |
| | swap 8.00 n/a n/a |
+-----------------------------+-----------------------------------------------+
| 2 sdb 60.00 0.00 | /var/log/Avaya 60.00 58.93 0.05 |
+-----------------------------+-----------------------------------------------+
| 3 sdc 20.00 0.00 | /media/data 20.00 19.56 0.04 |
+-----------------------------+-----------------------------------------------+
| 4 sdd 10.00 0.00 | /media/cassandra 10.00 9.71 0.02 |
+-----------------------------+-----------------------------------------------+
sys smcvemgt command
The system layer
smcvemgt
command is used to manage the Linux kernel patches related to the
following vulnerabilities:
• Variant #2/Spectre (CVE-2017–5715)
• Variant #3/Meltdown (CVE-2017–5754)
Note:
The kernel patch for the Variant #1/Spectre (CVE-2017–5754) vulnerability is permanently
enabled on the system and cannot be disabled.
The choice to enable or disable these patches is a trade-off between performance and security
impact:
• If the patches are enabled, the system might experience noticeable performance losses.
• If the patches are disabled, the system is not protected against the Variant #2/Spectre and
Variant #3/Meltdown vulnerabilities.
By default, Linux patches for Variant #2/Spectre and Variant #3/Meltdown are enabled. The
Variant #2/Spectre patch is enabled with Linux kernel defaults. In default operation mode, the
Variant #2/Spectre Linux patch selects the mitigation method that is best suited for the processor
architecture of the host machine.
Note:
To be fully functional, patches for the Variant #2/Spectre vulnerability require hardware
support, which is provided by VMware and hardware vendors through microcode updates.
Changes made by the
smcvemgt
command to the Linux kernel tunalbles always cause a server
reboot. The script does not manage the state of application services. To ensure that the
application services are stopped before the reboot, run the
svc csa stop
command before
Planning and preinstallation
October 2018
Deploying the Avaya Aura
®
Web Gateway
34