c l113

Novell® Open Enterprise Server 2 on Linux:Installation and Migration for Absolute Beginners

Marcus GouldPremium Support Engineermgould@novell.com

Introduction

Agenda

• Install a new Novell® Open Enterprise Server 2 Linux Server Into An Existing Tree

• Migrate from OES NetWare® to OES Linux

• Compare and Contrast

• Learn new things

What To Expect

• An introduction

• A quick march up the learning curve

• Overcome the fear of the unknown

• Lots of new information

• Building on what you already know

...Give you the knowledge and confidence to grabthe DVDs and build your first OES2 server...

What Not To Expect

• A month of Advanced Technical Training in two hours

• Lots of depth

• Answers to everything– No NCS, DNS, DHCP, AFP, CIFS, DSfW, DST, SMS, SLP, NSM,

NFR, NAM, FTP, iSCSI, NTP, ZAM, ZDM, ZPM, ZSM, ZCM, NetStorage, iFolder, Apache, Tomcat, GroupWise, BorderManager or Sentinel!

Recursion!

• My computer dictionary says– Recursion /rikursh’n/noun-- See recursion.

• We'll look at it later!

Demonstration Lab Setup

Current Tree

• London– NetWare® 6.5 SP8– DNS and DHCP– FTP installation source

Current Tree

• Manchester– NetWare® 6.5 SP8– DATAVOL: with some test data– iPrint Broker

Printer drivers– Print Manager

Test printer

• New Server– Unformatted machine - two disks

Demonstration

Summary of an Installation and Migration

8GbLondon

192.168.100.10SYS:

M [Root]

8Gb8GbLondon

192.168.100.10Manchester192.168.100.20

DATAVOL:

Broker

NDPSM RW [Root]

Man_NDPSM

Man_HPJL4

Man_Broker

Drivers

M [Root]

8Gb8GbLondon

192.168.100.10Manchester192.168.100.20

SLES10 SP3OES2 SP2

DATAVOL:

Broker

NDPSM RW [Root]

Man_NDPSM

Man_HPJL4

Man_Broker

Drivers

Copy install media to London

M [Root]

8Gb8GbLondon

192.168.100.10Manchester192.168.100.20

DATAVOL:

Broker

NDPSM RW [Root]

Man_NDPSM

Man_HPJL4

Man_Broker

Drivers

Make files available via FTP

M [Root]

8Gb8GbLondon

192.168.100.10Manchester192.168.100.20

DATAVOL:

Broker

NDPSM RW [Root]

Man_NDPSM

Man_HPJL4

Man_Broker

Drivers

temp192.168.100.30Boot from SLES10 SP3

M [Root]

8Gb8GbLondon

192.168.100.10Manchester192.168.100.20

DATAVOL:

Broker

NDPSM RW [Root]

Man_NDPSM

Man_HPJL4

Man_Broker

Drivers

temp192.168.100.30Build temp using London as source

M [Root]

8Gb8GbLondon

192.168.100.10Manchester192.168.100.20

DATAVOL:

Broker

NDPSM RW [Root]

Man_NDPSM

Man_HPJL4

Man_Broker

Drivers

temp192.168.100.30

Print Manager

Driver Store

Ensure pre-migration server, NCP™, NSS, iPrint and iManager are selected – other needed components will be selected automatically

M [Root]

8Gb8GbLondon

192.168.100.10Manchester192.168.100.20

DATAVOL:

Broker

NDPSM RW [Root]

Man_NDPSM

Man_HPJL4

Man_Broker

Drivers

temp192.168.100.30

Print Manager

Driver Store

Configure NSS and create new volume

M [Root]

DATAVOL:

8Gb8GbLondon

192.168.100.10Manchester192.168.100.20

DATAVOL:

Broker

NDPSM RW [Root]

Man_NDPSM

Man_HPJL4

Man_Broker

Drivers

/Man_Print_Manager

Man_Driver_Store

temp192.168.100.30

Print Manager

Driver Store

Configure iPrint – create new Driver Store and Print Manager

M [Root]

DATAVOL:

