osa
v.4.5.0


Uninstall OpenManage
BIOS, ESM, and Drivers
SNMP and DCOM
Checking the Registry
Server Administrator Install
IT Assistant Install
ITA - Discovery


Drivers and Downloads
User Guides
Subscription Service
Videos and Resources OM Product Ports List


 


Please read this entire document before you
begin the updates and deployment of the software.


Step 1

Uninstalling Open Manage

Uninstall any OpenManage/Server Administrator, ITA, Array manager software you have on the server. If you have Open Manage 4.2 or earlier use OMCLEAN to remove the Open Manage software otherwise use add/remove programs in the control panel.

DO NOT USE OMCLEAN TO REMOVE OPEN MANAGE VERSION 4.3, 4.4, or 4.5.

Step 2

Updating Bios, ESM, and Drivers

Update Drivers/Bios/ESM/Firmware for all the components on the server.

RECOMMENDED STEPS FOR UPDATING THE SYSTEM:

1. Update the Main System Bios.
2. Update the ESM Firmware, and ERA firmware(if applicable)
3. Uninstall any older versions of OpenManage Software.
4. Update the raid controller driver in the Device Manager.
5. Update the raid controller firmware.

Downloads and Drivers
http://support.dell.com/support/downloads/index.aspx?c=us&cs=555&l=en&s=biz&~ck=mn

Step 3

Installing and Configuring SNMP and DCOM

Install and configure SNMP and DCOM.

This section shows how to install and configure SNMP and DCOM Permissions.

To install SNMP services go to Control Panel > Add and Remove Programs. From here you should have the option to Add/Remove Windows Components. Select this. SNMP is under Management and Monitoring tools. This is dependant on the version of Windows you are currently running. Also you may want to reference the User Guide for help on how to configure SNMP in other operating systems.

SNMP Setup for Windows Operating Systems

Go to Start > Run > type services.msc

In the service window, select SNMP Service. All of your services are listed in alphabetical order. Double Click SNMP.

Below you will find screenshots of the SNMP settings Dell recommends for your first discovery.



As you can see above, we have a community name of public (community names are case sensitive), along with a Trap Destination of localhost. You could also add the IP Address or the Server Name. If you need to add a Community Name, type in ‘public’ in the space provided then click ‘Add to list’. To add a ‘Trap destination’ click ‘Add’ then type in the destination and click ‘Add’(can either be IP or hostname). This is the preferred setting on a server that has both IT Assistant and Server Administrator on it, which allows the server to discover itself. Below you will see the preferred setup for a server that has just Server Administrator.

As you can see in the illustration below, we have an Accepted Community Name of ‘public’ which has READ/WRITE’ access rights. We also have the ‘Send Authentication Trap’ button unchecked, and ‘Accept SNMP packets from any host’ checked.



Once you have these basic settings, click Apply, OK, then you must restart the SNMP service. This will apply all changes you have made to SNMP. Please note restarting SNMP will require you to restart both IT Assistant services if you have IT Assistant loaded on the machine. This is a normal function. Once SNMP has restarted, you can attempt discovery of your servers. These SNMP settings are recommended for your initial discovery.


Setting DCOM Permissions

Choose Operating System: NT4/2000 / 2003 Server

DCOM permissions for servers with NT4 and Server 2000:



Click Start > Run > and type dcomcnfg.exe and click OK. This will bring up the Distributed COM Configuration Properties window shown below.



Click ‘Edit Default’ for Default Access Permissions, you will get the window shown below:



Click ‘Add’ then click ‘Show Users’.



As you highlight each name, click ‘Add’ to add them to the ‘Add Names’ section. You want to choose all users you wish to have access to your Open Manage product. After you have added all your users, click ‘OK’ then do the same with 'Default Launch Permissions', and 'Default Configuration Permissions' as well.



Once you are finished, click the 'Default Properties Tab’ and make sure 'Default Authentication Level' is set to 'Connect', and the 'Default Impersonation Level' is set to 'Identify'.

DCOM permissions for Server 2003:



Click 'Start' > Run > and type DCOMcnfg.exe and click OK.



This will bring up the 'Component Services' Window shown above. In the picture below under Console Root you will see Component Services. Expand Component Services, and then right click on My Computer, go to properties and click it. In the ‘My Computer Properties’ dialog box, click the ‘Default COM Security’ tab. Below you will see screenshots of the 'Component Services', and ‘My Computer Properties’ dialog boxes.





Click ‘Edit Default’ for 'Access Permissions', which will bring up the Access Permissions dialog box shown below.



Click 'Add', then add the exact user account that is trying to use or install your Open Manage product. Be sure that that user has Allow for Local Access. When complete, click ok, which will bring you back to the COM Security tab on the My Computer Properties dialog box. Please click Edit Default and take the same steps you did with the Access Permissions in the Launch Permissions dialog box as shown below.





Once you have completed the steps, click OK and click the Default Properties tab on the main My Computer Properties dialog box. In this dialog box, you will need to make sure the Default Authentication Level is set to Connect, and the Default Impersonation Level is set to Identify. Click Apply then OK. You will see a screenshot of this dialog box above.

Step 4

Checking the Registry

The Registry only needs to be looked at if you have NOT been able to discover your servers.

SNMP Registry Settings

Registry settings for Windows 2000/2003



Click Start > Run > and type REGEDIT and click OK.



This will bring up the Windows registry, which is shown above.

Once you are in the registry you will want to navigate to the ‘HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\SNMP\Parameters\ExtensionAgents’ key. Once you have located the key, you will see something like what is above. The keys that you are looking for are:

