Guest

Cisco Element Manager System

Frequently Asked Questions About CEMF Field Issues

Cisco - Frequently Asked Questions About CEMF Field Issues

Document ID: 24869

Updated: Jan 31, 2006

   Print


Questions


Q. Should databases remain in the system when they are not part of the system being restored? (Products affected : CEMF 3.x)

A. Yes, this is the expected behaviour. Doing a restore doesn't automatically remove old databases and configurations before performing the restore.

An Element Manager (EM) stores data in several databases. Therefore, when you restore a backup created before an EM was installed, you overwrite the databases with databases that have no knowledge of that EM. Any databases that were associated directly with the EM, but were not included within the backup that you have restored, remains in the system (they are not removed).

To avoid problems when restoring an earlier backup (if you have installed an EM since the backup was made), the following steps describe the correct way to proceed:

  1. Perform backup
  2. Install a new EM
  3. Use the new EM
  4. De-install EM
  5. Restore backups taken at step 1 (that is, with no knowledge of the new EM)
Q. How do I update the IP address of an existing CEMF server installation? (Products affected : CEMF 3.x)

A. The IP address of an existing server installation may be updated via the command:
/cemf updateIP -m xxx.xxx.xxx.xxx (where xxx.xxx.xxx.xxx is the desired IP address)
Note: This facility is available in the base CEMF 3.1 package, but CEMF 3.0.4 - Patch 05 is required for it to work on CEMF 3.0.4.
Q. How do I install a CEMF server on a machine with multiple IP addresses when I don't want to use the default IP address? (Products affected : CEMF 3.x)

A. On a CEMF 3.1 installation, use the updateIP function to change the server to the desired IP address, and following this change, clients can connect to the server on the new address.

Because the updateIP function isn't present in the base CEMF 3.0.4 system, the initial (unpatched) server installation must specify the first (default) IP address. Following this, apply the patch containing the updateIP function and then the existing server IP address is updated to the desired value denoted in the updateIP command. The CEMF 3.0.4 installation is then available for new client connections on this address.

Q. How do I connect my client to a CEMF installation that is not using its default IP address? (Products affected : CEMF 3.x)

A. When installing the client, specify the IP address being used by the server together with the PROPER host name (it is important that the proper host name is used).
Q. How can I change the host name and/or IP Address that my CEMF installation uses? (Products affected: CEMF 3.x)

A. Cisco EMF provides the user with the updateName and updateIP functions for this purpose.

Refer to the Cisco Element Management Framework - Installation and Administration Guide, section "Administering Cisco EMF WorkStations", subsections "Updating Hostname" and "Updating IP address" for details of how to carry out these operations.

Q. What are jumbo, mini, and mini-jumbo patches and how does their numbering convention work? (Products affected : CEMF 3.x)

A. Jumbo patches (or jumbos) are patches applied to CEMF, that roll-up all updates from previous patches.

Mini patches contain selective software updates, and are applied to specific jumbos. Mini patches can be applied in any order, so they should not contain duplicate files. If they contain duplicate patches, regression may occur.

Mini-jumbo patches are mini-patches that contain software updates that exist in other mini patches. Any installed mini patches that are obsoleted by a mini-jumbo, are automatically deinstalled when that mini-jumbo is applied. In turn, any subsequent attempt to install the obsoleted mini patch fails as long as the mini-jumbo is present. Like mini patches, mini-jumbos can be applied in any order. The following rules apply:

  • A mini or mini-jumbo patch can only be installed on the jumbo patch it is patching.
  • It is not possible to install a mini or mini-jumbo patch if a later jumbo is already installed.
  • Installing a jumbo patch automatically de-installs all previous patches.
  • Installing a mini-jumbo patch automatically de-installs all previous mini and mini-jumbo patches made to that jumbo patch.
  • A jumbo patch can only be installed on top of the version of the package it is patching (for example, applying a CEMF 3.1 based patch to a CEMF 3.0.4 system is not permitted).
  • It is not possible to install a mini or mini-jumbo patch if its fixes are already incorporated into a later mini-jumbo that is already installed.

The identification format is slightly different between jumbo and mini/mini-jumbo patches. This is explained below.

The CEMF jumbo-patch ids use the following format:

  • Digits 1 and 2 are used to indicate that the patch is a jumbo patch pertaining to CEMF, and is set to a value of 17.
  • Digits 3 and 4 indicate whether the jumbo patch pertains to the server or client - 00 or 01, respectively.
  • Digits 5 and 6 represent the jumbo-patch level, which is sequential.
  • Digit 7 is a hyphen, used solely as a divider.
  • Digits 8 and 9 indicate the build number of the patch, which is sequential.

For example, 170003-12 represents build 12 of CEMF-server patch level 3, while 170105-02 indicates build 2 of CEMF-client patch level 5.

The CEMF mini and mini-jumbo patches use the following format:

  • Digits 1 and 2 indicate a mini or mini-jumbo patch pertaining to the server or client, where 19 indicates a server patch and 20 a client.
  • Digits 3 and 4 indicate the level of the parent jumbo patch.
  • Digits 5 and 6 represent a unique identification number for the mini or mini-jumbo patch.
  • Digit 7 is a hyphen, used solely as a divider.
  • Digits 8 and 9 indicate the build number of the patch, which is sequential.

