The PowerVault 715N NAS system allows you to change languages for its Microsoft Windows Powered operating system's user interface. The MUI allows the PowerVault 715N to display Windows Powered operating systems menus, dialogs, and help files in multiple languages. The supported MUI languages are simplified Chinese, traditional Chinese, Dutch, English, French, German, Italian, Japanese, Korean, Spanish, and Swedish. You must install a language MUI from the Multilingual Support CD before it can be used on the system. When you receive a PowerVault 715N NAS system from Dell, the root directory of drive C includes a localization directory, which contains all of the files included in the Multilingual Support CD. If you have performed the reinstallation procedure, this directory does not exist, and you must install a language MUI from the Multilingual Support CD.
See "Logging in to the NAS Manager" in "NAS Manager."
After a MUI language has been installed, you can apply it to any user by performing the following steps: See "Logging in to the NAS Manager" in "NAS Manager." The default administrator user name is administrator and the default password is powervault.
Installing and Configuring Support for Other Languages
The Windows Powered operating system that comes installed on the PowerVault 715N can be configured to support reading and writing documents in a number of languages. To install the software required to support a specific language, perform the following steps: See "Logging in to the NAS Manager" in "NAS Manager."
Network Adapter TeamingNetwork adapter teaming allows the system to use the combined throughput of multiple network ports in parallel to increase performance or to provide fault tolerance. Network adapter teaming on your NAS system supports the following technologies:
Adaptive Load BalancingAdaptive Load Balancing (ALB) is a simple and efficient method for increasing the NAS system's network transmission throughput. The ALB software continuously analyzes transmission loading on each adapter and balances the load across the teamed ports as needed. Adapter teams configured for ALB also provide the benefits of adapter fault tolerance. To use ALB, the Ethernet ports on the NAS system must be linked to the same Ethernet switch. Adapter Fault ToleranceAdapter Fault Tolerance (AFT) provides the safety of an additional backup link between the NAS system and the hub or switch. If a hub, switch port, cable, or Ethernet port fails, you can maintain uninterrupted network performance. AFT is implemented with a primary adapter and a backup, or secondary, adapter. If the link to the primary adapter fails, the link to the secondary adapter automatically takes over. Link AggregationLink aggregation is a performance technology developed by Intel and others to increase a system's network throughput. Unlike ALB, link aggregation can be configured to increase both transmission and reception channels between your system and switch. Link aggregation works only with compatible Intel switches. To use link aggregation, the Ethernet ports of the NAS system must be linked to the same Intel Ethernet switch. Fast EtherChannelFast EtherChannel (FEC) is a performance technology developed by Cisco Systems to increase a system's network throughput. Unlike ALB, FEC can be configured to increase both transmission and reception channels between your NAS system and switch. FEC works only with compatible Cisco switches. To use FEC, the Ethernet ports of the NAS system must be linked to the same Cisco FEC-compatible switch. IEEE 802.3adIEEE 802.3ad is a performance technology standard that increases a system's network throughput. IEEE 802.3ad is similar to the FEC standard developed by Cisco. However, whereas FEC works only with FEC-compatible Cisco switches, IEEE 802.3ad works with all switches that support IEEE 802.3ad. To use IEEE 802.3ad, the Ethernet ports of the NAS system must be linked to the same IEEE 802.3ad switch. Creating Intel PROSet II Network TeamsSee "Logging in to the NAS Manager" in "NAS Manager."
The Network Teaming utility, Intel PROSet II, displays. The Teaming Wizard displays. The types of team include Adapter Fault Tolerance, Adaptive Load Balancing, Fast EtherChannel*/Link Aggregation, and IEEE 802.3ad.
Removing Intel PROSet II Network TeamsSee "Logging in to the NAS Manager" in "NAS Manager."
The Network Teaming utility, Intel PROSet II, displays. Removing an Intel PROSet II Adapter From a Network TeamSee "Logging in to the NAS Manager" in "NAS Manager."
The Network Teaming utility, Intel PROSet II, displays. Changing the Intel PROSet II Network Team ModeSee "Logging in to the NAS Manager" in "NAS Manager."
The Network Teaming utility, Intel PROSet II, displays.
The types of team include Fault Tolerance, Load Balancing, Fast EtherChannel*/Link Aggregation, and IEEE 802.3ad. Creating Network Teams Using the Broadcom Advanced Server Control SuiteSee "Logging in to the NAS Manager" in "NAS Manager."
The Broadcom Advanced Server Control Suite window displays.
The types of team include Start Load Balance and Fail Over, FEC/GEC, and Link Aggregation (IEEE 802.3ad).
Removing Broadcom Adapter From a Network TeamSee "Logging in to the NAS Manager" in "NAS Manager."
The Broadcom Advanced Server Control Suite window displays.
Changing the Network Team Mode Using the Broadcom Advanced Server Control SuiteSee "Logging in to the NAS Manager" in "NAS Manager."
The Broadcom Advanced Server Control Suite window displays.
The types of team include Start Load Balance and Fail Over, FEC/GEC, and Link Aggregation (IEEE 802.3ad). Services for UNIX®Services for UNIX (SFU) provides the tools needed to integrate UNIX and Windows networks by leveraging existing UNIX network resources and expertise. SFU includes more than 60 of the most common UNIX command line utilities to provide a familiar environment for UNIX users and administrators. Server for NFS allows you to leverage your existing UNIX network resources for UNIX clients. SFU provides important tools to enhance and simplify the administration of your network.
Server for Network File System (NFS)SFU provides a robust Server for NFS that can be used to provide disk resources from systems running Windows NT and Windows 2000 to any system on your network that supports NFS. To administer Server for NFS, set the following options from the SFU MMC console:
UNIX UtilitiesTable 7-2 lists UNIX utilities provided with SFU.
Telnet ServerThe Telnet server works optimally for most installations. It accepts logins from a variety of clients, including the Telnet clients shipped with Windows 2000, Windows NT, Windows 95, and Windows 98, as well as a variety of character mode terminal clients from virtually any operating system. In addition, it can be configured to meet specific site requirements such as improving security, simplifying logins, and supporting stream or console mode. AuthenticationThe SFU Telnet server supports Windows NT LAN Manager (NTLM) for authentication of client logins. NTLM allows users to be automatically authenticated to the Telnet server based on their Windows NT login. This makes using Telnet completely transparent to users, while ensuring that clear text passwords do not pass over the network. However, NTLM must be supported on the client side of the login as well. When users are logged in to a system that is using NTLM login, they are restricted to local drives on that system. If they need to map network resources, they can do so by explicitly mapping with full credentials. AdministrationThe Telnet server is administered using the SFU MMC snap-in or the tnadmin program. The following options are available:
Services for UNIX MMC ConsoleSFU UNIX includes a single MMC for managing all of SFU. The MMC provides a cohesive management interface that allows you to administer all systems on the network from any console. Further, since SFU supports the Windows Management Interface (WMI), management can be scripted from the command line. You can access the MMC Console by selecting Computer Management under System Management on the Advanced Administration Menu. See "Using the PowerVault Advanced Administration Menu" in "NAS Manager." ActiveState ActivePerl 5.6SFU includes ActiveState's ActivePerl 5.6, a full-featured port of Perl 5.6 and Perl Script to Windows Powered operating systems. Among other improvements, ActivePerl 5.6 includes support for fork() emulation at the interpreter level, improving the portability of scripts and modules. ActivePerl also provides full support for the Windows Script Host, making ActivePerl an excellent tool for system administration tasks. User Name MappingUser Name Mapping provides mapping of names between the UNIX and Windows environments. You can configure User Name Mapping from the SFU MMC Console or by using the NAS Manager to configure properties for the NFS Sharing Protocol. With User Name Mapping, you can create simple maps between Windows Powered user accounts and corresponding UNIX accounts. You can also use the Advanced Map feature to map accounts with dissimilar names. Given that UNIX user names are case-sensitive, while Windows Powered operating system names are not, the use of User Name Mapping can greatly simplify maintaining and managing accounts in the two environments. User Name Mapping uses Network Information Service (NIS) or local Personal Computer Network File System (PCNFS) user and group files to authenticate users. Also, User Name Mapping supports bidirectional one-to-many mapping, allowing you to map a single UNIX or Windows Powered operating system account to multiple accounts in the other environment. For example, you can map more than one administrative account in a Windows Powered operating system to the UNIX root account. To create user and group name maps, perform the following steps: See "Logging in to the NAS Manager" in "NAS Manager."
ConfigurationTo configure the type of server to be used to access UNIX user and group names, perform the following steps:
Defining MapsTo define simple maps in SFU, select the Simple Maps check box, and then perform the following steps:
If you are defining explicit maps, you create user and group maps individually. To create explicit maps, perform the following steps:
This action refreshes your UNIX users or groups selection.
Basic ScenariosFor UNIX and Windows NT User Name Mapping, an NIS Server must already exist in the UNIX environment or UNIX user and group files must exist on the PowerVault NAS system. User Name Mapping associates UNIX users and groups to Windows NT users and groups. You can use two types of maps, simple and explicit. Simple maps define a one-to-one relationship between the same user names and groups. Explicit maps define a relationship between dissimilar user names and groups. WorkgroupIn the workgroup scenario, you configure User Name Mapping locally on the PowerVault 715N system. All maps are contained on this system. DomainIn the domain scenario, you configure NFS Authentication on all domain controllers. The NT Authentication Service installation program must be installed on the domain controller and available in the DomainUtils share on the NAS system. To install the NT Authentication Service on a domain controller, perform the following steps:
Filename Character TranslationAlthough Windows and UNIX file systems do not allow certain characters in filenames, the characters that are prohibited by each operating system are not the same. For example, a valid Windows filename can not contain a colon (:), but a UNIX filename can. If a UNIX user attempts to create a file in an NFS share and that file contains an illegal character in its name, the attempt will fail. You can use filename character translation to replace characters that are not allowed in a file system by mapping them to characters that are valid. To enable filename character translation, create a text file that maps Windows to UNIX characters, and then modify the registry entry that specifies the path and name of the translation file. The filename character translation text file is a list of mapped characters in the following format, such as the following: 0xnn : 0xnn [ ; comment ] where nn is the hexadecimal value of the character The entry for a map from the UNIX character ":" to the Windows character "-" in the filename character translation text is as follows: 0x3a : 0x2d ; Map ':' (0x3a) to '-' (0x2d) To map the character combination "()" to the character "^", add the following entry: 0x28 0x29 : 0x5e ; Map '()' to '^' To specify the path and name of the filename character translation text file for Server for NFS to use, modify the following registry key to contain the path and filename of the character translation file: HKLM\SOFTWARE\Microsoft\Server for NFS\CurrentVersion\Mapping\CharacterTranslation File Server for MacintoshFile Server for Macintosh (FSM) provides the tools needed to integrate Macintosh and Windows networks by leveraging existing Macintosh network resource and expertise. FSM is disabled by default on the NAS system. See "Enabling the AppleTalk Protocol" for information about enabling FSM. Enabling the AppleTalk ProtocolThe AppleTalk protocol is disabled on the NAS system by default. You must enable the AppleTalk protocol for Macintosh clients to access the NAS system. To enable the AppleTalk protocol, perform the following steps: See "Logging in to the NAS Manager" in "NAS Manager." Adapter BindingsFSM can bind to only one network adapter. By default, it is bound to the embedded 10/100TX Network Adapter. To change the binding in systems with multiple network adapters, the AppleTalk protocol properties for the network adapter to be used by AppleTalk must be modified to accept inbound connections. AppleTalk Protocol Adapter BindingTo modify the AppleTalk protocol adapter binding for filers with multiple network adapters, perform the following steps from the NAS Manager: See "Logging in to the NAS Manager" in "NAS Manager."
Microsoft UAM VolumeA user authentication map (UAM) is a software program that prompts users for an account name and password before they log in to a server. The Macintosh Chooser has a standard UAM built in that uses the clear-text password or Apple's RandNum Exchange method of security. Microsoft Authentication offers an additional level of security because the password is used as a key to encrypt a random number. If the system administrator has determined that encryption is an important security measure, you may be asked to use Microsoft Authentication in addition to Microsoft UAM authentication. RequirementsTo use Microsoft UAM 5.01, you must have a Macintosh client running AppleShare Client 3.8 or newer or the Mac operating system (OS) 8.5 or newer operating system. If you do not meet the minimum requirements, the Microsoft UAM Installer installs the old Microsoft UAM 1.0 module. If you upgrade your system software, you need to run the Microsoft UAM Installer again. Installing User AuthenticationLog in to the Microsoft UAM Volume on the system to access the MS UAM file, and then drag this file to the AppleShare Folder in your System folder. To access the Microsoft Authentication files on the system, perform the following steps: See "Logging in to the NAS Manager" in "NAS Manager."
Ask your system administrator if you are not sure of the zone.
To install the authentication files on the Macintosh workstation, perform the following steps:
The installer reports whether the installation succeeded. If the installation succeeded, Macintosh users of this workstation are offered Microsoft Authentication when they connect to the system. Restarting Workstation ServicesIf File Services for Macintosh cannot establish communications to the local RPC service, you may need to restart the Workstation Service. To restart the Workstation Service, perform the following steps: See "Logging in to the NAS Manager."
The Advanced Administration Menu displays. If it does not display, double-click the Advanced Administration Menu icon on the desktop of the NAS appliance.
Services for Novell® NetWare®Services for NetWare (SFN) are compatible with Novell NetWare Bindery service for authentication and file access using the internetwork packet exchange/sequenced packet exchange (IPX/SPX) network protocol. Services for NetWare are disabled by default. See "Enabling Services For NetWare." Enabling Services For NetWareThe NetWare protocol is disabled on the NAS system by default. You must enable the NetWare protocol for NetWare clients to access the NAS system. To enable the NetWare protocol, perform the following steps: See "Logging in to the NAS Manager" in "NAS Manager." Configuring the NWLink IPX/SPX Compatible ProtocolTo configure this protocol, you need the internal network number, the frame type, and the network number. Internal Network NumberInternal network numbers are used for internal routing and are generally needed only for servers. You should not need to change this option on your system. Frame Type and Network NumberFrame types define the packet formats that are used by different networks. It is important that all systems in a network have the same frame type so that they can communicate with the rest of the network. When you are configuring your system, it attempts to automatically detect the frame type for the client. In most cases, this is successful. However, occasionally the automatic detection feature selects an inappropriate frame type, usually because more than one frame type exists on the network. If this happens, you should manually set the frame type to match the one specified on your NetWare server. Note that if more than one frame type exists, you should select the one that is detected first. For example, if the frame types Ethernet 802.2 and Ethernet 802.3 are bound to the same segment, then configure frame type Ethernet 802.2. The order of detection is Ethernet 802.2, Ethernet 802.3, Ethernet II, and then Ethernet SNAP. Configuring the IPX ProtocolBy default, the IPX protocol is configured on the NAS system to automatically detect frame types. To use the IPX protocol, you must change your NAS system's IPX properties to manually detect frame types. To configure the IPX protocol to manually detect frame types, perform the following steps: See "Logging in to the NAS Manager."
The Advanced Administration Menu displays. If it does not display, double-click the Advanced Administration Menu icon on the desktop of the NAS appliance.
The IPX protocol is now configured on the NAS system to manually detect frame types. Microsoft Directory Synchronization ServicesMicrosoft Directory Synchronization Services (MSDSS) allows you to synchronize a wide variety of data stored in the Active Directory service with Novell Directory Service (NDS) and NetWare 3.x binderies. MSDSS is a highly flexible service that helps Novell users to perform the following tasks:
MSDSS supports two-way synchronization with NDS and one-way synchronization with NetWare 3.x binderies to provide a complete directory interoperability solution. MSDSS also supports password synchronization and provides a directory migration service. MSDSS allows NetWare users to deploy Active Directory without having to replace existing directories or bear the cost of managing two separate directories. As a result, users have the flexibility to:
MSDSS is easy to use and makes synchronization and Active Directory setup easy through its management interface. It is fully featured to allow users a choice of management, synchronization, and migration options. MSDSS supports all major NetWare platforms and most Novell directories and binderies, and it includes support for IPX/SPX and TCP/IP network protocols. Windows 2000 MSDSS Domain ControllerTo implement MSDSS, you must install the Windows 2000 Server operating system and the MSDSS software (available on the Microsoft Services for NetWare Version 5 CD) on at least one system. In Windows 2000, when you promote a system running Windows 2000 Server to an Active Directory server, it becomes a domain controller. You use this domain controller to configure Active Directory, install MSDSS, and then import information from the existing NetWare environment. The larger the environment, the more new servers you need. If you are planning to have more than one domain, then you need new hardware for the first domain controller in each domain. You must also install Novell Client Access software on the MSDSS server or servers. MSDSS uses Novell Client Access to authenticate and to access NDS. While accessing NDS, it authenticates, but does not use a license. MSDSS also uses Novell Client Access to map one directory's contents to another, taking into account the fact that the object classes in Novell's NDS or bindery directories are different from Active Directory object classes. Novell Client Access is also required to use the File Migration utility to migrate files. You can install Novell Client Access in four modes: IP only, IPX only, IP and IPX combined, and IP with IPX Compatibility Mode. Most NetWare environments still use IPX. MSDSS works in all the modes because it uses Novell Client Access to access the lower layers. If you are migrating NDS, you can import the user and group information from one NDS server to the MSDSS server because you have one user database per tree. You can then migrate the file system. Remember that each Novell server has its own file system, which is not replicated to other servers (whereas NDS is replicated to other servers). After the files are migrated, you can uninstall NDS from the server to provide more space for the Windows 2000 Server operating system. Outline of the Deployment ProcedureThe next two sections describe the procedures for implementing MSDSS in a smaller (local area network [LAN] only) or larger (wide area network [WAN]) network. You need to adapt the guidelines to suit your environment and goals. Small EnvironmentA small company with a LAN-based and uncomplicated network is often a likely candidate for a quick migration. After doing all the preparations described in the previous section, perform the following steps (adjusted, if necessary, to your situation):
You must also run the File Migration utility.
When you are performing a migration, this page does not include the option to actually perform an initial reverse synchronization, but it is the page where you specify which password option you want to use. After the user accounts are migrated, you can migrate the file system (migrating the users before the files allows you to migrate file-system permissions). Follow the instructions in the Help printout, "To migrate files." The prompts guide you through the following steps:
The NDS Modify option converts, by default, to Read because it does not have an equivalent NFTS right. You might want to click the Write check box to allow read/write access.
If the NDS or Bindery volume you selected in the source tree displays Unavailable, then you are not currently logged in to that tree or Bindery server. Log in, and then press <F5> after reselecting the volume to view the directories within the displayed volume.
The utility scans all source volumes and counts and displays the number of directories and files in each. It ensures that proper access has been given to each source volume, directory, and file. If any errors occur, the utility displays them under NetWare scan logs and Windows scan logs, respectively. You can select a number of acceptable errors; if this number is exceeded, the process aborts, allowing you to return to previous steps to correct the errors.
Manually migrate (or use third-party utilities to migrate) object security permissions and system accounts, printer objects, application objects, and other objects that MSDSS does not migrate from Bindery or NDS to Active Directory. (MSDSS migrates NetWare user accounts, groups, and distribution lists for Bindery and NDS, and, for NDS only, MSDSS also migrates NDS organizational units and organizations.)
You must configure the desktops to join the Windows 2000 domain.
Be sure that the users know how to handle their password the first time they log in (for possible password options, see "MSDSS Password Management" in "MSDSS Deployment: Understanding Synchronization and Migration)" at www.microsoft.com. Medium-Sized or Large EnvironmentAn organization large enough to have WAN links probably selects to synchronize its networks temporarily while performing a gradual migration over time (up to 3 months for a large network), or it prefers to use synchronization to establish a mixed Novell/Windows 2000 network on a long-term basis. If you plan a staged migration, one-way synchronization is often the appropriate choice. After doing all the preparation described above, perform the following steps (adjusted, if necessary, to your situation):
MSDSS does not support custom object mapping for Bindery.
For more information, see the Novell website at support.novell.com/servlet/Knowledgebase and the Windows 2000 website at www.microsoft.com/windows2000. Using Secure Sockets LayersThis section explains how secure sockets layers (SSL) are used in the NAS system. It also explains how to use your own certificate, if you have one, and how to regenerate your certificate. Introduction to SSL CertificatesCertificates contain information that is used to establish system identities over a network. This identification process is called authentication. Although authentication is similar to conventional forms of identification, certificates enable Web servers and users to authenticate each other before establishing a connection to create more secure communications. Certificates also contain encryption values, or keys, that are used in establishing an SSL connection between the client and server. Information, such as a credit card number, sent over this connection is encrypted so that it cannot be intercepted and used by unauthorized parties. Two types of certificates are used in SSL. Each type has its own format and purpose. Client certificates contain personal information about the clients requesting access to your site, which allows you to positively identify them before allowing them access to the site. Server certificates contain information about the server, which allows the client to positively identify the server before sharing sensitive information. Server CertificatesTo activate your Web server's SSL 3.0 security features, you must obtain and install a valid server certificate. Server certificates are digital identifications containing information about your Web server and the organization sponsoring the server's Web content. A server certificate enables users to authenticate your server, check the validity of Web content, and establish a secure connection. The server certificate also contains a public key, which is used in creating a secure connection between the client and server. The success of a server certificate as a means of identification depends on whether the user trusts the validity of information contained in the certificate. For example, a user logging on to your company's website might be hesitant to provide credit card information, despite having viewed the contents of your company's server certificate. This might be especially true if your company is new and not well known. For this reason, certificates are sometimes issued and endorsed by a mutually trusted, third-party organization, called a certification authority. The certification authority's primary responsibility is confirming the identity of those seeking a certificate, thus ensuring the validity of the identification information contained in the certificate. Alternatively, depending on your organization's relationship with its website users, you can issue your own server certificates. For example, in the case of a large corporate intranet handling employee payroll and benefits information, corporate management might decide to maintain a certificate server and assume responsibility for validating identification information and issuing server certificates. For more information, see "Obtaining a Server Certificate From a Certification Authority." PowerVault 715N CertificateBy default, the PowerVault 715N has a self-generated and self-signed certificate. The configured SSL port is 1279.
Using a Custom CertificateIf a certification authority is present in the network, the administrator can choose to change the default PowerVault 715N certificate. The administrator must use the wizards to first request a certificate and then apply it to the NAS system. Obtaining a Server Certificate From a Certification Authority
Find a certification authority that provides services that meet your business needs, and then request a server certificate.
To obtain a server certificate, perform the following steps: See "Logging in to the NAS Manager."
The Advanced Administration Menu displays. If it does not display, double-click the Advanced Administration Menu icon on the desktop of the NAS appliance.
The certification authority processes the request and sends you the certificate.
For more information about SSL, see the Internet Information Server online help. SNMP ConsiderationsYour NAS system uses the simple network management protocol (SNMP), which is a set of protocols used by systems to provide information to a central management information database. The NAS Manager provides a method for configuring the community and agent properties. Configuring SNMP Community PropertiesSee "Logging in to the NAS Manager" in "NAS Manager."
Select this option if you want a trap message sent when authentication fails.
Configuring SNMP Agent PropertiesSee "Logging in to the NAS Manager" in "NAS Manager."
|
|
|
*Contact a chat agent thru the chat icon on the right top corner of the page to order a system with English components, Operating System and software. Precios en pesos mexicanos que incluyen gastos de importación, entrega a domicilio en México e IVA. Precios promocionales hasta 5 sistema por orden y cliente y no válidos para distribuidores y revendedores. La fotografía puede no corresponder al equipo en promoción. El peso de una portátil varía según la configuración. No pueden combinarse promociones de diferentes medios. Disponibilidad del Microsoft Office 2007 en español varía por región. Microsoft Office Edición Básica incluye Word, Excel y Outlook. Celeron, Celeron Inside, Centrino, Centrino Inside, Core Inside, Intel, logotipo Intel, Intel Atom, Intel Atom Inside, Intel Core, Intel Inside, logotipo Intel Inside, Intel Viiv, Intel vPro, Itanium, Itanium Inside, Pentium, Pentium Inside, Viiv Inside, vPro Inside, Xeon, y Xeon Inside son marcas registradas de Intel Corporation en Estados Unidos y en otros países. Si desea más información en cuanto a la clasificación del procesador Intel, consulte www.intel.com/espanol/go/rating.Dell no tiene derechos sobre otras marcas, nombres comerciales y productos de terceros aquí anunciados. El sistema de 6 pagos mensuales para compras con las tarjetas de crédito Banamex y American Express, sólo aplica para configuraciones participantes. Dell no es responsable por cargos adicionales por uso de tarjeta o intereses, cargos por mora o penas por caso de retraso de acuerdo con su contrato con el banco. Favor de proporcionar copia de identificación oficial del adquirente (credencial de elector, pasaporte, cartilla del servicio militar) a la entrega del equipo. Dell no será responsable por aquellos errores tipográficos o fotográficos que se llegasen a presentar. ©2009 Dell Inc. Todos los derechos reservados. |