Warning: -file- is being assigned a // sourceMappingURL, but already has one TypeError: invalid Array.prototype.sort argument Warning: 08/09 is not a legal ECMA-262 octal constant. To import such a configuration file that has all secure properties removed, use the import merge mode; do not use the import replace mode. Using the import merge mode will preserve the existing secure properties in the ACI fabric. What are Components?
Components are one of the most powerful features of Vue.js. They help you extend basic HTML elements to encapsulate reusable code. At a high level, Components are custom elements that Vue.js compiler would attach specified behavior to. In some cases, they may also appear as a native HTML element extended with the special is attribute. Using Components Registration
Weve learned in the previous sections that we can create a component constructor using Vue.extend() :
To use this constructor as a component, you need to register it with Vue.component(tag, constructor) :
Note that Vue.js does not enforce the W3C rules for custom tag-names (all-lowercase, must contain a hyphen) though following this convention is considered good practice.
Once registered, the component can now be used in a parent instances template as a custom element, my-component . Make sure the component is registered before you instantiate your root Vue instance. Heres the full example:
Which will render:
Note the components template replaces the custom element, which only serves as a mounting point . This behavior can be configured using the replace instance option.
Also note that components are provided a template instead of mounting with the el option! Only the root Vue instance (defined using new Vue ) will include an el to mount to). Local Registration
You dont have to register every component globally. You can make a component available only in the scope of another component by registering it with the components instance option:
The same encapsulation applies for other assets types such as directives, filters and transitions. Registration Sugar
To make things easier, you can directly pass in the options object instead of an actual constructor to Vue.component() and the component option. Vue.js will automatically call Vue.extend() for you under the hood: Component Option Caveats
Most of the options that can be passed into the Vue constructor can be used in Vue.extend() , with two special cases: data and el . Imagine we simply pass an object as data to Vue.extend() :
The problem with this is that the same data object will be shared across all instances of MyComponent ! This is most likely not what we want, so we should use a function that returns a fresh object as the data option:
The el option also requires a function value when used in Vue.extend() , for exactly the same reason. Template Parsing
Vue.js template engine is DOM-based and uses native parser that comes with the browser instead of providing a custom one. There are benefits to this approach when compared to string-based template engines, but there are also caveats. Templates have to be individually valid pieces of HTML. Some HTML elements have restrictions on what elements can appear inside them. Most common of these restrictions are:
a can not contain other interactive elements (e.g. buttons and other links)
li should be a direct child of ul or ol , and both ul and ol can only contain li
option should be a direct child of select , and select can only contain option (and optgroup )
table can only contain thead , tbody , tfoot and tr , and these elements should be direct children of table
tr can only contain th and td , and these elements should be direct children of tr
In practice these restriction can cause unexpected behavior. Although in simple cases it might appear to work, you can not rely on custom elements being expanded before browser validation. E.g. my-selectoption.../option/my-select is not a valid template even if my-select component eventually expands to select.../select .
Another consequence is that you can not use custom tags (including custom elements and special tags like component , template and partial ) inside of select , table and other elements with similar restrictions. Custom tags will be hoisted out and thus not render properly.
In case of a custom element you should use the is special attribute:
In case of a template inside of a table you should use tbody , as tables are allowed to have multiple tbody : Props Passing Data with Props
Every component instance has its own isolated scope . This means you cannot (and should not) directly reference parent data in a child components template. Data can be passed down to child components using props .
A prop is a field on a components data that is expected to be passed down from its parent component. A child component needs to explicitly declare the props it expects to receive using the props option:
Then, we can pass a plain string to it like so:
Result: camelCase vs. kebab-case
HTML attributes are case-insensitive. When using camelCased prop names as attributes, you need to use their kebab-case (hyphen-delimited) equivalents: Dynamic Props
Similar to binding a normal attribute to an expression, we can also use v-bind for dynamically binding props to data on the parent. Whenever the data is updated in the parent, it will also flow down to the child:
It is often simpler to use the shorthand syntax for v-bind :
Result:
Literal vs. Dynamic
A common mistake beginners tend to make is attempting to pass down a number using the literal syntax:
However, since this is a literal prop, its value is passed down as a plain string '1' , instead of an actual number. If we want to pass down an actual JavaScript number, we need to use the dynamic syntax to make its value be evaluated as a JavaScript expression: Prop Binding Types
By default, all props form a one-way-down binding between the child property and the parent one: when the parent property updates, it will flow down to the child, but not the other way around. This default is meant to prevent child components from accidentally mutating the parents state, which can make your apps data flow harder to reason about. However, it is also possible to explicitly enforce a two-way or a one-time binding with the .sync and .once binding type modifiers :
Compare the syntax:
The two-way binding will sync the change of childs msg property back to the parents parentMsg property. The one-time binding, once set up, will not sync future changes between the parent and the child.
Note that if the prop being passed down is an Object or an Array, it is passed by reference. Mutating the Object or Array itself inside the child will affect parent state, regardless of the binding type you are using. Prop Validation
It is possible for a component to specify the requirements for the props it is receiving. This is useful when you are authoring a component that is intended to be used by others, as these prop validation requirements essentially constitute your components API, and ensure your users are using your component correctly. Instead of defining the props as an array of strings, you can use the object hash format that contain validation requirements:
The type can be one of the following native constructors:
String
Number
Boolean
Function
Object
Array
In addition, type can also be a custom constructor function and the assertion will be made with an instanceof check.
When a prop validation fails, Vue will refuse to set the value on the child component, and throw a warning if using the development build. Parent-Child Communication Parent Chain
A child component holds access to its parent component as this.$parent . A root Vue instance will be available to all of its descendants as this.$root . Each parent component has an array, this.$children , which contains all its child components.
Although its possible to access any instance in the parent chain, you should avoid directly relying on parent data in a child component and prefer passing data down explicitly using props. In addition, it is a very bad idea to mutate parent state from a child component, because:
It makes the parent and child tightly coupled;
It makes the parent state much harder to reason about when looking at it alone, because its state may be modified by any child! Ideally, only a component itself should be allowed to modify its own state. Custom Events
All Vue instances implement a custom event interface that facilitates communication within a component tree. This event system is independent from the native DOM events and works differently.
Each Vue instance is an event emitter that can:
Listen to events using $on() ;
Trigger events on self using $emit() ;
Dispatch an event that propagates upward along the parent chain using $dispatch() ;
Broadcast an event that propagates downward to all descendants using $broadcast() .
Unlike DOM events, Vue events will automatically stop propagation after triggering callbacks for the first time along a propagation path, unless the callback explicitly returns true .
A simple example: v-on for Custom Events
The example above is pretty nice, but when we are looking at the parents code, its not so obvious where the 'child-msg' event comes from. It would be better if we can declare the event handler in the template, right where the child component is used. To make this possible, v-on can be used to listen for custom events when used on a child component:
This makes things very clear: when the child triggers the 'child-msg' event, the parents handleIt method will be called. Any code that affects the parents state will be inside the handleIt parent method; the child is only concerned with triggering the event. Child Component Refs
Despite the existence of props and events, sometimes you might still need to directly access a child component in JavaScript. To achieve this you have to assign a reference ID to the child component using v-ref . For example:
When v-ref is used together with v-for , the ref you get will be an Array or an Object containing the child components mirroring the data source. Content Distribution with Slots
When using components, it is often desired to compose them like this:
There are two things to note here:
The app component does not know what content may be present inside its mount target. It is decided by whatever parent component that is using app .
The app component very likely has its own template.
To make the composition work, we need a way to interweave the parent content and the components own template. This is a process called content distribution (or transclusion if you are familiar with Angular). Vue.js implements a content distribution API that is modeled after the current Web Components spec draft, using the special slot element to serve as distribution outlets for the original content. Compilation Scope
Before we dig into the API, lets first clarify which scope the contents are compiled in. Imagine a template like this:
Should the msg be bound to the parents data or the child data? The answer is parent. A simple rule of thumb for component scope is:
Everything in the parent template is compiled in parent scope; everything in the child template is compiled in child scope.
A common mistake is trying to bind a directive to a child property/method in the parent template:
Assuming someChildProperty is a property on the child component, the example above would not work as intended. The parents template should not be aware of the state of a child component.
If you need to bind child-scope directives on a component root node, you should do so in the child components own template:
Similarly, distributed content will be compiled in the parent scope. Single Slot
Parent content will be discarded unless the child component template contains at least one slot outlet. When there is only one slot with no attributes, the entire content fragment will be inserted at its position in the DOM, replacing the slot itself.
Anything originally inside the slot tags is considered fallback content . Fallback content is compiled in the child scope and will only be displayed if the hosting element is empty and has no content to be inserted.
Suppose we have a component with the following template:
Parent markup that uses the component:
The rendered result will be: Named Slots
slot elements have a special attribute, name , which can be used to further customize how content should be distributed. You can have multiple slots with different names. A named slot will match any element that has a corresponding slot attribute in the content fragment.
There can still be one unnamed slot, which is the default slot that serves as a catch-all outlet for any unmatched content. If there is no default slot, unmatched content will be discarded.
For example, suppose we have a multi-insertion component with the following template:
Parent markup:
The rendered result will be:
The content distribution API is a very useful mechanism when designing components that are meant to be composed together. Dynamic Components
You can use the same mount point and dynamically switch between multiple components by using the reserved component element and dynamically bind to its is attribute: keep-alive
If you want to keep the switched-out components alive so that you can preserve its state or avoid re-rendering, you can add a keep-alive directive param: activate Hook
When switching components, the incoming component might need to perform some asynchronous operation before it should be swapped in. To control the timing of component swapping, implement the activate hook on the incoming component:
Note the activate hook is only respected during dynamic component swapping or the initial render for static components - it does not affect manual insertions with instance methods. transition-mode
The transition-mode param attribute allows you to specify how the transition between two dynamic components should be executed.
By default, the transitions for incoming and outgoing components happen simultaneously. This attribute allows you to configure two other modes:
in-out : New component transitions in first, current component transitions out after incoming transition has finished.
out-in : Current component transitions out first, new component transitions in after outgoing transition has finished.
Example A B Misc Components and v-for
You can directly use v-for on the custom component, like any normal element:
However, this wont pass any data to the component, because components have isolated scopes of their own. In order to pass the iterated data into the component, we should also use props:
The reason for not automatically injecting item into the component is because that makes the component tightly coupled to how v-for works. Being explicit about where its data comes from makes the component reusable in other situations. Authoring Reusable Components
When authoring components, it is good to keep in mind whether you intend to reuse this component somewhere else later. It is OK for one-off components to have some tight coupling with each other, but reusable components should define a clean public interface.
The API for a Vue.js component essentially comes in three parts - props, events and slots:
Props allow the external environment to feed data to the component;
Events allow the component to trigger actions in the external environment;
Slots allow the external environment to insert content into the components view structure.
With the dedicated shorthand syntax for v-bind and v-on , the intents can be clearly and succinctly conveyed in the template: Async Components
In large applications, we may need to divide the app into smaller chunks, and only load a component from the server when it is actually needed. To make that easier, Vue.js allows you to define your component as a factory function that asynchronously resolves your component definition. Vue.js will only trigger the factory function when the component actually needs to be rendered, and will cache the result for future re-renders. For example:
The factory function receives a resolve callback, which should be called when you have retrieved your component definition from the server. You can also call reject(reason) to indicate the load has failed. The setTimeout here is simply for demonstration; How to retrieve the component is entirely up to you. One recommended approach is to use async components together with Webpacks code-splitting feature: Assets Naming Convention
Some assets, such as components and directives, appear in templates in the form of HTML attributes or HTML custom tags. Since HTML attribute names and tag names are case-insensitive , we often need to name our assets using kebab-case instead of camelCase, which can be a bit inconvenient.
Vue.js actually supports naming your assets using camelCase or PascalCase, and automatically resolves them as kebab-case in templates (similar to the name conversion for props):
This works nicely with ES6 object literal shorthand: Recursive Component
Components can recursively invoke itself in its own template, however, it can only do so when it has the name option:
A component like the above will result in a max stack size exceeded error, so make sure recursive invocation is conditional. When you register a component globally using Vue.component() , the global ID is automatically set as the components name option. Fragment Instance
When you use the template option, the content of the template will replace the element the Vue instance is mounted on. It is therefore recommended to always have a single root-level, plain element in templates.
Instead of templates like this:
Prefer this:
There are multiple conditions that will turn a Vue instance into a fragment instance :
Template contains multiple top-level elements.
Template contains only plain text.
Template contains only another component (which can potentially be a fragment instance itself).
Template contains only an element directive, e.g. partial or vue-routers router-view .
Template root node has a flow-control directive, e.g. v-if or v-for .
The reason is that all of the above cause the instance to have an unknown number of top-level elements, so it has to manage its DOM content as a fragment. A fragment instance will still render the content correctly. However, it will not have a root node, and its $el will point to an anchor node, which is an empty Text node (or a Comment node in debug mode).
Whats more important though, is that non-flow-control directives, non-prop attributes and transitions on the component element will be ignored , because there is no root element to bind them to:
There are, of course, valid use cases for fragment instances, but it is in general a good idea to give your component template a single, plain root element. It ensures directives and attributes on the component element to be properly transferred, and also results in slightly better performance. Inline Template
When the inline-template special attribute is present on a child component, the component will use its inner content as its template, rather than treating it as distributed content. This allows more flexible template-authoring.
However, inline-template makes the scope of your templates harder to reason about, and makes the components template compilation un-cachable. As a best practice, prefer defining templates inside the component using the template option. Caught a mistake or want to contribute to the documentation? Edit this page on Github!
Contents Warning Node Has Slots In Importing Staten Island Backup and Export Configuration
When you perform a backup through Cisco UCS Manager , you take a snapshot of all or part of the system configuration and export the file to a location on your network. You cannot use Cisco UCS Manager to back up data on the servers.
You can perform a backup while the system is up and running. The backup operation only saves information from the management plane. It does not have any impact on the server or network traffic. Backup Types
You can perform one or more of the following types of backups through Cisco UCS Manager :
Full state A binary file that includes a snapshot of the entire system. You can use the file generated from this backup to restore the system during disaster recovery. This file can restore or rebuild the configuration on the original fabric interconnect, or recreate the configuration on a different fabric interconnect. You cannot use this file for an import.
All configuration An XML file that includes all system and logical configuration settings. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore.
System configuration An XML file that includes all system configuration settings such as usernames, roles, and locales. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore.
Logical configuration An XML file that includes all logical configuration settings such as service profiles, VLANs, VSANs, pools, and policies. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore. Considerations and Recommendations for Backup Operations
Before you create a backup operation, consider the following: Backup Locations
The backup location is the destination or folder on the network where you want Cisco UCS Manager to export the backup file. You can maintain only one backup operation for each location where you plan to save a backup file. Potential to Overwrite Backup Files
If you rerun a backup operation without changing the filename, Cisco UCS Manager overwrites the existing file on the server. To avoid overwriting existing backup files, change the filename in the backup operation or copy the existing file to another location. Multiple Types of Backups
You can run and export more than one type of backup to the same location. You need to change the backup type before you rerun the backup operation. We recommend that you change the filename for easier identification of the backup type and to avoid overwriting the existing backup file. Scheduled Backups
You cannot schedule a backup operation. You can, however, create a backup operation in advance and leave the admin state disabled until you are ready to run the backup. Cisco UCS Manager does not run the backup operation, save, or export the configuration file until you set the admin state of the backup operation to enabled. Incremental Backups
You cannot perform incremental backups of the Cisco UCS Manager system configuration. Backwards Compatibility
Starting with Release 1.1(1) of the Cisco UCS Manager , full state backups are encrypted so that passwords and other sensitive information are not exported as clear text. As a result, full state backups made from Release 1.1(1) or later cannot be restored to a Cisco UCS instance running an earlier software release. Import Configuration
You can import any configuration file that was exported from Cisco UCS Manager . The file does not need to have been exported from the same Cisco UCS Manager .
The import function is available for all configuration, system configuration, and logical configuration files. You can perform an import while the system is up and running. An import operation modifies information on the management plane only. Some modifications caused by an import operation, such as a change to a vNIC assigned to a server, can cause a server reboot or other operations that disrupt traffic.
You cannot schedule an import operation. You can, however, create an import operation in advance and leave the admin state disabled until you are ready to run the import. Cisco UCS Manager will not run the import operation on the configuration file until you set the admin state to enabled.
You can maintain only one import operation for each location where you saved a configuration backup file. Import Methods
You can use one of the following methods to import and update a system configuration through Cisco UCS Manager :
Merge The information in the imported configuration file is compared with the existing configuration information. If there are conflicts, the import operation overwrites the information on the Cisco UCS instance with the information in the import configuration file.
Replace The current configuration information is replaced with the information in the imported configuration file one object at a time. System Restore
You can restore a system configuration from any full state backup file that was exported from Cisco UCS Manager . The file does not need to have been exported from the Cisco UCS Manager on the system that you are restoring.
The restore function is only available for a full state backup file. You cannot import a full state backup file. You perform a restore through the initial system setup.
You can use the restore function for disaster recovery. Required User Role for Backup and Import Operations
You must have a user account that includes the admin role to create and run backup and import operations.
Backup Operations Creating a Backup Operation Before You Begin
Obtain the backup server IP address and authentication credentials.
Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the Work pane, click the General tab. Step 4 In the Actions area, click Backup Configuration . Step 5 In the Backup Configuration dialog box, click Create Backup Operation . Step 6 In the Create Backup Operation dialog box, complete the following fields: Name Description
Admin State field
This can be:
enabled Cisco UCS Manager runs the backup operation as soon as you click OK .
disabled Cisco UCS Manager does not run the backup operation when you click OK . If you select this option, all fields in the dialog box remain visible. However, you must manually run the backup from the Backup Configuration dialog box.
Type field
The information saved in the backup configuration file. This can be:
Full state A binary file that includes a snapshot of the entire system. You can use the file generated from this backup to restore the system during disaster recovery. This file can restore or rebuild the configuration on the original fabric interconnect, or recreate the configuration on a different fabric interconnect. You cannot use this file for an import.
All configuration An XML file that includes all system and logical configuration settings. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore.
System configuration An XML file that includes all system configuration settings such as usernames, roles, and locales. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore.
Logical configuration An XML file that includes all logical configuration settings such as service profiles, VLANs, VSANs, pools, and policies. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore.
Preserve Identities check box
If this check box is checked, the backup file preserves all identities derived from pools, including the MAC addresses, WWPN, WWNN, and UUIDs.
Location of the Backup File field
Where the backup file should be saved. This can be:
Remote File System The backup XML file is saved to a remote server. Cisco UCS Manager GUI displays the fields described below that allow you to specify the protocol, host, filename, username, and password for the remote system.
Local File System The backup XML file is saved locally. Cisco UCS Manager GUI displays the Filename field with an associated Browse button that let you specify the name and location for the backup file. Note
Once you click OK , the location cannot be changed.
Protocol field
The protocol to use when communicating with the remote server. This can be:
FTP
TFTP
SCP
SFTP
Hostname field
The hostname or IP address of the location where the backup file is stored. This can be a server, storage array, local drive, or any read/write media that the fabric interconnect can access through the network. Note
If you use ahostname rather than an IP address, you must configure a DNS server in Cisco UCS Manager.
Remote File field
The full path to the backup configuration file. This field can contain the filename as well as the path. If you omit the filename, the backup procedure assigns a name to the file.
User field
The username the system should use to log in to the remote server. This field does not apply if the protocol is TFTP.
Password field
The password for the remote server username. This field does not apply if the protocol is TFTP.
Cisco UCS Manager does not store this password. Therefore, you do not need to enter this password unless you intend to enable and run the backup operation immediately. Step 7 Click OK . Step 8 If Cisco UCS Manager displays a confirmation dialog box, click OK .
If you set the Admin State field to enabled, Cisco UCS Manager takes a snapshot of the configuration type that you selected and exports the file to the network location. The backup operation displays in the Backup Operations table in the Backup Configuration dialog box. Step 9 (Optional) To view the progress of the backup operation, do the following:
If the operation does not display in the Properties area, click the operation in the Backup Operations table.
In the Properties area, click the down arrows on the FSM Details bar.
The FSM Details area expands and displays the operation status. Step 10 Click OK to close the Backup Configuration dialog box.
The backup operation continues to run until it is completed. To view the progress, re-open the Backup Configuration dialog box. Running a Backup Operation Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the Work pane, click the General tab. Step 4 In the Actions area, click Backup Configuration . Step 5 In the Backup Operations table of the Backup Configuration dialog box, click the backup operation that you want to run.
The details of the selected backup operation display in the Properties area. Step 6 In the Properties area, complete the following fields:
In the Admin State field, click the Enabled radio button.
For all protocols except TFTP, enter the password for the username in the Password field.
Optional: Change the content of the other available fields. Step 7 Click Apply .
Cisco UCS Manager takes a snapshot of the configuration type that you selected and exports the file to the network location. The backup operation displays in the Backup Operations table in the Backup Configuration dialog box. Step 8 (Optional) To view the progress of the backup operation, click the down arrows on the FSM Details bar.
The FSM Details area expands and displays the operation status. Step 9 Click OK to close the Backup Configuration dialog box.
The backup operation continues to run until it is completed. To view the progress, re-open the Backup Configuration dialog box. Modifying a Backup Operation
You can modify a backup operation to save a file of another backup type to that location or to change the filename and avoid overwriting previous backup files. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the Work pane, click the General tab. Step 4 In the Actions area, click Backup Configuration . Step 5 In the Backup Operations area of the Backup Configuration dialog box, click the backup operation that you want to modify.
The details of the selected backup operation display in the Properties area. If the backup operation is in a disabled state, the fields are dimmed. Step 6 In the Admin State field, click the enabled radio button. Step 7 Modify the appropriate fields.
You do not have to enter the password unless you want to run the backup operation immediately. Step 8 (Optional) If you do not want to run the backup operation immediately, click the disabled radio button in the Admin State field. Step 9 Click OK . Deleting One or More Backup Operations Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the Work pane, click the General tab. Step 4 In the Actions area, click Backup Configuration . Step 5 In the Backup Operations table of the Backup Configuration dialog box, click the backup operations that you want to delete. Tip
You cannot click a backup operation in the table if the admin state of the operation is set to Enabled. Step 6 Click the Delete icon in the icon bar of the Backup Operations table. Step 7 If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes . Step 8 In the Backup Configuration dialog box, click one of the following: Option Description
Apply
Deletes the selected backup operations without closing the dialog box.
OK
Deletes the selected backup operations and closes the dialog box.
Import Operations Creating an Import Operation
You cannot import a Full State configuration file. You can import any of the following configuration files:
All configuration
System configuration
Logical configuration Before You Begin
Collect the following information that you will need to import a configuration file:
Backup server IP address and authentication credentials
Fully qualified name of a backup file
Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the Work pane, click the General tab. Step 4 In the Actions area, click Import Configuration . Step 5 In the Import Configuration dialog box, click Create Import Operation . Step 6 In the Create Import Operation dialog box, complete the following fields: Name Description
Admin State field
This can be:
enabled Cisco UCS runs the import operation as soon as you click OK .
disabled Cisco UCS does not run the import operation when you click OK . If you select this option, all fields in the dialog box remain visible. However, you must manually run the import from the Import Configuration dialog box.
Action field
You can select:
Merge The configuration information is merged with the existing information. If there are conflicts, the system replaces the information on the current system with the information in the import configuration file.
Replace The system takes each object in the import configuration file and overwrites the corresponding object in the current configuration.
Location of the Import File field
Where the backup file that you want to import is located. This can be:
Remote File System The backup XML file is stored on a remote server. Cisco UCS Manager GUI displays the fields described below that allow you to specify the protocol, host, filename, username, and password for the remote system.
Local File System The backup XML file is stored locally. Cisco UCS Manager GUI displays the Filename field with an associated Browse button that let you specify the name and location for the backup file to be imported.
Protocol field
The protocol to use when communicating with the remote server. This can be:
FTP
TFTP
SCP
SFTP
Hostname field
The hostname or IP address from which the configuration file should be imported. Note
If you use ahostname rather than an IP address, you must configure a DNS server in Cisco UCS Manager.
Remote File field
The name of the XML configuration file.
User field
The username the system should use to log in to the remote server. This field does not apply if the protocol is TFTP.
Password field
The password for the remote server username. This field does not apply if the protocol is TFTP.
Cisco UCS Manager does not store this password. Therefore, you do not need to enter this password unless you intend to enable and run the import operation immediately. Step 7 Click OK . Step 8 In the confirmation dialog box, click OK .
If you set the Admin State to enabled, Cisco UCS Manager imports the configuration file from the network location. Depending upon which action you selected, the information in the file is either merged with the existing configuration or replaces the existing configuration. The import operation displays in the Import Operations table of the Import Configuration dialog box. Step 9 (Optional) To view the progress of the import operation, do the following:
If the operation does not automatically display in the Properties area, click the operation in the Import Operations table.
In the Properties area, click the down arrows on the FSM Details bar.
The FSM Details area expands and displays the operation status. Step 10 Click OK to close the Import Configuration dialog box.
The import operation continues to run until it is completed. To view the progress, re-open the Import Configuration dialog box. Running an Import Operation
You cannot import a Full State configuration file. You can import any of the following configuration files: Warning Node Has Slots In Importing States
All configuration
System configuration
Logical configuration Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the Work pane, click the General tab. Step 4 In the Actions area, click Import Configuration . Step 5 In the Import Operations table of the Import Configuration dialog box, click the operation that you want to run.
The details of the selected import operation display in the Properties area. Step 6 In the Properties area, complete the following fields:
In the Admin State field, click the Enabled radio button.
For all protocols except TFTP, enter the password for the username In the Password field.
Optional: Change the content of the other available fields. Step 7 Click Apply .
Cisco UCS Manager imports the configuration file from the network location. Depending upon which action you selected, the information in the file is either merged with the existing configuration or replaces the existing configuration. The import operation displays in the Import Operations table of the Import Configuration dialog box. Step 8 (Optional) To view the progress of the import operation, click the down arrows on the FSM Details bar.
The FSM Details area expands and displays the operation status. Step 9 Click OK to close the Import Configuration dialog box.
The import operation continues to run until it is completed. To view the progress, re-open the Import Configuration dialog box. Modifying an Import Operation Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the Work pane, click the General tab. Step 4 In the Actions area, click Import Configuration . Step 5 In the Import Operations area of the Import Configuration dialog box, click the import operation that you want to modify.
The details of the selected import operation display in the Properties area. If the import operation is in a disabled state, the fields are dimmed. Step 6 In the Admin State field, click the enabled radio button. Step 7 Modify the appropriate fields.
You do not have to enter the password unless you want to run the import operation immediately. Step 8 (Optional) If you do not want to run the import operation immediately, click the disabled radio button in the Admin State field. Step 9 Click OK . Deleting One or More Import Operations Warning Node Has Slots In Importing Statement Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the Work pane, click the General tab. Step 4 In the Actions area, click Import Configuration . Step 5 In the Import Operations table of the Backup Configuration dialog box, click the import operations that you want to delete. Tip
You cannot click an import operation in the table if the admin state of the operation is set to Enabled. Step 6 Click the Delete icon in the icon bar of the Import Operations table. Step 7 If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes . Step 8 In the Import Configuration dialog box, click one of the following: Option Description
Apply
Deletes the selected import operations without closing the dialog box.
OK
Deletes the selected import operations and closes the dialog box. Restoring the Configuration for a Fabric Interconnect Before You Begin Warning Node Has Slots In Importing State Park
Collect the following information that you will need to restore the system configuration:
Fabric interconnect management port IP address and subnet mask
Default gateway IP address
Backup server IP address and authentication credentials
Fully qualified name of a Full State backup file
Note
You must have access to a Full State configuration file to perform a system restore. You cannot perform a system restore with any other type of configuration or backup file.
Procedure Step 1 Connect to the console port. Step 2 If the fabric interconnect is off, power on the fabric interconnect.
You will see the power on self-test message as the fabric interconnect boots. Step 3 At the installation method prompt, enter gui . Step 4 If the system cannot access a DHCP server, you may be prompted to enter the following information:
IP address for the management port on the fabric interconnect
Subnet mask for the management port on the fabric interconnect
IP address for the default gateway assigned to the fabric interconnect Step 5 Copy the web link from the prompt into a web browser and go to the Cisco UCS Manager GUI launch page. Step 6 On the launch page, select Express Setup . Step 7 On the Express Setup page, select Restore From Backup and click Submit . Step 8 In the Protocol area of the Cisco UCS Manager Initial Setup page, select the protocol you want to use to upload the full state backup file:
SCP
TFTP
FTP
SFTP Step 9 In the Server Information area, complete the following fields: Name Description
Server IP
The IP address of the computer where the full state backup file is located. This can be a server, storage array, local drive, or any read/write media that the fabric interconnect can access through the network.
Backup File Path
The file path where the full state backup file is located, including the folder names and filename.
User ID
The username the system should use to log in to the remote server. This field does not apply if the protocol is TFTP.
Password
The password for the remote server username. This field does not apply if the protocol is TFTP. Step 10 Click Submit .
You can return to the console to watch the progress of the system restore.
The fabric interconnect logs in to the backup server, retrieves a copy of the specified full-state backup file, and restores the system configuration.
For a cluster configuration, you do not need to restore the secondary fabric interconnect. As soon as the secondary fabric interconnect reboots, Cisco UCS Manager sychronizes the configuration with the primary fabric interconnect.
Components are one of the most powerful features of Vue.js. They help you extend basic HTML elements to encapsulate reusable code. At a high level, Components are custom elements that Vue.js compiler would attach specified behavior to. In some cases, they may also appear as a native HTML element extended with the special is attribute. Using Components Registration
Weve learned in the previous sections that we can create a component constructor using Vue.extend() :
To use this constructor as a component, you need to register it with Vue.component(tag, constructor) :
Note that Vue.js does not enforce the W3C rules for custom tag-names (all-lowercase, must contain a hyphen) though following this convention is considered good practice.
Once registered, the component can now be used in a parent instances template as a custom element, my-component . Make sure the component is registered before you instantiate your root Vue instance. Heres the full example:
Which will render:
Note the components template replaces the custom element, which only serves as a mounting point . This behavior can be configured using the replace instance option.
Also note that components are provided a template instead of mounting with the el option! Only the root Vue instance (defined using new Vue ) will include an el to mount to). Local Registration
You dont have to register every component globally. You can make a component available only in the scope of another component by registering it with the components instance option:
The same encapsulation applies for other assets types such as directives, filters and transitions. Registration Sugar
To make things easier, you can directly pass in the options object instead of an actual constructor to Vue.component() and the component option. Vue.js will automatically call Vue.extend() for you under the hood: Component Option Caveats
Most of the options that can be passed into the Vue constructor can be used in Vue.extend() , with two special cases: data and el . Imagine we simply pass an object as data to Vue.extend() :
The problem with this is that the same data object will be shared across all instances of MyComponent ! This is most likely not what we want, so we should use a function that returns a fresh object as the data option:
The el option also requires a function value when used in Vue.extend() , for exactly the same reason. Template Parsing
Vue.js template engine is DOM-based and uses native parser that comes with the browser instead of providing a custom one. There are benefits to this approach when compared to string-based template engines, but there are also caveats. Templates have to be individually valid pieces of HTML. Some HTML elements have restrictions on what elements can appear inside them. Most common of these restrictions are:
a can not contain other interactive elements (e.g. buttons and other links)
li should be a direct child of ul or ol , and both ul and ol can only contain li
option should be a direct child of select , and select can only contain option (and optgroup )
table can only contain thead , tbody , tfoot and tr , and these elements should be direct children of table
tr can only contain th and td , and these elements should be direct children of tr
In practice these restriction can cause unexpected behavior. Although in simple cases it might appear to work, you can not rely on custom elements being expanded before browser validation. E.g. my-selectoption.../option/my-select is not a valid template even if my-select component eventually expands to select.../select .
Another consequence is that you can not use custom tags (including custom elements and special tags like component , template and partial ) inside of select , table and other elements with similar restrictions. Custom tags will be hoisted out and thus not render properly.
In case of a custom element you should use the is special attribute:
In case of a template inside of a table you should use tbody , as tables are allowed to have multiple tbody : Props Passing Data with Props
Every component instance has its own isolated scope . This means you cannot (and should not) directly reference parent data in a child components template. Data can be passed down to child components using props .
A prop is a field on a components data that is expected to be passed down from its parent component. A child component needs to explicitly declare the props it expects to receive using the props option:
Then, we can pass a plain string to it like so:
Result: camelCase vs. kebab-case
HTML attributes are case-insensitive. When using camelCased prop names as attributes, you need to use their kebab-case (hyphen-delimited) equivalents: Dynamic Props
Similar to binding a normal attribute to an expression, we can also use v-bind for dynamically binding props to data on the parent. Whenever the data is updated in the parent, it will also flow down to the child:
It is often simpler to use the shorthand syntax for v-bind :
Result:
Literal vs. Dynamic
A common mistake beginners tend to make is attempting to pass down a number using the literal syntax:
However, since this is a literal prop, its value is passed down as a plain string '1' , instead of an actual number. If we want to pass down an actual JavaScript number, we need to use the dynamic syntax to make its value be evaluated as a JavaScript expression: Prop Binding Types
By default, all props form a one-way-down binding between the child property and the parent one: when the parent property updates, it will flow down to the child, but not the other way around. This default is meant to prevent child components from accidentally mutating the parents state, which can make your apps data flow harder to reason about. However, it is also possible to explicitly enforce a two-way or a one-time binding with the .sync and .once binding type modifiers :
Compare the syntax:
The two-way binding will sync the change of childs msg property back to the parents parentMsg property. The one-time binding, once set up, will not sync future changes between the parent and the child.
Note that if the prop being passed down is an Object or an Array, it is passed by reference. Mutating the Object or Array itself inside the child will affect parent state, regardless of the binding type you are using. Prop Validation
It is possible for a component to specify the requirements for the props it is receiving. This is useful when you are authoring a component that is intended to be used by others, as these prop validation requirements essentially constitute your components API, and ensure your users are using your component correctly. Instead of defining the props as an array of strings, you can use the object hash format that contain validation requirements:
The type can be one of the following native constructors:
String
Number
Boolean
Function
Object
Array
In addition, type can also be a custom constructor function and the assertion will be made with an instanceof check.
When a prop validation fails, Vue will refuse to set the value on the child component, and throw a warning if using the development build. Parent-Child Communication Parent Chain
A child component holds access to its parent component as this.$parent . A root Vue instance will be available to all of its descendants as this.$root . Each parent component has an array, this.$children , which contains all its child components.
Although its possible to access any instance in the parent chain, you should avoid directly relying on parent data in a child component and prefer passing data down explicitly using props. In addition, it is a very bad idea to mutate parent state from a child component, because:
It makes the parent and child tightly coupled;
It makes the parent state much harder to reason about when looking at it alone, because its state may be modified by any child! Ideally, only a component itself should be allowed to modify its own state. Custom Events
All Vue instances implement a custom event interface that facilitates communication within a component tree. This event system is independent from the native DOM events and works differently.
Each Vue instance is an event emitter that can:
Listen to events using $on() ;
Trigger events on self using $emit() ;
Dispatch an event that propagates upward along the parent chain using $dispatch() ;
Broadcast an event that propagates downward to all descendants using $broadcast() .
Unlike DOM events, Vue events will automatically stop propagation after triggering callbacks for the first time along a propagation path, unless the callback explicitly returns true .
A simple example: v-on for Custom Events
The example above is pretty nice, but when we are looking at the parents code, its not so obvious where the 'child-msg' event comes from. It would be better if we can declare the event handler in the template, right where the child component is used. To make this possible, v-on can be used to listen for custom events when used on a child component:
This makes things very clear: when the child triggers the 'child-msg' event, the parents handleIt method will be called. Any code that affects the parents state will be inside the handleIt parent method; the child is only concerned with triggering the event. Child Component Refs
Despite the existence of props and events, sometimes you might still need to directly access a child component in JavaScript. To achieve this you have to assign a reference ID to the child component using v-ref . For example:
When v-ref is used together with v-for , the ref you get will be an Array or an Object containing the child components mirroring the data source. Content Distribution with Slots
When using components, it is often desired to compose them like this:
There are two things to note here:
The app component does not know what content may be present inside its mount target. It is decided by whatever parent component that is using app .
The app component very likely has its own template.
To make the composition work, we need a way to interweave the parent content and the components own template. This is a process called content distribution (or transclusion if you are familiar with Angular). Vue.js implements a content distribution API that is modeled after the current Web Components spec draft, using the special slot element to serve as distribution outlets for the original content. Compilation Scope
Before we dig into the API, lets first clarify which scope the contents are compiled in. Imagine a template like this:
Should the msg be bound to the parents data or the child data? The answer is parent. A simple rule of thumb for component scope is:
Everything in the parent template is compiled in parent scope; everything in the child template is compiled in child scope.
A common mistake is trying to bind a directive to a child property/method in the parent template:
Assuming someChildProperty is a property on the child component, the example above would not work as intended. The parents template should not be aware of the state of a child component.
If you need to bind child-scope directives on a component root node, you should do so in the child components own template:
Similarly, distributed content will be compiled in the parent scope. Single Slot
Parent content will be discarded unless the child component template contains at least one slot outlet. When there is only one slot with no attributes, the entire content fragment will be inserted at its position in the DOM, replacing the slot itself.
Anything originally inside the slot tags is considered fallback content . Fallback content is compiled in the child scope and will only be displayed if the hosting element is empty and has no content to be inserted.
Suppose we have a component with the following template:
Parent markup that uses the component:
The rendered result will be: Named Slots
slot elements have a special attribute, name , which can be used to further customize how content should be distributed. You can have multiple slots with different names. A named slot will match any element that has a corresponding slot attribute in the content fragment.
There can still be one unnamed slot, which is the default slot that serves as a catch-all outlet for any unmatched content. If there is no default slot, unmatched content will be discarded.
For example, suppose we have a multi-insertion component with the following template:
Parent markup:
The rendered result will be:
The content distribution API is a very useful mechanism when designing components that are meant to be composed together. Dynamic Components
You can use the same mount point and dynamically switch between multiple components by using the reserved component element and dynamically bind to its is attribute: keep-alive
If you want to keep the switched-out components alive so that you can preserve its state or avoid re-rendering, you can add a keep-alive directive param: activate Hook
When switching components, the incoming component might need to perform some asynchronous operation before it should be swapped in. To control the timing of component swapping, implement the activate hook on the incoming component:
Note the activate hook is only respected during dynamic component swapping or the initial render for static components - it does not affect manual insertions with instance methods. transition-mode
The transition-mode param attribute allows you to specify how the transition between two dynamic components should be executed.
By default, the transitions for incoming and outgoing components happen simultaneously. This attribute allows you to configure two other modes:
in-out : New component transitions in first, current component transitions out after incoming transition has finished.
out-in : Current component transitions out first, new component transitions in after outgoing transition has finished.
Example A B Misc Components and v-for
You can directly use v-for on the custom component, like any normal element:
However, this wont pass any data to the component, because components have isolated scopes of their own. In order to pass the iterated data into the component, we should also use props:
The reason for not automatically injecting item into the component is because that makes the component tightly coupled to how v-for works. Being explicit about where its data comes from makes the component reusable in other situations. Authoring Reusable Components
When authoring components, it is good to keep in mind whether you intend to reuse this component somewhere else later. It is OK for one-off components to have some tight coupling with each other, but reusable components should define a clean public interface.
The API for a Vue.js component essentially comes in three parts - props, events and slots:
Props allow the external environment to feed data to the component;
Events allow the component to trigger actions in the external environment;
Slots allow the external environment to insert content into the components view structure.
With the dedicated shorthand syntax for v-bind and v-on , the intents can be clearly and succinctly conveyed in the template: Async Components
In large applications, we may need to divide the app into smaller chunks, and only load a component from the server when it is actually needed. To make that easier, Vue.js allows you to define your component as a factory function that asynchronously resolves your component definition. Vue.js will only trigger the factory function when the component actually needs to be rendered, and will cache the result for future re-renders. For example:
The factory function receives a resolve callback, which should be called when you have retrieved your component definition from the server. You can also call reject(reason) to indicate the load has failed. The setTimeout here is simply for demonstration; How to retrieve the component is entirely up to you. One recommended approach is to use async components together with Webpacks code-splitting feature: Assets Naming Convention
Some assets, such as components and directives, appear in templates in the form of HTML attributes or HTML custom tags. Since HTML attribute names and tag names are case-insensitive , we often need to name our assets using kebab-case instead of camelCase, which can be a bit inconvenient.
Vue.js actually supports naming your assets using camelCase or PascalCase, and automatically resolves them as kebab-case in templates (similar to the name conversion for props):
This works nicely with ES6 object literal shorthand: Recursive Component
Components can recursively invoke itself in its own template, however, it can only do so when it has the name option:
A component like the above will result in a max stack size exceeded error, so make sure recursive invocation is conditional. When you register a component globally using Vue.component() , the global ID is automatically set as the components name option. Fragment Instance
When you use the template option, the content of the template will replace the element the Vue instance is mounted on. It is therefore recommended to always have a single root-level, plain element in templates.
Instead of templates like this:
Prefer this:
There are multiple conditions that will turn a Vue instance into a fragment instance :
Template contains multiple top-level elements.
Template contains only plain text.
Template contains only another component (which can potentially be a fragment instance itself).
Template contains only an element directive, e.g. partial or vue-routers router-view .
Template root node has a flow-control directive, e.g. v-if or v-for .
The reason is that all of the above cause the instance to have an unknown number of top-level elements, so it has to manage its DOM content as a fragment. A fragment instance will still render the content correctly. However, it will not have a root node, and its $el will point to an anchor node, which is an empty Text node (or a Comment node in debug mode).
Whats more important though, is that non-flow-control directives, non-prop attributes and transitions on the component element will be ignored , because there is no root element to bind them to:
There are, of course, valid use cases for fragment instances, but it is in general a good idea to give your component template a single, plain root element. It ensures directives and attributes on the component element to be properly transferred, and also results in slightly better performance. Inline Template
When the inline-template special attribute is present on a child component, the component will use its inner content as its template, rather than treating it as distributed content. This allows more flexible template-authoring.
However, inline-template makes the scope of your templates harder to reason about, and makes the components template compilation un-cachable. As a best practice, prefer defining templates inside the component using the template option. Caught a mistake or want to contribute to the documentation? Edit this page on Github!
Contents Warning Node Has Slots In Importing Staten Island Backup and Export Configuration
When you perform a backup through Cisco UCS Manager , you take a snapshot of all or part of the system configuration and export the file to a location on your network. You cannot use Cisco UCS Manager to back up data on the servers.
You can perform a backup while the system is up and running. The backup operation only saves information from the management plane. It does not have any impact on the server or network traffic. Backup Types
You can perform one or more of the following types of backups through Cisco UCS Manager :
Full state A binary file that includes a snapshot of the entire system. You can use the file generated from this backup to restore the system during disaster recovery. This file can restore or rebuild the configuration on the original fabric interconnect, or recreate the configuration on a different fabric interconnect. You cannot use this file for an import.
All configuration An XML file that includes all system and logical configuration settings. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore.
System configuration An XML file that includes all system configuration settings such as usernames, roles, and locales. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore.
Logical configuration An XML file that includes all logical configuration settings such as service profiles, VLANs, VSANs, pools, and policies. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore. Considerations and Recommendations for Backup Operations
Before you create a backup operation, consider the following: Backup Locations
The backup location is the destination or folder on the network where you want Cisco UCS Manager to export the backup file. You can maintain only one backup operation for each location where you plan to save a backup file. Potential to Overwrite Backup Files
If you rerun a backup operation without changing the filename, Cisco UCS Manager overwrites the existing file on the server. To avoid overwriting existing backup files, change the filename in the backup operation or copy the existing file to another location. Multiple Types of Backups
You can run and export more than one type of backup to the same location. You need to change the backup type before you rerun the backup operation. We recommend that you change the filename for easier identification of the backup type and to avoid overwriting the existing backup file. Scheduled Backups
You cannot schedule a backup operation. You can, however, create a backup operation in advance and leave the admin state disabled until you are ready to run the backup. Cisco UCS Manager does not run the backup operation, save, or export the configuration file until you set the admin state of the backup operation to enabled. Incremental Backups
You cannot perform incremental backups of the Cisco UCS Manager system configuration. Backwards Compatibility
Starting with Release 1.1(1) of the Cisco UCS Manager , full state backups are encrypted so that passwords and other sensitive information are not exported as clear text. As a result, full state backups made from Release 1.1(1) or later cannot be restored to a Cisco UCS instance running an earlier software release. Import Configuration
You can import any configuration file that was exported from Cisco UCS Manager . The file does not need to have been exported from the same Cisco UCS Manager .
The import function is available for all configuration, system configuration, and logical configuration files. You can perform an import while the system is up and running. An import operation modifies information on the management plane only. Some modifications caused by an import operation, such as a change to a vNIC assigned to a server, can cause a server reboot or other operations that disrupt traffic.
You cannot schedule an import operation. You can, however, create an import operation in advance and leave the admin state disabled until you are ready to run the import. Cisco UCS Manager will not run the import operation on the configuration file until you set the admin state to enabled.
You can maintain only one import operation for each location where you saved a configuration backup file. Import Methods
You can use one of the following methods to import and update a system configuration through Cisco UCS Manager :
Merge The information in the imported configuration file is compared with the existing configuration information. If there are conflicts, the import operation overwrites the information on the Cisco UCS instance with the information in the import configuration file.
Replace The current configuration information is replaced with the information in the imported configuration file one object at a time. System Restore
You can restore a system configuration from any full state backup file that was exported from Cisco UCS Manager . The file does not need to have been exported from the Cisco UCS Manager on the system that you are restoring.
The restore function is only available for a full state backup file. You cannot import a full state backup file. You perform a restore through the initial system setup.
You can use the restore function for disaster recovery. Required User Role for Backup and Import Operations
You must have a user account that includes the admin role to create and run backup and import operations.
Backup Operations Creating a Backup Operation Before You Begin
Obtain the backup server IP address and authentication credentials.
Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the Work pane, click the General tab. Step 4 In the Actions area, click Backup Configuration . Step 5 In the Backup Configuration dialog box, click Create Backup Operation . Step 6 In the Create Backup Operation dialog box, complete the following fields: Name Description
Admin State field
This can be:
enabled Cisco UCS Manager runs the backup operation as soon as you click OK .
disabled Cisco UCS Manager does not run the backup operation when you click OK . If you select this option, all fields in the dialog box remain visible. However, you must manually run the backup from the Backup Configuration dialog box.
Type field
The information saved in the backup configuration file. This can be:
Full state A binary file that includes a snapshot of the entire system. You can use the file generated from this backup to restore the system during disaster recovery. This file can restore or rebuild the configuration on the original fabric interconnect, or recreate the configuration on a different fabric interconnect. You cannot use this file for an import.
All configuration An XML file that includes all system and logical configuration settings. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore.
System configuration An XML file that includes all system configuration settings such as usernames, roles, and locales. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore.
Logical configuration An XML file that includes all logical configuration settings such as service profiles, VLANs, VSANs, pools, and policies. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore.
Preserve Identities check box
If this check box is checked, the backup file preserves all identities derived from pools, including the MAC addresses, WWPN, WWNN, and UUIDs.
Location of the Backup File field
Where the backup file should be saved. This can be:
Remote File System The backup XML file is saved to a remote server. Cisco UCS Manager GUI displays the fields described below that allow you to specify the protocol, host, filename, username, and password for the remote system.
Local File System The backup XML file is saved locally. Cisco UCS Manager GUI displays the Filename field with an associated Browse button that let you specify the name and location for the backup file. Note
Once you click OK , the location cannot be changed.
Protocol field
The protocol to use when communicating with the remote server. This can be:
FTP
TFTP
SCP
SFTP
Hostname field
The hostname or IP address of the location where the backup file is stored. This can be a server, storage array, local drive, or any read/write media that the fabric interconnect can access through the network. Note
If you use ahostname rather than an IP address, you must configure a DNS server in Cisco UCS Manager.
Remote File field
The full path to the backup configuration file. This field can contain the filename as well as the path. If you omit the filename, the backup procedure assigns a name to the file.
User field
The username the system should use to log in to the remote server. This field does not apply if the protocol is TFTP.
Password field
The password for the remote server username. This field does not apply if the protocol is TFTP.
Cisco UCS Manager does not store this password. Therefore, you do not need to enter this password unless you intend to enable and run the backup operation immediately. Step 7 Click OK . Step 8 If Cisco UCS Manager displays a confirmation dialog box, click OK .
If you set the Admin State field to enabled, Cisco UCS Manager takes a snapshot of the configuration type that you selected and exports the file to the network location. The backup operation displays in the Backup Operations table in the Backup Configuration dialog box. Step 9 (Optional) To view the progress of the backup operation, do the following:
If the operation does not display in the Properties area, click the operation in the Backup Operations table.
In the Properties area, click the down arrows on the FSM Details bar.
The FSM Details area expands and displays the operation status. Step 10 Click OK to close the Backup Configuration dialog box.
The backup operation continues to run until it is completed. To view the progress, re-open the Backup Configuration dialog box. Running a Backup Operation Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the Work pane, click the General tab. Step 4 In the Actions area, click Backup Configuration . Step 5 In the Backup Operations table of the Backup Configuration dialog box, click the backup operation that you want to run.
The details of the selected backup operation display in the Properties area. Step 6 In the Properties area, complete the following fields:
In the Admin State field, click the Enabled radio button.
For all protocols except TFTP, enter the password for the username in the Password field.
Optional: Change the content of the other available fields. Step 7 Click Apply .
Cisco UCS Manager takes a snapshot of the configuration type that you selected and exports the file to the network location. The backup operation displays in the Backup Operations table in the Backup Configuration dialog box. Step 8 (Optional) To view the progress of the backup operation, click the down arrows on the FSM Details bar.
The FSM Details area expands and displays the operation status. Step 9 Click OK to close the Backup Configuration dialog box.
The backup operation continues to run until it is completed. To view the progress, re-open the Backup Configuration dialog box. Modifying a Backup Operation
You can modify a backup operation to save a file of another backup type to that location or to change the filename and avoid overwriting previous backup files. Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the Work pane, click the General tab. Step 4 In the Actions area, click Backup Configuration . Step 5 In the Backup Operations area of the Backup Configuration dialog box, click the backup operation that you want to modify.
The details of the selected backup operation display in the Properties area. If the backup operation is in a disabled state, the fields are dimmed. Step 6 In the Admin State field, click the enabled radio button. Step 7 Modify the appropriate fields.
You do not have to enter the password unless you want to run the backup operation immediately. Step 8 (Optional) If you do not want to run the backup operation immediately, click the disabled radio button in the Admin State field. Step 9 Click OK . Deleting One or More Backup Operations Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the Work pane, click the General tab. Step 4 In the Actions area, click Backup Configuration . Step 5 In the Backup Operations table of the Backup Configuration dialog box, click the backup operations that you want to delete. Tip
You cannot click a backup operation in the table if the admin state of the operation is set to Enabled. Step 6 Click the Delete icon in the icon bar of the Backup Operations table. Step 7 If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes . Step 8 In the Backup Configuration dialog box, click one of the following: Option Description
Apply
Deletes the selected backup operations without closing the dialog box.
OK
Deletes the selected backup operations and closes the dialog box.
Import Operations Creating an Import Operation
You cannot import a Full State configuration file. You can import any of the following configuration files:
All configuration
System configuration
Logical configuration Before You Begin
Collect the following information that you will need to import a configuration file:
Backup server IP address and authentication credentials
Fully qualified name of a backup file
Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the Work pane, click the General tab. Step 4 In the Actions area, click Import Configuration . Step 5 In the Import Configuration dialog box, click Create Import Operation . Step 6 In the Create Import Operation dialog box, complete the following fields: Name Description
Admin State field
This can be:
enabled Cisco UCS runs the import operation as soon as you click OK .
disabled Cisco UCS does not run the import operation when you click OK . If you select this option, all fields in the dialog box remain visible. However, you must manually run the import from the Import Configuration dialog box.
Action field
You can select:
Merge The configuration information is merged with the existing information. If there are conflicts, the system replaces the information on the current system with the information in the import configuration file.
Replace The system takes each object in the import configuration file and overwrites the corresponding object in the current configuration.
Location of the Import File field
Where the backup file that you want to import is located. This can be:
Remote File System The backup XML file is stored on a remote server. Cisco UCS Manager GUI displays the fields described below that allow you to specify the protocol, host, filename, username, and password for the remote system.
Local File System The backup XML file is stored locally. Cisco UCS Manager GUI displays the Filename field with an associated Browse button that let you specify the name and location for the backup file to be imported.
Protocol field
The protocol to use when communicating with the remote server. This can be:
FTP
TFTP
SCP
SFTP
Hostname field
The hostname or IP address from which the configuration file should be imported. Note
If you use ahostname rather than an IP address, you must configure a DNS server in Cisco UCS Manager.
Remote File field
The name of the XML configuration file.
User field
The username the system should use to log in to the remote server. This field does not apply if the protocol is TFTP.
Password field
The password for the remote server username. This field does not apply if the protocol is TFTP.
Cisco UCS Manager does not store this password. Therefore, you do not need to enter this password unless you intend to enable and run the import operation immediately. Step 7 Click OK . Step 8 In the confirmation dialog box, click OK .
If you set the Admin State to enabled, Cisco UCS Manager imports the configuration file from the network location. Depending upon which action you selected, the information in the file is either merged with the existing configuration or replaces the existing configuration. The import operation displays in the Import Operations table of the Import Configuration dialog box. Step 9 (Optional) To view the progress of the import operation, do the following:
If the operation does not automatically display in the Properties area, click the operation in the Import Operations table.
In the Properties area, click the down arrows on the FSM Details bar.
The FSM Details area expands and displays the operation status. Step 10 Click OK to close the Import Configuration dialog box.
The import operation continues to run until it is completed. To view the progress, re-open the Import Configuration dialog box. Running an Import Operation
You cannot import a Full State configuration file. You can import any of the following configuration files: Warning Node Has Slots In Importing States
All configuration
System configuration
Logical configuration Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the Work pane, click the General tab. Step 4 In the Actions area, click Import Configuration . Step 5 In the Import Operations table of the Import Configuration dialog box, click the operation that you want to run.
The details of the selected import operation display in the Properties area. Step 6 In the Properties area, complete the following fields:
In the Admin State field, click the Enabled radio button.
For all protocols except TFTP, enter the password for the username In the Password field.
Optional: Change the content of the other available fields. Step 7 Click Apply .
Cisco UCS Manager imports the configuration file from the network location. Depending upon which action you selected, the information in the file is either merged with the existing configuration or replaces the existing configuration. The import operation displays in the Import Operations table of the Import Configuration dialog box. Step 8 (Optional) To view the progress of the import operation, click the down arrows on the FSM Details bar.
The FSM Details area expands and displays the operation status. Step 9 Click OK to close the Import Configuration dialog box.
The import operation continues to run until it is completed. To view the progress, re-open the Import Configuration dialog box. Modifying an Import Operation Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the Work pane, click the General tab. Step 4 In the Actions area, click Import Configuration . Step 5 In the Import Operations area of the Import Configuration dialog box, click the import operation that you want to modify.
The details of the selected import operation display in the Properties area. If the import operation is in a disabled state, the fields are dimmed. Step 6 In the Admin State field, click the enabled radio button. Step 7 Modify the appropriate fields.
You do not have to enter the password unless you want to run the import operation immediately. Step 8 (Optional) If you do not want to run the import operation immediately, click the disabled radio button in the Admin State field. Step 9 Click OK . Deleting One or More Import Operations Warning Node Has Slots In Importing Statement Procedure Step 1 In the Navigation pane, click the Admin tab. Step 2 Click the All node. Step 3 In the Work pane, click the General tab. Step 4 In the Actions area, click Import Configuration . Step 5 In the Import Operations table of the Backup Configuration dialog box, click the import operations that you want to delete. Tip
You cannot click an import operation in the table if the admin state of the operation is set to Enabled. Step 6 Click the Delete icon in the icon bar of the Import Operations table. Step 7 If Cisco UCS Manager GUI displays a confirmation dialog box, click Yes . Step 8 In the Import Configuration dialog box, click one of the following: Option Description
Apply
Deletes the selected import operations without closing the dialog box.
OK
Deletes the selected import operations and closes the dialog box. Restoring the Configuration for a Fabric Interconnect Before You Begin Warning Node Has Slots In Importing State Park
Collect the following information that you will need to restore the system configuration:
Fabric interconnect management port IP address and subnet mask
Default gateway IP address
Backup server IP address and authentication credentials
Fully qualified name of a Full State backup file
Note
You must have access to a Full State configuration file to perform a system restore. You cannot perform a system restore with any other type of configuration or backup file.
Procedure Step 1 Connect to the console port. Step 2 If the fabric interconnect is off, power on the fabric interconnect.
You will see the power on self-test message as the fabric interconnect boots. Step 3 At the installation method prompt, enter gui . Step 4 If the system cannot access a DHCP server, you may be prompted to enter the following information:
IP address for the management port on the fabric interconnect
Subnet mask for the management port on the fabric interconnect
IP address for the default gateway assigned to the fabric interconnect Step 5 Copy the web link from the prompt into a web browser and go to the Cisco UCS Manager GUI launch page. Step 6 On the launch page, select Express Setup . Step 7 On the Express Setup page, select Restore From Backup and click Submit . Step 8 In the Protocol area of the Cisco UCS Manager Initial Setup page, select the protocol you want to use to upload the full state backup file:
SCP
TFTP
FTP
SFTP Step 9 In the Server Information area, complete the following fields: Name Description
Server IP
The IP address of the computer where the full state backup file is located. This can be a server, storage array, local drive, or any read/write media that the fabric interconnect can access through the network.
Backup File Path
The file path where the full state backup file is located, including the folder names and filename.
User ID
The username the system should use to log in to the remote server. This field does not apply if the protocol is TFTP.
Password
The password for the remote server username. This field does not apply if the protocol is TFTP. Step 10 Click Submit .
You can return to the console to watch the progress of the system restore.
The fabric interconnect logs in to the backup server, retrieves a copy of the specified full-state backup file, and restores the system configuration.
For a cluster configuration, you do not need to restore the secondary fabric interconnect. As soon as the secondary fabric interconnect reboots, Cisco UCS Manager sychronizes the configuration with the primary fabric interconnect.