For example, 191101-03 indicates build 3 of a CEMF-server mini or mini-jumbo patch, with an id number of 01, pertaining to a level 11 jumbo patch. While, 201104-05, indicates build 5 of a CEMF-client mini or mini-jumbo patch, with an id number of 04, which pertains to a level 11 jumbo.

The following example illustrates how the patching mechanism should be used. Ignore the patch build numbers since these vary depending on which version/build of CEMF is being patched.

For this example, a server based jumbo patch 170021-05 requires a series of mini and mini-jumbo patches over a period of time.

Assume that you have installed jumbo patch 170021-05 onto a system it already has patches applied, an action that results in the automatic removal of any previously applied patches:

 


     [CEMF + various patches] --> [CEMF + 170021-05] 
Next you apply mini patches 192101-03, 192102-03 and 192103-01, which coexist with the installed jumbo.
     [CEMF + 170021-05] -->  [CEMF + 170021-05 + 192101-03 + 192102-03 + 192103-01] 
Next you apply mini-jumbo 192104-02, which incorporates, and subsequently removes, mini patch 192102-03.
     [CEMF + 170021-05 + 192101-03 + 192102-03 + 192103-01] --> [CEMF + 170021-05 + 192101-03 + 192103-01 + 
     192104-02] 
Any attempt to reinstall 192102-03 results in failure as long as 192104-02 is installed.

 

Q. My CEMF Management machine is behind a firewall. What ports should I open on the firewall to allow me to use auto discovery to deploy and manage 6400 devices? (Products affected : CEMF 3.x)

A. You must enable the following ports on the firewall so that auto discovery can work normally through the firewall:

Type of Traffic
Protocol Type
Port Number
SNMP
UDP
161 and 162
Telnet
TCP
23
tftp
UDP
69
icmp
TCP and UDP
7
Q. How do I update the CEMF Server that my CEMF Client is using? (Products affected : CEMF 3.x)

A. Follow these steps:

  1. Ensure that CEMF is not running on the client.
  2. Open all files in this directory: <CEMFROOT>/config/env/
  3. Replace all occurrences of the old CEMF Server hostname with the new CEMF Server hostname in each file.
  4. If this following file is present, /var/adm/Atlantech/system/info replace all occurrences of the old CEMF Servers' hostname and IP address with the new CEMF Server hostname and IP address.
  5. Restart your client installation and the new session points to the new CEMF Server.
Q. Why does my installation abort when I try to install my Element Manager on top of CEMF? (Products affected : CEMF 3.x)

A. This is a known problem with certain versions of the tar utility, and is related to the version of Solaris that you are using.

The problem appears during the Element Manager (EM) installation process, but it is not a CEMF problem since CEMF does not use the tar utility. The source files for the installation of the EM were corrupted when they were untarred. The following text is a response to a support call to Sun MicroSystems to inquire about this tar/Solaris problem:

"There are incompatibility issues between tar for Solaris 2.5.1 (or older versions of 2.6) and 2.6. These only manifest themselves on file names that are *exactly* 100 characters long. If a tar is created on 2.6 and then extracted on 2.5.1 (or old 2.6) file names 100 chars long will become corrupt."

This has been confirmed by the Sun Support team who refer to the following Sun bug references: 4230018, 1159730, 4159825, 105792-03. The problem has been reproduced within Suns' support labs (although the engineer said he had never seen it before). Sun recommends that you upgrade to 2.6 and get the latest patches to work around the problem.

Q. Why do I get the message "/usr/bin/showrev: get_env_var(remove.list, SUNW_PATCHID)" when I install a CEMF patch? And why can't I use the <CEMFROOT>/cemfinstall -r command to uninstall the patch package? (Products affected : CEMF 3.x)

A. Cisco EMF installation scripts use the unix /usr/bin/showrev command, which in turn reads the contents of /var/sadm/pkg. This directory is intended to hold only package information and if it contains anything other than that, the showrev command fails.

In this case a file called remove.list has been (wrongly) added to directory /var/sadm/pkgs. If this file is deleted then the showrev command works the way Cisco EMF expects, and the patch installation completes successfully.

Q. How do I delete a DSLAM that I mistakenly deployed directly under the Physical view, so that I can deploy it under a Site object I created under the Physical view? (Products affected : CEMF 3.x)

A. To prevent duplicate IP addresses within the system, Cisco EMF uses the Network view to check for attempts to deploy objects with an IP address the same as existing objects. In order to resolve the problem above you must delete the relevant network from the Network view, and then the unwanted DSLAM from the Physical view. The DSLAM should now deploy successfully under the Site object.
Q. How can I make sure my installed CEMF functions after I change my machine hostname? (Products affected : CEMF 2.1.x)

