Novell

Storage Manager™

January 26, 2009

Installation Guide

2.5 w w w . n o v e l l . c o m

Legal Notices Condrey Corporation makes no representations or warranties with respect to the contents of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Condrey Corporation reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Also, Condrey Corporation makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Condrey Corporation reserves the right to make changes to any Condrey Corporation software product described herein, at any time, without obligation to notify any person or entity of such revisions or changes. You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside. Copyright © 2002-2009 Condrey Corporation. All Rights Reserved. No part of this publication may be reproduced, photocopied, stored electronically or transmitted in any fashion with out the express written consent of the publisher.

Document Version: 60519

Condrey Corporation Trademarks

File System Factory is a trademark of Condrey Corporation. AuditLogin is a trademark of Condrey Corporation. IUAdmin is a trademark of Condrey Corporation. Internet User Administrator is a trademark of Condrey Corporation.

Novell and other Third-Party Trademarks

Novell is a registered trademark of Novell, Inc. in the United States and other countries. Novell Directory Services is a trademark of Novell, Inc. eDirectory is a trademark of Novell, Inc. NetWare is a registered trademark of Novell, Inc. in the United States and other countries. NCP is a trademark of Novell, Inc. NLM is a trademark of Novell, Inc. Windows is a trademark of Microsoft Corporation. All other third-party trademarks are property of their respective owners.

Condrey Corporation 125 The Parkway, Suite 500 Greenville, South Carolina 29615 USA

Contents Legal Notices............................................................................................................................... 2

Condrey Corporation Trademarks........................................................................................ 2

Novell and other Third-Party Trademarks ............................................................................ 2

Install Novell Storage Manager ................................................................................................... 4

Overview ................................................................................................................................ 4

Install or Upgrade of the Novell Storage Manager ................................................................... 4

Installing NSMAdmin to the local workstation ......................................................................... 9

Upgrading Novell Storage Manager for eDirectory ............................................................ 15

Configure Novell Storage Manager via NSMAdmin ................................................................ 16

Installing and Deploying Event Monitors ............................................................................... 21

Deploying Event Monitors for NetWare ............................................................................. 21

Installing the Event Monitor for OES2 Linux ....................................................................... 25

Installing the NSM Event Monitor for OES2 Linux .............................................................. 25

Configuring the NSM Event Monitor for OES2 Linux .......................................................... 25

Registering the NSM Event Monitor for OES2 Linux via NSMAdmin ................................... 27

Best Practices for NSM Event Monitors ............................................................................. 28

Installing and Deploying NSM Agents (formerly Sentinels) ..................................................... 28

Deploying the NSM Agent for Netware .............................................................................. 28

Installing the Agent for OES2 Linux .................................................................................... 31

Configuring the NSM Agent for OES2 Linux ........................................................................ 31

Registering the NSM Agent for OES2 Linux via NSMAdmin ................................................ 32

Install Novell Storage Manager

Overview Installing and configuring Novell Storage Manager

Requirements

NetWare 6.5 Service Pack 7 or later

Install or Upgrade of the Novell Storage Manager Launch the Novell_Storage_Manager_2_5_for_eDirectory.exe and follow the prompts.

Installing NSMAdmin to the local workstation

Minimum Requirements

Microsoft Windows XP SP2, Vista (32bit or 64bit) Microsoft .Net Framework 3.5 Administrator Privileges

Upgrading Novell Storage Manager for eDirectory

Configure Novell Storage Manager via NSMAdmin

1. Launch NSMAdmin executable. Click on Start->All Programs->Novell-Storage Manager->NSMAdmin

2. Login to the NSM Management Interface:

a. Server IP and Port#: <Your Servers IP Address or DNS Name>:8009 b. User ID: Admin.OU.Org Note that the full distinguished dotted name is required. c. Password: xxxxxxx

3. NSMAdmin will start in Wizard Mode, click Next to continue.

