SLES/OES Partitioning

I have an HP ml110 G7 server with B110i (fakeraid) controller 2 - 1 Tb drives in Raid 10 with 1 Tb online spare drive. I am installing SLES 11 SP3 and OES 11 SP2. I partitioned the storage with a /boot, /, and swap partition the remainder as LVM. When I try to initiate an NSS pool there is no device space available.
How should I partition the array? Can NSS pools use the unassigned space on the LVM partition? How?

On 21/02/2014 23:06, jjoyce wrote:
> I have an HP ml110 G7 server with B110i (fakeraid) controller 2 - 1 Tb
> drives in Raid 10 with 1 Tb online spare drive. I am installing SLES 11
> SP3 and OES 11 SP2. I partitioned the storage with a /boot, /, and swap
> partition the remainder as LVM. When I try to initiate an NSS pool
> there is no device space available.
>
> How should I partition the array? Can NSS pools use the unassigned
> space on the LVM partition? How?
There are two issues at play here:
1) OES11 includes it's own Novell Linux Volume Manager (NLVM) which is
used instead of LVM and that's why there is no free space available to
create a NSS pool
2) you should not use software RAID for NSS storage and instead use NSS
Software RAID
See http://www.novell.com/documentation/...a/bwvc1xm.html
HTH.
Simon
Novell Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

Similar Messages

SLES OES Patching using ZCM - Best Practice?

Have recently updated an underused ZLM 7.3 to ZCM 11 and have started to utilise it to perform patching of SLES 10 SP3 and OES 2.
At present I have a Novell subscription that downloads from novell NU as Patches with
Create Category based Bundle Groups on.
I hadn't at this point got my head around the sandbox but now want to utilise this as I don't want to implement it willy nilly and have patches deployed and installed without testing first.
So first question is whether there is a best practice document for using ZCM 11 for patching SLES 10 and Sles/oes boxes that describes how best to use the sandbox.
Next question is whether sandbox applies to the patches or only monolithic bundles
At the end of the day it would be great to have a best practice document on how to utilise ZCM with change control over keeping SLES10/OES boxes patched up to date

Hello,
updates via ZCM is also a problem for me.
At least i could give a little response from testing.
As stated in the oes2 documentation patches had to be used for updates. At that point i had the problem that the subscription only created a bundle group which included the patches.
The monolithic bundle seems to be an ordinary update (zcm docu states rpm -U ...) and so should not be used for oes2 servers.
I found out that its ok to rename the patch bundle group created by the subscription to fix the patchlist. I use bundle names which include the date to keep updates from sles and oes in sync.
So you should be able to do updates with these bundlegroups without problem but it is not very nice because each patch bundle had its on log report and entry in the bundle list.
So to keep a global view is not very easy.
The other problem is that there is no official documentation neither on the oes2 or the zcm site how to correct update/patch a sles or oes system with zcm (without patchlink).
Hope this will be included soon as all linux satellite server will have the problem that this is the only way to get updates without direkt connection to the internet - at least as far as i can see.

Need some help with SLES/OES

Converting from Netware 6.5 to SLES/OES. We really do not want to migrate our servers over as we have had one to many cooks in the kitchen and the eDirectory and file structure is not very clean. Very confused, even after going through some Novell self training manuals. Do we need OES? What version of SLES and OES play nice together?
Our environment consists of about 2000 devices, mostly XP but a fair amount of Windows 7 machines. Our users are broken into two organizational units, one for our high school and one for our junior high. Each OU has users broken into teachers and student groups. Obviously, teachers have more authority and storage space than students. Students profile are based on some of the classes they take that need some special privileges. We have it structured now that only one application is pushed to the students or teacher desktop. Only thing we really do is script to map drives for storage and push down app to direct traffic to our Internet filter. We do not use anything like Groupwise, iFolder, or iPrint at this time.
Getting close to crunch time and need to figure out not only server configuration, but what client software to put on our workstation. Any help, guidance, or direction would be greatly appreciated.

On Sun, 22 Jul 2012 23:36:02 GMT, jdelucaka
<[email protected]> wrote:
>
>Converting from Netware 6.5 to SLES/OES. We really do not want to
>migrate our servers over as we have had one to many cooks in the kitchen
>and the eDirectory and file structure is not very clean. Very confused,
>even after going through some Novell self training manuals. Do we need
>OES? What version of SLES and OES play nice together?
>
>Our environment consists of about 2000 devices, mostly XP but a fair
>amount of Windows 7 machines. Our users are broken into two
>organizational units, one for our high school and one for our junior
>high. Each OU has users broken into teachers and student groups.
>Obviously, teachers have more authority and storage space than students.
>Students profile are based on some of the classes they take that need
>some special privileges. We have it structured now that only one
>application is pushed to the students or teacher desktop. Only thing we
>really do is script to map drives for storage and push down app to
>direct traffic to our Internet filter. We do not use anything like
>Groupwise, iFolder, or iPrint at this time.
>
>Getting close to crunch time and need to figure out not only server
>configuration, but what client software to put on our workstation. Any
>help, guidance, or direction would be greatly appreciated.
Since you mention you are currently mapping drives for storage, I
assume you are using NSS and setting rights for users. If you want to
keep doing things the same way, use the OES/SLES combination. Last I
heard, you want to use SLES 11 SP1 if using OES 11. Not sure if that
has changed yet or not. I'm in the middle of migrating Netware to OES
11 and it is a smooth process. Not sure how much printing you do, but
you might want to consider iPrint...I like how it simplifies the whole
process.
Regards,
Ken