A. Assuming the IP address of the host remains the same, follow these steps:

  1. Before starting the system, rename the configuration environment (config/env) files to the new host name. These files are used to locate the ports to talk to/bind to for this host.

  2. Change the hostname in the licence file to the new hostname. This file is used to determine which host we should talk to for licence requests. However, the licence file uses the hostID, so as long as this has not changed, a new licence key is NOT needed.

  3. Ensure that ObjectStore is stopped. Rename the server configuration file in <os_rootdir>/etc from:

    <old_hostname>_server_parameters

    to

    <new_hostname>_server_parameters

    On start-up, the ObjectStore startup script looks for a server file with its host name to see if it should start a server or not.

  4. /var/adm/Atlantech/system/info

    This is only used to keep the information entered by a user during installation. Any re-installation uses these values as the defaults in prompts, so you should ensure that these are the correct values.

Q. What hardware specification do you recommend for deployments? (Products affected : CEMF 3.x)

A. Small deployments

Sun Ultra 60 configured as follows:

  • 2 x 9Gb internal disks
  • 1 x 9Gb 10,000rpm external disk
  • 512 Mb memory. (This may need to increase to 1Gb depending on performance benchmarking)
  • 2 x 360 MHz processors
  • 2Gb swap

Large deployments

Sun Enterprise 450 configured as follows:

  • 6 x 9Gb 10,000 rpm disks on 3Ultra SCSI controllers
  • 1 Gbyte memory
  • 4 x 250 Mhz processors
  • 2Gb swap

CEMF Clients

As above, with

  • 256Mb memory
  • 1Gb swap
Q. What Solaris 2.6 patches should I install for running CEMF? (Products affected : CEMF 3.x)

A. CEMF requires only a standard Solaris installation, with the default patches. Running showrev -p on one of our workstations shows that the following patches are installed. This is the specification we would recommend.

Patch: 106183-03 Obsoletes:  Requires: 105181-05, 105222-02, 105223-02, 105492-02, 105600-02, 105604-03, 105651-03, 
   105742-02, 105795-02, 105836-02, 106168-01, 106169-01, 106170-01, 106171-01, 106172-01, 106173-01 
