4.1Supported Virtualization Software (Project-Specific Only)
The use of virtualization software in conjunction with OpenScape Office generally requires a project-specific release.
OpenScape Office HX V2
|
OpenScape Office LX V3
|
VMware vSphere ESX/ESXi 4
|
VMware vSphere ESX/ESXi 4
| 4.2Supported Operating System Versions
OpenScape Office HX V2
|
OpenScape Office LX V3
|
OpenSuse 10.3 (32 bit) (only for upgrading)
|
SUSE Linux Enterprise Server 11 SP1 (x86)
|
SLES 10 SP2 (x86) (only for upgrading)
|
|
SLES 10 SP3 (x86)
|
| 4.3General Software Constraints and Restrictions -
Only the 32 bit versions of the Linux operating systems may be used.
-
Apart from OpenScape Office and the related applications, no further applications should be installed and operated on the Linux machine.
-
The only exception is the antivirus application. Virus scanners can be operated on a computer with OpenScape Office in accordance with the application requirements.
-
The installation of OpenScape Office overwrites any existing configuration files (e.g., for DHCP, FTP, Samba, Postfix, etc.).
4.3.1Patches and Updates for the SLES Operating System
SEN has formulated a generally applicable security policy concerning the use of patches and software updates for operating systems running SEN applications as well as the resulting procedures and responsibilities. Some extracts from it are reproduced below:
Extract from the SEN Security Policy:
“Support of Operating System Updates for Server Applications”
|
Customers of SEN usually define their own security policies and standards, where the installation of security updates for the servers' operating systems is a mandatory requirement. The updates need to be applied in a timely manner to protect the server from being exploited by viruses, worms or other malicious attacks from the network. SEN explicitly recommends implementing best-practice security measures in the customer's network. This also includes the installation of security updates as soon as practical to the customer. Note however, that
-
The installation of any operating system update may require compatibility tests prior to their release for the application software.
-
The urgency of some operating system updates often requires the customer to proceed in advance of advice or verification from the vendors of the software installed on the affected application servers.
As a general statement, SEN assumes that future operating system updates maintain backward compatibility to older versions of the files and executables being updated. Based on that fact, SEN assumes low risk with installing these updates.
However, SEN strongly recommends that customers perform functional and performance testing prior to deploying these updates in a production environment.
As part of product planning and the System-, Release- and Regression-Tests, SEN reviews and tests Operating System updates on a regular basis. The general proceeding is as follows……..
Service Packs and Minor Versions
Updates at short notice are contained in the release notes. The list may change with every major, minor or fix release of the product. The minimum Operating System version required to run the application does not change within a product’s major release, but every new major release of the product may remove older Operating System versions from the list. Therefore, if more than one service pack or version is listed, SEN recommends always using the latest one that the product officially supports.
Security Updates and Critical Updates
All System-, Release- and Regression-Tests are performed using the latest updates released by the Operating System vendor until the time the respective test was planned and executed. SEN recommends using always the latest updates released by the vendor. Their installation does not void the customer's warranty or maintenance contract for the product. SEN also recommends functional and performance testing to be performed prior to deploying these updates in a production environment. If the installation or operation of an Operating System update causes the SEN product to malfunction, then the customer should:
-
Remove or disable the update to restore proper system operation. The customer can, of course, choose to leave the update installed if, in their opinion, the risk of operating without it is higher than the cost of the malfunction.
-
Report the problem to SEN using the normal product support process. Re-install or enable the update after investigation and advice from SEN.
|
The complete and current "SEN Security Policy - Support of Operating System Updates for Server Applications" is available via the link provided in section 8.1.2.4
4.3.1.1Procedure for OpenScape Office HX / LX
General:
In principle, only updates for the Linux version supplied by SEN in conjunction with OpenScape Office HX / LX may be installed.
An upgrade to a possibly newer Linux version or service pack is not allowed, unless this is explicitly noted in the SEN software release information for OpenScape Office HX and LX.
The following scenarios must be differentiated for the handling of the Linux update function.
1.) Update during the SLES installation
After registering the activation code at Novell, there is an option to update the previously installed SLES version online. This option should be exercised during the installation, and all components offered for the update should be installed, except for complete service packs.
2.) Update after the SLES installation and before the OpenScape Office installation
After the SLES software installation and the registration of the activation code at Novell, an online update can be optionally performed using YaSt. All components offered for the update, except for complete service packs, may be installed.
3.) Update after the OpenScape Office installation
After the installation of OpenScape Office, only those "security patches" that are installed automatically online without any questions may be installed.
The SLES software manager should ensure this with the appropriate settings.
Depending on the OpenScape Office HX / LX and SLES versions involved, there may be some deviations from the scenarios described above. These will be communicated in the release notes for the OpenScape Office HX / LX software.
All other SLES software updates must be tested for proper functionality in conjunction with OpenScape Office HX / LX prior to being used on a production system.
4.3.2VMware vSphere ESX / ESXi 4 (Project-Specific)
The following VMware vSphere ESX/ESXi 4 features are supported:
-
Thin Provisioning
-
High Availability (HA)
-
VMotion
-
Data Recovery (VDR)
-
DRS (Automatic VMotion)
-
Storage VMotion
The following VMware vSphere ESX/ESXi 4 features are not supported:
Share with your friends: |
