Cool Solutions

Using Novell Remote Manager on OES Linux and OES NetWare Servers



By:

April 25, 2007 8:46 am

Reads: 6560

Comments:0

Score:0

In this AppNote I will show you how to use Novell Remote Manager on OES Linux and OES NetWare servers.

Although the basics of Novell Remote Manager (NRM) are the same, NRM on NetWare and Linux do have some differences.

Lets start with the Interface.

You can access NRM as follows:

http:\\<server-ip>:8008

You’ll notice that you will be redirected to a https:\\ page and that the port is being changed to 8009.

Below is the NRM portal of the OES Linux Server.

Here is the NRM portal of the OES NetWare server.

The first difference you see is the File system. On the OES Linux Server you see a file system hierarchy, on the OES NetWare server you see a Directory structure with the Volumes it has.

If you dig further into the menu items you will also see that on the OES NetWare server there are more options to choose from. I will not go through all the options you can use, I just will tell you about some that you should know.

On OES NetWare you can create a inventory report of your NetWare Volumes. To create a report, on the Home Page click on the round icon beside the Volume.

A screen like this comes up.

Halfway down the screen, click on Volume Inventory Report.

You can now choose to see the last created report or to create a new one.

Click on Create a new report. This can take a little while depending on your volumes size, file count, etc.

When the report is created, you will see something like the this.

If you scroll down the page, more information is available.

You can see how much Disk space is available on the DATA Volume.

The figure below shows you how much disk space a specific file type uses.

This one is also very cool. You can see what user has the most files in use:

As you can see, in my test lab, I have only one user.

To show you all of the reports is not really important and if I did this article would be too long. Just do it on your own data server and see what you can come up with.

Now lets create a Volume Inventory Report on the OES Linux Server.

Click on the round icon next to “rootfs“.

You see the difference between the OES Linux and NetWare servers.

Click on File System Inventory.

The only thing you can see is the amount of files on the system.

So, as you can see on the OES NetWare Server, there are more options if you are looking at the Volume Inventory Report.

Another thing I would like to tell you about is the DEBUG Account.

Lets assume that you have a corrupt eDirectory and no users can login any more. This means that you also can’t login into NRM. Therefor the SADMIN Account can be created. To create it click on the Configure icon on the top of the NRM page.

Now click emergency account (SADMIN uses) admin set password.

Enter the password you would like to use for the SADMIN user and click SET.

A message comes up telling you the SADMIN account is been enabled.

Now test if you can login with that account.

The user name for the SADMIN account is: sadmin

Enter the Password and Click login.

As you can see in the upper left corner, the SADMIN user is logged in now. Now I am able to login to NRM without the need of a proper working eDirectory.

In the figure below I have opened the configure page of NRM on the OES Linux Server. As you can see the SADMIN user option is not available here.

Some of the other configuration parameters that you saw on the OES NetWare server NRM, can be configured by changing the httpstkd configuration file. You can make changes to this file by clicking on Edit httpstkd config file

If you made any changes to this file you have to restart NRM for the changes to take effect. You can do this by clicking on the Restart httpstkd button.

The last thing I would like to show you is how to monitor a group or server.

On the left menu click Configure New Group.

As you see a picture come up with the world atlas. You also see the DA1 server, it is represented by the green dot. It’s green because everything on the server is running ok.

Now I will show you how you can add a second server to the picture.

Right click somewhere in the picture.

As you can see a window comes up. Click Add Item, and new configuration screen comes up.

Enter the Name of the Server and the IP address. In this article I will leave the other settings as the default but you can change them if you know how it works.

Click Add.

Now you see that the second DA2 server is also in the picture.

The DA2 server has a yellow color, this means something is not running ok.

You can move the Servers by left-clicking on them and move them to another place on the screen.

If you click on the yellow dot, you are able to log in to the NRM Health page of the DA2 server.

Now you can see what is wrong with the server and take action on that. In my case there was a little problem with timesync. (I created this problem myself to show you how it works :-) )

You can add as many Servers into a group as you like.

You can also change the background. The Default background is a picture of the world, but you can change it to something else if you like.

Right click on the picture and click Group Configuration.

I have now changed the background to Europe West. I have also given the Group a name: OES Network.

Click Apply to save the settings and see what happens.

As you can see the background is changed. To save the Group Configuration, right click somewhere in the background and click Save Group.

Enter the Group Name and click Save Group.

If you click Select Group from the left menu, you can choose to open the Group again if you logged out before.

Make sure the OES Network Group is in the first drop box, then click Build Group. You will notice that the map appears that you saved earlier.

As you can see Novell Remote Manager is a very powerful tool you can use to monitor your OES NetWare and Linux Servers.

Start testing everything NRM offers and I am sure you can use many of the features it has.

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Categories: Uncategorized

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

RSS