Incompatibles: Packages: SUNWkvm, SUNWcsu, SUNWarc, SUNWhea Patch: 105642-03 Obsoletes: Requires: Incompatibles: Packages: SUNWkvm Patch: 105181-21 Obsoletes: 105214-01, 105636-01, 105776-01, 106031-02, 106308-01, 106048-07, 105222-03, 105604-09
Requires: Incompatibles: Packages: SUNWkvm, SUNWcsu, SUNWcsr, SUNWcar, SUNWhea Patch: 105642-08 Obsoletes: Requires: Incompatibles: Packages: SUNWkvm Patch: 105401-09 Obsoletes: 105524-01 Requires: Incompatibles: Packages: SUNWcsu, SUNWcsr, SUNWarc, SUNWnisu Patch: 106141-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106075-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106049-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106044-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106035-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106033-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106031-02 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu, SUNWcar Patch: 105990-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu, SUNWxcu4 Patch: 105988-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105953-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105867-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105792-02 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105757-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105755-03 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105746-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105736-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105724-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105722-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105718-02 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105705-02 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu, SUNWhea Patch: 105693-03 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu, SUNWcsr Patch: 105686-02 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105621-02 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu, SUNWarc Patch: 105615-03 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105568-05 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105562-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu, SUNWnisu Patch: 105518-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105516-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105490-04 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu, SUNWcsr, SUNWarc, SUNWbtool, SUNWhea,
SUNWtoo, SUNWosdem, SUNWxcu4 Patch: 105405-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu, SUNWarc Patch: 105397-02 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105393-02 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105216-03 Obsoletes: Requires: 105401-07 Incompatibles: Packages: SUNWcsu Patch: 105210-05 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu, SUNWarc Patch: 105210-24 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu, SUNWarc Patch: 105621-17 Obsoletes: 105393-11, 105686-02, 105845-01, 106064-01, 106075-01, 106033-01 Requires:
Incompatibles: Packages: SUNWcsu, SUNWcsr, SUNWarc, SUNWhea, SUNWnisu Patch: 106828-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105401-28 Obsoletes: 105524-01 Requires: Incompatibles: Packages: SUNWcsu, SUNWcsr, SUNWarc, SUNWhea, SUNWnisu Patch: 105562-03 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu, SUNWnisu Patch: 105210-27 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu, SUNWarc Patch: 105568-17 Obsoletes: Requires: 105210-27 Incompatibles: Packages: SUNWcsu, SUNWhea Patch: 105216-04 Obsoletes: Requires: 105401-07 Incompatibles: Packages: SUNWcsu Patch: 105621-23 Obsoletes: 105393-11, 105686-02, 105845-01, 106064-01, 106075-01, 106033-01 Requires: 105181-20
Incompatibles: Packages: SUNWcsu, SUNWcsr, SUNWarc, SUNWhea, SUNWnisu Patch: 105615-08 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105665-03 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106257-05 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106271-06 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu, SUNWnisu Patch: 106301-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106439-06 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106448-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106226-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105667-02 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105722-05 Obsoletes: 105724-01 Requires: Incompatibles: Packages: SUNWcsu Patch: 106522-04 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106569-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu, SUNWarc Patch: 106592-03 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106625-05 Obsoletes: 105572-11 Requires: Incompatibles: Packages: SUNWcsu, SUNWcsr, SUNWarc Patch: 106834-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu, SUNWxcu4 Patch: 107758-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 107774-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 107565-02 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 108492-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 108895-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 108307-02 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 107733-08 Obsoletes: 105490-09 Requires: Incompatibles: Packages: SUNWcsu, SUNWcsr, SUNWarc, SUNWbtool,
SUNWhea, SUNWtoo, SUNWosdem, SUNWxcu4 Patch: 109266-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 109339-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 108804-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106361-08 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu, SUNWcsr, SUNWxcu4 Patch: 106655-02 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106882-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 108166-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 107490-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 106651-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsu Patch: 105181-05 Obsoletes: 105636-01, 105776-01 Requires: Incompatibles: Packages: SUNWcsr, SUNWcar, SUNWhea Patch: 106173-02 Obsoletes: Requires: 105181-05 Incompatibles: Packages: SUNWcsr Patch: 106171-01 Obsoletes: Requires: 105181-05 Incompatibles: Packages: SUNWcsr Patch: 106170-02 Obsoletes: Requires: 105181-05 Incompatibles: Packages: SUNWcsr, SUNWhea Patch: 106169-02 Obsoletes: Requires: 105181-05 Incompatibles: Packages: SUNWcsr, SUNWcar Patch: 106168-02 Obsoletes: Requires: 105181-05 Incompatibles: Packages: SUNWcsr, SUNWcar Patch: 105836-02 Obsoletes: Requires: 105181-05 Incompatibles: Packages: SUNWcsr Patch: 105742-03 Obsoletes: Requires: 105181-05 Incompatibles: Packages: SUNWcsr Patch: 105604-05 Obsoletes: Requires: 105181-05 Incompatibles: Packages: SUNWcsr, SUNWcar, SUNWhea Patch: 105600-05 Obsoletes: Requires: 105181-05 Incompatibles: Packages: SUNWcsr, SUNWhea Patch: 105222-03 Obsoletes: Requires: 105181-05 Incompatibles: Packages: SUNWcsr, SUNWcar, SUNWhea Patch: 105651-06 Obsoletes: Requires: 105181-05, 105222-02, 105223-02, 105492-02, 105600-02, 105604-03, 105742-02,
105795-02, 105836-02, 106168-01, 106169-01, 106170-01, 106171-01, 106172-01, 106173-01 Incompatibles:
Packages: SUNWcsr, SUNWcar, SUNWhea Patch: 105847-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 105845-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 105797-02 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 105786-03 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 105780-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 105778-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 105720-03 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 105572-03 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 105564-02 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 105529-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 105528-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 105486-02 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 105379-03 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 105214-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 106323-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 105654-03 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 105924-03 Obsoletes: 105610-04 Requires: Incompatibles: Packages: SUNWcsr, SUNWpd Patch: 105356-15 Obsoletes: 105797-07 Requires: Incompatibles: Packages: SUNWcsr Patch: 105379-05 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 105786-12 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 105720-12 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 105600-17 Obsoletes: Requires: 105181-05 Incompatibles: Packages: SUNWcsr, SUNWhea Patch: 105529-09 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr, SUNWhea Patch: 105780-05 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 108468-02 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 106639-04 Obsoletes: Requires: Incompatibles: Packages: SUNWcsr Patch: 106216-01 Obsoletes: Requires: Incompatibles: Packages: SUNWcar Patch: 106495-01 Obsoletes: Requires: Incompatibles: Packages: SUNWesu, SUNWtoo Patch: 105802-03 Obsoletes: Requires: Incompatibles: Packages: SUNWtltk Patch: 105802-12 Obsoletes: 106480-01 Requires: Incompatibles: Packages: SUNWtltk, SUNWtltkm Patch: 106084-01 Obsoletes: Requires: Incompatibles: Packages: SUNWxildh Patch: 105633-05 Obsoletes: Requires: Incompatibles: Packages: SUNWxwfnt, SUNWxwplt, SUNWxwcft, SUNWxwslb Patch: 105633-41 Obsoletes: Requires: Incompatibles: Packages: SUNWxwfnt, SUNWxwplt, SUNWxwcft, SUNWxwslb Patch: 105618-01 Obsoletes: Requires: Incompatibles: Packages: SUNWxwplt Patch: 105400-02 Obsoletes: Requires: Incompatibles: Packages: SUNWxwplt Patch: 105284-36 Obsoletes: Requires: Incompatibles: Packages: SUNWmfrun Patch: 105464-01 Obsoletes: Requires: Incompatibles: Packages: SUNWxwopt, SUNWxwman Patch: 105464-02 Obsoletes: Requires: Incompatibles: Packages: SUNWxwopt, SUNWxwman Patch: 106415-03 Obsoletes: Requires: Incompatibles: Packages: SUNWxwopt Patch: 105669-02 Obsoletes: Requires: Incompatibles: Packages: SUNWdtbas Patch: 105630-01 Obsoletes: Requires: Incompatibles: Packages: SUNWdtbas Patch: 105160-02 Obsoletes: Requires: Incompatibles: Packages: SUNWdtbas Patch: 105669-10 Obsoletes: Requires: Incompatibles: Packages: SUNWdtbas Patch: 106242-02 Obsoletes: Requires: Incompatibles: Packages: SUNWdtbas Patch: 108201-01 Obsoletes: Requires: Incompatibles: Packages: SUNWdtbas Patch: 106193-01 Obsoletes: Requires: Incompatibles: Packages: SUNWadmap Patch: 105800-01 Obsoletes: Requires: Incompatibles: Packages: SUNWadmap Patch: 105800-05 Obsoletes: Requires: 106125-05 Incompatibles: Packages: SUNWadmap, SUNWadmc Patch: 106193-03 Obsoletes: 106350-01 Requires: Incompatibles: Packages: SUNWadmap Patch: 105800-06 Obsoletes: Requires: 106125-05 Incompatibles: Packages: SUNWadmap, SUNWadmc Patch: 106317-01 Obsoletes: Requires: Incompatibles: Packages: SUNWadmc Patch: 108660-01 Obsoletes: Requires: Incompatibles: Packages: SUNWadmfw Patch: 105363-05 Obsoletes: Requires: Incompatibles: Packages: SUNWxfb Patch: 105363-31 Obsoletes: Requires: Incompatibles: Packages: SUNWxfb Patch: 106123-01 Obsoletes: Requires: Incompatibles: Packages: SUNWdoc Patch: 106123-04 Obsoletes: Requires: Incompatibles: Packages: SUNWdoc Patch: 106262-01 Obsoletes: Requires: Incompatibles: Packages: SUNWman Patch: 106261-01 Obsoletes: Requires: Incompatibles: Packages: SUNWman Patch: 106260-01 Obsoletes: Requires: Incompatibles: Packages: SUNWman Patch: 106219-01 Obsoletes: Requires: Incompatibles: Packages: SUNWman Patch: 105390-02 Obsoletes: Requires: Incompatibles: Packages: SUNWman Patch: 106471-02 Obsoletes: Requires: Incompatibles: Packages: SUNWatfsr, SUNWatfsu, SUNWhea Patch: 105472-02 Obsoletes: Requires: Incompatibles: Packages: SUNWatfsu Patch: 105472-07 Obsoletes: Requires: Incompatibles: Packages: SUNWatfsu Patch: 106648-01 Obsoletes: Requires: Incompatibles: Packages: SUNWolrte, SUNWolslb Patch: 106649-01 Obsoletes: Requires: Incompatibles: Packages: SUNWolrte Patch: 105837-02 Obsoletes: Requires: Incompatibles: Packages: SUNWdtdte Patch: 105703-03 Obsoletes: Requires: Incompatibles: Packages: SUNWdtdte Patch: 105558-04 Obsoletes: Requires: 107434-01 Incompatibles: Packages: SUNWdtdte, SUNWdtdst Patch: 105837-03 Obsoletes: Requires: Incompatibles: Packages: SUNWdtdte Patch: 105703-22 Obsoletes: Requires: Incompatibles: Packages: SUNWdtdte Patch: 105566-01 Obsoletes: Requires: Incompatibles: Packages: SUNWdtdmn Patch: 105566-07 Obsoletes: Requires: Incompatibles: Packages: SUNWdtdmn, SUNWdtdst Patch: 105566-08 Obsoletes: Requires: Incompatibles: Packages: SUNWdtdmn, SUNWdtdst Patch: 108199-01 Obsoletes: Requires: Incompatibles: Packages: SUNWdtdmn Patch: 106138-01 Obsoletes: Requires: Incompatibles: Packages: SUNWoldst Patch: 105497-01 Obsoletes: Requires: Incompatibles: Packages: SUNWoldst Patch: 106222-01 Obsoletes: Requires: Incompatibles: Packages: SUNWoldst Patch: 106650-04 Obsoletes: Requires: 106648-01, 106649-01 Incompatibles: Packages: SUNWoldst Patch: 105377-03 Obsoletes: Requires: Incompatibles: Packages: SUNWbcp Patch: 105492-02 Obsoletes: Requires: 105181-05 Incompatibles: Packages: SUNWcg6 Patch: 105798-03 Obsoletes: Requires: Incompatibles: Packages: SUNWcpr Patch: 106112-01 Obsoletes: Requires: Incompatibles: Packages: SUNWdtdst Patch: 106025-01 Obsoletes: Requires: Incompatibles: Packages: SUNWdtdst Patch: 105558-01 Obsoletes: Requires: Incompatibles: Packages: SUNWdtdst Patch: 105338-07 Obsoletes: Requires: Incompatibles: Packages: SUNWdtdst, SUNWdthev, SUNWdtma Patch: 107434-01 Obsoletes: Requires: Incompatibles: Packages: SUNWdtdst Patch: 105338-25 Obsoletes: Requires: 107434-01 Incompatibles: Packages: SUNWdtdst, SUNWdthev, SUNWdtma Patch: 106112-05 Obsoletes: Requires: 105669-07 Incompatibles: Packages: SUNWdtdst Patch: 106437-03 Obsoletes: Requires: 105669-06 Incompatibles: Packages: SUNWdtdst Patch: 106027-01 Obsoletes: Requires: Incompatibles: Packages: SUNWdtwm Patch: 106027-08 Obsoletes: Requires: 106125-08 Incompatibles: Packages: SUNWdtwm Patch: 105360-10 Obsoletes: Requires: Incompatibles: Packages: SUNWffb, SUNWffbcf, SUNWffbw, SUNWffbxg Patch: 105360-34 Obsoletes: Requires: Incompatibles: Packages: SUNWffb, SUNWffbcf, SUNWffbw, SUNWffbxg Patch: 105591-09 Obsoletes: 101242-13 Requires: Incompatibles: Packages: SUNWlibC Patch: 105743-01 Obsoletes: Requires: Incompatibles: Packages: SUNWfns Patch: 105223-04 Obsoletes: Requires: 105181-05 Incompatibles: Packages: SUNWhea Patch: 105223-05 Obsoletes: Requires: 105181-05 Incompatibles: Packages: SUNWhea Patch: 106172-02 Obsoletes: Requires: 105181-05 Incompatibles: Packages: SUNWhmd Patch: 105795-03 Obsoletes: Requires: 105181-05 Incompatibles: Packages: SUNWhmd, SUNWhmdu Patch: 106172-04 Obsoletes: Requires: 105181-05 Incompatibles: Packages: SUNWhmd Patch: 106407-05 Obsoletes: Requires: Incompatibles: Packages: SUNWide Patch: 107336-01 Obsoletes: Requires: Incompatibles: Packages: SUNWkcsrt, SUNWkcspg Patch: 106064-01 Obsoletes: Requires: Incompatibles: Packages: SUNWnisu Patch: 105552-02 Obsoletes: Requires: Incompatibles: Packages: SUNWnisu Patch: 105403-01 Obsoletes: Requires: Incompatibles: Packages: SUNWnisu Patch: 105552-03 Obsoletes: Requires: Incompatibles: Packages: SUNWnisu Patch: 105403-03 Obsoletes: Requires: Incompatibles: Packages: SUNWnisu Patch: 108346-03 Obsoletes: Requires: Incompatibles: Packages: SUNWnisu Patch: 105741-02 Obsoletes: Requires: Incompatibles: Packages: SUNWpd Patch: 105580-05 Obsoletes: Requires: Incompatibles: Packages: SUNWpd, SUNWpdu Patch: 105741-07 Obsoletes: Requires: Incompatibles: Packages: SUNWpd Patch: 105580-15 Obsoletes: Requires: Incompatibles: Packages: SUNWpd, SUNWpdu Patch: 108091-03 Obsoletes: Requires: Incompatibles: Packages: SUNWplow Patch: 105637-01 Obsoletes: Requires: Incompatibles: Packages: SUNWpmu Patch: 106029-01 Obsoletes: Requires: Incompatibles: Packages: SUNWsprot, SUNWxcu4t Patch: 106029-04 Obsoletes: Requires: Incompatibles: Packages: SUNWsprot, SUNWxcu4t Patch: 106125-02 Obsoletes: Requires: Incompatibles: Packages: SUNWswmt Patch: 106125-08 Obsoletes: Requires: Incompatibles: Packages: SUNWswmt Patch: 106125-09 Obsoletes: Requires: Incompatibles: Packages: SUNWswmt Patch: 105426-01 Obsoletes: Requires: Incompatibles: Packages: SUNWtnfc Patch: 105407-01 Obsoletes: Requires: Incompatibles: Packages: SUNWvolu Patch: 107618-01 Obsoletes: Requires: Incompatibles: Packages: SUNWvolu Patch: 105189-02 Obsoletes: Requires: Incompatibles: Packages: SUNWxi18n Patch: 106040-13 Obsoletes: 105189-03 Requires: Incompatibles: Packages: SUNWxi18n, SUNWxim Patch: 106040-03 Obsoletes: Requires: Incompatibles: Packages: SUNWxim Patch: 105361-03 Obsoletes: Requires: Incompatibles: Packages: SUNWxilvl
Q. My existing CEMF and ObjectStore installations are configured to use a raw partition. How do I add more partitions to increase available space? (Products affected : CEMF 3.0.x)