OES 11 SP2 Shema Extensions

I am planning on adding my first OES 11 SP2 server into our Tree. What is the best way to Extend the schema to prepare for this? According to the Docs it says
"The simplest way to extend the schema for OES 11 SP2 servers is to have a tree admin install the first OES 11 SP2 server and the first instance of each OES 11 SP2 service that you plan to run on your network."
I am a tree admin, so if I install the latest SLES/OES on a server, does this mean that the schema will automatically be extended and I will not have to do anything else with the Schema? Or is there a better way to do this by extending it prior to installing the server into the tree?
Thanks,
Andrew

On 04/08/2014 10:56 AM, acshearer wrote:
>
> Here is the link from the documentation.
>
> https://www.novell.com/documentation...t.html#bhora0c
Good to know.
Well, there are technically correct things about that page, though I wish
it would elaborate a bit more.
First, the reason you use a tree admin is because you need to be a tree
admin to make schema changes at the [root] of the tree. Simple enough.
Second, while pointing to a Read/Write of [root] should work, the fact of
the matter is that one of the few roles that a Master has alone is control
of schema, so why does the doc state to point to a R/W? No idea. Point
to the Master of [root] unless you really, really cannot (and I would be
surprised if this was ever really a legitimate problem/limitation). Doing
so ensures that, if schema is taken by the Master, it will be pushed out
(to other server holding replicas of the [root] partition) and down (to
child partition Masters and R/Ws). Schema always flows out and down.
That a R/W may be clever enough to take changes and send them to the
Master is moot, in my mind.
Finally, I've never used that Yast-based schema tool, and that may work
really well. The biggest concern I would have with that is that it
implies adding your new server to the tree in a way that cannot extend
tree schema, and then doing the schema extension later. That's not
terrible, and eDirectory will be fine eventually, but in the meantime your
new OES server may have fits about things requiring new schema, such as
the LDAP services in eDir 8.8 SP8. As a result, LDAP may not load until
you do this schema extension, then some followup steps ('ndsconfig
upgrade' on the new server may do all of it for you) to get things
configured once the new schema is available throughout the tree. My hope,
though, is that the Yast-based tool can be pointed not just to the Master
(not R/W... a broken record I am, I know) or [root], but that it can be
pointed from this tree (the test one I mentioned before) to that tree over
there (the production one) and do the same thing. If so, this may be the
easiest and safest way (since not using ndsrepair) to extend schema in a
tree from another server. If so, I like this tool.
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

ZENworks 7 on SLES - OES2, yes or no?

Existing environment is ZDM7 SP1 on NetWare 6.5. I'm looking to bring a
new ZDM7 SP1 IR4a server online on SLES 10 SP2 and i'm pondering whether
or not I should add OES2 into the mix? Looking to hear from others...
From my initial reading, I have the impression that OES2 will more or
less account for various services/dependencies required by ZENworks.
Skipping OES2 means more manual installation/configuration re:
eDirectory, LDAP, Samba, etc to get things working.
I'm doing some mock up in a virtual environment now.
Thanks.

tanmaygoel,
>That's an interesting point and I am currently trying to make this
>decision. Why do you say that? What are the advantages of installing
>Zenworks Configuration Management 10.2 on SLES as compared to SLES+OES?
You will not have the services / port conflicts when you install just
SLES. ZCM doesn't require or use any of the OES services and thus there is
no benefit. There IS one exception to this. It is possible to change the
content-repo location to a NSS mount point which would then make it
possible to access the images via a workstation from UNC or drive letter.
Jared Jennings
Novell Support Forums Sysop
Senior Systems Architect, Data Technique, Inc.
http://www.datatechnique.com
My Blog and Wiki with Tips, Tricks, and Tutorials
http://jaredjennings.org
Twitter@ http://twitter.com/jaredljennings

SLES10 SP4/OES2 SP3 32 bit Clean Install - Basic Questions

Hi everyone.
I am now an expert in installing the above software and ending up with a server which does not work as we require. Must be something I am doing wrong. Hope someone can spot it.
Have installed and supported Netware servers for 25 years without major problems. Decided now to move to SLES because Novell say we should and we need Groupwise 12 to replace GroupWise 8.
The operational environment we are targeting is an 80 user edirectory/NDS based single tree, single context containing two Netware 6.5 SP8 HP Proliant servers running uncomplicated file and print services , NSS volumes, Groupwise 8, DHCP, ifolder, Quickfinder and the like, spread across the two servers. It all works a treat. Client PCs are are all XP Pro with Novell client software.
The idea would be to replace one of the two Netware servers first with a SLES/OES server and then the second Netware server with a second SLES/OES server and move GroupWise functionality to one of the SLES/OES servers. Ideally users would continue to log on using their eDirectory accounts without noticing anything was going on in the background.
The test environment we have set up is a 5 user NDS/eDirectory single tree, single context already containing a single Netware 6.5 SP8 Proliant server running file and print, NSS volumes etc and Groupwise 8. Into this tree we are trying to install a 32 bit server with a empty 36 GB SCSI disc running SLES 10 SP4 with OES2 DP3 as an add in, with NSS data volumes.
Because it only takes a few hours to do we have repeatedly run the SLES 10/OES2 install (probably about 9 times!) with minor variations to see whether we can end up with a properly configured SLES/OES server but there is always one problem or another.
The major problem we have is how to configure NSS data volumes on the SLES server and how to allow users to be validated against their eDirectory entries and knowing whether the test server is 'good to go'.
The process we followed for each test install, after checking edirectory was clean and removing any entries placed in the tree by earlier attempts to install the SLES server in the same tree were:
1. Boot the SLES 10 SP4 32 DVD (downloaded ISO and burnt DVD) and selected Installation.
2. Followed the prompts on time zone and language etc and selected i386 OES CD (also downloaded ISO and burnt) as the Software Add-In.
3. Loaded SLES DVD and OES CD as and when requested
4. At the Partitioning stage we selected the EVMS proposal, and at the Software selection stage selected the base software, file server Role, Documentation, DHCP, eDirectory, iFolder, iPrint, Quickfinder, NSS and LDAP.
5. Miscellaneous errors would appear or not appear during the eDirectory stage (eg LUM error, or iFolder error) but the eDirectory stage would still seem to complete OK and get ticked.
6. The system would then reboot and appear to come up OK.
HOWEVER, we are not convinced we have created a fully working reliable server.
and
SPECIFICALLY we are unable to create NSS volumes and we cannot logon users via their eDirectory accounts.
NSSMU shows a single device sda (33.92 Gb) and three partitions sda1 (70Mb), sda2 (31.91GB), and sda3 (1.94GB). sda2 seems to contain all the 'spare' space on the disk (type Linux LVM) but says there is no spare space to create our NSS partitions.
iManager cannot see any devices to configure NSS data volumes on the SLES server but it connects OK
NSSCON status seems to show NSS to be running
EVMSGUI shows /dev/evms/lvm2/system/ro at 10 Gb, /dev/evms/lvm2/system/sw at 2GB and /dev/evms/sda1 at 70 Mb
So my questions are:
Does the above look right?
Why cannot we get at the spare disk space to set up NSS volumes? Did the EVMS proposal grab it all and if so how do we get it back?
Did not selecting the EVMS partitioning proposal do everything needed to run NSS?
[There seems to be some suggestion in the several hundred pages of SLES, OES and NSS Guides, Installation manuals, Configuration manuals etc that we have studied over several days, that we now have to edit a fstab file to make it work properly (Really? in this day and age where clicking on Setup.Exe will configure a fully working Windows server) Is that so? Is there anything else we need to do?]
How do we get the users to access their NDS accounts to log into SLES and Netware?
How do we know the server is OK for operaational use and 'works' ?
HELP!!!
ADB

alandbond wrote:
> I
> have already trawled the self help Forums believing that before SLES
> 11 came along everyone must have been setting up NSS volumes on SLES
> 10/OES2 as a matter of course as they moved from Netware and so me
> trying to do it now should not be akin to rocket science.
You are partially correct. Admins who used NSS on NetWare likely did
install NSS on OES Linux but I suspect they used a separate drive for
NSS either by installing an additional drive, by carving out a chunk of
space on their RAID array and assigning it to a separate LUN, or by
running OES in a VM where storage space on a single disk/array can
appear as separate drives.
> If Novell say in that guide as they do
> (just as do you and ab and Simon in responses to my post) that the
> IDEAL way to include NSS is to have a separate disk for Suse and NSS
> volumes, BUT as long as you use EVMS to manage the volumes it IS
> SUPPORTED, then I consider it should be possible without grief to do
> this and not considered as me putting round pegs in square holes.
Semantics!
IDEAL = Recommended; EVMS != IDEAL; EVMS != Recommended;
IMO, Novell recognised that they had to provide a way for customers to
install NSS on a system that only had a single disk and provided this
procedure as a workaround. By the way, they also support 2-node
clusters but they aren't recommended either. I have also seen cases
where a supported configuration was deemed no longer to be supported as
NTS became aware of additional complications.
My point (and Simon's and ab/Aaron's) is this: Just because it is
supported doesn't mean you should do it. If we can agree on this point,
I'll try to help you to get it working. The last thing I want to do is
give others the impression that by helping you find a solution we think
this is a good idea!!!
> This latest release of software even goes as far as including an EVMS
> Partitioning proposal which can be selected (as I did) within the
> clean install process.
>
> This is what it says:
Okay! I'm only looking at the information you provided. Let's analyse
it!
>
> A.2.1 Understanding the EVMSBased Partitioning Scheme
> Using EVMS to manage the system device allows you to later add NSS
> pools and volumes
Yes, NSS requires the volume manager to be EVMS and not LVM!
> on any *unpartitioned* free space on it.
But you have not left *any* unpartitioned free space!
> You must modify the partitioning scheme to use EVMS during the
> install. It is not possible to change the volume manager for the
> system device after the install.
True.
> Beginning in OES 2 SP3, the Partitioner in the YaST Install offers the
> Create EVMS Based Proposal option to automatically create an EVMS
> solution for the system device.
> For unpartitioned devices over 20 GB in size,
This is what you have...
> this option creates a boot partition
> and a container for the swap and / (root) volumes
> in up to the first 20 GB,
> and leaves the remainder of the space on the device
> as unpartitioned free space.
But it didn't (or you didn't)!
> Table A-1 shows the default proposed setup
> for a machine with 768 MB RAM.
> The default swap size is 1 GB or larger,
> depending on the size of the RAM on your machine.
> The remainder of the device is left as unpartitioned free space.
Let's look at the default proposal. This is *not* what you have.
> Table A-1 Default EVMS Proposal for Devices over 20 GB in Size
>
> Device Size Type Mount Point
> /dev/sda1 70.5 MB Ext2 /boot
> /dev/sda2 14.9 GB Linux LVM
> /dev/evms/lvm2/system 14.9 GB EVMS lvm2/system
> /dev/evms/lvm2/system/root 10.0 GB EVMS /
> /dev/evms/lvm2/system/swap 1.1 GB EVMS swap
A single (SATA/SAS/SCSI) drive will be known as sda (/dev/sda).
/dev/sda1 is the first partition. In the example and in your
configuration this is the /boot partition. In both cases it is 70.5 MB.
/dev/sda2 is the second partition. The partition uses LVM so logical
volumes of various sizes can be created within the partition. The total
size of all logical volumes cannot be larger than the size of the
partition.
In the above example:
/root is 10.0 GB and swap is 1.1 GB. This leaves: 14.9 - (10.0 + 1.1) =
3.8 GB of additional space within /sda2 which can be used to create
additional logical volumes. Furthermore sda1 + sda2 use only ~ 15 GB.
Only 15 GB of the disk has been allocated. The remainder of the disk is
*unallocated* and *unpartitioned*. Presumably, it was left that way so
that the space could be used for NSS.
In your case: sda2 is 31.91 GB
This does not follow the Default EVMS Proposal for Devices over 20 GB
in Size. Either YaST did not allocate space according to the default
proposal or you changed it. Either way, sda2 (+sda3) consume *all* of
the available disk space. It is no wonder that there is no space
available for NSS!
> What do you reckon???
I reckon that something went wrong along the way. If you did not
specifically change the default allocation yourself, then consider this
one example of kinds the things that can happen when one tries to
exploit seldom used, but supported, features!
It looks like it is time for yet another installation. This time, make
sure you leave enough unpartitioned space on the drive for NSS and let
me know how you make out.
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...

