Table 158 Troubleshooting Firewalls (continued)

Configur-

Manual Start

If Mentioned in

Step 1 Discovery

ation

Parameters

cim.extension.parameters

and

 

for CIM Extension

 

RMI Registry

 

 

 

Port

 

 

 

 

No DNS, never

 

jboss.properties

Any IP that is

resolve.

 

cimom.Dcxws.agency.firstw

reachable

 

 

ait=200000

Communication Port:

 

 

cimom.Dcxws.agency.timeo

 

 

4673

 

 

ut=200000

 

 

 

 

 

No firewall.

start -credentials

-credentials abcuser:passwd

Specify abcuser

Don't want to

abcuser:passwd

 

and password in

use root

 

 

the discovery list.

credentials.

 

 

Communication Port:

Want to

 

 

 

 

4673

discover with a

 

 

 

 

 

non-existent

 

 

 

user.

 

 

 

 

 

 

 

With 3 firewall

start

-on10.250.250.10:1234

10.250.250.10:12

ports opened on

-on10.250.250.10:1234

-on172.31.250.10:5678

34 OR

different ports

-on172.31.250.10:5678

-on 192.168.250.10:

172.31.250.10:56

respectively

-on192.168.250.10:9012

9012

78 OR

1234, 5678,

-credentials abcuser:passwd

-credentials abcuser:passwd

192.168.250.10:9

9012. Don't

 

 

012.

want to use root

 

 

Specify abcuser

credentials.

 

 

 

 

and passwd in the

Want to

 

 

 

 

discovery list.

discover with a

 

 

 

 

Communication Port:

non existent

 

 

user.

 

 

1234, 5678, 9012

 

 

 

 

 

 

 

Volume Names from Ambiguous Automounts Are Not Displayed

Volume names from ambiguous automounts on Solaris hosts are not displayed on the Storage Volumes page or in Capacity Manager. Some Solaris hosts have autofs and NFS mounted through an automounter. The management server cannot display volume names from ambiguous automounts because it cannot determine if the comma-separated strings that are part of the mounted volume name are host names or part of the name of a remote volume.

698 Troubleshooting