Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Storage and Availability Management

Showing posts tagged with ASL remove filter
Rishi Manocha | 02 Apr 2009 | 0 comments

The following services have just been updated. Please find below new functionalities now available to you:

Veritas Installation Assessment Service [VIAS]

  • Combined Notification Center – Users can create user defined ad-hoc or environment specific notifications for new patches, ASL/APM releases, new versions of the HCL and updates to Veritas Operations Services (VOS) from one easy-to-use web application. Both the notification center and VIAS reports now connect directly with Patch Central allowing the applications to synergistically cross-leverage customer data
  • Windows Support (Beta) – Support for the SFWHA “ConfigChecker” application to pre-qualify Windows environments

Find Out More
Link to VIAS

...

Ameya | 03 Aug 2007 | 1 comment
Array Policy Module (APM)

=====================

The APM framework was introduced in Volume Manager 4.0 release. The 4.0 release brought about a major change in DMP architecture - the introduction of APM. As the name suggests, the Array Policy Module (APM) is specific to an array type and defines the policies for an array type. Analogous to its Array Support Library (ASL) counterpart in user space which enables the DDL to identify the array completely, the APM enables DMP kernel to perform array specific operations such as failover, NDU (Non-Disruptive Upgrade), STPG (Set Target Port Groups) and even an I/O policy.

The APM makes it possible for DMP to dynamically add kernel support for an array. The support for enabling an APM is completely online and does not require a reboot. An APM is essentially a dynamically loadable kernel module that is validated and loaded by DMP whenever DMP detects the array type support exported by that APM. In other words, the DDL...

Ameya | 13 Apr 2007 | 1 comment

The first basic function for a multi path (MP) driver is to identify the set of block devices that can be supported. The device discovery is generally triggered when the MP driver is loaded into the operating system (OS) as part of boot process. During early boot, not all devices connected to the system may be available. For example, the devices connected using the fibre channel (FC) cables may not be available during early boot time unless there is special support from the bootstrap, which is usually from NVRAM or EEPROM, to identify the fibre channel devices. In any case, it may be required for a MP driver to rescan the OS device tree at a later stage of boot process.

One of the biggest challenges in device discovery is the ability and skill of MP driver to discover disk devices and their attributes in a non-intrusive fashion such that the disk media is not touched. In other words, the device discovery has to be purely read-only operations to identify the disk and disk...