4. Fill-in Server, Port, Tree, User Name, and Password fields, click Next to continue.

5. Browse for the NSM version 2.5 license or click the "Get a License" button, click Next to continue.

Note: NSM requires a new license file for both fresh installs and upgrades from older

versions.

6. Click Next, to extend the schema. Note: NSM requires that the eDirectory schema be extended for both new installs and

upgrades.

7. NSM depends on a Proxy Account. This account by default will be created in the same container as the NSM Engine Server. If this is an upgrade please verify that the proper nsmproxy account is being referenced.

8. The NSMAdmin wizard can set the rights necessary for the proxy user. click Next to continue.

9. The NSM Engine wizard is now complete.

10. The NSM Engine will not finish initializing with this new configuration. Note: If this is an upgrade the Engine my take a few minutes to become available. As the

Engine upgrades all of the existing policies, and initializes its workers.

Installing and Deploying Event Monitors

Overview

NSM for eDirectory now has two available Event Monitors one for NetWare and other for OES 2

Linux. The NetWare based Event Monitor is a NetWare Loadable Module (NLM), and uses NDAP

over NCP to monitor eDirectory for events. The OES 2 SP1 Linux based Event Monitor runs as

daemon, and uses LDAP to monitor eDirectory. Both Event Monitors use HTTP(S) to

communicate with the Engine.

Requirements

NetWare 6.5 SP7 or later

Deploying Event Monitors for NetWare

1. Launch NSMAdmin executable. Click on Start->All Programs->Novell-Storage Manager->NSMAdmin

2. Login to the NSM Management Interface:

a. Server IP and Port#: <Your Servers IP Address or DNS Name>:8009 b. User ID: Admin.OU.Org Note that the full distinguished dotted name is required. c. Password: xxxxxxx

3. Select the “Config” tab. 4. Select “Event Servers” from the Component Config section.

5. If this is a new install, click the "Add" and select a server that meets the requirements for Event Monitoring.

6. If this is an upgrade, and the server meets the requirements, highlight the server to be

upgraded and click the "Upgrade" button.

7. If this is an upgrade, and the server does not meet the requirements, highlight the server

to be removed and click the "Remove" button.

This completes the steps for configuring a minimum of at least one event server for monitoring events in the Directory. Note: Two Event Monitors are needed per replica ring for best results.

A Results dialog confirming the results of the Event Monitor deployment is displayed.

Installing the Event Monitor for OES2 Linux

Overview

Installing the NSM Event Monitor for Linux requires OES2-SP1 or SLES 10 SP2.

Note: NSM Event Monitors for Linux will not show up in NSMAdmin the same way as NetWare

Servers. The NSM Event Monitor for Linux must be installed first on the Server. Once installed,

the NSM Event Monitor will begin to send heartbeat messages to the NSM Engine which will

allow the Event Monitor to be registered via NSMAdmin. Registration is required to allow the

Engine to trust the Event Monitor.

Copy the novell-storagemanager-event-2.5.0-xx-installer.bin file from the NSM Engine

component directory to the desired Linux server.

Installing the NSM Event Monitor for OES2 Linux

The NSM Event Monitor for Linux must be installed from via terminal as root.

Accept the EULA.

When the installation completes the nsmevent-config utility will need to be run to configure the

NSM Event Monitor for OES2 Linux. The utility can be run from the console by typing the

following:

After the installation is complete the installer is prompted to configure the NSM Event Monitor

for Linux using the nsmevent-config utility. The nsmevent-config checks to see if a

nsmagentd.conf file exists, and if not will create one. If the configuration (conf) file is created by

the utility the utility will start in wizard mode to get the NSM Event Monitor for Linux

configured, and accepting events.

Configuring the NSM Event Monitor for OES2 Linux

The wizard mode of the utility will need to know the IP Address of the Engine Server, the port to

communicate with the NSM Engine (8009 by default), the IP Address of the LDAP Server to be

