Parameter

Description

 

 

CFG_FILE

Specifies the location for the FSE implementation services configuration file.

 

Linux specific

 

On Linux platform, the default full pathname of the file is

 

/etc/opt/fse/services.cfg.

 

Windows specific

 

On Windows platform, the default full pathname of the file is

 

%InstallPath%\etc\services.cfg.

 

 

DEBUG_LEVEL

Specifies the logging level information for the FSE Management Console

 

server (for details, see ”Configuring the logging level” on page 27). The

 

setting can be overridden by specifying the corresponding command line

 

option when starting the FSE Management Console server.

 

The default value is d1 -DAll.

 

 

OMNIORB_CONFIG

Specifies the location of the omniORB.cfg file.

 

The usage of the omniORB.cfg file is required on each host with:

 

• more than one active network adapter.

 

• private network communication as the means for data transfer in the FSE

 

implementation.

 

For details on how to configure the omniORB.cfg file, see chapter

 

”Configuring FSE”.

 

This option does not have default value.

 

Linux specific

 

Default location of the omniORB.cfg file is the directory /etc/opt/fse.

 

Template of the omniORB.cfg file resides in the directory

 

/opt/fse/newconfig.

 

Windows specific

 

Default location of the omniORB.cfg file is the directory

 

%InstallPath%\etc. Template of the omniORB.cfg file resides in the

 

directory %InstallPath%\newconfig.

 

Location of the omniORB.cfg file can also be specified with the

 

OMNIORB_CONFIG environment variable. You must set the variable before

 

starting the FSE Management Console server or FSE Management Console

 

client.

 

 

ORB_ARGS

Specifies the command line parameters that are passed to the omniORB

 

binary.

 

The default value is -ORBendPoint giop:tcp::4055.

 

 

Configuring the logging level

Both the FSE Management Console server and the FSE Management Console client can be configured to log their activities to log files. A specific path and filename can be defined using the corresponding configuration file parameters or they can be specified in the appropriate command line options.

Logging is done according to the specified debug level, which is encoded by two parameters: -dLeveland -DObject

#Argument for debug level after the option -d can be either integer or literal:

0 No - no trace information (default value)

1 Err - only errors

2 Wrn - errors and warnings

3 Inf - errors, warnings, and trace

HP StorageWorks File System Extender Software user guide 27