A. To add partitions to the rawfs follow these steps (as root):

  1. Take note of the device partition(s) to be added, such as /dev/rdsk/c1t0d0s0 (consult your Systems Administrator if unsure)
  2. Ensure that CEMF has been shutdown, <CEMFROOT>/bin/cemf stop
  3. Ensure the environment variable OS_ROOTDIR reflects the ObjectStore install path (/opt/ODI/OS5.1/ostore)
  4. Shutdown ObjectStore, $OS_ROOTDIR/bin/ossvrshtd <hostname>
  5. Edit the $OS_ROOTDIR/etc/<hostname>_server_parameters file. Add a PartitionN for each new partition. See example below.
  6. Restart ObjectStore, $OS_ROOTDIR/lib/osserver. The new partitions are initialised
  7. Run osdf utility to show increased available space, $OS_ROOTDIR/bin/osdf <hostname>
Server parameter file example:
Log File: /opt/transact.log
Partition0: PARTITION /dev/rdsk/c0t0d0s0
Partition1: PARTITION /dev/rdsk/c1t0d0s0

Note: PartitionN statements can appear in the server parameter file in any order, but empty slots are not allowed. For example, if you have four partitions, they must be numbered 0 through 3.

Q. Why does my CEMF reset cause a hang at the Parsing Configuration [Types|Groups|Objects]... stage of a start? (Products affected : CEMF 3.x)

