Infrastructure Manager Configuration
Infrastructure Manager, which is new for Cisco HCS 8.6(2), allows you to provision and query the Cisco HCS Shared Data Repository. The Cisco HCS Shared Data Repository provides configuration information for HCM - Service Assurance. The Cisco HCS Shared Data Repository is a repository of data that represents the Cisco HCS configuration of data centers, customers and management components in the service provider's network. This repository is then used by HCM - Service Assurance to provide more effective, detailed, and accurate operational alarms and events.
This chapter contains information on the following topics:
•Infrastructure Manager Element Description
•CUCDM Sync Services
•vCenter Sync Services
•General Procedures
Infrastructure Manager Element Description
The following section contains information on the elements available in the Infrastructure Manager. These elements appear as configuration options in the Infrastructure Manager.
Table 7-1 Infrastructure Manager Element Description
|
|
Data Center |
Each Data Center in the Shared Data Repository represents a physical Data Center involved in the Cisco HCS deployment. A Data Center will typically house one or more Unified Computing Systems (UCS), one or more Storage Array Networks (SANs), VMware and vCenter infrastructure, several Data Center monitoring applications (DCNM), and networking infrastructure to tie it all together. |
UCS Manager |
The Unified Computing System Manager (UCS Manager) provides centralized management for a Unified Computing System, which is comprised of multiple chassis, each with multiple blades. Each Data Center typically contains at least one UCS Manager and associated chassis and blades. These hardware resources are used to run the Virtual Machines for the customer applications such as Cisco Unified Communications Manager. UCS Managers and their associated chassis and blades should be configured to match the hardware resources in the Data Center. Furthermore, each blade should be linked to an ESXi Host in the vCenter configuration. When this linkage is made in the Infrastructure Manager configuration, the Service Assurance components of Cisco HCS can perform advanced fault correlation by attributing failures in the UCS hardware with alarms from ESXi Hosts, virtual machines, and customer applications. This fault correlation helps system administrators more quickly troubleshoot and isolate problems in the network. A UCS Manager should be configured for each UCS Manager deployed in the Data Center. |
vCenter |
A vCenter is the hypervisor manager from VMware. It provides centralized control and visibility at every level of virtual infrastructure and unlocks the power of the vSphere through proactive management. You can manually configure or automatically synchronize vCenter data with vSphere. If Sync enabled is checked, the VMware Data Center, VMware Cluster, Virtual Machine, and ESXi Host are auto-synced from the vCenter. In addition, if sync is enabled, modifications directly from the GUI are prohibited. For vCenter Sync to funtion at least one vCenter, vCenter credentials and vCenter network address information must be added. A vCenter should be configured for each vCenter server deployed in the Data Center. If the vCenter is managing VMware infrastructure that spans multiple Data Centers, configure the vCenter in the Data Center in which the vCenter server itself is deployed. |
VMware Data Center |
A VMware Data Center is a logical grouping of VMware Clusters. The VMware Data Center Summary page displays a list of the VMware Data Centers in your Cisco HCS as well as basic details about each one. If vCenter sync is enabled, and successful, VMware Data Centers are added, edited, and deleted through the vCenter sync. Any configuration changes to VMware Data Centers should be done from the vCenter user interface. Configure one Data Center for each physical Data Center that hosts equipment in the Cisco HCS deployment. The Data Center may be owned by the service provider or by a customer. |
VMware Cluster |
A VMware Cluster is a logical grouping of ESXi Hosts and Virtual Machines in the VMware infrastructure. The VMware Cluster Summary page displays a list of the VMware Clusters in your Cisco HCS as well as basic details about each one. If vCenter sync is enabled and successful, VMware Clusters are added, edited, and deleted through the vCenter sync. Any configuration changes to VMware Clusters should be done from the vCenter user interface. |
Virtual Machine |
A Virtual Machine is the machine deployed by VMware within a VMware Cluster. The Virtual Machine Summary page displays a list of the Virtual Machines in your Cisco HCS as well as basic details about each one. If vCenter sync is enabled and successful, Virtual Machines are added, edited, and deleted through the vCenter sync. Any configuration changes to Virtual Machines should be done from the vCenter user interface. |
ESXi Hosts |
The ESXi Host is the VMware Virtual Machine manager (VMM) or hypervisor associated with a specific blade. The ESXi Host Summary page displays a list of the ESXi Hosts in your Cisco HCS as well as basic details about each one. If vCenter sync is enabled and successful, ESXi Hosts are added, edited, and deleted through the vCenter sync. With the exception of the Blade linkage, any configuration changes to ESXi Hosts should be done from the vCenter user interface. After the ESXi Host information has been automatically synced, the Blade association must be configured manually. |
CUBE-SP |
The Cisco Unified Border Element - Service Provider edition (CUBE-SP) provides a network-to-network demarcation interface for signaling interworking, media interworking, address and port translations, billing, security, quality of service (QoS), Call Admission Control (CAC), and bandwidth management. The CUBE-SP Summary page displays a list of the CUBE-SPs in the aggregation layer of your Cisco HCS as well as basic details about each one. |
Customers |
The customer page displays the details of the customer in your Cisco HCS. If CUCDM sync is enabled and successful, customers are added, edited and deleted through the CUCDM sync. |
Cluster |
A cluster refers to a unified communications application cluster, such as Cisco Unified Communications Manager cluster or Cisco Unified Presence cluster. The Cluster Summary page displays a list of the clusters in your Cisco HCS as well as basic details about each one. It is recommended to configure Cisco Unified Presence, Cisco Unity Connection, and Cisco Unified Communications Manager clusters on the CUCDM server and have the CUCDM Sync Service add the clusters to the Shared Data Repository. Other cluster types, such as Contact Center, should be added through Infrastructure Manager. |
Cluster Application |
The Cluster Application Summary page displays a list of the cluster applications in your Cisco HCS as well as basic details about each one. It is recommended to configure Cisco Unified Presence, Cisco Unity Connection, and Cisco Unified Communications Manager cluster applications on the CUCDM server and have the CUCDM Sync Service add the cluster applications to the Shared Data Repository. Other cluster application types, such as Contact Center, should be added through Infrastructure Manager. |
SIP Trunk |
The SIP Trunk Summary page displays information about the SIP trunks belonging to a Cisco Unified Communications Manager application instance and those associated with one or more CUBE-SP (Cisco Unified Border Element - Service Provider) instances in your Cisco HCS. SIP Trunk data must be entered manually in Infrastructure Manager as it is not synced from CUCDM. |
Customer Equipment |
The Customer Equipment Summary page displays a list of the your customers' equipment, such as routers, gateways, SRST, media devices, and CUBE, in your Cisco HCS as well as basic details about each one. If CUCDM sync is enabled, and successful, routers, gateways, SRST, and media devices configured as IOS Devices on the CUCDM are added, edited, and deleted through the CUCDM sync. |
Management Application |
The Management Application Summary page displays a list of the management applications in your Cisco HCS as well as basic details about each one. The applications include CUOM, CUSM, CUCDM, Fulfillment_CDM, DCNM_LAN, DCNM_SAN, and DCNM_DB. Some CUCDM data can be manually configured or automatically synced with CUCDM sync. If sync enabled is checked, the Service Provider, Customer, Cluster, Cluster Application, and Customer equipment are auto-synced from the CUCDM. In addition, if sync is enabled, modifications directly from the GUI are prohibited. CUCDM must be manually configured in the management application section to allow CUCDM to start syncing. Disabling auto sync allows for modification and deletion of synced data. |
Jobs |
The Jobs Summary page displays a list of the all the automatic and manual jobs added to your Cisco HCS as well as basic details about each one. |
Sync Request |
You can configure manual syncs on the Sync Request page for the following entities: •Service Provider: All Data Centers and customers in the system are synced. •Customer: Only the selected customers are synced. •Data Center: All VCenters in the Data Center are synced. •VCenter: Only the selected vCenter is synced. |
Default Credentials |
Default credentials are user IDs and passwords for accessing applications through the Web, CLI, or SNMP, as applicable. The appropriate default credentials are assigned to each equipment type that is configured, either manually or through CUCDM sync. Configure a default credential for each user ID that is common across all equipment of a certain type. For example, if all Cisco Unified Communications Manager applications have the same SNMP V2 community string, configure a default credential for the Cisco Unified Communications Manager equipment type with the common SNMP V2 community string. This SNMP credential will then apply to all Cisco Unified Communications Manager applications that are synced from CUCDM. |
Service Provider |
The service provider page displays the details of the service provider in your Cisco HCS. If CUCDM sync is enabled and successful, customer equipment is added, edited, and deleted through the CUCDM sync. |
Settings |
The Settings page provides some thresholds for Cisco Unified Operations Manager assignments that can be configured. Each customer is assigned to a Cisco Unified Operations Manager, and each Cisco Unified Operations Manager can service multiple customers and the subscribers associated with those customers. The Settings page allows the administrator to specify the maximum number of customers, devices and subscribers each Cisco Unified Operations Manager can service. The Settings page also allows the administrator to specify the warning threshold for the same. When a maximum is reached, no further assignments can be made to that Cisco Unified Operations Manager. When a warning threshold is reached, the Usage is highlighted on the Management Application page. |
CUCDM Sync Services
The CUCDM sync service, which maintains synchronization of provisioned Cisco HCS data between CUCDM and the Cisco HCS Shared Data Repository, copies data from CUCDM to the Cisco HCS Shared Data Repository. The sync service supports automatic and manual synchronization. The CUCDM sync service allows Cisco HCS Fulfillment and DMA-CUOM to use the CUCDM configuration to push data to CUOM, which supports monitoring of Cisco Unified Communications Manager, Cisco Unity Connection, Cisco Unified Presence, and Cisco IOS gateway and media resource devices. Service Assurance uses the CUCDM configuration in conjunction with vCenter configuration to perform fault correlation and event enrichment.
Synced Data for CUCDM Sync Services
The following section outlines the data that is synced from CUCDM.
•Service Provider: Name, Account ID, Description, Contact Name, Contact Address 1, Contact Address 2, Contact City, Contact State, Contact Country, Contact Zip Code, Contact Phone Number, Contact email.
•Customer: Name, Extended Name, Account ID, External Customer ID, Contact Name, Contact Address 1, Contact Address 2, Contact City, Contact State, Contact Country, Contact Zip Code, Contact Phone Number, Contact email.
•Cisco Unified Communications Manager Cluster: Name, Description, Country Code, Email, Call Processing ID, CUCDMAAppVersion, Manual Mode (T or F), Customer association.
•Cisco Unified Communications Manager Application Instance: Name, Description, IS Publisher (T or F), Network Address, Host Name, Admin ID, Admin Password.
•Cisco Unified Presence Cluster: Name, Description, Email, Cluster ID, CUCDMAAppVersion, Manual Mode (T or F), Customer Association.
•Cisco Unified Presence Application Instance: Name, IS Publisher, Network Address, Host Name, Admin ID, Admin Password.
•Cisco Unity Connection Cluster: Name, Description, Email, Country Code, Call Processing ID, CUCDMAAppVersion, Manual Mode (T or F), Customer Association.
•Cisco Unity Connection Application Instance: Name, IS Publisher (T or F), Network Address, Host Name, Admin ID, Admin Password.
•Customer Equipment: Name, Role, Network Address, Host Name, Admin ID, Admin Password, Customer Association.
Configuration Checklist for CUCDM Sync Services
The following table lists the steps that you must perform to CUCDM Sync Services up and running.
Table 7-2 Configuration Checklist for CUCDM Sync Services
|
|
|
Step 1 |
Start the CUCDM Sync Services. |
Starting the Services |
Step 2 |
Configure Cisco Unified Communications Domain Manager as the Management Application. |
Adding New Elements |
Step 3 |
Verify configuration by performing a manual sync for the Service Provider. |
Performing a Manual Sync |
Step 4 |
Verify configuration by viewing the job status. |
Viewing Jobs |
vCenter Sync Services
The Cisco HCS VCenterSync Service monitors configuration data on one or more vCenter servers, copies data from the vCenter servers to the Cisco HCS Shared Data Repository, and maintains synchronization between the vCenter servers and the Cisco HCS Shared Data Repository. Cisco HCM-Service Assurance uses the vCenter configuration to perform fault correlation and event enrichment.
Synced Data for vCenter Sync Services
The following section outlines the data that is synced from vCenter:
•VMware Data Center
•VMware Clusters
•Virtual Machines
•ESXi Hosts
Configuration Checklist for vCenter Sync Services
The following table lists the steps that you must perform to vCenter Sync Services up and running.
General Procedures
The following section contains the general procedures related to Infrastructure Manager.
Starting the Services
Step 1 From the CLI, activate the services by entering the following:
admin: utils service activate Cisco HCS VCenterSync Service
admin: utils service activate Cisco HCS Fulfillment Service
admin: utils service activate Cisco HCS CUCDMSync Service
admin: utils service activate Cisco HCS DMA-CUOM Service
admin: utils service activate Cisco HCS North Bound Interface Web Service
admin: utils service activate Cisco HCS SI UI
admin: utils service activate Cisco HCS Service Inventory
admin: utils service activate Cisco Platform Manager Service
admin: utils service activate Platform Administrative Web Service
Step 2 Verify the services are active and running, by entering the following:
admin: utils service list.
Viewing and Editing Elements
Step 1 In the side menu, navigate to the element you want to view or edit.
Step 2 Click the link of the element in the Name column.
Step 3 View or edit information about the element on the Edit page.
For more field descriptions, refer to online help.
Adding New Elements
Step 1 In the side menu, navigate to the element you want to add.
Step 2 Click Add New.
Step 3 Enter the required information, refer to "Add New Elements Descriptions" section for more information.
Step 4 Click Save.
Add New Elements Descriptions
The following tables outline the different options for adding new elements.
Table 7-4 Data Center
|
|
|
|
Enter the name of the new Data Center. |
|
Select the owner of the new Data Center. |
|
|
Enter the address for the new Data Center. |
|
Enter the address for the new Data Center. |
|
Enter the city for the new Data Center. |
|
Enter the state for the new Data Center. |
|
Enter the zip code for the new Data Center. |
DCNM (Data Center Network Management) Monitoring
|
|
Select the DCNM-DB for monitoring the new Data Center. |
|
Select the DCNM-LAN for monitoring the new Data Center. |
|
Select the DCNM-SAN for monitoring the new Data Center. |
Table 7-5 UCS Manager
|
|
|
|
Enter the name for the new UCS manager. |
|
Select the Data Center for the UCS manager. |
|
Enter the IPv4 for the USC manager. You can find this IP address in the Cisco UCS Manager GUI under the Admin tab, Properties section, Virtual IP Address field. |
|
Interconnect A IPv4 Address
|
Enter the appropriate IP address. |
Interconnect B IPv4 Address
|
Enter the appropriate IP address. |
Table 7-6 Add Credentials
|
|
|
Select the credential type related to the UCS manager Depending on the credential type, enter the remaining fields. To configure the administration credentials, choose the Admin credential type. |
|
Enter the user ID related to the UCS manager. |
|
Enter the password for the user ID for the UCS Manager. |
|
Enter the password for the user ID for the UCS Manager. |
|
Enter the community string related to the UCS manager. |
|
Select the access type related to the UCS manager. |
Table 7-7 Chassis
|
|
|
Enter the chassis ID. |
|
Select the UCS manager of the new chassis. |
|
Enter the product name of the new chassis. |
Table 7-8 Blade
|
|
|
Enter the distinguished name for the new blade. |
|
Select the chassis for the new blade. |
|
Enter the product name for the new blade. |
|
Enter the slot number for the new blade. |
Table 7-9 vCenter
|
|
|
Enter the name for the new vCenter. |
|
Enter the description for the new vCenter. |
|
Select the required Data Center in which the vCenter server is deployed. |
|
Select the Virtual Machine that is hosting the vCenter server. |
|
Check to enable vCenter sync. (Optional) |
Table 7-10 Network Address Information
|
|
|
Select SP_Space for service provider.
|
|
Enter either the correct IP address or the hostname. |
|
|
|
Enter the domain if using hostname. |
|
Check if you want SRV address displayed. |
Table 7-11 VMware Data Center
|
|
|
Enter the name of the new VMware Data Center. |
|
Select the related vCenter of the new VMware Data Center. |
Table 7-1 VMware Cluster
|
Enter the name of the new VMware Cluster. |
|
Select the related VMware Data Centers of the VMware Cluster. |
Table 7-12 Virtual Machine
|
|
|
Enter the name of the new Virtual Machine. |
|
Select the related VMware Clusters of the new Virtual Machine. |
|
Enter the hostname of the new Virtual Machine. |
|
Enter the domain name of the new Virtual Machine. |
Table 7-13 ESXi Host
|
|
|
Enter the name of the new ESXi Host. |
|
Enter the IPV4 of the new ESXi Host. |
|
Select the VMware Cluster of the new ESXi Host. |
|
Select the blade of the new ESXi Host. This field is not automatically synced and must be manually configured. |
Table 7-14 CUBE-SP
|
|
|
This field is auto populated. Displays the service provider of the new CUBE-SP. |
|
Enter the name of the new CUBE-SP. |
|
Enter the description of the new CUBE-SP. |
|
|
Displays the name of the SIP Trunk. |
|
Displays the description of the SIP trunk. |
|
Displays any associations with CUBE-SP. |
Table 7-15 Customer
|
|
|
|
Enter the new customer name. The name must be unique to the Shared Data Repository. |
|
Enter the new customer ID. |
|
Enter the new extended customer name. |
|
|
Enter the new customer address. |
|
Enter the new customer address. |
|
Enter the new customer city. |
|
Enter the new customer state. |
|
Enter the new customer country. |
|
Enter the new customer zip code. |
|
Enter the new customer contact name. |
|
Enter the new customer contact telephone number. |
|
Enter the new customer contact email. |
Customer Specific Information
|
Number of End User Subscribers
|
Enter the new customer's number of end user subscribers. The DMA-Cisco Unified Operations Manager service will update the number of End User Subscribers based on inventory results on the Unified CM. |
CUOM (Cisco Unified Operations Manager) Monitoring this Customer
|
Select a Cisco Unified Operations Manager from the list that monitors this customer. |
Table 7-16 Cluster
|
|
|
|
Enter the new cluster name. |
|
Select the new cluster customer. |
|
Enter the new cluster description. |
|
Enter the new cluster CPID. |
|
Select the new cluster type. |
CUCDM (Cisco Unified Communications Domain Manager) AppVersion
|
Displays the CUCDM application version and is auto-populated if cluster data is synced using CUCDM Sync Service. |
|
Select manual mode if required. |
CUOM (Cisco Unified Operations Manager) Monitoring this Cluster
|
Select the new cluster Cisco Unified Operations Manager monitoring this cluster. |
|
|
Enter the new cluster contact email. |
|
Enter the new cluster contact country code. |
Table 7-17 Cluster Application
|
|
|
Enter the new cluster application type. |
|
Enter the new cluster application name. |
|
Enter the new cluster application description. |
|
Enter the new cluster application node type. |
|
Enter the new cluster application related cluster. |
|
Enter the new cluster application related Virtual Machine. |
SIP Trunks (SIP Trunk data is not synced from CUCDM)
|
|
Displays the name of the SIP trunk. |
|
Displays the description of the SIP trunk. |
|
Displays any associations with CUBE-SP. |
Table 7-18 SIP Trunk
|
|
|
Enter the new SIP trunk name |
|
Enter the new SIP trunk description. |
|
Enter the Cisco Unified Communications Manager related to the new SIP trunk. |
|
|
Displays the name of the CUBE-SP. |
|
Displays the description of the CUBE-SP. |
|
Check the check box to associate with the SIP trunk. |
Table 7-19 Customer Equipment
|
|
|
Enter the new customer equipment name. |
|
Enter the name of the customer. |
|
Enter the new customer equipment roles. |
CUOM (Cisco Unified Operations Manager) Monitoring this Cluster
|
Enter the related Cisco Unified Operations Manager monitoring this cluster for the new customer equipment. |
Table 7-20 Management Application
|
|
|
Enter the new management application type. |
|
Enter the new management application name. |
|
Enter the new management application description. |
|
Enter the Virtual Machine hosting the management application. If the correct Virtual Machine is not visible in the list, ensure the vCenter server managing the Virtual Machine is configured and the automatic synchronization is functioning properly. |
Table 7-21 Management Application - CUCDM
|
|
|
Select CUCDM. |
|
Enter the name. |
|
Select the software version for the CUCDM. |
|
Enter the webservice port. |
|
Enter a description. |
|
Select the Virtual Machine for the CUCDM. |
|
Enter the host ID. |
|
Check to enable sync with the CUCDM server. |
|
Enter the time interval for syncing with CUCDM. |
Table 7-22 Default Credentials
|
|
|
Select the equipment type. |
|
Select the credential type. |
|
Select the access type. |
|
|
Enter the user ID. |
|
Enter the password for the user ID. |
|
Re-enter the password for the user ID. |
Community String Information
|
|
Enter the community string. |
Re-enter Community String
|
Re-enter the community string. |
Deleting Elements
Note Elements not added through the Infrastructure Manager cannot be deleted unless the sync service for the element is disabled.
Step 1 In the side menu, navigate to the element you want to delete.
Step 2 Check the check box for the element you want to delete.
Step 3 Click Delete Selected.
Performing a Manual Sync
Step 1 In the side menu, select Administration > Sync Request.
Step 2 Select the Job Entity from the drop down list.
Step 3 Select the item you want to sync.
Step 4 Click Sync Selected.
You can configure manual syncs on the Sync Request page for the following entities:
•Service Provider: All Data Centers and customers in the system are synced.
•Customer: Only the selected customers are synced.
•Data Center: All VCenters in the Data Center are synced.
•VCenter: Only the selected vCenter is synced.
The following table lists the available options on the Sync Request page in your Cisco HCS.
|
|
|
Select one of the following to sync: •Service Provider •Data Center •vCenter •Customer |
|
|
Displays the name of the service provider. |
|
Displays the account number of the service provider. |
|
|
Displays the name of the Data Center. |
|
Displays the name of the service provider for the Data Center. |
|
Displays the number of DCNMs related to the Data Center. |
|
Displays the number of UCS managers related to the Data Center. |
|
Displays the number of VCenters related to the Data Center. |
|
|
Displays the name of the vCenter. |
|
Displays the Data Center name related to the vCenter. |
|
Displays the number of VMware Data Centers related to the vCenter. |
|
|
Displays the name of the customer. |
|
Displays the extended name of the customer. |
|
Displays the name of the service provider. |
|
Displays the number of Cisco Unified Operations Managers related to the customer. |
|
Displays the number of clusters related to the customer. |
|
Displays the number of Data Centers related to the customer. |
|
Displays the number of customer equipment related to the customer. |
Viewing Jobs
The Jobs Summary page displays a list of the all the automatic and manual jobs added to your Cisco HCS as well as basic details about each one. Follow this procedure to view jobs.
Step 1 In the side menu, select Administration > Jobs.
Step 2 Hover the cursor over the cross-hairs next to the Job Type and the description of the job or the reason for the sync failure will be displayed. Select the item you want to sync.
The following table describes the fields that are displayed.
Table 7-23 Viewing Jobs
|
|
|
Displays the job type. |
|
Displays the job entity. |
|
Displays the entity list. |
|
Displays the initiated job date and time. |
|
Displays the completed job date and time. |
|
Displays the job status. |
|
Displays the job actions. |
|
View content using Quick Filter, Advanced Filter, or All selection from the drop-down list. You can Manage Preset filters from this drop-down list as well. |
If a sync is already in progress, rules are applied to determine if a new sync request is initiated or if the sync in progress is considered to have covered the data requested in the new sync request. The following table outlines the condition and the action for jobs.
Table 7-24 Rules for Syncs
|
|
SP sync req while SP sync in progress |
Complete in-progress sync. Update results for all jobs. |
All customer sync req while SP sync in progress |
Complete in-progress sync. Update results for all jobs. |
Single customer sync req while SP sync in progress |
Complete in-progress sync. Update results for all jobs. |
List of customers sync req while SP sync in progress |
Complete in-progress sync. Update results for all jobs. |
SP sync req while customer sync in progress |
Complete in-progress sync. Initiate new sync. |
SP sync req while customer list sync in progress |
Complete in-progress sync. Initiate new sync. |
Customer sync req while same customer sync in progress |
Complete in-progress sync. Update results for all jobs. |
Customer sync req while customer list sync in progress containing requested customer |
Complete in-progress sync. Update results for all jobs. |
Customer list sync req while customer list sync in progress |
Complete in-progress sync. Initiate new sync. |
Customer list sync req while customer sync in progress |
Complete in-progress sync. Initiate new sync. |
Related Topics
•Introduction to Cisco Hosted Collaboration Mediation Fulfillment
•The Cisco HCM-F Administrative Interface
•Infrastructure Manager Element Description
•CUCDM Sync Services
•vCenter Sync Services
•General Procedures
•Command Line Interface for Cisco HCM-F, page 10-1