Cluster update for NetWare 6.5 SP8 v1.80.05
This document (5043380) is provided subject to the disclaimer at the end of this document.
patches this patch supersedes
patches that supersede this patch
patch attributes
document
technical support
This Field Test File is supported by Novell Technical Services.
abstract
Post Support Pack 8 SBD modules that resolve abends caused by SBD corruption.
details
Overview:
Updated SBD modules for Novell NetWare 6.5
System Requirements:
Novell NetWare 6.5 Support Pack 8
Installation:
(1) Unload NCS on the cluster node you are upgrading.
(2) Verify the existing SBD.NLM and SBDLIB.NLM modules do not have the following properties set on the file(s):
Delete Inhibit - If checked, this indicates that this file or folder cannot be deleted.
Read Only - If checked, this indicates that this file cannot be deleted or modified.
(3) rename the existing SYS:\SYSTEM\SBD.NLM to SYS:SYSTEM\SBD.SP8
rename the existing SYS:\SYSTEM\SBDLIB.NLM to SYS:\SYSTEM\SBDLIB.SP8
(4) Copy the SBD.NLM and SBDLIB.NLM from this patch to SYS:\SYSTEM\ respectively.
(5) Re-apply the 'Delete Inhibit' and 'Read Only' settings to these new modules when applicable.
(6) Re-load NCS on this cluster node
Un-installing:
(1) Unload NCS on the cluster node you are downgrading
(2) Verify the 'Delete Inhibit' and 'Read Only' settings again
(3) Delete the existing SYS:\SYSTEM\SBD.NLM and SYS:\SYSTEM\SBDLIB.NLM
(4) rename the existing SYS:\SYSTEM\SBD.SP8 to SYS:SYSTEM\SBD.NLM
rename the existing SYS:\SYSTEM\SBDLIB.SP8 to SYS:\SYSTEM\SBDLIB.NLM
(5) Re-apply the 'Delete Inhibit' and 'Read Only' settings to these new modules when applicable.
(6) Re-load NCS on this cluster node
Known Problems and Limitations:
1. There is no upper limit of the size of a SBD partition. However, NCS only utilizes the first 2TB of any SBD partitions.
2. 1MB of space can hold approx. 2000 events. NCS normally generates fewer than 2000 events a day.
Once a partition is full, NCS keeps overwriting the oldest events.
3. Older 'sbd' and 'sbdlib' modules can work with larger SBD partitions.
We are not aware of any problems using these modules and clustering on NetWare 6.5 SP7.
We have run these modules on a 'mixed' SP7/SP8 cluster succesfully, however please be aware these modules
have been tested against NetWare 6.5 SP8, and have undergone only limited testing against NetWare 6.5 SP7.
4. Only these newer modules are capable of creating larger partitions, and displaying information about NCS log.
5. In addition to similar manual steps, we will add a field to specify SBD partition size during installation time on Linux (and only on Linux).
Technical Support Information:
These modules resolve the issue described in :
- Bug 257911 - list of devices in SBD install scrolls of screen in large environments, Device IDs are in decimal
The Device ID's of where the SBD partiton may be created are now displayed in HEX values.
- Bug 455710 - Abends due to corrupt entry in cluster SBD partition
Data corruption within the SBD partition caused cluster servers to abend in "SbdReadRecord()" of SBD.NLM. This corruption sometimes already occurred within few hours after re-creating the SBD partition.
We store the length of a message in a SBD record on the SBD partition. Data corruption on the partition may enlarge the length and therefor cause the server to abend when copying the message. We have now added a defensive mechanism in SBD to prevent the server from abending. We do this by having the mechanism check if the length exceeds the maximum length allowed for reading a record from this partition, and by verifying the length before we write the SBD records out to the SBD partition.
In order to benefit from this fix, you need to delete and re-create the existing SBD partition.
Please follow these guidelines for (re-)creating larger SBD partitions on Novell NetWare 6.5 SP8:
1. Unload NCS on all nodes.
2. On one node, delete old SBD partitions using NSSMU.
3. Copy the modules from this patch to sys:\system\.
4. Load 'clstrlib', 'vll', 'sbdlib' and 'sbd'.
SBD will report that 'There is NO SBD Partition required by the cluster' and asks you to run 'SBD install'
5. Run 'SBD install xx' (where xx is the size of the partition in MB).*
6. Choose whether to mirror SBD partitions.
7. Enter the device numbers in hexadecimal values **
8. If successful, run NSSMU on other nodes to make sure that old SBD partitions are
deleted and new partitions are created with the right size.
If needed, run 'scan for new devices' to clear NSS caches.
9. Load NCS on all nodes.
* To better help estimate what the the size of your 'new' SBD partition should be,
you may refer to point 2 with the "Known Problems and Limitations" section
** When you have more devices for the SBD partition available than fit on the screen,
you can use the PGUP/PGDN button to browse through the list that scrolled of the
screen before you specify the Device ID for the SBD partition
Module overview:
SP7 is shipped with the following SBD modules:
SBDLIB.NLM
Cluster Split Brain Detector Library Build Number = 1.8.4-367
Version 1.80.04 12 September 2007
SBD.NLM
Cluster Split Brain Detector Build Number = 1.8.4-367
Version 1.80.04 12 September 2007
SP8 is shipped with the following SBD modules:
SBDLIB.NLM
Cluster Split Brain Detector Library Build Number = 1.8.4-367
Version 1.80.04 12 September 2007
SBD.NLM
Cluster Split Brain Detector Build Number = 1.8.5-470
Version 1.80.05 6 October 2008
After applying this patch you have the following SBD modules:
SBDLIB.NLM
Cluster Split Brain Detector Library Build Number = 1.8.5-501
Version 1.80.05 3 March 2009
SBD.NLM
Cluster Split Brain Detector Build Number = 1.8.5-501
Version 1.80.05 3 March 2009
file contents
Compressed File Name: sp8sbdup.zip
| Files Included | Size | Date |
|---|---|---|
| sp8sbdup/sbdlib.nlm | 10.7 KB (11051) | 2009-03-04 08:59:53 |
| sp8sbdup/sbd.nlm | 34.7 KB (35633) | 2009-03-04 08:59:55 |
| license_agreement.txt | 2.8 KB (2909) | 2009-03-04 09:25:02 |
| readme_5043380.html | N/A | 2009-03-09 02:46:29 |
| readme.html | N/A | 2009-03-09 02:46:29 |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.
Novell is a registered trademark of Novell, Inc. in the United States and other countries. SUSE is a registered trademark of SUSE Linux AG, a Novell business. *All third-party trademarks are the property of their respective owners.
© 2007 Novell, Inc. All Rights Reserved.