//List of files which are indexed.
f = new Array();
f["0"]= " Create a custom ID range for virtual MAC addresses, virtual WWNs, or virtual serial numbers OneView, online help, help, REST API Create a custom ID range for virtual MAC addresses, virtual WWNs, or virtual serial numbers When the appliance starts for the first time, a random range, called the default range, is created for each pool In addition to this range, you can add an automatically generated range Before you create an automatically generated range, you must select an available generated range Each type of range uses a different REST API For example, to create a virtual MAC address range, you use restidpoolsvmacranges When you create a custom range, you must provide the attributes using one of the following combinations: The start address and end address The total count is calculated automatically based on the start address and end address The start count and total count The end address is calculated automatically based on the total count The range category is custom Prerequisites Minimum required session ID privileges: Network administrator virtual MAC addresses, virtual WWNs Server administrator virtual serial numbers Infrastructure administrator all ID types Creating a custom ID range for virtual MAC addresses using REST APIs POST restidpoolsvmacranges Creating a custom ID range for virtual WWNs using REST APIs POST restidpoolsvwwnranges Creating a custom ID range for virtual serial numbers using REST APIs POST restidpoolsvsnranges ";
f["1"]= " Logical Enclosures OneView, online help, help, REST API Logical Enclosures Use REST APIs to  Update the firmware in a logical enclosure Update enclosures in the logical enclosure from the enclosure group Configure an enclosure with an OA configuration script Download a logical enclosure support dump See more tasks Learn more About logical enclosures About OA configuration scripts logicalenclosures REST APIs ";
f["2"]= " Algorithms for securing the appliance CIC int, features, product description, reference, security, roles OneView, online help, help, REST API Algorithms for securing the appliance SSLTLS See Supported cipher suites Local user passwords: SHA256 Hashing algorithm with 8 bit Salt and 1000 iterations are used to hash the password Onetime Password mechanism for administrator password reset and Hewlett Packard Enterprise support SKEY onetime password mechanism Backup files: Backup files are encrypted with keys supplied by Hewlett Packard Enterprise Hewlett Packard Enterprise recommends that you encrypt backup files with an encryption key that you generate to ensure confidentiality and the integrity of the backup file Other passwords are encrypted using 128bit Blowfish Support dumps: Encryption: 128bit AES Hash: SHA256 The AES key is encrypted separately using 2,048bit RSA Updates: Not encrypted; digitally signed using SHA256 and 2,048bit RSA The following SSL cipher suites are enabled on the HPE OneView appliance web server The cipher suites support the connection among the browser, other clients, and the appliance Supported cipher suites SSL Cipher suite SSLTLS version Kx Au Enc Mac ECDHERSAAES256GCMSHA384 TLSv12 ECDH RSA AESGCM256 AEAD ECDHERSAAES256SHA384 TLSv12 ECDH RSA AES256 SHA384 ECDHERSAAES128GCMSHA256 TLSv12 ECDH RSA AESGCM128 AEAD ECDHERSAAES128SHA256 TLSv12 ECDH RSA AES128 SHA256 DHERSAAES256GCMSHA384 TLSv12 DH RSA AESGCM256 AEAD DHERSAAES256SHA256 TLSv12 DH RSA AES256 SHA256 DHERSAAES128GCMSHA256 TLSv12 DH RSA AESGCM128 AEAD DHERSAAES128SHA256 TLSv12 DH RSA AES128 SHA256 AES256GCMSHA384 TLSv12 RSA RSA AESGCM256 AEAD AES256SHA256 TLSv12 RSA RSA AES256 SHA256 AES128GCMSHA256 TLSv12 RSA RSA AESGCM128 AEAD AES128SHA256 TLSv12 RSA RSA AES128 SHA256 ECDHERSAAES256CBCSHA TLSv10  TLSv11  TLSv12 ECDH RSA AES256 SHA1 ECDHERSAAES128CBCSHA TLSv10  TLSv11  TLSv12 ECDH RSA AES128 SHA1 ECDHERSA3DESCBCSHA TLSv10  TLSv11  TLSv12 ECDH RSA 3DES SHA1 DHERSA3DESEDECBCSHA TLSv10  TLSv11  TLSv12 DH RSA AES256 SHA1 DHERSAAES128CBCSHA TLSv10  TLSv11  TLSv12 DH RSA AES128 SHA1 DHERSAAES256CBCSHA TLSv10  TLSv11  TLSv12 DH RSA AES SHA1 AES128CBC TLSv10  TLSv11  TLSv12 RSA RSA AES128 SHA1 AES256CBC TLSv10  TLSv11  TLSv12 RSA RSA AES128 SHA1 3DESEDECBC TLSv10  TLSv11  TLSv12 RSA RSA 3DES SHA1 The following SSL cipher suites are enabled on the HPE OneView appliance RabbitMQ server The cipher suites support the connection among the RabbitMQ clients of the appliance dhe_rsa,aes_256_cbc,sha256, dhe_dss,aes_256_cbc,sha256, rsa,aes_256_cbc,sha256, dhe_rsa,aes_128_cbc,sha256, dhe_dss,aes_128_cbc,sha256, rsa,aes_128_cbc,sha256, dhe_rsa,aes_256_cbc,sha, dhe_dss,aes_256_cbc,sha, rsa,aes_256_cbc,sha, dhe_rsa,aes_128_cbc,sha, dhe_dss,aes_128_cbc,sha, rsa,aes_128_cbc,sha, rsa,rc4_128,sha, rsa,rc4_128,md5 ";
f["3"]= " Upload a hotfix OneView, online help, help, REST API Upload a hotfix You can upload one or more hotfixes to the appliance and then create a custom baseline that includes the hotfix and an SPP This new custom SPP can then be applied to any resource managed by HPE OneView Uploading a custom firmware bundle using REST APIs POST restfirmwarebundle ";
f["4"]= " Activity notification OneView, online help, help, REST API Activity notification Use REST APIs to  Configure the appliance to send email notification of alerts Add an email recipient and filter pair Edit an email recipient and filter pair Delete an email recipient and filter Enable or disable email notification of alerts Send test email See more tasks Learn more About email notification of alert messages POST restappliancenotificationsemailconfig REST APIs GET restappliancenotificationsemailconfig REST APIs ";
f["5"]= " Resource model format OneView, online help, help, REST API Resource model format The resources support JSON JavaScript Object Notation for exchanging data using a REST API If not otherwise specified in the REST API operation, the default is JSON See also:  http:wwwjsonorg ";
f["6"]= " Read resource information published to the index OneView, online help, help, REST API Read resource information published to the index The information that appliance resources publish to the index is a subset of attributes that you can retrieve using simple to complex filter and query parameters To learn more about using these parameters, see Common REST API Parameters Prerequisites Minimum required session ID privileges: Infrastructure administrator Reading resource information published to the index using REST APIs GET restindexresources NOTE: The Index always returns the latest version of resource data, independent of what is sent in the XAPIVersion header on the request this header controls the Index DTO model, but not the data contained within To obtain a specific version of a resource’s data, perform a GET on that resource’s URI with the desired XAPIVersion header ";
f["7"]= " Server Hardware OneView, online help, help, REST API Server Hardware Use REST APIs to  Add a server blade to an enclosure Assign administrators to fix server hardware issues Create a rack server Delete a rack server Delete a server blade from management Identify server hardware that needs administrative attention Power on or power off server hardware Reassign the server profile to a server blade previously removed from an enclosure Read a rack server Read unsupported server hardware Refresh the connection between server hardware and the appliance Remove a server blade from an enclosure Update firmware for specific server hardware See more tasks Learn more About server hardware serverhardware REST APIs enclosures REST APIs ";
f["8"]= " Read an unmanaged device OneView, online help, help, REST API Read an unmanaged device Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator Reading an unmanaged device using REST APIs Select an unmanaged device URI GET restunmanageddevices Get the unmanaged device GET restunmanageddevices id ";
f["9"]= " Delete a local user account OneView, online help, help, REST API Delete a local user account Prerequisites Minimum required session ID privileges: Infrastructure administrator Deleting a user account using REST APIs Select a user account name GET restusers Delete the user account DELETE restusers userName ";
f["10"]= " Add a storage system storagesystemsall OneView, online help, help, REST API Add a storage system You add a storage system to bring it under management of the appliance by providing its IP address or host name, along with its credentials After you add the storage system, you can add networks and assign those networks to a storage array target port Prerequisites Minimum required session ID privileges: Infrastructure administrator or Storage administrator The storage system IP address or host name The storage system user name and password with root access The storage system is up and running and WSAPI service is enabled See the documentation for HPE StoreServ 3PAR Storage systems for more information The storage system is configured with domains and pools Adding a storage system using REST APIs Select the Fibre Channel or Fibre Channel over Ethernet network URIs GET restfcnetworks OR GET restfcoenetworks Add the storage system under appliance management and discover the storage array target ports POST reststoragesystems Specify the unmanagedPorts in the managedPorts collection and the expectedNetworkUri PUT reststoragesystems id NOTE: If you do not want to add networks at this time, set the expectedNetworkUri attribute to empty string  You can add the networks later using a PUT operation After you add the storage system, you can Add a storage pool and Create a storage volume ";
f["11"]= " Create multiple Ethernet networks using a single POST operation OneView, online help, help, REST API Create multiple Ethernet networks using a single POST operation When you create multiple Ethernet networks, you must specify VLAN IDs in the range 2–4094 To learn more about tagged networks, see About networks NOTE: When you add multiple Ethernet networks at once, you can only specify Tagged for the ethernetNetworkType attribute Prerequisites Minimum required session ID privileges: Network administrator Creating multiple Ethernet networks using a single POST operation using REST APIs POST restethernetnetworksbulk NOTE: The connectionTemplateUri attribute must be set to null ";
f["12"]= " Add channel partners OneView, online help, help, REST API Add channel partners Prerequisites Minimum required session ID privileges: Server administrator Adding channel partners using REST APIs Add channel partner ID POST restsupportchannelpartners Verify the partner ID with Hewlett Packard Enterprise POST restsupportchannelpartnersvalidator ";
f["13"]= " About activities CONTACT CI DOC OWNERS before modifying this content OneView, online help, help, REST API About activities An activity is a record of a user or systeminitiated action or task or an alert message to inform you that an event occurred that requires your attention An alert message is an important troubleshooting tool It indicates when an event occurred and which resource reported it An alert message provides details about the event and suggests a solution If a user or systeminitiated action is complete, there is a record for it If an action is not complete, you can see which subtasks were completed or are still running and which subtasks are interrupted or stopped The appliance interleaves tasks, alerts, and administrator's notes into a single view, which simplifies the correlation of user activity with system health You can view all activities, filter the activities by several criteria to view only those you want to see, or search for a specific activity You can assign alerts to the appropriate administrator for their timely resolution When issues are investigated and resolved, you can clear them so they no longer require your attention You can annotate alert messages to keep an historical record of issues and their resolutions, or you can note a decision that affected the alert resolution ";
f["14"]= " Update logical interconnect SNMP settings OneView, online help, help, REST API Update logical interconnect SNMP settings To update logical interconnect SNMP settings, perform a PUT operation to reapply all of the logical interconnect SNMP settings attributes View the logical interconnect SNMP settings attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes Prerequisites Minimum required session ID privileges: Infrastructure administrator Updating logical interconnect SNMP settings using REST APIs Select a logical interconnect URI GET restlogicalinterconnects Using the logical interconnect URI, get the logical interconnect SNMP settings GET logical interconnect URIsnmpConfiguration Edit the SNMP settings Update the logical interconnect SNMP settings PUT logical interconnect URIsnmpConfiguration ";
f["15"]= " Add an authentication login domain OneView, online help, help, REST API Add an authentication login domain You can use an external authentication login domain also called an enterprise directory to authenticate users logging in to the appliance instead of maintaining individual local login accounts If you replicate the authentication login domain for high availability or disaster tolerance, add the replicated login domain as a separate login domain Prerequisites Minimum required session ID privileges: Infrastructure administrator Information about the directory service you are adding: Directory name Protocol Base DN domain name Directory servers Obtain an X509 certificate from the directory service provider This certificate ensures the integrity of communication between the appliance and the directory service Creating an authentication login domain using REST APIs POST restlogindomains ";
f["16"]= " Remove a server blade from an enclosure OneView, online help, help, REST API Remove a server blade from an enclosure To remove a server blade from mnagement you phycially remove it from an enclosure When you remove a server blade from an enclosure, an alert is created If the server blade has an associated server profile, the server profile status will change to critical To learn more about how to reinsert the server blade, see Reassign the server profile to a server blade previously removed from an enclosure ";
f["17"]= " Create a data center OneView, online help, help, REST API Create a data center You define a data center’s physical topology by specifying the outer measurements of the data center and then adding and positioning racks containing systems, enclosures, and devices The appliance enables you to manage the power and cooling requirements for your servers, enclosures, and iPDUs Prerequisites Minimum required session ID privileges: Server administrator Creating a data center using REST APIs POST restdatacenters ";
f["18"]= " Update the interconnect firmware for HPE Virtual Connect Fibre Channel interconnects OneView, online help, help, REST API Update the interconnect firmware for HPE Virtual Connect Fibre Channel interconnects If you have an enclosure with an Virtual Connect Fibre Channel interconnect module and you want to bring the enclosure under management of the appliance, the interconnect’s firmware must be upgraded first in the following situations See the HPE OneView Support Matrix for a list of supported Virtual Connect Fibre Channel interconnects If you have an Virtual Connect Fibre Channel interconnect with IPv6 addresses in an enclosure, the interconnect firmware version must be 410, the minimum supported baseline version If you have an Virtual Connect Fibre Channel interconnect in an enclosure by itself or with other Virtual Connect Fibre Channel interconnects only, the interconnect firmware version must be 410, the minimum supported baseline version Prerequisites  Required privileges: Network administrator or Infrastructure administrator Updating the interconnect firmware for Virtual Connect Fibre Channel interconnects Use the Onboard Administrator or the external DHCP server to assign an IPv4 address to the interconnect Use HPSUM or the Virtual Connect Support Utility VCSU to update the firmware on the interconnect Optional: After the firmware is upgraded, use the Onboard Administrator or the external DHCP server to assign an IPv6 address to the interconnect ";
f["19"]= " Best practices for monitoring health OneView, online help, help, REST API Best practices for monitoring health To ensure the health of the components in your data center environment, follow these best practices Overall health monitoring Server hardware health monitoring Network health monitoring Overall health monitoring NOTE: You can view health and alerts on some monitored servers To see what servers can be monitored, see monitored server hardware in the HPE OneView Support Matrix Monitoring step Filter alerts based on severity or date to view current health issues GET restalertsfilter=severity='UNKNOWN, OK, DISABLED, WARNING,CRITICAL'&filter=created='YYYYMMDDThh:mm:sssssZ' NOTE: The DISABLED severity is not applicable to alerts Related information: Activity Get alerts for a specific physical resource type, such as server hardware GET restalertsfilter=physicalResourceType='physical_server' Related information: Server Hardware View the originating events that caused a specific alert Select an alert GET restalerts Get a specific alert using the alert ID GET restalerts id Get the associated events GET restevents id Fix the problem Use the recommended fix perform a GET operation on the specific alert resource and view the correctiveAction attribute, or research the alert Server hardware health monitoring A server or servers turn to a warning or critical status when something is not correct within the appliance If a server profile has been applied to a failed server, the server profile will also be in a failed status Monitoring step Use details from the alert to fix the problem When available, attempt the recommended fix first In some cases, additional research of the alert might be needed to best determine the fix GET restalertsfilter=physicalResourceType='physical_servers'&filter=severity='WARNING, CRITICAL' Related information: Activity Make sure that server profiles are appropriately assigned to the server hardware Related information: Create a server profile Network health monitoring To determine the current health of a network or networks on the appliance, view alerts for interconnects and logical interconnects to verify the correct connections To list alerts, you can perform a GET operation on alerts and filter for alerts related to interconnects To list states, you can perform a GET operation on interconnects and logical interconnects and filter for an OK state Monitoring step View alerts for interconnects Select an interconnect alert GET restalertsfilter=physicalResourceType='interconnect'&filter=severity='WARNING, CRITICAL' Get a specific alert using the alert ID GET restalerts id Related information: Interconnects Filter for logical interconnects with unhealthy stacking Get unhealthy logical interconnect GET restlogicalinterconnectsfilter=stackingHealth='Unknown, Disconnected' View specific unhealthy interconnect using the interconnect ID GET restlogicalinterconnects id Related information: Logical Interconnects Use information provided in the alert to fix the problem Use the recommended fix if there is one, or research the alert Related information: Activity ";
f["20"]= " Where to find HPE OneView documentation OneView, online help, help, REST API Where to find HPE OneView documentation User guides and other manuals HPE OneView user guides and other manuals are available on the Hewlett Packard Enterprise Information Library See Websites for other information resources Online help To view help on the appliance, click to open the Help sidebar Links in the sidebar open help in a new browser window or tab: Help on this page opens help for the current screen Browse help opens the top of the help system where you decide which help topics you want to read about Browse REST API help opens help for API scripting and reference information Clicking on a screen or dialog box opens contextsensitive help for that dialog box NOTE: To submit feedback about HPE OneView documentation, send email to docsfeedback@hpecom See also  Enable offappliance browsing of UI help and REST API help ";
f["21"]= " HPE OneView REST API scripting help OneView, online help, help, REST API HPE OneView REST API scripting help The REST API scripting documentation is designed to work in tandem with the HPE OneView REST API Reference The scripting scenarios list the sequence of REST API operations you must invoke for each task and include links into the HPE OneView REST API Reference to provide details about the resource model schema and JSON JavaScript Object Notation examples Topic Where to find the information Where can I learn about the REST interface Learning about REST APIs What tasks can I perform using the REST APIs What can I do with HPE OneView REST APIs Where can I find detailed reference information about the REST API resource model schema and JSON examples HPE OneView REST API Reference What tasks can I perform using the appliance UI HPE OneView Help How do I subscribe to messages on the StateChange Message Bus Using the StateChange Message Bus SCMB How do I subscribe to messages on the Metric Streaming Message Bus Using the Metric Streaming Message Bus MSMB Where can I download code samples and a technical preview of PowerShell and Python libraries PowerShell and Python code sample libraries Where can I find HPE OneView user guides and other manuals http:wwwhpecominfooneviewdocs How do I submit documentation feedback to Hewlett Packard Enterprise docsfeedback@hpecom Legal notices  To see the publication date, help system version and edition, and copyright and legal information, see the legal notices ";
f["22"]= " Data services OneView, online help, help, REST API Data services HPE OneView REST APIs allow you to enable the collection of specific metrics from physical servers, enclosures, and power devices that can be streamed to subscribers, using a message bus You can also configure HPE OneView to stream remote system logs from managed server hardware for later analysis Use REST APIs to  Fetch metric streaming capability Fetch metric streaming configuration Update metric streaming configuration Fetch remoteSyslog configuration Update remoteSyslog configuration See more tasks Learn more About data services About accessing HPE OneView message buses ";
f["23"]= " Reset the administrator password OneView, online help, help, REST API Reset the administrator password Before you can reset the administrator password, you must access the appliance console and create a temporary administrator password You use this password in the REST API complete the administrator password reset See Controlling access to the appliance console Prerequisites Minimum required session ID privileges: Infrastructure administrator Temporary administrator password from the appliance console Resetting the administrator password using REST APIs PUT restusersadministratorresetPassword ";
f["24"]= " Create an unmanaged device OneView, online help, help, REST API Create an unmanaged device Devices that the appliance does not automatically add and manage are unmanaged devices You can manually add these devices to the appliance for tracking, inventory, and power management purposes Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator Creating an unmanaged device using REST APIs POST restunmanageddevices ";
f["25"]= " Read interconnect statistics OneView, online help, help, REST API Read interconnect statistics To analyze network traffic on a specific interconnect requires several different REST APIs to view an interconnect, port, or subport To see which statistics are available, view the resource models for each REST API: SwitchStatistics, PortStatistics, or SubportStatistics FIP snooping information is available through PortStatistics and SubportStatistics Prerequisites Minimum required session ID privileges: Infrastructure administrator Reading interconnect statistics using REST APIs Select an interconnect URI GET restinterconnects Using the interconnect URI, get all statistics for all the ports GET interconnect URIstatistics Reading port statistics using REST APIs Select an interconnect URI GET restinterconnects Using the interconnect URI, select a port name GET interconnect URIports Using the interconnect URI and port name, get the port and subport statistics GET interconnect URIstatistics portName Reading subport statistics using REST APIs Select an interconnect URI GET restinterconnects Using the interconnect URI, select a port name and subport number GET interconnect URIports Using the interconnect URI, port name, and subport number, get the subport statistics GET interconnect URIstatistics portNamesubport subPortNumber ";
f["26"]= " Update a server hardware type OneView, online help, help, REST API Update a server hardware type To update a server hardware type, perform a PUT operation to reapply all of the server hardware type attributes View the server hardware type attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes Prerequisites Minimum required session ID privileges: Server administrator Updating a server hardware type using REST APIs Select the server hardware type URI GET restserverhardwaretypes Get the server hardware type using the URI from step 1 GET restserverhardwaretypes id Edit the server hardware type Update the server hardware type PUT restserverhardwaretypes id ";
f["27"]= " About c7000 enclosures OneView, online help, help, REST API About c7000 enclosures A c7000 enclosure is added into HPE OneView as a Managed including Migratedor Monitored enclosure Managed HPE OneView manages the enclosure enabling you to apply configurations, deploy server profiles, monitor operation status, collect statistics, and alert users to specific conditions Managed enclosures require an HPE OneView Advanced or an HPE OneView Advanced wo iLO license See License types Monitored HPE OneView monitors hardware for inventory and hardware status only Server profile management is not allowed within HPE OneView for a monitored enclosure Monitored enclosures use a free HPE OneView Standard license See License types Migrated HPE OneView migrates an enclosure from Virtual Connect Manager VCM so that its contents can be managed in HPE OneView If you migrate an enclosure, the existing configuration is captured and recreated in HPE OneView, provided the configuration is supported by HPE OneView ";
f["28"]= " Update the public key OneView, online help, help, REST API Update the public key The public key verifies that Hewlett Packard Enterprise created its RPMs and update packages and that the code has not been modified since it was signed Before you update the public key, you must obtain a new public key Prerequisites Minimum required session ID privileges: Infrastructure administrator New HEP public key Updating the public key using REST APIs PUT restappliancefirmwareverificationKey ";
f["29"]= " Logical Switches OneView, online help, help, REST API Logical Switches Use REST APIs to  Create a logical switch Edit a logical switch Update a logical switch from group Change a logical switch operational mode Refresh a logical switch Delete a logical switch See more tasks Learn more About logical switches Logicalswitches REST APIs ";
f["30"]= " Reports OneView, online help, help, REST API Reports Use REST APIs to  Save a report Learn more About reports reports REST APIs ";
f["31"]= " Read a server profile OneView, online help, help, REST API Read a server profile Reading a server profile using REST APIs Select a server profile URI GET restserverprofiles Read the server profile GET restserverprofiles id ";
f["32"]= " Documentation feedback This module is for the boilerplate documentation feedback text OneView, online help, help, REST API Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback  docsfeedback@hpecom When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document For online help content, include the product name, product version, help edition, and publication date located on the legal notices page ";
f["33"]= " About logical switches OneView, online help, help, REST API About logical switches A logical switch is added into HPE OneView as a managed or monitored logical switch The logical switch can consist of a maximum of two physical topofrack switches external to the c7000 enclosure configured in a single stacking domain There is a connectivity limitation of one logical interconnect to one logical switch Interconnects within a logical interconnect cannot be connected to more than one logical switch A logical switch is based on a logical switch group configuration If the logical switch transitions to an Inconsistent with group state because of changes in either the logical switch or the logical switch group, to return to a consistent state About assigning Cisco Nexus switches to a logical switch  You can create a logical switch with a maximum of two Cisco Nexus switches When there are two Cisco Nexus switches in a logical switch, they are expected to be in a virtual port channel vPC environment vPC must be configured on both switches, and they should belong to the same vPC domain For information about supported switches, see the Hewlett Packard Enterprise Information Library for supportability information More information Managed logical switches Monitored logical switches Logical switch configuration guidelines About logical switch groups Managed logical switches Adding a logical switch for HPE OneView management enables you to apply configurations needed for the interconnect uplink ports to be provisioned at the switch internal downlink ports Managed mode allows you to deploy server profile connections for interconnects, monitor operation status, collect statistics, and alert users to specific conditions and incompatibilities between the upstream switch and interconnect When adding a logical switch, any existing configuration for ports connected to HPE OneView interconnects is reconfigured based on configuration specified for the HPE OneView interconnect uplinks Any port that is actively managed by an external management system remains unchanged and is not brought into HPE OneView management Before adding a managed logical switch Before you add a logical switch as managed, consider the following for Fabric Extender and Virtual Connect interconnects physically connected to the logical switch: When only IPv4 Ethernet networks are assigned to an uplink set at creation time, the uplink set can be physically connected to any upstream switch in the logical switch When an FCoE network is assigned to an uplink set at creation time, the uplink set is limited to singlehomed physical connectivity and all uplink ports must connect to the same upstream switch in the logical switch If a port is subsequently added to the uplink set with an FCoE network or an existing port in the uplink set is connected to a second upstream switch, that port is not available for configuration and an alert is generated If a new port added to the uplink set is connected to the same switch as the other ports, that port is available to carry traffic and an alert is not generated To change an uplink set from singlehomed connectivity to multihomed connectivity or viceversa, the uplink set configuration must be deleted and recreated with the appropriate network assignments and physical configuration Make sure that LLDP is enabled on the topofrack switch internal downlink ports where Virtual Connect interconnects under HPE OneView management are connected More information About logical switches Logical switch configuration guidelines Create a logical switch Change a logical switch operational mode Monitored logical switches Adding a logical switch as monitored enables HPE OneView to monitor the logical switch for operation status, collect statistics, and alert users to specific conditions and incompatibilities between the switch and Fabric Extender or Virtual Connect interconnect In the monitored mode, deployment of the server profile connections is supported for HPE Virtual Connect interconnects but not for Fabric Extender FEX interconnects More information About logical switches Change a logical switch operational mode Logical switch configuration guidelines When Virtual Connect interconnects are connected to a logical switch, an uplink set cannot span multiple interconnects This limitation is similar to FEX interconnects However, multiple uplink sets are supported on a single Virtual Connect interconnect When you enable or disable a topofrack switch internal port, the associated port on a FEX interconnect also displays the updated port status When retrieving MAC addresses for FEX interconnects, only the entries that are associated with the managed FEX interconnects are displayed If an FCoE network is assigned to an uplink set that is configured as dualhomed, an invalid configuration, that FCoE network is not provisioned on the switch Deployment of any server profile connection with this FCoE network will fail When a logical switch is defined and configured with only a single physical switch, the uplink set associated with any FEX module connected to this logical switch is considered singlehomed Therefore, you can add an FCoE network to the uplink set even if the uplink set was initially created only with Ethernet networks Deployment of any server profile connection with this FCoE network will succeed For server profiles created for server ports connected to FEX interconnects, Ethernet networks are only supported on physical function a, and FCoE networks are only supported on physical function b at the server port When both physical functions have connections defined, traffic is split evenly across both ports If HPE OneView cannot log in to the switch, a critical alert is generated Prevent any event on the switch that might trigger switch configuration; otherwise, the switch transitions to ConfigError state and you must reapply the configuration on the associated logical interconnects to recover If HPE OneView is unable to claim a member switch of the logical switch when the operational mode of the logical switch is Managed, the operating state of the switch will transition to Added with Error In this case, the Message of the Day MOTD banner on the switch will indicate that the switch is currently claimed by another HPE OneView appliance and the message “ This switch is being controlled by OneView Domain, Appliance ID: ” displays You should remove the logical switch from that HPE OneView appliance, and then perform a refresh on the logical switch from the current HPE OneView appliance to reinitiate the claim operation HPE OneView does not fully automate configuration of FCoE connectivity on the switch specified in the logical switch For each FCoE network specified in the uplink set, HPE OneView only provisions the VLAN for that network on the switch Network administrators must provision additional configuration for FCoE connectivity manually on the switch in addition to what HPE OneView provisions To deploy server profile connections to a FEX interconnect, HPE OneView provisions the virtual Fibre Channel interface VFC, VFC binding to FEX downlink port, and VSAN interface assignment on the switch For the deployment of server profile connections for a Virtual Connect interconnect, the Network administrator must configure the virtual Fibre Channel interface vFC, VFC binding to server port, and VSAN interface assignment binding manually When a Nexus switch expansion module is removed, a warning alert is generated unless the module is powered off HPE OneView can detect configuration changes that occur on the switches specified in the logical switch when it no longer matches the configuration that HPE OneView provisions Warning alerts are generated Administrators can correct the configuration manually or reapply the configuration on the associated logical interconnects to recover ";
f["34"]= " About restoring the appliance CONTACT CI DOC OWNERS before modifying this content OneView, online help, help, REST API About restoring the appliance Restoring an appliance from a backup file replaces all management data and most configuration settings with the data and settings in the backup file, including user names and passwords, audit logs, and available networks The appliance is not operational during the restore operation and it can take several hours to perform; the more resources and devices to restore, the longer the restore operation takes A restore operation cannot be canceled or undone after it has started The appliance blocks login requests while a restore operation is in progress IMPORTANT: A restore operation is required to recover from catastrophic failures, not to fix minor problems that can be resolved in other ways Therefore, after the restore operation is complete, you can restore an appliance from a backup file that was created on the same appliance or, if an appliance fails and cannot be repaired, from a backup file from a different appliance In this case, the backup file must have been created from an appliance running the same version of HPE OneView Actions during the restore operation Description Validates the resource inventory During a restore operation, the appliance firmware validates the resource inventory enclosures, servers, interconnects and reconciles the data in the backup file with the current state of the managed environment The state of the managed environment is likely to be different from the state of that environment at the time the backup file was created After the restore operation, the appliance uses alerts to report any discrepancies that it cannot resolve automatically If you removed, and then readded an enclosure after a backup file was created, and then perform a restore operation using that backup file, you must refresh the enclosure before the appliance can connect If you added server hardware to the appliance after the backup file was created, that hardware is not in the appliance database when the restore operation completes You must add that hardware to the appliance and then repeat any other configuration changes such as assigning server profiles that were made between the time the backup file was created and the restore operation completed Rediscovers enclosures to validate contents During the restore operation, the appliance rediscovers each enclosure to validate its contents—especially to ensure that the appliance still claims them Then the appliance rediscovers each server and clears the virtual IDs of any servers added to an enclosure since the last time the backup file was created The appliance also refreshes all rack servers to ensure they are claimed Clears virtual IDs The appliance clears virtual IDs for server hardware that does not have a profile assigned but does have virtual IDs configured These servers most likely had a profile assigned after the last backup was made ";
f["35"]= " Read labels OneView, online help, help, REST API Read labels Prerequisites Minimum required session ID privileges: a session ID with privileges to edit the resource model Reading a label using REST APIs Perform a GET operation on a resource collection URI for example, restserverprofiles and then select a resource model URI Get the label using the URI from step 1 GET restlabelsresources resource URI ";
f["36"]= " Delete a logical switch group OneView, online help, help, REST API Delete a logical switch group You cannot delete a logical switch group while it is being used by one or more logical switches To delete the logical switch group, first delete the logical switches using the logical switch group Prerequisites Minimum required session ID privileges: Network administrator Deleting a logical switch group using REST APIs Select a logical switch group URI GET restlogicalswitchgroups Delete the logical switch group using the URI from step 1 DELETE restlogicalswitchgroups id ";
f["37"]= " Read utilization for specific server hardware OneView, online help, help, REST API Read utilization for specific server hardware You can view historical data for server hardware utilization, such as CPU utilization, ambient temperature, average power and average peak power, for the last 24 hours for a specified time range Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator Reading utilization for specific server hardware using REST APIs Select a server hardware URI GET restserverhardware Get utilization data for specific server hardware GET restserverhardware idutilization ";
f["38"]= " SANs sans OneView, online help, help, REST API SANs Use REST APIs to  View managed SANs See more tasks Learn more About SANs fcsansproviders REST APIs fcsansdevicemanagers REST APIs fcsansmanagedsans REST APIs ";
f["39"]= " Querying resources and pagination using common REST API parameters OneView, online help, help, REST API Querying resources and pagination using common REST API parameters Querying resources You can use a set of common parameters to customize the results returned from a GET operation, such as sorting or filtering Each REST API specification lists the set of available common parameters For more information, see Common REST API Parameters Pagination when querying for a collection of resources When you perform a GET operation to retrieve multiple resources that is, a GET on a collection URI, such as restserverprofiles, the resources are returned in a collection object that includes an array of resources along with information about the set of resources returned This collection of resources may be automatically truncated into pages to improve performance when a query would return a large number of resources The collection attributes described below provide information needed to determine whether the full set of resources were returned, or if additional queries are required to retrieve additional pages For example, a collection object includes a next page and previous page URI These URIs indicate whether additional pages are available, and can be retrieved via a GET operation on these URIs This provides a simple model for ensuring all resources in the query have been retrieved, by doing iterative GETs on the nextPageUri attribute until the attribute comes back emptynull See Example: Return all resources in a specific collection query below It’s also possible to query for a specific page of resources, using the start and count query parameters These parameters indicate the index of the first resource to be returned, and the number of resources to return in the page, respectively NOTE: Queries across multiple pages in a collection are stateless, and are based simply on the start index and a count of resources returned from that starting point at the time the query is made For example, if any server profiles were added or deleted after you performed a GET operation using a specific next page URI from a collection of server profile resources, and you perform the GET again, the returned page using the same next page URI may not contain the same set of resources Note also that the specific set of resources returned with a given start and count parameter is highly dependent on any filter, query and sort parameters sent in the request, therefore it’s important to always pass the same filter, query and sort parameters on all requests for additional pages The nextPageUri and prevPageUri attributes will be prepopulated with any filter, query and sort parameters from the current request Attributes returned in all GET operations performed on a collection URI, for example restserverprofile:  total The total number of resources available in the requested collection taking into account including any filters Not necessarily what was returned count The actual number of resources returned in the members attribute start The zerobased index of the first item returned in the members attribute members The array of resources returned in the current result set nextPageUri A URI that can be used to query for the next page in the result set using the same count specified in the current query prevPageUri A URI that can be used to query for the previous page in the result set using the same count specified in the current query NOTE: A null or empty nextPageUri or prevPageUri attribute is an indication that you have reached the last or first page respectively in the query This allows scripts to iterate on nextPageUri until null, in order to retrieve the full set of resources in the query Example: Return all resources in a specific collection query  The number of resources returned in a query might not match what was specified in the count parameter Clients must always check the returned results to determine whether the full results set was returned or not The two reasons that all the resources may not be returned in a query are: You've reached the last page of the query and there are simply not that many resource left to return This is also indicated by a returned prevPageUri with a null value For performance reasons, the service may automatically truncate the returned result set, requiring additional GET requests with appropriate start & count parameters set in order to retrieve the full set of resources The simplest way to make sure that you have retrieved all resources in a specific collection is to always perform iterative GET requests using the returned nextPageUri until the value is null See the following example in pseudocode based on any filtersqueries and sort order: currentCollection = doGetrestserverhardware; allResources = currentCollectionmembers; While currentCollectionnextPageUri  currentCollection = doGetcurrentCollectionnextPageUri; allResourcesAppendcurrentCollectionmembers;  ";
f["40"]= " Delete a server profile OneView, online help, help, REST API Delete a server profile Prerequisites Minimum required session ID privileges: Server administrator Deleting a server profile using REST APIs Select a server profile URI GET restserverprofiles Delete the server profile DELETE restserverprofiles id ";
f["41"]= " Error handling OneView, online help, help, REST API Error handling If an error occurs during a REST API operation, a 4 xx clientside or 5 xx appliance error is returned along with an error message  ErrorMessage resource model The error message contains a description and might contain recommended actions to correct the error A successful REST API POST operation returns the newly created resource synchronous or a TaskResource URI in the Location header asynchronous ";
f["42"]= " Update the allocated IDs in a range for virtual MAC addresses OneView, online help, help, REST API Update the allocated IDs in a range for virtual MAC addresses If you want to reserve or allocate IDs in a virtual MAC address range, you can update the allocated IDs To update a virtual MAC address range, perform a PUT operation to reapply all of the virtual MAC address attributes View the virtual MAC address range attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes Prerequisites Minimum required session ID privileges: Infrastructure administrator, Network administrator, or Server administrator Updating the allocated IDs in a range for virtual MAC addresses using REST APIs Select a virtual MAC address range URI GET restidpoolsvmac Get the virtual MAC address range and note the allocatorUri GET restidpoolsvmacranges id Update the allocated IDs using the allocatorUri from step 2 PUT restidpoolsvmacranges idallocator ";
f["43"]= " About server hardware types OneView, online help, help, REST API About server hardware types A server hardware type defines the physical configuration for server hardware and defines the settings that are available to server profiles to be assigned to that type of server hardware For example, the server hardware type for the HPE ProLiant BL460c Gen8 Server Blade includes a complete list of BIOS settings and the defaults for that model The appliance creates server hardware types according to the server hardware it detects The server hardware type is used when you create a server profile to show which settings are available ";
f["44"]= " Refresh the connection between server hardware and the appliance OneView, online help, help, REST API Refresh the connection between server hardware and the appliance If server hardware has lost connectivity or is not synchronized with the appliance, you need to refresh it During normal operation, server hardware can lose connectivity with the appliance and become out of sync if you make changes to it through the iLO or OA To prevent loss of connectivity, use the appliance to make changes to server hardware Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator Refreshing server hardware using REST APIs PUT restserverhardware idrefreshState ";
f["45"]= " Using a message bus to send data to subscribers OneView, online help, help, REST API Using a message bus to send data to subscribers Use REST APIs to  Connect to the SCMB Set up a queue to connect to the HPE OneView SCMB exchange Connect to the MSMB Set up a queue to connect to the HPE OneView MSMB exchange See more tasks Learn more About accessing HPE OneView message buses JSON structure of message received from the SCMB JSON structure of message received from the MSMB ";
f["46"]= " Read a logical interconnect MAC address table OneView, online help, help, REST API Read a logical interconnect MAC address table The MAC address table can be used to troubleshoot your network The table includes information to help you identify the associated networks, uplink sets, and server profiles You can get up to a maximum of 100 entries per GET operation Prerequisites Minimum required session ID privileges: Infrastructure administrator or Network administrator Reading a logical interconnect MAC address table using REST APIs Select the logical interconnect URI GET restlogicalinterconnects Get the logical interconnect MAC address table GET logical interconnect URIforwardinginformationbase ";
f["47"]= " Change a logical switch operational mode OneView, online help, help, REST API Change a logical switch operational mode A logical switch operating in one operation mode can be changed to another mode When changing a logical switch from operational mode monitored to managed, you might be required to reconfigure interconnects specified by the logical switch before the configurations are applied at the switches in the logical switch When changing the operational mode from operational mode managed to monitored, you are warned that existing configurations might no longer be operational, but they will not be removed from the logical switch Any future configuration of the monitored logical switch must be performed outside of HPE OneView management For FEX interconnects, server profile connections are marked as failed Prerequisites Minimum required session ID privileges: Network administrator Changing a logical switch operational mode using REST APIs Select a logical switch URI GET restlogicalswitches Change the operation mode of the logical switch using the URI from step 1 PUT restlogicalswitches id ";
f["48"]= " Reapply a logical interconnect group to bring a logical interconnect into compliance OneView, online help, help, REST API Reapply a logical interconnect group to bring a logical interconnect into compliance If a logical interconnect is not compliant with its logical interconnect group, you can reapply the logical interconnect group to make the logical interconnect compliant For example, if you replace a physical interconnect in the logical interconnect, and it needs to be compliant with the logical interconnect, you can reapply the logical interconnect group After the logical interconnect group is reapplied, the physical interconnect has the same configuration as other physical interconnects in the same logical interconnect Prerequisites Minimum required session ID privileges: Network administrator Reapply a logical interconnect group to bring a logical interconnect into compliance using REST APIs Select a logical interconnect URI GET restlogicalinterconnects Using the logical interconnect URI, reapply the logical interconnect group PUT logical interconnect URIcompliance NOTE: If you know the specific physical interconnect that is not compliant with a logical interconnect, you can perform a GET restinterconnects id on the physical interconnect to view the associated logical interconnect Next, you can reapply the logical interconnect group to the logical interconnect ";
f["49"]= " Save a report OneView, online help, help, REST API Save a report Select a report by its number and format The specified report, which contains only tabular data, is returned as an attachment in the response body Prerequisites Required session ID privileges: Network administrator, Server administrator, Infrastructure administrator, Storage administrator Retrieve a list of reports using REST APIs Retrieve a list of available reports GET restreports Saving a report using REST APIs Optionally, retrieve a list of available report numbers See previous procedure Generate and return a report by its reportnumber and format For a commaseparated values report format, use: GET restreports reportnumbersaveformat='csv' For a report formatted for Microsoft Excel, use: GET restreports reportnumbersaveformat='xlsx' ";
f["50"]= " Read a network set OneView, online help, help, REST API Read a network set Prerequisites Minimum required session ID privileges: Network administrator Reading a network set using REST APIs Select a network set URI GET restnetworksets Read the network set GET restnetworksets id ";
f["51"]= " Create a user with local authentication OneView, online help, help, REST API Create a user with local authentication You can add a user authorized to access all resources managed by the appliance full access user or a user who has access based on their job responsibilities rolebased specialist For each of these users, authentication is confirmed by comparing the user login information to an authentication directory hosted locally on the appliance The default administrator login for the appliance is automatically assigned with full access Infrastructure administrator privileges Prerequisites Minimum required session ID privileges: Infrastructure administrator You must have the following information: User's unique identifier name Initial password User's full name Optional: Contact information for the user Creating a new local user using REST APIs POST restusers See also  Quick Start: Initial configuration using REST APIs top of chapter ";
f["52"]= " About enclosure groups OneView, online help, help, REST API About enclosure groups An enclosure group is a logical resource that defines a standard configuration for member logical enclosures The network connectivity for an enclosure group is defined by the logical interconnect groups associated with the enclosure group Enclosure groups and logical interconnect groups A logical interconnect group that is assigned to a bay within an enclosure group must have that bay populated within the logical interconnect group All populated bays in a logical interconnect group must be assigned to the enclosure group For example, a logical interconnect group that has bays 1 and 2 populated must be assigned to bays 1 and 2 of the enclosure group in order for the enclosure group to be created ";
f["53"]= " About firmware bundles OneView, online help, help, REST API About firmware bundles The appliance provides firmware management across the data center with no additional tools to download and install Using the firmware management features built in to the appliance, you can define firmware baselines and perform firmware updates across many resources When you add a resource to the appliance, the appliance automatically updates the resource firmware to the minimum version required to be managed by the appliance or version defined to be a baseline See also About unsupported firmware A firmware bundle, also known as an Service Pack for ProLiant SPP, is a comprehensive collection of firmware and system software components, all tested together as a single solution stack that includes drivers, agents, utilities, and firmware packages Firmware bundles enable you to update firmware on HPE ProLiant servers, controllers, storage, server blades, and enclosures You can forcibly downgrade appliance firmware to an older version, but be aware that doing so can result in slower installation speeds and has the potential to render the device unusable Firmware repository An embedded firmware repository enables you to upload SPP firmware bundles and hotfixes to the appliance and deploy them across your environment according to your best practices You can view the versions and contents of the SPPs in the repository from the Firmware Bundles screen Selecting a firmware bundle displays its release date, supported languages and operating systems, and the bundle components The screen also displays the amount of storage space available for additional firmware bundles on the appliance You cannot add a firmware bundle that is larger than the amount of space available in the repository NOTE: To ensure that your hardware has the latest and most robust firmware bundle that takes advantage of all available management features, download the latest firmware bundle to your appliance and add it to the firmware repository HPE OneView supports 128 parallel server firmware updates for Windows and Linux, and 10 parallel server firmware updates for ESXi About applying SPPs as baselines You can apply SPPs as baselines to enclosures, interconnects, and server profiles, establishing a desired version for firmware and drivers across devices When you download an SPP from http:wwwhpecominfospp to your local system, upload it to the firmware bundle repository on the appliance You can use the PATCHrestlogicalenclosuresid REST API to update enclosure firmware and the restlogicalinterconnectsidfirmware REST API to update logical interconnect firmware Also, you can use the restserverprofilesid REST API set the firmware baseline for the assigned server hardware You can remove any or all SPPs from the firmware bundle repository However, Hewlett Packard Enterprise recommends you have at least one SPP available at all times because an SPP is required when adding resources to the appliance that are below the minimum firmware versions for monitoring or managing If you want to delete an SPP, Hewlett Packard Enterprise recommends that you reassign all resources to a different SPP before removing the SPP For c7000 enclosures, select Manage manually if you want to manage the firmware using another tool About uploading and using hotfixes Hewlett Packard Enterprise sometimes releases component hotfixes between main SPP releases Hewlett Packard Enterprise notifies you that a hotfix is available to upload and provides details about the SPP to which the hotfix applies Create a custom SPP in HPE OneView using the base SPP and the hotfix See Upload a hotfix for more information The new custom SPP can be used to set the baseline on the various managed resources in HPE OneView If a hotfix pertains to a managed resource that is already on the baseline, then the hotfix alone is applied NOTE: If the firmware update target system is Linux OS, the HPE ProLiant System ROM version listed is the ROM Linux hotfix component If not, the latest ROM version updated in the SPP bundle is listed About unsupported firmware When you add a resource to bring it under management, the resource firmware must be updated to the minimum supported level The appliance attempts to automatically update the firmware while the resource is being added to the appliance If the update fails, an alert is generated NOTE: You must upload a supported SPP to the appliance firmware repository before you can update device firmware See http:wwwhpecominfohpeoneviewupdates to obtain HPE OneView software updates and productspecific firmware bundles Unsupported firmware for firmware bundles If you attempt to add a firmware bundle that contains firmware below the minimum versions supported, an alert is generated and the firmware bundle is not added to the appliance firmware repository Unsupported firmware for enclosures When adding an enclosure, the appliance: Generates an alert if the logical interconnect firmware for the interconnects is below the required minimum level or if the interconnect firmware levels do not match You must update the logical interconnect firmware from the Logical Interconnects screen or REST APIs Updates the OA firmware automatically, if below the required minimum Must have a supported SPP installed on the appliance Updates the iLO firmware automatically, if below the required minimum Must have a supported SPP installed on the appliance Unsupported firmware for logical enclosures When adding a logical enclosure, the appliance: Generates an alert if the actual firmware versions for one or more components do not match the required minimum Even if you do not specify a baseline SPP and iLO firmware will be updated automatically, if below the required minimum Must have a supported SPP installed on the appliance Select the firmware baseline from the Logical Enclosures screen or REST APIs Unsupported firmware for server profiles You are prevented from applying server profiles if the associated iLO firmware is below the minimum supported version Unsupported firmware for interconnects If you attempt to add an interconnect with firmware that is below the minimum supported version, an alert is generated You must update the logical interconnect firmware from the Logical Interconnects screen or REST APIs About updating firmware When a device is added, the firmware is automatically updated to the firmware management baseline specified, except for: HPE ProLiant G6 servers and HPE ProLiant G7 servers which must be managed outside of HPE OneView Virtual Connect interconnect firmware which is managed separately as part of the Logical Interconnect See “Update firmware on logical interconnects for c7000 enclosures in the online help NOTE: When adding an enclosure and the OA or iLO firmware is below the minimum supported version for HPE OneView, the firmware is automatically updated using the SPP that contains the latest OA or iLO firmware while the enclosure is being added If all SPPs have been deleted, however, such an enclosure cannot be imported In this situation, first upload an SPP that provides at least the minimum required versions for the OA and the iLO before adding the enclosure Every resource  OA, iLO, server, or Virtual Connect goes offline when you upgrade its firmware Always perform the upgrade during a maintenance window To help minimize downtime during firmware activation, see See “Maintain availability during Virtual Connect interconnect firmware upgrades” in the online help Resource When you update firmware Enclosures The OA Onboard Administrator is taken offline when you update firmware for an enclosure Server profiles Firmware updates require that you edit the server profile to change the firmware baseline You must power down the server hardware to which the server profile is assigned before you change the firmware baseline Firmware baseline can be changed while server power is on if Smart Update Tools is used Interconnects An interconnect is taken offline when you: Update or activate firmware for a logical interconnect Staging firmware does not require interconnects be taken offline Update firmware for an enclosure and select the option to update the enclosure, logical interconnect, and server profiles If an interconnect has firmware that has been staged but not activated, any subsequent reboot of that interconnect activates the firmware, which takes the interconnect offline You can prevent the loss of network connectivity for servers connected to a logical interconnect that has a stacking mode of Enclosure and a stacking health of Redundantly Connected by updating firmware using the following method: Stage the firmware on the logical interconnect Activate the firmware for the interconnects in evennumbered enclosure bays Wait until the firmware update to complete and the interconnects are in the Configured state Activate the firmware for the interconnects in the oddnumbered enclosure bays Upgrading the firmware is based on your assigned role: The Server administrator role can upgrade the firmware on the enclosure OA and servers The Network administrator role can upgrade the firmware on interconnects The Infrastructure administrator role can upgrade the firmware on all devices About managing firmware manually Enclosures and server profiles can be set to Manage manually which means that firmware is managed using external tools, such as HP SUM HPE OneView reports firmware versions from the devices, but does not attempt to update the firmware HP SUM can then manage firmware and drivers through the operating system Virtual Connect firmware is always managed through HPE OneView Using HP SUM for updates HP SUM can update both firmware and drivers for devices managed by HPE OneView, except for Virtual Connect interconnects HP SUM is a free download from http:wwwhpecominfoSmartUpdate Use HP SUM to: Description Install or update drivers After updating firmware using HPE OneView, use HP SUM to update drivers in the environment using the same SPP baseline that was applied using HPE OneView Update firmware After updating firmware using HP SUM, refresh the affected devices in HPE OneView to reflect the new firmware version Select Actions→ Refresh from the Enclosures or Server Hardware screens NOTE: Downgrading devices below the minimum supported firmware version is not recommended while the devices are managed by HPE OneView If you need to downgrade below the minimum supported firmware level, remove the enclosure from HPE OneView before downgrading Install hotfixes Use HP SUM to install hotfixes After performing the update, refresh the affected devices in HPE OneView to reflect the new firmware version Select Actions→ Refresh from the Enclosures or Server Hardware screens ";
f["54"]= " Understanding the security features of HPE OneView CIC int, features, product description, reference, security, roles OneView, online help, help, REST API Understanding the security features of HPE OneView Most security policies and practices used in a traditional environment are applicable in a virtualized environment However, in a virtualized environment, these policies might require modifications and additions To learn more about the security features of the appliance, select topics from the following list: High level overview Securing the appliance Security best practices Best practices for maintaining a secure appliance Nonbrowser clients User access and authentication Authentication for appliance access Controlling access for authorized users Creating a login session Specifying user accounts and roles Protecting credentials Console access Controlling access to the appliance console Certificates Managing certificates from a browser Learn more Algorithms for securing the appliance Ports required for HPE OneView Files you can download from the appliance Understanding the audit log ";
f["55"]= " About unmanaged devices OneView, online help, help, REST API About unmanaged devices An unmanaged device is a device, such as a server, enclosure, KVM keyboard, video and mouse switch, inrack monitorkeyboard, or router, that occupies space in a rack andor consumes power but is not managed by the appliance Unmanaged devices are created automatically to represent devices that are attached to an Intelligent Power Distribution Unit iPDU using Power Discovery Services connections BladeSystem enclosures and ProLiant DL series servers are in the unmanaged or unsupported state These will be represented as unmanaged enclosures and servers and are not unmanageddevices resources When creating an unmanaged device, you provide its name, model description, height in Uslots and maximum power requirements These values are used in power and cooling capacity analysis and enable alerts to be generated identify potential power and cooling issues Because there is no communication to the unmanaged device, the status is disabled unless appliancegenerated alerts identify issues to be addressed For purposes of power configuration, unmanaged devices are assumed to have two power supply connections to support redundant power These are identified as power supplies 1 and 2 If an unmanaged device does not support redundant power, connect only power supply 1, then clear the alert about lack of redundant power to the device For devices that are not discovered through Power Discovery Services connections, you can manually add these devices to the appliance for tracking, inventory, and power management purposes ";
f["56"]= " Storage Volume Templates storagevolumetemplatesall OneView, online help, help, REST API Storage Volume Templates I want to  Create a storage volume template Read a storage volume template Update a storage volume template Delete a storage volume template See more tasks Learn more About volume templates storagevolumetemplates REST APIs storagesystems REST APIs storagepools REST APIs ";
f["57"]= " Read the internal networks in a logical interconnect OneView, online help, help, REST API Read the internal networks in a logical interconnect You can obtain a list of Ethernet networks identified as internal networks in a logical interconnect Prerequisites Minimum required session ID privileges: Network administrator Read the internal VLAN IDs in a logical interconnect using REST APIs Select the logical interconnect URI GET restlogicalinterconnects GET restlogicalinterconnectsidinternalNetworks ";
f["58"]= " Update a network set OneView, online help, help, REST API Update a network set To update a network set, perform a PUT operation to reapply all of the network set attributes View the network set attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes The attributes that you can change include the connection template, networks, network set name, and untagged network Prerequisites Minimum required session ID privileges: Network administrator Updating a network set using REST APIs Select the network set URI GET restnetworksets Get the network set using the URI from step 1 GET restnetworksets id Edit the network set Update the network set PUT restnetworksets id ";
f["59"]= " Data center switch port requirements OneView, online help, help, REST API Data center switch port requirements Although you can configure an uplink set to receive incoming network traffic as untagged by designating a network in that uplink set as Native, traffic egressing the uplink set is always VLAN tagged except for untagged uplink sets The switch ports for data center network switches that connect to the Virtual Connect interconnects must be configured as follows: Spanning tree edge because the Virtual Connect interconnects appear to the switch as access devices instead of switches VLAN trunk ports tagging to support the VLAN IDs included in the uplink set that connects to the switch port For example, if you configure an uplink set, prodUS, that includes the production networks prod 1101 through prod 1104 to use the X2 ports of the interconnects in bay 1 and bay 2 of Enclosure 1, then the data center switch ports that connect to those X2 ports must be configured to support VLAN IDs 1101, 1102, 1103, and 1104 If multiple uplinks in an uplink set connect the same logical interconnect to the same data center switch, you must configure the data center switch ports for LACP Link Aggregation Control Protocol in the same LAG Link Aggregation Group to ensure that all the uplinks in the uplink set are active Set the frequency of control messages: short — every 1 second with a 3–second timeout; or long — every 30 seconds with a 90–second timeout Also consider the type of network traffic and if you are creating an activestandby or activeactive configuration ";
f["60"]= " Index OneView, online help, help, REST API Index Use REST APIs to  Read resource information published to the index Read associated resource information published to the index Read resource tree information published to the index See more tasks Learn more indexresources REST APIs indexassociations REST APIs indextrees REST APIs indexsearchsuggestions REST APIs ";
f["61"]= " About server profile templates OneView, online help, help, REST API About server profile templates Server profile templates provide a mechanism to store configurations for a server profile Typically, you capture bestpractice configurations in a server profile template, and then create and deploy server profiles About creating a server profile template You can create one or more templates to store the configurations for all the settings of a server profile When you create a server profile template, you can specify the server hardware type and the enclosure group You cannot change the server hardware type and the enclosure group after creating the template All profiles generated from the same template will have the same server hardware type and enclosure group The connections are always mapped to ports; that is, a saved server profile template will never have connections with Port=Auto You cannot configure connections with Port=None You cannot add an existing private volume About editing a server profile template Edit a server profile template to change the settings associated with that template You can edit a server profile template any time after it has been created You can also edit a server profile template that has an Error condition to make corrections When you edit a server profile template, the appliance analyzes the changes and updates the template configuration Then, all the server profiles created from the template are evaluated for compliance and a notification is given indicating the number of profiles that will be affected by the change The profiles are marked as noncompliant You can use Update from template option in Server Profiles to accept all the changes from the template NOTE: Server hardware must be powered off to update from template, unless the changes that are made can be made online such as networks and network bandwidth When you edit a server profile template, consider the following: Server profile template names must be unique You cannot switch between virtual and physical identifiers for the following: Serial numberUUID MAC address WWN ";
f["62"]= " Interconnects OneView, online help, help, REST API Interconnects Use REST APIs to  Read interconnect statistics Reapply interconnect configuration See more tasks Learn more About interconnects interconnects REST APIs ";
f["63"]= " About Quality of Service for network traffic OneView, online help, help, REST API About Quality of Service for network traffic Quality of Service QoS is a set of service requirements that the network must meet in order to ensure an adequate service level for data transmission The goal of QoS is a guaranteed delivery system for network traffic The QoS feature enables administrators to configure traffic queues for different priority network traffic, categorize and prioritize ingress traffic, and adjust priority settings on egress traffic Administrators can use these settings to ensure that important traffic receives the highest priority handling while less important traffic is handled at a lower priority Network traffic is categorized, and then classified After being classified, traffic is given priorities and scheduled for transmission For endtoend QoS, all hops along the way must be configured with similar QoS policies of classification and traffic management Traffic prioritization happens because of two things in an endtoend QoS policy At the interconnect, the packets are egressed based on the associated queue bandwidth The more the bandwidth, the higher the priority for the associated traffic at the queue Egress dot1p remarking helps achieve priority at the next hops in the network If the queue egress traffic is remarked to a dot1p value, and that dot1p value is mapped to a queue in the next hops with higher bandwidth, then these packets in the endtoend network are treated with higher priority QoS configuration is defined in the logical interconnect group and applied to the logical interconnect QoS statistics are collected by the interconnects A QoS configuration is applied only on VC Ethernet and VC FlexFabric interconnects on c7000 enclosures Consistency state of a logical interconnect with QoS configurations The UI displays only the currently active QoS configuration that is applied on the interconnects In addition, two inactive QoS configurations are stored for Custom with FCoE and Custom without FCoE configuration types These are the last known QoS configurations for the corresponding configuration types, applied previously on the associated logical interconnect and logical interconnect group While checking for consistency of a logical interconnect to its associated logical interconnect group, the compliance of inactive QoS configurations is also checked inactive QoS configurations are not visible in the UI Even if active QoS configurations are exactly the same between a logical interconnect and associated logical interconnect group, because of inconsistencies in inactive QoS configurations stored internally, a logical interconnect’s consistency status can be shown as Inconsistent Perform an Update from group to bring the logical interconnect group and logical interconnect into a consistent state ";
f["64"]= " About server hardware OneView, online help, help, REST API About server hardware A server hardware resource represents an instance of server being managed or monitored by HPE OneView To define the configuration for a server hardware resource, assign a server profile to it There are different ways servers can be added into HPE OneView Managed HPE OneView manages the server enabling you to apply configurations, assign server profiles, monitor operation status, collect statistics, and alert users to specific conditions Server blades that are in a managed enclosure will automatically be added as managed Managed servers require an HPE OneView Advanced or an HPE OneView Advanced wo iLO license Monitored HPE OneView monitors the hardware for inventory and hardware status only The server can be managed outside of HPE OneView Server blades that are in a monitored enclosure will be added as monitored Monitored servers use a free license called HPE OneView Standard Server hardware management features The appliance supports the following features on server hardware when added as managed Feature Supported server hardware HPE ProLiant BL G7  a HPE ProLiant BL and WS Gen8 and HPE ProLiant BL and WS Gen9 HPE ProLiant DL Gen8 and HPE ProLiant DL Gen9 Power on or power off the server ✓ ✓ ✓ View inventory data ✓ ✓ ✓ Monitor power, cooling, and utilization  b ✓ ✓ ✓ Monitor health and alerts With manual installation and configuration of SNMP Agents NOTE: SNMP Agents are not available on ESXi ✓ ✓ Launch iLO remote console ✓ ✓ ✓ SSO single signon to iLO web interface ✓ ✓ ✓ Automatic firmware upgrade iLO to minimum supported version when added to the appliance ✓ ✓ ✓ Rack visualization and editing ✓ ✓ ✓ Automatic discovery of server hardware type ✓ ✓ ✓ Server profile features BIOS settings   ✓ ✓  c Firmware   ✓ ✓ Connections to networks ✓ ✓   Boot order  d ✓ ✓ ✓  c Local storage  e   ✓ ✓  f SAN storage ✓ ✓    a The appliance might report an unsupported status for some doublewide, doubledense ProLiant G7 server blade models, which means that the appliance cannot manage them To learn more, see About unsupported server hardware  b Not all servers support monitoring power, cooling, and utilization  c HPE ProLiant DL580 Gen8 is not supported  d Due to a limitation in Gen9 BL server ROMs dated 82714 or earlier, it is not possible to set the primary boot device when the boot mode is set to UEFI or UEFI Optimized If Manage boot order is selected, a warning will be displayed in the corresponding profile indicating this condition  e Only supported with the embedded array controller M2 drives are supported in specific configurations See the HPE OneView Support Matrix for details  f Local storage is supported for select models of HPE ProLiant DL Gen9 server hardware See the HPE OneView Support Matrix for a list of models that support local storage About unsupported server hardware The appliance cannot manage unsupported server hardware However, you can place unsupported server hardware in enclosures or racks Adding unsupported server hardware to the appliance enables you to account for the physical space it occupies in an enclosure or rack for planning and inventory purposes The appliance displays basic information about unsupported server hardware that it obtains from the iLO or the OA When the appliance detects unsupported server hardware, it places the hardware in the Unsupported state You can perform a remove action on unsupported server hardware to remove it from the appliance NOTE: Unsupported DL servers can only be added via an intelligent iPDU ";
f["65"]= " Delete a license key OneView, online help, help, REST API Delete a license key Use this procedure to remove a key that was added incorrectly and needs to be removed Prerequisites Required session ID privileges: Infrastructure administrator The license key has no assignments associated with it Deleting a license key using REST APIs Obtain a list of licenses GET restlicenses Determine the license key ID you want to delete For example, if the license key URI is restlicenses100, the license key is 100 Delete the license key DELETE restlicenses ID For example, using the example license key from the previous step: DELETE restlicenses100 ";
f["66"]= " REST API reference OneView, online help, help, REST API REST API reference Click here to view the HPE OneView REST API Reference, which has detailed information about each REST API The reference also includes the parameters, request headers, response headers, and response codes that apply to all REST APIs ";
f["67"]= " PowerShell and Python code sample libraries OneView, online help, help, REST API PowerShell and Python code sample libraries Windows PowerShell and Python libraries are available on Gitcompliant websites to download and use for your REST API scripting The libraries are currently under the MIT Open Source license, and you can modify the source code for your own purposes Each library provides methods for you to submit feedback, issues, and other discussions to Hewlett Packard Enterprise About Git version control: The repository layouts and overall workflows use a very standard simple workflow where the master branch is always the top of tree trunk Hewlett Packard Enterprise tags each release and branches a release only to fix an issue on a specific release To learn more about using Git, see http:gitscmcombook NOTE: If you have questions about REST API scripting or HPE OneView, post your questions to the user community forum at http:wwwhpecominfooneviewcommunity PowerShell library The PowerShell library is hosted on GitHub and is available here: https:githubcomHewlettPackardPOSHHPOneView To subscribe to the site and monitor the project, you need a valid Microsoft or GitHub account Downloading releases or source code does not require authentication For ease of use when the library is updated, a new installer is provided You can use a browser or a GIT Windows client to download the source code and samples To download the Windows client, see http:windowsgithubcom The GitHub site provides an issues tracker to submit issues or feature requests Python library The Python library is hosted on a GitHub website and is available here: https:githubcomHewlettPackardpythonhpOneView To receive development discussions, sign up on the public mailing list at https:groupsgooglecomforum#!forumhponeviewpython ";
f["68"]= " Delete a rack server OneView, online help, help, REST API Delete a rack server When a rack server is deleted, it is no longer under appliance management Prerequisites Minimum required session ID privileges: Server administrator Deleting a rack server using REST APIs Select a rack server URI GET restserverhardware Delete a rack server DELETE restserverhardware id ";
f["69"]= " Create a storage volume template storagevolumetemplatesall OneView, online help, help, REST API Create a storage volume template Prerequisites Minimum required session ID privileges: Infrastructure administrator or Storage administrator Creating a storage volume template using REST APIs Select a storage pool URI GET reststoragepools Create the storage volume template using the URI from step 1 POST reststoragevolumetemplates ";
f["70"]= " Update firmware for specific server hardware OneView, online help, help, REST API Update firmware for specific server hardware The firmware update for server hardware is managed through the server profile After you select the server hardware, the associated server profile is modified to update the firmware Prerequisites Minimum required session ID privileges: Infrastructure administrator Updating firmware for specific server hardware using REST APIs Select server hardware URI with a server profile GET restserverhardware Select the firmware URI you prefer to apply GET restfirmwaredrivers Get the server profile assigned to the server hardware GET restserverprofiles id Replace the firmware URI in the server profile Update the server profile PUT restserverprofiles id ";
f["71"]= " Update enclosure firmware OneView, online help, help, REST API Update enclosure firmware Select a new SPP and update the firmware for all hardware components in an enclosure When setting a new firmware baseline for an enclosure, you have the option to update the: Enclosure only OA firmware Enclosure, logical interconnect, and the server profiles  OA, interconnect, and server firmware including iLO NOTE: If you update the enclosure, logical interconnect, and the server profiles, the previous firmware version stored in the server profile is replaced with the new firmware version You can downgrade or reinstall the firmware using a force upgrade When you set the forceInstallFirmware attribute to false, the firmware bundle that you select is applied regardless of what version is installed on the enclosure, logical interconnects, and server profiles Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator A firmware bundle, also known as Service Pack for ProLiant SPP, uploaded to the appliance Updating enclosure firmware using REST APIs Select the firmware URI to apply GET restfirmwaredrivers Select the enclosure URI GET restenclosures Update the enclosure firmware This step installs the firmware PATCH restlogicalenclosures id NOTE: If you prefer not to update the logical interconnects firmware, then set the updateFirmwareOn attribute to EnclosureOnly ";
f["72"]= " Register for remote support OneView, online help, help, REST API Register for remote support Prerequisites Minimum required session ID privileges: Server administrator Register for remote support using REST APIs PUT restsupportregistration ";
f["73"]= " Assign administrators to fix server hardware issues OneView, online help, help, REST API Assign administrators to fix server hardware issues You can filter alerts specifically for server hardware and additional attributes such as severity After you get the alerts, edit the assigned user value, and then update the alerts Prerequisites Minimum required session ID privileges: Infrastructure administrator Assigning administrators to fix server hardware issues using REST APIs Get server hardware alerts without an owner GET restalertsfilter=physicalResourceType='serverhardware'&filter=severity='UNKNOWN, OK, MAJOR, CRITICAL'&filter=urgency='None, Deferrable, Medium, High, Immediate, Unknown'&filter=assignedToUser='null' Add an administrator to the alert Update the alert PUT restalerts id ";
f["74"]= " Delete an authentication login domain OneView, online help, help, REST API Delete an authentication login domain Prerequisites Minimum required session ID privileges: Infrastructure administrator The authentication directory service to be removed must not be the default directory Either set another authentication login domain as the default or allow local logins See Change the default authentication login domain or Enable or disable local logins Deleting an authentication login domain using REST APIs Select the login domain URI GET restlogindomains Delete the login domain DELETE restlogindomains LoginDomain ";
f["75"]= " Delete a server profile template OneView, online help, help, REST API Delete a server profile template Prerequisites Minimum required session ID privileges: Server administrator Deleting a server profile template using REST APIs Select a server profile template URI GET restserverprofiletemplates Delete the server profile template DELETE restserverprofiletemplates id ";
f["76"]= " Delete a rack OneView, online help, help, REST API Delete a rack When a rack is deleted, it is no longer managed by the appliance Prerequisites Minimum required session ID privileges: Server administrator Deleting a rack using REST APIs Select a rack URI GET restracks Delete the rack DELETE restracks id ";
f["77"]= " Using the Metric Streaming Message Bus MSMB OneView, online help, help, REST API Using the Metric Streaming Message Bus MSMB Connect to the MSMB Set up a queue to connect to the HPE OneView MSMB exchange JSON structure of message received from the MSMB Example to connect and subscribe to MSMB using NET C# Example to connect and subscribe to MSMB using Java Examples to connect and subscribe to MSMB using Python Recreate the AMQP client certificate The Metric Streaming Message Bus MSMB is an interface that uses asynchronous messaging to notify subscribers about the most recent metrics of the managed resources You can configure the interval and the metrics that you want to receive using the REST APIs Connect to the MSMB Prerequisites To use the MSMB, you must do the following tasks: Use REST APIs to create and download an Advanced Message Queuing Protocol AMQP certificate from the appliance Connect to the MSMB using one or both of these methods: Use the “EXTERNAL” authentication mechanism Connect without sending a user name and password Using one of these methods ensures that certificatebased authentication is used Set up a queue with an empty queue name AMQP generates a unique queue name You use this queue name to bind to exchanges and receive messages Create and download the AMQP client certificate Creating and downloading the client certificate, private key, and root CA certificate Create the certificate POST restcertificatesclientrabbitmq Request body: type:RabbitMqClientCertV2,commonName:default Download the certificate and private key GET restcertificatesclientrabbitmqkeypairdefault Download the root CA certificate GET restcertificatesca After you connect the client to the MSMB, you can Set up a queue to connect to the HPE OneView MSMB exchange Connecting the client to the MSMB The MSMB consumer requests a client certificate as part of the registration process The appliance manages the client certificates in a JVK Java KeyStore file The appliance issues a client certificate to the MSMB consumer The MSMB client provides a SSL client certificate to create a connection with the appliance The appliance can revoke the MSMB client certificate to deny access to the MSMB client The client is managed into a CRL Certificate Revocation List file The appliance authenticates the MSMB client using the client certificate Set up a queue to connect to the HPE OneView MSMB exchange The metric streaming messages are published to the HPE OneView MSMB exchange name To subscribe to messages, you must create a queue or connect to an existing queue that receives messages from the MSMB exchange based on a routing key When you create a queue, you define the routing key associated with the queue to receive specific messages Exchange Name: msmb Routing Key: msmb# where: msmb The HPE OneView exchange name for metric streaming Sample queues Subscription Example Receive all MSMB messages for physical servers, enclosures, and power devices The exchange is msmb The routing key is msmb# Configure metric relay using Metric Streaming configuration API JSON structure of message received from the MSMB The following table lists the attributes included in the JSON payload of each message from the MSMB The resource model for the HPE OneView resource is included in the resource attribute To view all resource models, see the HPE OneView REST API Reference Attribute Data type Description resourceUri String The URI for the resource changeType String The statechange type: Created, Updated, or Deleted newState String The new state of the resource eTag String The ETag for the resource when the state change occurred timestamp String The time the message was sent newSubState String If substate messages are required for substate machines associated with a primary state, this is the resourcespecific substate resource MetricData The resource model associatedTask String If a task is not associated with this message, the value is null userInitiatedTask String The value of the userInitiated attribute included in the associatedTask attribute changedAttributes Array A list of toplevel attributes that have changed based on the POST or PUT call that caused the statechange message to be sent data Object Additional information about the resource state change MetricData Attribute Data type Description startTime String The starting time of the metric collection sampleIntervalInSeconds Integer Interval between samples numberOfSamples Integer Number of samples in the list for each metric type resourceType String Identifies the category of resource The supported devices are serverhardware, enclosures, and powerdevices resourceDataList List Metric sample list uri String Canonical URI of the resource category String Identifies the category of resource The supported devices are serverhardware, enclosures, and powerdevices created Timestamp Date and time when the resource was created modified Timestamp Date and time when the resource was last modified eTag String Entity tagversion ID of the resource, the same value that is returned in the ETag header on a GET of the resource type String Uniquely identifies the type of the JSON object Structure of message received from the MSMB  eTag: null, resourceUri: restenclosures09SGH100X6J1, changeType: Updated, newState: null, newSubState: null, associatedTask: null, userInitiatedTask: false, changedAttributes: null, data: null, resource:  type: MetricData, resourceType: enclosures, resourceDataList:   metricSampleList:   valueArray:  null , name: RatedCapacity ,  valueArray:  523 , name: AveragePower ,  valueArray:  573 , name: PeakPower ,  valueArray:  null , name: PowerCap ,  valueArray:  23 , name: AmbientTemperature ,  valueArray:  null , name: DeratedCapacity  , resourceId: 09SGH100X6J1  , numberOfSamples: 1, sampleIntervalInSeconds: 300, startTime: 20140917T08:43:36294Z, eTag: null, modified: null, created: null, category: enclosures, uri: restenclosures09SGH100X6J1 , timestamp: 20140917T08:48:36819Z  Example to connect and subscribe to MSMB using NET C# Prerequisites In addition to completing the prerequisites, you must complete the examplespecific prerequisites before using the NET C# examples To use the Net C# examples, add the following to the Windows certificate store: CA root certificate Client certificate Private key To try the Net C# examples, do the following: Download the root CA certificate GET restcertificatesca Save the contents in the response body into a text file named rootCAcrt You must copy and paste everything from BEGIN CERTIFICATE to END CERTIFICATE, including the dashes, but not including the quotes Import the rootCAcrt file into the Windows certificate store under Trusted Root Certification Authorities Download the client certificate and private key GET restcertificatesclientrabbitmqkeypairdefault Save the contents of the client certificate and private key in the response body into a text file named msmbcrt You must copy and paste everything from BEGIN CERTIFICATE to END CERTIFICATE for the client certificate Next, copy and paste everything from BEGIN RSA PRIVATE KEY to END RSA PRIVATE KEY for the private key You must include the dashes, but do not include the quotes Using Net C# to directly reference client certificate Convert the client certificate and private key to PKCS format for Net opensslexe pkcs12 passout pass:default export in msmbcrt out msmbp12 Example  public void Connect  string exchangeName = msmb; string hostName = OneViewdomain; string queueName = ; string routingKey = msmb#; ConnectionFactory factory = new ConnectionFactory; factoryAuthMechanisms = new RabbitMQClientAuthMechanismFactory  new ExternalMechanismFactory ; factoryHostName = hostname; factoryPort = 5671; factorySslCertPath = @msmbp12; factorySslCertPassphrase = default; factorySslServerName = hostname; factorySslEnabled = true; IConnection connection = factoryCreateConnection; IModel model = connectionCreateModel; queueName = modelQueueDeclarequeueName, false, false, false, null; modelQueueBindqueueName, exchangeName, routingKey, null; using Subscription sub = new Subscriptionmodel, queueName  foreach BasicDeliverEventArgs ev in sub  DoSomethingWithMessageev; subAck;    Using Net C# to import certificate to Microsoft Windows certificate store Import the msmbcrt into your preferred Windows certificate store Example  public void Connect  string exchangeName = msmb; string hostName = OneViewdomain; string queueName = ; string routingKey = msmb#; string userName = rabbitmq_readonly; X509Store store = new X509StoreStoreNameRoot, StoreLocationLocalMachine; storeOpenOpenFlagsReadWrite; X509Certificate cert = storeCertificates FindX509FindTypeFindBySubjectName, userName, false OfType<X509Certificate> First; ConnectionFactory factory = new ConnectionFactory; factoryAuthMechanisms = new RabbitMQClientAuthMechanismFactory  new ExternalMechanismFactory ; factoryHostName = hostname; factoryPort = 5671; factorySslCerts = new X509CertificateCollectionnew X509Certificate  cert ; factorySslServerName = hostname; factorySslEnabled = true; IConnection connection = factoryCreateConnection; IModel model = connectionCreateModel; queueName = modelQueueDeclarequeueName, false, false, false, null; modelQueueBindqueueName, exchangeName, routingKey, null; using Subscription sub = new Subscriptionmodel, queueName  foreach BasicDeliverEventArgs ev in sub  DoSomethingWithMessageev; subAck;    NOTE: Using Net C# to import certificate to Microsoft Windows certificate store references the Trusted Root Certificate Authorities store, located under Local Computer StoreNameRoot = Trusted Root Certificate Authorities StortLocationLocalMachine = Local Computer Example to connect and subscribe to MSMB using Java Download the client certificate and private key GET restcertificatesclientrabbitmqkeypairdefault Save the contents of the client certificate in the response body into a text file named defaultclientcrt You must copy and paste everything from BEGIN CERTIFICATE to END CERTIFICATE, including the dashes, but not including the quotes Save the contents of the private key in the response body into a text file named defaultclientkey You must copy and paste everything from BEGIN RSA PRIVATE KEY to END RSA PRIVATE KEY, including the dashes, but not including the quotes Create a PKCS12 keystore from the private key and the public certificate openssl pkcs12 export name myclientcert in defaultclientcrt inkey defaultclientkey out myclientp12 Convert the PKCS12 keystore into a JKS keystore keytool importkeystore destkeystore c:MyKeyStore srckeystore myclientp12 srcstoretype pkcs12 alias myclient Example to connect and subscribe to MSMB using Java c:MyKeyStore contains client certificate and private key Load it into Java Keystore final char keyPassphrase = MyKeyStorePasswordtoCharArray; final KeyStore ks = KeyStoregetInstancejks; ksloadnew FileInputStreamc:MyKeyStore, keyPassphrase; final KeyManagerFactory kmf = KeyManagerFactorygetInstanceSunX509; kmfinitks, keyPassphrase; c:MyTrustStore contains CA certificate Load it into Java Trust Store final char trustPassphrase = MyTrustStorePasswordtoCharArray; final KeyStore ks = KeyStoregetInstancejks; tksloadnew FileInputStreamc:MyTrustStore, trustPassphrase; final TrustManagerFactory tmf = TrustManagerFactorygetInstanceSunX509; tmfinittks; load SSLContext with keystore and truststore final SSLContext c = SSLContextgetInstanceSSL; cinitkmfgetKeyManagers, tmfgetTrustManagers, new SecureRandom; final ConnectionFactory factory = new ConnectionFactory; factorysetHost1921682144; Set Auth mechanism to EXTERNAL so that commonName of the client certificate is mapped to AMQP user name Hence, No need to set userIdPassword here factorysetSaslConfigDefaultSaslConfigEXTERNAL; factorysetPort5671; factoryuseSslProtocolc; final Connection conn = factorynewConnection; final Channel channel = conncreateChannel; do not specify queue name AMQP will create a queue with random name starting with amqgen eg amqgen32sfQz95QJ85K_lMBhU6HA final DeclareOk queue = channelqueueDeclare, true, false, true, null; Now get the queue name from above call and bind it to required Exchange with required routing key channelqueueBindqueuegetQueue, msmb, msmb#; Now you should be able to receive messages from queue final GetResponse chResponse = channelbasicGetqueuegetQueue, false; if chResponse == null  SystemoutprintlnNo message retrieved;  else  final byte body = chResponsegetBody; SystemoutprintlnReceived:   new Stringbody;  channelclose; connclose; Examples to connect and subscribe to MSMB using Python The Python examples show how to connect and subscribe to the MSMB For more information about Python Pika AMQP client library and AMQP client library, see Introduction to Pika  http:pikareadthedocsorg, http:wwwpythonorg, and AMQP Client Library  https:pypipythonorgpypiamqplib Installation Install the pika and amqp libraries Download and install the setup tools  Python setuppy install at https:pypipythonorgpypisetuptools#downloads Install the pika tools When you install the pika or amqp libraries, run the same python setuppy install command from the downloaded pika or amqp directory Create the certificate POST restcertificatesclientrabbitmq Request body: type:RabbitMqClientCertV2,commonName:default Download the client certificate and private key GET restcertificatesclientrabbitmqkeypairdefault Save the contents of the client certificate in the response body into a text file named clientpem You must copy and paste everything from BEGIN CERTIFICATE to END CERTIFICATE, including the dashes, but not including the quotes You must replace all instances of n with CRLF carriage return  line feed Save the contents of the private key in the response body into a text file named keypem You must copy and paste everything from BEGIN RSA PRIVATE KEY to END RSA PRIVATE KEY, including the dashes, but not including the quotes You must replace all instances of n with CRLF carriage return  line feed Download the root CA certificate GET restcertificatesca Save the contents in the response body into a text file named carootpem You must copy and paste everything from BEGIN CERTIFICATE to END CERTIFICATE, including the dashes, but not including the quotes You must replace all instances of n with CRLF carriage return  line feed Pika Pika example When you invoke the script, you must pass –host: hostname or IP See the following examples: host:19216811 –host:myapplianceexamplecom IMPORTANT: If the connection fails on the first attempt to invoke this script after an appliance reboot, try invoking the script again import pika, ssl from optparse import OptionParser from pikacredentials import ExternalCredentials import json import logging loggingbasicConfig ############################################### # Callback function that handles messages def callbackch, method, properties, body: msg = jsonloadsbody timestamp = msg'timestamp' resourceUri = msg'resourceUri' resource = msg'resource' changeType = msg'changeType' print print %s: Message received: %timestamp print Routing Key: %s %methodrouting_key print Change Type: %s %changeType print Resource URI: %s %resourceUri print Resource: %s %resource # Pem Files needed, be sure to replace the n returned from the APIs with CRLF # carootpem  the CA Root certificate  GET restcertificatesca # clientpem, first POST restcertificatesclientrabbitmq Request body: type:RabbitMqClientCert,commonName:default # GET restcertificatesclientrabbitmqkeypairdefault # clientpem is the key with BEGIN CERTIFICATE # keypem is the key with BEGIN RSA PRIVATE KEY # Setup our ssl options ssl_options = ca_certs: carootpem, certfile: clientpem, keyfile: keypem, cert_reqs: sslCERT_REQUIRED, server_side: False parser = OptionParser parseradd_option'host', dest='host', help='Pika server to connect to default: %default', default='localhost',  options, args = parserparse_args # Connect to RabbitMQ host = optionshost print Connecting to %s:5671, to change use host hostName  %host connection = pikaBlockingConnection pikaConnectionParameters host, 5671, credentials=ExternalCredentials, ssl=True, ssl_options=ssl_options # Create and bind to queue EXCHANGE_NAME = msmb ROUTING_KEY = msmb# channel = connectionchannel result = channelqueue_declare queue_name = resultmethodqueue channelqueue_bindexchange=EXCHANGE_NAME, queue=queue_name, routing_key=ROUTING_KEY channelbasic_consumecallback, queue=queue_name, no_ack=True # Start listening for messages channelstart_consuming AMQP AMQP example When you invoke the script, you must pass –host: hostname or IP See the following examples: host:19216811 –host:myapplianceexamplecom IMPORTANT: If the connection fails on the first attempt to invoke this script after an appliance reboot, try invoking the script again #!usrbinenv python from optparse import OptionParser from functools import partial import amqplibclient_0_8 as amqp def callbackchannel, msg: for key, val in msgpropertiesitems: print '%s: %s' % key, strval for key, val in msgdelivery_infoitems: print '> %s: %s' % key, strval print '' print msgbody print '' print msgdelivery_tag channelbasic_ackmsgdelivery_tag # # Cancel this callback # if msgbody == 'quit': channelbasic_cancelmsgconsumer_tag def main: parser = OptionParser parseradd_option'host', dest='host', help='AMQP server to connect to default: %default', default='localhost',  options, args = parserparse_args host = optionshost:5671 # Pem Files needed, be sure to replace the n returned from the APIs with CRLF # carootpem  the CA Root certificate  GET restcertificatesca # clientpem, first POST restcertificatesclientrabbitmq Request body: type:RabbitMqClientCert,commonName:default # GET restcertificatesclientrabbitmqkeypairdefault # clientpem is the key with BEGIN CERTIFICATE # keypem is the key with BEGIN RSA PRIVATE KEY ssl_options = ca_certs: carootpem, certfile: clientpem, keyfile: keypem, # cert_reqs: CERT_REQUIRED, server_side: False print 'Connecting to host %s, to change use host hostName ' %host conn = amqpConnectionhost, login_method='EXTERNAL', ssl=ssl_options print 'Successfully connected, creating and binding to queue' ch = connchannel qname, _, _ = chqueue_declare chqueue_bindqname, 'msmb', 'msmb#' chbasic_consumeqname, callback=partialcallback, ch print 'Successfully bound to queue, waiting for messages' #pyamqp: # # Loop as long as the channel has callbacks registered # while chcallbacks: chwait chclose connclose if __name__ == '__main__': main Recreate the AMQP client certificate If you change the appliance name, you must recreate the AMQP client certificate NOTE: If the certificates are already created, you can skip this step Prerequisites Minimum required session ID privileges: Infrastructure administrator Recreating and downloading the client certificate, private key, and root CA certificate Revoke the certificate DELETE restcertificatescarabbitmq_readonly Request body is not required NOTE: When you revoke the default client certificate, the appliance regenerates the CA certificate, AMQP server certificate, and the default client certificate Download the certificate and private key GET restcertificatesclientrabbitmqkeypairdefault Download the root CA certificate GET restcertificatesca ";
f["78"]= " Recover from an unexpected appliance shutdown OneView, online help, help, REST API Recover from an unexpected appliance shutdown If the appliance unexpectedly shuts down, the appliance will attempt to automatically recover To check whether all tasks and issues were resolved automatically, you can view alerts and tasks to see the current status of appliance resources Manually restart any tasks that have a status of interrupted or error For example, if the appliance unexpectedly shuts down during a firmware update, upon appliance restart, the task status is error Prerequisites Minimum required session ID privileges: any user with read privileges Reading critical alerts using REST APIs GET restalertsfilter=alertState='Critical' Reading interrupted tasks and recommended actions using REST APIs GET resttasksfilter=taskState='Interrupted' To view the recommended actions, within the taskError attribute, view the recommendedActions attribute If the recommended action is to refresh the resource, perform a GET on the associatedResourceURI, change refreshState to equal RefreshPending, and then perform a PUT using all the attributes ";
f["79"]= " Attach an existing volume to a server profile OneView, online help, help, REST API Attach an existing volume to a server profile Prerequisites Minimum required session ID privileges: Server administrator Attaching an existing volume to a server profile using REST APIs Obtain the hardware information: Get a list of available targets GET restserverprofilesavailabletargets For an assigned profile, note the fields serverHardwareUri, serverHardwareTypeUri, and enclosureGroupUri for the hardware target of interest For an unassigned profile, note the serverHardwareTypeUri and enclosureGroupUri for the hardware target of interest For an empty bay, note the fields serverHardwareTypeUri, enclosureGroupUri, enclosureUri, and enclosureBay Obtain the network information to create connections: Get a list of network connections GET restserverprofilesavailablenetworksserverHardwareTypeUri= uri&enclosureGroupUri= uri Insert serverHardwareTypeUri and enclosureGroupUri from step 1 Note the fields uri and limitedToPorts If manually selecting the storage targets, note which networks are fabric attach, as indicated via the accessType field Get available ports GET restserverprofilesprofileportsserverHardwareTypeUri= uri&enclosureGroupUri= uri Insert serverHardwareTypeUri and enclosureGroupUri from step 1 Note the fields portId, maximumLinkMbps, supportedFcGbps, and capabilities Obtain the SAN storage information: Determine the desired host OS enumeration GET reststoragesystemshosttypes Pick an existing available storage volume GET restserverprofilesavailablestoragesystemsserverHardwareTypeUri= uri&enclosureGroupUri= uri Note the fields connections, storageSystemUri, and volumeUri for the desired volume to attach to the profile If manually selecting the storage targets, obtain them GET storage system urimanagedPorts Note the fields portWwn, expectedNetworkUri, and actualNetworkUri Match the expectedNetworkUri with the uri field obtained in step 2a Create the server profile with the information from the previous steps POST restserverprofiles ";
f["80"]= " Delete a scope CONTACT CI DOC OWNERS before modifying this content OneView, online help, help, REST API Delete a scope Use this procedure to delete a scope, including its resource assignments The resources are not deleted Deleting a scope using REST APIs Obtian the scope ID: GET restscopes Delete the scope: DELETE restscopesid ";
f["81"]= " Remote Support OneView, online help, help, REST API Remote Support Use REST APIs to  Register for remote support Update remote support settings Add channel partners Delete a channel partner Add a contact Delete a contact Collect remote support data Register with the portal Delete portal registration See more tasks Learn more remote support REST APIs ";
f["82"]= " Read a rack OneView, online help, help, REST API Read a rack You can view the attributes associated with a specific rack Prerequisites Minimum required session ID privileges: Server administrator Reading a rack using REST APIs Select a rack URI GET restracks Get the rack GET restracks id ";
f["83"]= " Read active ID pools and their properties OneView, online help, help, REST API Read active ID pools and their properties Prerequisites Minimum required session ID privileges: Infrastructure administrator, Network administrator, or Server administrator Reading Vmac ID pools and their properties using REST APIs GET restidpoolsvmac Reading Vsn ID pools and their properties using REST APIs GET restidpoolsvsn Reading Vwwn ID pools and their properties using REST APIs GET restidpoolsvwwn ";
f["84"]= " What can I do with HPE OneView REST APIs OneView, online help, help, REST API What can I do with HPE OneView REST APIs This page provides navigation to actions and tasks you might want to perform using REST APIs Get started with REST Learning about REST APIs HPE OneView REST API Reference Get started with configuring your environment Quick Start: Initial configuration using REST APIs StateChange Message Bus Subscribe to messages in the StateChange Message Bus Metric Streaming Message Bus Subscribe to messages in the Metric Streaming Message Bus Activity Activity Activity notification Servers Server Profiles Addresses and Identifiers Enclosure Groups Enclosures Server Hardware Server Hardware Types Reports Networks and connectivity Logical Interconnect Groups Logical Interconnects Networks Interconnects Switches Logical Switches Logical Switch Groups Quick Start: Add an activeactive network configuration Quick Start: Migrate from an activestandby to an activeactive network configuration Security Users and Groups Storage SAN Managers Storage Pools Storage Systems Storage Volumes Storage Volume Templates Facilities Data services Data Centers Racks Power Delivery Devices Utilization Settings Licensing Firmware Appliance Remote Support Enclosures, enclosure groups, and logical enclosures Add an enclosure to manage its content Migrate a c7000 VCM enclosure using REST API Add a c7000 enclosure to monitor the hardware Create an enclosure group Update an enclosure group Delete an enclosure group Search Index Labels Best practices Monitoring health Learn more Where to find HPE OneView documentation ";
f["85"]= " Read the status of a task OneView, online help, help, REST API Read the status of a task When you perform an asynchronous REST API operation, a TaskResource URI is returned in the Location header You can use this URI to read the current status of the task Prerequisites Minimum required session ID privileges: Infrastructure administrator Reading the status of a task using REST APIs GET resttasks id ";
f["86"]= " Copy an unassigned server profile OneView, online help, help, REST API Copy an unassigned server profile Prerequisites Minimum required session ID privileges: Server administrator Copying an unassigned server profile using REST APIs Get all server profiles GET restserverprofiles Search for serverHardwareUri=null in the list of returned server profiles to find unassigned server profiles Select an unassigned server profile Get the unassigned server profile GET restserverprofiles id Delete the server profile uri value Create a new server profile POST restserverprofiles ";
f["87"]= " About Fibre Channel over Ethernet FCoE networks OneView, online help, help, REST API About Fibre Channel over Ethernet FCoE networks FCoE networks are a combination of both Ethernet and Fibre Channel technology and are used when storage traffic is carried over a dedicated Ethernet VLAN Like a tagged Ethernet network, FCoE networks use VLANs to allow multiple networks to use the same physical connection See the HPE OneView Support Matrix for the number of FCoE networks that can be assigned to a single interconnect and for a single logical interconnect or logical interconnect group Like FC traffic, FCoE traffic does not cross stacking links FCoE networks lower cost through: Cable consolidation Reduction in the number of SAN fabric switches Adapter and interconnect consolidation FCoE network requirements Assigned VLAN ID, from 2 to 4094 Ethernet uplink set Uplink ports are FCoEcapable and come from a single FCoEcapable interconnect module FCoE support depends upon the Virtual Connect firmware version of the interconnect module, as shown in the following table Virtual Connect firmware version Supported functionality Supported interconnects 410 A single FCoE network in an uplink set Virtual Connect FlexFabric 10Gb24Port Module Virtual Connect Flex1010D Module for HPE BladeSystem Cclass 420 or higher Up to 32 FCoE networks in an uplink set Up to 32 FCoE networks per interconnect cumulative across all uplink sets for the interconnect FIP snooping Virtual Connect FlexFabric 10Gb24Port Module Virtual Connect Flex1010D Module for HPE BladeSystem Cclass Virtual Connect FlexFabric–2040 F8 Module, ports X1–X8 430 or higher Up to 32 FCoE networks in an uplink set Up to 32 FCoE networks per interconnect cumulative across all uplink sets for the interconnect FIP snooping Virtual Connect FlexFabric 10Gb24Port Module Virtual Connect Flex1010D Module for HPE BladeSystem Cclass Virtual Connect FlexFabric–2040 F8 Module, ports X1–X8 and QSFP ports ";
f["88"]= " Refresh a logical switch OneView, online help, help, REST API Refresh a logical switch The refresh action reclaims the topofrack switches in a logical switch This can be useful when the switch firmware is updated If a switch in a logical switch is in an unmanaged state due to a firmware version mismatch, it can be brought into the Monitored state by refreshing the logical switch Prerequisites Minimum required session ID privileges: Network administrator Refreshing a logical switch using REST APIs Select a logical switch URI GET restlogicalswitches Refresh the logical switch using the URI from step 1 PUT restlogicalswitches idrefresh ";
f["89"]= " Update a server profile OneView, online help, help, REST API Update a server profile To update a server profile, perform a PUT operation to reapply all of the server profile attributes View the server profile attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes Prerequisites Minimum required session ID privileges: Server administrator Added enclosure that includes a server blade without a server profile Editing some server profile settings requires the server hardware to be powered off, while for others, the server hardware can remain powered on You can edit the following settings with server hardware powered on: Profile name Profile description Requested bandwidth of an existing connection Changes between a network and network set of an existing connection NOTE: You cannot change an existing connection between Ethernet network or network set and Fibre Channel networks A Fibre Channel network can only be changed to another Fibre Channel network on the same interconnect Updating a server profile using REST APIs Select the server profile URI GET restserverprofiles Get the server profile using the URI from step 1 PUT restserverprofiles id Edit the server profile Update the server profile PUT restserverprofiles id IMPORTANT: When you move a server profile to a different enclosure, if the profile is configured to boot from a Direct attach storage device, you must manually update the boot connection of the profile to specify the WWPN that is used for the storage device that is directly attached to the destination enclosure Each enclosure connects to a different port of the Direct attach storage device, so the WWPN for that storage device is different for each enclosure If you do not specify the correct WWPN and LUN for the device, the server does not successfully boot from that boot target ";
f["90"]= " Quick Start: Add an activeactive network configuration OneView, online help, help, REST API Quick Start: Add an activeactive network configuration This quick start describes the process to add an activeactive configuration for an enclosure Prerequisites Minimum required session ID privileges: Infrastructure administrator or Network administrator to add the network Minimum required session ID privileges: Infrastructure administrator or Server administrator to change the server profile configurations Two or more fully supported Virtual Connect interconnect modules as listed in the HPE OneView Support Matrix The enclosures and server blades are already added to the appliance Follow recommended naming conventions described in Requirements for an activeactive configuration Adding an activeactive network configuration for single or multiple logical interconnect groups For each Virtual Connect interconnect module you want to set up as an activeactive configuration in the appliance, make configuration changes to the following resources: Resource Task Description Networks Add networks For an enclosure group with a single logical interconnect group: Add a pair of Ethernet networks for each VLAN you want to connect: one network for the first interconnect module and one network for the second interconnect module using the same VLAN ID For example, create Dev101_A and Dev101_B for VLAN ID 101 For a multiple logical interconnect group configuration: Add an Ethernet network to be used in both logical interconnect groups For the name attributes, assign names to the networks following Requirements for an activeactive configuration For the vlanId attribute, enter the same ID for the pair of networks Set the smartLink attribute to true Logical Interconnect Groups and Logical Interconnects Create uplink sets For an enclosure group with a single logical interconnect group: Create a pair of uplink sets to associate the networks with the uplink ports on the interconnect module Assign one set of networks to the uplink set that has ports on the first interconnect module Assign the other networks to the uplink set that has ports on the second interconnect module For example, uplink port X5 is defined in both sets: UplinkSet_A for bay 1 and UplinkSet_B for bay 2 Dev101_A is assigned to UplinkSet_A, and Dev101_B is assigned to UplinkSet_B For a multiple logical interconnect group configuration: Create an uplink set on the first logical interconnect group and an uplink set on the second logical interconnect group with the same networks You can either add the networks to existing uplink sets or create new uplink sets for the networks Uplinks in each uplink set must be restricted to a single interconnect Duplicate VLAN IDs are not allowed in the same uplink set For more information, see About logical interconnects and About logical interconnect groups Network Sets Optional Add one or more pairs of network sets Each set should include only the networks that will be used on the same server profile connection For example, create network set DevSet_A for your development Dev_A networks, and create DevSet_B for your development Dev_B networks Adding a network to a network set does not require that you take resources offline You do not need to update server profiles that have connections to the network set Duplicate VLAN IDs are not allowed in a network set Each network set should have multiple networks For more information, see About network sets Server Profiles and Server Hardware Power off the server before you edit the server profile Edit the server profile to add two connections Assign one port for the networks or network sets on one module, and assign a different port for the networks or network sets on the other module Make sure the networks associated with the uplink ports in the uplink set match the networks assigned to the profile connections in the downlink ports For example, Connection1 is LOM1:1a for DevSet_A, and Connection2 is LOM1:1b for DevSet_B Power on the server When adding a connection to the server profile, select the physical port connected to the module with the uplink set containing the networks configured for that connection Do not select Auto For more information, see About server profiles ";
f["91"]= " Logical Interconnects OneView, online help, help, REST API Logical Interconnects Use REST APIs to  Create an uplink set Create and download a logical interconnect MAC address table file Enable or disable LLDP tagging using REST APIs Enable or disable enhanced TLV support using REST APIs Find noncompliant logical interconnects Read a logical interconnect MAC address table Read the internal networks in a logical interconnect Reapply a logical interconnect group to bring a logical interconnect into compliance Set up logical interconnect port monitoring Update logical interconnect firmware Update internal networks on a logical interconnect Update logical interconnect settings Update logical interconnect SNMP settings Update a logical interconnect Link Aggregation Control Protocol LACP timer Configure Quality of Service settings for a logical interconnect See more tasks Learn more About logical interconnects About firmware associated with a logical interconnect About activeactive configurations About SNMP settings About Quality of Service for network traffic logicalinterconnects REST APIs ";
f["92"]= " Understanding the audit log CIC int, features, product description, reference, security, roles OneView, online help, help, REST API Understanding the audit log The audit log contains a record of actions performed on the appliance, which you can use for individual accountability You must have Infrastructure administrator privileges to download the audit log To download the audit log, see Download audit logs Monitor the audit logs because they are rolled over periodically to prevent them from getting too large Download the audit logs periodically to maintain a longterm audit history Each user has a unique logging ID per session, enabling you to follow a user’s trail in the audit log Some actions are performed by the appliance and might not have a logging ID A breakdown of an audit entry follows: Token Description Datetime The date and time of the event Internal component ID The unique identifier of an internal component Reserved The organization ID Reserved for internal use User domain The login domain name of the user User nameID The user name Session ID The user session ID associated with the message Task ID The URI of the task resource associated with the message Client hostIP The client browser IP address identifies the client machine that initiated the request Result The result of the action, which can be one of the following values: SUCCESS FAILURE SOME_FAILURES CANCELED KILLED Action A description of the action, which can be one of the following values: ADD MODIFY DELETE ACCESS RUN LIST ENABLE DISABLE SAVE SETUP UNSETUP DEPLOY START DONE KILLED CANCELED LOGIN LOGOUT DOWNLOAD_START Severity A description of the severity of the event, which can be one of the following values, listed in descending order of importance: INFO NOTICE WARNING ERROR ALERT CRITICAL Resource category For REST API category information, see the HPE OneView REST API Reference Resource URIname The resource URIname associated with the task Message The output message that appears in the audit log Maintenance console entries   The audit log includes entries for these Maintenance console events: Entries in which no login was required Successful logins Unsuccessful logins Unsuccessful challengeresponse authorization attempts Attempted appliance restarts Attempted appliance shutdowns Attempts to reset the administrator password Service console launches and exits ";
f["93"]= " Power Delivery Devices OneView, online help, help, REST API Power Delivery Devices Use REST APIs to  Add an iPDU Resolve connectivity issues between an iPDU and the appliance Change the locator light state of a power delivery device to on or off Control power to a power delivery device outlet Add a noniPDU power delivery device Read a power device Read the power utilization of a power device Update a power delivery device Update enclosure capacity settings Update server hardware capacity settings Delete a power delivery device See more tasks Learn more About power delivery devices powerdevices REST APIs ";
f["94"]= " REST API version and backward compatibility OneView, online help, help, REST API REST API version and backward compatibility When you perform a REST API operation, an XAPIVersion header is required This version header corresponds to the REST API version of software currently running on the appliance To determine the current REST API version on a given appliance, perform GET restversion This GET operation does not require an XAPIVersion header If multiple appliances are running in your environment, you need to determine the REST API version required by each appliance : If an XAPIVersion header is not included in the request, the APIs default to version 1 Since most APIs in HPE OneView have a minimum of 3 or greater, invoking an API without including the XAPIVersion header will likely result in an HTTP 404 error, because that version of the API will not be found The requests documented in the HPE OneView 20 REST API scripting help correspond to a versionNumber of 200 Requests specifying API version 200 always provide the behavior documented here Future API changes will introduce higher version numbers Supported REST API versions This release of HPE OneView supports the new REST API version 200 in addition to supporting the REST API version 3 minimum that was supported in previous releases of HPE OneView The HPE OneView REST API documentation for older REST API versions is available online at wwwhpecominfooneviewdocs, and the documentation for the current version of supported REST APIs is included with the online help for this release as well as online Backward compatibility The following list explains how to preserve your existing scripts when upgrading to a new version of HPE OneView, take advantage of new functionality, and find the current and previous versions of the HPE OneView REST API documentation Prevent scripts from breaking To prevent your existing scripts from breaking that were written for a specific API version, use the same XAPIVersion value for that specific REST API This ensures that the same set of data is sent and returned in the response body during PUT and POST operations NOTE: The set of possible enumerated values that may be returned in a given resource attribute may be extended from release to release independent of the API version Clients should ignore any values that they do not expect To maintain backward compatibility, the set of enumerated values will not be reduced and the meaning of these values will not change for a given API version NOTE: The Index or SCMB always returns the latest version of resource data, independent of what is sent in the XAPIVersion header on the request this header controls the Index DTO model, but not the data contained within To obtain a specific version of a resource’s data, perform a GET on the resource’s URI with the desired XAPIVersion header Use new functionality To take advantage of new functionality, you must move to the new XAPIVersion value If the XAPIVersion value is set globally in your scripts, moving to a new XAPIVersion will likely impact multiple REST APIs To view a list of REST APIs that have changed, see the HPE OneView Release Notes If you do not need to use the new functionality, you can use a previous XAPIVersion and avoid impacting your existing scripts Hewlett Packard Enterprise recommends that you move to the new XAPIVersion, because backward compatibility is not guaranteed from release to release, and older functionality will be deprecated The current version of the REST APIs are documented in the HPE OneView REST API Reference that is included on the appliance To view previous versions of the REST API reference, go to wwwhpecominfooneviewdocs ";
f["95"]= " Enclosure Groups OneView, online help, help, REST API Enclosure Groups Use REST APIs to  Create an enclosure group Update an enclosure group Delete an enclosure group See more tasks Learn more About enclosure groups enclosure groups REST APIs ";
f["96"]= " Read utilization for a specific power delivery device OneView, online help, help, REST API Read utilization for a specific power delivery device You can view historical data for power delivery device utilization, such as average power and average peak power, for the last 24 hours Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator Reading utilization for a specific power delivery device using REST APIs Select a power delivery device URI GET restpowerdevices Get utilization for specific power delivery device GET restpowerdevices idutilization ";
f["97"]= " Edit an email recipient and filter pair OneView, online help, help, REST API Edit an email recipient and filter pair Use the procedure below: To add, change, or remove an email address for an existing filter query To change an existing filter query Prerequisites Required session ID privileges: Infrastructure administrator Editing an email recipient and filter pair using REST APIs Perform a GET for the appliance email notifications: GET restappliancenotificationsemailconfig Edit the alert filter query, email address, or both, as needed Using the resource URI from step 1, reconfigure the appliance for email notifications: POST restappliancenotificationsemailconfig ";
f["98"]= " Enable or disable email notification of alerts OneView, online help, help, REST API Enable or disable email notification of alerts Sometimes it might be useful to disable email notification of alerts for a filter and recipient pair For example, there might be an error in the filter query that causes continuous email messages You can disable the modified filter and recipient pair until you find and correct the error, and then enable email notification for the filter and recipient pair You can also enable or disable the entire email notification feature, which affects all the filter and recipient pairs Prerequisites Required session ID privileges: Infrastructure administrator Enabling or disabling all email notification of alerts using REST APIs Perform a GET for the appliance email notifications: GET restappliancenotificationsemailconfig Set the alertEmailDisabled field to enable or disable all email notification Using the resource URI from step 1, reconfigure the appliance for email notifications: POST restappliancenotificationsemailconfig Enabling or disabling an individual filter and recipient pair using REST APIs Perform a GET for the appliance email notifications: GET restappliancenotificationsemailconfig Set the disabled field for the filter and recipient pair that you want to enable or disable Using the resource URI from step 1, reconfigure the appliance for email notifications: POST restappliancenotificationsemailconfig ";
f["99"]= " Edit an enclosure OneView, online help, help, REST API Edit an enclosure You can edit the name of the enclosure When the name of the enclosure changes, the server hardware and interconnects are assigned the new name However, the name of the logical interconnect is not changed The logical interconnect name changes if the logical enclosure name changes Prerequisites Minimum required session ID privileges: Infrastructure Administrator Editing an enclosure using REST APIs Select an enclosure URI GET restenclosures Edit the enclosure using the URI from step 1 PATCH restenclosures id op: replace, path: name, value:  new enclosure name ";
f["100"]= " Enable or disable enhanced TLV support using REST APIs OneView, online help, help, REST API Enable or disable enhanced TLV support using REST APIs Enabling or disabling the enableRichTLV parameter determines the information that is advertised in the Chassis ID TLV of LLDP frames sent out by an interconnect Modifying this parameter impacts any service that queries this information for network topology information, for example attempting to derive network topology based on the contents of LLDPDUs Prerequisites Minimum required session ID privileges: Infrastructure administrator Virtual Connect 430 or higher installed on the interconnect Enabling enhanced TLV support using REST APIs Select a logical interconnect URI GET restlogicalinterconnects Get the logical interconnect using the URI from step 1 GET restlogicalinterconnects id Set enableRichTLV to true Update the logical interconnect PUT restlogicalinterconnects id Disabling enhanced TLV support using REST APIs Select a logical interconnect URI GET restlogicalinterconnects Get the logical interconnect using the URI from step 1 GET restlogicalinterconnects id Set enableRichTLV to false Update the logical interconnect PUT restlogicalinterconnects id More information About enhanced typelengthvalue TLV structure ";
f["101"]= " About data services OneView, online help, help, REST API About data services Using data services, you can make data available for offline analysis and troubleshooting For information on supported data types, see the following sections on metric streaming and log forwarding About metric streaming The HPE OneView REST APIs allow you to configure the relay of enclosure, serverhardware, and powerdevices performance metrics over MSMB Following is the list of metrics supported Enclosures: Rated Capacity: The limit of the enclosure’s peak power consumption, in watts Derated Capacity: The limit of the enclosure’s average power consumption, in watts Ambient Temperature: The temperature of the enclosure over the time interval in Celsius or Fahrenheit Average Power: The average power consumption of the device over the time interval, in watts Powercap: The power cap set for the enclosure, in watts Peak Power: The peak power consumption of the enclosure over the time interval, in watts Powerdevices: Average Power: The average power consumption of the device over the time interval, in watts Peak Power: The peak power consumption of the device over the time period, in watts Serverhardware: CPU Utilization: The percentage of CPU utilized by the device over the time interval CPU Average Frequency: The speed of the device CPU over the time interval, in GHz Ambient Temperature: The temperature of the enclosure over the time interval in Celsius or Fahrenheit Average Power: The average power consumption of the device over the time interval, in watts Powercap: The userdefined power cap set for serverhardware Peak Power: The peak power consumption of the device over the time period, in watts About log forwarding to a remote syslog server REST APIs can be used to configure the remote syslog destination Once configured, the logs are streamed directly from the device using rsyslog ";
f["102"]= " Delete a power delivery device OneView, online help, help, REST API Delete a power delivery device When a power delivery device is deleted, it is no longer managed by the appliance Prerequisites Minimum required session ID privileges: Server administrator Deleting a power delivery device using REST APIs Select a power delivery device URI GET restpowerdevices Delete the power delivery device DELETE restpowerdevices id ";
f["103"]= " About power delivery devices OneView, online help, help, REST API About power delivery devices Power delivery devices provide power to IT hardware A typical power topology in a data center includes power delivery devices such as power feeds, breaker panels, branch circuits, and power distribution units PDUs, as well as the load segments, outlet bars, and outlet components of these devices Adding your power delivery devices to the appliance enables power management using thermal limits, rated capacity, and derated capacity The following classes of devices can be managed by the appliance: Intelligent Power Distribution Units iPDUs, which the appliance can automatically discover and control Other power delivery devices that the appliance cannot discover By manually adding these devices to the appliance, they become available for tracking, inventory, and power management purposes Regardless of how power delivery devices are added to the appliance, the appliance automatically generates the same types of analysis capacity, redundancy, and configuration For iPDUs, the appliance gathers statistical data and reports errors Connectivity and synchronization with the appliance The appliance monitors the connectivity status of iPDUs If the appliance loses connectivity with an iPDU, an alert displays until connectivity is restored The appliance will try to resolve connectivity issues and clear the alert automatically, but if it cannot, you must resolve the issue and manually refresh the iPDU to bring it in synchronization with the appliance The appliance also monitors iPDU to remain synchronized with changes to hardware and power connections However, some changes to devices made outside of the control of the appliance from iLO or the OA, for example may cause them to become out of synchronization with the appliance You may have to manually refresh devices that lose synchronization with the appliance NOTE: Hewlett Packard Enterprise recommends that you do not use iLO or the OA to make changes to a device Making changes to a device from its iLO or OA could cause it to lose synchronization with the appliance See Resolve connectivity issues between an iPDU and the appliance to learn more ";
f["104"]= " Add a SAN manager OneView, online help, help, REST API Add a SAN manager You can choose from a static list of SAN providers that is included on the appliance When you choose a provider, you populate the connectionInfo attributes and add the SAN manager NOTE: For the HPE 5900: In a cascaded switch environment, a SAN Manager can perform operations on all VSANs configured on that switch including VSANs that span across multiple switches If a VSAN is configured on only one switch, you need to add the switch as a SAN manager, even if the switch has already been discovered through a spanning VSAN For VSANs that are discovered on multiple SAN managers, you must select one SAN manager to associate to a network Once you associate a SAN manager to a network, all other SAN managers that the VSAN was discovered on will be removed from the list The appliance can only manage the VSAN from this associated SAN manager from now on Zone aliases created for a particular VSAN on a SAN manager are not visible to other SAN managers that manage the VSAN Prerequisites Minimum required session ID privileges: Infrastructure administrator or Storage administrator The SAN manager is supported by the appliance and is configured properly See the HPE OneView Support Matrix for more information about supported SAN managers The SAN manager’s IP address The SAN manager’s user name and password : To add an HPE SAN manager, it must be configured so that there is an SNMPv3 user created See also: the Quick Start: Configuring an HPE 5900 for management by HPE OneView chapter in the HPE OneView User Guide for detailed instructions on configuring an HPE 5900 Adding a SAN manager using REST APIs Select a SAN provider GET restfcsansproviders Add the SAN manager using the connectionInfo attributes returned in step 1 Add the credentials, IP address, and any additional values specific to the SAN provider POST restfcsansprovidersiddevicemanagers Next, you can add SANs When you create a network and select a SAN, the SAN is automatically associated to the SAN manager ";
f["105"]= " Update an enclosure group OneView, online help, help, REST API Update an enclosure group To update an enclosure group, perform a PUT operation to reapply all of the enclosure group attributes View the enclosure group attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator Updating an enclosure group using REST APIs Select the enclosure group URI GET restenclosuregroups Get the enclosure group using the URI from step 1 GET restenclosuregroups id Edit the enclosure group Update the enclosure group PUT restenclosuregroups id ";
f["106"]= " Collect remote support data OneView, online help, help, REST API Collect remote support data Minimum required session ID privileges: Server administrator Collect remote support data using REST APIs Run a collection on the given device immediately POST restsupportdatacollections Download the collection for a given collection ID GET restsupportdatacollectionsdownload ";
f["107"]= " Delete a firmware bundle from the firmware repository OneView, online help, help, REST API Delete a firmware bundle from the firmware repository Hewlett Packard Enterprise recommends that you unassign the SPP from all devices that the SPP is assigned to before removing the SPP Prerequisites Minimum required session ID privileges: Infrastructure administrator, Server administrator, or Network administrator Deleting a firmware bundle from the firmware repository using REST APIs Select a firmware bundle URI GET restfirmwaredrivers Delete the firmware bundle using the URI from step 1 DELETE restfirmwaredrivers id ";
f["108"]= " Websites OneView, online help, help, REST API Websites Website Link Hewlett Packard Enterprise Information Library wwwhpecominfoenterprisedocs Hewlett Packard Enterprise Support Center wwwhpecomsupporthpesc Contact Hewlett Packard Enterprise Worldwide wwwhpecomassistance OneView Docs wwwhpecominfooneviewdocs Subscription ServiceSupport Alerts wwwhpecomsupporteupdates Software Depot wwwhpecomsupportsoftwaredepot Customer Self Repair wwwhpecomsupportselfrepair Insight Remote Support wwwhpecominfoinsightremotesupportdocs Single Point of Connectivity Knowledge SPOCK Storage compatibility matrix wwwhpecomstoragespock HP Virtual Connect user guides HP Virtual Connect command line references http:wwwhpcomgovirtualconnect HP 3PAR StoreServ Storage http:wwwhpcomgostorage HPE Integrated LightsOut http:wwwhpecominfoilo HPE BladeSystem enclosures http:wwwhpcomgobladesystem HPE ProLiant server hardware websites General information: http:wwwhpcomgoproliant BL series server blades: http:wwwhpecominfoblades DL series rack mount servers: http:www8hpcomusenproductsproliantserversindexhtmlfacet=ProLiantDLRack Storage white papers and analyst reports wwwhpecomstoragewhitepapers ";
f["109"]= " Server Profile Templates OneView, online help, help, REST API Server Profile Templates Server profile templates help to monitor, flag, and update server profiles in HPE OneView A server profile template serves as a structural reference when creating a server profile All of the configuration constructs of a server profile are present in the server profile template This template type defines the centralized source for the configuration of firmware, connections, local storage, SAN storage, boot, BIOS, profile affinity, and hides unused flexNICs Use REST APIs to  Create a server profile template Create server profile from a server profile template Copy a server profile template Edit a server profile template Delete a server profile template See more tasks Learn more About server profile templates serverprofiletemplates REST APIs ";
f["110"]= " Licensing OneView, online help, help, REST API Licensing Use REST APIs to  Add a license key to the appliance license pool Delete a license key View all licenses View license status View server hardware without an assigned license See more tasks Learn more About licensing About HPE OneView Advanced licensing for managing server hardware licenses REST APIs ";
f["111"]= " Configure an enclosure with an OA configuration script OneView, online help, help, REST API Configure an enclosure with an OA configuration script About OA configuration scripts Extract a script from a configured OA Copy an OA configuration script View or download OA command documentation Disallowed OA commands Sample OA configuration script About OA configuration scripts Use configuration scripts to simplify new enclosure deployment and configuration, particularly when setting up multiple enclosures, eliminating the need to configure each enclosure manually You can GET an enclosure configuration script from a logical enclosure or enclosure group You can UPDATE and DELETE an enclosure configuration script on individual logical enclosures To create a configuration script, do one of the following: Extract a script from a configured OA Copy an existing configuration script from a logical enclosure or enclosure group By entering a configuration script on the Enclosure Groups screen, a copy of the configuration script is stored with every logical enclosure you add that is associated with that enclosure group The configuration script is run on the physical enclosure when: You add an enclosure and the associated enclosure group contains a configuration script You GET the configuration script of a logical enclosure, make changes and then update PUT the script You refresh an enclosure which reruns the enclosure configuration script associated with the enclosure not the enclosure group You can initially enter passwords, SNMP community strings, and pass phrases in plain text as you create an enclosure or enclosure group script However, all passwords, SNMP community strings, and pass phrases are masked replaced by  in any UI or REST API response and are never displayed in plain text If you replace the  password string with another string and rerun the script, the password is changed to the new string Note that some commands cannot be run a second time For example, if you rerun the ADD USER username  command on the same enclosure and have changed the  string, the command will fail because that user already exists In this situation, remove the newly added user before you rerun the script If any part of the command that is returned with  is changed, and you do not replace  with another string, the value of the password or the SNMP community string becomes  For example, if you submit the script with the command SET USER PASSWORD user_name1 new_password, the script returns SET USER PASSWORD user_name1  If you change the command to SET USER PASSWORD user_name2 , the password for user_name2 is set to , and not new_password A subset of OA commands is disallowed in the enclosure configuration script to prevent conflicts with the appliance configuration and settings There is no syntax checking or other validation of the remaining script See Disallowed OA commands for a list of the OA commands not allowed in a configuration script View or download OA command documentation for a complete reference of OA commands Extract a script from a configured OA Prerequisites  Minimum required session ID privileges: Administrator Extracting a script from a configured OA using REST APIs When you perform a GET operation on an enclosure, the script URI is returned inside of the response body Select an enclosure GET restlogicalenclosures Get the enclosure using the URI from step 1 GET restlogicalenclosures id Get the script using the configuration script URI returned in step 2 GET restlogicalenclosures idscript For security, the retrieved current configuration does not contain any user passwords You can manually edit the script to add the user passwords after the user name on the ADD USER lines Copy an OA configuration script Get a copy of an existing configuration script from a logical enclosure or enclosure group Prerequisites  Minimum required session ID privileges: Server administrator Copying an OA configuration script using REST APIs When you perform a GET operation on a logical enclosure or enclosure group, the script URI is returned inside of the response body You can copy this script, make updates, and then reapply  PUT the script to another enclosure Select an enclosure or enclosure group GET restenclosures GET restenclosuregroups Get the enclosure or enclosure group using the URI from step 1 GET restenclosures id GET restenclosuregroups id Get the script using the configuration script URI returned in step 2 GET restlogicalenclosures idscript View or download OA command documentation For a complete reference of OA commands, view or download the HPE BladeSystem Onboard Administrator Command Line Interface User Guide from the HPE Support Center Viewing or downloading OA command documentation Go to http:wwwhpecomsupporthpesc Select Manuals from the left navigation pane Enter HPE Onboard Administrator in the Search box Select the returned result, HPE Onboard Administrator Select User guide Find the HPE BladesSystem Onboard Administrator Command Line Interface User Guide  title and view or download to your local computer Disallowed OA commands The following commands are not allowed in an enclosure configuration script because they conflict with the appliance configuration and could prevent the appliance from operating properly and securely Disallowed OA commands ADD EBIPA REMOVE CA CERTIFICATE SET ENCLOSURE NAME ADD EBIPAV6 REMOVE EBIPA SET ENCLOSURE SERIAL_NUMBER CLEAR NTP REMOVE EBIPAV6 SET ENCRYPTION CLEAR VCMODE REMOVE HPSIM CERTIFICATE SET FACTORY DISABLE DHCP_DOMAIN_NAME REMOVE OA ADDRESS IPV6 SET FIPS MODE DISABLE EBIPA REMOVE SNMP TRAPRECEIVER SET HPSIM TRUST MODE DISABLE EBIPAV6 REMOVE SNMP TRAPRECEIVER V3 SET IPCONFIG DISABLE FIRMWARE MANAGEMENT REMOVE SNMP USER SET NTP DISABLE HTTPS REMOVE TRUSTED HOST SET NTP PRIMARY DISABLE IPV6 REMOVE USER CERTIFICATE SET OA DOMAIN_NAME DISABLE IPV6DYNDNS REMOVE USER vcmuser SET OA NAME DISABLE NTP REMOVE USERS ALL SET PASSWORD DISABLE SLAAC SAVE EBIPA SET SNMP COMMUNITY READ DISABLE SNMP SAVE EBIPAV6 SET SSO TRUST MODE DISABLE TRUSTED HOST SET DATE SET TIMEZONE DISABLE USER vcmuser SET EBIPA SET USER ACCESS vcmuser ENABLE DHCP_DOMAIN_NAME SET EBIPAV6 SHOW ALL ENABLE EBIPA SET EBIPA INTERCONNECT SHOW SYSLOG  OA  HISTORY  ENABLE EBIPAV6 SET EBIPA SERVER UNASSIGN  SERVER  INTERCONNECT   <bay number>  ALL  <bay number range>  vcmuser ENABLE FIRMWARE MANAGEMENT SET ENCLOSURE ASSET TAG UNASSIGN OA vcmuser Sample OA configuration script Sample OAScriptcfg script #Sample script for HPE OneView # #NOTE: Set Enclosure Information SET RACK NAME Insert_Rack_Name #Optionally Configure Power SET POWER MODE REDUNDANT SET POWER SAVINGS ON SET ENCLOSURE POWER_CAP OFF SET ENCLOSURE POWER_CAP_BAYS_TO_EXCLUDE None #Set Interconnect PowerDelay Information SET INTERCONNECT POWERDELAY 18 0 #Set Server Power Delay Information SET SERVER POWERDELAY 116 0 #Optionally Configure Alertmail SET ALERTMAIL SMTPSERVER DISABLE ALERTMAIL #Optionally Configure NTP SET NTP SECONDARY SET NTP POLL 720 #Optionally Set Remote Syslog Information SET REMOTE SYSLOG SERVER  SET REMOTE SYSLOG PORT 514 DISABLE SYSLOG REMOTE #Optionally ADD a new user account and set as Admin on ALL bays ADD USER admin password SET USER CONTACT admin  SET USER FULLNAME admin  SET USER ACCESS admin ADMINISTRATOR ASSIGN SERVER 116 admin ASSIGN INTERCONNECT 18 admin ASSIGN OA admin ENABLE USER admin #Optionally reset the default Administrator password Set USER Administrator enter new password here #Set Login Banner Text Information CLEAR LOGIN_BANNER_TEXT DISABLE LOGIN_BANNER #Set Network Information #NOTE: Setting your network information through a script while # remotely accessing the server could drop your connection # If your connection is dropped this script may not execute to conclusion #NOTE: Set the IP address and DNS name for both OA1 and OA2 SET NIC AUTO 1 SET NIC AUTO 2 ENABLE ENCLOSURE_IP_MODE SET LLF INTERVAL 60 ENABLE LLF DISABLE DHCPV6 ";
f["112"]= " Creating a login session CIC int, features, product description, reference, security, roles OneView, online help, help, REST API Creating a login session You create a login session when you log in to the appliance through the browser or some other client for example, using the REST API Additional requests to the appliance use the session ID, which must be protected because it represents the authenticated user A session remains valid until you log out or the session times out for example, if a session is idle for a longer period of time than the session idle timeout value ";
f["113"]= " SAN Managers OneView, online help, help, REST API SAN Managers Use REST APIs to  Add a SAN manager Update a SAN manager See more tasks Learn more About SAN managers fcsansproviders REST APIs fcsansdevicemanagers REST APIs fcsansmanagedsans REST APIs ";
f["114"]= " Reassign the server profile to a server blade previously removed from an enclosure OneView, online help, help, REST API Reassign the server profile to a server blade previously removed from an enclosure When you reinsert a server blade into the same bay, the server profile is reassociated with it and a task notification is created But, if you reinsert a server blade into a different bay, the server profile associated with that server blade has a task error message stating that the server blade has been moved to a new location To resolve this issue, either reassign the server profile to the server blade in the new location, or move the server blade to the original bay Prerequisites Minimum required session ID privileges: Server administrator Reassigning the server profile to a server blade previously removed from an enclosure using REST APIs Get the server blade that was reinserted into a different bay GET restserverhardwarefilter=state='AddedWithErrors' Get the server profile URI that was associated with the server blade GET resttasksfilter=associatedResourceUri=' server blade URI' Get the server profile associated with the server blade GET restserverprofiles id Add the correct server hardware URI to the server profile Update the server profile POST restserverprofiles ";
f["115"]= " Add an iPDU OneView, online help, help, REST API Add an iPDU To bring an HPE Intelligent Module Power Distribution Unit iPDU under appliance management, you need the host name associated with the iPDU To find the host name, perform a GET REST API operation Prerequisites Minimum required session ID privileges: Server administrator The iPDU host name or IP address The iPDU administrator username and password Adding an iPDU and bringing it under management using REST APIs POST restpowerdevicesdiscover ";
f["116"]= " Delete portal registration OneView, online help, help, REST API Delete portal registration Prerequisites Minimum required session ID privileges: Server administrator Delete portal registration using REST APIs DELETE restsupportportalregistration ";
f["117"]= " Add or delete individual labels for a specific resource model OneView, online help, help, REST API Add or delete individual labels for a specific resource model To update labels for a specific resource, perform a POST operation to reapply all of label attributes View the labels attributes by using a GET operation, edit the attributes, and then perform a POST operation If you delete labels, the labels are removed during the POST operation Prerequisites Minimum required session ID privileges: a session ID with privileges to edit the resource model Updating labels for a specific resource model using REST APIs Perform a GET operation on a resource collection URI for example, restserverprofiles and then select a resource model URI Get the label using the URI from step 1 GET restlabelsresources resource URI Edit the labels Update the labels using the resource URI that you selected in step 1 Any labels that you deleted in step 3 are removed from the resource during the update POST operation POST restlabelsresources ";
f["118"]= " About activeactive and activestandby configurations OneView, online help, help, REST API About activeactive and activestandby configurations When determining which Virtual Connect network configuration to use activeactive or activestandby, consider the type of network traffic the enclosure must support For example: Will there be a high volume of servertoserver traffic eastwest in the enclosure Is the traffic flow in the enclosure mainly inbound and outbound northsouth By considering network traffic patterns, you can maximize the connected bandwidth or minimize servertoserver traffic leaving the enclosure Use an activestandby configuration if network traffic is between systems in the same enclosure eastwest This configuration minimizes or eliminates any servertoserver communications from leaving the enclosure Use an activeactive configuration if network traffic is inbound and outbound northsouth of the enclosure About activestandby configurations An activestandby configuration is an Ethernet network configuration where servers in the enclosure have two NIC ports connected to the same Virtual Connect network A single uplink set has uplinks in both interconnects The uplinks in one interconnect are active; the uplinks in the other interconnect are standby and available in the event of a network or interconnect failure Communications between servers do not leave the interconnect module For external communications, all servers in the enclosure use the active uplink, regardless of which NIC is actively passing traffic An activestandby configuration: Provides predictable bandwidth Does not oversubscribe topofrack switch ToR bandwidth An activestandby configuration has the following requirements: A minimum of one Ethernet network and one uplink set for each external VLAN ID you define About activeactive configurations An activeactive configuration is an Ethernet network configuration that allows active traffic on the same VLAN on multiple interconnect modules The NICs on all the servers in the enclosure have their NICs connected to adjacent Virtual Connect modules All uplinks are active to forward network traffic An activeactive configuration: Provides full use of all uplink ports no uplink port in standby mode Allows all traffic to egress through the interconnect module connected to the NIC port without crossing the internal stacking link, if stacking is used Doubles the available bandwidth while maintaining redundancy when combined with Smart Link The networks associated with an uplink set must be included in the server profile connection for the interconnect module For example, if Net_101_A is in uplink set US_A, which has ports from the interconnect module in bay 1, Net_101_A must be associated with the downlink port connected to the interconnect module in bay 1 for example, LOM1:1a When setting up an activeactive configuration in an enclosure, determine if you have a single logical interconnect group or a multiple logical interconnect group per enclosure configuration For more information, see About multiple logical interconnect groups in an enclosure group In a single logical interconnect group configuration, have at least two Ethernet interconnect modules with stacking links in the enclosure All interconnects are defined in one logical interconnect in the single logical interconnect group When you set up the activeactive configuration, all networks are available on both interconnects, and subsequently to any server connected to these interconnects through the use of the stacking links Networks are created in pairs for each VLAN you want to connect In a multiple logical interconnect group configuration, where you define each interconnect in a separate logical interconnect group, and subsequently separate logical interconnects, the interconnects are no longer stacked Because you can use the same network in both logical interconnect groups, you can create an activeactive configuration with twice as many available networks Requirements for an activeactive configuration An activeactive configuration requires proper configuration of OS and NIC teaming An activeactive configuration also requires two Virtual Connect modules and resources that meet the following requirements For an example of an activeactive configuration for an enclosure group with a single logical interconnect group, see Sample activeactive configuration for single logical interconnect group Resource Requirement Best practice Networks For a single logical interconnect group configuration, add a pair of networks for each VLAN you want to connect: at least one network for the first interconnect module and another for the second interconnect module using the same VLAN ID The smartLink attribute must be set to true for both networks For a single logical interconnect group configuration, designate a network name for a paired network using the naming convention <purpose>_ <VLAN ID>_ <side> where: <purpose> could be dev, mgmt, or prod, for example <side> could be A or B, 1 or 2, or right or left Uplink Set For a single logical interconnect group configuration, create a pair of uplink sets to associate the networks with the uplink ports on the interconnect module One set of networks assigned to the uplink set with uplinks on the first interconnect module The other networks assigned to the uplink set with uplinks on the second interconnect module Uplink ports in each uplink set are restricted to one interconnect For a multiple logical interconnect group configuration, create an uplink set on the first interconnect module and an uplink set on the second interconnect module with the same networks For a single logical interconnect group configuration, assign names to uplink sets using the naming convention <uplink set name>_ <side>, where: <side> could be A or B, 1 or 2, or right or left Network Sets optional One or more pairs of network sets Each set should include only networks that are intended to be used in the same server profile connection For example, if Net_101_A is in uplink set US_A, which has ports from the interconnect module in bay 1, Net_101_A must be associated with the downlink port connected to the interconnect module in bay 1 for example, LOM1:1a For a single logical interconnect group configuration, designate a network set name using the naming convention <purpose>_ <side>, where: <purpose> could be dev, mgmt, or prod for example <side> could be A or B, 1 or 2, or right or left Server Profiles The physical ports to which you want to map the network or network sets Map the profile connections to the downlink ports on the same interconnect module as the uplinks on the uplink set This ensures that the networks associated with the uplink ports in the uplink set match the networks assigned to the profile connections in the downlink ports Do not set the portId attribute to Auto Sample activeactive configuration for single logical interconnect group ";
f["119"]= " Update site information OneView, online help, help, REST API Update site information Prerequisites Minimum required session ID privileges: Server administrator Update site information using REST APIs PUT restsupportsitessiteKey ";
f["120"]= " Create a rack server OneView, online help, help, REST API Create a rack server Before you can add a rack server, you need the iLO management processor credentials for the rack server Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator The server’s iLO is configured with a host name or IP address The server is connected to a live power source Adding a rack server using REST APIs POST restserverhardware ";
f["121"]= " Modify a scope definition CONTACT CI DOC OWNERS before modifying this content OneView, online help, help, REST API Modify a scope definition Use this procedure to modify a scope name and description without modifying its resource assignments Modifying a scope definition using REST APIs Obtian the scope ID: GET restscopes Modify the scope: PUT restscopesid ";
f["122"]= " Enable or disable enhanced TLV support using REST APIs OneView, online help, help, REST API Enable or disable enhanced TLV support using REST APIs Enabling or disabling the enableRichTLV parameter determines the information that is advertised in the Chassis ID TLV of LLDP frames sent out by an interconnect Modifying this parameter impacts any service that queries this information for network topology information, for example attempting to derive network topology based on the contents of LLDPDUs Prerequisites Minimum required session ID privileges: Infrastructure administrator Virtual Connect 430 or higher installed on the interconnect Enabling enhanced TLV support using REST APIs Select a logical interconnect group URI GET restlogicalinterconnectgroups Get the logical interconnect group using the URI from step 1 GET restlogicalinterconnectgroups id Set enableRichTLV to true Update the logical interconnect group PUT restlogicalinterconnectgroups id Disabling enhanced TLV support using REST APIs Select logical interconnect group URI GET restlogicalinterconnectgroups Get the logical interconnect group using the URI from step 1 GET restlogicalinterconnectgroups id Set enableRichTLV to false Update the logical interconnect group PUT restlogicalinterconnectgroups id More information About enhanced typelengthvalue TLV structure ";
f["123"]= " Enable metric streaming OneView, online help, help, REST API Enable metric streaming Metrics for managed resources can be streamed at a specified interval You can do the following steps to enable the metric relay: Enabling metric streaming APIs using REST APIs Get list of resource types and metrics that can be configured for live streaming GET restmetricscapability Configure the live metric stream PUT restmetricsconfiguration Receive the live stream of metrics on AMQP message exchange – MSMB msmb NOTE: MSMB Metric Streaming Message Bus is an interface that uses asynchronous messaging to notify subscribers about the most recent metric of the managed resources Metrics are streamed for servers with ILO Advanced Licenses only Supported servers are G7, Gen 8, and Gen 9 Fetch metric streaming capability You can fetch the list of resource types and supported metrics that HPE OneView is capable of relaying Fetching metric streaming capability using REST APIs Get list of resource types and metrics GET restmetricscapability Fetch metric streaming configuration You can fetch the current configuration for which metrics are being streamed Fetching metric streaming configuration using REST APIs Get configuration for metrics GET restmetricsconfiguration Update metric streaming configuration You can update the metrics configuration with new values An update overwrites the existing configuration Updating metric streaming configuration using REST APIs Update the metric streaming configuration PUT restmetricsconfiguration ";
f["124"]= " Best practices for backing up an appliance OneView, online help, help, REST API Best practices for backing up an appliance Method Description Creating Always use the HPE OneView backup feature to back up your appliance CAUTION: Do not use any hypervisorprovided capabilities or snapshots to back up HPE OneView appliances because doing so can cause synchronization errors and result in unpredictable and unwanted behavior Frequency Hewlett Packard Enterprise recommends backing up your appliance configuration regularly, preferably daily and especially: After adding hardware After changing the appliance configuration Before and after updating the appliance firmware After performing a factory reset of the frame You can back up the appliance while it is in use and while normal activity is taking place You do not need to wait for tasks to stop before creating a backup file Archiving The backup file format is proprietary However, Hewlett Packard Enterprise recommends that you: Create and download the backup file Store the backup file in a safe, offappliance location to protect your sensitive data Hewlett Packard Enterprise recommends using an enterprise backup product such as Hewlett Packard Enterprise Data Protector to archive backup files For information on Hewlett Packard Enterprise Data Protector, see the following website: http:wwwhpecomsoftwaredataprotector Hewlett Packard Enterprise provides REST APIs for integration with enterprise backup products ";
f["125"]= " Delete a storage volume storagevolumesall OneView, online help, help, REST API Delete a storage volume When a storage volume is deleted, it is removed from appliance management and deleted from the storage system resulting in loss of all data If you want to remove the storage volume from appliance management without deleting data, set the export only header to true  exportOnly:true The exported volume remains on the storage system and you can add it again to the appliance Prerequisites Minimum required session ID privileges: Infrastructure administrator or Storage administrator Deleting a storage volume using REST APIs Select a storage volume URI GET reststoragevolumes Delete the storage volume DELETE reststoragevolumes id ";
f["126"]= " Developer tools in a web browser OneView, online help, help, REST API Developer tools in a web browser You can use developerdebug tools in your web browser to view the REST API operations as they happen in the UI The UI uses REST APIs for all operations; therefore, anything you can do in the UI can be done using REST API operations ";
f["127"]= " Control power to a power delivery device outlet OneView, online help, help, REST API Control power to a power delivery device outlet Some power delivery devices are equipped with locator lights that you can power on to help locate a device in the data center You can use REST APIs to power on and off the locator lights on power delivery devices Prerequisites Minimum required session ID privileges: Server administrator Controlling power to a power delivery device outlet using REST APIs Select a power delivery device URI GET restpowerdevices Get the power delivery device GET restpowerdevices id Turn on or off a power delivery device PUT restpowerdevices idpowerState ";
f["128"]= " Update the IDs returned in a range for virtual MAC addresses OneView, online help, help, REST API Update the IDs returned in a range for virtual MAC addresses If there are IDs that are no longer in use, and you want to make them available, you can update the returned IDs To update a virtual MAC address range, perform a PUT operation to reapply all of the virtual MAC address attributes View the virtual MAC address range attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes Prerequisites Minimum required session ID privileges: Infrastructure administrator, Network administrator, or Server administrator Updating the IDs returned in a range for virtual MAC addresses Select a virtual MAC address range URI GET restidpoolsvmac Get the virtual MAC address range and note the collectorUri GET restidpoolsvmacranges id Update the returned IDs using the collectorUri from step 2 PUT restidpoolsvmacranges idcollector ";
f["129"]= " Best practices for maintaining a secure appliance CONTACT CI DOC OWNERS before modifying this content CIC int, features, product description, reference, security, roles OneView, online help, help, REST API Best practices for maintaining a secure appliance The following table comprises a partial list of security best practices that Hewlett Packard Enterprise recommends in both physical and virtual environments Differing security policies and implementation practices make it difficult to provide a complete and definitive list Topic Best Practice Accounts Limit the number of local accounts Integrate the appliance with an enterprise directory solution such as Microsoft Active Directory or OpenLDAP Certificates Use certificates signed by a trusted certificate authority CA, if possible HPE OneView uses certificates to authenticate and establish trust relationships One of the most common uses of certificates is when a connection from a web browser to a web server is established The machine level authentication is carried out as part of the HTTPS protocol, using SSL Certificates can also be used to authenticate devices when setting up a communication channel The appliance supports selfsigned certificates and certificates issued by a CA The appliance is initially configured with selfsigned certificates for the web server, database, and message broker software The browser will display a warning when browsing to the appliance using selfsigned certificates Hewlett Packard Enterprise advises customers to examine their security needs that is, to perform a risk assessment and consider the use of certificates signed by a trusted CA For the highest level of security, Hewlett Packard Enterprise recommends that you use certificates signed by a trusted certificate authority: Ideally, you should use your company's existing CA and import their trusted certificates The trusted root CA certificate should be deployed to user’s browsers that will contact systems and devices that will need to perform certificate validation If your company does not have its own certificate authority, then consider using an external CA There are numerous thirdparty companies that provide trusted certificates You will need to work with the external CA to have certificates generated for specific devices and systems and then import these trusted certificates into the components that use them As the Infrastructure administrator, you can generate a CSR certificate signing request and, upon receipt, upload the certificate to the appliance web server This ensures the integrity and authenticity of your HTTPS connection to the appliance Certificates can also be uploaded for the database and message broker For more information, see Using a certificate authority Network Hewlett Packard Enterprise recommends a strict separation of the management LAN and production LAN, using VLAN or firewall technology or both to maintain the separation: Management LAN Connect all management processor devices including Onboard Administrators and virtual connections through an Onboard Administrator, iLOs, and iPDUs to the management LAN Grant management LAN access to authorized personnel only: Infrastructure administrators, Network administrators, and Server administrators Production LAN Connect all NICs for managed devices to the production LAN Do not connect management systems for example, the appliance, the iLO card, and the Onboard Administrator directly to the Internet If you require access to the Internet, use a corporate VPN virtual private network that provides firewall protection Nonessential services The appliance is preconfigured so that nonessential services are removed or disabled in its management environment Ensure that you continue to minimize services when you configure host systems, management systems, network devices including network ports not in use to significantly reduce the number of ways your environment could be attacked Passwords For local accounts on the appliance, change the passwords periodically according to your password policies Ensure that passwords include at least three of these types of characters: Numeric character Lowercase alphabetic character Uppercase alphabetic character Special character Roles Clearly define and use administrative roles and responsibilities; for example, the Infrastructure administrator performs most administrative tasks For more information on roles, see About user roles Service Management Consider using the practices and procedures, such as those defined by the Information Technology Infrastructure Library ITIL For more information, see the following website: http:wwwitilofficialsitecomhomehomeaspx Updates Ensure that a process is in place to determine if software and firmware updates are available, and to install updates for all components in your environment on a regular basis Virtual Environment Educate administrators about changes to their roles and responsibilities in a virtual environment Restrict access to the appliance console to authorized users For more information, see Restricting console access If you use an Intrusion Detection System IDS solution in your environment, ensure that the solution has visibility into network traffic in the virtual switch Turn off promiscuous mode in the hypervisor and encrypt traffic flowing over the VLAN to lessen the effect on any VLAN traffic sniffing NOTE: In most cases, if promiscuous mode is disabled in the hypervisor, it cannot be used on a VM Virtual Machine guest The VM guest can enable promiscuous mode, but it will not be functional Maintain a zone of trust, for example, a DMZ demilitarized zone that is separate from production machines Ensure proper access controls on Fibre Channel devices Use LUN masking on both storage and compute hosts Ensure that LUNs are defined in the host configuration, instead of being discovered Use hard zoning which restricts communication across a fabric based on port WWNs Worldwide Names, if possible Ensure that communication with the WWNs is enforced at the switchport level ";
f["130"]= " Start working with REST APIs OneView, online help, help, REST API Start working with REST APIs Prerequisites  To make individual REST calls to the HPE OneView API, you will need to install a RESTclient extension addon or plugin into your webbrowser To install the client, visit your browser's Tools, Addons, or Extensions page to search for, download, and install the appropriate extension For example, you could install REST Client for the Firefox browser, or Advanced REST Clientor Postman for the Chrome browser NOTE: In the following example, it is assumed that HPE OneView has already been configured for initial use with Administrator access If HPE OneView has not yet been configured, additional steps are required which are not included in this example It is also assumed you already know how to use the REST client to construct API statements Starting to work with REST APIs Once the extension is installed, restart your browser and browse to the HPE OneView loginscreen as you normally would IMPORTANT: Be sure to accept the security exception certificate or the browser will block further requests Open a new tab in the same browser, and start your RESTclient extension Make your first RESTcall a GET request Enter the appliance URL and press SEND For example: https:1921681101 You should receive a 200OK response and some text If you receive a 0 status instead, check that you accepted the certificate as noted in step 1 Make your second RESTcall an operation to get your SessionID for subsequent operations Add the following two httpheaders to your request: Contenttype: applicationjson Accept: applicationjson Add the textbody RAWtext with a valid username and password For example: userName:administrator,password:mypassword Set the request to be: https:1921681101restloginsessions Set the requesttype to: POST and SEND your request You should receive a 200 OK status and a sessionID similar to the following:  sessionID: 2zCmY9frjiYp1XIzsCiu2H1EjUgmcy08   If you receive a 403 Forbidden response, check that your credential is valid Add a third header with your new sessionID Make your third request For example: Auth: 2zCmY9frjiYp1XIzsCiu2H1EjUgmcy08 Set the request to be: https:1921681101restversion Set the request to GET and SEND your request You should receive the appliance version  minimumVersion: 1, currentVersion: 120  See the HPE OneView REST API Reference for additional requests and additional header requirements ";
f["131"]= " About SNMP settings OneView, online help, help, REST API About SNMP settings Network management systems use SNMP Simple Network Management Protocol to monitor networkattached devices for conditions that require administrative attention By configuring settings on the Logical Interconnect Groups and Logical Interconnects screens, you can enable thirdparty SNMP managers to monitor readonly network status information of the interconnects An SNMP manager typically manages a large number of devices, and each device can have a large number of objects It is impractical for the manager to poll information from every object on every device Instead, each SNMP agent on a managed device notifies the manager without solicitation by sending a message known as an event trap HPE OneView enables you to control the ability of SNMP managers to read values from an interconnect You can filter the type of SNMP trap to capture, and then designate the SNMP manager to which traps will be forwarded By default, SNMP is enabled with no trap destinations set When you create a logical interconnect, it inherits the SNMP settings from its logical interconnect group To customize the SNMP settings at the logical interconnect level, use the Logical Interconnects screen or REST APIs ";
f["132"]= " Read resource tree information published to the index OneView, online help, help, REST API Read resource tree information published to the index The information that appliance resources publish to the index includes associated resources that are readable using a tree structure For example, when you perform a GET operation on the enclosure, you can specify the parent and child depth, to control the amount and type of resources that are returned Prerequisites Minimum required session ID privileges: Infrastructure administrator Reading resource tree information published to the index using REST APIs GET resttrees ";
f["133"]= " Quick Start: Initial configuration using REST APIs OneView, online help, help, REST API Quick Start: Initial configuration using REST APIs After installation, you must configure the appliance and bring your environment under management or monitoring The individual procedures for configuring the appliance and bringing your environment under management for the first time are no different than when they are performed subsequently or when adding individual components or performing maintenance However, during the initial configuration, you will likely be bringing your entire environment under management and configuring it in the appliance all at once While the appliance is designed to allow flexibility in the order that you create, add, and update resources and devices, Hewlett Packard Enterprise recommends following the workflow below for your initial set up or when making significant additions or changes to your environment “Configure the appliance and bring your environment under management of the appliance” “Optional: Define the physical topology and power systems of your environment in the appliance” Configure the appliance and bring your environment under management of the appliance Configuration step Prerequisites Description Accept the End User License Agreement EULA NOTE: You can enable or disable support access optional while accepting the EULA Support access is enabled by default None You must accept the EULA to proceed with the appliance configuration If you do not accept the EULA, an error occurs when you attempt to change the administrator password If you want to allow authorized personnel to access your system to assess problems that you report, you can enable authorized support access Configure the appliance Fully qualified host name of the appliance IPv4 address of the appliance through DHCP or static address; DHCP is not recommended Default gateway IP address One or more DNS server IP addresses IPv6 address of the appliance optional This step prepares the appliance for your environment After you complete this step, you can begin building your environment infrastructure Create users: Create a user with local authentication Assign roles to an enterprise group Local authentication Login name Full name optional Initial password Choose a role or create a specialized role Contact information optional Directorybased authentication An enterprise directory server to authenticate and authorize users Default directory when multiple directories are configured After you create local and directorybased users, they can access the appliance and complete tasks based on their assigned role in your data center environment Upload a firmware bundle Recommended NOTE: If you do not upload an SPP, you will not be able to add hardware that does not meet minimum firmware requirements At least one HPE Service Pack for ProLiant SPP firmware bundle The SPP enables you to update firmware on servers, blades, enclosures, and interconnects You can apply SPPs as baselines to enclosures, interconnects, and server profiles NOTE: This process might take several minutes You can proceed to the next configuration step Create networks: Create an Ethernet network Create a Fibre Channel network Network name VLAN ID Bandwidth settings Smart link, private network, or both optional   Create a network set Network set name Networks to add to the network set Untagged VLAN A network set provides uniformity across server profiles that reference this network set and group Ethernet networks for faster configuration Update a connection template Connection template URI Minimum bandwidth Maximum bandwidth When you create an Ethernet or Fibre Channel network, a connection template is created A connection template defines the maximum and typical bandwidth You must have Network administrator privileges to update a connection template Create a logical interconnect group Define the logical interconnects in the added enclosures Create uplink sets to connect networks or network sets to uplink ports A logical interconnect group defines a template for the interconnects in an enclosure Create an enclosure group Assign a logical interconnect group to the enclosure group An enclosure group provides uniform configuration across a group of enclosures that reference it The enclosure group contains a reference to a logical interconnect group that defines how the physical interconnects are configured in the enclosure Add an enclosure to manage its content NOTE: If your enclosure does not have embedded licenses, you will have to add licenses to the appliance If you have an SNMP read community string you prefer to use, add it before you begin adding enclosures Add a c7000 enclosure to monitor the hardware IP address or fully qualified domain name of the enclosure OA credentials For managed enclosures, assign an enclosure group For managed enclosures, assign a firmware baseline When you add an enclosure to be managed, you can apply configurations, deploy server profiles, monitor operation status, collect statistics, and alert users to specific conditions When you add an enclosure to monitor, you can monitor operation status, collect statistics, and alert users to specific conditions Create a server profile Server profile name and description Enclosure name and bay ID Server hardware Network connectivity FlexNIC to assign to the network connection BIOS settings Boot order Server profiles capture all aspects of server configuration in one place, enabling you to consistently replicate new server profiles and to rapidly adjust them for changes in your data center environment Optional: Define the physical topology and power systems of your environment in the appliance Configuration step Prerequisites Add power devices to the appliance Define your power devices using the Power Delivery Devices resource Device type Device name Rated capacity of the device Line voltage and phase Power feed side  A or B Power connections to the device Add and configure racks Add racks and configure the layout of enclosures, power delivery devices, and other rack devices using the racks resource Rack name Dimensions of the rack and number of slots Add enclosures and power delivery devices to the rack Edit the layout of devices within the rack The thermal limit of the rack optional NOTE: The appliance automatically creates racks and when you import enclosures It places enclosures that are linked by management cables in the same rack Create data centers and position racks in them Define the physical topology of your data center using the Data Centers resource to enable temperature monitoring and 3D visualization using the UI Data center name Dimensions of the data center Position racks in the data center Power information such as electrical derating, voltage, and power costs Cooling information such as cooling capacity and cooling to power cost multiplier ";
f["134"]= " Add a c7000 enclosure to monitor the hardware &cicfusionabstract; OneView, online help, help, REST API Add a c7000 enclosure to monitor the hardware You can add c7000 enclosures to inventory and monitor the hardware Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator The enclosure OA user name and password The enclosure primary or standby OA is configured with a host name or IP address Power supplies are configured and the enclosure power is turned on Adding a c7000 enclosure to monitor the hardware using REST APIs Add an enclosure To monitor the hardware in this enclosure, specify Monitored for the State value POST restenclosures See also  About monitored c7000 enclosures Enclosures ";
f["135"]= " Change the locator light state of a power delivery device to on or off OneView, online help, help, REST API Change the locator light state of a power delivery device to on or off To find a specific physical power delivery device in a rack, turn on the locator light Prerequisites Minimum required session ID privileges: Server administrator Change the locator light of a power delivery device to on or off using REST APIs Select a power delivery device URI GET restpowerdevices Get the power delivery device GET restpowerdevices id Turn on or off the locator light PUT restpowerdevices iduidState ";
f["136"]= " About firmware associated with a logical interconnect OneView, online help, help, REST API About firmware associated with a logical interconnect All components in a logical enclosure must either run the same firmware version or run firmware versions that are compatible to each other You can select a single Service Pack for ProLiant SPP and apply it to all components in an enclosure, therefore minimizing the chance of downtime due to firmware incompatibility You can also apply an SPP to a logical interconnect, which results in all associated interconnects having the same firmware baseline This operation, by default, updates firmware only on those member interconnects that are running a different version of firmware and ignores the interconnects that are running the same firmware version The firmware version associated with the logical interconnect is automatically updated when an enclosure is added and an SPP is selected for the firmware baseline The OA and iLO firmware are updated as well Network disruptions do not occur as long as server profiles have not yet been defined or applied in the new enclosure However, if manage manually is selected during an enclosure add, the baseline for the interconnects is Not set If subsequent firmware updates apply to the enclosure only, the baseline is still shown in HPE OneView as Not set A baseline can be set for logical interconnect firmware update either when adding the enclosure using the Enclosures screen, or when updating the firmware from the Logical Enclosures screen and selecting Enclosure  logical interconnect  server profiles If a baseline for logical interconnect is never set, the firmware for the enclosure must be managed manually About updating firmware for logical interconnects Firmware activation options allow you to maintain network availability and reduce the probability of outages due to human error You also have the option of staging the firmware for later activation You can activate the staged firmware on an individual interconnect or on all interconnects You have the following options when updating firmware based on the logical interconnect: Option Description Update firmware stage  activate Stages uploads the selected firmware to the secondary flash memory on the interconnect, and then activates the firmware as the baseline At the end of this operation, all member interconnects are running the same firmware baseline and are compliant with one another This option and parallel activation affects the connectivity to and from the servers until the activation is complete, but does update the firmware in the shortest time See About activating firmware options for information about parallel activation Stage firmware for later activation Stages uploads the selected firmware to the secondary flash memory on the interconnect, but does not activate the firmware You can activate the firmware at a later time This option allows manual sequencing of the firmware activation and is the preferred approach to minimize service interruption Activate firmware Activates the selected staged firmware When updating firmware based on the logical interconnect, if one or more interconnects are already running the targeted firmware version, HPE OneView excludes those interconnects from the firmware update About activating firmware options You have the following options for activating the firmware on Ethernet and Fibre Channel interconnect modules: Option Description Oddeven Activates odd numbered interconnect modules 1, 3, 5, and 7 on the left side, followed by even numbered modules 2, 4, 6, 8 on the right side Serial Activates one interconnect module at a time starting with the highest numbered bay This method is the least disruptive Parallel Activates all interconnect modules at the same time This method is the most disruptive and can cause network and storage connectivity outages ";
f["137"]= " About labels OneView, online help, help, REST API About labels You can use labels to organize resources into groups For example, you might want to identify the servers that are used primarily by the Finance team, or identify the storage systems assigned to the AsiaPacific division Resources supporting labels also have filters to allow you to filter by the labels that have been placed on the resource The global search can be used to search for resources by label ";
f["138"]= " Add labels to a resource model OneView, online help, help, REST API Add labels to a resource model You can add labels to a resource model to organize resource models into groups First you must select a resource model URI before adding labels Prerequisites Minimum required session ID privileges: a session ID with privileges to edit the resource model Adding a label using REST APIs Perform a GET operation on a resource collection URI for example, restserverprofiles and then select a resource model URI Add a label or set of labels using the resource URI from step 1 POST restlabelsresources ";
f["139"]= " About accessing HPE OneView message buses OneView, online help, help, REST API About accessing HPE OneView message buses HPE OneView supports asynchronous messaging to notify subscribers of changes to managed resources—both logical and physical – and changes to metrics on managed resources For example, you can program applications to receive notifications when new server hardware is added to the managed environment or when the health status of physical resources changes, and you can stream power, thermal and CPU metrics for managed resources Using HPE OneView REST APIs, you can obtain certificates to access the two message buses described in this chapter: the StateChange Message Bus or the Metric Streaming Message Bus The message content is sent in JSON JavaScript Object Notation format and includes the resource model Before you can set up subscription to messages, you must create and download an AMQP Advanced Message Queuing Protocol  client certificate from the appliance using REST APIs Next, you connect to the message bus using an AMQP client configured for certificatebased authentication and the TLS 11 or TLS 12 protocol After connecting to the message bus, you set up a queue with the queue name empty, and AMQP generates a unique queue name You use this queue name to bind your client to exchanges and receive messages Examples are provided in the following sections, using NETC#, Java, and Python to connect to and receive messages from these messages buses ";
f["140"]= " Nonbrowser clients ATLAS CIC int, features, product description, reference, security, roles OneView, online help, help, REST API Nonbrowser clients The appliance supports an extensive number of REST APIs Any client, not just a browser, can issue requests for REST APIs The caller must ensure that they take appropriate security measures regarding the confidentiality of credentials, including: The session token, which is used for data requests Responses beyond the encryption of the credentials on the wire using HTTPS ";
f["141"]= " Create an enclosure group OneView, online help, help, REST API Create an enclosure group An enclosure group is a logical resource that defines a consistent configuration for an enclosure making up a logical enclosure The network connectivity for an enclosure group is defined by the logical interconnect groups associated with the enclosure group For more information about enclosure groups, see About enclosure groups When you add an enclosure, you can choose the enclosure group that is associated with a specific logical interconnect group or groups and those attributes are applied to the enclosure and physical interconnects contained within that enclosure Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator An existing logical interconnect group Creating an enclosure group using REST APIs Select a logical interconnect group URI GET restlogicalinterconnectgroups Create an enclosure group that includes the logical interconnect group URI you selected POST restenclosuregroups See also  Quick Start: Initial configuration using REST APIs ";
f["142"]= " Read a storage volume template storagevolumetemplatesall OneView, online help, help, REST API Read a storage volume template Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator Reading a storage volume template using REST APIs Select a storage volume template GET reststoragevolumetemplates Read the storage volume template GET reststoragevolumetemplates id ";
f["143"]= " Update the firmware in a logical enclosure OneView, online help, help, REST API Update the firmware in a logical enclosure The firmware baseline can be set during the logical enclosure creation to align all the management module firmware This includes updating the enclosure manager  Onboard Administrator and the iLO for the server hardware as well as the interconnects within the enclosure Options include updating the firmware for the enclosure controller  Onboard Administrator only, all components in the enclosure  Onboard Administrator and logical interconnects, or all infrastructure components as well as server blades with assigned server profiles Other flags can be set to force the firmware installation even if the baseline provided is already installed or is a downgrade candidate, and to validate whether the update to the logical interconnect would occur in a disruptive or nondisruptive mode Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator Updating a logical enclosure using REST APIs Set the firmware baseline for a logical enclosure: GET restlogicalenclosures PATCH restlogicalenclosuresid PUT restlogicalenclosuresid ";
f["144"]= " Delete all labels for a specific resource model OneView, online help, help, REST API Delete all labels for a specific resource model To delete all labels for a specific resource, perform a DELETE operation If you want to add or delete individual labels for a specific resource, see Add or delete individual labels for a specific resource model Prerequisites Minimum required session ID privileges: a session ID with privileges to edit the resource model Reading a label using REST APIs Perform a GET operation on a resource collection URI for example, restserverprofiles and then select a resource model URI Delete the resource model labels using the URI from step 1 DELETE restlabelsresources resource URI ";
f["145"]= " About Ethernet networks OneView, online help, help, REST API About Ethernet networks You use Ethernet networks as data networks You can create the following types of Ethernet networks: Tagged Untagged Tunnel About tagged Ethernet networks A tagged network uses virtual LANs VLANs, allowing multiple networks to use the same physical connections By sharing physical uplinks, you can separate traffic streams from different servers using the same set of uplinks Tagged Ethernet networks that are connected to enclosure interconnects require a VLAN ID You can add multiple Ethernet networks that use the same VLAN ID This capability is required for logical interconnects that use an activeactive configuration Each network name in the appliance must be unique Tagged Ethernet networks and network sets You can assign multiple tagged Ethernet networks to a named group called a network set Later, when you add a connection in a server profile, you can select this network set to enable multiple networks to be selected for that single connection Any change made to a network set is applied to all server profiles using the network set About untagged Ethernet networks An untagged network is a single dedicated network without a VLAN tag, used to pass traffic without VLAN tags Any tagged packets are dropped Forwarding is done by MAC address You might want to configure an untagged network for iSCSI storage traffic or set up networks without configuring VLANs About tunnel Ethernet networks A tunnel network is a single dedicated network with a dedicated set of uplink ports used to pass a group of VLANs without changing the VLAN tags You may want to use tunnel networks if you want to expand beyond the current total of 1000 networks per logical interconnect and 162 networks per downlink port, or if you want to control the resources and QoS You can have a tunnel network with a maximum of 4094 VLANs About Smart Link Smart Link enables the server software to detect and respond to a loss of network connectivity on the interconnect uplink ports With Smart Link enabled, the Virtual Connect interconnects will drop the Ethernet link on all server connections associated with the network if all uplink ports within an uplink set lose their connection to the data center switches Smart Link causes the operating system to detect a failure and direct traffic to an alternate path In order for the Smart Link functionality to operate as designed, valid DCC Device Control Channelcompatible NIC firmware and drivers must be installed on the server blade Smart Link can be helpful when using certain server network teaming bonding policies Smart Link must be enabled for activeactive, horizontal stacking, and primaryslice configurations ";
f["146"]= " Backup the appliance OneView, online help, help, REST API Backup the appliance If an appliance is corrupted, you might need to restore the appliance from a backup file The backup file contains configuration settings and management data that is stored in a proprietary format After the backup is initiated, a TaskResource URI is created, that you use to track the progress of the backup When the backup is complete, you can use a GET REST API operation to download and change the backup file name The latest backup is stored on the appliance and is replaced when a new backup is initiated Prerequisites Minimum required session ID privileges: Backup administrator Creating and downloading an appliance backup file using REST APIs Create the backup file POST restbackups Download the backup file GET restbackupsarchive backup URI NOTE: After the POST operation is complete, a TaskResource URI and backup URI are returned You can use the TaskResource URI to monitor the progress of the backup Use the backup URI to refer to a specific backup when downloading the backup file or performing another operation ";
f["147"]= " Add an email recipient and filter pair OneView, online help, help, REST API Add an email recipient and filter pair After initial configuring of the email notification feature, you can add additional filter queries with corresponding email addresses Prerequisites Required session ID privileges: Infrastructure administrator Adding an email recipient and filter pair using REST APIs Perform a GET for the appliance email notifications: GET restappliancenotificationsemailconfig Enter the alert filter query and the corresponding email address or addresses Using the resource URI from step 1, reconfigure the appliance for email notifications: POST restappliancenotificationsemailconfig ";
f["148"]= " Addresses and Identifiers OneView, online help, help, REST API Addresses and Identifiers Use REST APIs to  Create an automatically generated ID range for virtual MAC addresses, WWNs, or serial numbers Create a custom ID range for virtual MAC addresses, virtual WWNs, or virtual serial numbers Read active ID pools and their properties Update the allocated IDs in a range for virtual MAC addresses Update the IDs returned in a range for virtual MAC addresses See more tasks Learn more About ID pools idpools REST APIs idpoolsvmacranges REST APIs idpoolsvsnranges REST APIs idpoolsvwwnranges REST APIs ";
f["149"]= " Appliance access over SSL CONTACT CI DOC OWNERS before modifying this content CIC int, features, product description, reference, security, roles OneView, online help, help, REST API Appliance access over SSL All access to the appliance is through HTTPS HTTP over SSL, which encrypts data over the network and helps to ensure data integrity ";
f["150"]= " Best practices OneView, online help, help, REST API Best practices Hewlett Packard Enterprise recommends the following best practices Learn about the builtin best practice features of HPE OneView Groups, templates, and sets Appliance Best practices for maintaining a secure appliance Best practices for backing up an appliance Best practices for restoring an appliance Monitoring infrastructure health Best practices for monitoring health Network configuration Requirements for an activeactive configuration ";
f["151"]= " Add an enclosure to manage its content OneView, online help, help, REST API Add an enclosure to manage its content Adding a c7000 enclosure using its IP address or host name, along with the enclosure OA Onboard Administrator user name and password, brings the enclosure and its contents under appliance management Before adding an enclosure, you must create or select an enclosure group You can also update the enclosure firmware or enclosure and logical interconnect firmware while adding the enclosure To learn more about the logical interconnect groups that are associated with enclosure groups, see Create a logical interconnect group and Create an enclosure group NOTE: The name associated with the enclosure is the enclosure name set in the OA, not the OA name If the enclosure that you are adding contains Virtual Connect Fibre Channel interconnects, see Update the interconnect firmware for HPE Virtual Connect Fibre Channel interconnects Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator If an enclosure group does not exist, you must create it If you have an SNMP read community string you prefer to use, Update the SNMP read community string before you begin adding an enclosure The enclosure OA user name and password The enclosure primary or standby OA is configured with a host name or IP address Power supplies are configured and the enclosure power is turned on The firmware repository contains at least one firmware bundle Adding a c7000 enclosure using REST APIs Select an enclosure group URI GET restenclosuregroups Add an enclosure To update the firmware, specify the value EnclosureOnly or EnclosureAndLogicalInterconnect for the updateFirmwareOn property POST restenclosures NOTE: You might want to forcibly add an enclosure, for example, if the enclosure is managed by another appliance You must set the force attribute to true However, if the enclosure is managed by VCM or VCEM, you might be able to migrate the enclosure into HPE OneView instead, which saves the configuration information See Migrate a c7000 VCM enclosure using REST API Forcibly adding an enclosure removes any existing configuration POST restenclosures See also  Quick Start: Initial configuration using REST APIs Enclosures ";
f["152"]= " Restore the appliance from a backup file OneView, online help, help, REST API Restore the appliance from a backup file Prerequisites Minimum required session ID privileges: Infrastructure administrator You have uploaded a backup file to the appliance Restoring the appliance from a backup file using REST APIs Initiate the restore process POST restrestores The restore URI is returned List the status of the restore process GET restrestores ";
f["153"]= " Utilization OneView, online help, help, REST API Utilization Use REST APIs to  Read utilization for a specific enclosure Read utilization for specific server hardware Read utilization for a specific power delivery device See more tasks Learn more restenclosures idutilization REST APIs restserverhardware idutilization REST APIs restpowerdevices idutilization REST APIs ";
f["154"]= " Add a license key to the appliance license pool OneView, online help, help, REST API Add a license key to the appliance license pool Prerequisites Minimum required session ID privileges: Infrastructure administrator, Server administrator Adding a license key to the appliance license pool using REST APIs POST restlicenses ";
f["155"]= " About network sets OneView, online help, help, REST API About network sets A network set is a collection of tagged Ethernet networks that form a named group to simplify server profile creation Network sets are useful in virtual environments where each server profile connection needs to access multiple networks Use network sets in server profile connections to make all networks on a connection's downlink port available Network sets define how packets will be delivered to the server when a server Ethernet connection is associated with the network set Network sets also enable you to define a VLAN trunk and associate it with a server connection Instead of assigning a single network to a connection in a server profile, you can assign a network set to that connection Using network sets, you can quickly deploy changes to the network environment to multiple servers For example, you have 16 servers connected to a network set To add a new network to all 16 servers, you only need to add it to the network set instead of each server individually You can create a network set for your production networks and one for your development networks You can configure a hypervisor with a vSwitch to access multiple VLANs by creating a network set as a trunk that includes these networks Network set prerequisites All networks in a network set must be Ethernet networks and must have unique external VLAN IDs Untagged and tunnel networks are single networks and do not use network sets All networks in a network set must be configured in the same appliance A network can be a member of multiple network sets All networks in a network set must be added to uplink sets or internal networks in the logical interconnect group and its logical interconnects in order to be used in server profiles with connections to the logical interconnect A network set can be empty contain no networks or can contain one or more of the networks configured in the logical interconnect group and logical interconnect Empty network sets enable you to create network sets in the configuration before you create the member networks, or to remove all of the member networks before you add their replacements However, if a server profile adds a connection to an empty network set, the server cannot connect to any data center networks using that connection Creating, editing, and deleting network sets When you create or modify a network set, you can designate a network for untagged packets If you do not designate an untagged network, untagged packets are rejected on the profile connection associated with this network set Server traffic must be tagged with the VLAN ID of one of the Ethernet networks in the network set Untagged server traffic is either sent to the untagged network if an untagged network is defined or is rejected if no untagged network is defined The untagged network can send tagged and untagged traffic between the server and the interconnect simultaneously When you create or modify a network set, you define the maximum bandwidth and the preferred bandwidth for connections to that network set A server profile can override the preferred bandwidth but not the maximum bandwidth When a network is deleted, it is automatically deleted from all network sets to which it belonged When you delete a network set, the networks that belong to the network set are not affected However, any servers with a connection to that network set are affected because their connections are defined as being to the network set and not to the individual networks Because the network set is no longer available, the network traffic to and from that server through that connection is stopped When you delete a network set, any server profile connections that specified that network set become disconnected When deleting networks in a network set, if all inuse networks are removed from the network set, all assigned profiles using this network set are in error and the server profile connections lose connectivity To avoid connectivity loss, either leave at least one network in the network set or disassociate the network set from all server profiles ";
f["156"]= " Upload a firmware bundle OneView, online help, help, REST API Upload a firmware bundle Update the firmware repository on the appliance by uploading a firmware bundle, also known as a Service Pack for ProLiant SPP An SPP is a comprehensive update package of firmware, drivers, and utilities delivered as a single PXEbootable ISO image After the firmware bundle has been uploaded to the repository, it can be set as the firmware baseline for one device or across a set of devices Firmware baselines for servers are managed using server profiles, either by editing an existing server profile or by creating a new server profile to include a new service pack To manage firmware baselines for enclosures and interconnects, edit a device configuration directly Prerequisites Minimum required session ID privileges: Infrastructure administrator, Server administrator, or Network administrator Uploading a firmware bundle using REST APIs POST restfirmwarebundles See also  Quick Start: Initial configuration using REST APIs ";
f["157"]= " Update a logical interconnect Link Aggregation Control Protocol LACP timer OneView, online help, help, REST API Update a logical interconnect Link Aggregation Control Protocol LACP timer The LACP timer controls the frequency of the Link Aggregation Control Protocol Data Units LACPDU that are sent between the logical interconnect and the external switch to form a LAG Link Aggregation Group This timer can be set to the following: Short A message is sent every 1 second with a 3 second timeout Long A message is sent every 30 seconds with a 90 second timeout The long setting allows for situations such as preventing a timeout and loss of communication during an external switch firmware upgrade Prerequisites Minimum required session ID privileges: Infrastructure administrator Updating the Link Aggregation Control Protocol LACP in an uplink set using REST APIs Select a logical interconnect URI GET restlogicalinterconnects Get the logical interconnect using the URI from step 1 The associated logical interconnect group URI is returned in the response body GET restlogicalinterconnects id Get the logical interconnect group associated with logical interconnect The associated uplink sets URIs are returned in the response body GET restlogicalinterconnectgroups id Select an uplink set URI and update the LACP timer attribute  LacpTimer PUT restuplinksets id ";
f["158"]= " Change the default authentication login domain OneView, online help, help, REST API Change the default authentication login domain Initially, the default login domain is the local domain of user accounts Use this procedure to designate an authentication login domain as the default login domain If you added more than one authentication login domain, you can also use this procedure to select a different default login domain Prerequisites Minimum required session ID privileges: Infrastructure administrator At least one authentication directory service must be available on the appliance Changing the default authentication login domain using REST APIs Select a new default login domain URI GET restlogindomains Change the default login domain POST logindomainsglobalsettingsdefaultlogindomain NOTE: When you change the default login domain using this REST API, the new default login domain is displayed on the appliance UI log in screen ";
f["159"]= " About volumes storagevolumesall OneView, online help, help, REST API About volumes A volume represents a logical disk provisioned from a storage pool on a storage system You can attach volumes to one or more servers by configuring a volume attachment in the server profile The volume attachment manages volume presentation on the storage system  StoreServ port selection, host and vlun creation as well as SAN zoning on SANs with automatic zoning enabled that connect the server and storage system Using volume templates, you can create multiple volumes with the same configuration You can increase grow the capacity of a volume by editing it You cannot decrease the capacity of a volume ";
f["160"]= " Update a power delivery device OneView, online help, help, REST API Update a power delivery device To update a power delivery device, perform a PUT operation to reapply all of the power delivery device attributes View the power delivery device attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes Prerequisites Minimum required session ID privileges: Server administrator Updating a power delivery device using REST APIs Select the power delivery device URI GET restpowerdevices Get the power delivery device using the URI from step 1 GET restpowerdevices id Edit the power delivery device Update the power delivery device PUT restpowerdevices id ";
f["161"]= " Add a noniPDU power delivery device OneView, online help, help, REST API Add a noniPDU power delivery device Power delivery devices that the appliance cannot discover are considered unmanaged You must provide configuration information about them before the appliance can add and analyze them Entering configuration information about these unmanaged power delivery devices ensures more accurate analysis of power capacity, power consumption, and redundancy To add a description of a power delivery device that is not an iPDU under the appliance management, add the attributes manually Prerequisites Minimum required session ID privileges: Server administrator Adding a noniPDU power delivery device using REST APIs POST restpowerdevices ";
f["162"]= " Move a monitored c7000 enclosure to managed status OneView, online help, help, REST API Move a monitored c7000 enclosure to managed status Once a c7000 enclosure is monitored in the appliance, if you decide to change from monitored to managed, you must remove the enclosure from the appliance and then migrate or add it back as a managed enclosure, obtaining the appropriate license Migration would keep the configuration settings whereas add would not migrate the configuration Prerequisites Minimum required session ID privileges: Infrastructure Administrator Deleting a c7000 enclosure from appliance management using REST APIs Select an enclosure URI GET restenclosures Remove the enclosure using the URI from step 1 DELETE restenclosures id Do one of the following: To retain the enclosure configuration, see Migrate a c7000 VCM enclosure using REST API To add a new enclosure, including adding a new configuration, see Add an enclosure to manage its content NOTE: If the appliance cannot establish communication with an enclosure, you must forcibly remove the enclosure from the appliance This situation might occur if you physically remove the enclosure and it is offline DELETE restenclosures id&force=true ";
f["163"]= " About storage pools storagepoolsall OneView, online help, help, REST API About storage pools A storage pool is an aggregation of physical storage resources disks in a storage system Storage systems contain information about the storage ports through which they can be accessed You can provision logical storage spaces, known as volumes, from storage pools You can choose one or more storage pools when adding a storage system to the appliance Storage pools are created on a storage system using the management software for that system You cannot create or delete storage pools from the appliance—you can only add or remove them from management After you add storage pools, you can provision volumes on them ";
f["164"]= " Labels OneView, online help, help, REST API Labels Use REST APIs to  Add labels to a resource model Read labels Add or delete individual labels for a specific resource model Delete all labels for a specific resource model See more tasks Learn more About labels labels REST APIs ";
f["165"]= " Networks OneView, online help, help, REST API Networks Use REST APIs to  Create an Ethernet network Create multiple Ethernet networks using a single POST operation Create a Fibre Channel network Create an FCoE network Update a connection template Quick Start: Add an activeactive network configuration Quick Start: Migrate from an activestandby to an activeactive network configuration See more tasks Learn more About networks About Fibre Channel networks About Fibre Channel over Ethernet FCoE networks About Ethernet networks ethernetnetworks REST APIs fcnetworks REST APIs fcoenetworks REST APIs ";
f["166"]= " Attach a new volume to a server profile OneView, online help, help, REST API Attach a new volume to a server profile Prerequisites Minimum required session ID privileges: Server administrator Attaching a new volume to a server profile using REST APIs Obtain the hardware information: Get a list of available targets GET restserverprofilesavailabletargets For an assigned profile, note the fields serverHardwareUri, serverHardwareTypeUri, and enclosureGroupUri for the hardware target of interest For an unassigned profile, note the serverHardwareTypeUri and enclosureGroupUri for the hardware target of interest For an empty bay, note the fields serverHardwareTypeUri, enclosureGroupUri, enclosureUri, and enclosureBay Obtain the network information to create connections: Get a list of network connections GET restserverprofilesavailablenetworksserverHardwareTypeUri= uri&enclosureGroupUri= uri Insert serverHardwareTypeUri and enclosureGroupUri from step 1 Note the fields uri and limitedToPorts If manually selecting the storage targets, note which networks are fabric attach, as indicated via the accessType field Get available ports GET restserverprofilesprofileportsserverHardwareTypeUri= uri&enclosureGroupUri= uri Insert serverHardwareTypeUri and enclosureGroupUri from step 1 Note the fields portId, maximumLinkMbps, supportedFcGbps, and capabilities Obtain the SAN storage information: Determine the desired host OS enumeration GET reststoragesystemshosttypes Determine the available storage pools GET reststoragepools Note the fields storageSystemUri and uri Note the freeCapacity The volume you create must be smaller than that value If manually selecting the storage targets, obtain them GET storage system urimanagedPorts Note the fields portWwn, expectedNetworkUri, and actualNetworkUri Match the expectedNetworkUri with the uri field obtained in step 2a Create the server profile with the information from the previous steps POST restserverprofiles ";
f["167"]= " Delete an email recipient and filter OneView, online help, help, REST API Delete an email recipient and filter The procedure below accounts for situations in which: An email recipient might have more than one filter query A filter query might apply to more than one recipient A filter query and recipient pair might be no longer needed Deleting an email recipient and filter involves using a GET operation to return all the possible combinations of recipient and filter, isolating the combination you want to remove, and then performing a DELETE operation to remove it Prerequisites Required session ID privileges: Infrastructure administrator Deleting an email recipient and filter using REST APIs Perform a GET for the appliance email notifications: GET restappliancenotificationsemailconfig Remove the alert filter query and email address you want to delete Using the resource URI from step 1, reconfigure the appliance for email notifications: POST restappliancenotificationsemailconfig ";
f["168"]= " Network Sets OneView, online help, help, REST API Network Sets Use REST APIs to  Create a network set Create or delete a network in a network set Read a network set Update a network set Delete a network set See more tasks Learn more About network sets networksets REST APIs ";
f["169"]= " Support and other resources OneView, online help, help, REST API Support and other resources ";
f["170"]= " Storage Pools storagepoolsall OneView, online help, help, REST API Storage Pools I want to  Add a storage pool Remove a storage pool See more tasks Learn more About storage pools storagepools REST APIs storagesystems REST APIs ";
f["171"]= " Read the power utilization of a power device OneView, online help, help, REST API Read the power utilization of a power device Prerequisites Minimum required session ID privileges: Server administrator Reading a power device using REST APIs Select a power delivery device URI GET restpowerdevices Get the power delivery device utilization GET restpowerdevices idutilization Look at the array metricList to get the metric name and its associated metricSamples, metricCapacity, and allocation to get the utilization information ";
f["172"]= " Controlling access to the appliance console CONTACT CI DOC OWNERS before modifying this content CIC int, features, product description, reference, security, roles OneView, online help, help, REST API Controlling access to the appliance console Use the hypervisor management software to restrict access to the appliance, which prevents unauthorized users from accessing the password reset and service access features See Restricting console access Typical legitimate uses for access to the console are: Troubleshooting network configuration issues Resetting an appliance administrator password For information on how to reset the administrator password, see Reset the administrator password Enabling service access by an onsite authorized support representative The virtual appliance console is displayed in a graphical console; password reset and Hewlett Packard Enterprise Services access use a nongraphical console Switching from one console to another VMware vSphere and Microsoft HyperV Open the virtual appliance console Press and hold CtrlAlt Press and release the space bar VMware vSphere only Press and release F1 to select the nongraphical console or F2 to select the graphical console Switching from one console to another KVM Open the Virtual Machine Manager In the Menu bar, select Send Key→ CtrlAltF1 for the nongraphical console or select Send Key→ CtrlAltF2 for the graphical console Enable or disable authorized services access When you first start up the appliance, you can choose to enable or disable access by onsite authorized support representatives By default, onsite authorized support representatives are allowed to access your system through the appliance console and diagnose issues that you have reported Support access is a rootlevel shell, which enables the onsite authorized support representative to debug any problems on the appliance and obtain a onetime password using a challengeresponse mechanism similar to the one for a password reset Any time after the initial configuration of the appliance, an Infrastructure administrator can enable or disable services access through the UI with the following procedure: Prerequisites  Minimum required privileges: Infrastructure administrator Enabling or disabling authorized services access From the main menu, select Settings Click the Edit icon in the Security panel The Edit Security window opens Select the appropriate setting for Service console access: Disabled to prevent access to the console Enabled to allow access to the console Click OK You can also use an appliancesettings REST API to enable or disable services access NOTE: Hewlett Packard Enterprise recommends that you enable access Otherwise, the authorized support representative will not be able to access the appliance to correct troubleshoot issues Restricting console access You can restrict console access to the virtual appliance through secure management practices of the hypervisor itself For VMware vSphere, this information is available from the VMware website: http:wwwvmwarecom In particular, search for topics related to vSphere's Console Interaction privilege and best practices for managing VMware's roles and permissions For Microsoft HyperV, restrict access to the console through rolebased access For information, see the Microsoft website: http:wwwmicrosoftcom ";
f["173"]= " Update a local user password OneView, online help, help, REST API Update a local user password To update a user password, perform a PUT operation to reapply all of the user account attributes View the user account attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes Prerequisites Minimum required session ID privileges: Infrastructure administrator Updating a local user password using REST APIs Select the user name GET restusers Using the user name from step 1, get the user information GET restusers userName Update the user password PUT restusers ";
f["174"]= " Enable or disable local logins OneView, online help, help, REST API Enable or disable local logins The appliance is configured to allow local logins by default If you disabled local logins so that you could use an authentication directory service exclusively, use this procedure to allow local logins Prerequisites Minimum required session ID privileges: Infrastructure administrator Enabling or disabling local logins using REST APIs Get the current status of local login GET restlogindomainsglobalsettingsallowlocallogin Enable or disable local logins POST restlogindomainsglobalsettingsallowlocallogin ";
f["175"]= " Firmware OneView, online help, help, REST API Firmware Use REST APIs to  Delete a firmware bundle from the firmware repository Install a firmware bundle using a server profile Read the firmware repository for firmware bundles Update enclosure firmware Upload a firmware bundle Upload a hotfix Update logical interconnect firmware Update the interconnect firmware for HPE Virtual Connect Fibre Channel interconnects See more tasks Learn more About firmware bundles About unsupported firmware firmwarebundles REST APIs firmwaredrivers REST APIs ";
f["176"]= " Read utilization for a specific enclosure OneView, online help, help, REST API Read utilization for a specific enclosure You can view historical data for enclosure utilization, such as average power and average peak power, for the last 24 hours NOTE: The following parameters are available only for c7000 enclosures: PowerCap DeratedCapacity RatedCapacity Prerequisites Minimum required session ID privileges: Server administrator Reading utilization for a specific enclosure using REST APIs Select an enclosure URI GET restenclosures Get utilization for a specific enclosure GET restenclosures idutilization ";
f["177"]= " Update a storage volume template storagevolumetemplatesall OneView, online help, help, REST API Update a storage volume template To update a storage volume template, perform a PUT operation to reapply all of the storage volume template attributes View the storage volume template attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator Updating a storage volume template using REST APIs Select the storage volume template URI GET reststoragevolumetemplates Get the storage volume template using the URI from step 1 GET reststoragevolumetemplates id Edit the storage volume template Update the storage volume template PUT reststoragevolumetemplates id ";
f["178"]= " Fabrics OneView, online help, help, REST API Fabrics Use REST APIs to  Read a fabric Learn more About fabrics fabrics REST APIs ";
f["179"]= " Read a fabric OneView, online help, help, REST API Read a fabric Retrieve the fabric URI Prerequisites Minimum required session ID privileges: Network administrator Read a fabric using REST APIs Select a fabric URI GET https:appliancerestfabrics Read the fabric GET https:appliancerestfabricsid ";
f["180"]= " About networks OneView, online help, help, REST API About networks The HPE Virtual Connect interconnects in enclosures support the following types of data center networks: Fibre Channel for storage networks, including fabricattach SAN Fibre Channel FC connections and directattach Flat SAN Fibre Channel connections Ethernet for data networks, including tagged, untagged, or tunnel networks Fibre Channel over Ethernet FCoE for storage networks where storage traffic is carried over a dedicated Ethernet VLAN IMPORTANT: The networking features described in this section apply to enclosures and servers only The appliance does not monitor or manage the network features and hardware for rack mount servers or networking equipment outside the enclosures About creating networks Before creating networks, be aware of the networking maximums See the HPE OneView Support Matrix for more information Before you create a connection in a server profile, you must: Create at least one network Add the network to a logical interconnect group Assign the network to internal networks or an uplink set You can create networks before you add an enclosure, which is known as preprovisioning About provisioning networks An Ethernet network is provisioned to an interconnect when the network is associated with an uplink set or internal networks in a logical interconnect An FC or FCoE network is provisioned to an interconnect when the network is associated with an uplink set in a logical interconnect An Ethernet and FCoE network must be provisioned to a logical interconnect and be consistent with the logical interconnect group to be deployed in a server profile connection ";
f["181"]= " Quick Start: Migrate from an activestandby to an activeactive network configuration OneView, online help, help, REST API Quick Start: Migrate from an activestandby to an activeactive network configuration This quick start describes the process of migrating from an existing activestandby configuration to an activeactive configuration for an enclosure Prerequisites Minimum required session ID privileges: Infrastructure administrator or Network administrator to add the network Minimum required session ID privileges: Infrastructure administrator or Server administrator to change the server profile configurations Two or more fully supported Virtual Connect interconnect modules as listed in the HPE OneView Support Matrix The enclosures and server blades are already added to the appliance Follow recommended naming conventions described in Requirements for an activeactive configuration Migrating from an activestandby to an activeactive configuration For an enclosure group with a single logical interconnect group, when migrating from an activestandby configuration to an activeactive configuration, make configuration changes to the following resources: Resource Task Description Logical Interconnect Groups Find the uplink set or sets that you want to convert to activeactive Record all networks in the uplink sets For more information, see Logical Interconnect Groups Networks Rename the networks by adding <side> to the network name, as described in Requirements for an activeactive configuration for example, Dev_100_A Create Ethernet networks using the same external VLAN ID for each network renamed in step 3 for example, Dev_100_B For the vlanId attribute, enter the same ID as those in the original uplink set Set the smartLink attribute to true For more information, see Networks or Network Sets Network Sets Optional Add network sets for the networks created in step 4 Adding a network to a network set does not require that you take resources offline You do not need to update server profiles that have connections to the network set Duplicate VLAN IDs are not allowed in a network set For more information, see Network Sets Logical Interconnect Groups and Logical Interconnects Determine if all logical interconnects have active and standby uplink ports on the same modules If the standby uplinks are on the same module, go to step 7 If the standby uplinks are on different modules, force a failover so that all standby uplinks are on the same module Go to step 7 Edit the activestandby uplink set and delete the standby uplinks Create a second uplink set for the standby uplinks removed in step 7 Add the networks created in step 4 to the new uplink set For example, UplinkSet_B contains all Dev_B networks Update the logical interconnect To determine the port status active or standby, perform a GET restinterconnectsidports operation on the interconnect and review the portStatus of each uplink port  portType:Uplink Hewlett Packard Enterprise recommends deleting the standby uplinks from the original uplink set, and then adding them to the new uplink set This method prevents connectivity loss For more information, see the online help for Logical Interconnects Server Profiles and Server Hardware Power off the server before you edit the server profile Edit the server profile to add a connection for the new networks or network sets Power on the server Change every server profile connection associated with the port servicing the original standby uplinks Assign the new networks or network sets created in steps 4 or 5 to the port For more information, see Server Profiles Logical Interconnect Groups and Logical Interconnects Edit the logical interconnect group and rename the original uplink set by adding <side> to the name, as described in Requirements for an activeactive configuration for example, UplinkSet_A Do not make any changes other than the uplink set name For more information, see the online help for Logical Interconnects ";
f["182"]= " About unmanaged and unsupported c7000 enclosures OneView, online help, help, REST API About unmanaged and unsupported c7000 enclosures Unmanaged enclosures An unmanaged enclosure is one that is not currently managed or monitored by HPE OneView See About unmanaged devices to learn more about unmanaged devices Unsupported enclosures An unsupported enclosure cannot be managed by HPE OneView However, you can place unsupported enclosures in racks Adding unsupported enclosures to HPE OneView enables you to account for the physical space the enclosure occupies in a rack for planning and inventory purposes If you have an enclosure with G6 ProLiant server blades, consider adding the enclosure as monitored instead of unsupported See About monitored c7000 enclosures ProLiant G7 or later server blades can be managed in HPE OneView See About managed c7000 enclosures HPE OneView displays basic information about unsupported enclosures, such as the model name, Onboard Administrator name, and the number of OAs in the enclosure You can specify the maximum power for the unsupported enclosure, which allows you to define its power capacity and enables HPE OneView to generate alerts when maximum capacity is reached ";
f["183"]= " List all scopes CONTACT CI DOC OWNERS before modifying this content OneView, online help, help, REST API List all scopes Use this procedure to obtain a list of all defined scopes Listing all scopes using REST APIs List all scopes: GET restscopes ";
f["184"]= " About migrating c7000 enclosures managed by other management systems OneView, online help, help, REST API About migrating c7000 enclosures managed by other management systems Enclosures managed by VCM Virtual Connect Manager or VCEM Virtual Connect Enterprise Manager can be migrated into HPE OneView Migration recreates the configuration information for an enclosure including hardware, Virtual Connect domain, networks, and server profiles including MAC addresses and WWNs in the profile connections Up to four single enclosure domains managed by VCM can be migrated simultaneously to HPE OneView through the UI or REST API VCEMmanaged enclosures can be prepared for migration to HPE OneView through the VCEM GUI or a PowerShell module See Prepare a VCEM enclosure for migration into HPE OneView for more information NOTE: HPE OneView does not support G6 server blades for migration or management You can replace the G6 server blades with a G7 or later blade, or you can monitor the enclosure See About monitored c7000 enclosures When you add an enclosure to be migrated, you can specify an enclosure group or create a new enclosure group See About managed c7000 enclosures More information About offline or inservice migration About migrating partially stacked domains About VCM settings that will not be migrated Before migrating c7000 enclosures About blocking issues during migration About migration acknowledgments About offline or inservice migration You can migrate enclosures into HPE OneView offline or inservice Offline Servers are powered off before migration Advantages: Faster migration time and partiallystacked domain support Inservice Servers remain powered on during migration Advantage: Minimum downtime in server connectivity Both types of migration require that: All blocking issues, as identified in the compatibility report, are resolved All acknowledgements are understood and accepted, including additional acknowledgments for inservice migration for example, BIOS and SRIOV In addition, inservice migration requires: A fully stacked enclosure in a dual ring or leftright vertical stacking link configuration See recommended stacking connections in the HPE Virtual Connect for cClass BladeSystem Setup and Installation Guide NOTE: Changes made during inservice migration do not take effect until the server is rebooted for the first time following the migration Plan a reboot if one of the acknowledgements, such as an SRIOV virtual function configuration, indicated a change which would impact your operation If the additional inservice migration conditions cannot be met, an offline migration is recommended More information About blocking issues during migration About migration acknowledgments About migrating partially stacked domains In Virtual Connect Manager, three types of Ethernet stacking configurations are supported and can be migrated into HPE OneView: Full Every Ethernet interconnect has a path to all other Ethernet interconnects Full stacking is the default mode This configuration is migrated into HPE OneView with all Ethernet and Fibre Channel interconnects in one logical interconnect group This configuration can be migrated inservice or offline See Full stacking migration from Virtual Connect Manager to HPE OneView Primaryslice Stacking occurs only between the primary and standby Ethernet interconnects within the domain This configuration is migrated into HPE OneView with the primary and secondary interconnects configured within one logical interconnect group All other Ethernet interconnects are configured in their own logical interconnect group with one Ethernet interconnect per logical interconnect group Fibre Channel interconnects are configured together in a separate logical interconnect group This configuration must be migrated offline See Primaryslice stacking migration from Virtual Connect Manager to HPE OneView Horizontal Stacking occurs between each horizontal Ethernet interconnect pair This configuration is migrated into HPE OneView with all horizontallyadjacent interconnects configured into one logical interconnect group If there is no horizontallyadjacent interconnect present, when migrated, the corresponding logical interconnect group contains only a single Ethernet interconnect This configuration must be migrated offline Fibre Channel interconnects are configured together in a separate logical interconnect group See Horizontal stacking migration from Virtual Connect Manager to HPE OneView Full stacking migration from Virtual Connect Manager to HPE OneView Primaryslice stacking migration from Virtual Connect Manager to HPE OneView Horizontal stacking migration from Virtual Connect Manager to HPE OneView You migrate a VCMmanaged enclosure into a new or existing enclosure group New enclosure group — the logical interconnect groups are created based on the Virtual Connect stacking configuration The networks and uplink sets are copied to the newly created logical interconnect groups For horizontal or primaryslice: Ethernet networks are copied to all logical interconnect groups containing Ethernet interconnects Uplink sets are copied to all logical interconnect groups Uplink set ports are copied only to the created uplink set within the logical interconnect groups containing those ports All Ethernet settings such as QoS are migrated to the newly configured Ethernet logical interconnect groups FCoE networks are added to the uplink set created in the logical interconnect group containing the associated uplink set ports Virtual Connect fabrics are copied as Fibre Channel uplink sets within the logical interconnect group containing the fabric uplink ports An associated Fibre Channel network is also created SNMP configurations are migrated to all the logical interconnect groups, including the Fibre Channel logical interconnect group Existing enclosure group — the existing HPE OneView logical interconnect groups must match the exact bay and interconnect type of the Virtual Connect configuration Otherwise, a compatibility error occurs and the migration is blocked For example, if a VCMmanaged enclosure is Primaryslice and bays 1, 2, 3, and 4 are populated with HPE Virtual Connect FlexFabric 10Gb24–Port Modules, an error occurs if HPE OneView does not have a matching enclosure group with the logical interconnect groups defined with the same interconnect type HPE Virtual Connect FlexFabric 10Gb24–Port Module for all four bays In addition, bays 1 and 2 must be configured together in one logical interconnect group and bays 3 and 4 must be configured into two separate logical interconnect groups as seen in Primaryslice stacking migration from Virtual Connect Manager to HPE OneView The attributes applied to the logical interconnect groups such as uplink sets, Ethernet settings, and SNMP configurations must also match or errors can occur More information About blocking issues during migration Migrate a c7000 VCM enclosure using REST API About VCM settings that will not be migrated The following VCM settings will not be migrated into HPE OneView User account specific information such as certificates, user accounts, LDAP, RADIUS, TACACS, session timeout, and user role configurations Port monitoring configuration After migration, port monitoring can be configured separately on each logical interconnect See Configure a port to monitor network traffic in the online help for more information Address pools of MACs, WWNs, and serial numbers defined in VCM HPE OneView migrates the MACs, WWNs, and serial numbers that are part of assigned profiles NOTE: Any new addresses allocated in HPE OneView after the migration are pulled from the HPE OneView address pools An administrator can manually define custom ranges in HPE OneView to match those that were defined in VCM to continue allocating from that range Before migrating c7000 enclosures Before you start the migration process, plan the migration See “Planning for enclosure migration from VCM into HPE OneView” in the HPE OneView User Guide to make sure certain requirements, such as backing up the VCM configuration, are met The migration process is illustrated by the following figure Migration process See planning your migration in the HPE OneView User Guide for tips on preparing your configuration for migration Automated functions Once the compatibility issues have been addressed and the migration takes place, HPE OneView validates the configuration information and then automatically performs the following functions: Creates networks and network sets Creates a Logical Interconnect Group or uses an existing group Creates an Enclosure Group or uses an existing group Creates server profiles unassigned to servers but associated to server hardware types The newly created HPE OneView server profiles retain the same MACs and WWNs used in the corresponding VCM server profiles Imports the enclosure and adds physical resources such as interconnects and servers Assigns server profiles For inservice migration, interconnects are reconfigured sequentially during the migration, overwriting the VCM configuration with the HPE OneView configuration With a redundant configuration, HPE OneView detects the loss of connectivity for an interconnect and redirects traffic to the alternate path At the end of the migration, the Virtual Connect domain is no longer available in VCM To migrate an enclosure, see Migrate a c7000 VCM enclosure using REST API About c7000 migration and firmware Before migrating the enclosure, make sure the firmware is at the required minimum See the HPE OneView Support Matrix for more information When migrating enclosures, the firmware baseline is automatically set to manage manually The firmware settings in VCM are migrated to HPE OneView HPE OneView does not allow firmware updates during the enclosure migration process Once the enclosure is migrated to HPE OneView, you can update the firmware See Best practices for firmware and Update firmware for enclosures in the UI help for more information About blocking issues during migration The following partial list of Virtual Connect features are considered blocking issues because they are not supported in HPE OneView Blocking issues can also result when settings conflict between the Virtual Connect domain and the HPE OneView logical interconnect group into which the domain is being migrated HPE OneView checks for these features and blocks the migration when these issues are found Resolving an issue might require disabling a feature within Virtual Connect, changing a configuration in Virtual Connect, or in some cases, changing the HPE OneView logical interconnect group If a feature is required in your environment and your enclosure contains ProLiant G6 or later server blades, you might want to consider monitoring your enclosure See About monitored c7000 enclosures NOTE: VCEMmanaged enclosures can be migrated to HPE OneView  See About migrating c7000 enclosures managed by other management systems for more information Blocking issues Advanced SRIOV  a Autodeployment c3000 enclosures, ProLiant G1 through G6 server blades , Integrity blades and Storage server blades Ethernet, iSCSI, and FCoE connection speed type disabled Federal Information Processing Standard FIPS 140–2 IGMP multicast filters and filter sets More than 1000 networks defined within the VC domain Multiple enclosure stacked domains Partially stacked domains  b Server VLANs mapped to alternate network VLANs SNMP v3 Storage management credentials Unassigned Ethernet, iSCSI, or FCoE network connections  b Unsupported Fibre Channel speeds  b VCEM multiple FC initiators  a Blocking issue for mixing automatic and nonautomatic settings for inservice migration However, for offline migration, settings are set to default virtual functions are evenly spread across all physical functions  b Blocking issue for inservice migration only NOTE: In general, for functions that are not required in your environment, disabling the function in VCM enables you to migrate the enclosure About unassigned VCM server profile connections during migration An unassigned VCM server profile connection is a connection without a specified network or fabric There are five types of connections within VCM Ethernet — One or more Ethernet networks assigned to the same server profile connection FCoE — An FCoE network associated with an uplink set Ethernet and FCoE networks may share the same uplink set FCoE FC SAN — An FCoE connection assigned to a SAN fabric These connections have one or more native Fibre Channel connections to the uplink ports which are part of the SAN fabric They utilize FlexFabric physical function 2 of the adapter Native Fibre Channel — A native Fibre Channel adapter connection to a Fibre Channel interconnect iSCSI — An iSCSI, Ethernet network or unshared iSCSI network that is associated with an uplink set Ethernet and iSCSI networks may share the same uplink set HPE OneView does not support unassigned server profile connections, so the connections are not migrated and cannot be recreated for the migrated server profile For native Fibre Channel connections, a warning issue appears on the compatibility report For all other connections, a blocking issue appears on the compatibility report for inservice migrations To determine how to resolve unassigned server profile connections depends on the reason for the unassigned connection and the ramifications to the OS configuration if the connection is not migrated More information “Unassigned server profile connections cannot be migrated” in the Troubleshooting section of the online help About blocking issues during migration Migrate a c7000 VCM enclosure using REST API About migration acknowledgments Some issues that are not considered blocking or warning issues for VCM migration are shown as acknowledgments Some acknowledgements do relate to warnings in the compatibility report In either case, acknowledgments are important instructions that must be followed and acknowledged before the migration can begin Acknowledgments display in the UI after all blocking issues are resolved and a final compatibility report is generated In the REST API, the acknowledgments are returned in the acknowledgements attribute For specific acknowledgements, see the following: VCM configuration backup acknowledgment Resource modification acknowledgment Redundant hardware and software configuration acknowledgment for inservice migration BIOS acknowledgment for inservice migration SRIOV acknowledgment for inservice migration Server profile acknowledgment VCM configuration backup acknowledgment Verify a backup of the VCM configuration including the output from show config includepoolinfo has been obtained and is secured where it will be available in the event that the enclosure migration is unsuccessful The backup is used if the VCM configuration must be reverted back to Virtual Connect Manager control The VCM configuration backup can be created through the VCM web UI or the VCMCLI More information Virtual Connect User Guide at http:wwwhpecominfovirtualconnectdocs Migrate a c7000 VCM enclosure using REST API About migration acknowledgments Resource modification acknowledgment Although HPE OneView is fully operational during a migration, do not modify HPE OneView resources until the migration is complete IMPORTANT: Modifying HPE OneView resources can cause the migration to fail, leaving the enclosure unconfigured and requiring recovery before it can be made operational The migration is complete when the task in the HPE OneView Activities screen shows migration complete For example, do not edit networks, network sets, logical enclosures, logical interconnect groups, or server profiles for the enclosures involved in the migration Do not perform other maintenance activities such as server power, appliance restart, or firmware update during the migration process More information Migrate a c7000 VCM enclosure using REST API About migration acknowledgments Redundant hardware and software configuration acknowledgment for inservice migration To minimize the impact to applications and services during an HPE OneView inservice migration, redundant hardware and software configurations are required The fully stacked enclosure must be configured in a dual ring or leftright vertical stacking link configuration See recommended stacking connections in the HPE Virtual Connect for cClass BladeSystem Setup and Installation Guide Interconnects are reconfigured sequentially during the migration, overwriting the VCM configuration with the HPE OneView configuration At most, storage is disrupted for a single interconnect at any point during the migration and network traffic is disrupted for the even or odd numbered bays at any point during the migration Configure redundant network and storage connections and provide failover such as network interface bonding and MPIO drivers so that network and storage traffic continues to pass on one module of the pair while the other module is reconfigured As in a logical interconnect firmware update, the server operating system detects the loss of connectivity for the interconnect module and redirects traffic to the alternate path More information Migrate a c7000 VCM enclosure using REST API About migration acknowledgments BIOS acknowledgment for inservice migration In Virtual Connect Manager, administrators can configure specific boot settings such as PXE or SAN boot for profile connections while leaving the default USEBIOS setting in place on other connections in the same profile After inservice migration, the server continues to boot based on the configured boot settings However, the first time the server is rebooted after inservice migration, any connection on the profile configured to USEBIOS is converted to not bootable to match HPE OneView conventions More information Migrate a c7000 VCM enclosure using REST API About migration acknowledgments SRIOV acknowledgment for inservice migration In VCM, administrators can specify the distribution of SRIOV Single Root IO Virtualization virtual functions across the FlexNICs in server profiles HPE OneView distributes virtual functions evenly across all the FlexNICs in the server profile When the SRIOV connection setting in the Virtual Connect domain is default, VCM assigns all SRIOV virtual functions to the third FlexNIC on the port When migrating from VCM to HPE OneView, this redistribution takes effect the first time the server is rebooted after the migration to HPE OneView The redistribution causes the server to reenumerate PCI devices, which can disrupt server network traffic, as a result of the new device ordering Review and revise the network configuration of hypervisors and guest virtual machines in the host OS, if needed, to avoid disrupting their network connectivity More information Migrate a c7000 VCM enclosure using REST API About migration acknowledgments Server profile acknowledgment Virtual Connect server profiles that are not assigned to server hardware are not migrated to HPE OneView To migrate these server profiles: Assign them to server hardware, if available Manually recreate the server profiles in HPE OneView after migration See Perform postmigration tasks More information Create a server profile Migrate a c7000 VCM enclosure using REST API About migration acknowledgments ";
f["185"]= " Install a firmware bundle using a server profile OneView, online help, help, REST API Install a firmware bundle using a server profile After you upload a firmware bundle SPP to the appliance, use a server profile to install it on server hardware See Create a server profile and Update a server profile for more information NOTE: You can downgrade or reinstall the firmware using a force upgrade When you set the forceInstallFirmware attribute to false, the firmware bundle that you select is applied regardless of what version is installed on the server hardware ";
f["186"]= " Accessing updates This module describes how to access product updates and alerts OneView, online help, help, REST API Accessing updates Some software products provide a mechanism for accessing software updates through the product interface Review your product documentation to identify the recommended software update method To download product updates, go to either of the following: Hewlett Packard Enterprise Support Center Get connected with updates page: wwwhpecomsupporteupdates Software Depot website: wwwhpecomsupportsoftwaredepot To view and update your entitlements, and to link your contracts and warranties with your profile, go to the Hewlett Packard Enterprise Support Center More Information on Access to Support Materials page: wwwhpecomsupportAccessToSupportMaterials IMPORTANT: Access to some updates might require product entitlement when accessed through the Hewlett Packard Enterprise Support Center You must have an HP Passport set up with relevant entitlements ";
f["187"]= " About the Virtual Connect FlexFabric–2040 F8 interconnect module OneView, online help, help, REST API About the Virtual Connect FlexFabric–2040 F8 interconnect module The Virtual Connect FlexFabric–2040 F8 Module for HPE BladeSystem cClass has several unique features For more information, see the HPE Virtual Connect FlexFabric–2040 F8 Module for HPE BladeSystem cClass Installation Instructions at http:wwwhpecominfoqs Enclosure requirements CAUTION: To avoid overheating: Make sure there are 10 fans in the enclosure Do not insert more than six Virtual Connect FlexFabric–2040 F8 modules in one enclosure ";
f["188"]= " Storage Systems storagesystemsall OneView, online help, help, REST API Storage Systems I want to  Add a storage system See more tasks Learn more About storage systems storagesystems REST APIs ";
f["189"]= " Read a rack server OneView, online help, help, REST API Read a rack server Prerequisites Minimum required session ID privileges: Server administrator Reading a rack server using REST APIs Select a rack server URI GET restserverhardware Read the rack server GET restserverhardware id ";
f["190"]= " About scopes CONTACT CI DOC OWNERS before modifying this content OneView, online help, help, REST API About scopes A scope is a grouping of resources that can be used to restrict the range of an operation or action For example, you can create scopes based on: Organizations Marketing, Research and Development, Finance Usage Production, Development, Testing Skills Linux, Windows The resources are arranged by categories All the resources in these categories can be added to or removed from a scope: Enclosures Server Hardware Networks Ethernet, FC, and FCoE Network Sets Interconnects, excluding SAS resources Logical Interconnects, excluding SAS resources Logical Interconnect Groups, excluding SAS resources Switches Logical Switches Logical Switch Groups NOTE: Resources in other categories are considered to be included in all scopes, and they cannot be removed When scopes are defined and resources assigned to them, you can: Restrict your view of the user interface UI to the resources in the scope Filter email notifications for alerts based on the scope of the associated resources More information NOTE: Scope APIs are subject to incompatible changes, including redefinition or removal, in future releases List all scopes List information about a specific scope Create a scope Modify a scope definition Change scope resource assignments Delete a scope ";
f["191"]= " Create a scope CONTACT CI DOC OWNERS before modifying this content OneView, online help, help, REST API Create a scope Use this procedure to create a scope, and to define its name and description Creating a scope using REST APIs Create the scope: POST restscopes More information List all scopes List information about a specific scope Change scope resource assignments ";
f["192"]= " Read a power device OneView, online help, help, REST API Read a power device Prerequisites Minimum required session ID privileges: Server administrator Reading a power device using REST APIs Select a power delivery device URI GET restpowerdevices Get the power delivery device GET restpowerdevices id ";
f["193"]= " Create and download a logical interconnect MAC address table file OneView, online help, help, REST API Create and download a logical interconnect MAC address table file The MAC address table file can be used to troubleshoot your network The file includes information to help you identify the associated networks, uplink sets, and server profiles First, you create the logical interconnect MAC address file on the appliance, and then download the CSV zip file When you initiate a POST operation to create the file, the existing MAC address table file is replaced Prerequisites Minimum required session ID privileges: Infrastructure administrator or Network administrator Creating and download a logical interconnect MAC address table file using REST APIs Select the logical interconnect URI GET restlogicalinterconnects Using the logical interconnect URI from step 1, create the logical interconnect MAC address table file The response includes the file URI POST logical interconnect URIforwardinginformationbase Using the MAC address table file URI returned in step 2, download the logical interconnect MAC address table file GET MAC address table file URI ";
f["194"]= " Create a server profile with userspecified IDs OneView, online help, help, REST API Create a server profile with userspecified IDs Use userspecified IDs to migrate server profiles from HPE Virtual Connect or HPE Virtual Connect Enterprise Manager to HPE OneView, or to recreate an accidentallydeleted server profile with SAN storage If you are recreating a deleted server profile that uses SAN storage, first create an unassigned server profile, then copy the virtual IDs that you need from that profile, and then delete the profile to release the IDs for use in your recreated server profile To retain storage provisioning, you must use the WWPN from the original server profile This WWPN is in the storage array volume export Prerequisites Minimum required session ID privileges: Server administrator A managed enclosure that includes a server blade without a server profile If you are recreating an accidentallydeleted server profile with SAN storage: WWPN that storage is exported to that should exist in the storage array volume export WWNN: any WWN not currently in use—typically WWPN  1 MAC: any virtual MAC address not currently in use TIP: You can obtain a free MAC address by creating an unassigned profile with a virtual MAC address, copy the MAC address, and then delete the profile Create an unassigned server profile, note the virtual IDs, and delete the unassigned server profile to release the IDs for use in your recreated server profile See Create an unassigned server profile to use as a template If you are migrating server profiles from HPE Virtual Connect or HPE Virtual Connect Enterprise Manager, you need the IDs used in those server profiles Creating a server profile with userspecified IDs using REST APIs Get a server hardware URI GET restserverprofilesservers Select the BIOS settings for the server hardware using the associated server hardware type URI GET restserverhardwaretypes id Get available server ports using the server hardware type URI and enclosure group URI associated with the server hardware GET restserverprofilesprofileportsserverHardwareTypeUri= uri&enclosureGroupUri= uri Select the network URIs for the server profile connections using the server hardware type URI and the enclosure group URI GET restserverprofilesavailablenetworksserverHardwareTypeUri= uri&enclosureGroupUri= uri Select the firmware URI to apply GET restfirmwaredrivers Create the server profile with the information from the previous steps During this step you can specify the boot order and BIOS settings and add the userspecified IDs Serial number serialNumberType:UserDefined serialNumber:serial number not in use or serial number transferred from VCVCEM Ethernet connection macType:UserDefined macAddress:virtual mac address not in use or virtual mac address transferred from VCVCEM Fibre Channel connection wwpnType:UserDefined wwpn:virtual wwpn not in use, wwpn from accidentallydeleted profile with SAN storage, or wwpn transferred from VCVCEM wwnn:virtual wwnn not in use, wwnn from accidentallydeleted profile with SAN storage, or wwnn transferred from VCVCEM macType:UserDefined macAddress:virtual mac address not in use or virtual mac address transferred from VCVCEM  POST restserverprofiles ";
f["195"]= " Create or delete a network in a network set OneView, online help, help, REST API Create or delete a network in a network set See Update a network set ";
f["196"]= " Create an FCoE network OneView, online help, help, REST API Create an FCoE network When you create an FCoE network, a connection template is automatically created A connection template defines the connection settings for the FCoE network The settings include maximum and minimum allowable bandwidth Prerequisites Minimum required session ID privileges: Network administrator Creating an FCoE network using REST APIs POST restfcoenetworks NOTE: The connectionTemplateUri attribute must be set to null See also  Quick Start: Initial configuration using REST APIs top of chapter ";
f["197"]= " Activity OneView, online help, help, REST API Activity Use REST APIs to  Assign an owner to an alert Download audit logs Filter alerts by health and status Read alerts for a physical resource type Read the status of a task Update an alert See more tasks Learn more About activities alerts REST APIs ";
f["198"]= " Create a storage volume storagevolumesall OneView, online help, help, REST API Create a storage volume You can create a storage volume with or without a storage volume template If you do not specify a storage volume template, you must specify the storage volume provisioning attributes Before you create a storage volume, you select a storage system and associated storage pool After you create a storage volume, you can add it to a server profile Prerequisites Minimum required session ID privileges: Infrastructure administrator or Storage administrator You have added at least one storage system You have added at least one storage pool Creating a storage volume with a storage volume template using REST APIs Select a storage system URI GET reststoragesystems Select a storage volume template GET reststoragevolumetemplates Create the storage volume with the information from the previous steps POST reststoragevolumes Creating a storage volume without a storage template using REST APIs Select a storage system URI GET reststoragesystems Select a storage pool from the storage system URI you selected in step 1 GET storage system URIstoragepools Create the storage volume with the information from the previous steps POST reststoragevolumes ";
f["199"]= " List information about a specific scope CONTACT CI DOC OWNERS before modifying this content OneView, online help, help, REST API List information about a specific scope Listing information about a specific scope using REST APIs Retrieve the information for a scope: GET restscopesid ";
f["200"]= " Create a certificate signing request OneView, online help, help, REST API Create a certificate signing request The appliance uses a certificate for authentication over SSL The certificate contains a public key, and the appliance maintains the corresponding private key, which is uniquely tied to the public key A certificate authority CA is a trusted party that issues a certificate that enables others, who trust the CA, to also trust the host In essence, the CA vouches for the host Obtaining a CAauthenticated certificate Create a certificate signing request Send the certificate signing request to the CA The CA designates how and where to send the request The CA authenticates the requester Import the certificate Prerequisites Minimum required session ID privileges: Infrastructure administrator Required attributes: Country State or province City or locality Organization name Common name fully qualified host name of the appliance Certificate authority challenge password Certificate authority unstructured name Creating a certificate signing request using REST APIs POST restcertificateshttpscertificaterequest Next step: After you receive the certificate from the CA, import the certificate See Import a certificate ";
f["201"]= " About data centers OneView, online help, help, REST API About data centers A data center represents a physically contiguous area in which racks containing IT equipment are located For example, you have IT equipment in two rooms or on separate floors You could create a data center for each of these areas Each server, enclosure, or power distribution device in your data center can report its power requirements, but it can be difficult to understand the power and cooling requirements for your data center as a whole The appliance enables you to bring power and cooling management of your servers, enclosures, and power delivery devices together in a single management system When you initialize the appliance for the first time, it creates a data center named Datacenter 1 You can rename or edit this data center to match the values and layout of your data center, you can use it as the basis for a planned data center model, or you can delete this data center without adverse effects Default rack placement When you add a rack to the appliance for management, the rack is displayed in all data centers even though its actual location is not known When you assign a rack to a data center, it is no longer displayed in other data centers ";
f["202"]= " Connectivity and synchronization with HPE OneView OneView, online help, help, REST API Connectivity and synchronization with HPE OneView HPE OneView monitors the connectivity status of enclosures If HPE OneView loses connectivity with an enclosure, a notification is displayed until connectivity is restored HPE OneView attempts to resolve connectivity issues and clears the alert automatically, but if it is unsuccessful, you must resolve the issue and manually refresh the enclosure to synchronize it HPE OneView also makes sure the enclosures are synchronized with changes to hardware and configuration settings However, some changes to enclosures made outside of HPE OneView from OA, for example might cause the enclosure to lose synchronization You might have to manually refresh an enclosure that lose synchronization with HPE OneView You can manually synchronize an enclosure with HPE OneView by refreshing the enclosure from the Enclosures screen Refreshing an enclosure will refresh all devices in it See the online help for the Enclosures screen to learn more See also  About enclosures Enclosures ";
f["203"]= " Protecting credentials CIC int, features, product description, reference, security, roles OneView, online help, help, REST API Protecting credentials Local user account passwords are stored using a salted hash; that is, they are combined with a random string, and then the combined value is stored as a hash A hash is a oneway algorithm that maps a string to a unique value so that the original string cannot be retrieved from the hash Passwords are masked in the browser When transmitted between appliance and the browser over the network, passwords are protected by SSL Local user account passwords must be a minimum of eight characters, with at least one uppercase character The appliance does not enforce additional password complexity rules Password strength and expiration are dictated by the site security policy see Best practices for maintaining a secure appliance If you integrate an external authentication directory service also known as an enterprise directory with the appliance, the directory service enforces password strength and expiration ";
f["204"]= " Update logical interconnect group SNMP settings OneView, online help, help, REST API Update logical interconnect group SNMP settings To update logical interconnect group SNMP settings, perform a PUT operation to reapply all of the logical interconnect group SNMP settings attributes View the logical interconnect group SNMP settings attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes Prerequisites Minimum required session ID privileges: Infrastructure administrator Update logical interconnect group SNMP settings using REST APIs Select logical interconnect group URI GET restlogicalinterconnectgroups Get the logical interconnect group using the URI from step 1 GET restlogicalinterconnectgroups id Edit the attribute values in the snmpConfiguration property Update the logical interconnect group PUT restlogicalinterconnectgroups id NOTE: When you update the logical interconnect group SNMP settings, the updates are not automatically pushed to the logical interconnects The logical interconnects are not compliant until you reapply the logical interconnect group ";
f["205"]= " Ports required for HPE OneView CIC int, features, product description, reference, security, roles OneView, online help, help, REST API Ports required for HPE OneView HPE OneView requires specific ports to be available to the appliance to manage servers, enclosures, and interconnects Ports required for HPE OneView Port number Protocol Use Description 22 TCP Inbound and Outbound Used for SSH and SFTP SSH is required to communicate with VC Ethernet and FlexFabric interconnect modules SFTP is required for actions such as firmware upgrades and support dumps 80 TCP Inbound Used for the HTTP interface Typically, this port redirects to port 443; this port provides the access required by the iLO 123 UDP Inbound HPE OneView acts as an NTP server, iLO and Onboard Administrator requires access 123 UDP Outbound Used as an NTP client to synchronize the appliance time 161 UDP Outbound Supports SNMP GET calls to obtain status data from a server through iLO Also used for iPDU 162 UDP Inbound Used for SNMP trap support from the iLO, Onboard Administrator, and iPDU devices This port is also used to monitor the VC interconnects and trap forwarding 443 TCP Inbound Used for the HTTPS interface to user interface and APIs 443 TCP Outbound Used for secure SSL access to the iLO and Onboard Administrator Used for Redfish, RIBCL, SOAP, and iPDU communication 2162 UDP Inbound Used as an alternative SNMP trap port 5671 TCP Inbound Allows external scripts or applications to connect to and monitor messages from the SCMB StateChange Message Bus 17988 TCP Outbound Used for virtual media access to the iLO from HPE OneView 17990 TCP Browser to iLO Provides browser access to the remote console ";
f["206"]= " Read server hardware types OneView, online help, help, REST API Read server hardware types Prerequisites Minimum required session ID privileges: Server administrator Reading server hardware types using REST APIs Select a server hardware type URI GET restserverhardwaretypes Get the server hardware type GET restserverhardwaretypes id ";
f["207"]= " About topofrack switches OneView, online help, help, REST API About topofrack switches Topofrack switches provide a unified, converged fabric over 10Gb Ethernet for LAN and SAN traffic This unification enables network consolidation, reducing the number of adapters and cables required and eliminating redundant switches A configuration of enclosures, server blades, and thirdparty devices—such as topofrack switches—provides scalability in managing server blades and higher demand for bandwidth from each server with accesslayer redundancy See the HPE OneView Support Matrix for the complete list of supported devices Modular data centers, deploying both individual server blades and racks of server blades, can use a topofrack switch deployment model as a solution for network consolidation You can increase data center flexibility by placing switching resources in each rack so that server connectivity can be aggregated Integration with topofrack switches provides the following benefits: A distributed modular system that creates a scalable server access environment One single point of management and policy enforcement Reduced operational expenses less cabling, reduced power consumption for operation and cooling, effective bandwidth utilization Currently, HPE OneView support for these resources focuses on providing a monitored view of the environment with the ability for limited configuration changes on the interconnect facing ports Firmware update is not supported HPE OneView supports status and configuration monitoring and compliance monitoring of Cisco Nexus topofrack switches when they are operating as access switches and connected directly to a Cisco FEX Cisco Fabric Extender for BladeSystem in an enclosure ";
f["208"]= " About monitored c7000 enclosures OneView, online help, help, REST API About monitored c7000 enclosures You can add c7000 enclosures to inventory and monitor the hardware This is useful when you have enclosures that have already been deployed and you cannot migrate them into HPE OneView Enclosures with G6 and later ProLiant server blades cannot be managed, but can be monitored Monitoring hardware in c7000 enclosures can be done with a free license called HPE OneView Standard For more information, see License types NOTE: If the firmware for any part of the enclosure does not meet the supported minimum, the enclosure will be added in an Unmanaged state To resolve this issue, update the firmware manually outside of HPE OneView and then refresh the enclosure To add a c7000 enclosure for monitoring, see Add a c7000 enclosure to monitor the hardware Move a c7000 enclosure from monitored to managed Once an enclosure is monitored in HPE OneView, if you decide to change from monitored to managed, you must remove the enclosure from HPE OneView and then migrate or add it back as a managed enclosure, obtaining the appropriate license Migration keeps the configuration settings, whereas add does not migrate the configuration ";
f["209"]= " Change scope resource assignments CONTACT CI DOC OWNERS before modifying this content OneView, online help, help, REST API Change scope resource assignments Use this procedure to assign resources to a scope, remove resource assignments from a scope, or both Changing scope resource assignments using REST APIs Obtian the scope ID: GET restscopes Change the resource assignments for that scope: PATCH restscopesidresourceassignments NOTE: A single resource can be assigned to and unassigned from multiple scopes through a PATCH API request on the resource with modifications to the scopeUris attribute ";
f["210"]= " Identify server hardware that needs administrative attention OneView, online help, help, REST API Identify server hardware that needs administrative attention To get server hardware that might need administrative attention, you can filter alerts specifically for server hardware The example below shows how to find server hardware using the severity and urgency attributes Prerequisites Minimum required session ID privileges: Infrastructure administrator Identifying server hardware that needs administrative attention using REST APIs GET restalertsfilter=physicalResourceType='physical_servers'&filter=severity='UNKNOWN, OK, MAJOR, CRITICAL'&filter=urgency='None, Deferrable, Medium, High, Immediate, Unknown' ";
f["211"]= " About volume templates storagevolumetemplatesall OneView, online help, help, REST API About volume templates A volume template is a logical resource that enables you to create a standard configuration from which multiple volumes can be created ";
f["212"]= " Configure Quality of Service settings for a logical interconnect OneView, online help, help, REST API Configure Quality of Service settings for a logical interconnect Prerequisites Minimum required session ID privileges: Network administrator Configuring Quality of Service settings for a logical interconnect using REST APIs Edit Quality of Service settings of an existing logical interconnect: Select a logical interconnect URI GET restlogicalinterconnects Get the logical interconnect URI from step 1 GET restlogicalinterconnects id Edit the qosConfiguration settings Update the logical interconnect PUT restlogicalinterconnects id ";
f["213"]= " Delete an enclosure group OneView, online help, help, REST API Delete an enclosure group You cannot delete an enclosure group if it has members Before you delete an enclosure group, you must remove from management all enclosures in the group Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator Deleting an enclosure group using REST APIs Select the enclosure group URI GET restenclosuregroups Delete the enclosure group using the URI from step 1 DELETE restenclosuregroups id ";
f["214"]= " Learning about REST APIs OneView, online help, help, REST API Learning about REST APIs REST Representational State Transfer is a web service that uses basic CRUD Create, Read, Update and Delete operations performed on resources using HTTP POST, GET, PUT, and DELETE To learn more about REST concepts, see http:enwikipediaorgwikiRepresentational_state_transfer The appliance has a resourceoriented architecture that provides a uniform REST interface Every resource has one URI Uniform Resource Identifier and represents a physical device or logical construct You can use REST APIs to manipulate resources To view a list of resources, see the HPE OneView REST API Reference For general information about REST APIs, see the following topics: Get started Log in to the appliance using REST APIs URI format Resource model format Resource operations Asynchronous versus synchronous operations REST API version and backward compatibility Return codes Query resources and track task status Querying resources and pagination using common REST API parameters Task resource Error handling and concurrency control Error handling Error message format Concurrency control using etags Code samples and developer tools PowerShell and Python code sample libraries Developer tools in a web browser Data collection Using the StateChange Message Bus SCMB Enable metric streaming Using the Metric Streaming Message Bus MSMB Using remoteSyslog ";
f["215"]= " View server hardware without an assigned license OneView, online help, help, REST API View server hardware without an assigned license View a list of server hardware that are not in compliance and do not have an assigned license Prerequisites Minimum required session ID privileges: Infrastructure administrator, Server administrator Viewing servers without an assigned license using REST APIs GET restlicensesfilter=licenseType='Unlicensed' ";
f["216"]= " Delete a server blade from management OneView, online help, help, REST API Delete a server blade from management To remove a server blade from management, you must remove an entire enclosure See Delete a c7000 enclosure from management ";
f["217"]= " Add a server blade to an enclosure OneView, online help, help, REST API Add a server blade to an enclosure When you insert a server blade into an empty slot in an enclosure, it is automatically recognized, and an alert is generated that a server blade was added Performing a GET on the enclosure shows that the server blade status is OK and no profile is associated with it To find all the recently added blade servers, perform a GET on the alerts resource Prerequisites Minimum required session ID privileges: Server administrator Viewing recently added server blades in the appliance environment using REST APIs GET restalertsfilter=lifeCycle&filter=physicalResourceType='server_hardware' ";
f["218"]= " Register with the portal OneView, online help, help, REST API Register with the portal Prerequisites Minimum required session ID privileges: Server administrator Register with the portal using REST APIs POST restsupportportalregistration ";
f["219"]= " Enclosures OneView, online help, help, REST API Enclosures Use REST APIs to  Add an enclosure to manage its content Add a c7000 enclosure to monitor the hardware Delete a c7000 enclosure from management Edit an enclosure Migrate a c7000 VCM enclosure using REST API Move a monitored c7000 enclosure to managed status Refresh the connection between an enclosure and the appliance Replace a c7000 enclosure OA and midplane See more tasks Learn more About enclosures About c7000 enclosures enclosures REST APIs ";
f["220"]= " Add a rack OneView, online help, help, REST API Add a rack When you add a rack, HPE ProLiant Servers mounted in HPE Intelligent Series Racks are automatically grouped in racks in the proper positions The rack serial number provides the initial rack names This applies to BladeSystem Enclosures that provide HPE Intelligent Series Racks as well If iPDUs Intelligent Power Distribution Units are powering devices in a rack, the appliance infers that they are present in the rack and automatically adds them to the rack layout Prerequisites Minimum required session ID privileges: Server administrator Adding a rack using REST APIs POST restracks ";
f["221"]= " Troubleshooting appliance backup and restore OneView, online help, help, REST API Troubleshooting appliance backup and restore If an unrecoverable error occurs while the appliance is being restored, the appliance reboots and then resets to factory default settings In that situation, use the user interface or REST APIs  Configure the appliance to reconfigure the appliance After reconfiguring the appliance, use a different backup file to restore the appliance Resolving HTTP errors The following table lists REST API error codes and resolutions HTTP error Response body error code Description and resolution 400 Bad Request INVALID_PARAMETER Description: An invalid parameter was specified Resolution: Specify a valid backup ID It must be in the form: hostname _backup_ YYYYMMdd_HHmmss 401 Unauthorized AUTHORIZATION Description: An incorrect user name or password was specified Resolution: Verify the credentials Specify the correct user name and password 404 Not Found RESOURCE_NOT_FOUND Description: The incorrect URI was specified Resolution: Specify the correct URI You may need to wait for the appliance software to start You can find out the correct URI using this document It might help to issue the REST request to obtain the last backup resource 409 Conflict BACKUP_IN_PROGRESS Description: The requested operation cannot be performed because a backup is in progress A backup cannot be uploaded or restored while the appliance is taking a backup Resolution: Wait until the backup finishes or cancel the backup, then retry the operation BACKUP_DOWNLOAD_IN_PROGRESS Description: The requested operation cannot be performed because a backup is being downloaded A backup file cannot be uploaded or restored while a download is in progress Resolution: Wait until the download finishes, then retry the operation BACKUP_UPLOAD_IN_PROGRESS Description: The requested operation cannot be performed while a backup file is uploaded Resolution: Wait until the upload finishes, then retry the operation BACKUP_RESTORE_IN_PROGRESS Description: The requested operation cannot be performed while a restore operation is in progress Resolution: Wait until the restore operation finishes, then retry the operation 500 Internal Server Error Various Description: An internal error occurred Resolution: Create a support dump Try to restore a different backup ";
f["222"]= " Set up logical interconnect port monitoring OneView, online help, help, REST API Set up logical interconnect port monitoring For analysis, you can use port monitoring to duplicate and direct network traffic to one logical interconnect port from up to 16 physical servers Prerequisites Minimum required session ID privileges: Network administrator Set up logical interconnect port monitoring using REST APIs Select the logical interconnect URI GET restlogicalinterconnects Using the logical interconnect URI, get the current port monitoring information GET logical interconnect URIportmonitor Enable port monitoring and add the list of ports you want to monitor PUT logical interconnect URIportmonitor ";
f["223"]= " Create a selfsigned certificate OneView, online help, help, REST API Create a selfsigned certificate The appliance uses a certificate for authentication over SSL The certificate contains a public key, and the appliance maintains the corresponding private key, which is uniquely tied to the public key A selfsigned certificate indicates that a host vouches for itself, which, in some cases, might be adequate By default, browsers do not trust selfsigned certificates and display a warning A more secure alternative is a certificate issued by a thirdparty certificate authority For information on these certificates, see Create a certificate signing request Prerequisites Minimum required session ID privileges: Infrastructure administrator Required attributes: Country State or province City or locality Organization name Common name fully qualified host name of the appliance Creating a selfsigned certificate using REST APIs PUT restcertificateshttps ";
f["224"]= " Upload a backup file to the appliance OneView, online help, help, REST API Upload a backup file to the appliance When you upload a backup file to the appliance, it replaces the backup file currently stored on the appliance Prerequisites Minimum required session ID privileges: Infrastructure administrator To successfully restore a backup file, the appliance must be running a version of the firmware that is compatible with the backup file If the backup file firmware version is not compatible with the appliance firmware version, an error is returned when you attempt to upload the backup file Uploading a backup file to the appliance using REST APIs POST restbackupsarchive ";
f["225"]= " Update a logical switch from group OneView, online help, help, REST API Update a logical switch from group The update from group operation is not performed automatically, as in the case of logical interconnects For this operation you must edit the logical switch Prerequisites Minimum required session ID privileges: Network administrator Updating a logical switch from group using REST APIs Select a logical switch URI GET restlogicalswitches Update the logical switch from its logical switch group using the URI from step 1 PUT restlogicalswitches id ";
f["226"]= " Scopes OneView, online help, help, REST API Scopes Use REST APIs to  Create a scope Change scope resource assignments Delete a scope List all scopes List information about a specific scope Modify a scope definition See more tasks Learn more About scopes scopes REST APIs ";
f["227"]= " Delete a c7000 enclosure from management OneView, online help, help, REST API Delete a c7000 enclosure from management When you remove a c7000 enclosure from appliance management, you remove all of its associated interconnects, servers, alerts, activities, and other objects Before removing the enclosure, you must remove the server profiles from the server hardware in the enclosure If the enclosure is hosting active server profiles, you cannot perform the remove operation Prerequisites Minimum required session ID privileges: Infrastructure Administrator Deleting a c7000 enclosure from appliance management using REST APIs Select an enclosure URI GET restenclosures Remove the enclosure using the URI from step 1 DELETE restenclosures id NOTE: If the appliance cannot establish communication with an enclosure, you must forcibly remove the enclosure from the appliance This situation might occur if you physically remove the enclosure and it is offline DELETE restenclosures idforce=true ";
f["228"]= " About interconnects OneView, online help, help, REST API About interconnects Interconnects enable communication between the server hardware in the enclosure and the data center networks About managed and monitored interconnects Interconnects are added automatically when the enclosure that contains them is added to the appliance Managed HPE OneView manages the interconnects enabling you to apply configurations, collect statistics, and alert users to specific conditions Monitored HPE OneView monitors hardware for inventory and hardware status only Monitored interconnects are not associated with firmware baselines or logical interconnects By default, newly added interconnects have their firmware in an unset state Managed interconnects Managed interconnects are an integral part of an enclosure, and each managed interconnect is a member of a logical interconnect Each logical interconnect is associated with a logical interconnect group, which is associated with an enclosure group For more information about logical interconnects, see  For information about the relationship that enclosures and enclosure groups have with interconnects, logical interconnects, and logical interconnect groups, see Logical Interconnects You can update managed interconnect firmware using an SPP Service Pack for ProLiant About unmanaged and unsupported interconnects Unmanaged interconnects If you assign an enclosure group which includes a logical interconnect group to an enclosure in which the interconnects installed in the enclosure do not match the logical interconnect group, each interconnect reports its state as unmanaged The physical interconnect configuration in the enclosure must match the logical interconnect group before an interconnect can be managed Unsupported interconnects Unsupported hardware is hardware that the appliance cannot manage For c7000, if the appliance detects an interconnect that it does not expect not defined in the logical interconnect group or cannot manage, the appliance places it into an inventory state and creates a resource for it, but does not bring it under management If the location corresponds to the definition in the logical interconnect group, it assigns the interconnect a critical health status and displays an alert with a resolution of replacing the interconnect with a model it can manage The appliance displays the model name of the unsupported interconnect that it obtains from the OA Onboard Administrator NOTE: If you try to create a server profile that has a connection to an unsupported interconnect, the operation will fail FIP snooping Fibre Channel over Ethernet FCoE is used to transport Fibre Channel FC storage data over a dedicated Ethernet cable FCoE Initialization Protocol FIP handles the FC discovery and login process for FCoE networks FIP uses a Fibre Channel Forwarder FCF, which is an Ethernet switch capable of handling FCoE An FCF is like a Fibre Channel switch that has Ethernet ports FIP provides an Ethernet MAC address used by FCoE to traverse the Ethernet network FIP obtains the Fibre Channel ID FC ID from the Ethernet network, which is required on the Fibre Channel network FIP snooping provides statistical data that can be used to monitor, verify, or troubleshoot connectivity For a list of interconnects where FIP snooping is supported, see the appropriate support or compatibility matrix on the Hewlett Packard Enterprise Information Library More information “ Additional uplink port details” in the online help “ Additional downlink port details” in the online help Connectivity and synchronization with the appliance The appliance analyzes the health status of interconnects and issues alerts when there is a change in status of an interconnect or port The appliance maintains the configuration that you specify on the interconnects that it manages The appliance also tracks the connectivity status of interconnects If the appliance loses connectivity with an interconnect, an alert is displayed until connectivity is restored The appliance attempts to resolve connectivity issues and clear the alert If it cannot, you have to resolve the issues and manually refresh the interconnect to synchronize it with the appliance You can manually refresh the connection between the appliance and an interconnect from the Interconnects screen ";
f["229"]= " Read unsupported server hardware OneView, online help, help, REST API Read unsupported server hardware When unsupported server hardware is added into the appliance environment, the hardware is not managed You can retrieve a list of unsupported hardware in your environment Prerequisites Minimum required session ID privileges: Infrastructure administrator Reading unsupported server hardware using REST APIs GET restserverhardwarefilter=state='Unsupported' ";
f["230"]= " Update server hardware capacity settings OneView, online help, help, REST API Update server hardware capacity settings To update server hardware capacity settings, perform a PUT operation that includes only the calibratedMaxPower attribute View server hardware capacity settings attributes by using a GET operation, edit the calibratedMaxPower attribute, and then perform a PUT operation that includes only the edited calibratedMaxPower attribute Prerequisites Minimum required session ID privileges: Server administrator Updating server hardware capacity settings using REST APIs Select a server hardware URI GET restserverhardware Get the current server hardware capacity using the URI from step 1 GET server hardware URIenvironmentalConfiguration Edit the server hardware capacity The only attribute to send in the response body is calibratedMaxPower Do not send all attributes from the GET operation Update the server hardware capacity PUT server hardware URIenvironmentalConfiguration ";
f["231"]= " Read associated resource information published to the index OneView, online help, help, REST API Read associated resource information published to the index The information that appliance resources publish to the index includes associated resources For example, when you perform a GET operation on specific server hardware, the return response includes the associated server profile and enclosure To learn more about using parameters to refine the results returned from a GET operation, see Common REST API Parameters Prerequisites Minimum required session ID privileges: Infrastructure administrator Reading associated resource information published to the index using REST APIs GET restassociations ";
f["232"]= " About reports OneView, online help, help, REST API About reports HPE OneView offers reports to help you monitor your inventory as well as help you monitor your environment The inventory reports provide information about your servers or enclosures such as model, serial number, part number, and so on Other reports provide a picture of the overall status of your environment For more detailed information about the reports, see the HPE OneView User Guide ";
f["233"]= " Racks OneView, online help, help, REST API Racks Use REST APIs to  Add a rack Read a rack Read the power configuration of a rack Update a rack Delete a rack See more tasks Learn more About racks racks REST APIs ";
f["234"]= " Prepare a VCEM enclosure for migration into HPE OneView OneView, online help, help, REST API Prepare a VCEM enclosure for migration into HPE OneView An enclosure managed by Virtual Connect Enterprise Manager VCEM can be migrated into HPE OneView The Virtual Connect domain for the enclosure must be removed from the Virtual Connect domain group before starting the migration process To remove the Virtual Connect domain, use one of the following options: Option 1 — Use the VCEM GUI First, remove the Virtual Connect domains from the Virtual Connect domain group through the VCEM web interface VCEM marks the MACs and WWNs that are assigned to profiles in the domain as External This ensures that VCEM does not reuse those addresses in the future The enclosure is managed by VCM NOTE: VCM ranges, even if originated from a VCEM domain group, will not be migrated The individual MACWWN for each profile connection will be used as a userdefined ID within HPE OneView Any new addresses assigned in the future will be allocated from the HPE OneView address pools Follow the VCM migration process as outlined in Before migrating c7000 enclosures Option 2 — Use the HPE PowerShell module An HPE PowerShell module is available to automate the process described in Option 1 Download the HPE PowerShell library from http:hewlettpackardgithubioPOSHHPOneView From the HPE PowerShell module, execute the InvokeHPOVVcmMigration command See the HPE PowerShell module documentation for more information Follow the VCM migration process as outlined in Before migrating c7000 enclosures ";
f["235"]= " Create a logical switch group OneView, online help, help, REST API Create a logical switch group Prerequisites Minimum required session ID privileges: Network administrator Creating a logical switch group using REST APIs POST restlogicalswitchgroups ";
f["236"]= " Add a default site OneView, online help, help, REST API Add a default site Prerequisites Minimum required session ID privileges: Server administrator Add a default site using REST APIs POST restsupportsitesdefault ";
f["237"]= " Log in to the appliance using REST APIs OneView, online help, help, REST API Log in to the appliance using REST APIs When you log in to the appliance using the loginsessions REST API, a session ID is returned You use the session ID in all subsequent REST API operations in the auth header The session ID is valid for 24 hours ";
f["238"]= " Create a support dump for authorized technical support OneView, online help, help, REST API Create a support dump for authorized technical support Some error messages recommend that you create a support dump of the appliance to send to an authorized support representative for analysis The support dump process: Deletes any existing support dump file Gathers logs and other information required for debugging Creates a compressed file Unless you specify otherwise, all data in the support dump file is encrypted so that it is accessible only by an authorized support representative You might choose not to encrypt the support dump file if you have an onsite, authorized support representative or if your environment prohibits outside connections You can also validate the contents of the support dump file and verify that it does not contain sensitive data such as passwords IMPORTANT: If the appliance is in an error state, you can still create an encrypted support dump file without logging in or other authentication The support dump file contains the following: Operating system logs from varlog Product logs from cilogs The results of certain operating system and productrelated commands Items logged in the support dump file are recorded in UTC Coordinated Universal Time Prerequisites  Minimum required session ID privileges: Infrastructure administrator Creating a support dump using REST APIs Create a support dump POST restappliancesupportdumps Use the value of the uri element in the Response Body from the POST in step 1 to download the support dump GET restappliancesupportdumpsfile name IMPORTANT: Unless you specify otherwise, the support dump file is encrypted so that only authorized support personnel can view its contents In accordance with the Hewlett Packard Enterprise data retention policy, support dump files sent to Hewlett Packard Enterprise are deleted after use ";
f["239"]= " Remove a storage pool storagepoolsall OneView, online help, help, REST API Remove a storage pool When a storage pool is removed, it is no longer managed by the appliance In the storage system, the storage pool is moved from the managedPools collection to the unmanagedPools collection Prerequisites Minimum required session ID privileges: Infrastructure administrator or Storage administrator The storage pool does not contain storage volumes or storage volume templates Removing a storage pool using REST APIs Select a storage pool URI GET reststoragepools NOTE: To select a storage pool URI from a specific storage system, you can perform a GET operation using reststoragesystems id and select a storage pool URI from the managedPools collection Delete the storage pool DELETE reststoragepools id ";
f["240"]= " About remote support OneView, online help, help, REST API About remote support Register with Hewlett Packard Enterprise to allow automatic case creation for hardware failures on servers and enclosures and to enable Proactive Care Once enabled, all eligible devices added in the future will be automatically enabled for remote support Eligible devices are Gen8 and newer blades and rack servers and enclosures NOTE: Servers must be at iLO 21 firmware level or above to be enabled for remote support Hewlett Packard Enterprise will contact you to ship a replacement part or send an engineer for devices that are under warranty or support contract Remote support enables Proactive Care services including Proactive Scan reports and FirmwareSoftware Analysis reports with recommendations that are based on collected configuration data Remote support is secure No business data is collected, only devicespecific configuration and fault data All communications are outbound only and use industry standard TLS encryption ensuring confidentiality and integrity of the information About channel partners The Partner ID uniquely identifies a partner as an HPE Authorized Partner Hewlett Packard Enterprise is the default channel partner if no other channel partner is assigned HPE Authorized Resellers By enabling remote support, you enable the reseller to access configuration reports and contract warranty reports in Insight Online in the HPE Support Center, as well as configuration details and some contract and warranty details HPE Authorized Service Partners In addition to the above information provided to Authorized Resellers, the Service Partner has access to service event status and reports, with links into the HPE Channel Services Network portal About data collection Basic collection sends configuration information to Hewlett Packard Enterprise for analysis and proactive services in accordance with your warranty and service agreements This data is transmitted every 30 days Enclosures only support basic collection Active health sends information about the server’s health, configuration, and runtime telemetry to Hewlett Packard Enterprise This information is used to troubleshoot issues and closedloop quality analysis This data is transmitted every 7 days ";
f["241"]= " Retrieve switch data OneView, online help, help, REST API Retrieve switch data Prerequisites Minimum required session ID privileges: Network administrator Retrieving switch data using REST APIs GET restswitches id ";
f["242"]= " Create a logical switch OneView, online help, help, REST API Create a logical switch Prerequisites Minimum required session ID privileges: Network administrator The physical switch IP address SSH credentials: user name and password SNMP credentials: port, version, and community string SNMP version v1v2c only Creating a logical switch using REST APIs POST restlogicalswitches ";
f["243"]= " About pause flood protection OneView, online help, help, REST API About pause flood protection Ethernet switch interfaces use pause framebased flow control mechanisms to control data flow When a pause frame is received on a flow control enabled interface, the transmit operation is stopped for the pause duration specified in the pause frame All other frames destined for this interface are queued up If another pause frame is received before the previous pause timer expires, the pause timer is refreshed to the new pause duration value If a steady stream of pause frames is received for extended periods of time, the transmit queue for that interface continues to grow until all queuing resources are exhausted This condition severely impacts the switch operation on other interfaces In addition, all protocol operations on the switch are impacted because of the inability to transmit protocol frames Both port pause and prioritybased pause frames can cause the same resource exhaustion condition Virtual Connect interconnects provide the ability to analyze server downlink ports for pause flood conditions and take protective action by disabling the port Virtual Connect 431 and later also monitors and reports on uplinks and stacking links for pause flood The default polling interval is 10 seconds and is not customer configurable The SNMP agent supports trap generation when a pause flood condition is detected or cleared ";
f["244"]= " Create a server profile OneView, online help, help, REST API Create a server profile Prerequisites Minimum required session ID privileges: Server administrator A managed enclosure that includes a blade server without a server profile or a rack server under management without a server profile The selected server hardware is powered off NOTE: Duplicate VLANs must be placed on different physical ports LOMs Create or edit the connections to specify different networks or place them on different physical ports Creating a server profile using REST APIs Get a server hardware URI GET restserverprofilesavailableservers Select the BIOS settings for the server hardware using the associated server hardware type URI To retrieve the available values from the given server hardware type: GET restserverhardwaretypes id Get available server ports using the server hardware type URI and enclosure group URI associated with the server hardware The hardware type and enclosure group of the physical server must match the profile GET restserverprofilesprofileportsserverHardwareTypeUri= uri&enclosureGroupUri= uri Select the network URIs for the server profile connections using the server hardware type URI and the enclosure group URI GET restserverprofilesavailablenetworksserverHardwareTypeUri= uri&enclosureGroupUri= uri NOTE: If you are attaching SAN storage, you can select connections that are associated with the storage system See step 7 Select the firmware URI you prefer to apply GET restfirmwaredrivers Define the local storage settings for the server based on the storage capabilities from the associated server hardware type Retrieve the available local storage capabilities from the given server hardware GET restserverhardwaretypes id Select the OS type used by the storage attachments Optional Only apply to attach SAN storage GET reststoragesystemshosttypes Select storage volumes that are visible to that server hardware typeenclosure group Optional Only apply to attach SAN storage For each storage volume that you want to attach, you need the associated storage system URI and storage pool URI This information is returned in the response body GET restserverprofilesavailablestoragesystemscount=25&start=0&enclosureGroupUri= uri&serverHardwareTypeUri= uri Create the server profile with the information from the previous steps During this step you can specify the boot order and BIOS settings POST restserverprofiles ";
f["245"]= " Best practices for restoring an appliance CONTACT CI DOC OWNERS before modifying this content OneView, online help, help, REST API Best practices for restoring an appliance Topic Best Practice Before you begin Note the passwords you use Maintain a list of the current user accounts on the appliance The restore operation resets the user names and passwords to those that were in effect when the backup file was created Create a support dump Use the support dump to diagnose failures that occurred before the restore operation Download the existing audit logs, and store them for safekeeping The restore operation restores the audit logs from the backup file, overwriting the existing logs Stop all automatically scheduled backups Restart the automatically scheduled backups after the appliance is restored Make the backup file accessible to the appliance from which you plan to issue the upload request If you are using an enterprise backup product to archive backup files, follow any steps required by your backup product to prepare for the restore operation Inform users Make sure that all users logged in to the appliance log out Users who are logged in when the restore operation begins are automatically logged out, losing whatever work was in progress All users are blocked from logging in during the restore operation Use the right backup file Use the latest backup file to restore the appliance Changes made after the backup file is created cannot be saved Make sure the appliance network settings are the ones you want the appliance to use after the restore operation Appliance network configuration settings are not included in the backup file Ensure that the appliance being restored and the appliance on which the backup file was created have the same firmware version; otherwise, the restore operation fails The platform type, hardware model, and the major and minor numbers of the appliance firmware must match to restore a backup The format of the appliance firmware version is as follows: majornumber minornumber revisionnumber buildnumber The revision and build numbers do not need to match If the backup file is incompatible with the firmware on the appliance, the upload returns an error and the restore operation stops You will need to update the firmware or select a different backup file If the backup file was created on an appliance that is different from the one you are restoring, do one of the following: Delete the original appliance Reconfigure the original appliance so that it no longer manages the devices it was managing when the backup file was created Serious errors can occur if multiple appliances attempt to manage the same devices ";
f["246"]= " Enable or disable LLDP tagging using REST APIs OneView, online help, help, REST API Enable or disable LLDP tagging using REST APIs Enabling or disabling the enableTaggedLldp parameter determines the LLDP management address TLV of LLDP frames sent out by an interconnect Prerequisites Minimum required session ID privileges: Infrastructure administrator or Network administrator Minimum required Virtual Connect version: 445 Enabling LLDP tagging using REST APIs Select a logical interconnect URI GET restlogicalinterconnects Get the logical interconnect using the URI from step 1 GET restlogicalinterconnects id Set enableTaggedLldp to true Update the logical interconnect PUT restlogicalinterconnects restlogicalinterconnects id Disabling LLDP tagging using REST APIs Select a logical interconnect URI GET restlogicalinterconnects Get the logical interconnect using the URI from step 1 GET restlogicalinterconnects id Set enableTaggedLldp to false Update the logical interconnect PUT restlogicalinterconnects id More information About Link Layer Discovery Protocol LLDP tagging ";
f["247"]= " Action privileges for user roles OneView, online help, help, REST API Action privileges for user roles The following table lists the user action privileges associated with each user role The Use privilege is a special case that allows you to associate objects to objects that you own but you are not allowed to change For example, in a logical interconnect group, a user assigned the role of Server administrator is not allowed to define logical interconnect groups, but can use them when adding an enclosure Action privileges for user roles Category Action privileges for user roles C=Create, R=Read, U=Update, D=Delete, Use Infrastructure administrator Server administrator Network administrator Backup administrator Storage administrator Read only Hardware setup activities CRUD CRU CRU R CRU R CRU alerts RUD RUD RUD — RUD R RUD appliance CRUD R R R R R R audit logs CR R R — R — — backups CRUD R R CRD R R R communitystring RU R CRU — R — — connections CRUD R CR R R R — connection templates CRUD, Use R, Use CRUD R R R — console users CRUD — — — — — — data centers CRUD CRUD R R R R CRUD debug logs CRUD CRU CRU — R R — device bays CRUD CRUD R R R R CRUD domains CRUD R CRU R R R — enclosures CRUD CRUD R R R R CRUD enclosure groups CRUD, Use CRUD, Use R R R R — Ethernet networks CRUD R CRUD R R R — events CRU CRU CRU — R R CR fabrics CRUD R CRUD R R R — FC aliases CRUD R R R CRUD R — FC device managers CRUD R R R CRUD R — FC endpoints R R R R R R — FC networks CRUD R CRUD R R R — FCOE networks CRUD, Use R CRUD, Use R R R — FC ports R R R R R R — FC providers R R R R R R — FC SANs CRUD R R R CRUD R — FC SAN services CRUD R R R CRUD R — FC switches R R R R R R — FC tasks R R R R R R — FC zones CRUD R R R CRUD R — firmware drivers CRUD CRUD CRUD R R R R global settings CRUD CRUD CRUD R CRUD R CRUD grouptorolemappings CRUD — — — R R — ID range vmacs MAC addresses CRUD R CRU R R R — ID range vsns serial numbers CRUD CRU R R R R — ID range vwwns World Wide Names CRUD R CRU R R R — integrated tools CRUD R R R R R — interconnects CRUD CR CRUD R R R CRUD, Use interconnect types R, Use R CRUD R R R CRUD labels CRUD CRUD CRUD R CRUD R R licenses CRUD CR R R R R — logical downlinks R R R R R R — logical interconnects CRU, Use R, Use RU, Use R R R — logical interconnects groups CRUD, Use R, Use CRUD, Use R R R — login domains CRUD — — — R R — login sessions CRUD RU RU RU RU RU — managed SANs CRUD, Use R R, Use R CRUD, Use R — migratable VC domains CRUD, Use — — — — — — networks CRUD, Use R, Use CRUD, Use R R R — network sets CRUD, Use CRUD  a CRUD R R R — notifications CRUD CRD CRD R R R — organizations CRUD — — — R R — ports RU, Use — RU, Use — R — — power devices CRUD CRUD R R R R CRUD racks CRUD CRUD R R R R CRUD reports R R R R R R — restores CRUD — — — — R — roles CRUD — — — — R — SANS CRUD, Use R R R CRUD, Use R — SAN manager CRUD, Use R R R CRUD, Use R — server hardware CRUD, Use CRUD, Use R R R R CRUD, Use server hardware types CRUD, Use CRUD, Use R R R R CRUD, Use server profiles CRUD CRUD R R R R — storage pools CRD R R R CRUD R — storage systems CRUD R R R CRUD R — storage target ports CRUD R R R CRUD R — storage volumes CRUD CRUD R R CRUD R — storage volume attachments CRUD CRUD R R CRUD R — storage volumes templates CRUD R R R CRUD R — switches CRUD, Use RU CRUD R R R — tasks R R R R R R R trap forwarding RU R R R R R — unmanaged devices CRUD CRUD R R R R CRUD uplink sets CRUD R CRUD R R R — users CRUD — — — — R — user preferences CRUD — — — — R —  a Server administrators cannot edit bandwidths ";
f["248"]= " Find noncompliant logical interconnects OneView, online help, help, REST API Find noncompliant logical interconnects When a logical interconnect is modified and no longer meets compliance with the associated logical interconnect group, an alert is created and the logical interconnect status is changed to NOT_CONSISTENT Prerequisites Minimum required session ID privileges: Network administrator Filtering for noncompliant logical interconnects using REST APIs GET restlogicalinterconnectsfilter=consistencyStatus='NotConsistent' ";
f["249"]= " Create an Ethernet network OneView, online help, help, REST API Create an Ethernet network When you create an Ethernet network, a connection template is automatically created A connection template defines the connection settings for the Ethernet network The settings include maximum and minimum allowable bandwidth To learn more about tagged, untagged, or tunnel networks, see About networks Prerequisites Minimum required session ID privileges: Network administrator Creating an Ethernet network using REST APIs POST restethernetnetworks NOTE: The connectionTemplateUri attribute must be set to null See also  Quick Start: Initial configuration using REST APIs top of chapter ";
f["250"]= " Appliance OneView, online help, help, REST API Appliance Use REST APIs to  Quick Start: Initial configuration using REST APIs Configure the appliance Backup the appliance Create a certificate signing request Create a selfsigned certificate Create a support dump for authorized technical support Enable or disable authorized support access Import a certificate Read the public key Restore the appliance from a backup file Update the appliance Update the public key Update the SNMP read community string Upload a backup file to the appliance See more tasks Learn more About backing up the appliance About restoring the appliance About SNMP settings appliancedevicereadcommunitystring REST APIs appliancenetworkinterfaces REST APIs backups REST APIs certificates REST APIs certificatesca REST APIs certificateshttps REST APIs settingsenableServiceAccess REST APIs eula REST APIs firmware REST APIs restores REST APIs supportdumps REST APIs ";
f["251"]= " Assign an unassigned server profile OneView, online help, help, REST API Assign an unassigned server profile Prerequisites Minimum required session ID privileges: Server administrator Assigning an unassigned server profile using REST APIs Get all server profiles GET restserverprofiles Search for serverHardwareUri=null in the list of returned server profiles to find unassigned server profiles Select an unassigned server profile Get the unassigned server profile GET restserverprofiles id Get server hardware using the unassigned server profile hardware type and enclosure group GET restserverprofilesserversserverHardwareTypeUri= uri&enclosureGroupUri= uri Add the server hardware URI to the server profile Update the server profile PUT restserverprofiles id ";
f["252"]= " Read the public key OneView, online help, help, REST API Read the public key The public key verifies that Hewlett Packard Enterprise created its RPMs and update packages and that the code has not been modified since it was signed Prerequisites Minimum required session ID privileges: Infrastructure administrator Reading the public key using REST APIs GET restappliancefirmwareverificationKey ";
f["253"]= " Update logical interconnect settings OneView, online help, help, REST API Update logical interconnect settings A logical interconnect is automatically created when you add an enclosure with physical interconnects The logical interconnect represents all the physical interconnects contained in the enclosure To update the logical interconnect settings, perform a PUT operation to reapply all of the logical interconnect settings attributes View the logical interconnect settings attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes NOTE: To learn more about loop protection settings, see About loop protection To learn more about pause flood protection settings, see About pause flood protection Prerequisites Minimum required session ID privileges: Network administrator Updating a logical interconnect using REST APIs Select a logical interconnect URI GET restlogicalinterconnects Get the logical interconnect settings using the URI from step 1 The settings are contained in the ethernetSettings attribute GET restlogicalinterconnects id Edit the logical interconnect settings Update the logical interconnect settings PUT restlogicalinterconnects idsettings ";
f["254"]= " Configure the appliance to send email notification of alerts OneView, online help, help, REST API Configure the appliance to send email notification of alerts Configure the appliance to send email messages when specific alerts are generated Prerequisites Required session ID privileges: Infrastructure administrator SMTP settings and credentials, as needed IMPORTANT: Passwords are sent in clear text because this feature does not support TLSSSL for SMTP sessions If passwords are required for email accounts, Hewlett Packard Enterprise recommends creating a dedicated email account solely for email notification of alerts Alert email filters For each alert email filter, the email addresses of the recipients Configuring the appliance to send email notification of alerts using REST APIs Configure the appliance for email notifications: POST restappliancenotificationsemailconfig ";
f["255"]= " Configure Quality of Service settings for a logical interconnect group OneView, online help, help, REST API Configure Quality of Service settings for a logical interconnect group Prerequisites Minimum required session ID privileges: Network administrator Configuring Quality of Service settings for a logical interconnect group using REST APIs Configure Quality of Service settings when you create a logical interconnect group: Create a logical interconnect group and configure the qosConfiguration settings POST restlogicalinterconnectgroups Edit Quality of Service settings of an existing logical interconnect group: Select a logical interconnect group URI GET restlogicalinterconnectgroups Get the logical interconnect group URI from step 1 GET restlogicalinterconnectgroups id Edit the qosConfiguration settings Update the logical interconnect group PUT restlogicalinterconnectgroups id ";
f["256"]= " Remove a switch OneView, online help, help, REST API Remove a switch You can remove a switch that has been migrated from HPE OneView version 1 x Logical switch groups and logical switches are available only from HPE OneView version 20 and later Migrated switches do not have an associated logical switch These switches would be in the Unmanaged state and cannot be monitored until you remove and subsequently add them using a logical switch Prerequisites Minimum required session ID privileges: Network administrator Removing a switch using REST APIs Select a switch URI GET restswitches Remove the migrated switch using the URI from step 1 DELETE restswitches id ";
f["257"]= " Delete a logical switch OneView, online help, help, REST API Delete a logical switch When you delete a logical switch, the appliance no longer monitors the physical switches associated with it Prerequisites Minimum required session ID privileges: Network administrator Deleting a logical switch using REST APIs Select a logical switch URI GET restlogicalswitches Delete the logical switch using the URI from step 1 DELETE restlogicalswitches id ";
f["258"]= " About logical switch groups OneView, online help, help, REST API About logical switch groups The logical switch group is a template for creating logical switches Logical switches are an aggregation of up to two physical topofrack switches Once constructed from a logical switch group, a logical switch continues to be associated with its logical switch group Any change in consistency between the logical switch group and its associated logical switches is monitored and made visible on the associated logical switch screen in HPE OneView ";
f["259"]= " About managed c7000 enclosures OneView, online help, help, REST API About managed c7000 enclosures Adding an enclosure for management enables you to apply configurations, deploy server profiles, monitor operation status, collect statistics, and alert users to specific conditions There are different ways to add a managed enclosure into HPE OneView Add an enclosure that is new to your environment one that is not managed by another system Any existing configuration settings are erased and not brought into HPE OneView See Before adding an enclosure for management for more information Migrate an enclosure if it is managed by Virtual Connect Manager VCM so that the existing configuration is captured and recreated in HPE OneView See About migrating c7000 enclosures managed by other management systems for more information NOTE: You can forcibly add an enclosure from another management system However, it removes all current configuration settings where it is currently being managed, and does not import the configuration settings into HPE OneView Adding or migrating an enclosure for management requires an HPE OneView Advanced or an HPE OneView Advanced wo iLO license See License types ProLiant G6 and ProLiant G7 BL680c server blades If you add an enclosure for management that contains ProLiant G6 server blade or a ProLiant BL680c server blade, the following occurs: These server blades are added to HPE OneView in a Monitored state See About monitored c7000 enclosures The HPE OneView Standard license is automatically applied to these servers only, even though they are in a managed enclosure See License types Firmware for these servers is not updated during the enclosure add The server firmware must be updated manually outside of HPE OneView after adding the enclosure Before adding an enclosure for management Before you add an enclosure for management, consider the following: Do you want a single or multiple logical interconnect for all interconnects in the enclosure See About multiple logical interconnect groups in an enclosure group for more information Do you want a new or existing enclosure group An existing enclosure group applies the configurations from that group to your new enclosure The interconnects in the enclosure are configured automatically according to the logical interconnect groups associated with the enclosure group For a multilogical interconnect configuration, select the enclosure group you created that contains the multiple logical interconnect groups A new enclosure group creates a configuration based on the enclosure you are adding This automatically creates a single logical interconnect for all interconnects in the enclosure If you are creating a new enclosure group, enter a unique name for the group Do you want a new or existing logical interconnect group An existing logical interconnect group applies the configurations from that group to the interconnects A new logical interconnect group creates a configuration based on the interconnects found in the enclosure ";
f["260"]= " About enclosures OneView, online help, help, REST API About enclosures An enclosure is a physical structure with device bays supporting compute, networking, and storage building blocks These building blocks share the enclosure's common power, cooling, and management infrastructure For information about enclosures, see the following topics About c7000 enclosures About managed c7000 enclosures About monitored c7000 enclosures About migrating c7000 enclosures managed by other management systems About unmanaged and unsupported c7000 enclosures ";
f["261"]= " View all licenses OneView, online help, help, REST API View all licenses View a list of all licenses that are managed by the appliance The list includes products, keys, and their associated licensed server hardware as well as any unlicensed server hardware Prerequisites Minimum required session ID privileges: Infrastructure administrator, Server administrator Viewing the license details using REST APIs GET restlicenses ";
f["262"]= " Managing certificates from a browser CONTACT CI DOC OWNERS before modifying this content CIC int, features, product description, reference, security, roles OneView, online help, help, REST API Managing certificates from a browser A certificate authenticates the appliance over SSL The certificate contains a public key, and the appliance maintains the corresponding private key, which is uniquely tied to the public key NOTE: This section discusses certificate management from the perspective of the browser For information on how a nonbrowser client such as cURL uses the certificate, see the documentation for that client The certificate also contains the name of the appliance, which the SSL client uses to identify the appliance The certificate has the following boxes: Common Name CN This name is required By default it contains the fully qualified host name of the appliance Alternative Name The name is optional, but Hewlett Packard Enterprise recommends supplying it because it supports multiple names including IP addresses to minimize namemismatch warnings from the browser By default, this name is populated with the fully qualified host name if DNS is in use, a short host name, and the appliance IP address NOTE: If you enter Alternative Names, one of them must be your entry for the Common Name These names can be changed when you manually create a selfsigned certificate or a certificate signing request Selfsigned certificate The default certificate generated by the appliance is selfsigned; it is not issued by a trusted certificate authority By default, browsers do not trust selfsigned certificates because they lack prior knowledge of them The browser displays a warning dialog box; you can use it to examine the content of the selfsigned certificate before accepting it Using a certificate authority Use a trusted CA certificate authority to simplify certificate trust management; the CA issues certificates that you import If the browser is configured to trust the CA, certificates signed by the CA are also trusted A CA can be internal operated and maintained by your organization or external operated and maintained by a third party You can import a certificate signed by a CA, and using it instead of the selfsigned certificate The overall steps are as follows: You generate a CSR certificate signing request You copy the CSR and submit it to the CA, as instructed by the CA The CA authenticates the requestor The CA sends the certificate to you, as stipulated by the CA You import the certificate ";
f["263"]= " About user roles CONTACT CI DOC OWNERS before modifying this content OneView, online help, help, REST API About user roles User roles enable you to assign permissions and privileges to users based on their job responsibilities You can assign full privileges to a user, or you can assign a subset of permissions to view, create, edit, or remove resources managed by the appliance User role permissions Role Type of user Permissions or privileges Full Infrastructure administrator View, create, edit, or remove resources managed or monitored by the appliance, including management of the appliance, through the UI or using REST APIs An Infrastructure administrator can also manage information provided by the appliance in the form of activities, notifications, and logs Only an Infrastructure administrator can restore an appliance from a backup file Read only Read only View managed or monitored resource information Cannot add, create, edit, remove, or delete resources Specialized Backup administrator Create and download backup files, view the appliance settings and activities Has the authority to use scripts to log in to the appliance and run scripts to back up the appliance Cannot restore the appliance from a backup file NOTE: This role is specifically intended for scripts using REST APIs to log into the appliance to perform scripted backup creation and download so that you do not expose the Infrastructure administrator credentials for backup operations Hewlett Packard Enterprise recommends that users with this role should not initiate interactive login sessions through the HPE OneView user interface   Network administrator View, create, edit, or remove networks, network sets, connections, interconnects, uplink sets, and firmware bundles View related activities, logs, and notifications Cannot manage user accounts   Server administrator View, create, edit, or remove server profiles and templates, network sets, enclosures, and firmware bundles Access the Onboard Administrator and physical servers, and hypervisor registration View connections, networks, racks, power, and related activities, logs, and notifications Add volumes, but cannot add storage pools or storage systems Cannot manage user accounts   Storage administrator View, add, edit, or remove storage systems View, add, or remove storage pools View, create, edit, add, or delete volumes View, create, edit, or delete volume templates View, add, or edit SAN managers View or edit SANs ";
f["264"]= " Delete a network set OneView, online help, help, REST API Delete a network set When a network set is deleted, the networks, connection templates, and logical interconnect groups that it contains are not deleted The server profiles that use the network set will no longer have a connection This action will be reflected in alerts Deleting a network set using REST APIs Select a network set URI GET restnetworksets Delete the network set DELETE restnetworksets id ";
f["265"]= " Assign roles to an enterprise group OneView, online help, help, REST API Assign roles to an enterprise group To add enterprise group users, they must be a part of an enterprise group When you add a group and assign one or more roles to that group, the group’s users are automatically set up for appliance authentication and authorization Prerequisites Minimum required session ID privileges: Infrastructure administrator One or more authentication directories are configured in the appliance Credentials to access the directory Assigning roles to a directorybased group using REST APIs POST restlogindomainsgrouptorolemapping See also  Quick Start: Initial configuration using REST APIs ";
f["266"]= " Task resource OneView, online help, help, REST API Task resource When you make an asynchronous REST API operation, HTTP status 202 Accepted is returned and the URI of a TaskResource resource model is returned in the Location header of the response You can then perform a GET on the TaskResource model URI to poll for the status of the asynchronous operation The TaskResource model also contains the name and URI of the resource that is affected by the task in the associatedResource attribute Creating an appliance backup example Create an appliance backup POST restbackups The URI of a TaskResource in the Location header is returned in the response Poll for status of the backup using the TaskResource URI returned in step 1 GET resttasks id When the task reaches the Completed state, use the associatedResource URI in the TaskResource to download the backup file GET associatedResource URI ";
f["267"]= " Controlling access for authorized users ATLAS CIC int, features, product description, reference, security, roles OneView, online help, help, REST API Controlling access for authorized users Access to the appliance is controlled by roles, which describe what an authenticated user is permitted to do on the appliance Each user must be associated with at least one role Specifying user accounts and roles User login accounts on the appliance must be assigned a role, which determines what the user has permission to do For information on each role, and the capabilities these roles provide, see About user roles Mapping of SSO roles for iLO and OA The appliance enables SSO single signon to iLO and OA Onboard Administrator without storing usercreated iLO or OA credentials The following table describes the mapping of roles between the appliance, iLO, and OA Appliance role SSO to iLO roles SSO to OA roles Infrastructure administrator Admin Admin Server administrator Admin Admin Network administrator User User Read only User User Backup administrator None None Storage administrator User User Appliance roles See About user roles iLO roles Administrator privileges enable assigning all administrative rights for server reset, remote console, and login tasks User privileges have access restrictions, based on IP address, DNS name, or time OA roles Administrator privileges enable creating or editing all user accounts on an enclosure Operator privileges enable full information access and control of bays to which you have permitted access to NOTE: SSO cannot configure permitted bays User privileges enable full information access but no control capability Mapping appliance interactions with iLO , OA, and iPDU The appliance performs configurations on the iLO , OA, and iPDU The following table summarizes how the appliance interacts with these devices For firewall information, see Ports required for HPE OneView Protocol or interaction Description iLO OA iPDU Use Configure Use Configure Use Configure NTP Configures NTP   ✓   ✓     SNMP Enables and configures SNMP to collect information ✓ ✓ ✓ ✓ ✓ ✓ SNMP traps Enables and configures SNMP traps sent to appliance ✓ ✓ ✓ ✓ ✓ ✓ HTTPS RIBCLSOAPJSON  a Collects information the specific protocol varies, but all use SSL ✓   ✓   ✓   Remote Console Links from the UI to the iLO Remote Console ✓           SSH Not used             Telnet Not used             XML reply Collects generic system information ✓   ✓       SSO Enables and configures an SSO certificate for UI access See Mapping of SSO roles for iLO and OA for the privileges that are granted ✓ ✓ ✓ ✓     Appliance user account _HPOneViewAdmin Configures and manages the system using an administratorlevel user account and randomly generated password ✓ ✓     ✓ ✓  a SSL encrypts traffic on the network, but does not authenticate the remote system's certificate ";
f["268"]= " Reapply interconnect configuration OneView, online help, help, REST API Reapply interconnect configuration You can reapply the configuration settings of physical interconnects from the appliance using the reapply logical interconnect configuration feature You may want to do this after replacing an interconnect, after a connection loss, or if an interconnect configuration fails The logical interconnect configuration is reapplied to all managed interconnects Prerequisites Minimum required session ID privileges: Infrastructure administrator, or Network administrator Reapplying interconnect configuration using REST APIs Select a logical interconnect URI GET restlogicalinterconnects Using the logical interconnect URI, reapply the logical interconnect configuration PUT restlogicalinterconnects lsIdconfiguration ";
f["269"]= " About fabrics OneView, online help, help, REST API About fabrics A fabric provides a common model and consistent state representation for both layer 2 and layer 3 network configurations and deployed network services associated with a physical network The set of available networks in a domain are consistent among the networks, interconnect modules, and logical switches, when all are part of the same fabric Creating and deleting a fabric A fabric is created and assigned a default name when a domain is created A fabric is deleted when the domain is deleted Only a single, default fabric is created for each domain Multiple fabrics associated with one domain are not supported Associating resources with fabrics The following resources are associated with a fabric: Networks Logical Interconnects Logical Interconnect Groups Logical Switches Logical Switch Groups When you create a resource, the resource is associated with a fabric When you delete a resource, the association to the fabric is deleted ";
f["270"]= " Logical Switch Groups OneView, online help, help, REST API Logical Switch Groups Use REST APIs to  Create a logical switch group Edit a logical switch group Delete a logical switch group See more tasks Learn more About logical switch groups About logical switches Logicalswitchgroups REST APIs ";
f["271"]= " Create server profile from a server profile template OneView, online help, help, REST API Create server profile from a server profile template Prerequisites Minimum required session ID privileges: Server administrator A managed enclosure that includes a blade server without a server profile template or a rack server under management without a server profile template Creating server profile from a server profile template using REST APIs Select a server profile template to use GET restserverprofiletemplates Get the server profile contents from the template GET on restserverprofiletemplates idnewprofile Identify an hardware to use GET restserverprofilesavailableservers Modify or update server profile name and hardware URI If you want, you can customize other sections Create server profile with the modified content POST restserverprofiles ";
f["272"]= " Server Hardware Types OneView, online help, help, REST API Server Hardware Types Server hardware types are automatically created when an enclosure or rack is added This API allows you to retrieve and update the available server hardware types Use REST APIs to  Read server hardware types Update a server hardware type See more tasks Learn more About server hardware types serverhardwaretypes REST APIs ";
f["273"]= " Update logical interconnect firmware OneView, online help, help, REST API Update logical interconnect firmware After an enclosure is imported and a logical interconnect is defined, you might need to update the logical interconnect firmware When the logical interconnect firmware update is applied, all physical interconnects within the logical interconnect are updated During the update, the logical interconnect is offline and the firmware is uploaded and installed If you prefer, you can upload firmware to the logical interconnect without installing it, so the firmware is ready to be installed later Uploading the firmware without installing it does not disrupt the logical interconnect operation Prerequisites Minimum required session ID privileges: Infrastructure administrator or Network administrator A firmware bundle, also known as Service Pack for ProLiant SPP, uploaded to the appliance Updating logical interconnect firmware using REST APIs Select the firmware URI to apply GET restfirmwaredrivers Select the logical interconnect URI GET restlogicalinterconnects Update the logical interconnect firmware This step uploads and installs the firmware PUT restlogicalinterconnects idfirmware NOTE: To view attributes and values to use for updating upload and install, uploading, or installing logical interconnect firmware, see restlogicalinterconnects idfirmware ";
f["274"]= " Update a local user account OneView, online help, help, REST API Update a local user account To update a local user account, perform a PUT operation to reapply all of the local user account attributes View the local user account attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes Prerequisites Minimum required session ID privileges: Infrastructure administrator Updating a local user account using REST APIs Select the user name GET restusers Using the user name from step 1, get the user information GET restusers userName Update the user account PUT restusers ";
f["275"]= " Read the firmware repository for firmware bundles OneView, online help, help, REST API Read the firmware repository for firmware bundles The firmware repository holds all of the firmware bundles, also known as Service Packs for ProLiant SPPs An SPP is a comprehensive update package of firmware, drivers, and utilities delivered as a single ISO image Prerequisites Minimum required session ID privileges: Infrastructure administrator, Server administrator, or Network administrator Reading the firmware repository for firmware bundles using REST APIs GET restfirmwaredrivers ";
f["276"]= " Update an unmanaged device OneView, online help, help, REST API Update an unmanaged device To update an unmanaged device, perform a PUT operation to reapply all of the unmanaged device attributes View the unmanaged device attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator Updating an unmanaged device using REST APIs Select an unmanaged device URI GET restunmanageddevices Get the unmanaged device using the URI from step 1 GET restunmanageddevices id Edit the unmanaged device Update the unmanaged device PUT restunmanageddevices id ";
f["277"]= " Create an uplink set OneView, online help, help, REST API Create an uplink set Each uplink set must have a unique name and contain at least one network See the HPE OneView Support Matrix for the maximum number of supported uplink sets For more information about uplink sets, see About logical interconnects Prerequisites Minimum required session ID privileges: Infrastructure administrator or Network administrator Creating an uplink set using REST APIs Select the logical interconnect URI GET restlogicalinterconnects Get the logical interconnect using the URI from step 1 GET restlogicalinterconnects id Select a set of Ethernet, Fibre Channel, or FCoE network URIs not assigned to an uplink set GET restethernetnetworksfilter=assignedToUplinkSet='false' GET restfcnetworksfilter=assignedToUplinkSet='false' GET restfcoenetworksfilter=assignedToUplinkSet='false' Select the uplink ports using the interconnect URIs The URIs are contained in the logical interconnect resource model returned in step 2 GET uriports Create the uplink set with the information from the previous steps POST restuplinksets ";
f["278"]= " Create a network set OneView, online help, help, REST API Create a network set A network set is a collection of networks within a single domain that can be used together as a named group to simplify server profile creation Instead of using a server profile to assign one network to a connection, a network set is assigned to a connection When you create a network set, you can designate one network as untagged This untagged network handles untagged traffic After you create a network set, you can add or delete a network from the network set To learn more about editing a network set, see Update a network set Prerequisites Minimum required session ID privileges: Network administrator All networks in a network set must be Ethernet networks All networks in a network set must be in the same interconnect domain Creating a network set using REST APIs Select the Ethernet network URIs GET restethernetnetworks Select the connection template URI GET restconnectiontemplate Create a network set with the above information POST restnetworksets See also  Quick Start: Initial configuration using REST APIs ";
f["279"]= " About logical interconnects OneView, online help, help, REST API About logical interconnects A logical interconnect is a single administrative entity that consists of the configuration for a set of interconnects in a single enclosure, and includes: The uplink sets, which connect to data center networks The mapping of networks to physical uplink ports, which is defined by the uplink sets for a logical interconnect The internal networks, which are used for servertoserver communications without traffic egressing any uplinks The downlink ports, which connect through the enclosure midplane to the servers in the enclosure The connections between interconnects, which are called stacking links Stacking links can be internal cables through the enclosure or external cables between the external ports of interconnects See the appropriate support or compatibility matrix on the Hewlett Packard Enterprise Information Library for the maximum number of networks that can be provisioned on a logical interconnect For a server administrator, a logical interconnect represents the available networks through the interconnect uplinks and the interconnect downlink capabilities through a physical server’s interfaces For a network administrator, a logical interconnect represents an Ethernet stacking configuration, aggregation layer connectivity, stacking topology, network reachability, statistics, and troubleshooting tools About uplink sets An uplink set defines a single, dedicated network or a group of networks and physical ports on a set of interconnects in an enclosure An uplink set enables you to attach the interconnects to the data center networks An uplink set enables multiple ports to support port aggregation multiple ports connected to a single external interconnect and link failover with a consistent set of VLAN networks For tagged Ethernet networks, an uplink set enables you to identify interconnect uplinks that carry multiple networks over the same cable For untagged or tunnel Ethernet networks, an uplink set identifies interconnect uplinks that are dedicated to a single network For Fibre Channel networks, you can add one network to an uplink set Fibre Channel does not allow virtual networks or VLANs For Fibre Channel over Ethernet FCoE networks, an uplink set enables you to carry multiple Fibre Channel and tagged Ethernet networks over the same set of Ethernet cables One uplink set per Cisco FEX module is allowed An uplink set is part of a logical interconnect The initial configuration of the uplink sets for a logical interconnect is determined by the configuration of the uplink sets for the logical interconnect group, but you can change override the uplink sets for a specific logical interconnect Changes you make to the uplink sets for a logical interconnect group are not automatically propagated to existing logical interconnects For example, to propagate a newly added VLAN to a logical interconnect group uplink set to its existing logical interconnects, you must individually update each logical interconnect configuration from the logical interconnect group For each logical interconnect: You can define zero or more uplink sets See networking limits in the HPE OneView Support Matrix for the maximum number of supported uplink sets and the maximum network types supported in an uplink set If you do not define any uplink sets, the servers in the enclosure cannot connect to data center networks A network can be a member of one uplink set per logical interconnect group only An uplink set with Fibre Channel or FCoE networks can use uplinks from only one interconnect An uplink set can contain one or more tagged Ethernet networks An uplink set for an untagged or a tunnel network can only contain that one untagged or tunnel network An uplink set can contain one or more FCoE networks, but the uplinks must be contained within a single FCoEcapable interconnect See firmware requirements in About Fibre Channel over Ethernet FCoE networks Within a logical interconnect group or logical interconnect, all VLAN IDs must be unique across uplink sets and internal networks Internal networks allow servertoserver connectivity within the logical interconnect Internal networks are created by adding existing networks to the internal networks set Internal networks can be added to uplink sets which automatically removes them from the internal networks set Cisco FEX modules do not support internal networks Ethernet networks in an uplink set must be specified individually and cannot be specified by selecting a network set The use of network sets in uplink sets is not supported for the following reasons: The networking configuration is intended to be managed by users with a role of Network administrator Because users with a role of Server administrator can create and edit network sets, allowing network sets to be members of uplink sets could result in server administrators changing the mapping of networks to uplink ports without the knowledge of the network administrator Because a network can be a member of more than one network set, allowing network sets to be members of uplink sets would make it more difficult to ensure that no single network is a member of more than one uplink set, especially as the network set configurations change over time About internal networks An internal network is a network that has no uplink ports and is used for servertoserver communications within a logical interconnect Servers that communicate with each other over internal networks do so without the traffic egressing any uplinks Only tagged, untagged, and tunnel Ethernet networks can be members of internal networks If network connectivity outside of the logical enclosure is required, the network must be in an uplink set associated with an uplink NOTE: A network is not available for profile connections until it is added to an uplink set or internal networks in a logical interconnect group and the associated logical interconnect Adding and removing internal networks Each logical interconnect group and logical interconnect has an internal network list which is initially empty Adding a network to the internal network list in both the logical interconnect group and logical interconnect allows it to be used in server profile connections that can be mapped to downlinks on the interconnects within the logical interconnect IMPORTANT: Duplicate networks in the internal networks list on more than one logical interconnect can result in the inability for the servers in the enclosure to communicate Therefore, it is recommended to define all your internal networks on one logical interconnect in the enclosure You can add or remove internal networks from the Logical Interconnects or Logical Interconnect Groups screen The internal network configuration created in the logical interconnect group is inherited by associated logical interconnects A logical interconnect can be made consistent with the parent logical interconnect group by selecting Actions→ Update from group Networks in the internal networks list appear as available networks for uplink sets They are automatically removed from internal networks if they are added to an uplink set Removing an Ethernet network from an uplink set in a logical interconnect automatically moves it to internal networks so network connectivity is not lost for server profile connections using the network However, if you remove an Ethernet network from an uplink set in a logical interconnect group, the network does not get moved automatically to the internal networks If you want the network to be internal, edit the logical interconnect group and add the network to the internal networks About stacking links and stacking health Stacking links Stacking links apply to Ethernet networks only You can connect all the interconnects to one another through stacking links so that Ethernet traffic from a server connected to an interconnect downlink can reach the data center networks through that interconnect or through a stacking link from that interconnect to another interconnect When adding enclosures, create a single logical interconnect group with a single logical interconnect that contains all interconnects within the enclosure This creates a fully stacked enclosure To set up an enclosure that is not stacked, configure multiple logical interconnect groups where each interconnect is in a separate logical interconnect group and subsequently separate logical interconnects before adding the enclosure You can also set up a partiallystacked enclosure where you have more than one interconnect in a logical interconnect group See About multiple logical interconnect groups in an enclosure group for more information Stacking health The appliance detects the topology within an enclosure of the connections between interconnects, and determines the redundancy of paths between servers and data center networks The appliance reports redundancy information as the stacking health of the logical interconnect, which is one of the following: Redundantly Connected There are at least two independent paths between any pair of interconnects in the logical interconnect, and there are at least two independent paths from any downlink port on any interconnect in the logical interconnect to any other port uplink or downlink in the logical interconnect Connected There is a single path between any pair of interconnects in the logical interconnect, and there is a single path from any downlink port on any interconnect in the logical interconnect to any other port uplink or downlink in the logical interconnect Disconnected At least one interconnect is not connected to the other member interconnects in the logical interconnect Not applicable Interconnects do not support stacking or there is a single interconnect in the logical interconnect Creating or deleting a logical interconnect Creating a logical interconnect in an enclosure A logical interconnect is automatically added when the enclosure is added When you add a c7000 enclosure, the following occurs: A logical enclosure is created based on the defined enclosure group The appliance detects the physical interconnects and their stacking links, if any The appliance automatically creates a single logical interconnect for each logical interconnect group defined in the enclosure group NOTE: The number of logical interconnects that are created depends on how the enclosure group was defined See Update a logical interconnect group The appliance automatically names the logical interconnects using the following naming convention: logical_enclosure_name logical_interconnect_group_name The data for the logical interconnects displays on the Logical Interconnects screen To add or change logical interconnects, see Edit a logical interconnect group in the online help Update a logical interconnect group for more information Deleting a logical interconnect To delete a logical interconnect, you must remove the logical interconnect group from the enclosure group, and then perform an update from group on the logical enclosure This deletes the logical interconnect from the logical enclosure ";
f["280"]= " Update enclosures in the logical enclosure from the enclosure group OneView, online help, help, REST API Update enclosures in the logical enclosure from the enclosure group Update a logical enclosure to ensure that it matches the configuration of its parent enclosure group Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator Updating enclosures in the logical enclosure from the group using REST APIs Update the logical enclosure from the group PUT restlogicalenclosuresidupdateFromGroup ";
f["281"]= " Update a data center OneView, online help, help, REST API Update a data center To update a data center, perform a PUT operation to reapply all of the data center attributes View the data center attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes Prerequisites Minimum required session ID privileges: Server administrator Updating a data center using REST APIs Select a data center URI GET restdatacenters Get the data center using the URI from step 1 GET restdatacenters id Edit the data center Update the data center PUT restdatacenters id ";
f["282"]= " Update the appliance OneView, online help, help, REST API Update the appliance Image files for appliance updates are available from http:wwwhpecominfohpeoneviewupdates The content delivered in the image file and the speed of your network connection determine the amount of time required for the download IMPORTANT: The appliance will restart after it is updated This restart will not disrupt the operation of the systems under management, but it will close the management console Prerequisites Minimum required session ID privileges: Infrastructure administrator Ensure that no other users are logged in to the appliance before starting the appliance update and that no one logs in during the update Hewlett Packard Enterprise recommends that you create and download a backup file before updating the appliance See Backup the appliance Create a VM snapshot of your system before you install an update file Updating the appliance firmware using REST APIs Upload the firmware POST restappliancefirmwareimage Start the firmware update PUT restappliancefirmwarependingfile= upgrade file name NOTE: After the update is uploaded to the appliance, you can perform GET restappliancefirmwarepending to retrieve the estimated time to complete the firmware update, and to determine if a reboot is required To view the release notes and EULA for the update, perform GET restappliancefirmwaredocumentcontent tarFileName suffix documentType For documentType, specify release or eula ";
f["283"]= " Authentication for appliance access CONTACT CI DOC OWNERS before modifying this content CIC int, features, product description, reference, security, roles OneView, online help, help, REST API Authentication for appliance access Access to the appliance requires authentication using a user name and password User accounts are configured on the appliance or in an enterprise directory All access browser and REST APIs, including authentication, occurs over SSL to protect the credentials during transmission over the network ";
f["284"]= " About SAN managers OneView, online help, help, REST API About SAN managers SAN Managers are a resource in HPE OneView that represent a connection to an external entity through which SANs are discovered and managed The external entity can be vendorspecific management software or a physical switch SANs are created outside of HPE OneView in the SAN manager vendor’s management interface Once created, SANs can be discovered and managed in HPE OneView using the SAN Manager resource When creating SAN managers, it is possible to have two SAN managers discovering the same SAN, causing it to show up twice in the SAN view When associating an HPE OneView network to the SAN, the choice of which SAN to associate determines which SAN manager will be used to manage the SAN, and the other will be removed hidden as HPE OneView does not permit a SAN to be managed through more than one SAN manager HPE OneView supports SAN managers from different vendors See the HPE OneView Support Matrix for a list of supported SAN managers About zone sets A zone set is a set of zones you can configure all zones on a SAN manager by activating a zone set from the SAN manager HPE OneView modifies the active zone set when performing zoning or alias configuration Zone sets are not exposed in HPE OneView Active zone set The zone set currently enforced by the fabric Inactive zone set The inactive zone sets for the SAN Only one zone set can be activate at a time SAN manager Term for Inactive zone set HPE Standby zone set Cisco Local zone set Brocade BNA Zone configurations Configuring SAN managers to be managed by HPE OneView You must configure SAN managers using the management software provided by the SAN manager vendor to properly manage them in HPE OneView After properly configuring the SAN manager, you can add it to HPE OneView CAUTION: Performing zone operations from multiple switches without executing a full zone set distribution might result in the loss of zoning data NOTE: Switch vendors support fabric world wide name FWWN or node port world wide name PWWN zone memberships HPE OneView only uses PWWN for zone membership Best Practice: SAN managers  Always use a single switch to perform all zoning operations, regardless of the management software you use to perform the zoning Always use the full zone set distribution commands and settings when making zone changes HPE OneView does this on the SAN manager and SAN through which it is managing by default Configuring HPE SAN managers You must have a valid SNMP v3 user with default read permissions See The HPE OneView User Guide Configuring Cisco SAN manager You must have a valid SNMP v3 user with write permissions See The HPE OneView User Guide Configuring Brocade Network Advisor SAN manager You must have a valid user account with SMIS running See the documentation for your SAN manager for more information To allow HPE OneView to see SAN fabric topology changes automatically, you must disable Track Fabric Changes on the BNA Otherwise, you must perform an Accept Changes operation on the BNA whenever you make changes to the SAN fabric topology for HPE OneView to see them See the BNA documentation for more information on disabling Track Fabric Changes ";
f["285"]= " About server profiles OneView, online help, help, REST API About server profiles Capturing bestpractice configurations About editing a server profile About moving a server profile Working with server profiles to control removeandreplace behavior About assigning a server profile to an empty device bay About server profile connections About server profile connections and changing server hardware types About server profiles and local storage About attaching SAN volumes to a server profile Capturing bestpractice configurations After setting up your data center, you can create server profiles to provision hundreds of servers as easily as you provision one server A server profile is the configuration for a server instance Server profiles and server profile templates capture the entire server configuration in one place, enabling you to replicate new server profiles and to modify them to reflect changes in your data center A server profile includes: Basic server identification information Connectivity settings for Ethernet networks, network sets, Fibre Channel, and FCoE networks Firmware versions Local storage settings SAN storage settings Boot settings BIOS settings When you create a server profile, you can specify the server hardware to which you want to apply the profile Leave the server hardware unassigned if the server hardware is not yet installed Typically, you capture bestpractice configurations in a server profile template, and then create individual server profiles Similar to virtual machine VM templates, profiles enable you to create a provisioning baseline for server hardware types in an enclosure When you create a server profile, it is designated for a server hardware type and enclosure group for server blades, whether the profile is assigned or unassigned Server hardware can have only one profile assigned to it By default, the server profile controls the server boot behavior The server hardware type determines the available options you can select in the server profile If applicable, you can select the boot mode and PXE boot policy You also have the option of specifying the order in which the server hardware attempts to boot HPE ProLiant Gen9 servers support both legacy BIOS and UEFI for configuring the boot process while HPE ProLiant Gen8 are legacy BIOS mode servers only For more information about UEFI, see UEFI FAQs at Unified Extensible Firmware Interface Forum By selecting to manage BIOS settings through the appliance, you can view all settings, only those you have modified, or only those that are different than the default values The BIOS settings displayed depend on the supported server hardware Applying the sections of a server profile to server hardware is a sequential process The screen displays the current section being applied, followed by other sections that have been applied successfully If a server profile needs to be reapplied due to an error, only the unconfigured sections and unapplied sections are reapplied For example, if a firmware update succeeds, but the subsequent BIOS portion of the apply operation fails, the firmware is not applied a second time when the profile is reapplied This helps to prevent unnecessary and timeconsuming updates for the profile Best practice: Perform server profile management tasks on one enclosure at a time  For best performance, create, delete, edit, copy, or move server profiles for server hardware on one enclosure before managing server profiles on a different enclosure About editing a server profile Edit a server profile to change the settings associated with that profile You can edit a server profile any time after it has been created You can also edit a server profile with an Error condition to make corrections When you edit a server profile, the state of the server changes The appliance analyzes the changes and determines the actions to update the server For example, if you change the BIOS settings but not the firmware baseline, the firmware is not updated Only the requested changes are applied NOTE: If you change the server settings or state using tools other than the appliance, the changes are not detected or managed These changes might be overwritten the next time the profile is edited When you edit a server profile, consider the following: Editing a profile is an asynchronous operation Name and description changes take effect immediately, but other changes might take time to complete If a profile is associated with a server profile template, changes can cause the profile to be out of compliance with its template See About server profile consistency validation for more information Profile names must be unique When unassigning a server profile with local storage configured, the logical drive contents are at risk of being lost To preserve the logical drive, physically remove the disk drives or make a copy of the contents of the logical drive so that you can reassign the profile at a later time BIOS settings are managed using the server profile and the settings on the server are overwritten when the server profile is applied You cannot switch between virtual and physical identifiers for the following, unless you delete and recreate the profile connection: Serial numberUUID MAC address WWN To edit some server profile settings, the server hardware must be powered off; for others, the server hardware can remain powered on You can edit the following settings with the server hardware powered on: Profile name Profile description Profile affinity Requested bandwidth of an existing connection Network and network set of an existing connection except when the connection is bootable NOTE: You cannot change an existing connection between an Ethernet network or network set and a Fibre Channel network A Fibre Channel network can only be changed to another Fibre Channel network on the same interconnect Create, attach, and edit storage volumes NOTE: If the server is configured to boot using the storage path, that path cannot be disabled Firmware and OS Drivers using Smart Update Tools Firmware only using Smart Update Tools The profile cannot be modified while the server hardware is powered on if the previous modification were not successfully applied, unless the failure was solely due to SAN storage About moving a server profile You can move a server profile to another piece of server hardware; for example, if you are removing one piece of server hardware and replacing it with another that is similar The move operation enables you to quickly change the hardware destination without rebuilding the entire server profile If you cannot move a server profile directly to the new server hardware, you can change it to unassigned This enables you to retain server profiles that are not currently assigned to any server IMPORTANT: When you move a server blade profile to a different enclosure, and the profile is configured to boot from a direct attach storage device, you must manually update the boot connection of the profile to specify the WWPN that is used for the storage device that is directly attached to the destination enclosure Each enclosure connects to a different port of the direct attach storage device, so the WWPN for that storage device is different for each enclosure If you do not specify the correct WWPN and LUN for the device, the server does not successfully boot from that boot target IMPORTANT: When you move a server profile to a different server, and the profile is managing internal local storage, you must manually move the physical disks from the original server to the new server in order to preserve your data Working with server profiles to control removeandreplace behavior In a server profile, the Affinity control sets the removeandreplace behavior for server blade If you apply a server profile to a server blade and the server is subsequently removed from the device bay, the Affinity setting controls whether the server profile is reapplied when you insert a server blade into the empty bay Server profiles for rack servers do not have affinity Affinity value Description Device bay The server profile you assign to the empty device bay is applied to any server blade you insert into the bay, provided the server hardware type of the inserted server blade matches the server hardware type specified in the server profile Device bay affinity is the default Device bay  server hardware Device bay  server hardware UUID The server profile you assign to the empty device bay is not applied if you insert a different server into the bay The serial number and server hardware type of the inserted server blade must match the values in the server profile Affinity between the server profile and the server hardware is established when one of the following conditions is met: The server profile is assigned to server hardware in a device bay The server profile is assigned to an empty device bay and you subsequently insert a server blade with a matching server hardware type into the bay Editing a server profile resets its server hardware affinity If you assign the server profile to a populated device bay, the server hardware in the bay becomes associated with the profile If the server profile is unassigned or assigned to an empty device bay, any current association is cleared About assigning a server profile to an empty device bay You can assign a server profile to an empty bay The server profile is applied automatically to the server hardware when the server is inserted into the bay and meets the following criteria: The enclosure bay is not assigned by another server profile for example, you cannot assign a profile to bay 9 if a profile for a fullheight server hardware type is assigned to bay 1 This is checked when the profile is assigned The server hardware type of the hardware matches the server hardware type specified in the server profile About server profile connections The maximum number of connections supported by a profile is dependent on the total number of virtual ports defined by the server hardware type and enclosure group associated with the profile The total number of virtual ports is determined by multiplying the number of virtual ports per FlexFabric adapter by the number of FlexFabric adapters defined by the server hardware type The maximum number of connections is 50 or the total number of virtual ports plus two for unassigned connections, whichever is greater About server profile connections and changing server hardware types When changing the server hardware type on a server profile with deployed connections, the new server hardware type must define enough ports to allow automatic port assignment of all currently deployed connections If the new server hardware type does not have sufficient port capacity, automatic port assignment fails when applied to a server and results in the failure of the profile edit operation To avoid this condition, do one of the following: Delete connections so that the remaining number can be automatically assigned Edit the connections and set the port assignment to None so that those connections are not deployed About server profiles and local storage You can manage local storage on server hardware using server profiles Logical drives and unique identifiers About RAID level and controller RAID levels and number of physical drives About local storage and integrated storage controllers NOTE: HPE OneView does not erase data from physical drives when the server profile that specifies the drives is deleted or unassigned It might be possible to access the data, so if you want to ensure the data is inaccessible, erase all sensitive data before you delete the server profile or the local storage configuration Logical drives and unique identifiers If you configure new logical drives in your server profile or import the existing logical drives from the server hardware, HPE OneView stores a unique identifier for each logical drive in the server profile configuration when the server profile is applied On subsequent server profile apply operations, HPE OneView checks for the existence of the identifier on the physical drives of the assigned server hardware If the identifier is missing, the apply operation fails in order to ensure that if the server profile is reassigned to new server hardware, the physical drives are inserted correctly HPE OneView erases the current identifier in a server profile apply operation if any of the following conditions exist: Reinitialize internal storage is selected The Logical drive has been deleted from the server profile The storage controller is set to managed manually About RAID level and controller You can use RAID to define logical drives or HBA to present drives directly to the controller The RAID levels which the controller can support are defined in the specifications of each controller You must check the specifications of each controller to verify which RAID levels the controller supports Supported RAID levels depend on the server hardware type and on the physical server configuration Ensure you have enough physical drives present for the selected RAID level NOTE: Although RAID 50 and RAID 60 are supported by some controllers, they are not supported by HPE OneView To use RAID 50 or RAID 60, set the controller to manage manually in HPE OneView More information RAID levels and number of physical drives RAID levels and number of physical drives See the HPE OneView Support Matrix for information on the number of drives supported by specific server hardware RAID 0 Minimum of 1 drive, increments of 1 RAID 1 Requires 2 drives RAID 10 Requires 4 drives, increments of 2 RAID 1 ADM Requires 3 drives RAID 5 Minimum of 3 drives, increments of 1 RAID 6 Minimum of 4 drives, increments of 1 About local storage and integrated storage controllers HPE OneView is not aware of existing local storage configuration in the integrated storage controller unless you import the local storage when applying a server profile to the server hardware The import option is not a guarantee that no data will be lost For example, if the server is currently in HBA mode, you must change it to RAID mode before it can be imported, and that change in controller mode can cause data loss Once you create a logical drive and apply it to server hardware, that logical drive can no longer be modified While deleting or unassigning a server profile does not directly delete local storage data from the server hardware, data can be lost if a server profile that contains changes to the local storage configuration is applied to the server hardware in the future The table below describes how to preserve your data when making profile or hardware changes Make a change to server hardwareserver profile and preserve integrated local storage data Change in server hardware Procedure Result Move server profile from one server hardware to another Move physical drives to new server hardware Unassign server profile from the current server hardware Physically remove the local storage drives from the server hardware Insert the local drives into new server hardware Do not select Reinitialize internal storage when you apply the server profile to the new server hardware The appliance verifies that the physical drives have been inserted correctly by validating the saved unique identifier Assign a server profile to server hardware that has local storage configured A Import existing drives and data Delete or unassign the current server profile Select Import existing logical drives when applying the new server profile The unique identifier is preserved The existing logical drives and data are imported B Back up and copy data Back up data Delete or unassign the server profile Select Reinitialize internal storage when applying the new server profile Copy the backedup data to the new logical drive on the server hardware A new logical drive is created with a new unique identifier The backedup data is copied to the new logical drive About attaching SAN volumes to a server profile Volumes are associated with server profiles through volume attachments Attaching a volume to a server profile gives the server hardware assigned to the server profile access to storage space on a storage system As you create or edit a server profile, you can attach an existing volume or dynamically create a new volume to attach Newly created volumes can be marked as permanent so that they continue to exist after they are removed from the profile or if the profile is deleted Otherwise, a nonpermanent volume is deleted when the server profile is deleted Properties for attaching a volume can be configured through the server profile For example, you can enable and disable storage paths from the server to the SAN storage Storage targets Within a server profile, storage target ports for volume attachment can be assigned automatically or you can manually assign available ports The target ports that are assigned automatically will belong to same port group Target ports that you assign manually can belong to the same or different port groups Port groups are created when you add a storage system to HPE OneView Manual target selection is supported for Fabric attach paths only, not Direct attach paths Existing HPE 3PAR volumes On 3PAR StoreServ Storage systems, a host sees VLUN allows only a specific host to see a volume and a matched set VLUN allows only a specific host on a specific port to see the volume To reuse a host sees configuration in HPE OneView when adding an existing 3PAR volume to a profile, you must enter the exact LUN value as configured on the 3PAR array In HPE OneView, use the Manual LUN option to add the exact LUN value in the Add Volume dialog To reuse endtoend connectivity for the volume, manually specify the following: LUN value matching the LUN on the 3PAR storage system Target ports Also, to attach export a 3PAR volume as host sees, all storage paths to that volume must be enabled or disabled together Some paths cannot be enabled while some are disabled For more information, download the HPE 3PAR StoreServ Storage Concepts Guide from the HPE Storage Information Library http:wwwhpecominfostoragedocs About server profile consistency validation Consistency checking is validating a server profile to ensure that it matches the configuration of its parent server profile template The appliance monitors both the server profile and server profile template, compares the two, and checks the following for consistency Profile section Consistency checking General Server hardware type Enclosure group Affinity NOTE: Server hardware type and enclosure group inconsistencies must be fixed manually; that is, you must edit the profile and change the hardware type and enclosure group to match the template Firmware If firmware is not managed by a server profile template, then a firmware server profile configuration is not validated for consistency Otherwise, the following configurations are validated for consistency Firmware baseline Installation method NOTE: Forcibly installed firmware is compared only if the firmware baseline is inconsistent Otherwise, forcibly installed firmware is not checked for consistency Connections Connections are compared to identify if extra or missing connections are present For similar connections, the following attributes are checked for differences Port Network Requested bandwidth Connection boot settings NOTE: Extra connections in the server profile with port id None are not considered inconsistent Local Storage If local storage is not managed by server profile template, then local storage server profile configuration is not validated for consistency Otherwise, the following configurations are validated for consistency Controller mode Logical drives NOTE: Inconsistencies in local storage are not fixed automatically by Update from Template They must be fixed manually SAN Storage If SAN storage is not managed by server profile template, then SAN storage server profile configuration is not validated for consistency Otherwise, for volumes with sharing type private, the profile requires the same number of private volumes as defined in the server profile template from the same storage pools, and that LUN numbers remain consistent Any differences in the number of private volumes, their storage pool, or a LUN number will be flagged as an inconsistency For volumes with sharing type shared,the profile must be attached to all the shared volumes associated to the server profile template with matching LUN numbers and storage paths to remain consistent Additional shared volumes can be attached without causing a consistency state The Host OS type designated in a profile must match the server profile template to remain compliant NOTE: Extra attachments in the server profile do not cause inconsistency Boot Settings If Boot settings are not managed by server profile template, then server profile configuration for boot settings is not validated for consistency Otherwise, all configurations must match the server profile template BIOS Settings If BIOS settings are not managed by server profile template, then BIOS server profile configuration is not validated for consistency Otherwise, all configuration must match the server profile template Advanced “ Hide unused FlexNICs” instruction must match the server profile template If configurations match, the server profile Consistency state field is set to Consistent and is considered to be compliant Any inconsistency results in an alert for the server profile and the Consistency state field is set to Inconsistent with template ";
f["286"]= " Create an automatically generated ID range for virtual MAC addresses, WWNs, or serial numbers OneView, online help, help, REST API Create an automatically generated ID range for virtual MAC addresses, WWNs, or serial numbers When the appliance starts for the first time, a random range, called the default range, is created for each pool In addition to this range, you can add an automatically generated range Before you create an automatically generated range, you must select an available generated range Each type of range uses a different REST API For example, to create a virtual MAC address range, you use restidpoolsvmac When you create an automatically generated range, the following attributes are required: The start address and end address of the available range obtained through the GET operation The total count NOTE: The range category is generated Prerequisites Minimum required session ID privileges: Network administrator virtual MAC addresses, virtual WWNs Server administrator virtual serial numbers Infrastructure administrator all ID types Creating an automatically generated ID range for virtual MAC addresses using REST APIs Select a generated range that is not in use GET restidpoolsvmacgenerate Create the ID range POST restidpoolsvmacranges Creating an automatically generated ID range for virtual WWNs using REST APIs Select a generated range that is not in use GET restidpoolsvwwngenerate Create the ID range POST restidpoolsvwwnranges Creating an automatically generated ID range for virtual serial numbers using REST APIs Select a generated range that is not in use GET restidpoolsvsngenerate Create the ID range POST restidpoolsvsnranges ";
f["287"]= " Send test email CONTACT CI DOC OWNERS before modifying this content OneView, online help, help, REST API Send test email Use this procedure to test and verify the configuration of email notification of alerts Sending test email using REST API Create a request body: Optionally specify a string for the message body in the textMessageBody Optionally specify a string for the subject line in the subject Designate the recipients by Specify an array of strings for toAddress to designate the recipients Send the test email message: POST restappliancenotificationstestemail ";
f["288"]= " Return codes OneView, online help, help, REST API Return codes Return code Description 2 xx Successful operation 4 xx Clientside error with error message returned 5 xx Appliance error with error message returned NOTE: If an error occurs, indicated by a return code 4 xx or 5 xx, an ErrorMessage is returned The expected resource model is not returned See also:  REST API Response Codes ";
f["289"]= " Accessing Hewlett Packard Enterprise Support This module describes how to contact HPE and access manuals and support services OneView, online help, help, REST API Accessing Hewlett Packard Enterprise Support For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: wwwhpecomassistance To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: wwwhpecomsupporthpesc Information to collect Technical support registration number if applicable Product name, model or version, and serial number Operating system name and version Firmware version Error messages Productspecific reports and logs Addon products or components Thirdparty products or components ";
f["290"]= " Update an alert OneView, online help, help, REST API Update an alert To update an alert, perform a PUT operation to reapply all of the alert attributes View the alert attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes You can update the following attributes: alertState, alertUrgency, notes to add a note, assignToUser Prerequisites Minimum required session ID privileges: Server administrator Updating an alert using REST APIs Select an alert URI GET restalerts Get the alert using the URI from step 1 GET restalerts id Edit the alert Update the alert PUT restalerts id ";
f["291"]= " Resolve connectivity issues between an iPDU and the appliance OneView, online help, help, REST API Resolve connectivity issues between an iPDU and the appliance The appliance automatically synchronizes with iPDUs when they are added, on startup of the appliance, and when it detects changes to the power connections to the iPDU However, if an iPDU becomes out of synchronization with the appliance, you must refresh the connection manually Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator Resolving connectivity issues between an iPDU and the appliance using REST APIs PUT restpowerdevicesidrefreshState ";
f["292"]= " About loop protection OneView, online help, help, REST API About loop protection The loop protection feature enables detection of loops on downlink ports, which can be Flex10 logical ports or physical ports The feature applies when Device Control Channel DCC protocol is running on the Flex10 port HPE OneView network loop protection uses two methods to detect loops: The interconnect periodically injects a loop detection frame into the logical interconnect and analyzes the downlink ports for the looped back detection frame If this detection frame is found on the downlink ports, the server has a loop condition The interconnect reviews and intercepts common loop detection frames used in other switches, such as Cisco and ProCurve to prevent any impact on the upstream switch When network loop protection is enabled on the Logical Interconnects screen, and a loop detection frame is received on a downlink port, the downlink port is disabled immediately until an administrative action is taken The administrative action involves resolving the loop condition and clearing the loop protection error condition The loop detected status on a server can be cleared by editing the server profile and unassigning all networks from the connection corresponding to the server in the loop detected state The SNMP agent supports trap generation when a loop condition is detected or cleared To reset loop protection, see Update logical interconnect settings ";
f["293"]= " Power on or power off server hardware OneView, online help, help, REST API Power on or power off server hardware There are several options for powering on or powering off server hardware For example, when powering off server hardware, you can choose MomentaryPress, PressAndHold, ColdBoot, or Reset Prerequisites Minimum required session ID privileges: Infrastructure administrator Powering on or powering off server hardware using REST APIs Select the server hardware URI GET restserverhardware Get the server hardware power status GET restserverhardware idpowerState Update the server hardware power status PUT restserverhardware idpowerState ";
f["294"]= " Update enclosure capacity settings OneView, online help, help, REST API Update enclosure capacity settings To update the enclosure capacity settings, perform a PUT operation that includes only the calibratedMaxPower attribute View the enclosure capacity settings attributes by using a GET operation, edit the calibratedMaxPower attribute, and then perform a PUT operation that includes only the edited calibratedMaxPower attribute Prerequisites Minimum required session ID privileges: Server administrator Updating enclosure capacity settings using REST APIs Select an enclosure URI GET restenclosures Get the enclosure capacity using the URI from step 1 GET enclosure URIenvironmentalConfiguration Edit the enclosure capacity The only attribute to send in the response body is calibratedMaxPower Do not send all attributes from the GET operation Update the enclosure capacity PUT enclosure URIenvironmentalConfiguration ";
f["295"]= " Add a storage pool storagepoolsall OneView, online help, help, REST API Add a storage pool When you add a storage pool, you perform a GET operation on a specific storage system to view the unmanaged storage pools Prerequisites Minimum required session ID privileges: Infrastructure administrator or Storage administrator You have added at least one storage system Adding a storage pool using REST APIs Select a storage system URI GET reststoragesystems Get the storage system using the URI from step 1 GET reststoragesystems id Select the storage pool or pools that you want to add from the returned unmanagedPools collection Add the storage pools to the storage system POST reststoragepools ";
f["296"]= " About licensing OneView, online help, help, REST API About licensing This topic describes the types of licenses, how to purchase licenses, how licenses are delivered, and how to determine how many licenses you have available License types Purchasing or obtaining licenses License delivery License key format Licensing and utilization statistics Licensing scenarios License reporting License types Server hardware licenses The following types of licenses are available for managing or monitoring hardware in HPE OneView Managed hardware licenses The following HPE OneView Advanced licenses provide support as listed below, and in addition, enable integration with other products HPE OneView Advanced Provides an HPE OneView Advanced license and an iLO Advanced license This license is intended for server hardware and enclosures you want to manage with HPE OneView See Purchasing or obtaining licenses for more information HPE OneView Advanced wo iLO Provides an HPE OneView Advanced license only This license is intended for server hardware you want to manage with HPE OneView This license is for servers with iLOs that are already licensed, or server hardware for which you do not require an iLO license See Purchasing or obtaining licenses for more information An HPE OneView Advanced wo iLO license provides support for all server hardware features on the appliance, with the following exceptions: Server hardware without an iLO Advanced license does not display utilization data Rack mount servers without an iLO Advanced license cannot access the remote console Monitored hardware license HPE OneView Standard Provides an HPE OneView Standard license for all monitored server hardware This license is automatically selected: for the enclosure when adding a monitored enclosure for the server when adding a monitored server for all ProLiant G6 server blades or G7 BL680c server blades when adding a managed enclosure HPE OneView does not manage the hardware running with an HPE OneView Standard license See About monitored c7000 enclosures for more information When you add an enclosure or rack mount server to the appliance, you must specify one of these licenses For examples, see “Licensing scenarios” in the online help More information About HPE OneView Advanced licensing for managing server hardware About HPE OneView Standard licensing for monitoring server hardware EULA The appliance has a EULA EndUser License agreement that you must accept before using the appliance for the first time You can view the EULA from the Help sidebar and online at http:wwwhpecominfoonevieweula About HPE OneView Advanced licensing for managing server hardware This topic provides information about licensing for server hardware including server blades and rack mount servers This section applies to HPE OneView Advanced and HPE OneView Advanced wo iLO licenses only The appliance uses serverbased licensing, but server blades and rack mount servers are managed differently Server blade licenses are managed at the enclosure level, and rack mount server licenses are managed at the server level When you add an enclosure, you specify a license policy for all server blades in the enclosure When you add a rack mount server, you specify a license type for that server Both policy and type refer to either of the two licenses: HPE OneView Advanced or HPE OneView Advanced wo iLO An HPE OneView Advanced wo iLO license provides support for all server hardware features on the appliance, with the following exceptions: Server hardware without an iLO Advanced license does not display  Rack mount servers without an iLO Advanced license cannot access the remote console NOTE: The appliance applies embedded integrated licenses to managed server hardware on which they reside Server blade licensing at the enclosure level A server blade licensing policy at the enclosure level is an efficient way to handle licensing for all servers in an enclosure When you add an enclosure to the appliance, you must choose a server hardware license policy This sets the licensing policy for all server hardware in the enclosure You cannot change the policy for an enclosure unless you remove and readd the enclosure For more information on how the appliance handles enclosure licenses, see About licensing NOTE: A license embedded on a managed server blade will override the enclosure license policy If you add a managed server blade with an embedded license, the appliance assigns the embedded license to that server, regardless of the enclosure license policy Embedded licenses on monitored server hardware are ignored Enclosure licensing policy behavior When you add a managed enclosure to the appliance: You must choose a licensing policy: HPE OneView Advanced or HPE OneView Advanced wo iLO A license embedded on the OA Onboard Administrator is added to the appliance license pool If the server blade does not have an embedded license, the appliance attempts to assign a license from the pool If there are not enough licenses to satisfy the policy, a notification is displayed that instructs you on how to address the issue If you add server blades to the enclosure after it has been added to the appliance, the server hardware will use the enclosure license policy There is no guarantee that an embedded OA license will be applied to the server blades in the enclosure that contains the embedded license Licenses embedded on a server iLO are automatically added to the appliance and applied to the server hardware on which they are embedded If the server hardware has an existing permanent iLO Advanced license, the appliance assigns an HPE OneView Advanced wo iLO license, regardless of the license type you choose To change the server hardware license policy of an enclosure, you must remove the enclosure from management and then readd it with the new license policy When you add server hardware to the appliance, the iLO Advanced license that is part of the HPE OneView Advanced license is applied to the server hardware iLO If a server blade does not have an iLO license and there are not enough of the selected license type available, the appliance will attempt to apply a demo iLO license to the server blade About rack mount server licensing Rack mount server licensing is managed at the server level When you add a rack mount server to the appliance, you must choose a license type You cannot change the license type for a rack mount server unless you remove and readd it NOTE: Embedded licenses take precedent over the license type you choose If you add a rack mount server to be managed with an embedded license, the appliance assigns the license to that rack mount server, regardless of the license type you choose Remote console support is not enabled if the rack mount server does not have an iLO license Rack mount server licensing behavior When you add a managed rack mount server to the appliance: You must choose a license type: HPE OneView Advanced or HPE OneView Advanced wo iLO A license embedded on the rack mount server iLO is automatically added to the appliance and applied to the rack mount server If the server hardware has an existing permanent iLO Advanced license, the appliance assigns an HPE OneView Advanced wo iLO license, regardless of the license type you choose If the rack mount server does not have an embedded license, the appliance attempts to assign a license from the license pool If there are not enough licenses available, a notification is displayed that instructs you on how to address the issue The iLO Advanced license that is part of your HPE OneView Advanced license is applied to the iLO when you add a rack mount server To change the license type of a rack mount server that does not have an embedded license, you must remove the rack mount server from management and then readd it with the new license type About HPE OneView Standard licensing for monitoring server hardware The HPE OneView Standard license applies to only monitored servers and enclosures and cannot be applied to managed servers The HPE OneView Standard license is automatically applied when adding enclosures or server hardware to monitor The HPE OneView Standard license is automatically applied when adding an enclosure to be managed that contains any ProLiant G6 server blades or G7 BL680c server blades These servers are added in a Monitored state Purchasing or obtaining licenses Server hardware licenses HPE OneView requires a license for each server that it manages or monitors For monitored servers or enclosures, an HPE OneView Standard license is automatically applied at no charge For managed servers or enclosures, an HPE OneView Advanced or HPE OneView Advanced wo iLO license is required Purchasing factoryintegrated embedded software and hardware provides the best licensing experience because the Advanced license is delivered on the hardware and HPE OneView automatically adds the licenses to the license pool on discovery of the hardware If you purchase nonintegrated licenses, you must activate and register the licenses using the Hewlett Packard Enterprise licensing portal at https:myenterpriselicensehpecom After you register your licenses, you add the license keys to the appliance For examples, see “Licensing scenarios” in the online help License delivery Server hardware licenses License delivery depends on how the license is purchased The license delivery methods for HPE OneView Advanced and HPE OneView Advanced wo iLO are: Embedded on the server hardware iLO software purchased, integrated with the hardware Embedded on the enclosure OA enclosure bundle license for 16 servers Standalone, nonintegrated purchased separately from the hardware More information About HPE OneView Advanced licensing for managing server hardware License key format For HPE OneView Advanced and HPE OneView Advanced wo iLO, the supported key format is: < encrypted key string> < annotation>_< optional encrypted key string> The encrypted key string is expected to be a series of characternumber blocks separated by spaces The annotation includes space separated fields representing an Hewlett Packard Enterprise sales order number, a product number, a product description, and an EON entitlement order number The iLO Advanced license key string, if present, uses the format: xxxxxxxxxxxxxxxxxxxxxxxxx and is preceded by an underscore _ The HPE OneView Advanced wo iLO license does not include the iLO Advanced license key string Example HPE OneView Advanced key: ABKE C9MA T9PY 8HX2 V7B5 HWWB Y9JL KMPL K6ND 7D5U UVQW JH2E ADU6 H78V ENXG TXBA KFVS D5GM ELX7 DK2K HKK9 DXLD QRUF YQUE BMUF AQF2 M756 9GVQ QZWD LY9B V9ZF BG2B JKTG 2VCB LK4U R4UR V886 3C9X MQT3 G3AD LVKK 5LRG E2U7 GHA3Order1 Number2 HPE OneView_Example_License EON3_35T9XZQR9V716S8TD48PJLBTW Licensing and utilization statistics The appliance gathers and reports utilization statistics for server hardware that has an iLO Advanced license, including monitored servers and enclosures Utilization statistics are not available for server hardware that does not have an iLO Advanced license Licensing scenarios The way in which the appliance handles license assignments depends on the following: Whether the enclosure or server hardware has an embedded license The license type you choose when you add the enclosure or server hardware Whether there are available licenses in the appliance license pool for server hardware without an embedded license The following table describes how the appliance handles licensing for different user actions Licensing scenarios User action License policy or type Result Notes Add a managed enclosure with embedded HPE OneView Advanced or HPE OneView Advanced wo iLO license The embedded license takes precedent over the enclosure license policy you select Embedded OA licenses are added to the appliance pool and applied to server hardware that is not licensed Because the embedded licenses from an enclosure are placed in a pool, these licenses are available to apply to any server managed by the appliance Add managed server hardware with embedded HPE OneView Advanced or HPE OneView Advanced wo iLO license Embedded licenses are applied to the server hardware regardless of the license type you select Embedded licenses are assigned to the server hardware on which they reside   Add managed server hardware with an existing, permanent iLO Advanced license The server hardware will be assigned an HPE OneView Advanced wo iLO license regardless of the license policy or type HPE OneView Advanced wo iLO Licenses available in the pool The appliance assigns a license to the server hardware No HPE OneView Advanced wo iLO licenses available in the pool The appliance issues a warning that there are not enough licenses to satisfy the policy   Add a managed enclosure or server hardware with no embedded license Any Licenses available in the pool The appliance assigns a license to the server hardware No licenses available in the pool The appliance issues a warning that there are not enough licenses to satisfy the policy After the 60day trial period, a message notifies you when there are not enough licenses for the number of managed server hardware Add a managed enclosure with ProLiant G6 or Proliant BL680 G7 servers Any The G6 servers will be assigned an HPE OneView Standard license while the other servers are assigned the HPE OneView Advanced or HPE OneView Advanced wo iLO license you specified   Add enclosure to monitor the hardware All the server hardware in the enclosure will be assigned an HPE OneView Standard license HPE OneView Standard license The appliance automatically assigns this license when adding an enclosure for monitoring the hardware Embedded licenses on monitored server hardware are ignored   Remove a monitored enclosure HPE OneView Standard The license is unassigned from the server hardware   Remove managed server hardware HPE OneView Advanced applied to server hardware The license remains assigned to the server hardware If the server hardware is readded, it will be assigned the same license Removing server hardware with licenses assigned to them can cause the number of licensed servers shown in the licensing graphs to be greater than the number of servers currently being managed because the licenses are still being counted as assigned to server hardware Remove managed server hardware HPE OneView Advanced wo iLO or HPE OneView Advanced license not yet applied to server The license is unassigned from the server hardware   License reporting Basic license reporting indicates whether the appliance has enough licenses for the managed server hardware in your environment More information About HPE OneView Advanced licensing for managing server hardware Licensing ";
f["297"]= " Update internal networks on a logical interconnect OneView, online help, help, REST API Update internal networks on a logical interconnect You can update the Ethernet networks identified as internal networks in a logical interconnect Prerequisites Minimum required session ID privileges: Network administrator Update internal networks in a logical interconnect using REST APIs Select the logical interconnect URI GET restlogicalinterconnects Obtain the URIs of the Ethernet networks you want to identify as internal networks GET restethernetnetworks PUT restlogicalinterconnectsidinternalNetworks ";
f["298"]= " View managed SANs sans OneView, online help, help, REST API View managed SANs After you add a SAN manager, you can view the SANs managed by it SANs are managed imported with the SAN manager as you create networks and associate them with SANs Prerequisites Required session ID privileges: Infrastructure administrator or Storage administrator Viewing a single managed SAN using REST APIs Get a list of managed SANs GET restfcsansmanagedsansid Viewing a list of managed SANs using REST APIs Get a list of managed SANs GET restfcsansmanagedsans ";
f["299"]= " Delete site OneView, online help, help, REST API Delete site Prerequisites Minimum required session ID privileges: Server administrator Delete the site using REST APIs DELETE restsupportsitessiteKey ";
f["300"]= " About Fibre Channel networks OneView, online help, help, REST API About Fibre Channel networks You can use Fibre Channel networks to connect to storage systems Fibre Channel network types Fabricattach Fibre Channel networks Directattach Fibre Channel networks Fibre Channel network types The Virtual Connect interconnects in enclosures support the following types of Fibre Channel networks when connecting to storage systems: Fabricattach networks—The enclosure interconnects connect to data center SAN fabric switches Directattach networks—Also called Flat SAN, in which the enclosure interconnects connect directly to a supported storage system You cannot change the type of Fibre Channel network, but you can delete the network in HPE OneView, and then add the network as a different type A logical interconnect can be defined to use directattach storage and fabricattach storage at the same time Directattach and fabricattach Fibre Channel networks Fabricattach Fibre Channel networks SAN infrastructures typically use a Fibre Channel switching solution involving several SAN switches that implement NPIV NPort ID Virtualization technology NPIV uses Nports and Fports to build a Fibre Channel SAN fabric NPIV enables multiple N_Ports to connect to a switch through a single F_Port, so that a server can share a single physical port with other servers, but access only its associated storage on the SAN When you configure a fabricattach Fibre Channel network, the port you choose for the uplink from the enclosure interconnect to the storage SAN must support NPIV N_Port ID Virtualization You can use Virtual Connect Fibre Channel modules to connect storage The appliance manages up to six Virtual Connect Fibre Channel modules in bays 3 through 8 of an enclosure Virtual Connect Fibre Channel modules are not supported in bay 1 and bay 2 Directattach Fibre Channel networks The directattach Fibre Channel solution, also called the Flat SAN solution, eliminates the need for a connection from the enclosure interconnects to a Fibre Channel SAN switch This means you can connect the enclosure interconnects directly to the 3PAR storage system The directattach Fibre Channel solution is available for 3PAR storage solutions using FlexFabric interconnects Servers connecting to a directattach Fibre Channel network have access to all devices connected on the uplink ports defined for that network If there is more than one connection from a FlexFabric module to the storage system, each server can access as many paths to the storage LUN logical unit number as there are connections to the 3PAR storage system For directattach Fibre Channel networks, the enclosure interconnect does not distribute server logins across uplink ports Server login distribution does not apply to directattach Fibre Channel networks IMPORTANT: If you do not use automated storage provisioning, you must manually update the boot connection when moving a server profile When you move a server profile to a different enclosure and the profile is configured to boot from a directattach storage system, you must manually update the boot connection of the profile to specify the WWPN World Wide Port Name used for the storage system that is directly attached to the enclosure Each enclosure connects to a different port of the directattach storage system, so the WWPN for that storage system is different for each enclosure If you do not specify the correct WWPN and LUN for the storage system, the server will not boot successfully from the boot target ";
f["301"]= " Update a logical interconnect group OneView, online help, help, REST API Update a logical interconnect group To update a logical interconnect group, perform a PUT operation to reapply all of the logical interconnect group attributes View the logical interconnect group attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes Prerequisites Minimum required session ID privileges: Network administrator Updating a logical interconnect group using REST APIs Select a logical interconnect group URI GET restlogicalinterconnectgroups Get the logical interconnect using the URI from step 1 GET restlogicalinterconnectgroups id Edit the logical interconnect group Update the logical interconnect group PUT restlogicalinterconnectgroups id ";
f["302"]= " Create a data center layout OneView, online help, help, REST API Create a data center layout You can add the physical placement of racks in your data center to the data centers resource, including the rotation and coordinates After you add the layout information, a visual representation is available in the appliance UI Prerequisites Minimum required session ID privileges: Server administrator Creating a data center layout using REST APIs Select a data center URI GET restdatacenters Add the layout information to the contents attribute Update the data center PUT restdatacenters id ";
f["303"]= " Edit a logical switch group OneView, online help, help, REST API Edit a logical switch group Prerequisites Minimum required session ID privileges: Network administrator Editing a logical switch group using REST APIs Select a logical switch group URI GET restlogicalswitchgroups Get the logical switch group using the URI from step 1 GET restlogicalswitchgroups id Edit the logical switch group Update the logical switch group PUT restlogicalswitchgroups id ";
f["304"]= " Delete a data center OneView, online help, help, REST API Delete a data center When you delete a data center, it is no longer managed by the appliance Prerequisites Minimum required session ID privileges: Server administrator Deleting a data center using REST APIs Select a data center URI GET restdatacenters Delete the data center using the URI from step 1 DELETE restdatacenters id ";
f["305"]= " Edit a logical switch OneView, online help, help, REST API Edit a logical switch Prerequisites Minimum required session ID privileges: Network administrator Editing a logical switch using REST APIs Select a logical switch URI GET restlogicalswitches Get the logical switch using the URI from step 1 GET restlogicalswitches id Edit the logical switch Update the logical switch PUT restlogicalswitches id ";
f["306"]= " Unmanaged Devices OneView, online help, help, REST API Unmanaged Devices Use REST APIs to  Create an unmanaged device Read an unmanaged device Update an unmanaged device See more tasks Learn more About unmanaged devices unmanageddevices REST APIs ";
f["307"]= " Migrate a c7000 VCM enclosure using REST API OneView, online help, help, REST API Migrate a c7000 VCM enclosure using REST API An enclosure managed by Virtual Connect Manager VCM can be migrated into HPE OneView through the UI or through REST API The Virtual Connect VC enclosure can be migrated to a new enclosure group or an existing enclosure group VCEMmanaged enclosures can be migrated to HPE OneView through the VCEM GUI or a PowerShell module See Prepare a VCEM enclosure for migration into HPE OneView for more information More information “Planning for enclosure migration from VCM into HPE OneView” in the HPE OneView User Guide About migrating c7000 enclosures managed by other management systems Prerequisites Required privileges: HPE OneView Infrastructure administrator, Onboard Administrator, and VCM Domain Administrator OA and VCM credentials as well as the OA IP address for the enclosure For VCEMmanaged enclosures: VCEM credentials to remove the Virtual Connect domain from the domain group using the VCEM web interface, or the HPE PowerShell module See Prepare a VCEM enclosure for migration into HPE OneView for more information Back up and secure the VCM configuration including the output from show config includepoolinfo See VCM configuration backup acknowledgment for more information Review the HPE OneView Support Matrix and verify the enclosure contains supported servers, interconnect modules, and mezzanine cards Assign server profiles before the migration or recreate server profiles after the migration, if applicable See Server profile acknowledgment for more information Ensure network connectivity with OA and iLOs in the Virtual Connect domain Ensure all interconnect modules are present and powered on within the enclosure Migrating a VCM enclosure using REST APIs Determine if a migration is already in progress GET restmigratablevcdomains A collection of compatibility reports are returned along with the number of concurrently executing migrations and the ability to create a compatibility report or migrate an enclosure while other operations are in progress The migratabilityState must be MigrationValid to continue Validate the enclosure configuration POST restmigratablevcdomains See restmigratablevcdomains for a list of required URIs The enclosure VCM IP address is retrieved from Onboard Administrator OA The following URIs are optional For enclosure group, do one of the following: If you want to migrate the enclosure into an existing enclosure group, use enclosureGroupUri If you want to migrate the enclosure into a new enclosure group, the enclosure group name is automatically generated based on the serial number A tasksid is returned identifying the compatibility report NOTE: GET resttasksid until the validation task is completed Once the task has completed, a restmigratablevcdomainsid URI is returned Retrieve a compatibility report using a restmigratablevcdomainsid URI obtained in step 2 GET restmigratablevcdomainsid Does the report indicate errors Yes, resolve compatibility errors Repeat step 3 until all blocking issues are resolved No, continue to the next step Is this an offline migration Yes, power off the servers in the enclosure that is being migrated, and run a final compatibility report No, run a final compatibility report Respond to the acknowledgments and import the VC enclosure PUT restmigratablevcdomainsid Include migrationState set to Migrated and AcknowledgementKey for each acknowledgment The migration for the current enclosure is started Do you want to migrate another enclosure Yes Go to step 1 No, proceed to the next step Check for the completion of the migrations GET restmigratablevcdomains The migrationSubState shows Completed If not, follow the proposed resolution Perform postmigration tasks Perform postmigration tasks Was the migration an offline migration Yes, power on the servers in the migrated enclosure No, proceed to the next step Optional: Recreate server profiles in HPE OneView, if server profiles were not assigned to server hardware before migration Recreate the server profiles using the information from the VCMCLI show config –includepoolinfo captured before the migration Enter the MAC, WWN, Serial Number, UUID information as “user specified” to retain the same values in HPE OneView that were present in the VCM server profile Perform the following best practices: Back up the new configuration in HPE OneView Test network and storage connectivity Plan a reboot if one of the acknowledgements, such as an SRIOV virtual function configuration, indicated a change which would impact your operation NOTE: During an inservice migration, some changes do not take effect until the servers are rebooted for the first time following a migration Resolve compatibility issues The migration tool detects if the features and hardware within a VCMmanaged enclosure are compatible with HPE OneView Each detected issue is grouped into a category such as hardware, domain, logical interconnect group, or server profile to identify the part of the Virtual Connect domain or HPE OneView system that is impacted An issue is also given one of the following compatibility issue levels Medium An issue has been identified where you may lose some functionality, but the functional loss would not be significant Within the report, both Medium and High issues are denoted as a warning High The issue identified is considered serious Depending on how you use the feature, there may be significant consequences Determine whether to resolve this issue before continuing with the migration Critical The issue identified is likely to cause an outage if the migration were to continue This is a blocking issue and must be resolved before continuing with the migration Resolving compatibility issues Review each issue and suggested resolution NOTE: If performing an offline migration, resolve all nonpower related issues first before powering down the server to limit application downtime Evaluate warnings to determine if action needs to be taken If the warning indicates that the issue will affect your use of the configuration, then take action Otherwise, the warning can be ignored Resolve all blocking migration errors by modifying the configuration in VCM or HPE OneView Resolving an issue may require disabling a feature within Virtual Connect, changing a configuration in Virtual Connect, or in some cases, changing the HPE OneView logical interconnect group For example, if there is a mismatch with uplink sets and one of those uplink sets already exists in HPE OneView and 10 enclosures with the same configuration are to be migrated into the same enclosure group, update the uplink set in HPE OneView Reexecute the test compatibility report until all blocking issues are resolved Continue with the migration process More information About blocking issues during migration About migrating c7000 enclosures managed by other management systems ";
f["308"]= " Troubleshooting the appliance OneView, online help, help, REST API Troubleshooting the appliance Use REST APIs to  Troubleshoot restore and backup Recover from an unexpected appliance shutdown Learn more See the HPE OneView Help ";
f["309"]= " About backing up the appliance OneView, online help, help, REST API About backing up the appliance HPE OneView provides the ability to save your configuration settings and management data to a backup file and enables you to use that backup to restore a corrupted appliance in the event of a catastrophic failure The backup process involves creating a backup file and then downloading that file so that you can store it to a safe and secure offappliance location for future use You can schedule automatic backup operations and designate a remote location for the backup file For advice on creating and archiving a backup file, see Best practices for backing up an appliance IMPORTANT: In the unlikely event you need to restore the appliance, Hewlett Packard Enterprise recommends backing up your appliance configuration on a regular basis, preferably daily and especially: After adding hardware After changing the appliance configuration Before and after updating the appliance firmware To prevent a backup file from being overwritten or deleted, download it and save it to an offappliance location before running the next backup process The appliance stores one backup file or one support dump file on the appliance at a time Creating a backup file replaces the current backup file or support dump file Likewise, creating a support dump file replaces the previous support dump or the backup file If you start a backup while a support dump is in progress, the backup operation does not proceed until the support dump operation completes If you as the Infrastructure administrator start a support dump while a backup operation is in progress, you have the option of cancelling the backup and proceeding with the support dump HPE OneView provides a Backup administrator user role specifically for backing up the appliance by permitting access to other resource views without permitting actions on those resources, or other tasks Only the Infrastructure administrator or the Backup administrator can create a backup file, either through the UI or REST APIs What the backup process backs up What the backup process does not back up HPE OneView database System files: Nondatabase data Audit log License files Nondata files: Static files that are installed as part of the execution environment, and are not specific to the appliance or managed environment configuration Log files except the Audit log file Appliance network configuration Firsttime setup configuration files Firmware bundles Any server settings, such as the following, that HPE OneView has not set: Boot and BIOS configuration settings SAN and Local storage configurations Network configurations Settings such as these are neither validated by nor persisted by HPE OneView Use a backup file to do the following: Restore the appliance from which the backup file was created Restore the settings to a different appliance For example, if an appliance fails and cannot be repaired, you can use a backup file to restore the management configuration settings and management data to a replacement appliance created from the same version of the virtual machine image REST APIs let you: Schedule a backup process from outside the appliance Collect backup files according to your site policies Integrate with enterprise backup and restore products ";
f["310"]= " About user accounts OneView, online help, help, REST API About user accounts Rolebased access The appliance provides default roles to separate responsibilities in an organization A user role enables access to specific resources managed from the appliance Rolebased access control enforces permissions to perform operations that are assigned to specific roles You assign specific roles to system users or processes, which gives them permission to perform certain system operations Because a user is not assigned permissions directly, but instead acquires them through their role or roles, individual user rights are managed by assigning the appropriate roles to the user At initial appliance startup, there is a default administrator account with full access Infrastructure administrator privileges For more information about the actions each role can perform, see Action privileges for user roles Local authentication You can add a user authorized to access all resources managed by the appliance full access user or add a user who has access based on their job responsibilities rolebased specialist For each of these users, authentication is confirmed by comparing the user login information to an authentication directory hosted locally on the appliance The default administrator login for the appliance is automatically assigned with full access Infrastructure administrator privileges Directorybased authentication You can add a user authorized by membership to access all resources managed by the appliance full access user or add a user authorized by membership who has access based on their job responsibilities rolebased specialist For each of these users, authentication is confirmed by comparing the user login information to an enterprise directory ";
f["311"]= " Create an unassigned server profile to use as a template OneView, online help, help, REST API Create an unassigned server profile to use as a template Prerequisites Minimum required session ID privileges: Server administrator Added enclosure that includes a server blade without a server profile Creating an unassigned server profile using REST APIs Get a server hardware type URI GET restserverhardwaretypes Select the enclosure group URI GET restenclosuregroups Select the BIOS settings for the server hardware GET restserverhardwaretypes id Get available server ports using the server hardware type URI and enclosure group URI GET restserverprofilesprofileportsserverHardwareTypeUri= uri&enclosureGroupUri= uri Select the network URIs for the server profile connections using the server hardware type URI and enclosure group URI GET restserverprofilesavailablenetworksserverHardwareTypeUri= uri&enclosureGroupUri= uri Select the firmware URI you prefer to apply GET restfirmwaredrivers Get available ports for the server hardware type and enclosure POST restserverprofilesprofileportsserverHardwareTypeUri= uri&enclosureGroupUri= uri Create the server profile with the information from the previous steps POST restserverprofiles ";
f["312"]= " Resource operations OneView, online help, help, REST API Resource operations RESTful APIs are stateless The resource manager maintains the resource state that is reported as the resource representation The client maintains the application state and the client might manipulate the resource locally, but until a PUT or POST is made, the resource as known by the resource manager is not changed Operation HTTP Verb Description Create POST resource URI payload = resource data Creates new resources A synchronous POST returns the newly created resource An asynchronous POST returns a TaskResource URI in the Location header This URI tracks the progress of the POST operation Read GET resource URI Returns the requested resource representations Update PUT resource URI payload = update data Updates an existing resource PATCH resource URI payload = update data Updates a part of the resource For example, when you only need to update one field of the resource Delete DELETE resource URI Deletes the specified resource ";
f["313"]= " Enable offappliance browsing of UI help and REST API help OneView, online help, help, REST API Enable offappliance browsing of UI help and REST API help The offappliance versions of the HPE OneView help systems are useful for developers who are writing REST API scripts or other users who prefer the convenience of accessing help locally without logging in to the appliance NOTE: You can also browse the API Reference at http:wwwhpecominfooneviewdocs Downloading HTML UI help and HTML REST help Go to the Enterprise Information Library: http:wwwhpecominfooneviewdocs Select the HPE OneView online help and API Reference download zip and save it to your computer or to a local directory on a web server Use the utility of your choice to extract the contents of the zip file Navigate to the content directory Doubleclick the indexhtml file to open the HPE OneView help system ";
f["314"]= " Create a server profile template OneView, online help, help, REST API Create a server profile template Prerequisites Minimum required session ID privileges: Server administrator A managed enclosure that includes a blade server without a server profile template or a rack server under management without a server profile template Creating a server profile template using REST APIs Identify a server hardware type and enclosure group for which the server profile template will be created Select the BIOS settings for the server hardware using the associated server hardware type URI To retrieve the available values from the given server hardware type: GET restserverhardwaretypes id Get available server ports using the server hardware type URI and enclosure group URI GET restserverprofilesprofileportsserverHardwareTypeUri= uri&enclosureGroupUri= uri Select the network URIs for the server profile connections using the server hardware type URI and the enclosure group URI GET restserverprofilesavailablenetworksserverHardwareTypeUri= uri&enclosureGroupUri= uri NOTE: If you are attaching SAN storage, you can select connections that are associated with the storage system See step 7 Select the firmware URI you prefer to apply GET restfirmwaredrivers Define the local storage settings for the server based on the storage capabilities from the associated server hardware type Retrieve the available local storage capabilities from the given server hardware GET restserverhardwaretypes id Select the OS type used by the storage attachments Optional Only apply to attach SAN storage GET reststoragesystemshosttypes Select storage volumes that are visible to that server hardware typeenclosure group Optional Only apply to attach SAN storage For each storage volume that you want to attach, you need the associated storage system URI and storage pool URI This information is returned in the response body GET restserverprofilesavailablestoragesystemscount=25&start=0&enclosureGroupUri= uri&serverHardwareTypeUri= uri Create the server profile template with the information from the previous steps POST restserverprofiletemplates ";
f["315"]= " Refresh the connection between an enclosure and the appliance OneView, online help, help, REST API Refresh the connection between an enclosure and the appliance If an enclosure has lost connectivity or is not synchronized with the appliance, you must refresh the connection An enclosure can lose connectivity with the appliance during normal operation; it can become not synchronized with the appliance if you make changes to it through the OA or iLO To prevent loss of connectivity, make changes to an enclosure through the appliance Prerequisites Minimum required session ID privileges: Infrastructure administrator Refreshing the connection between an enclosure and the appliance using REST APIs PUT restenclosures idrefreshState NOTE: To track the progress of the refresh operation, use the TaskResource URI that is returned after the PUT operation See Read the status of a task ";
f["316"]= " Update a rack OneView, online help, help, REST API Update a rack To update a rack, perform a PUT operation to reapply all of the rack attributes View the rack attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes Prerequisites Minimum required session ID privileges: Server administrator Updating a rack using REST APIs Select a rack URI GET restracks Get the rack using the URI from step 1 GET restracks id Edit the rack Update the rack PUT restracks id ";
f["317"]= " Replace a c7000 enclosure OA and midplane OneView, online help, help, REST API Replace a c7000 enclosure OA and midplane When you replace an enclosure OA and midplane, most of the steps that you need to perform are done without using the appliance REST APIs Before you replace the OA, back up the configuration settings You will use these configuration settings to reconfigure the new OA To physically replace the OA and midplane, and prepare the enclosure for operational status, follow the prerequisites and refer to the service guide for your enclosure to complete the replacement After you physically replace and reconfigure the OA and midplane, you must perform a refresh on the enclosure using a REST API Prerequisites Minimum required session ID privileges: Infrastructure administrator The enclosure Onboard Administrator OA user name and password Settings of enclosure of the OA that you are replacing UUID of enclosure midplane that you are replacing Physically replace the enclosure OA and midplane using the service guide instructions for your enclosure Ensure the new midplane is reconfigured Reconfigure the new OA to match the settings the OA that you are replacing Refreshing the enclosure using REST APIs PUT restenclosures idrefreshState NOTE: To track the progress during the enclosure refresh, you can use the task resource that is returned after the PUT operation ";
f["318"]= " Edit a server profile template OneView, online help, help, REST API Edit a server profile template Prerequisites Minimum required session ID privileges: Server administrator Editing a server profile template using REST APIs Get the server profile template you want to edit GET restserverprofiletemplatesid Make the changes Create a new server profile template PUT restserverprofiletemplatesid ";
f["319"]= " Customer self repair This module is for the boilerplate CSR information OneView, online help, help, REST API Customer self repair Hewlett Packard Enterprise customer self repair CSR programs allow you to repair your product If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience Some parts do not qualify for CSR Your Hewlett Packard Enterprise authorized service provider will determine whether a repair can be accomplished by CSR For more information about CSR, contact your local service provider or go to the CSR website: wwwhpecomsupportselfrepair ";
f["320"]= " About storage systems storagesystemsall OneView, online help, help, REST API About storage systems A storage system or storage array is a storage device from which logical disks volumes can be provisioned and mapped or masked to servers Bringing SAN storage systems under management of the appliance enables you to add and create volumes You can then attach volumes to server profiles through volume attachments This enables the server hardware assigned to the server profiles to access the SAN storage system When adding a storage system, you must choose a domain on the storage system You can then select storage pools from that domain on the storage system to add to the appliance After you add storage pools, you can assign networks to the storage ports associated with the storage system See the HPE OneView Support Matrix for a list of supported storage systems About HPE 3PAR StoreServ Storage systems You can connect supported HPE 3PAR StoreServ Storage systems to the appliance You must configure a 3PAR system using the 3PAR software to bring it under management of the appliance Partner port states Port state Definition Equivalent 3PAR state none Normal state, not failed over none failing over The port is offline and is in the process of failing over to the partner port failover_pending failed over The port is offline and has failed over to the partner port failed_over failed The port is off offline and cannot fail over to the partner port active_down recovering The port is online and in the process of returning to a normal state failback_pending partner port failed over The partner port has failed over and the port is the partner port traffic active partner failed The partner port has failed and the fail over operation was not successful active_down ";
f["321"]= " Files you can download from the appliance CONTACT CI DOC OWNERS before modifying this content CIC int, features, product description, reference, security, roles OneView, online help, help, REST API Files you can download from the appliance You can download the following data files from the appliance: Support dump By default, all data in the support dump is encrypted and accessible by an authorized support representative only Backup file All data in the backup file is in a proprietary format Hewlett Packard Enterprise recommends that you encrypt the file according to your organization's security policy Audit logs Session IDs are not logged, only the corresponding logging IDs are logged Passwords and other sensitive data are not logged ";
f["322"]= " Add an external storage volume storagevolumesall OneView, online help, help, REST API Add an external storage volume You can add to the appliance a storage volume that exists on a storage system under management of the appliance Prerequisites Minimum required session ID privileges: Infrastructure administrator or Storage administrator The appliance manages the storage system and storage pool that contains the storage volume you want to add Add an external storage volume using REST APIs Select a storage system URI GET reststoragesystems Select a storage pool from the storage system URI you selected in step 1 GET storage system URIstoragepools Add the storage volume with the information from the previous steps POST reststoragevolumes ";
f["323"]= " About logical interconnect groups OneView, online help, help, REST API About logical interconnect groups About multiple logical interconnect groups in an enclosure group About copying a logical interconnect group About uplink sets in a logical interconnect group About Link Layer Discovery Protocol LLDP tagging About enhanced typelengthvalue TLV structure One or more logical interconnect groups are associated with an enclosure group and are used to define the logical interconnect configuration for every enclosure that is using that enclosure group Logical interconnect group configurations include the IO bay occupancy, uplink sets, available networks based on the uplink sets and internal networks, and downlinks All references to a logical interconnect group by an enclosure group or logical interconnect must be removed before you can delete the logical interconnect group About multiple logical interconnect groups in an enclosure group Multiple logical interconnect groups can be associated with one enclosure group The advantages of using multiple logical interconnect groups in an enclosure group are: Having airgap separation between Ethernet networks to allow isolation of network traffic Eliminating the need for stacking cables between interconnects, freeing uplink ports for data center traffic Doubling the number of networks in an activeactive configuration See About activeactive and activestandby configurations for more information Logical interconnect group requirements Interconnects in horizontally adjacent bays must contain the same interconnect type or an empty bay When to create a logical interconnect group By default, a single logical interconnect group containing all the interconnects in the enclosure is automatically created when you add an enclosure, unless you create the logical interconnect groups before adding the enclosure If you want to have multiple logical interconnects in an enclosure: Create logical interconnect groups with the interconnects that you want in each logical interconnect Add the logical interconnect groups to an enclosure group Add the enclosure using the enclosure group About copying a logical interconnect group To streamline the creation of logical interconnect groups, you can copy existing logical interconnect groups When you copy a logical interconnect group, all the settings, uplink sets, and networks copy to the new group The new group is not associated automatically with enclosure groups or logical interconnects After copying a logical interconnect group, you can edit the logical interconnect group or associate it to an enclosure group For example, you have an existing logical interconnect group and you want a new group with the same settings, except a different internal network Copy the existing logical interconnect group, and then edit the new logical interconnect group to change the internal network More information “Copy a logical interconnect group” in the online help About uplink sets in a logical interconnect group The uplink sets portion of the logical interconnect group defines the initial configuration for uplink sets for each logical interconnect in the enclosure group If you change the uplink sets for an existing logical interconnect group, only enclosures that you add after the configuration change are configured with the new uplink set configuration Changing uplink sets in a logical interconnect group makes the logical enclosure and logical interconnects associated with it inconsistent with the logical interconnect group Select Update from group to bring the logical enclosure and logical interconnect back into compliance with the changes made to the logical interconnect group About Link Layer Discovery Protocol LLDP tagging Link Layer Discovery Protocol LLDP information is sent by devices at a fixed interval in the form of an Ethernet frame Each frame contains one LLDP Data Unit LLDPDU Each LLDPDU is a sequence of typelengthvalue TLV structures Untagged LLDP frames By default, Virtual Connect interconnects use untagged LLDP frames to advertise their identity and learn about their link partners LLDP advertises the Virtual Connect interconnect’s management IP addresses to uplink, downlink, and stacking link ports LLDP frames also identify stacking links in a logical interconnect The IPv4 address and IPv6 address if enabled are used as the LLDP management address TLV Tagged LLDP frames LLDP can also be used to communicate with a virtual switch in the hypervisor through the use of tagged LLDP frames on downlink ports The tagged frame contains the VLAN ID that identifies the subport of the configured FlexNIC This information is used to build the network topology LLDP tagging can be enabled or disabled through the HPE OneView UI or REST API More information Enable or disable LLDP tagging using REST APIs About logical interconnect groups About logical interconnects About enhanced typelengthvalue TLV structure Enhanced TLV is part of the Link Layer Discovery Protocol LLDP exchange of information between interconnects Enhanced TLV determines what is contained on the Chassis ID TLV of LLDP frames sent out by an interconnect Enhanced TLV can be enabled or disabled through the HPE OneView UI or REST API Enable The Chassis ID TLV advertises the enclosure name and serial number to other interconnects Disable The Chassis ID TLV contains the switch MAC address Enhanced TLV values Enable enhanced TLV format System name  <hostname> <serial number>BAY: <bay_number> Chassis ID ENC: <enclosure_name>:SERIAL NO: <enclosure_serial_number> Part description  <op_speed> <connector_type> Disable enhanced TLV format System name  <hostname> Chassis ID  <switch_mac_address> Part description  IFMIB::ifDescr value, for example HPE VC FlexFabric 10Gb24–Port Module 410 X1 More information Enable or disable enhanced TLV support using REST APIs About logical interconnect groups About logical interconnects ";
f["324"]= " URI format OneView, online help, help, REST API URI format All URIs point to resources The client does not need to create or modify URIs The URI for a resource is static and uses the format https: applrest resource category resource ID where: https: appl The appliance address rest The type of URI  resource category The category of the resource for example, serverprofiles  resource instance ID The specific resource instance identifier optional ";
f["325"]= " About SANs sans OneView, online help, help, REST API About SANs SANs are Fibre Channel FC or Fibre Channel over Ethernet FCoE storage area networks that connect servers to storage systems The possible states for SANs are: Discovered A SAN that is not associated with a network SANs are automatically discovered when a SAN manager is added to HPE OneView Managed A SAN that is associated with one or more networks in HPE OneView Only managed SANs can be configured to be automatically zoned by HPE OneView Directattach SANs  HPE OneView creates a directattach SAN flat SAN automatically when you configure an enclosure with a logical interconnect that contains a directattach uplink set HPE OneView names the directattach SAN using the format <interconnect><uplink set> The SAN that HPE OneView creates is a Fibre Channel FC directattach SAN that is not zoned, and cannot be edited NOTE: HPE OneView creates a SAN for each interconnect module that is connected to a directattach Fibre Channel network About SAN zoning Zoning policy A SAN zone enables communication between devices connected to the SAN SAN zoning policies determine how zoning should be configured on a SAN SAN zoning policies define whether or not zoning is automated as well as the naming format of zones and aliases In HPE OneView, you can specify the name format of the zones and aliases that will be created when you associate a storage volume to a server profile via a volume attachment By specifying zone name and alias formats using text strings and server profile objects, you can create names that are meaningful and conform with your naming conventions NOTE: HPE OneView performs zoning only when you add a connection to a server profile and attach a SAN storage volume to it When you do this, HPE OneView will determine if the current zoning allows connectivity If current zoning does not allow connectivity, HPE OneView will create the necessary zoning based on the specified zoning policy Automate zoning  Automated zoning enables HPE OneView to automatically create, edit, and delete zones on a zoned SAN when you attach storage volumes to servers through a volume attachment in a server profile Yes Zoning is automated HPE OneView takes full control of the zone naming and contents based on the zoning policy for the SAN Use automated zoning when you want HPE OneView to configure new zones for volume attachments to server profiles Existing zones are not modified unless the SAN storage attributes defined in a server profile change No Zoning is not modified by HPE OneView You must manually manage zoning ";
f["326"]= " About racks OneView, online help, help, REST API About racks A rack is a physical structure that contains IT equipment such as enclosures, servers, power delivery devices, and unmanaged devices an unmanaged device uses slots in the rack and consumes power or exhausts heat, but it is not managed by the appliance You can manage your racks and the equipment in them by adding them to the appliance Having your racks managed by the appliance enables you to use the appliance for space and power planning The appliance also gathers statistical data and monitors the power and temperature of the racks it manages When you add an enclosure to the appliance, it automatically creates a rack and places the enclosure in it The appliance places into the rack all enclosures connected by management link cables When enclosures are added, the appliance places them in the rack from top to bottom When an enclosure is placed in an Intelligent Series Rack, the enclosure slots are automatically detected For other racks, to accurately depict the layout of your enclosures within the rack you must edit the rack to place the enclosure in the proper slots You can use the appliance to view and manage your rack configuration and power delivery topology You can specify the physical dimensions of the rack width, height, and depth, the number of U slots, and the location of each piece of equipment in the rack You can specify the rack PDUs that provide power to the rack, and their physical position in the rack or on either side You can also describe how the devices in the rack are connected to those PDUs The appliance automatically discovers the rack height and rack model for a ProLiant server with Location Discovery Services and updates the physical locations of devices when they are relocated within and between racks for c7000 enclosures NOTE: When the appliance discovers HPE Intelligent Series Racks, it sets the rack height automatically using the Intelligent Rack Location Discovery Services for c7000 enclosures For nonintelligent racks or for empty racks, the default rack height is 42U After adding a rack to the appliance for management, you can add the rack to a data center to visualize the data center layout and to monitor device power and cooling data After the rack is under management, you can configure the power delivery topology with redundant and uninterruptible power supplies to the devices in the rack Changing a rack name The way a rack is named and how you change the name of a rack depends on how it was added to the appliance Rack naming Add method Initial naming method Name change method Automatically added when the appliance discovers an enclosure the rack contains for c7000 enclosures Defined by enclosure OA Change rack name from enclosure OA Automatically discovered from a ProLiant server with Location Discovery Services for c7000 enclosures Assigned using rack serial number as rack name Update a rack Manually from the Racks screen Manually using the restracksid REST API Defined by the user Update a rack ";
f["327"]= " Download audit logs OneView, online help, help, REST API Download audit logs The audit log helps the security administrator understand what securityrelated actions took place You can gather log files and other information that your authorized support representative needs so that they can diagnose and troubleshoot an appliance Prerequisites Minimum required session ID privileges: Infrastructure administrator Downloading audit logs using REST APIs GET restauditlogsdownload NOTE: To filter only specific audit log entries, you can use GET restauditlogs with the optional filter parameter ";
f["328"]= " Configure the appliance OneView, online help, help, REST API Configure the appliance After you install the appliance image, you must accept the End User License Agreement EULA, and enable or disable authorized support access optional Next, change the default administrator password for the appliance and configure the network connections When you configure the network connections on the appliance using a REST API POST operation that includes all of the networking settings, the appliance starts You can now import enclosures and start managing your data center environment To monitor and verify successful appliance configuration, you use the task API Reference the TaskResource URI that is returned after you post the network configuration using the networkinterfaces REST API Use REST APIs to  Accept the End User License Agreement EULA Change the default administrator password Configure the network Update the SNMP read community string For information about the appliance resource, see the HPE OneView REST API Reference Accept the End User License Agreement EULA Before you log in to the appliance for the first time, you must accept the EULA During this step you can enable or disable authorized support access Support access is enabled by default After the appliance is configured, you can use this REST API to enable or disable authorized support access Accepting the End User License Agreement EULA using REST APIs POST restapplianceeulasave Change the default administrator password The first time you log in to the appliance, you must change the default administrator password Log in using the default administrator password, and then use the returned session ID to change the password Prerequisites Default administrator password Changing the default administrator password using REST APIs Log in to the appliance using the default administrator password userName: Administrator password: admin POST restloginsessions Change the default administrator password POST restuserschangePassword Configure the network Log in to the appliance as an administrator and create a REST request that includes the network information provided by your network administrator After you POST the network configuration using the restappliancenetworkinterfaces API, a TaskResource URI is returned in the Location header Use the TaskResource URI to track the progress When the network configuration is complete, the appliance starts You can also configure both the network as well as time and place settings using the restappliancenetworkinterfaces API You can change these settings together or separately using the restappliancenetworkinterfaces API The time and language settings include the NTP server settings Best practices Always use static IP addresses when configuring the appliance Use of DHCP addresses is not recommended unless the DHCP server is configured so that the same addresses are always assigned to the appliance Use of randomly assigned DHCP addresses is not supported and will result in connectivity issues when the DHCP server changes the address assigned to the appliance Prerequisites Minimum required session ID privileges: Infrastructure administrator A virtual appliance connected to the network Network information provided by your Network administrator, such as the IP address and host name for the appliance, DNS name servers, subnet, and gateway Configuring the network using REST APIs POST restappliancenetworkinterfaces NOTE: If you are setting up multiple network interfaces, provide the network interfaces information for all networks in the REST API POST operation Change to a dualstack protocol To change the appliance from an IPv4 protocol to dualstack to run both IPv4 and IPv6 protocols, update the appliance network setting Prerequisites Minimum required session ID privileges: Infrastructure administrator A virtual appliance connected to the network Changing to a dualstack protocol using REST APIs Get the network settings GET restappliancenetworkinterfaces Change the ipv6​Type attribute to DHCP Update the network settings POST restappliancenetworkinterfaces Update the SNMP read community string The SNMP read community string is used by the appliance to communicate with the managed devices If you use the REST APIs to update the SNMP read community string for an appliance that has managed devices, you must also refresh the managed devices Prerequisites Minimum required session ID privileges: Infrastructure administrator Updating the SNMP read community string using REST APIs Get the read community string GET restappliancedevicereadcommunitystring Edit the communityString attribute Update the SNMP read community string POST restappliancedevicereadcommunitystring Refreshing the connections between the enclosures and the appliance Get a list of the enclosure IDs GET restenclosures For each enclosure ID, refresh the connection between the enclosure and the appliance Refreshing the connections between the rack mount servers and the appliance Get a list of the rack mount server IDs GET restserverhardwarefilter=position=0 For each rack mount server ID, refresh the connection between the server and the appliance See also  Quick Start: Initial configuration using REST APIs top of chapter ";
f["329"]= " About email notification of alert messages OneView, online help, help, REST API About email notification of alert messages You can configure the appliance to send an email message to notify you or others when an alert is generated With this feature, an alert is compared against specified filter search criteria and, if it matches, the text of the alert message is sent as email to previously specified recipients You can verify the configuration by sending test messages The appliance provides for as many as 100 recipient and filter combinations, and there can be as many as 50 recipients in a single email message With this flexibility, you can finetune which alert messages are sent and to whom For example, you can configure the appliance to send Warning alerts to one recipient and Critical alerts to another Filters have the same syntax as the Smart Search box in the Activity screen, so you can copy and paste that information The appliance sends the email message in both plain text and HTML MIME types, which allows the recipient’s mail application to determine how they are displayed You can enable or disable this email notification feature, or you can enable or disable individual filter notifications, as required ";
f["330"]= " Delete a channel partner OneView, online help, help, REST API Delete a channel partner Prerequisites Minimum required session ID privileges: Server administrator Deleting a channel partner using REST APIs DELETE restsupportchannelpartnerspartnerKey ";
f["331"]= " About logical enclosures OneView, online help, help, REST API About logical enclosures A logical enclosure represents a logical view of a single enclosure with an enclosure group serving as a template If the intended configuration in the logical enclosure does not match the actual configuration on the enclosures, the logical enclosure becomes inconsistent Use the Logical Enclosures screen to manage firmware, configuration scripts, create a support dump, and to apply updates made from the Enclosure Groups screen to the enclosures in the logical enclosure A logical enclosure is automatically created when a c7000 enclosure is added About inconsistent logical enclosures A logical enclosure can become inconsistent in the following cases: The enclosure group referenced by the logical enclosure or the logical enclosure configuration script has been modified For example, a logical interconnect group has been added, modified, or removed from the enclosure group The logical interconnects are inconsistent with the logical interconnect groups Any other logical enclosure configuration is inconsistent with the enclosure group There are extra or missing logical interconnects when compared to the enclosure group's inventory of logical interconnect groups More information Update enclosures in the logical enclosure from the enclosure group About updating firmware from a logical enclosure You can update firmware from a logical enclosure for shared infrastructure, shared infrastructure and profiles, and OA Onboard Administrators only, if any When you update the firmware for an enclosure associated with a logical enclosure, the firmware baseline configured for the logical enclosure sets the baseline on the enclosure and each of the logical interconnects in the enclosure, as well as the OA From the Logical Enclosures screen, you can initiate firmware updates Firmware is updated in the following order: Onboard Administrators Logical interconnects Server hardware and their associated server profiles More information Update the firmware in a logical enclosure ";
f["332"]= " Update a storage volume storagevolumesall OneView, online help, help, REST API Update a storage volume To update a storage volume, perform a PUT operation to reapply all of the storage volume attributes View the storage volume attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes Only name, description, shareable, and provisionedCapacity can be updated provisionedCapacity can only be increased, not decreased Prerequisites Minimum required session ID privileges: Infrastructure administrator or Storage administrator Updating a storage volume using REST APIs Select a storage volume URI GET reststoragevolumes Get the storage volume using the URI from step 1 GET reststoragevolumes id Edit the storage volume Update the storage volume PUT reststoragevolumes id ";
f["333"]= " Read the power configuration of a rack OneView, online help, help, REST API Read the power configuration of a rack You can view the attributes associated with the power capacity and allocation of a specific rack Prerequisites Minimum required session ID privileges: Server administrator Reading the power configuration of a rack using REST APIs Select a rack URI GET restracks Get the rack power configuration GET restracks iddeviceTopology Look at the fields max and capacity for utilization information ";
f["334"]= " Download a logical enclosure support dump OneView, online help, help, REST API Download a logical enclosure support dump A logical enclosure support dump file includes content from each member logical interconnect After the logical enclosure support dump is created, the content of the appliance support dump is automatically added to it and the entire bundle of files is compressed into a zip file and optionally encrypted for downloading The Infrastructure administrator can retrieve a support dump created by any user by issuing the GET REST command to download Aside from the Infrastructure administrator, no user can retrieve a dump created by another user, even if it is encrypted For example, a Server administrator can issue the POST REST command to create a support dump, and the Infrastructure administrator can then issue the GET to download it NOTE: Only the Infrastructure administrator can create an unencrypted logical enclosure support dump An attempt by any role other than the Infrastructure administrator to create an unencrypted support dump will fail Create a support dump containing only logical enclosure data  By default, the logical enclosure support dump includes the appliance support dump To create a logical enclosure support dump that does not contain the appliance support dump, set the value of excludeApplianceDump to true in the request body for the POST that creates the dump Create support dumps containing data from multiple logical enclosures  To create a logical enclosure support dump for multiple logical enclosures, issue a set of REST commands to create and retrieve each logical enclosure support dump If desired, you can set the value of excludeApplianceDump to true in the request body for the support dump for all but one of the logical enclosures This will avoid overlapping content in the support dumps You must wait for each support dump to complete before creating a subsequent support dump Prerequisites Any user role can create an encrypted support dump Downloading a logical enclosure support dump using REST APIs Select a logical enclosure URI GET restlogicalenclosures Using a logical enclosure URI from step1, create the support dump POST restlogicalenclosures idsupportdumps This returns the task that is executing to create the dump Using the task URI returned in step 2, GET the task repeatedly to check the field percentComplete for the task to determine when the support dump is complete GET resttasks id When the dump is complete, the resourceUri of the associatedResource in the task is set to the URI of the complete dump Use the resourceUri of the associatedResource to retrieve the support dump GET restappliancesupportdumps id ";
f["335"]= " Enable or disable authorized support access OneView, online help, help, REST API Enable or disable authorized support access HPE OneView contains a technical feature that will allow an onsite authorized support representative to access your system, through the system console, to assess problems that you have reported This access will be controlled by a password generated by Hewlett Packard Enterprise that will only be provided to the authorized support representative You can disable access at any time while the system is running NOTE: When authorized support access is disabled, you can reset the local administrator password Prerequisites Minimum required session ID privileges: Infrastructure administrator Enabling or disabling authorized support access using REST APIs PUT restappliancesettingsenableServiceAccess ";
f["336"]= " Create a logical interconnect group OneView, online help, help, REST API Create a logical interconnect group A logical interconnect group defines the attributes that are applied to a logical interconnect a collection of physical interconnects in an enclosure that represent a logical interconnect The logical interconnect group can be added to an enclosure group When a logical enclosure is created, if you choose the enclosure group that is associated with a specific logical interconnect group, then those attributes are applied to the physical interconnects contained within that enclosure, creating a logical interconnect Prerequisites Minimum required session ID privileges: Network administrator Creating a logical interconnect group using REST APIs POST restlogicalinterconnectgroups See also  Quick Start: Initial configuration using REST APIs ";
f["337"]= " Read alerts for a physical resource type OneView, online help, help, REST API Read alerts for a physical resource type To read alerts for a physical resource type such as server hardware, filter alerts by the physical resource type Prerequisites Minimum required session ID privileges: Server administrator Reading alerts for a physical resource type using REST APIs Get alerts for a physical resource type GET restalertsfilter=physicalResourceType=' resource type' ";
f["338"]= " View license status OneView, online help, help, REST API View license status View a summary of the total license count, consumed count, and unlicensed server hardware count per product Also, view a license summary for a specific type of product Prerequisites Minimum required session ID privileges: Infrastructure administrator, Server administrator Viewing license status using REST APIs GET restlicensesview=summary Viewing license status for a specific product using REST APIs GET restlicensesfilter=product=' product name'&view=summary For example, to view a HPE OneView license, enter: GET restlicensesfilter=product='HPE OneView'&view=summary ";
f["339"]= " Securing the appliance CONTACT CI DOC OWNERS before modifying this content CIC int, features, product description, reference, security, roles OneView, online help, help, REST API Securing the appliance CATA Comprehensive Applications Threat Analysis is a powerful security quality assessment tool designed to substantially reduce the number of latent security defects The design of the appliance employed CATA fundamentals and underwent CATA review The following factors secured hardened the appliance and its operating system: Best practice operating system security guidelines were followed The appliance operating system minimizes its vulnerability by running only the services required to provide functionality The appliance operating system enforces mandatory access controls internally The appliance maintains a firewall that allows traffic on specific ports and blocks all unused ports See Ports required for HPE OneView for the list of network ports used Key appliance services run only with the required privileges; they do not run as privileged users The operating system bootloader is password protected The appliance cannot be compromised by someone attempting to boot in singleuser mode The appliance is designed to operate entirely on an isolated management LAN Access to the production LAN is not required The appliance enforces a password change at first login The default password cannot be used again The appliance supports selfsigned certificates and certificates issued by a certificate authority The appliance is initially configured with a selfsigned certificate As the Infrastructure administrator, you can generate a CSR certificate signing request and, upon receipt, upload the certificate to the appliance This ensures the integrity and authenticity of your HTTPS connection to the appliance All browser operations and REST API calls use HTTPS All weak SSL Secure Sockets Layer ciphers are disabled The appliance supports secure updating Hewlett Packard Enterprise digitally signs all updates to ensure integrity and authenticity Backup files and transaction logs are encrypted Support dumps are encrypted by default, but you as Infrastructure administrator have the option to not encrypt them Support dumps are automatically encrypted when a user with another role creates them Operatingsystemlevel users are not allowed to access the appliance Hewlett Packard Enterprise closely monitors security bulletins for threats to appliance software components and, if necessary, issues software updates ";
f["340"]= " Using the StateChange Message Bus SCMB OneView, online help, help, REST API Using the StateChange Message Bus SCMB Connect to the SCMB Set up a queue to connect to the HPE OneView SCMB exchange JSON structure of message received from the SCMB Example to connect and subscribe to SCMB using NET C# Example to connect and subscribe to SCMB using Java Examples to connect and subscribe to SCMB using Python Recreate the AMQP client certificate Connect to the SCMB Prerequisites Minimum required session ID privileges: Infrastructure administrator To use the SCMB, you must do the following tasks: Use REST APIs to create and download an Advanced Message Queuing Protocol AMQP certificate from the appliance Connect to the SCMB using one or both of these methods: Use the “EXTERNAL” authentication mechanism Connect without sending a user name and password Using one of these methods ensures that certificatebased authentication is used Set up a queue with an empty queue name AMQP generates a unique queue name You use this queue name to bind to exchanges and receive messages Create and download the AMQP client certificate Creating and downloading the client certificate, private key, and root CA certificate Create the certificate POST restcertificatesclientrabbitmq Request body: type:RabbitMqClientCertV2,commonName:default Download the certificate and private key GET restcertificatesclientrabbitmqkeypairdefault Download the root CA certificate GET restcertificatesca After you connect the client to the SCMB, you can Set up a queue to connect to the HPE OneView SCMB exchange Connecting the client to the SCMB The SCMB consumer requests a client certificate as part of the registration process The appliance manages the client certificates in a JVK Java KeyStore file The appliance issues a client certificate to the SCMB consumer The SCMB client provides an SSL client certificate to create a connection with the appliance The appliance can revoke the SCMB client certificate to deny access to the SCMB client The client is managed into a CRL Certificate Revocation List file The appliance authenticates the SCMB client using the client certificate Set up a queue to connect to the HPE OneView SCMB exchange The state change messages are published to the HPE OneView SCMB exchange name To subscribe to messages, you must create a queue or connect to an existing queue that receives messages from the SCMB exchange based on a routing key When you create a queue, you define the routing key associated with the queue to receive specific messages NOTE: The routing key is case sensitive The changetype requires an initial capital letter The resourcecategory and resourceuri are lowercase For example, if you set the changetype in the routing key to created instead of Created, you do not receive any messages The routing key syntax is: scmb resourcecategory changetype resourceuri where: scmb The HPE OneView exchange name resourcecategory The category of resource For a complete list of resources, see the HPE OneView REST API Reference changetype The type of change that is reported Valid values are Created, Updated, and Deleted resourceuri The URI of the specific resource associated with the statechange message NOTE: The task resources routing key syntax is scmb resourcecategory and does not use changetype and resourceuri To receive messages about all task resources: scmb# scmbtasks Sample queues Subscription Example Receive all SCMB messages for physical servers scmbserverhardware# NOTE: To match everything after a specific point in the routing key, use the # character This example uses # in place of resourceuri The message queue receives all serverhardware resource URIs Receive all messages for created connections scmbconnectionsCreated# Receive all messages for the enclosure with the URI restenclosuresEnc1234 scmbenclosuresrestenclosuresEnc1234 NOTE: To match everything for an individual field in the routing key, use the asterisk   This example uses  in place of changetype The message queue receives all change types: Created, Updated, and Deleted Receive all created messages for all resource categories and types scmbCreated# JSON structure of message received from the SCMB The following table lists the attributes included in the JSON payload of each message from the SCMB The resource model for the HPE OneView resource is included in the resource attribute To view all resource models, see the HPE OneView REST API Reference Attribute Data type Description resourceUri String The URI for the resource changeType String The statechange type: Created, Updated, or Deleted For details, see “ChangeType values” newState String The new state of the resource eTag String The ETag for the resource when the state change occurred timestamp String The time the message was sent newSubState String If substate messages are required for substate machines associated with a primary state, this is the resourcespecific substate resource Object The resource model associatedTask String If a task is not associated with this message, the value is null userInitiatedTask String The value of the userInitiated attribute included in the associatedTask attribute changedAttributes Array A list of toplevel attributes that have changed based on the POST or PUT call that caused the statechange message to be sent data Object Additional information about the resource state change ChangeType values ChangeType value Description Created The resource is created or is added to HPE OneView Updated The resource state, attributes, or both are updated Deleted The resource is permanently removed from HPE OneView JSON example  resourceUri : restenclosures123xyz, changeType : Created, newState : Managed, eTag : 123456, timestamp : 20130710T18:30:44Z, newSubState : null, resource :  category : enclosures, created : 20130710T18:30:00Z,  , associatedTask : resttasks4321, userInitiatedTask : true, changedAttributes : , data : ,  Example to connect and subscribe to SCMB using NET C# Prerequisites In addition to completing the prerequisites, you must complete the examplespecific prerequisites before using the NET C# examples To use the Net C# examples, add the following to the Windows certificate store: CA root certificate Client certificate Private key To try the Net C# examples, do the following: Download the root CA certificate GET restcertificatesca Save the contents in the response body into a text file named rootCAcrt You must copy and paste everything from BEGIN CERTIFICATE to END CERTIFICATE, including the dashes, but not including the quotes Import the rootCAcrt file into the Windows certificate store under Trusted Root Certification Authorities Download the client certificate and private key GET restcertificatesclientrabbitmqkeypairdefault Save the contents of the client certificate and private key in the response body into a text file named scmbcrt You must copy and paste everything from BEGIN CERTIFICATE to END CERTIFICATE for the client certificate Next, copy and paste everything from BEGIN RSA PRIVATE KEY to END RSA PRIVATE KEY for the private key You must include the dashes, but do not include the quotes Using Net C# to directly reference client certificate Convert the client certificate and private key to PKCS format for Net opensslexe pkcs12 passout pass:default export in scmbcrt out scmbp12 Example  public void Connect  string exchangeName = scmb; string hostName = OneViewdomain; string queueName = ; string routingKey = scmb#; ConnectionFactory factory = new ConnectionFactory; factoryAuthMechanisms = new RabbitMQClientAuthMechanismFactory  new ExternalMechanismFactory ; factoryHostName = hostname; factoryPort = 5671; factorySslCertPath = @scmbp12; factorySslCertPassphrase = default; factorySslServerName = hostname; factorySslEnabled = true; IConnection connection = factoryCreateConnection; IModel model = connectionCreateModel; queueName = modelQueueDeclarequeueName, false, false, false, null; modelQueueBindqueueName, exchangeName, routingKey, null; using Subscription sub = new Subscriptionmodel, queueName  foreach BasicDeliverEventArgs ev in sub  DoSomethingWithMessageev; subAck;    Using Net C# to import certificate to Microsoft Windows certificate store Import the scmbcrt into your preferred Windows certificate store Example  public void Connect  string exchangeName = scmb; string hostName = OneViewdomain; string queueName = ; string routingKey = scmb#; string userName = rabbitmq_readonly; X509Store store = new X509StoreStoreNameRoot, StoreLocationLocalMachine; storeOpenOpenFlagsReadWrite; X509Certificate cert = storeCertificates FindX509FindTypeFindBySubjectName, userName, false OfType<X509Certificate> First; ConnectionFactory factory = new ConnectionFactory; factoryAuthMechanisms = new RabbitMQClientAuthMechanismFactory  new ExternalMechanismFactory ; factoryHostName = hostname; factoryPort = 5671; factorySslCerts = new X509CertificateCollectionnew X509Certificate  cert ; factorySslServerName = hostname; factorySslEnabled = true; IConnection connection = factoryCreateConnection; IModel model = connectionCreateModel; queueName = modelQueueDeclarequeueName, false, false, false, null; modelQueueBindqueueName, exchangeName, routingKey, null; using Subscription sub = new Subscriptionmodel, queueName  foreach BasicDeliverEventArgs ev in sub  DoSomethingWithMessageev; subAck;    NOTE: Net C# code example 2 Microsoft Windows certificate store is referencing the Trusted Root Certificate Authorities store, located under Local Computer StoreNameRoot = Trusted Root Certificate Authorities StortLocationLocalMachine = Local Computer Example to connect and subscribe to SCMB using Java Download the client certificate and private key GET restcertificatesclientrabbitmqkeypairdefault Save the contents of the client certificate in the response body into a text file named defaultclientcrt You must copy and paste everything from BEGIN CERTIFICATE to END CERTIFICATE, including the dashes, but not including the quotes Save the contents of the private key in the response body into a text file named defaultclientkey You must copy and paste everything from BEGIN RSA PRIVATE KEY to END RSA PRIVATE KEY, including the dashes, but not including the quotes Create a PKCS12 keystore from the private key and the public certificate openssl pkcs12 export name myclientcert in defaultclientcrt inkey defaultclientkey out myclientp12 Convert the PKCS12 keystore into a JKS keystore keytool importkeystore destkeystore c:MyKeyStore srckeystore myclientp12 srcstoretype pkcs12 alias myclient Example to connect and subscribe to SCMB using Java c:MyKeyStore contains client certificate and private key Load it into Java Keystore final char keyPassphrase = MyKeyStorePasswordtoCharArray; final KeyStore ks = KeyStoregetInstancejks; ksloadnew FileInputStreamc:MyKeyStore, keyPassphrase; final KeyManagerFactory kmf = KeyManagerFactorygetInstanceSunX509; kmfinitks, keyPassphrase; c:MyTrustStore contains CA certificate Load it into Java Trust Store final char trustPassphrase = MyTrustStorePasswordtoCharArray; final KeyStore ks = KeyStoregetInstancejks; tksloadnew FileInputStreamc:MyTrustStore, trustPassphrase; final TrustManagerFactory tmf = TrustManagerFactorygetInstanceSunX509; tmfinittks; load SSLContext with keystore and truststore final SSLContext c = SSLContextgetInstanceSSL; cinitkmfgetKeyManagers, tmfgetTrustManagers, new SecureRandom; final ConnectionFactory factory = new ConnectionFactory; factorysetHost1921682144; Set Auth mechanism to EXTERNAL so that commonName of the client certificate is mapped to AMQP user name Hence, No need to set userIdPassword here factorysetSaslConfigDefaultSaslConfigEXTERNAL; factorysetPort5671; factoryuseSslProtocolc; final Connection conn = factorynewConnection; final Channel channel = conncreateChannel; do not specify queue name AMQP will create a queue with random name starting with amqgen eg amqgen32sfQz95QJ85K_lMBhU6HA final DeclareOk queue = channelqueueDeclare, true, false, true, null; Now get the queue name from above call and bind it to required Exchange with required routing key channelqueueBindqueuegetQueue, scmb, scmb#; Now you should be able to receive messages from queue final GetResponse chResponse = channelbasicGetqueuegetQueue, false; if chResponse == null  SystemoutprintlnNo message retrieved;  else  final byte body = chResponsegetBody; SystemoutprintlnReceived:   new Stringbody;  channelclose; connclose; Examples to connect and subscribe to SCMB using Python The Python code examples show how to connect and subscribe to the SCMB For more information about Python Pika AMQP client library and AMQP client library, see http:pikareadthedocsorg, http:wwwpythonorg, and https:pypipythonorgpypiamqplib Installation Install the pika and amqp libraries Download and install the setuptools Python setuppy install at https:pypipythonorgpypisetuptools#downloads Install the pika tools When you install the pika or amqp libraries, run the same python setuppy install command from the downloaded pika or amqp directory Create the certificate POST restcertificatesclientrabbitmq Request body: type:RabbitMqClientCertV2,commonName:default Download the client certificate and private key GET restcertificatesclientrabbitmqkeypairdefault Save the contents of the client certificate in the response body into a text file named clientpem You must copy and paste everything from BEGIN CERTIFICATE to END CERTIFICATE, including the dashes, but not including the quotes You must replace all instances of n with CRLF carriage return  line feed Save the contents of the private key in the response body into a text file named keypem You must copy and paste everything from BEGIN RSA PRIVATE KEY to END RSA PRIVATE KEY, including the dashes, but not including the quotes You must replace all instances of n with CRLF carriage return  line feed Download the root CA certificate GET restcertificatesca Save the contents in the response body into a text file named carootpem You must copy and paste everything from BEGIN CERTIFICATE to END CERTIFICATE, including the dashes, but not including the quotes You must replace all instances of n with CRLF carriage return  line feed Pika Pika example When you invoke the script, you must pass –host: hostname or IP See the following examples: host:19216811 –host:myapplianceexamplecom IMPORTANT: If the connection fails on the first attempt to invoke this script after an appliance reboot, try invoking the script again import pika, ssl from optparse import OptionParser from pikacredentials import ExternalCredentials import json import logging loggingbasicConfig ############################################### # Callback function that handles messages def callbackch, method, properties, body: msg = jsonloadsbody timestamp = msg'timestamp' resourceUri = msg'resourceUri' resource = msg'resource' changeType = msg'changeType' print print %s: Message received: %timestamp print Routing Key: %s %methodrouting_key print Change Type: %s %changeType print Resource URI: %s %resourceUri print Resource: %s %resource # Pem Files needed, be sure to replace the n returned from the APIs with CRLF # carootpem  the CA Root certificate  GET restcertificatesca # clientpem, first POST restcertificatesclientrabbitmq Request body: type:RabbitMqClientCert,commonName:default # GET restcertificatesclientrabbitmqkeypairdefault # clientpem is the key with BEGIN CERTIFICATE # keypem is the key with BEGIN RSA PRIVATE KEY # Setup our ssl options ssl_options = ca_certs: carootpem, certfile: clientpem, keyfile: keypem, cert_reqs: sslCERT_REQUIRED, server_side: False parser = OptionParser parseradd_option'host', dest='host', help='Pika server to connect to default: %default', default='localhost',  options, args = parserparse_args # Connect to RabbitMQ host = optionshost print Connecting to %s:5671, to change use host hostName  %host connection = pikaBlockingConnection pikaConnectionParameters host, 5671, credentials=ExternalCredentials, ssl=True, ssl_options=ssl_options # Create and bind to queue EXCHANGE_NAME = scmb ROUTING_KEY = scmb# channel = connectionchannel result = channelqueue_declare queue_name = resultmethodqueue channelqueue_bindexchange=EXCHANGE_NAME, queue=queue_name, routing_key=ROUTING_KEY channelbasic_consumecallback, queue=queue_name, no_ack=True # Start listening for messages channelstart_consuming AMQP AMQP example When you invoke the script, you must pass –host: hostname or IP See the following examples: host:19216811 –host:myapplianceexamplecom IMPORTANT: If the connection fails on the first attempt to invoke this script after an appliance reboot, try invoking the script again #!usrbinenv python from optparse import OptionParser from functools import partial import amqplibclient_0_8 as amqp def callbackchannel, msg: for key, val in msgpropertiesitems: print '%s: %s' % key, strval for key, val in msgdelivery_infoitems: print '> %s: %s' % key, strval print '' print msgbody print '' print msgdelivery_tag channelbasic_ackmsgdelivery_tag # # Cancel this callback # if msgbody == 'quit': channelbasic_cancelmsgconsumer_tag def main: parser = OptionParser parseradd_option'host', dest='host', help='AMQP server to connect to default: %default', default='localhost',  options, args = parserparse_args host = optionshost:5671 # Pem Files needed, be sure to replace the n returned from the APIs with CRLF # carootpem  the CA Root certificate  GET restcertificatesca # clientpem, first POST restcertificatesclientrabbitmq Request body: type:RabbitMqClientCert,commonName:default # GET restcertificatesclientrabbitmqkeypairdefault # clientpem is the key with BEGIN CERTIFICATE # keypem is the key with BEGIN RSA PRIVATE KEY ssl_options = ca_certs: carootpem, certfile: clientpem, keyfile: keypem, # cert_reqs: CERT_REQUIRED, server_side: False print 'Connecting to host %s, to change use host hostName ' %host conn = amqpConnectionhost, login_method='EXTERNAL', ssl=ssl_options print 'Successfully connected, creating and binding to queue' ch = connchannel qname, _, _ = chqueue_declare chqueue_bindqname, 'scmb', 'scmb#' chbasic_consumeqname, callback=partialcallback, ch print 'Successfully bound to queue, waiting for messages' #pyamqp: # # Loop as long as the channel has callbacks registered # while chcallbacks: chwait chclose connclose if __name__ == '__main__': main Recreate the AMQP client certificate If you change the appliance name, you must recreate the AMQP client certificate Prerequisites Minimum required session ID privileges: Infrastructure administrator Recreating and downloading the client certificate, private key, and root CA certificate Revoke the certificate DELETE restcertificatescarabbitmq_readonly Request body is not required NOTE: When you revoke the default client certificate, the appliance regenerates the CA certificate, AMQP server certificate, and the default client certificate Download the certificate and private key GET restcertificatesclientrabbitmqkeypairdefault Download the root CA certificate GET restcertificatesca ";
f["341"]= " Add a contact OneView, online help, help, REST API Add a contact Prerequisites Minimum required session ID privileges: Server administrator Add a contact using REST APIs POST restsupportcontacts ";
f["342"]= " Create a Fibre Channel network OneView, online help, help, REST API Create a Fibre Channel network When you create an Fibre Channel network, a connection template is automatically created A connection template defines the connection settings for the Fibre Channel network The settings include maximum and minimum allowable bandwidth Also, you must specify the Fibre Channel network fabric type that attaches to external storage devices: FabricAttach connects to external storage through SAN interconnects DirectAttach connects directly to external storage Prerequisites Minimum required session ID privileges: Network administrator Creating a Fibre Channel network using REST APIs POST restfcnetworks NOTE: The connectionTemplateUri attribute must be set to null See also  Quick Start: Initial configuration using REST APIs top of chapter ";
f["343"]= " Assign an owner to an alert OneView, online help, help, REST API Assign an owner to an alert To retrieve alerts that do not have an assigned owner, you can filter alerts by severity, urgency, and no assigned owner After retrieving the alerts, you can select an alert, add an owner, and then perform a PUT operation to update the alert Prerequisites Minimum required session ID privileges: Server administrator Assigning an owner to an alert using REST APIs Select an alert that does not have an assigned owner GET restalertsfilter=severity='UNKNOWN, OK, WARNING, CRITICAL'&filter=urgency='None, Deferrable, Medium, High, Immediate, Unknown'&filter=assignedToUser=' ' Get the alert GET restalerts id Assign an owner to the alert Update the alert PUT restalerts id NOTE: The DISABLED severity does not apply to alerts ";
f["344"]= " Data Centers OneView, online help, help, REST API Data Centers Use REST APIs to  Create a data center Create a data center layout Update a data center Delete a data center See more tasks Learn more About data centers datacenters REST APIs ";
f["345"]= " Update a connection template OneView, online help, help, REST API Update a connection template When you create an Ethernet or Fibre Channel network, a connection template is created A connection template defines the connection settings for the Ethernet or Fibre Channel network The settings include maximum and minimum allowable bandwidth To update a connection template, perform a PUT operation to reapply all of the connection template attributes View the connection template attributes by using a GET operation, edit the attributes, and then perform a PUT operation using all of the attributes Prerequisites Minimum required session ID privileges: Network administrator Updating a connection template using REST APIs Select the connection template URI GET restconnectiontemplates Get the connection template using the URI from step 1 GET restconnectiontemplates id Edit the connection template Update the connection template Put restconnectiontemplates id See also  Quick Start: Initial configuration using REST APIs ";
f["346"]= " Asynchronous versus synchronous operations OneView, online help, help, REST API Asynchronous versus synchronous operations A synchronous operation returns a response after the REST API operation completes For example, POST restserverprofiles returns a newly created server profile in the response body An asynchronous operation, such as creating an appliance backup, returns the URI of a task in the Location response header You can use the task URI to retrieve the current status of the operation, and to obtain the associated resource once the task is complete This is common behavior for all asynchronous APIs You should not depend on any other behavior to get the current status of the operation such as the content of the returned response body, as it varies from API to API See the API Reference for the behavior of each specific API You should not depend on any other behavior to occur, as it is subject to change in the future, even for the same API version Example response header returned from an asynchronous appliance backup REST call HTTP11 202 Accepted Date: Tue, 26 Jan 2016 23:19:14 GMT Server: Apache Location: https:<hostname>resttasks39CE80C4EF2C471790EAEF166E83B49F ContentLength: 0 cachecontrol: nocache ";
f["347"]= " Refresh a switch OneView, online help, help, REST API Refresh a switch Refresh a switch in the Monitored state using the Refresh action from the Switches screen in the UI Refreshing a switch helps in validating the switch resource as well as retrieving the updated switch data ";
f["348"]= " Copy a server profile template OneView, online help, help, REST API Copy a server profile template Prerequisites Minimum required session ID privileges: Server administrator Copying a server profile template using REST APIs Get all server profile templates GET restserverprofiletemplates Delete the server profile template uri value Create a new server profile template POST restserverprofiletemplates ";
f["349"]= " Server Profiles OneView, online help, help, REST API Server Profiles You can create a server profile for specific hardware or create an unassigned server profile A server profile for specific hardware is based on the server hardware type and the enclosure group The server hardware type associated with a specific server, automatically assigned when an enclosure is added, defines what BIOS settings can be applied along with other attributes The enclosure group defines what connections are available to the server based on the logical interconnect group referenced by the enclosure group Use REST APIs to  Create a server profile Create an unassigned server profile to use as a template Create a server profile with userspecified IDs Attach an existing volume to a server profile Attach a new volume to a server profile Copy an unassigned server profile Assign an unassigned server profile Read a server profile Update a server profile Delete a server profile See more tasks Learn more About server profiles About server profiles and local storage serverprofiles REST APIs ";
f["350"]= " Using remoteSyslog OneView, online help, help, REST API Using remoteSyslog The remoteSyslog resource in HPE OneView provides APIs for remote log configuration You can obtain the logs from HPE OneView managed resources by doing the following: Configure HPE OneView for a remoteSyslog relay NOTE: This API configures the remote system logging on devices managed in HPE OneView The logs are relayed directly from the devices which natively support remote system logging This feature is supported only for version Gen 8 and greater servers and for c7000 enclosures Fetch remoteSyslog configuration You can fetch the current remoteSyslog configuration Fetching current remoteSyslog configuration using REST APIs Get the current remoteSyslog configuration GET restlogsremoteSyslog Update remoteSyslog configuration You can update the remoteSyslog configuration Updating remoteSyslog configuration using REST APIs Update remoteSyslog configuration PUT restlogsremoteSyslog ";
f["351"]= " Switches OneView, online help, help, REST API Switches Use REST APIs to  Retrieve switch data Refresh a switch Remove a switch See more tasks Learn more About topofrack switches switches REST APIs ";
f["352"]= " Enable or disable LLDP tagging using REST APIs OneView, online help, help, REST API Enable or disable LLDP tagging using REST APIs Enabling or disabling the enableTaggedLldp parameter determines the LLDP management address TLV of LLDP frames sent out by an interconnect Prerequisites Required privileges: Infrastructure administrator or Network administrator Minimum required Virtual Connect firmware version: 445 Enabling LLDP tagging using REST APIs Select a logical interconnect group URI GET restlogicalinterconnectgroups Get the logical interconnect group using the URI from step 1 GET restlogicalinterconnectgroups id Set enableTaggedLldp to true Update the logical interconnect group PUT restlogicalinterconnectgroups id Disabling LLDP tagging using REST APIs Select a logical interconnect group URI GET restlogicalinterconnectgroups Get the logical interconnect group using the URI from step 1 GET restlogicalinterconnectgroups id Set enableTaggedLldp to false Update the logical interconnect group PUT restlogicalinterconnectgroups id More information About Link Layer Discovery Protocol LLDP tagging ";
f["353"]= " Delete a storage volume template storagevolumetemplatesall OneView, online help, help, REST API Delete a storage volume template Prerequisites Minimum required session ID privileges: Infrastructure administrator or Server administrator Deleting a storage volume template using REST APIs Select a storage volume template GET reststoragevolumetemplates Delete the storage volume template DELETE reststoragevolumetemplates id ";
f["354"]= " Filter alerts by health and status OneView, online help, help, REST API Filter alerts by health and status You can retrieve a list of alerts filtered by different attributes The following example shows how to filter alerts by severity and urgency Prerequisites Minimum required session ID privileges: Server administrator Filtering alerts by health and status using REST APIs GET restalertsfilter=severity='UNKNOWN, OK, WARNING, CRITICAL'&filter=urgency='None, Deferrable, Medium, High, Immediate, Unknown' NOTE: The DISABLED severity does not apply to alerts ";
f["355"]= " Import a certificate OneView, online help, help, REST API Import a certificate After sending a certificate signing request to the CA and receiving a certificate, you must import it Prerequisites Minimum required session ID privileges: Infrastructure administrator Ensure that no other users are logged in to the appliance Importing a certificate using REST APIs POST restcertificates ";
f["356"]= " Delete a contact OneView, online help, help, REST API Delete a contact Prerequisites Minimum required session ID privileges: Server administrator Delete a contact using REST APIs DELETE restsupportcontactscontactKey ";
f["357"]= " Logical Interconnect Groups OneView, online help, help, REST API Logical Interconnect Groups Use REST APIs to  Create a logical interconnect group Update a logical interconnect group Update logical interconnect group SNMP settings Enable or disable LLDP tagging using REST APIs Enable or disable enhanced TLV support using REST APIs Configure Quality of Service settings for a logical interconnect group See more tasks Learn more About logical interconnect groups About Quality of Service for network traffic logicalinterconnectgroups REST APIs ";
f["358"]= " Update a SAN manager OneView, online help, help, REST API Update a SAN manager To update the SAN manager connection information, perform a PUT operation that includes only the connectionInfo attributes View the SAN manager connection attributes by using a GET operation, edit the connectionInfo attributes, and then perform a PUT operation that includes only the edited connectionInfo attributes Prerequisites Minimum required session ID privileges: Infrastructure administrator or Storage administrator Updating a SAN manager using REST APIs Select a SAN manager URI GET restfcsansdevicemanagers Get the SAN manager connection information using the URI from step 1 GET SAN manager URI Edit the connection information The only attributes to send in the response body are connectionInfo Do not send all attributes from the GET operation Update the SAN manager connection information PUT SAN manager URI ";
f["359"]= " Storage Volumes storagevolumesall OneView, online help, help, REST API Storage Volumes I want to  Add an external storage volume Create a storage volume Update a storage volume Delete a storage volume See more tasks Learn more About volumes storagevolumes REST APIs ";
f["360"]= " Unassign a server profile OneView, online help, help, REST API Unassign a server profile Prerequisites Minimum required session ID privileges: Server administrator Unassigning a server profile using REST APIs Select a server profile URI GET restserverprofiles Get the server profile GET restserverprofiles id Delete the server profile serverHardwareUri value Update the server profile PUT restserverprofiles id ";
f["361"]= " About ID pools OneView, online help, help, REST API About ID pools An ID pool is a collection of one or more ranges that can be randomly generated or userspecified to provide large address spaces By default, one virtual ID pool each of contiguous MAC addresses, WWNs, and serial numbers are created automatically when you initialize the appliance The pools are composed of address and ID ranges, which you can individually enable or disable You can delete any unused ranges ID pool ranges do not conflict with physical IDs, provided the virtual ranges that are created exclude the physical ID ranges Supported ID pools ID pool Description Virtual MAC addresses vMAC 6 byte quantity represented as 12 hexadecimal characters, bytes separated by a colon  : Unicast address ranges only, multicast bit must not be set Virtual World Wide Names vWWN 8 byte quantity represented as 16 hexadecimal characters, bytes separated by a colon  : Virtual Serial Numbers vSN 10 alphanumeric characters, uppercase ";
f["362"]= " Users and Groups OneView, online help, help, REST API Users and Groups You can create an account with either local authentication or associate directorybased authentication Local authentication accounts are managed by the appliance in a database located in the appliance Directorybased authentication accounts are managed externally by another service, such as Microsoft Active Directory Use REST APIs to  Create a user with local authentication Update a local user account Update a local user password Delete a local user account Add an authentication login domain Assign roles to an enterprise group Change the default authentication login domain Delete an authentication login domain Reset the administrator password Enable or disable local logins See more tasks Learn more About user accounts About user roles Action privileges for user roles users REST APIs logindomains REST APIs logindomainsglobalsettings REST APIs logindomainsgrouptorolemapping REST APIs ";
f["363"]= " Error message format OneView, online help, help, REST API Error message format When an error occurs in the processing of an API request, an error message is returned The following table lists the attributes in the JSON payload of an error message Attribute Data type Description errorCode String A string that uniquely identifies the type of error that occurred Useful for programmatic handling of specific error conditions message String A short description of the error that occurred details String A detailed description of the error recommendedActions Array<String> A list of strings indicating suggested user actions or resolutions for the specific error condition nestedErrors Array<ErrorMessage> For multipart errors for example, formvalidation errors, this field may contain specific of the individual components of the error for example, individual fields in error errorSource String For multipart errors for example, form validation errors, this field contains the identifier of the subcomponent in error for example, the individual field name data Object Internaladditional data associated with the error External clients will usually ignore this field ";
f["364"]= " Concurrency control using etags OneView, online help, help, REST API Concurrency control using etags A client uses etags to verify the version of the resource model This prevents the client from modifying  PUT a version of the resource model that is not current For example, if a client performs a GET on a server profile and receives an etag in the response header, modifies the server profile, and then updates  PUT the resource model, the etag in the PUT request header must match the resource model etag If the etags do not match, the client PUT request will not complete and a 412 PRECONDITION FAILED error is returned ";
f["365"]= " Update remote support settings OneView, online help, help, REST API Update remote support settings Prerequisites Minimum required session ID privileges: Server administrator Update remote support settings using REST APIs PATCH restsupport ";