A. During an CEMF start that follows a reset, the system parses a number of files in the following directories:
 CEMFROOT/config/configuration/types
 CEMFROOT/config/configuration/groups
 CEMFROOT/config/configuration/objectSpecifications
 
The files in these directories define types/groups/objects that are essential to the system operation. They are only parsed on an initial CEMF startup or after a reset; after that the information is databased. After/during parsing of these files the system creates objects internally to hold this information.

Solution A

When multiple EMs are installed on a CEMF platform, it is possible that the system tries to create too many objects at once. You can control this by changing the following line in the CEMFROOT/config/init/objectSpecificationFileParser.ini file:

Change the line:

MaxPerContext = 1000
to
MaxPerContext = 100

Solution B

If any of the files in these directories is incorrect, in that it doesn't specify types/groups/objects, or if any of these files are duplicates and specify the same types/groups/objects twice, the system will likely fail to start.

Check these directories for core files, editor backup files, user copies of files etc. Any of these should be removed.

For either solution you must stop, reset, and start CEMF.

Q. Why do Mapviewer and Auto Discovery fail to launch from the launch pad unless I invoke a session as root? (Products affected : CEMF 3.x)

A. When your system reports the following error, "The X server has refused connection for this session," this is actually an incorrect and misleading message for the problem described above. The problem is that OPENWINHOME is not set. Ensure this is set and the value is correct for the installation path for openwin (normally /usr/openwin). Set it to this value if it is not.
Q. Why won't CEMF applications run when the OPENWINHOME environment variable is not set? (Products affected : CEMF 3.x)