8Gb8GbLondon

192.168.100.10Manchester192.168.100.20

DATAVOL:

Broker

NDPSM RW [Root]

Man_NDPSM

Man_HPJL4

Man_Broker

Drivers

DATAVOL:

/Man_Print_Manager

Man_Driver_Store

temp192.168.100.30

Print Manager

Driver Store

Run miggui to migrate

miggui

M [Root]

8Gb8GbLondon

192.168.100.10Manchester192.168.100.20

DATAVOL:

Broker

NDPSM RW [Root]

Man_NDPSM

Man_HPJL4

Man_Broker

Drivers

DATAVOL:

/Man_Print_Manager

Man_Driver_Store

temp192.168.100.30

Print Manager

Driver Store

Run miggui to migrate Files

miggui

M [Root]

8Gb8GbLondon

192.168.100.10Manchester192.168.100.20

DATAVOL:

Broker

NDPSM RW [Root]

Man_NDPSM

Man_HPJL4

Man_Broker

Drivers

DATAVOL:

/Man_Print_Manager

Man_Driver_Store

Man_HPJL4Driverstemp192.168.100.30

Print Manager

Driver Store

Run miggui to migrate Files Broker, Manager, Drivers and Printers

miggui

M [Root]

8Gb8GbLondon

192.168.100.10Manchester192.168.100.20

DATAVOL:

Broker

NDPSM RW [Root]

Man_NDPSM

Man_HPJL4

Man_Broker

Drivers

DATAVOL:

/RW [Root]

Man_Print_Manager

Man_Driver_Store

Man_HPJL4Driverstemp192.168.100.30

Print Manager

Driver Store

Run miggui to migrate Files Broker, Manager, Drivers and Printers eDirectory Database, including replicas

miggui

M [Root]

8Gb8GbLondon

192.168.100.10Manchester192.168.100.20

DATAVOL:

Broker

NDPSM RW [Root]

Man_NDPSM

Man_HPJL4

Man_Broker

Drivers

DATAVOL:

/RW [Root]

Man_Print_Manager

Man_Driver_Store

Man_HPJL4DriversManchester192.168.100.20

Print Manager

Driver Store

Run miggui to migrate Files Broker, Manager, Drivers and Printers eDirectory Database, including replicas Identity – Name, Address, NICI keys, and certificates

miggui

M [Root]

8Gb8GbLondon

192.168.100.10Manchester192.168.100.20

DATAVOL:

Broker

NDPSM RW [Root]

Man_NDPSM

Man_HPJL4

Man_Broker

Drivers

DATAVOL:

/RW [Root]

Man_Print_Manager

Man_Driver_Store

Print Manager

Driver Store

Decommission old server

M [Root]

10Gb8GbLondon

192.168.100.10SYS:

DATAVOL:

/RW [Root]

Man_Print_Manager

Man_Driver_Store

Print Manager

Driver Store

Clean up and test new server

M [Root]

10Gb8GbLondon

192.168.100.10SYS:

DATAVOL:

/RW [Root]

Man_Print_Manager

Man_Driver_Store

Print Manager

Driver Store

M [Root]

Summary of an Installation and Migration – Start Point

Summary of an Installation and Migration – Temp OES Server Added

Summary of an Installation and Migration – Migration Complete

Live Demo

• Let's go...

Linux Overview

Background

• First version in 1991

• Linux is technically just the kernel– Requires the GNU utilities– Hence the full name GNU/Linux

What Do You Mean, Free?

• No restrictions: libre

• Costs no money: gratis

• General Public License (GPL)– Four Freedoms: Use, Study, Redistribute, Change– Changes and improvements must remain free (unlike BSD

licence)

• Open Source software is free but can still be charged for

– e.g.SUSE® Linux Enterprise Server, Red Hat, etc

openSUSE® and SUSE® Linux Enterprise• openSUSE

– Open Source project sponsored by Novell®

– Developed by Novell and the community– Free (gratis), free (libre) and unsupported by Novell– At the leading edge– Once openSUSE has matured and stabilised...