OES11 SP2 - Linux File System and NSS Pools & Volumes

Planning to install our first OES11 SP2 server into an existing tree - the
idea is to run this new OES11 server virtualized on VMware ESXi 5.5
The existing tree has two physical NW6.5SP8 servers running eDirectory
Version 8.7.3.10b (NDS Version 10554.64). One of the existing Netware
servers is used for DHCP/DNS, File Sharing from three NSS volumes and
Groupwise 7.0.4 whilst the second server is used for FTP services and
eDirectory redundancy. Ultimately the plan is to have two virtualized OES11
SP2 server with one for file sharing and the other for making the move from
GW7 to GW2012. And we're planning to stick with NSS for file sharing on the
new OES11 SP2 server.
I've come across a couple of posts for earlier versions of OES which
recommended not to put the Linux Native OS File System and NSS storage
pools/volumes on the same hard drive. Apparently the advice was a result of
needing to allow EVMS to manage the drive which could be problemmatic.
I've read the OES11 documentation which says that "The Enterprise Volume
Management System (EVMS) has been deprecated in SLES 11, and is also
deprecated in OES 11. Novell Linux Volume Manager (NLVM) replaces EVMS for
managing NetWare partitions under Novell Storage Services (NSS) pools."
So I'm wondering if there is still a compelling requirement to keep the
Linux Native File System and NSS pools/volumes on separate hard drives or
can they both now safely co-exist on the same drive without causing
headaches or gotchas for the future?
Neil