A. The following error, "The X server has refused connection for this session" appears when the OPENWINHOME environment variable is not set. This error relates to xhost settings. It occurs when you attempt to run a CEMF session by remotely logging on to a client or manager installation and using the X DISPLAY variable to display back to your local machine. This is not a supported CEMF configuration and is not recommended. However, in a development environment it is often useful to allow xhost access in both directions between the the remote machine and your local machine. This can be achieved by running the following commands:
run: xhost +<REMOTECEMFHOSTNAME>   on your local machine and then 

run: xhost +<LOCALHOSTNAME>   on the CEMF client or manager. 
Note: If you experience problems when trying to run xhost on the remote machine, ensure that DISPLAY is set to the remote machine and that the X server is currently running. If you are still experiencing problems, consult the xhost documentation.

Q. Why does the CEMF session splash screen hang after I enter my user name and password? (Products affected : CEMF 3.x)

A. If the Solaris hostname of the client is wrongly configured, this can cause the CEMF session to hang (the splash screen and login open but hang after the username and password are entered). This is caused by the clients machine name being mismatched with its name in DNS. The following scenario highlights this problem:

  • On the client machine, hostname returns nameA.
  • On the Manager, doing an nslookup for nameA fails.
  • In DNS, the client machine is called nameB.

The workaround is to change the hostname in the following files to use nameB:

    :/etc/hostname.hme0
    /etc/hosts
    /opt/cemf/config/env/avCore.sh

Q. Why does CEMF fail to start up and displayed the error message, 'Failed to load process files?' (Products affected : CEMF 3.0.x)

A. This can be caused by the machine's hostname not being in /etc/hosts. The problem has been seen on machines not using NIS or DNS, only files. The solution is to ensure the hosts file is updated to include the machine's hostname.
Q. How do I control which CEMF processes are running? (Products affected : CEMF 3.0.x)

A. Run Levels

