adobe fireworks cs4 download gratisadobe indesign 2 0 free download macadobe director 11 keygen downloadbibleworks 9 iso download
Now theres a fun way to manage your storage environment. Oracles Sun Storage Common Array Manager software comes with a common, simple-to-use interface to your Sun Storage arrays. The software takes the complexity from storage management, assisting you to accelerate deployment, simplify your environment, and improve utilization.
Join the worlds largest community of application developers, database admins, system admins/developers, and architects using industry-standard technologies along with Oracle products.
Oracles partner community in excess of 20, 000 partners including 1, 000 specialized partners offers you solutions and services that meet your business needs.
Sales: 1.800.633.0738 Users serious about Download common array manager 6.7 generally download:
One Interface, Run-Anywhere Flexibility
Now there s a fun way to manage your storage environment. Oracle s Sun Storage Common Array Manager software supplies a common,
The aggregate score in line with the apps rating, quantity of users, and a variety of other parameters closely associated with user satisfaction.
The greatest score is 10.
Download common array manager 6.7 google search
Additional strategies for Download common array manager 6.7 by our robot:
Drag the slider to create how much the chosen parameter Overall score improves an apps position inside search results.
Comprehensive utility to examine, browse, convert, enhance, and edit your images.
a nice assortment of image viewing, management, comparison, the most prevalent RAW
Open, extract, burn, create, edit, compress, encrypt, split convert ISO files.
Effortlessly search through your photo collections and take annoying image defects immediately.
image editors, managers, this kind of array applying some common color corrections
Portable code librarian document manager to securely store your computer data.
All-in-one optimization tool to speed up and transform your PCs performance.
Having a wide range of the most commonly Hard Disk Manager, among many
Tiny anti-virus tool meant to get rid of autorun and trojans.
most of common antivirus having a wide assortment of, the duty manager, or to
Intuitive desktop manager and typing assistant that improves your productivity.
the common the manager, a virtual desktop, a clipboard manager, information manager
It can be a really easy, fast, and reliable video converter.
Full-featured photo and image editor with support for some well-known formats.
Portable multi-tabbed file manager with strong file search and preview.
tabbed file manager featuring and an assortment of image all common formats, audio
Video4Web Converter can be a totally free video to flash video converter.
of layout commonly found digital right management. What discover a wide variety of formats
Go paperless with MIE Kiosk Data Collection and Whiteboard Scheduling Software.
SBench can be a powerful and intuitive interactive measurement software.
on a standard API specific window manager. Main RAID disk arrays - Designed
Convert CGM files to GIF, JPEG, PNG, TIFF plus more.
illustrations into common digital asset management or storage arrays. Larson
CCleaner is just about the best tools for cleaning your PC of unwanted files.
10, 415 votes 88 commented
Sun StorageTek Common Array Manager Software Release Notes, Release 6.0.1
This document contains information and facts about Release 6.0.hands down the Sun StorageTek Common Array Manager software, including issues and also that can affect installation and operation.
The Sun StorageTek Common Array Manager software offers an easy-to-use interface that you can configure, manage, and monitor Sun StorageTek storage arrays.
TABLE 1 lists the version information for your software one of them release.
To use optional premium features, you have to purchase licenses. When you order licenses, they shall be sent to you with instructions in order to activate the options. For additional information, look for these topics within the online Help:
TABLE 2 Available Licenses for Premium Features, by Array
Combo Data Snapshot, Data Volume Copy, Data Replicator, and 64 Domains
Combo Data Snapshot, Data Volume Copy
Combo Data Snapshot, Data Volume Copy, and Data Replicator
Following is usually a list of documents relevant to the Sun StorageTek Common Array Manager. For any document number with nn being a version suffix, use by far the most current version available.
In addition, the Common Array Manager software includes online Help and man pages for CLI commands.
For hardware information, consider the arrays release notes and hardware installation guide. You can look for this documentation at
documentation.
New to your Sun StorageTek CAM software in release 6.0.1 is Internet Small Computer Systems Interface iSCSI support to the Sun StorageTek 2510 storage system. Initiators include the clients with the iSCSI interface, issuing requests for services from components or logical units called targets. One iSCSI target is supported per array.7
The iSCSI port is needed for communication between iSCSI initiator as well as the iSCSI target. The array supports two iSCSI ports per controller, for any total of four years old per array.
An iSCSI session contains up to four connections between an initiator and its particular target. The iSCSI initiator and target send and receive data over an Ethernet connection, while using SCSI protocol. Across all connections in a session, an initiator sees the identical target. Multiple initiators could be connected towards the iSCSI target.
Note - For initial installation and configuration of iSCSI about the 2510, view the Sun StorageTek 2500 Series Array Installation Guide.
Note - For the complete number of drives, reference Table 5 inside Sun StorageTek 2500 Series Array Release Notes, Version 1.3.
Consult the Sun StorageTek Common Array Manager software online Help for more information and procedures, including configuring iSCSI targets and ports, mutual authentication on an iSCSI session, unnamed discovery sessions, and Internet Storage Name Service iSNS, plus much more.
CAM software runs within the platforms described in TABLE 3.
TABLE 4 lists Solaris packages that needs to be installed on your Solaris host. Installing the minimum Solaris os package as classified by TABLE 3 will install almost the last four files. Those files are important by Java, but are not utilised by the management software.
TABLE 5 lists Linux packages and libraries that really must be installed on your Linux host. The 32-bit versions from the packages and files are important.
For the modern patches available on your system, check SunSolve at
TABLE 6: lists the patch numbers and corresponding platforms.
TABLE 7 lists the disk and directory space requirements.
Open these incoming and outgoing ports for secure-by-default Solaris, Linux, and Windows platforms. In Windows, reference your firewall documentation for instructions regarding how to open a port with the firewall:
The remote scripting command-line interface client sends commands into a management host, which experts claim sends the commands to your array. TABLE 8 lists remote platforms that will run the CLI client.
For best internet browser performance while utilizing the Sun StorageTek Common Array Manager software, do this:
Specify No Proxy to the Common Array Manager host, to protect yourself from situations where your browser might hang, day out, or generate incorrect error messages. From Preferences Advanced Proxies or even a similar path, dependant upon your browser, add the Common Array Manager management host name for the No Proxy for section.
Be conscious Firefox and Mozilla browsers share session information: If you signing in to Common Array Manager after which open another browser instance or tab pointed towards the same URL, you hop on through precisely the same user session, so you don't have to visit again. The Current Logins field inside Common Array Manager isn't going to increment to feature the new window as another login. Therefore, when you require some other user session, you need to define an alternative profile or join from an alternative machine. This isn't going to happen with Microsoft Internet Explorer browsers, so you'll be able to also open a different session by using their browser.
For Solaris, Linux and Windows, the browser user interface with the Sun StorageTek Common Array Manager can be found in:
The array installation procedures are described inside the Sun StorageTek Common Array Manager Software Installation Guide part number 820-0213-nn. This section describes release-specific steps for firmware and management software patch upgrades that you have to perform:
Before you perform a setting up procedure, do this:
1. Locate the management software.
2. Locate by far the most current patches.
3. Verify which you have license certificates for everyone premium features, including storage domains.
4. Read cellular phone instructions.
Solaris and Linux or as being a user with administrator privilege Windows for the management host.
6. Note that before beginning the installation script, the CD verifies host requirements, including the following:
Unsupported versions of related software including Common Array Manager 4.x, Storage Automated Diagnostic Environment 2.x and unsupported versions in the sscs CLI
If the host meets the needs, the script will seek out earlier versions and figure out if a brand new installation or perhaps an upgrade/baseline installation is essential. If the script detects there's no earlier version installed, it's going to perform a complete new installation.
Note - Before you install CAM in a very sparse-root zone, install Lockhart 3.0.4 having its L10N packages inside the global zone.
Note - For Solaris 10, tend not to attempt to perform the Lockhart setup script when logged to the local zone. The CAM installation prevents this. Either install Lockhart in a whole root zone or install/upgrade Lockhart from the global zone before installing CAM in to the local zone.
Solaris: Upgrades from CAM 5.0.0.8, 5.0.1.1, 5.0.2.1, 5.1.0.10, 5.1.0.11, 5.1.1.2, 5.1.2.2, and 5.1.3.2 for this release are supported. You are not instructed to uninstall the present CAM version before installing this release.
Linux: Upgrade to your initial release on the Linux version isn't needed.
Windows: Upgrade for this build just isn't supported in 64-bit Windows 2003. Uninstall of previous CAM version is needed before installing this build in 64-bit Windows 2003. In other Windows platforms, upgrade to the present build is supported.
If installation failure occurs, examine the available disk space.
For details, consult mobile phone log:
1. Log in on the CLI within the management host or utilizing the remote CLI client as documented inside Sun StorageTek Common Array Manager Software Installation Guide part number 820-0213-nn.
2. Navigate on the appropriate directory to your operating system:
For Solaris and Linux, navigate to:
var/opt/CommonArrayManager/HostSoftware6.0.0.10/bin/uninstall
For the Suse 9 platform, CLI uninstall requires this rpm packages:
The command will get rid of the current installation.
If you're installing the management software on a whole new host, adhere to the entire installation and configuration procedure described within the Sun StorageTek Common Array Manager Software Installation Guide part number 820-0213-nn.
After initial installation and configuration, you'll be able to upgrade the management software and firmware with each release.
You can carry out a minimal installation that permits only command-line interface CLI functionality. This feature is completely new in release 6.0.1. Array firmware files usually are not installed using this type of option. Because firmware just isn't installed, the firmware analysis feature is just not available using this installation.
The CLI in past versions of Sun StorageTek Common Array Manager software required the world wide web server in order to operate. Minimal installation isn't going to require the online world server to get running so that you can function which is limited to calls around the management host the location where the management applications are installed.
The sscs command behaves normally, with these exceptions:
The local-only version of sscs requires administrator privileges in order to operate. There is no guest version in the local sscs command for read-only data.
The local-only version of sscs login and sscs logout commands usually do not provide value since function is not really required.
The sscs login command will not likely query for your user name or password.
The local-only sscs version command will undoubtedly print the version with the current CAM installation.
The CLI-only install options will never install or configure the Sun Web Console software. Even once the Sun Web Console has already been installed and running for the host system, mobile phone will not modify or configure the Sun Web Console.
1. From the Common Array Manager Installation page, select one of those options inside Select a feature bundle list:
Command-Line Only with Firmware management host software; CLI for local users, remote users, and remote management host; array firmware
Command-Line Only management host software; CLI for local users, remote users, and remote management host
2. Click Next and adhere to the prompts by pressing 1 for Next, 3 to Cancel, or 5 to Redisplay.
finalizes the Vital Product Data Registry.
The system will notify you that not hard to install has been successful.
3. Press 3 to Finish or 5 to Redisplay.
1. From the host software installer, select Uninstall.
The system will notify you the un-installation has become successful.
This section describes the key features from the firmware, including the subsequent:
To add trays with data already to them, call your service representative for assistance to protect yourself from data loss.
Controller firmware 06.19. x.x or better allows tray mixing of 6540, 6140, 6130, FLX240, FLX280, and FLX380 array controllers modules along with the Sun StorageTek CSM100, CSM200, FLA200, FLC200, and FLA3 expansion modules. After installing the firmware, 6130 controllers will use CSM200 expansion modules and CSM100 expansion modules can be employed with 6540 and 6140 controllers.
When you add a brand new CSM200 expansion module for an existing array inside a production or active environment, it's advisable practice to cable and add the trays even though the RAID controller module is powered on.
Before connecting any replacement drive or additional expansion module with an existing functioning array, it's wise practice get in touch with Sun Microsystems Support Services. One reason just for this is to protect yourself from issues relevant to DACstore, the configuration and status database maintained because of the array firmware, that stores its home elevators each from the disk drives.
Because corrective actions for the DACstore issue may call for a configuration restoration, you should maintain a current image with the configuration. And, keep in mind, it's wise practice to help keep recoverable backups of your computer data.
Supported Expansion Modules with Controller Firmware 06.19.25.16
CSM100, CSM200, FLA200, FLC200, FLA300
The Sun StorageTek 2500 Series Array uses Controller Firmware 6.17.52.10 and props up Sun StorageTek 2501 expansion module.
The Sun StorageTek FLX240, FLX280, and FLX380 arrays use Controller Firmware 6.19.25.26 and props up CSM100, CSM200, FLA200, FLC200, and FLA300 expansion modules.
TABLE 12 Supported Expansion Module - Sun StorageTek FLX240, FLX280, and FLX380 Arrays
For the most recent patches available for the system, check SunSolve at:
Within your directory where you installed the firmware, a README apply for each array type define the firmware baseline.
defines the firmware baseline to the Sun StorageTek 2500 Series Arrays.
defines the firmware baseline with the Sun StorageTek 6130, 6140, 6540, FLX240, FLX280, and FLX380 arrays.
TABLE 13 lists the firmware just for this release of Sun StorageTek Common Array Manager software.
Sun StorageTek 6540, 6140, and 6130 Arrays
Sun StorageTek Flexline 240, 280, and 380 Arrays
Check the build notes file distributed while using software for your exact firmware build. The Sun StorageTek Common Array Manager software will support one prior version with the firmware for legacy features on previously supported arrays. This does yet apply to your new Sun StorageTek 2500 Series Arrays.
In the next tables, the file path listed inside the Firmware File column for instance, would be the relative path for the
subdirectory the place that the firmware files can be found.
TABLE 18 lists the controller information for that Sun StorageTek 6130, 6140, 6540, FLX240, FLX280, and FLX380 arrays.
TABLE 18 Sun StorageTek 6130, 6140, 6540, FLX240, FLX280, and FLX380 Array Controller Information
TABLE 19 lists the NVSRAM information for your Sun StorageTek 6130, 6140, 6540, FLX240, FLX280, and FLX380 arrays.
TABLE 19 Sun StorageTek 6130, 6140, 6540, FLX240, FLX280, and FLX380 Array NVSRAM Information
TABLE 20 lists the IOM information to the Sun StorageTek 6130, 6140, 6540, FLX240, FLX280, and FLX380 arrays.
TABLE 20 Sun StorageTek 6130, 6140, 6540, FLX240, FLX280, and FLX380 Array IOM Information
TABLE 21 lists the disk drive information for your Sun StorageTek 6130, 6140, 6540, FLX240, FLX280, and FLX380 arrays.
TABLE 21 Sun StorageTek 6130, 6140, 6540, FLX240, FLX280, and FLX380 Array Disk Drive Information
The Install Firmware Baseline function is available like a separate feature inside Sun StorageTek Common Array Manager software. The software prompts you in the event the arrays firmware needs for being upgraded. It is just not necessary to uninstall the prevailing firmware before after that procedure.
Prerequisite: Before you perform an expert, make sure the array is not within a degraded state. If it truly is degraded, the upgrade will fail.
1. Log in to your management software as documented inside Sun StorageTek Common Array Manager Software Installation Guide part number 820-0213-nn.
2. From the Java Web Console page, click Sun StorageTek Common Array Manager.
3. From the Storage System Summary page, find the array which is why the firmware needs for being installed/upgraded.
4. Click the Install Firmware Baseline button, and stick to the prompts.
Controller firmware allows tray mixing of array controllers modules, two versions of expansion modules with the Sun StorageTek 6130, 6140, and 6540 arrays, as well as the FLX240, FLX280, and FLX380 arrays.
Mixing trays isn't supported to the Sun StorageTek 2500 Series Arrays.
A patch is designed for Release 6.0.1 that contributes support for the third expansion tray and 48 drives. Cabling instructions to the third expansion tray have yet to be added to Sun StorageTek 2500 Series Array Hardware Installation Guide or Service Advisor inside Sun StorageTek Common Array Manager software.
Note - Before installing the 48-drive patch, be on the firmware baseline of 06.70.42.10.
Prerequisite: Before discovering a Sun StorageTek FLX240, FLX280, FLX380 array using Common Array Manager and before performing any tray migration as an example, adding FLA300 expansion trays behind an active 6130, 6140 or 6540 controller, you have to use existing management software to upgrade the arrays and associated trays to your firmware version 6.19.25.00. After you register the arrays using Common Array Manager, it is possible to upgrade to your current baseline firmware, 6.19.25.26.
1. Before cabling the newly supported expansion module, upgrade the present controller and trays.
To add a preexisting expansion tray with a new array, it truly is safest to adhere to a similar procedure:
1. Install the brand new controller and trays.
2. Perform the firmware upgrade.
1. Do not cable the added expansion tray.
2. Install the Common Array Manager release following standard installation procedure.
There are separate procedures for Solaris, Windows, and Linux management hosts. The software update places a copy with the latest firmware within the management software server.
For CSM100 trays, you have to manually set the tray IDs.
3. Register the array, as required.
4. From the Storage Summary page or Array Administration page, go through the Install Firmware Baseline button.
6. Use Service Advisor to cable any additional expansion tray and add it to your array.
7. Upgrade the array again to update the firmware within the new tray.
Each release or patch from the Sun StorageTek Common Array Manager software spools the most recent firmware within the management host in the software or patch installation. When you register an array together with the management software, it sends an alarm in case you need to upgrade/install the baseline for your firmware. To begin the process: From the Storage System Summary page or Array Administration page, go through the Install Firmware Baseline button. For more info, see Upgrading Array FirmwareInstalling the Firmware Baseline.
In the unlikely event that updating the firmware on a variety results in a very performance or operational issue, you might like to revert back for the previous version on the array firmware by either rolling back towards the previous version with the management software or backing your firmware patch then performing the Update Array function. Rollbacks or backouts should be planned beforehand and implemented using tools and functions with the operating system for the management software host.
Each host platform that props up Sun StorageTek Common Array Manager software offers its facilities and methods some by third-party for applying and backing out updates to installed software. On Solaris, one example is, Live Upgrade may be used to perform upgrades of installed software such how the user can revert back for the previous version from the software by re-activating the first sort environment and rebooting. Solaris may also apply and backout patches over the use in the
Refer on the operating system documentation for details about implementing software rollback features. Such practices really should be part of comprehensive software lifecycle management procedures and policies for ones production environment.
The following sections provide info on known issues and recommended workarounds, along with operational information not found elsewhere within the documentation:
Bug 6590617 -Since the Sun StorageTek 6130 array will not report asset data for your cache backup batteries, the management software inserts a dash - as opposed to a value inside the Unique Identifier field on Component Summary for Battery page Troubleshooting FRUs Battery.
Workaround - Use the sscs CLI service command to control data channels 3 and 4.
Bug 6621713 -The first step with the array registration wizard has evolved from Scan Network to Scan Local Network and also the auto-discovery mechanism is improved to become faster and even more versatile. The system scans the neighborhood network for available storage systems that will not be yet registered. This shortens enough time it takes to scan a nearby network for storage systems, depending for the given IP addresses. When this process is complete, a listing of discovered storage systems is displayed.
Bug 6590637 -Attempting to switch the Cache Start% and Cache Stop% parameters through the arrays Administration page so the value sent to Cache Stop% is higher than the value sent to Cache Start% results inside error message setCacheParams operation failed:43.
Workaround - Use valid values. Since the Cache Stop% would be the percentage of unwritten data inside cache that can stop a cache flush that may be currently happening, it should not be over the value for Cache Start%, which may be the percentage of unwritten data from the cache which will trigger a cache flush.
Bug 6600387 -Some jobs, like volume creation jobs, are not cancelled for the array if they have started. However, if multiple tasks are queued up with an array, any job within the queue could be cancelled prior to array actually starts the task.
If you create management objects while an import array job is running, it will interfere together with the import. Be sure that everyone who uses the destination array isn't going to modify or create any objects including volumes, initiators, mappings, and so on as the import is beginning.
Bug 6649629 -When information is collected along with a drive is by-passed, one controllers might reboot. This can also happen when a variety containing a drive that was portion of a virtual disk is taken off while support info is collected. When support information is captured, file can also be captured. file posesses a set of shell commands which can be run for the controller. The hids 108 command, put in release 6.0, can reboot the controller when run while a drive inside a system is by-passed, or any time a drive that was portion of a virtual disk is physically removed.
Workaround - Avoid collecting support data at times of heavy use. The controller reset is only going to occur upon the capture on the support data. Individual collections of Alarms, Array Profiles, and Major Event Logs are possible within each with the management utilities. There is no completely successful workaround presently and this issue remains under investigation.
Bug 6592811 -For small virtual disks, disk defragmentation jobs may complete too quickly for any job task to become created and listed around the Jobs Summary page. If an oversight does occur during execution, the person will be notified.
Workaround -Run defragmentation jobs utilizing the CLI.
Bug 6515237 -Common Array Manager doesn't allow the disk drive order being specified during volume creation.
Bug 6498717 -When developing a data replication set, should the primary array cannot communicate together with the secondary array, a misleading error message displays stating that it can be unable to get volume candidate list from array.
Workaround - Verify that this arrays can communicate before replicating data.
Bug 6590097, 6577775, 6592717, 6592703 -Using an invalid array password may result in configuration error messages.
Bug 6661200 - Lockhart 3.0.4 is not installed or upgraded inside a sparse-root zone.
Workaround - Before you install CAM within a sparse-root zone, install Lockhart 3.0.4 which consists of L10N packages inside the global zone.
Bug 6600387 - When a long job is running, for instance large volume creation, the Cancel checkbox won't display on current job status. Some jobs are not cancelled if they have started around the array.
Workaround - If the queue includes multiple jobs to the array to complete, the job is usually cancelled for the point the place that the GUI sends the subsequent job on the array.
Bug 6650124 -Sometimes the url status of ports A1, A2, A3, B1, B2, and B3 when viewed by CAM are reported as down when functioning properly. This was tested with CAM Build 6.0.1.10 and ST2530.
When you install the Common Array Manager software for that first time, upon logging in to the browser program, a registration page will display. Fill your information before continuing.
During the original storage array registration process, Common Array Manager prompts you to definitely register using the Auto Service Request service by displaying the Auto Service Request ASR Setup page. This page will continue to display soon you either fill the page and then click OK, or click Decline either to decline or defer ASR service registration.
Note - You must register the array with ASR before while using Test button.
Bug 6602902 -When a virtual disk is in a very failed state along with the drive creating the failure is replaced, for that recommended action, the management software refers anyone to access Service Advisor to initialize the disk. However, Service Advisor isn't going to contain info on disk initialization plus the link erroneously accesses the Collect Support Data page.
Bug 6604026 -Data channels 3 and 4 can not be managed using Service Advisor; only channels 1 and a pair of are designed for management.
Bug 6569930 -Attempting to reset the array configuration while a volume incorporates a persistent reservation appears successful; however, the position status displays just as error, indicating how the configuration reset failed.
Workaround - Release the persistent reservation within the volume and retry the array configuration reset.
Bug 6577194 -The sscs CLI client will not allow mapping towards the access volume for in-band management.
Workaround -To map the access volume, makes use of the Common Array Manager.
Bug 654985 -In the sscs CLI, special shell characters or phrases who use them have being enclosed in double quotes.
For Windows only, the comma, can be a special character. Options separated by commas needs to be enclosed in quotes, as shown inside the following example:
sscs create - p Default - s 100MB - d t1d01, t1d02, t1d03 volume dhamonewvdisk
Bug 659945 -Logging to the sscs CLI client remotely may fail each time a Solaris machine is configured make use of NIS for name resolution when the login host isn't contained inside the NIS map.
Bug 661094 -The sscs manpage was delivered only around the Solaris platform.
Workaround -Refer for the CLI Quick Reference Guide to get a command list and command syntax.
Bug 6587666 -The CLI command sscs list fru will not list the variety of fans installed around the Sun StorageTek FLX240 and FLX280 arrays.
Workaround -Use the Common Array Manager to watch the amount of fans installed.
Bug 6584193 -Although type generic and type vlac are listed as options together with the CLI sscs switch command, these options aren't yet implemented.
Bug 6597344 -Clicking the Test Communications button to have an offline controller may erroneously report how the communications test has gone by.
Workaround -Verify a controllers offline state by viewing its alarms.
Bug 6529172 -A snapshot volume that may be disabled could be automatically reenabled from a firmware update occurs. If the snapshot volume is full, it might start generating warning events.
Workaround - Disable the snapshot again following the firmware update.
Bug 6612858 - The Event list from two different hosts against precisely the same array shows different events, whilst the alarms generated are consistent.
Workaround - To display results using the polling frequency and polling times on the arrays, find the Advanced Aggregation Filter option through the CAM Events page. When this choice is de-selected, all hosts show consistent output. Therefore, this really is working as designed.
Bug 6595884 -A firmware upgrade/baseline installation can lock volumes more than the process indicates. The array can report the upgrade completed and show an optimal state but the method can still lock the volumes.
Workaround -Wait a supplementary five to ten minutes and try again.
Bug 6608890 - The array is bound in commands it may process simultaneously and CAM is just not doing validation and queuing of primarily volume create commands.
Workaround - Check scripts for volume modification status prior to issue new volume modification commands.
Bug 6596281 - If a data replication set is made between two volumes together with the primary volume using a size lower than the secondary volume, the key volume may be expanded till it reaches the size with the secondary volume.
Bug 6561709 -When the main volume in a very replication set fails, the management software may incorrectly list the amount as replicating.
Bug 6501029 -When the management software lists a disk as failed plus the Service Advisor means of replacing drives is followed, the key to verify which the disk is preparing to remove might not list the failed disk.
Workaround -Use another solution menu option, Array Troubleshooting and Recovery, to watch the status in the disk
Bug 6523608 -Refreshing a snapshot doesn't update the filesystem when there is insufficient reserve space, yet some text displays indicating success. The arrays event log says the resnap completed successfully.
Workaround -In the snapshot feature from the management software, configure snapshots to fail if sufficient reserve space will not be available. The fail message will prompt someone to increase the reserve space.
Bug 6560461 -Although the base volume as well as the snapshot reserve volume support read-ahead, the snapshot volume itself isn't going to support read-ahead. As a result, the Read-ahead Enabled Option is set to False around the Snapshot Details page.
Bug 6599933 -Changing a volume created that has a one segment size to one using a different segment size mandates that you create a fresh profile with all the desired segment size, build a pool using profile, and apply the brand new pool towards the volume. However, in the event the original profile is made using a fixed amount of disks as opposed to a variable quantity of disks, then an oversight is returned.
Workaround -Adjust the modern profile so that the volume of disks is variable rather then fixed.
Sun StorageTek 2500 series will not support volume-copy. Any instances from the user interface or documentation that imply there can be a command or function just for this task are misleading.
Bug 6665635 -Creating volumes with sizes that incorporate a fraction will not work in locales employing a comma as decimal point. The check for the legal numeric value isn't localized, though the interpretation from the number afterwards is. If you correctly type in the locale having a comma as 17, 352, you're going to get this error message: You must give you a numeric capacity value.
Example -When you make a volume with 17.352GB within the standard en locale, you may enter the size as 17.352 and select GB as unit. However, in the de locale, the dot is interpreted as 1000-separator. A 17.352 size having a 1GB unit would try to make a 17 TB volume and likely fail with this particular error message: The size entered to the new volume exceeds the ideal space available within the selected pool.
Workaround -For GB and TB values it is possible to multiply by 1024 and enter as MB or GB.
Bug 6598844 -Members of any replication write consistency group ought to have matching attributes and roles.
is listed inside the CLI manpage, it will not be implemented. And, although CLI manpage lists the
this option just isn't yet implemented.
command, you will need to supply the file path with the firmware image file.
option, which enables you to definitely select a controller, as follows:
In synopsis and options, fru-type and unit-type are being used in an interchangeable way. For both - t and - x, use fru-type rather then unit-type being consistent.
Bug 6592877 - When a drive fails, the quantity group which it belongs is not redundant. A stand-by hot-spare drive is chosen and included in that volume group automatically when possible.
The chosen drive should be PRESENT, STANDBY-HOT-SPARE, OPTIMAL.
The chosen drive must be from the same technology FC, SATA, SAS since the FAILED drive.
The chosen drive will need to have adequate capability to contain the pieces from the volumes defined on that volume group these required metadata.
The chosen drive should match the spindle speed of other drives inside the volume group whenever possible.
If the degree group in which the failed drive belongs had Tray-Loss Protection TLP, it's best to select a hot spare drive that delivers TLP to the volume group.
Bug 652123 -All documentation might not really reflect changes made inside the graphical graphical user interface for release 6.0.1. Mainly, the forced firmware upgrade option has become removed, as well as the term Upgrade may be replaced with Install, as described within the following instances:
For Storage Summary and Administration pages, the Upgrade button is changed on the Install Firmware Baseline button
In the Firmware Upgrade wizard, Analyze and Upgrade Array Firmware has become changed to Analyze and Install Array Firmware Baseline
In Step 2 on the Firmware Upgrade wizard, the action menu label has evolved from Upgrade to Install Baseline or Install, as shown within the following examples:
Install Baseline, no disks
Install Baseline, disk only
Page 44 with the Sun StorageTek Common Array Manager Software Installation Guide, v.6.0 part number 820-0213-nn should state:
logging in with a management software station or by while using SSCS remote client on the remote host. The Installation Guide currently says Solaris rather than SSCS.
Bug 6593949 -The online Help won't provide a description for your Type field within the Snapshot Summary page. The Type field refers for the model quantity of the array. For example, 6140, 6130, 6540, 2530, 2540, FLX240, FLX280, FLX380, etc.
Some distributed versions with the Sun StorageTek Common Array Manager CLI Quick Reference had an unacceptable paths for the SSCS CLI command line.
Bug 6540170 - Common Array Manager can be utilized to create nearly 1022 volumes volumes 0 through 1021 for the Sun StorageTek 6130 array. However, when the Access LUN is at use, nearly 1023 volumes volumes 0-1022 might be created. If you make an effort to create over the supported quantity of volumes, a mistake message is returned.
Sun StorageTek 2500 series will not support volume-copy. Any instances within the user interface or documentation that imply there is usually a command or function due to this task is misleading.
Bug 6593508 - The review step of firmware Install wizard might display an incorrect warning which the array health is just not optimal.
Workaround -Check the Alarm Summary page to confirm the alarm.
In-band management is supported about the Sun StorageTek 6130, 6140, 6540, 2530 and 2540 arrays. Whereas release 6.0.0 in the Sun StorageTek Common Array Manager software only agreed to be qualified with Solaris SPARC and Linux 5.1 agents, release 6.0.1 has included-band management support for Solaris x86 and Windows.
The in-band management proxy agent can be a package and that is added into a host or gang of hosts with in-band connectivity via Fibre Channel to your storage array. An external management station might talk for this proxy host with an out-of-band connection and also the management commands are then relayed towards the storage device through the in-band path. This is really a transparent proxy agent which simply converts the RPC request packets to UTM SCSI- specific messages. The API CAM uses to control the arrays is similar whether the array is managed using the in-band or out-of-band path.
Multiple in-band proxy hosts could be used to access exactly the same array and multiple arrays are allowed behind just one proxy host.
Installation on the proxy agents is accomplished using the standard package addition tools inherent for the specific operating-system. For example, the
command can be used to fit the Solaris agent along with the associated Java Runtime package should also be installed. For Linux, the packages are RPM based as well as a runtime package is additionally needed. For windows, set up . packages are executable files offering their own Install Anywhere installer.
A proxy agent restart is essential after disruptive changes for the storage configuration. This won't apply to modifications in volumes exposed coming from a single array however it does apply if storage arrays are re-cabled differently or when the storage array configuration is different adding new storage arrays towards the configuration.
The in-band proxy agents will start if your host boots, nevertheless they will terminate if storage just isn't immediately seen. A restart on the agent instructions below will force a re-scan for storage arrays and, if any are only, the agent will continue to be running.
id471e7573
To verify the host sees the arrays management UTM LUN, do the next:
If the agent is definitely running, this will likely stop after which restart it.
Note - The SMagent requires Red Hat 5.1 also called 5 update 1 or maybe more. It just isn't supported on Red Hat 5.0.
Stopping Agent process 12632.
rootnsvr-150 agent SANtricity Storage Array Host Agent, Version 09.17.A0.03
Copyright C 1999-2006 LSI Logic Corporation. All rights reserved.
dev/sg2 Storage Array fms-lca1, Volume Access, LUN 31, Volume ID 600a0b80002fc0740000000000000000
Note - Support for that Windows proxy agent is just not qualified in CAM 6.0.1.
The Storage Manager Agent service is starting.
The Storage Manager Agent service was started successfully.
E: Program Files x86 StorageManager agent C: Java jdk1.5.011 bin java - classpath
PHYSICALDRIVE0 Storage Array fms-lca1, Volume Access, LUN 31, Volume ID 600a0b80002458d20000000000000000
PHYSICALDRIVE1 Storage Array fms-lca1, Volume Access, LUN 31, Volume ID 600a0b80002fc074
Bug 6584815 -When an access LUN is mapped to some proxy agent host for in-band management use, you will need to correlate the mappings involving the LUNs and also the host by while using
command for the UNIX prompt. The system can place the access LUNs and also the array ports through the UI or CLI, and it's going to then compare the outcome.
7. c8t0d31 SUN-UniversalXport-9617 cyl 8 alt 2 hd 64 sec 64
pci8, 700000/fibre-channel2/fp0, 0/ssdw200500a0b82fbc3c, 1f
13. c9t0d31 SUN-UniversalXport-9617 cyl 8 alt 2 hd 64 sec 64
pci8, 700000/fibre-channel2, 1/fp0, 0/ssdw200400a0b82fbc3c, 1f
b. List the array ports with all the UI or CLI:
In it, Port A/2 exposes c9t0d31 and Port B/2 exposes c8t0d31
Bug 6593318 - When a amount of in-band managed arrays are selected for removal, the operation usually complete successfully. However, one array can still be listed around the Storage System Summary page.
Note - For best performance, ensure both controllers are connected during configuration.
Bug 6603978 -The controller for the in-band managed array cannot not reset regardless if physical connectivity involving the array along with the management host continues to be verified.
Workaround -If physical connectivity is valid, un-register and re-register the array.
Bugs 6610504, 6609734, 6609155, 6607104, 6609732, 6612120 -An occasional problem exists the location where the in-band proxy agent may return the paths to your controllers back order. This error may occur on any platform.
The net result's an immediate communications error. The error message will typically read Error: Could not communicate while using controller to finish this request. Possible causes include network or connection problems, controller problems, or no power towards the host or storage array. Check these possible causes, then retry the operation.
This error might occur when performing these operations:.
snapshot copy, re-snap and disable
Workaround -Change the Current Volume Ownership any time a communication error is encountered during volume expansion: From the Volumes page, find the Specific Volume and change the value on the Owning Controller.
Changing the Current Volume Ownership can create an Alarm because the amount is not about the preferred controller. Select 1 of 2 actions:
Change the Volume back towards the original owner after performing the command.
Change the Preferred Volume Ownership with the desired volumes via sscs1m.
Bug 6588699 - When an in-band managed array loses communication with management host, the network address listed inside the Storage Summary page displays just as one out-of-band address as an alternative to an in-band address.
Workaround - If communication is lost with all the array, comprehend the alarms to ascertain if an in-band or out-of-band connection is lost.
Bug 6661742 - will not likely load. SMagent isn't supported on Redhat 5.0.
Workaround - The SMagent requires Red Hat 5.1 often known as 5 update 1 or older.
Bug 6612214 - When one from the arrays behind an in-band management proxy is taken off in Common Array Manager, the Common Array Manager software will alter the management from the other arrays behind the proxy to out-of-band management if path exists. An in-band discovery with the proxy agent would return them to in-band management in this instance.
Bug 6490238 -When installing the French version of Common Array Manager on Solaris and LINUX platforms, non-ASCII characters display as garbled text inside the copyright and license sections if your correct locale will not be used.
Workaround -Use the proper locale as an example, 8859-1 for Solaris and 88591 for LINUX or utilize the browser inside the English locale.
Bug 6495952 -When installing Chinese and Japanese version of Common Array Manager on SuSE Linux platforms, non-English characters are displayed as squares.
Workaround -Use English locale on SuSE Linux to put in the software.
Bug 6645809 -Test parameter names in troubleshooting test pages will not be localized. For example, doing a test from your Trouble Shooting menu within a Japanese environment won't display localized names for Target Controller, Password, and Send Results to Email.
Bug 6495952 -Graph titles and description pop-up will not be localized for Virtual Disk page. This bug can be a result of an workaround for the next bug 6516766 where resource strings for graph titles, descriptions, pop-ups, etc. were commented out inside foreign resource property files.
Bug 6500605 -For Solaris 10u4 and Solaris 8 and 9, the host cannot understand the storage devices management UTM LUN.
You should then receive output like the next, indicating which arrays be permitted access LUNs visible to your agent:
dev/rdsk/c5t200600A0B82458D4d31s2 Storage Array fms-lca1, Volume
Access, LUN 31, Volume ID 600a0b80002458d20000000000000000
dev/rdsk/c5t200700A0B82458D3d31s2 Storage Array fms-lca1, Volume
Access, LUN 31, Volume ID 600a0b80002fc0740000000000000000
Bug 6594360 -After you upgrade to S10U3 or later, the in-band management UTM LUNs are controlled by Solaris Traffic Manager MPxIO. In most cases, in-band management will never fail to be a result of this; however, it's best practice to ensure that this UTM LUNs are certainly not controlled by MPxIO. Performing the subsequent workaround task may help prevent problems.
command to have the Vendor and Product IDs. The VID needs to get 8 characters.
device-type-scsi-options-list SUN Universal Xport, disable-option; disable-option 0x7000000
WARNING: This operation will need a reboot.
Do you intend to continue? y/n default: y y
The changes can come into effect after rebooting the machine.
Reboot the device now? y/n default: y y
If you need coaching installing or making use of this product, visit:
Note - For the most recent patches available to your system, check SunSolve at:
Sun isn't responsible with the availability of third-party Web sites mentioned on this document. Sun doesn't endorse and just isn't responsible or responsible for any content, advertising, products, or some other materials situated on or through such sites or resources. Sun is not going to be responsible or chargeable for any actual or alleged damage or loss a result of or in connection with all the use of or reliance upon any such content, goods, or services situated on or through such sites or resources.
Download Sun StorageTek Common Array Manager CAM 6.0 Free
Offers One Interface, Run-Anywhere Flexibility
ability to observe and manage one or all arrays from any location around the network.
The Sun StorageTek Common Array Manager CAM software simplifies storage management having a common, simple-to-use interface, which makes it easy to accelerate deployment and help Sun StorageTek systems from different families. Version 6.0 is actually available and might be downloaded for free on the Sun Download Center.
CAM enables online administration, a frequent interface across all operating systems as well as the ability to observe and manage one or all arrays from any location within the network.
Version 6.0 provides integrated device management for Sun StorEdge 6130; Sun StorageTek 2530, 2540, 6140 and 6540; and StorageTek FLX240, FLX280 and FLX380 Arrays.
Supported platforms: Linux Intel x86, Red Hat Enterprise Linux 3 U8, Red Hat Enterprise Linux 4 U4, SUSE Linux Enterprise Server 9 and 10 Intel x86, Windows 2003 Server, Windows 2000 Server SP4, Windows XP Professional, Solaris 10 Operating System Solaris OS for x86 Platforms and Solaris 8, 9 and 10 OS SPARC Platform.
Its accessible in English, French, Chinese-Simplified and Japanese.
Other articles from the Storage portion of Volume 116, Issue 3:
Download Sun StorageTek Common Array Manager CAM 6.0 Free this article
Trending in Current Issue Vol 215, Issue 2
News and Solutions for Users of Solaris, Java and Oracles Sun hardware products
30, 000 Members 30, 000 Articles Published since 1998
Copyright 1998-2016 System News, Inc.
2015 company of heroes 2 ardennes assault download