Unable to Register a Sun Storage F5100 Array in Sun Storage Common Array Manager with a Large SAN and/or SAS Environment

Asset ID:	1-72-1634429.1
Update Date:	2017-07-17
Keywords:

Solution Type Problem Resolution Sure

Solution 1634429.1 : Unable to Register a Sun Storage F5100 Array in Sun Storage Common Array Manager with a Large SAN and/or SAS Environment

Applies to:

Sun Storage Common Array Manager (CAM) - Version 6.0 and later
Sun Storage J4200 Array - Version All Versions and later
Sun Storage J4500 Array - Version All Versions and later
Sun Storage J4400 Array - Version All Versions and later
Sun Flash F5100 Array - Version All Versions and later
Information in this document applies to any platform.

Symptoms

Sun Storage Common Array Manager (CAM) Browser User Interface (BUI) does not find any F5100 during the registration. When using the CAM CLI command ras_admin discover_subnet -I <proxy agent server IP> -D, it returns the error "No supported devices found at IP address <proxy agent server IP>".

Example:

# ras_admin discover_subnet -I myserver -D
Discovery task started with job id=process:2014.03.10.14.42.50.648

Starting IP discovery at address myserver
SNMP System Description is (SunOS pp11z1zg 5.10 Generic_147440-19 sun4u) at IP address myserver
Attempting to probe 6780_erie
myserver: 6780_erie Probe result = #ARG_ERROR
No CSM found at pp11z1zg
Attempting to probe 2510_exmoor
myserver: Not a 2510_exmoor
Attempting to probe b6000
date
myserver: b6000 Probe result = #ARG_ERROR
No JBODs found
Attempting to probe j4500
Attempting to probe j4400
Attempting to probe j4200
Attempting to probe 6180
myserver: Not a 6180
Attempting to probe nem
Attempting to probe f5100
No supported devices found at IP address myserver

Task completed successfully.

When looking at the fms log file, the error "java.lang.StackOverflowError" is present.

Where the fms log files are located at:

For Solaris: /var/opt/SUNWsefms/log/fms.[0-9]
For Linux: /var/opt/cam/log/fms.[0-9]
For Windows: c:\program files\sun\common array manager\component\fms\var\log\fms.[0-9]

Example:

# cat /var/opt/SUNWsefms/log/fms.0
Mar 10, 2014 5:00:42 PM com.sun.netstorage.fm.storade.device.storage.jbod.JbodProbe probeUtil
INFO: JBOD Probe Started
Mar 10, 2014 5:00:42 PM com.sun.netstorage.fm.storade.device.storage.host.APIManager getInstance
INFO: APIManager semaphore acquired by: Thread[jobs.discovery,5,main]
Mar 10, 2014 5:21:03 PM com.sun.netstorage.fm.storade.device.storage.jbod.JbodProbe probeUtil
INFO: JBOD API connected
Mar 10, 2014 5:21:03 PM com.sun.netstorage.fm.storade.device.storage.jbod.JbodProbe probeUtil
INFO: Error processing APIManager throw t
java.lang.StackOverflowError

Cause

The default FMS stack size might be too low for large SAN and/or SAS environments.

Solution

Below are the steps for increasing the heap and stack of FMS services JVM to Xmx=512m (for heap) and Xss=1024k (for stack).

For Solaris

Stop FMS:

For Solaris 8 and 9

# /opt/SUNWsefms/sbin/fmservice.sh stop

For Solaris 10

# svcadm disable fmservice
Edit the file /opt/SUNWsefms/sbin/fms as below:

Before:
FMS_JAVA_PARAMS="-Xmx128m -D${FMS_PKG}=${FMS_HOME}"

After:
FMS_JAVA_PARAMS="-Xmx512m -Xss1024k -D${FMS_PKG}=${FMS_HOME}"
Start FMS:

For Solaris 8 and 9

# /opt/SUNWsefms/sbin/fmservice.sh start

For Solaris 10

# svcadm enable fmservice

For Linux

Stop FMS:

# /opt/sun/cam/private/fms/sbin/fmservice.sh stop
Edit the file /opt/sun/cam/private/fms/sbin/fms as below:

Before:
FMS_JAVA_PARAMS="-Xmx128m -D${FMS_PKG}=${FMS_HOME}"

After:
FMS_JAVA_PARAMS="-Xmx512m -Xss1024k -D${FMS_PKG}=${FMS_HOME}"
Start FMS:

# /opt/sun/cam/private/fms/sbin/fmservice.sh start

For Windows

Stop FMS:

net stop Sun_STK_FMS
Edit the file C:\Program Files (X86)/Sun/Common\ Array\ Manager/Component/fms/System/wrapper.conf as below:

Before:
wrapper.java.maxmemory=128

After:
wrapper.java.maxmemory=512
wrapper.java.additional.11=-Xss1024k
Start FMS:

net start Sun_STK_FMS

Attachments

This solution has no attachment