• SUSE Linux Enterprise (SLE)– Commercial release– Paid for by subscription and supported by Novell– Some proprietary extras

SUSE® Linux Enterprise Server Platform Support• x86

• x86_64 (AMD64 and Intel EM64T)

• IA64 (Itanium 2)

• IBM POWER

• IBM System z (64-bit)

OES Overview

Background

• SUSE® Linux running NetWare® services– ...And some new ones

• Proprietary, not free

• Looks just like NetWare to users

• OES1 released in March 2005

• OES2 released October 2007

Platform Support

• x86

• x86_64 (AMD64 and Intel EM64T)

Version Control

• Cannot mix and match– OES2 SP1 requires SLES10 SP2– OES2 SP2 requires SLES10 SP3– ...etc

Problems, Problems, Problems

The Biggest Problem With Linux is...?

• Choice!

• Which one is better?

• Which one is right?

• Which one would Novell® recommend?

• Which one do you like best?

...If you ask ten people, how many different answers do you think you will get?

Is NetWare® Any Better?

GNOME Desktop

• GNU Network Object Model Environment

• Focus on usability and simplicity

• Default desktop with SLES and OES

• Runs on X Windows

KDE Desktop

• K Desktop Environment

• Feature-rich

• Can be installedinstead of GNOME(or as well as)

• Runs on X Windows

File Systems: ReiserFS

• Advantages– Simple, quick, stable– Good performance and recovery– Efficient disk usage– Best with many small files

• Disadvantages– Only supports metadata journalling– Repair tools not very robust– Not so good with large files

File Systems: EXT3

• Advantages– Quick, stable– Handles large files well– Supports metadata journalling and data writes

• Disadvantages– Does not scale well to large volumes– Does not scale well to many (>500 per directory) small files

File Systems: NSS

• Advantages– Very rich metadata (rights model)– Salvage, compression, shredding, snapshots, user quotas

• Disadvantages– So many features may present an overhead

The Basics

Scalability and Resilience

• OES NetWare®

– 32 Bit - 4 Gb address space– Most code executes in Ring 0– Some code executes in protected memory

• OES Linux– 32 Bit - 4 Gb address space– 64 Bit - Huge address space– Most code executes in protected memory– Some code executes in Ring 0

• OES NetWare®

– NetWare Loadable Module (NLM)– Both programs and libraries are modules– .NCF Scripts (also .BAS, etc)

• OES Linux– Binary Executables (no extension)– Shared Libraries (.so)– .sh scripts (also, .py, etc)

File Extensions

• A DOS/Windows thing– Extensions mean something to the Operating System

• Not widely used in Linux– A document called mytext.doc could be a spreadsheet

• A lot of conventions exist– e.g. .sh for shell script– e.g. .py for Python script– ...But you still don't need them

Just in Case

• Linux is case sensitive– cd /home/syd/music will workCD /home/syd/music will fail

– /home/syd/ and /home/SYD are different

• Everything!– File/Pathnames, commands, scripts...– ...Switches and parameters can mean different things

depending on their case

• If a command doesn't go according to plan– Check, check and then check again

• DOS, Windows and NetWare®

– Back slash: \ or Forward slash: /– e.g.edit sys:\etc\hosts

edit sys:/etc/hosts

• Linux– Forward slash only: /– e.g.edit /etc/hosts

• Novell® eDirectory™ on Windows and NetWare®

– NDAP format with dots:– e.g.cn=Syd.ou=Darkside.O=TheMoon

• eDirectory on Linux– LDAP format with commas:– e.g.cn=Syd,ou=Darkside,O=TheMoon

• There may be inconsistencies– If it doesn't work, try the other way!

Who's The Daddy?

• OES has two all-powerful superusers:– Linux: root– eDirectory: Admin

• Use sudo to run a single command as root

• Use su (or su -) to switch to root

• Do not login as a superuser for day-to-day activities

• Do not bring bad habits with you!

Logging In

• Console

• ssh

Who Knows Who is Who?

sudo -Elevated Privileges by Proxy

Moving Around

• 8 default consoles (tty)