CEMF 3.x uses the concept of the run level. This is an integer in the range 1..2^31-1 that is assigned to a process. It controls the order of startup on an ascending run level basis, and shutdown on a descending run level basis.

  1. Querying processes on a run level basis

    A binary exists called sysmgrClient that allows interogation of all the processes currently being handled by the sysmgr on a per run level basis. It must be run within a CEMF shell.

    1. Querying multiple run levels

      In the CEMFROOT/bin directory, issuing the following command gives a list (to stdout) of all processes under sysmgr control between run levels 1 and 14. This includes information such as the state of the process, the run level for the process and its tag (that is, the name identifier for process):

      ./sysmgrClient -s 1 -e 14

      If the specified end level is higher than specified start level, start and end levels are swapped and the information displayed. If only one of -s or -e is specified, a default value of 1 is used for the start level and 2^31-1 for the end level. Therefore, entering the following command lists all processes under sysmgr control between run level 1 and 2^31-1:

      ./sysmgrClient -s 1

    2. Querying a single run level

      It is also possible to display information for a single run level. To displays information for any processes at run level 5, enter the following command:

      ./sysmgrClient -i 5

    3. Retrieving the current run level of the sysmgr

      Entering the following command retrieves the current run level of the sysmgr and logs to the sysmgrClient log file (and stdout) the current run level of the sysmgr:

      ./sysmgrClient -g

    4. Changing the current run level of the sysmgr

      To change the current run level of the sysmgr to 10, enter:

      ./sysmgrClient -r 10

      Setting the run level of the sysmgr has one of three effects:

      • Specifying a run level higher than the current run level causes the sysmgr to start any processes present within the sysmgr that are present between the old and new run levels.
      • Specifying a run level lower than the current run level causes the sysmgr to stop any processes present within the sysmgr that are present between the old and new run levels.
      • Specifying a run level equal to the current run level results in no change of state within the sysmgr.

  2. Loading/Unloading of processes

    The sysmgrClient binary may also be used to load and unload a set of processes (under sysmgr control) specified in a processes file.

    1. Loading processes

      To load a set of processes from a process file, the sysmgrClient binary can be used as follows:

      ./sysmgrClient -l <processes-file-or-directory>

      Specifying a directory of process files to be loaded into the sysmgr results in these processes being first added to the sysmgr and then started. Specifiying a single file loads that file only. Multiple files or directories are not currently supported.

      Processes are only added if they are not already present within the sysmgr (a comparison is performed on the process tag). Processes are only started if the current run level of the sysmgr is less than or equal to the run level of the process.

    2. Unloading processes

      To unload a set of processes from a process file, the sysmgrClient binary can be used as follows:

      ./sysmgrClient -u <processes-file-or-directory>

      Specifying a directory of process files to be unloaded from the sysmgr results in these processes being stopped and then removed from the sysmgr. Specifiying a single file loads that file only. Multiple files or directories are not currently supported.

      Processes are only stopped or removed if they are present within the sysmgr.

      Note: If a run level is specified while trying to load or unload a set of processes, the run level is set before the loading or unloading operations are performed.

  3. Stopping/Starting processes by name

    Note: The name used by sysmgrClient is not the name of the process binary. sysmgrClient uses the name tag of the process that is specified within the appropriate process file in the <CEMFROOT>/config/processes directory (that is, name Coordinator).

    The sysmgrClient binary can be used to start and stop processes (under sysmgr control) simply by specifying the process name. For example, if you interrogate the sysmgr using the sysmgrClient by entering the following command:

    ./sysmgrClient -s 0

    You are presented with the following processes:

    PE::tag=Coordinator,stat=running,le=10,path=coordinator,arg=,pid=11705
    PE::tag=DeploymentEventChannelHost,stat=running,le=10,path=eventChannelHost,arg=DeploymentEventChannelHost,pid=11312
    PE::tag=MOAttributeEventChannelHost,stat=running,le=10,path=eventChannelHost,arg=MOAttributeEventChannelHost,pid=11313

    You may stop or start any one of these processes as follows:

    1. Stopping a process by name

      Using the example above, to stop the Coordinator process, enter:

      ./sysmgrClient -k Coordinator

      Note that the process name specified should be the tag of the process and not the name of the binary. The name of the binary can be found by entering:

      ./sysmgrClient -s 0

      The -k flag was chosen to indicate (k)illing of a process. Performing a ./sysmgrClient -s 0 command lists the processes as:

      PE::tag=Coordinator,stat=stoppedByClient,le=10,path=coordinator,arg=,pid=0 
      PE::tag=DeploymentEventChannelHost,stat=running,le=10,path=eventChannelHost,arg=DeploymentEventChannelHost,pid=11312
      PE::tag=MOAttributeEventChannelHost,stat=running,le=10,path=eventChannelHost,arg=MOAttributeEventChannelHost,pid=11313
       

      Note the change in state of the Coordinator.

    2. Starting a process by name

      Using the above example of a stopped process, you can start it again by entering:

      ./sysmgrClient -x Coordinator

      The -x flag was chosen to indicate e(x)ecution of a process. Performing a ./sysmgrClient -s lists the processes as:
      PE::tag=Coordinator,stat=running,le=10,path=coordinator,arg=,pid=11400 
      PE::tag=DeploymentEventChannelHost,stat=running,le=10,path=eventChannelHost,arg=DeploymentEventChannelHost,pid=11312 
      PE::tag=MOAttributeEventChannelHost,stat=running,le=10,path=eventChannelHost,arg=MOAttributeEventChannelHost,pid=11313 
      Again, note the change in state of the Coordinator.

      Note: Process starting/stopping by name has no effect on the run level of the sysmgr. Also, process starting/stopping by name operations are incompatible with all other operations that can be performed using the sysmgrClient. For example:

      ./sysmgrClient -x Coordinator -r 10

      Would be an invalid set of operations to perform, and the sysmgrClient would exit with the error message:
      Process kill operation incompatible with other operations, exiting!

  4. Usage options for sysmgrClient

    By typing the following command:

    ./sysmgrClient -h

    A usage help screen is displayed as follows:
    ./sysmgrClient
    [-c] check files only
    [-l <process-file-or-directory>] start and load processes specified in files
    [-u <process-file-or-directory>] stop and unload processes specified in files
    [-r <int-level>] set the run level
    [-g] get the current run level (output to logger)
    [-s <int>] start level to display processes under sysmgr control
    [-e <int>] end level to display processes under sysmgr control
    [-q] shutdown sysmgr
    [-k <process-name>] kill specified process.
    [-x <process-name>] execute specified process.

Related Information


Updated: Jan 31, 2006
Document ID: 24869