SOFTWARE\Microsoft\LANManagerMIB2Agent\CurrentVersion
SOFTWARE\Microsoft\RFC1156Agent\CurrentVersion
SOFTWARE\Dell Computer Corporation\OpenManage\DataEngine\SNMP Agent\CurrentVersion (for current releases of Open Manage).

SOFTWARE\Dell Computer Corporation\Dell OMSA\SNMP Agent\CurrentVersion (for older releases of Open Manage).

The first two keys listed above need to have a value of 1 and 2 respectively. This is what it would look like in Windows.



If you need to make any corrections to the values, make sure that you have exported the keys before doing any kind of corrections to the registry. Once the backup of the keys have been done, right click on the registry key’s name and choose Rename as seen below.



You may have to play around with the numbers to get the two Open Manage keys in the right place. This should not affect any of the other applications on the server. Most commonly we have seen the Veritas key listed as number one and then the Dell keys listed later on.


About Server Administrator

Server Administrator provides a comprehensive, one-to-one systems management solution in two ways: from an integrated, Web browser-based GUI (the Server Administrator home page) and from a command line interface (CLI) through the operating system. Server Administrator is designed for system administrators to both locally and remotely manage systems on a network. Server Administrator allows system administrators to focus on managing their entire network by providing comprehensive one-to-one systems management.

Step 5

Server Administrator Install v.2.2

Install Server Administrator on the managed server. You will run the setup.exe file. After this a prerequisite checker will come up, if everything looks okay continue by selecting Install, Modify, Repair or Remove Server Administrator on the bottom left:



Choose a custom install. You will NOT install the Intel or Broadcom SNMP Agents.
(NOTE: The remote access controller is only needed if you have the hardware). You will have a red X next to both as in the following:




About IT Assistant

Dell OpenManage™ IT Assistant provides a central point of access to monitor and manage systems on a local area network (LAN) or wide area network (WAN). By allowing an administrator a comprehensive view across the enterprise, IT Assistant can increase system uptime, automate repetitive tasks, and prevent interruption in critical business operations.

Step 6

IT Assistant Install v.7.1

The prerequisite check will run to check your system before installing IT Assistant.

If this is the first time you are installing IT Assistant the prerequisite check will detect that your system does not have the nessasary MSDE installed and provides you with a link for installation.

In general, the number of systems you expect to manage and the number of alerts you expect from your managed systems determine the database you use with IT Assistant. If you will be managing fewer than 500 systems, the SQL Server-compliant default database that ships with IT Assistant, Microsoft Data Engine (MSDE) 2000, is most likely a suitable data repository. However, if you are going to manage 500 systems or more and/or are receiving several alerts per second, you should use Microsoft SQL Server 2000 or later as your database. In addition, if you are performing frequent discoveries or status polls, you may benefit by the increased performance offered by SQL Server 2000 over MSDE 2000.



Click the Install MSDE link and setup will install the software.



The prerequisite check will run a second time and all features should now be available for install. Click the Install, Modify, Repair or Remove Management Station link to begin the installation of ITA.



Accept the terms in the license agreement and click next.



Choose to do a Custom Install and click next.



Select the program features you want to install and click next.

Note: You can also customize the installation path here.



Customize the ports ITA uses for Network Monitoring and Connection Service or just accept the defaults.



You will get an installation summary. Click Install.



The ITA machine must have java installed. The first time you open ITA if Java is not installed it will prompt you to install it.



Just choose Typical and click Next



When installation is complete click Finish.



Once Jave is installed the ITA program will open and give you the screen below for initial configuration of Discovery, Inventory, Status Polling, and Ranges.

The next section, "IT Assistant Configuring and Troubleshooting Discovery", goes into more detail about setting up your ranges for discovery.




Step 7

IT Assistant Configuring and Troubleshooting Discovery

Regardless of the size of your network, the following table shows Dell's recommendations for the best way to set up discovery targets. IT Assistant users define discovery target systems and ranges on a network to identify the systems that they want to locate and record in their database. When you set up a discovery target and range in IT Assistant, you are given the option of selecting a host name, an IP address, or a subnet range to identify the systems that you want IT Assistant to discover. This section shows which discovery type is best for the network environment you have.

Best Practice Recommendations for Setting Up Discovery

Preferred Discovery Range Type

DHCP

Primarily Static IP Addresses

Host name

Recommended

Recommended if DNS is present and IP addresses are spread among many different network segments

IP address

Not recommended

Recommended if IP addresses are spread among many different network segments

IP range

Recommended if located on one or a few network segments

Recommended if located on one or a few network segments



This is the final step. You will want to launch IT Assistant and set up your discovery ranges. Click on Discovery and Monitoring. From here choose Ranges.

Right click on Include Ranges and select New Include Range.

Step through the wizard and except the defaults. You will not need to enable CIM discovery unless you are planning to configure discovery of client systems.

Servers are discovered using SNMP and client systems are discovered using CIM.

To watch the progress of your discovery click on Discovery and Monitoring and choose Logs.



If you are having issues with servers not being discovered then double check your SNMP configuration or run the troubleshooting tool. Below is a screenshot for accessing the troubleshooting tool.



Now this window will pop up. Enter the IP Address of the server you are having problems discovering and click Get Test Configuration. At this point you should have a Run Selected Test(s) button.

Select a test to run and click Run Selected Test(s).

The primary test you will want to select is SNMP Connectivity. Highlight this choice and choose Run Selected Test(s).

If the test fails then check your SNMP configuration settings.

If you are trying to discover through a firewall then make sure the ports for SNMP are open.

Ports used for SNMP are 161 and 162.

For more information on the ports used by Open Manage check out the Open Manange Ports list document.



Go to beginning