. For Veritas Storage Foundation 6.0 and later, you must set the IOFENCE timeout parameter to 30000. For information on doing this, see (Veritas, Red Hat) Configuring Red Hat 6, 5 to support Veritas Storage Foundation on page 46. 8 Linux Host Utilities 6.1 Installation and Setup Guide. The Licensed Software and Documentation are deemed to be “commercial computer software” and “commercial computer software documentation” as defined in FAR Sections 12.212 and DFARS Section 227.7202. Symantec Corporation 20330 Stevens Creek Blvd. Cupertino, CA 95014 www.symantec.com Printed in the United States of America. The Licensed Software and Documentation are deemed to be “commercial computer software” and “commercial computer software documentation” as defined in FAR Sections 12.212 and DFARS Section 227.7202. Symantec Corporation 20330 Stevens Creek Blvd. Cupertino, CA 95014 www.symantec.com. The Sun StorEdge 3120 SCSI array supports Veritas Dynamic Multipathing (DMP) software. Note - For other supported software, see the Release Notes for your array. To enable VERITAS Dynamic Multipathing (DMP) support on VERITAS Volume Manager Version 3.2, ensure the HBA device SCSI initiator IDs are unique and then start the system. Refer to the Veritas Access Installation Guide on SORT for more details. Download link for Veritas Access software updates. Click the following link to download the Veritas Access software version 7.4.2.300 updates: For details about the new features and issues that are fixed in this release, see the Veritas Access 7.4.2.300 Release Update.
| Type | Private |
|---|---|
| Industry | Information Management |
| Founded | 1983 (as Tolerant Systems) January 29, 2016; 5 years ago (as Veritas Technologies) |
| Founders | Eli Alon Dave Shipley |
| Headquarters | Santa Clara, California, U.S. |
| Greg Hughes, CEO | |
| Owner | The Carlyle Group |
Number of employees | 7,000(2020) |
| Website | www.veritas.com |
Veritas Technologies LLC. is an American international data management company headquartered in Santa Clara, California. The company has its origins in Tolerant Systems, founded in 1983 and later renamed Veritas Software. It specializes in storage management software including the first commercial journaling file system, VxFS, VxVM, VCS, the personal/small office backup software Backup Exec and the enterprise backupsoftware, NetBackup. Veritas Record Now was an early CD recording software.
Prior to merging with Symantec (now known as NortonLifeLock) in 2004, Veritas was listed on the S&P 500 and the NASDAQ-100 under the VRTS ticker symbol.
In 2014, Symantec announced that it would demerge its information management business as Veritas Technologies LLC, in order to focus on security. It was purchased as part of the demerger by the private equity firmThe Carlyle Group for $8 billion in cash.
History[edit]
Early history[edit]
The company was founded by Eli Alon and Dale Shipley (both from Intel) as Tolerant Systems in 1983 to build fault-tolerant computer systems based on the idea of 'shoe box' building blocks. The shoe box consisted of an OS processor, running a version of Unix called TX, and on which applications ran, and an I/O processor, running a Real Time Executive, developed by Tolerant, called RTE: both processors were 320xx processors. The system was marketed as the 'Eternity Series.'
The TX software gained a level of fault-tolerance through check-pointing technology. Applications needed to be fortified with this check-pointing to allow roll-back of the application on another processor if a hardware failure occurred. Tolerant also developed a forerunner of today's RAID systems by incorporating a journaling file system and multiple copies of the disk drive content.
Dale Shipley formed Tolerant Software in January 1988. Tolerant Software produced a journaling file system and a virtual disk management system for the AT&T UNIX platform, which was built by a new team led by John Carmichael.
The firm started out with a relationship with AT&T to provide the file (Veritas File Manager – VxFS) and disk management (Veritas Volume Manager – VxVM) software for its UNIX operating system, and to jointly market and support the products to the System OEMS (Sun, HP, etc.). The OEM model provided royalties to Veritas when the OEM shipped its products to end users.
On December 9, 1993 the company had its initial public offering (IPO), selling 16 million shares to the public, and valuing the company at $64 million.
Growth and Acquisitions[edit]
At the end of 1996, Veritas had revenues of $36 million.
- Tidalwave Technologies Acquisition: In 1995 the company acquired Tidalwave Technologies, a small San Francisco-based company for $4.2 million in stock. Tidalwave specialized in cross-platform High Availability (HA) Software and thus entered the HA business.
- OpenVision Acquisition: In 1997 the company acquired OpenVision Technologies, another public company of the same size, and thus entered the backup business. Although the company only retained $20 million of OpenVision's 1996 base, it completed the 1997 year at $120 million. It was during this high growth period that the Veritas Board decided to consolidate the various business locations into a 550,000 SF facility in Mountain View, CA. Ernst & Young Consultants led by David Bentley as the project manager were brought in to lead this effort and soon hired HOK as the architect and Rudolf and Sletten as the general contractor. The new facility was completed in 2000.
- Seagate NSMG Acquisition: The company achieved $200 million in 1998, and in 1999 acquired the backup business from Seagate Software, which was also approximately $200 million in 1998. In 1999 the combined company achieved revenues of $700 million, and became the undisputed leader in the Storage Management Software industry. In 2000 the company achieved revenues of $1.2 billion, was added to the S&P 500, became a Fortune 1000 company, and became the tenth largest software company in the world by revenues, and third largest by market capitalization.
- Internet Bubble: In 2001 the industry went through a major downturn as the internet bubble burst. Nonetheless the company was able to achieve revenue growth of 25% to $1.5 billion, and operating margins of 25%.
- Growth of 42X: Through this accelerated growth, Veritas went from a $36 million company to a $1.5 billion company, a growth multiple of 42X in five years.
- April 1997 – Acquired OpenVision Technologies. This included NetBackup.
- May 1999 – Acquired the Network and Storage Management Group of Seagate Software. This included Backup Exec.
- August 2003 – Acquired Israel's Precise Software Solutions, one of the Application Performance Management (APM) leaders,[1] for about $400 million in cash and 7.4 million shares of its stock for a total of about $609 million.[2]
2004–2014: Merger with Symantec[edit]
On December 16, 2004, Veritas and Symantec announced their plans for a merger in a deal valued at $13.5 billion. The deal created the fourth-largest software firm in the world to date.[3] Veritas and Symantec's shareholders approved the merger on June 24, 2005, and it was completed on July 2.
2014–2016: Demerger[edit]
On October 10, 2014, Symantec announced it planned to split the company into two parts.[4] The security business would remain with Symantec, and the information management business would be known as Veritas Technologies Corporation. The separation of the companies was completed on January 29, 2016.[5]
On August 11, 2015, Symantec announced the sale of its Veritas information management business to The Carlyle Group.[6] Veritas and Symantec achieved operational separation on October 1, 2015. The sale completed on January 30, 2016, when Veritas became a privately held company.[6][7] The sale to go private was for $8 billion, and represented a mark-down on Symantec stock.[8]
2016: The New Beginning[edit]
After the demerger from Symantec in 2016, Veritas rebranded itself as Veritas Technologies LLC. with a new logo. As CEO, Bill Coleman was able to transform the company to have 'a startup, win-in-the-marketplace, customer-first culture' during the two-year turnaround.[9] On January 28, 2018, Veritas Technologies LLC. named Greg Hughes as its CEO.[10] With a new brand and a new CEO, Veritas Technologies planned to move its employees to its new headquarters in Santa Clara by the end of summer 2018.[11] In September 2020, Veritas Technologies LLC acquired Los Angeles-based software company Globanet.[12]
Products & Services[edit]
- Access
- VxFS and VxVM
- NetBackup Appliances
- Cluster Server (VCS)
- Enterprise Vault.cloud
- Enterprise Administrator
- Volume Replicator (VVR)
- SANPoint
- eDiscovery Platform
- APTARE IT Analytics™
- CloudPoint
- SaaS Backup
- Desktop and Laptop Option
- Flex Appliance
- Information Studio
- Data Insight
- Veritas Infoscale, data management such as HyperScale for OpenStack
- Resiliency Platform
Lawsuits[edit]
In 1999, VERITAS Software Corp. (VERITAS US) and VERITAS Ireland entered into a cost-sharing agreement (CSA) which was the subject of litigation with the U.S. Internal Revenue Service.[13]
See also[edit]
- Veritas Services and Operations Readiness Tools (SORT)
References[edit]
- ^'Veritas Buys Pair of Software Firms'. eWeek. 2002-12-19.
- ^Boulton, Clint (June 30, 2003), 'Veritas Closes Precise Software Purchase', InternetNews.com, retrieved 2009-11-03
- ^https://www.ecommercetimes.com/story/39030.html
- ^Robertson, Jordon (Oct 10, 2014), 'Symantec to Split Into Storage, Security Companies', Bloomberg, retrieved 2014-10-10
- ^corporate press release, Symantec and The Carlyle Group Plan to Close Acquisition of Veritas January 29, 2016, retrieved 2016-01-03
- ^ abcorporate press release, Symantec to Separate Into Two Focused, Industry-Leading Technology Companies, retrieved 2015-08-12
- ^corporate press release, Symantec and Veritas separation(PDF), retrieved 2016-02-15
- ^Preimesberger, Chris (Aug 11, 2015), Veritas Goes Private for $8 Billion Following Split from Symantec, retrieved 2017-03-23
- ^'Veritas taps new CEO, saying two-year turnaround is complete – SiliconANGLE'. SiliconANGLE. 2018-01-08. Retrieved 2018-05-04.
- ^Technologies, Veritas. 'Veritas Names Greg Hughes as Chief Executive Officer'. www.prnewswire.com. Retrieved 2018-05-04.
- ^'Veritas moving headquarters, hundreds of workers, to Santa Clara'. The Mercury News. 2017-11-20. Retrieved 2018-05-04.
- ^'Veritas Acquires Globanet, Extending Its Leading Digital Compliance Portfolio'. finance.yahoo.com. Retrieved 2020-09-29.
- ^https://scholar.google.com/scholar_case?case=17681094442401642589&q=Veritas+Software+Corp.+v.+Commissioner,&hl=en&as_sdt=6,48&as_vis=1
External links[edit]
| Sun StorEdge 3000 Family Installation, Operation, and Service Manual |
| C H A P T E R 5 |
| Software Management Tools |
This chapter describes the software management tools used for monitoring and managing the Sun StorEdge 3120 SCSI array. Topics include the following:
Note - For other supported software, see the Release Notes for your array. |
5.1 Overview of Provided Software
This section describes the software management tools available for monitoring and managing the Sun StorEdge 3120 SCSI array with in-band connections.
The following software management tools are provided on the Sun StorEdge 3000 Family Software and Documentation CD for your array.
- Sun StorEdge Configuration Service. Provides monitoring functions. Refer to the Sun StorEdge 3000 Family Configuration Service User's Guide for in-band setup procedures.
- Sun StorEdge Diagnostic Reporter. Provides event monitoring and notification. Refer to the Sun StorEdge 3000 Family Diagnostic Reporter User's Guide for information.
- Sun StorEdge Command-Line Interface (CLI). A command-line interface utility that provides script-based management. Refer to the Sun StorEdge 3000 Family CLI User's Guide for additional CLI information.
For details on how to install Sun StorEdge Configuration Service, Sun StorEdge Diagnostic Reporter, or the Sun StorEdge CLI software, refer to the Sun StorEdge 3000 Family Software Installation Manual.
5.2 Monitoring with Sun StorEdge Configuration Service
Sun StorEdge Configuration Service supports standalone JBOD arrays. However, because the Sun StorEdge 3120 SCSI array does not have a RAID controller or RAID controller firmware to manage the disks, this software support is limited to enabling JBOD support and viewing component and alarm characteristics.
See Section 5.2.2, Viewing Component and Alarm Characteristics.
5.2.1 Enabling JBOD Support
Use JBOD support only when you have a SCSI array connected directly to a host. This enables you to monitor peripheral device condition and events.
Note - Enabling JBOD support may impact I/O performance. |
To monitor peripheral device condition and events for a JBOD device from the Sun StorEdge Configuration Service Console, you first must enable JBOD support.
Note - Whenever you choose a command to perform administration or configuration activities in Sun StorEdge Configuration Service, if you are not logged in as ssadmin or ssconfig, you are prompted with a Log In dialog box to change your level of security. |
1. Choose View Agent Options Management.
The Agent Options Management window is displayed.
2. Select the Enable JBOD Support check box.
3. To immediately display the JBOD in the main window, you must probe for new inventory. Choose View View Server and click Probe.
4. Click OK.
The JBOD is displayed in the main window.
In a single-bus configuration, both ports of the JBOD array are connected to one HBA on the server, as shown in the following example.
FIGURE 5-1 Single-Bus Configuration
In a split-bus configuration, each port is connected to its own HBA, as shown in the following example. A SCSI Accessed Fault-Tolerant Enclosure (SAF-TE) limitation prevents the main window from showing the drives connected to port A and port B. The program can only monitor the JBOD from the server connected to port B as shown in the following example.
FIGURE 5-2 Split-Bus Configuration
Note - In a split-bus configuration, if each port is connected to a different server, the program can only monitor the JBOD from the server connected to port B. SAF-TE information is not displayed for port A. |
5.2.2 Viewing Component and Alarm Characteristics
In Sun StorEdge Configuration Service, to view environmental component and alarm characteristics, use the View Enclosure window or, for some components, the main window.
You can also view environmental and drive components using the Sun StorEdge CLI show enclosure-status command. For details, see Section 5.4, Monitoring with the Sun StorEdge CLI.
Main Window
In the main window, device states are color-coded and symbol-coded so that it is easy to identify when a device is in a state that requires attention. The status is propagated along the device tree, enabling you to trace a failure down to the device level. See TABLE 5-1for device status details.
Color | Symbol | State |
|---|---|---|
Purple | None | The group, server, or device is online. |
White | None | The user has not logged into this server. |
Yellow | One or more components of this group or server are not working properly, but the array is still functional. | |
Red | One or more components of this group or server are not working. For instance, a disk drive failure or an enclosure with a failed fan would warrant a critical state icon. | |
Gray | The group, server, or device is unresponsive. |
To view the cause of a critical or degraded device status, review the event log. For details on the event log, refer to the Sun StorEdge 3000 Family Configuration Service User's Guide.
View Enclosure Window
The View Enclosure window displays the component and alarm characteristics for a JBOD device. The window displays the status for environmental components including the fan, power supply, and temperature sensor.
To view the environmental component and alarm characteristics of a SCSI array from the Sun StorEdge Configuration Service Console, perform the following steps.
1. Select the event monitoring unit (EMU) icon.
2. Choose View View Enclosure.
To display FRU ID information, click View FRU.
FIGURE 5-3 View Enclosure Dialog Box
5.3 Event Messages from the Sun StorEdge Diagnostic Reporter
Sun StorEdge Diagnostic Reporter supports standalone JBOD arrays. However, triggered event notification is limited to environmental and hard drive failures. Refer to the Sun StorEdge 3000 Family Diagnostic Reporter User's Guide for more information.
5.4 Monitoring with the Sun StorEdge CLI
The Sun StorEdge CLI supports JBOD arrays. However, because JBOD arrays do not have a RAID controller or RAID controller firmware to manage the disks, this CLI support is limited to the following commands:
- about
- exit
- help
- quit
- select
- set led
- show access-mode
- show configuration
- show enclosure-status
- show frus
- show inquiry-data
- show led-status
- show safte-device
- version
about
Description
The about command displays version and copyright information.
Syntax
Examples
The following example shows the about text for the CLI.
exit
Description
The exit command exits the interactive mode. You can also use the quit command to exit the CLI.
Syntax
help
Description
The help command displays a short synopsis of the available commands.
Syntax
If no command is specified, basic usage information is displayed.
Examples
The following example shows the help text for the show channels command.
quit
Description
The quit command exits the interactive mode.You can also use the exit command to exit the CLI.
Syntax
select
Description
The select command selects a new device to which subsequent commands are issued. If no device is specified, and more than one choice exists, a menu of choices is displayed. This command should not be used on the command line because a select command is implicitly done if no device name is specified.
Syntax
Examples
The following command selects an in-band SCSI JBOD device.
set led
Description
The set led command changes the drive LED for the specified disk (or slot) from green to amber. For Sun StorEdge 3120 SCSI JBODs, specify a disk device using a Solaris device name such as sd31 or c1t0d0s2, or specify a slot number. Use the show led-status command to show the status of the identified disk drive.
Note - Selecting a slot by disk name is not supported in split-bus enclosure configurations because the enclosure services processor resides on only one of the internal buses and the CLI might not be able to determine the slot location of a particular device. In such configurations, use the show enclosure-status command and the disk documentation provided with your enclosure to determine the correct slot number instead. |
Syntax
To change a specific drive LED from green to amber, use the following syntax.
Arguments
Argument | Description |
|---|---|
slotn | Changes the drive LED from green to amber for the specified disk drive slot. |
disk sdn | Changes the drive LED from green to amber for the specified Solaris disk drive slot. |
disk cXtYdZ | Changes the drive LED from green to amber for the specified Solaris disk drive slot. |
{on | off} | Specify whether to change the LED from green to amber. |
Examples
In the following example, the LED adjacent to the drive with SCSI address 3 in the enclosure changes from green to amber:
show access-mode
Description
The show access-mode command displays whether the communication mode being used to manage the device is FC/SCSI channels (inband) or an Ethernet connection (out-of-band). Returned values include inband and out-of-band.
Note - If inband management access has been disabled by Sun StorEdge CLI or Sun StorEdge Configuration Service (SSCS), and a user attempts to use inband management, the message 'RAID controller not responding' displays when a command is run. |
Syntax
Examples
The following example shows the CLI communication mode is inband.
show configuration
Description
The show configuration command displays the array configuration including inquiry information, FRU information, SCSI Accessed Fault-Tolerant Enclosure (SAF-TE) device information, access mode, and enclosure status which includes the status for the fan, power supply, temperature sensor, and drive slots. The configuration can be displayed onscreen, or written to the specified file. The output is plain text by default, but XML output may be obtained by specifying the --xml option.
Syntax
Arguments
Argument | Description |
|---|---|
{--xml | -x} | If the -x or --xml options are specified, XML output is generated. |
filename | Specify the filename for the configuration file that you want to show. |
Examples
The following example writes the configuration information to the myconfig.xml file.
The following example shows a portion of the JBOD configuration.
Returned Values
Veritas Software Scsi & Raid Devices Driver Download 64-bit
Enclosure status values include:
Status | Description |
|---|---|
OK | This component has a status of OK. |
Absent | This component is absent. |
Fault | The component is exhibiting a fault condition. |
Unknown | This component status is not available. |
show enclosure-status
Description
The show enclosure-status command shows the status for all chassis components including SCSI Accessed Fault-Tolerant Enclosure (SAF-TE) revision number and status information, fan, power supply, temperature sensor, and drive slot status.
Note - In split-bus configurations on SCSI devices, half the drives display a status of Unknown. The drives are present, but because of a SAF-TE design limitation, the information does not display. |
Syntax
Examples
The following example shows the enclosure status for a Sun StorEdge 3120 SCSI device.
Returned Values
The following table describes the location of the enclosure devices from the back of the array orientation as shown in the following figure.
FIGURE 5-4 Enclosure Device Orientation
The returned values for the Sun StorEdge 3120 SCSI array are described in the following table.
Enclosure Types | Description |
|---|---|
fan 0 | Left side power supply fan |
fan 1 | Right side power supply fan |
PS 0 | Left side power supply |
PS 1 | Right side power supply |
Temp 0 | Left drive temperature sensor |
Temp 1 | Center drive temperature sensor |
Temp 2 | Temperature sensor on left side power supply module (Power supply 0 in FIGURE 5-4) |
Temp 3 | Temperature sensor on left side I/O module |
Temp 4 | Temperature sensor on right side I/O module |
Temp 5 | Right drive temperature sensor |
Temp 6 | Temperature sensor on right side power supply module (Power supply 1 in FIGURE 5-4) |
Disk Slot 0-3 | Disk slot identifier refers to the backplane FRU to which disks are connected |
Enclosure status values include:
Status | Description |
|---|---|
OK | This component has a status of OK. |
Absent | This component is absent. |
Fault | The component is exhibiting a fault condition. |
Unknown | This component status is not available. |
Note - The Enclosure SCSI Channel Type values include single-bus and split-bus. Throughout the documentation and the CLI, the term 'split-bus' is interchangeable with the term 'dual-bus.' For details on configuring an array, see Section 4.6, Connecting Sun StorEdge 3120 SCSI Arrays to Hosts. |
show frus
Description
The show frus command displays field-replaceable units (FRU) ID information for JBODs, including dynamic FRU status information. All FRU information is retrieved from the SCSI Accessed Fault-Tolerant Enclosure (SAF-TE) device.
Syntax
Examples
The following example returns all FRU information in a JBOD unit:
The following example shows a partial list of the FRUs in a Sun StorEdge 3120 SCSI device:
Returned Values
The returned status values for the show frus command are described in the following table.
Status | Description |
|---|---|
OK | All subcomponents of this FRU have a status of OK. |
Fault | One or more of the FRU components is exhibiting a fault condition. |
Absent | No FRU is located in the device. |
N/A | Not applicable. |
show inquiry-data
Description
The show inquiry-datacommand displays the SCSI inquiry data. The output of this command varies from one product to another, and from one channel to another.
Syntax
Note - The abbreviation inquiry can be substituted for the keywords show inquiry-data. |
Examples
The following example shows an in-band Sun StorEdge 3120 SCSI array inquiry.
show led-status
Description
The show led-status command displays the status of the LED adjacent to the specified disk drive slot in the array enclosure or expansion chassis. Returned values include on and off. If the value is on, the LED of the specified drive is amber. If the value is off, the LED of the specified drive is green if it is working properly.
Syntax
To show the status of LVD JBOD enclosures, use the following parameters:
Arguments
Argument | Description |
|---|---|
slotn | Shows the status for the LED adjacent to the specified disk drive slot. |
disk sdn | Shows the status for the LED adjacent to the specified Solaris disk drive slot. This argument is not accepted for split-bus chassis. |
disk cXtYdZ | Shows the status for the LED adjacent to the specified Solaris disk drive slot. This argument is not accepted for split-bus chassis. |
Examples
The following example shows the status of the LED adjacent to the disk assigned to drive slot 3 for an expansion chassis:
show safte-device
Description
The show safte-device command displays information returned by the SCSI Accessed Fault-Tolerant Enclosure (SAF-TE) device embedded in SCSI LVD RAID enclosures or JBODs.
The output includes the serial number of the chassis in which it is installed, the vendor and product IDs and SAF-TE firmware revision, and the 'SAF-TE firmware package' revision, which refers to firmware for other microprocesses in the chassis that are managed by the SAF-TE processor.
Syntax
Examples
The following example shows the SAF-TE device information for a Sun StorEdge 3120 SCSI array.
version
Description
The version command displays the version number of the CLI.
Syntax
Examples
In the following example, version 2.1 is displayed.
5.5 Managing Disks in the Sun StorEdge 3120 SCSI Array
Use your standard host system disk management utilities for all disk management in a JBOD array, such as partitioning and formatting. Refer to your host system documentation for more information about disk management.
For maintenance and troubleshooting information, see Chapter 7.
5.6 Enabling VERITAS DMP in a Single-Bus Configuration
The Sun StorEdge 3120 SCSI array supports Veritas Dynamic Multipathing (DMP) software.
Note - For other supported software, see the Release Notes for your array. |
To enable VERITAS Dynamic Multipathing (DMP) support on VERITAS Volume Manager Version 3.2, ensure the HBA device SCSI initiator IDs are unique and then start the system. Perform the following steps.
1. Create a single-bus, multi-initiator configuration that links two cables to two different HBAs.
For details about creating a single-bus multi-initiator configuration, see Section 4.6.5, A Single-Bus, Multi-Initiator JBOD Configuration.
2. Stop the server and at the OpenBoot PROM (OBP) Monitor ok prompt, type:
3. Issue the remaining commands on only one of the paths.
4. Edit or create the nvramrc to set the SCSI-initiator-id to a non-conflicting ID for these devices. The information returned from the probe-scsi-all command identifies the IDs that are currently used and unavailable for assignment.
For more information about ID assignment, see Section 4.6.2, Fixed Drive IDs.
5. From the OBP type:
6. Store the nvramrc by typing:
Veritas Software SCSI & RAID Devices Driver Download
7. Set the system to use the nvramrc and reset auto-boot by typing:
8. Reset the configuration by typing:
9. Reboot the hosts. A system reboot is required to implement these changes.
Note - SCSI arrays require a license from VERITAS in order to enable any of its advanced features. Refer to VERITAS Volume Manager Release Notes or contact VERITAS Software Corporation for licensing terms and information. |
Veritas Software Scsi & Raid Devices Driver Download Windows 10
| Sun StorEdge 3000 Family Installation, Operation, and Service Manual | 816-7956-15 |
Copyright © 2007, Dot Hill Systems Corporation. All rights reserved.