• Switch Screens– Text Consoles: <CTRL><ALT><F1> ... <F6>

– Graphical Console: <CTRL><ALT><F7>

– Error Messages: <CTRL><ALT><F10>

The Big Differences

Disk Naming

• Controller– SCSI: sdx– IDE: hdx

• Disks– a, b, c, etc– e.g. sda, sdb, hda, etc

• Partitions– 1, 2, 3, etc– e.g. sda1, sda2, sdb1, etc

sda sda1

sdb sdb1

Disk Naming

Where is Everything?

• System directories/ (The root directory)/bin /boot/dev /etc/home /initrd/lib /lost+found/media /mnt/opt /proc/root /sbin/usr /var/srv /tmp

• http://www.tldp.org/LDP/Linux-Filesystem-Hierarchy/html/index.html

Mount Points

• Any directory can be a mount point– Another device; e.g. hard disk, iPod, USB, etc– Remote network; e.g. CIFS, NFS, etc– Comparable to Distributed File System (DFS) on NSS

• e.g. mount /dev/sdc1 /mnt

• / (root) is comparable to SYS: on NetWare®

– Keep it on its own disk, just like SYS: on NetWare

Mount Points

sda3 /home

Mount Points

sda3 /home

sdb1 /media/disk

Mount Points

sda3 /home

sdb1 /media/disk

sdc2 /media/TMARCUST

Mount Points

Everything in the File System

• /dev

– Maps devices to files

• /proc

– Similar to the NetWare® virtual _admin: volume– e.g.cat /proc/diskstats

cat /proc/meminfo

Up and Down

• Runlevels– init 0 aka shutdown– init 1 Single user, no network, no services– init 2 Multiuser, network, no services– init 3 Multiuser, network, services– init 4 Not used/user defined– init 5 Multiuser, network, services, X Windows– init 6 aka reboot

• Server usually runs in runlevel 3 or 5

Start and Stop

• /etc/init.d/<service name> start|stop|status|...– Just text files – have a look! (use cat or more)– e.g./etc/init.d/tomcat5 stop

• service <service name> start|stop|status|...– Borrowed from RedHat– e.g.service tomcat5 start

• rc<service name> start|stop|status|...– SUSE-Specific– e.g.rctomcat5 status

Error Logs

• Main logs– /var/log/messages– /var/log/boot.msg

