If you are upgrading an FSE server, invoke the following commands:
#rpm
#rpm
In both cases, the second rpm command installs the FSE utilities: HSM Health Monitor and Log Analyzer.
If you are upgrading the FSE release 3.4 with an FSE system maintenance release or an FSE hot fix for this release, perform the following procedure to appropriately install the software on the consolidated FSE system or FSE server:
•At the command line, change the current directory to the one with the installation packages. Install all required FSE system maintenance release or FSE hot fix RPM packages with one invocation of the rpm command.
If you are upgrading a consolidated FSE system, invoke the following command:
#rpm
If you are upgrading an FSE server, invoke the following command:
#rpm
Starting up the FSE server
On the consolidated FSE system or the FSE server, you need to start the FSE processes. Depending on the type of the FSE host, you may need to perform additional steps after the startup. These steps are required because of a changed format of the FileSystemID parameter in the FSE partition configuration files.
Follow the procedure:
1.Run the fse
#fse
Consolidated FSE system
Starting omniORB Naming | Service: | [ | OK | ] |
Starting FSE Service: |
| [ | OK | ] |
Starting FSE Resource Manager: | [ | OK | ] | |
Starting FSE Management | Interface: | [ | OK | ] |
Installing HSMFS Filter | module: | [ | OK | ] |
Loading HSMFS Filter module: | [ | OK | ] | |
Starting HSM FS Event Manager: | [ | OK | ] | |
Mounting HSM File Systems: | [ | OK | ] |
FSE server
Starting | omniORB Naming Service: | [ | OK | ] |
Starting | FSE Service: | [ | OK | ] |
58 Upgrading from previous FSE releases