Hi Willem,
Many thanks for the further reply.
So we can just use the VMWare setup to "split" the one physical drive into
two virtual drives (one for the OS and the second for the pools).
And I've seen posts in other forums about the need for a decent battery
backed cache module for the P410i controller so I'll make sure we get one
(probably 512Mb module + battery).
Can I ask what is the advantage of configuring each VM's virtual disk to run
on it's own virtual SCSI adapter (by setting disk1 to scsi 0:0, disk2 to
scsi 1:0, and so on)?
Cheers,
Neil
>>> On 9/5/14 at 12:56, in message
<[email protected]>,
magic31<[email protected]> wrote:
> HI Niel,
>
> xyzl;2318555 Wrote: >
>> The new installation will run on a Proliant ML350 G6 with P410i>
> controller
>> so we can use the raid capability to create two different logical drives>
> as
>> suggested.
>
> As you will be using ESXi 5.5 as host OS, it's not needed to split
> thehost server storage into two logical drives... unless that's what
> youwant in perspective for "general performance" or redundancy reasons.
> Italso depends on the options that P410i controller has.
>
> On a side note, I'm not too familiar with the P410i controller... domake
> sure you have a decent battery backed cache module installed, asthat will
> greatly help with the disk performance bit.
> If the controller can handle it and the controller can handle it, go
> forraid 10 or raid 50. That might be too big a space penalty but will
> helpwith disk performance.
>
> Once you have your VMware server up and running, you can configure
> thetwo VM's with each two or more drives attached (on for the OS,
> thesecond or others for your pools).
> I usually create a virtual disk per pool+volume set (e.g. DATAPOOL
> &DATAVOLUME on one vm virtual disk, USERPOOL & USER volume on an other
> vmvirtual disk).
> With VMware you can than also configure each VM's virtual disk to run
> onit's own virtual SCSI adapter (bij setting disk1 to scsi 0:0, disk2
> toscsi 1:0, and so on).
>
>
> xyzl;2318555 Wrote: > Do you have any suggestions for the disk space that
> should be reserved> or
>> used for the Linux Native OS File System (/boot, /swap and LVM)?
>>
>
> Here's one thread that might be of interest (there are more
> throughoutthe SLES/OES
>
forums):https://forums.novell.com/showthread...rtitioning-%28
> moving-from-NW%29
>
> I still contently follow the method I choose for back in 2008, justwith
> a little bigger sizing which now is:
>
> On a virtual disk sized 39GB:
>
> primary partition 1: 500 MB /boot , fs type ext2
> primary partition 2: 12GB / (root), fs type ext3
> primary partition 3: 3 GB swap , type swap
>
> primary partition 4: LVM VG-SYSTEM (LVM partition type 8E), takes up
> therest of the disk **
> LVM volume (lv_var): 12 GB /var , fs type ext3
> LVM volume (lv_usr-install): 7GB /usr/install, fs type ext3
> * there's still a little space left in the LVM VG, in case var needs
> toquickly be enlarged
>
> One thing that's different in here vs what I used to do: I replaced
> the/tmp mountpoint with /usr/install
>
> In /usr/install, I place all relevant install files/IOS's
> andinstallation specifics (text files) for the server in question. Keeps
> itall in one neat place imo.
>
> Cheers,
> Willem-- Knowledge Partner (voluntary sysop)
> ---
> If you find a post helpful and are logged into the web interface,
> please show your appreciation and click on the star below it.
>
Thanks!---------------------------------------------------------------------
---magi
> c31's Profile: https://forums.novell.com/member.php?userid=2303View this
> thread: https://forums.novell.com/showthread.php?t=476852