monitored, the port to communicate with the LDAP Server, and credentials to login for

eDirectory (FDN of the NSMPROXY object). This information is saved into the nsmeventd.conf

file.

/etc/opt/novell/storagemanager/event/nsmeventd.conf

nsmevent-config

sh novell-storagemanager-event-2.5.0-xx-installer.bin

Once the NSM Event Monitor is configured the utility will act as console to allow control, and

management of the NSM Event Monitor for Linux.

The NSM Event Monitor for Linux logs are created in:

The NSM Event Monitor for Linux binaries are located in:

The NSM Event Monitor has also has setup the standard rc script to allow the administrator

quick access to start, stop, restart, and check the status of the NSM Event Monitor for Linux.

rcnsmeventd (start|stop|restart|status)

/opt/novell/storagemanager/event/bin

/var/opt/novell/storagemanager/event/log

Registering the NSM Event Monitor for OES2 Linux via NSMAdmin

1. Launch NSMAdmin, and select the “Config” tab. 2. Select Event Servers from the Component Config section.

3. Click the “Add” button

4. Select the OES2 Linux Server from the list of heart beating OES2 Linux Event Servers.

5. Click the “Add” button. The NSM Event is now registered.

Best Practices for NSM Event Monitors

Things to be aware of when designing the NSM Event Monitor placement:

Two (2) Event Monitors are needed per replica ring.

The NetWare and OES2 Linux based Event Monitors can both be used to monitor the

same replica, but not the same server.

Installing and Deploying NSM Agents (formerly Sentinels)

Deploying the NSM Agent for Netware

1. Launch NSMAdmin executable. Click on Start->All Programs->Novell-Storage Manager->NSMAdmin

2. Login to the NSM Management Interface:

a. Server IP and Port#: <Your Servers IP Address or DNS Name>:8009 b. User ID: Admin.OU.Org Note that the full distinguished dotted name is required.

c. Password: xxxxxxx

3. Select the “Config” tab. 4. Select “Agent Servers” from the Component Config section.

5. If this is a new install, click the "Add" and select a server that meets the requirements for

Agent Servers.

6. If this is an upgrade, and the server meets the requirements, highlight the server to be

upgraded and click the "Upgrade" button.

7. If this is an upgrade, and the server does not meet the requirements, highlight the server

to be removed and click the "Remove" button.

A Results dialog confirming the results of the Event Monitor deployment is displayed.

Installing the Agent for OES2 Linux

Requirements

The Linux Agent requires an OES2sp1 machine with NSS installed. The NSS software must be installed, even if using native Ext3 or Reiser file systems. The OES2SP1 installation CD maybe required if any dependencies are missing. Note: A 32-bit binary is provided. Installing this program on OES2sp1 64-bit is experimental and is unsupported at this time. The NSM Event Monitor for Linux must be installed from via terminal as root.

Accept the EULA, and allow the installation process to complete. Yast maybe called to install any

missing dependencies.

Configuring the NSM Agent for OES2 Linux

When the installation completes the nsmagent-config utility will need to be run to configure the

NSM Agent for OES2 Linux. The utility can be run from the console by typing the following:

After the installation is complete the installer is prompted to configure the NSM Agent for OES2

Linux using the nsmagent-config utility. The nsmevent-config checks to see if a

nsmagentd.conf file exists, or if not it will create one. If the configuration (conf) file is created

by the utility the utility will start in wizard mode to get the NSM Agent for OES2 Linux

configured, and accepting work from the NSM Engine.

nsmagent-config

sh novell-storagemanager-agent-2.5.0-xx-installer.bin

Registering the NSM Agent for OES2 Linux via NSMAdmin

1. Launch NSMAdmin, and select the “Config” tab.

2. Select Agent Servers from the Component Config section.

3. Click the “Add” button

4. Select the OES2 Linux Server from the list of heart beating OES2 Linux Agent Servers.

5. Click the “Add” button. The NSM Agent is now registered.