• Program-specific– /var/log/*– e.g. /var/log/apache2/error_log

• Other– Refer to the documentation– e.g. /var/opt/novell/log/*

Configuration Files

• Main configuration files– /etc/* and subdirectories– e.g. /etc/ntp.conf

/etc/iscsi/iscsid.conf/etc/opt/novell/ncp/ncpserv.audit.conf

• Application-specific– Refer to documentation– e.g. /var/opt/novell/ncs

• NetWare® – eDirectory™

– Hierarchical– Distributed– Encrypted Database

• Linux – Password Repository– Flat– Server-centric– Text file with encrypted entries (/etc/shadow or /etc/passwd)

• Integrate using LUM (more on that later)

NSS File Rights and Permissions

• NetWare® Rights– SRWCEMFA– Assigned to users, groups and containers– rights.exe, etc

• NetWare Attributes– AciDcDiDmHIcNPRiRoRwShSyTX– Assigned to files and directories– flag.exe, etc

Linux File Rights and Permissions

• Linux Rights– RWX– Assigned to a user, a group and everyone– chmod– e.g.chmod 644 diamond.txt

• Linux ACLs– setfacl, getfacl– Not really needed in an OES context

Permissions and Ownership

• -rw-r--r-- 1 mgould users 21 2010-02-03 14:10 diamond.txt

r w x r w x r w x

Owner Group Others

4 2 1 4 2 1 4 2 1

r w x r w x r w x

Owner Group Others

4 2 1 4 2 1 4 2 1

r w x r w x r w x

• e.g. chmod 644 diamond.txt

Owner Group Others

4 2 1 4 2 1 4 2 1

r w x r w x r w x

mgould users Everyone Else

File Ownership

• NetWare®/NSS owner (aka creator)– iManager

• Linux owner– chown

e.g.chown mgould diamond.txt– chgrp

e.g.chgrp users diamond.txt

Running Scripts and Executables

• Explicit path– e.g./sbin/myapp

• Relative path– e.g../myscript.sh– myscript.sh on its own won't work

• Check execute and owner– e.g.Can Syd execute this?-rwxrw-r-- 1 mgould users 98 2010-02-03 14:12 crazy.sh

File Formats

• Carriage Returns and Line Feeds– Do not use DOS/Windows editors– Handled differently– dos2unix

• Check with a hex editor– e.g.okteta

Not Part of OES Linux

• IPX

• Traditional Volumes

• Timesync

• iFolder 2

OES Services

eDirectory™

• ndsd daemon– List instances: ndsmanage

– DSRepair: ndsrepair

– DSTrace: ndstrace

• Default directories– Dibset: /var/opt/novell/eDirectory/data/dib– Binaries: /opt/novell/eDirectory/– Config: /etc/opt/novell/eDirectory/conf/nds.conf– Logs: /var/opt/novell/eDirectory/log/

Novell® Storage Services (NSS)• novell-nss kernel module

– Also ncp2nss– NSSMU: nssmu

– NSS Console: nsscon

• Mounted in Linux– /media/nss/<Volume_Name>

• Default directories– Binaries: /opt/novell/nss– Config: /etc/opt/novell/nss/nssstart.cfg

/etc/opt/novell/ncp2nss.conf– Logs: /var/opt/novell/log/ncp2nss.log

Novell® Core Protocol (NCP™)

• Runs as part of eDirectory™ (ndsd)– 'MONITOR': ncptop

– NCP Console: ncpcon

• Default directories– Binaries: /opt/novell/ncpserv– Config: /etc/opt/novell/ncpserv.conf– Logs: /var/opt/novell/log/ncpserv.log

Novell® Core Protocol (NCP™)

• Make Linux volumes available via NCP– ncpcon:create volume <NCP Vol> <Linux Dir>– e.g.create volume ncpdata /data/stuff– NoRM

• Why use NSS, then?– Scalability limited to underlying file system– Lacks NSS features like salvage, compression, shredding, etc

Linux User Management (LUM)

• Allows local Linux users to be managed via, and interface with, eDirectory™

• Optional but required by iPrint, NSS, etc– e.g.To see correct owner, modifier, deleter and archiver of a file

• Administration via iManager and YaST

• The defaults will work for this demonstration

Compatibility

• Many Legacy tools should still work

• ...But not necessarily supported!– DOS command-line Tools– DOS C-Worthy Tools– Windows Tools– NWAdmin– ConsoleOne®

Things You Weren't Expecting to See

Your in-house toolsmay require little

or no modification

Use at your own risk!

Your in-house toolsmay require little

or no modification

Linux Tools and Commands

• Read The Free Manuals

• All commands should have a man page

• Man pages– man <command>

– e.g.man ndsrepair– http://www.linuxmanpages.com/

More Free Information

• Info pages– info <command>

– e.g.info cp

• Many commands have an info page

Yet Another Setup Tool - YaST

• Similar to Windows Control Panel

• Easy to use

• Hides command lines, parameters and complexity

• Configure all aspects of SLES and OES

• GUI or text versions

• ...If in doubt how to configure the system, check YaST!

Handy Commands

• Don't forget: man <command>

• Navigating directories– mkdir (md), chdir (cd), rmdir (rd)– ls (dir) best used with -la parameter

i.e. ls -la

• Manipulating files– cat

– tail

– vi (edit)

Handy Commands

• Don't forget: man <command>

• Manipulating files– cp

– mv

– rm

Handy Commands

• Watching processes– top

– kill <PID> (or kill -9 <PID> if it just won't die)– ps (try ps -eaf)

• Manipulating disks– mount

– fdisk (try fdisk -l)– fsck

OES Tools and Commands

Handy Tools

• Server-based tools– You must be the root user to use these tools– NCP™: ncptop, ncpcon– NSS: nsscon, nssmu, ravsui– Trustees & attribs: rights, attrib, metamig– eDirectory™: ndstrace, ndsrepair

• Browser-based tools– You must have sufficient eDirectory rights to use these tools– iMonitor, iManager, NoRM

ncptop

ncpcon

nsscon

ravsui

rights

attrib

metamig

ndstrace

ndsrepair

Novell Remote Manager (NoRM)

iManager

iMonitor

Migration Utility

Types of Migration

• Consolidate– Reorganise resources

e.g.File, print, AFP, CIFS, DHCP, iFolder, etc– One-to-one or many-to-one– Same tree or different tree (not CIFS, AFP)

• Transfer ID– Transfer server identity from source to target– Includes name, IP address, eDirectory™ replicas, NICI keys,

certificates, etc– Same tree only

The Migration Tool Utility

• Check the documentation– Print this:http://www.novell.com/documentation/oes2/pdfdoc/mig_tools_lx/mig_tools_lx.pdf

• Check the prerequisites– Consolidation: Page 51 Transfer ID: Page 59

• Do a test run– Then do another test run– Ensure you have a good backup before doing it for real

miggui - The Migration Tool Utility

Troubleshooting

Find the Error Message

• Check the logs– There are lots of logs

• Check the case and syntax– Then check again

• Check permissions and ownership– Is it executable? Do you have permission to execute it?

• Don't abandon what you already know– Comms, eDirectory™, DNS, naming, location

Odds and Ends

Phrase Book

Linux NetWare®

Bonding NIC TeamingCore AbendFlash BIOSHW addr/burnt-in addr MAC addressIPL (Initial Program Load) (Re)boot/restart/reset/reinitializeNet adapter/ethx NIC (Network Interface Card)Router GatewaySerial port/ttysx Com port/COMxSlice Volume/partition

• NetWare to Linux command maphttp://www.novell.com/documentation/oes2/mgmt_lx_tips_lx_nw/data/nw2linux.html

Useful Sources of Information

• Novell®

• Partners

• http://support.novell.com

• http://forums.novell.com

• http://www.google.com

Summary

• That installation again, in pictures...

• Now the migration...

Summary

• Install an OES test system as soon as you can

• Experiment

• Build on what you already know

• Find your way around

• ...Have a lot of fun!

Any Questions?

Unpublished Work of Novell, Inc. All Rights Reserved.This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc. Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.

General DisclaimerThis document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. Novell, Inc. makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for Novell products remains at the sole discretion of Novell. Further, Novell, Inc. reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.

c l113

broker man

gb dhcp dns

gb dhcpbrokerdriversman

ndpsm london sys

gb dhcp broker driversman

gb nss

installation andmigration

gb driver store

Documents

l113 word meaning and discourse understanding · pdf...

c cccc c c c c c c c ˘c ˇˆc ˙ c˝ ˛ ˚c ˚ c˜ !c...

cmn - carpentras, bibl. mun., ms. 96 (leroquais,...

structural isomers c - c - c - c - c - c - c - c cc c - c -...

a brief review of double-pulsar system, psr j0737-3039...

t o n g a s s - usda · e e e e e e e e e e e cc c c cc c c...

bohren - mitsubishi materials corporation · l001 l002 l003...

l113 word meaning and discourse understanding · l113 word...

l113 safe use of lifting equipment

c c c - 101books.ru · c c ˇc c c$ c #c$ c ˙ c %c 2˜ c...

safe use of lifting equipment - bp-training.co.uk · 2017....

l113 word meaning and discourse understanding ·...

11/6/2013...072 wo 13k r144 r15 1149b t72 270 100k 100 220...

2p · !c c pp $ = 76-80!"#$%&'(c c c c c c c c c c c c c c...

loler l113 acop

m ain se t bb uusshhbb cckkrriiddggee p h at w mma aggi...

t-bone concerto - lindner-music.de · b & & & & & &????? ÷...

wb11524bs w b11524bsxp the predator · 10750 starting...

safe use of lifting equipmentsafe use of lifting equipment...

oliver p. morton papers l113, ob5 folder 14, obc44, v438 ·...