Replace old server (NW5.1) instead of upgrading-migrating ?

I have a small, mixed environment. Currently, one tree, 3 servers: 1: NW6.5SP8/OES, 2 & 3 : NW5.1 SP8
In the near (-immediate) future, I'm upgrading the NW5x servers (definitely), and possibly later the NW6.5/OES server to OES11.
One of the NW5.1 servers is being replaced - I'm trying to use OES 11 ( from the SLES+OES overlay disk) .
I need -nothing- other than the server name/id and IP address of the old machine. No data, no users.
I've cleaned up the old server ( say #2) - removing all file partitions except SYS, and all users except Admins. Old stuff like print queues, etc as well, using C1.
New migration server is set up per Novell docs, as a migration target, on same subnet, in same tree. --also on brand new hardware.
The migration tool ( set to migrate server ID) hangs on checking eDir; (not exact) ' source server is using eDir 8, which is not supported. Migration project will now terminate.'
Can I ( easily) remove the old server from my tree, and just install the OES11 server with the same name & IP address?
What can I do to avoid confusing/corrupting the eDir replica ring while I do this?
Or - as I suspect I will need to do for the other old NW5.1 ( #3)... do I need to make incremental upgrades - say to NW6.5SP8 first ?
On that server, I will need to preserve users, groups, and file systems when I move it to the new hardware 'home'.
Thankfully, the only uses on these two old boxen are file access and user authentication.
for detail;
Server #1, NW6.5 SP8 / OES (master replica): server version: 5.70.08, eDir 8.7.3.10 SMP, NDS 10554.34, DS.nlm 10554.34, DSRepair 10551.81
Server #2, NW5.1 SP8, (moving name/id only to new hardware): currently server 5.00.11, eDir ( * 8.7.3.4), NDS 8.85c, DS.nlm 8.85c, DSRepair 10550.86
Server #3, NW5.1 SP8 (planning move of all users & file systems): server 5.00.11, eDir ( * 8.6.2.6), NDS 8.85c, DS.nlm 8.85c, DSRepair 10250.42
* eDir versions not directly given in DSRepair tool, instead I used TID Support | Table of eDirectory versions , and the stated version of DSRepair.
Both servers #2 and #3 are old and ornery; I treat #3 like an old, nasty cat - and only give it _careful_ attention when needed.
For now, please let me know what shortcuts / - pro/con about just killing the old server #2 and replacing it with a brand new hardware-software clean slate?
I'll ask for more help ( or pay a consultant if needed) when that time comes for the others.
Thanks for reading, and for any advice.

On Fri, 22 Nov 2013 20:06:02 +0000, billhilger wrote:
> The migration tool ( set to migrate server ID) hangs on checking eDir;
> (not exact) ' source server is using eDir 8, which is not supported.
Worse, it's NW5, so you can't talk to it with IP, and your destination
server can't do IPX.
> Migration project will now terminate.' Can I ( easily) remove the old
> server from my tree, and just install the OES11 server with the same
> name & IP address?
I think that's really all you *can* do at this point.
> What can I do to avoid confusing/corrupting the eDir
> replica ring while I do this?
Remove the old server. Install the new one.
> Or - as I suspect I will need to do for the other old NW5.1 ( #3)... do
> I need to make incremental upgrades - say to NW6.5SP8 first ? On that
> server, I will need to preserve users, groups, and file systems when I
> move it to the new hardware 'home'.
Users and Groups are in eDirectory, so they'll be "preserved" by the fact
that you're not replacing the tree.
File systems - oy. You're probably also going from TFS to NSS here.
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com
Please post questions in the forums. No support provided via email.
If you find this post helpful, please click on the star below.

OES2SP3 to OES11SP1 nss volumes on iscsi target, hints?

Dear Colleagues,
I'm looking for a best migration scenario for the following assumtions:
One of SLES10SP3/OES2SP3 servers in my tree has file services and kanaka on it. Its nss volumes are located on iscsi targets attached from a Qnap storage. I'm migrating this server to a new hardware and SLES11/OES11SP1 and would like to transfer/switch volumes the easiest possible way. There is +/- 8TB of data to copy and I'm looking for a way around copynig it. Is it possible to perform the migration to newest SLES/OES on a different hardware and just re-attach iscsi target containing nss volumes, so all would stay consistent in the tree?
Please advise...

[QUOTE=mrosen;2266934]Hi.
On 06.06.2013 12:06, mpytel wrote:
> Is it possible to perform the migration to newest
> SLES/OES on a different hardware and just re-attach iscsi target
> containing nss volumes, so all would stay consistent in the tree?
Absolutely! You do a regular transfer ID migration, *without* copying
the NSS data that is on the iSCSI device. After the migration, bring up
the new server, attach to iSCSI, go into NSSMU and activate/mount the
partition once, and you're all set.
Dear Massimo,
I just finished TransferID migration and successfully re-attached iscsi targets containing NSS to the new server.
Is there an additional step I should execute to 're-read' volumes/pools contents so they appear on the new server?
M

Time issue seems odd to me

I put a secondary domain and po at a remote location - running 8.03 on Sles/Oes and moved all of the "local" users to that po.
while everything seems to run ok we have a weird time issue.
Mail into and out of the new mailboxes shows a three and a half hour time difference both in the date column in the groupwise client and in the printed header of the email.
The odd thing is that if I go to the properties of the email - the Creation date and the File date and time are both correct.
I can't see any time issues with the servers (primary or secondary) and especially something that would be 3:30 minutes off
there is a timezone difference between the pri and sec but that's just 1 hour.
Any thoughts?
As a workaround I have had my users add the creation column to see when they actually received the email as our clients have time critical projects.
Thanks
Dennis

Danita,
Thanks for the reply - Oh how I wish it were that easy - I've checked and double checked the PO object and the domain object - both say US eastern time.
If I send email from a mailbox on the secondary to the primary - everything is correct (a 1 hour time difference - Eastern to Central)
If I send mail from a mailbox on the primary to the secondary - it shows up right away, but says 3:30 minutes later than it should (in Date/Time, but not in Created)
If I send email from a mailbox on the secondary to a GMail account - the header shows the 3:30 offset, but the properties of the mail shows correctly.
I would be happy to send email from that po to anyone that wants to see for themselves.
Other than the PO Object and the DOM object - Where should I be looking for a time difference
and how would it be getting UTC minus 30 minutes - - Is there a special timezone out there for Hy Brasil?
The workstations all get their time settings from "time.windows.com" the windows default.
Thanks for looking into this - I just hope that I can get it figured out because as small of an issue that I think it is (they get their email, it just looks like it gets read before they officially receive it)
but it seems that this office uses the received time to track how long it takes them to do their work.
Dennis

MAC os X SnowLeopard and Lion integration with edir

Hi,
I have been reading a bit on the subject as my MAC server is nearing it's end of life and I still have an OES 2 server in use (old OES sp1).
Does someone know what is in plans for MAC users regarding ease of use when logging in to a SLES/OES system in the future?
OES3 and Filr seems intresting, but will there be any help in the MAC integration?
Currently have a SBS 5 user license but don't want to deploy it until it's easier to manage/use with macs
Running SLES11+Groupwise8 on my MAC server virtually and it's a perfect combination.
Thinkin about virtualizing the new SBS when it's launched - any news on that?
I know Simon Flood is a specialist in this area with MACs - have you any insight?
Sincerely,
DB

Originally Posted by smflood
On 27/10/2011 08:06, dominicus wrote:
> I have been reading a bit on the subject as my MAC server is nearing
> it's end of life and I still have an OES 2 server in use (old OES sp1).
Not sure what you mean by "OES 2 server in use (old OES sp1)", an OES2
server that was upgraded from original OES[v1] SP2 perhaps? OES2 SP3
(on SLES10 SP4) is latest available version and has (or will have once
the next Scheduled Maintenance patch comes out) improved AFP support for
Mac OS X Lion.
Yes an OES2 sp1 server and have not had the need to update.
Want to do a fresh install when it's easier to implement in a all MAC enviroment
> Does someone know what is in plans for MAC users regarding ease of use
> when logging in to a SLES/OES system in the future?
Whilst I'd like to see Novell implement something in OES to make Mac
integration easier (I and others have had conversations) there's nothing
currently planned.
Too bad. Do you recommend a third party product for that?
> OES3 and Filr seems intresting, but will there be any help in the MAC
> integration?
There is no OES3, OES11 is the next version.
OES11 will include support for DHX2 in the AFP protocol implementation
so there will be no need to configure each Mac client to use DHX[v1]
(this fix is also being backported to OES2 SP3 hence the earlier
reference to next OES2 SP3 Scheduled Maintenance patch). Other than
that it's the same as with OES2.
Filr is very interesting but doesn't help with Mac integration. There
will be an iOS client for iDevices but as it currently stands a Mac
client will follow in "version 2". Personally I'd like to see a Mac
client with version 1 but I'm assured Mac users will still be able to
use Filr.
> Currently have a SBS 5 user license but don't want to deploy it until
> it's easier to manage/use with macs
SBS? Are you referring to Microsoft's or Novell's small business
solution? Hopefully the latter and you mean NOWS SBE perhaps?
Yes Nows SBE, sorry for the confusion
> Running SLES11+Groupwise8 on my MAC server virtually and it's a perfect
> combination.
> Thinkin about virtualizing the new SBS when it's launched - any news on
> that?
Which virtualisation product are you using on your Mac server
(presumably an Xserve)? Whilst I know it can be done I'm not aware of
anyone who is virtualising Novell solutions on an Apple server but then
I don't get out much! ;-)
I'm currently using the VMware Fusion desktop product and it has been working flawless since the start
one year ago.
Running all on a MAC mini server edition with 8GB ram and all data stored on a NAS attached to my mac via firewire.
For a small office with only 5 users this has proven to be a sufficient.
> I know Simon Flood is a specialist in this area with MACs - have you
> any insight?
I'm still around. Hopefully the above answers some questions but
unfortunately asks more!
In the end I guess it all depends on what you want to achieve. Can you
have a user logging into a Mac authenticating against OES with the
user's home directory on an OES server. Yes sure and there is more than
one way to do it though the problem is support by Novell but we're
working on that!
Thanks for your reply. I'll work slowly on this and if I have any questions I'll post back or start a new conversation.
HTH.
Simon
Novell Knowledge Partner (NKP)
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partner (TTP) program. See novell.com/ttp for more details.

Install Issue

I have a MacBook Pro and I attempted to install Leopard onto it this past week. In the middle of the process, an error occured and it required me to restart the installation process. Once i restarted it, the installation program required me to format my hard drive because tiger was erased already and leopard was not installed yet. Granted, I have backups of all my files, but this was still extremely time consuming. The installation again errored out the second time i tried, but finally on the third try, it worked! It made it a very big hassle losing all my programs and all the preferences and settings i had before. Besides this huge glitch, leopard has been running great and i have all my programs reinstalled! Leopard runs great and i have not had any further problems with it!
When upgrading to Leopard make sure to backup important files!!!

On 28/08/2014 14:45, Stevo wrote:
> They are sles11sp3 / oes11sp2. Is that a feature of sles11sp3 where
> they talk back to nu.novell.com to install any software?
Not a feature as such but installing GroupWise on SLES/OES involves
using zypper to install various (GroupWise) packages. The first thing
zypper does is refresh it's cache of repositories and it's that which I
think is your nu.novell.com activity.
If you don't have a local SMT server available that you can point your
test servers at, one option might be to disable the regular SLES/OES
repos before running the GroupWise install and then re-enable them
afterwards. You can use "zypper lr -u" to list all subscribed repos,
then "zypper mr -d #" (when # is the number of the repos from "zypper lr
-u") to disable with "zypper mr -e #" to re-enable.
Note that I've not tested this myself and it's probably best to make
sure that you've fully patched your server first before disabling repos
and installing GroupWise.
HTH.
Simon
Novell Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

Apache

Hello everybody
I installed oracle 8i release 3 (8.1.7) on HP 9000 server os is Hp-ux 11.0 64 bit. in the database side everything is ok.
The problem is Apache server when its try to start web server the following error is happening.
Starting webserver in non SSL mode on port 7777 failed (see details)
Syntax error on line 14 of /oracle_home/Apache/Apache/conf/mod__ssl.conf...............
Finally the apachectl unable to start
How to solve this problem
Michael
null

Sarsippius,
> I am having some trouble finding out what version of Apache is current
> for Netware. I am currently running NW 6.5 SP 7 or 8.
>
> Right now the Apache version running is 2.0.59
>
> Is there a newer version for NW 6.5 and is there a document that shows
> how to install it?
http://httpd.apache.org/download.cgi#apache22
But, please be advised that most 6.5 supplied web stuff will not run
with this version, so if you intend to run it, keep the original apache
stuff and loadf this new version as a separate instance.
In the long run though, you might want to look at SLES/OES.
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)
Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

Tomcat running high utilization on OES11 SP2

I have Groupwise 2014 with webaccess and calendar publishing host installed on the same OES 11 SP2 in virtual environment. Tomcat is slowly eating up available CPUs until the system becomes unstable. Rcnovell-tomcat6 restart will temporarily clear the problem. The problem is described in TID 7010072 however, the document specifically says that the fix is not for OES11. Does anyone know how to address this on OES11?

Originally Posted by smflood
On 08/07/2014 20:46, bobodajdaj wrote:
> I have Groupwise 2014 with webaccess and calendar publishing host
> installed on the same OES 11 SP2 in virtual environment. Tomcat is
> slowly eating up available CPUs until the system becomes unstable.
> Rcnovell-tomcat6 restart will temporarily clear the problem. The problem
> is described in TID 7010072 however, the document specifically says that
> the fix is not for OES11. Does anyone know how to address this on OES11?
Firstly I'm not aware of an equivalent TID specific to OES11 so I'll ask
my Novell contacts.
OES11 uses novell-tomcat6 rather than tomcat6 as used with SLES11 with
configuration file at /etc/opt/novell/tomcat6/conf/novell-tomcat6.conf
so in the meantime perhaps make the same change as noted in TID 7010072
for SLES11 to the OES11 file.
Note there is more than one line (re)defining CATALINA_OPTS so I'd be
tempted to add the following line below the last CATALINA_OPTS line:
CATALINA_OPTS="$CATALINA_OPTS -Xthr:minimizeUserCPU -Xms800m -Xmx900m"
Restart the OES11 tomcat process via "rcnovell-tomcat6 restart".
HTH.
Simon
Novell Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
We are experiencing the same issue on our OES GroupWise 2014 server. Restarting novell-tomcat6 fixes temporarily, but always returns. Anyone find anything further with this? Just downloaded (1/12/15) and installed latest available hotpatches for GW2014 and SLES/OES, but did not resolve issue.

DHCP and failover issues

Hello,
I am trying to implement failover in our dhcp but I don't get it right....
I have 2 SLES/OES servers both can be used as DHCP server without failover (one active, the other not).
server 1 => SLES11SP1 with OES11 (dhcp version is 3.1.3 ESV)
server 2 => SLES11SP2 with OES11SP1 (dhcp version is 4.2.4-P2)
I have defined my failover dhcp services following TID 7004294, so I have defined to services (ip_serv1 and ip_serv2), each failover service does contain:
a) failover object ( FO2SERV2, FO2SERV1), where
Primary server is 10.7.0.248 10.7.0.248
Primary port is 647 847
Secondary server is 10.7.0.250 10.7.0.250
Secondary port is 847 647
Failover split is 128 128
Max. Client Lead Time 3600 3600
b) subnet 10.11.0.0 10.11.0.0 where these subnets have following pool
c) pool pool_10_11 pool_10_11 and these have the following failover attached to
FO2SERV2 FO2SERV1
I think that these parameter follow precisly the TID 7004294, but when I start the dhcpd services on the primary server I get the following messages:
I move from recover to startup
I move from startup to recover
DHCPDISCOVER from 00:23:24:07:84:53 (REFERENCE) via XXX.XXX.XXX.XXX: not responding (recovering)
and indeed I do not get any lease.
What am I doing wrong????
Any suggestions?
Thanks in advance

Originally Posted by ricard1
Finally I got it!!.
First I upgraded one of my servers to same release level as the second
Then I defined the Failover Objects with the same name as you suggested and using the same port (in my case 847).
That did the trick.
Thanks!
PS. it is a shame that some TID's are so wrong as this one (TID7004294).
Please provide TID feedback on the bottom of the page: https://www.novell.com/support/kb/doc.php?id=7004294
Thomas

SLES/OES Partitioning

Similar Messages

Maybe you are looking for