Step 1
| Log-in to
CISCO VIM
Insight.
|
Step 2
| In the
Navigation pane, expand the
Pre-Install
Section.
|
Step 3
| Click
Blueprint Setup.
|
Step 4
| On the
Blueprint Initial Setup page of the Cisco VIM Insight
, complete the following fields:
Name
|
Description
|
Blueprint Name field
|
Enter the name for the blueprint configuration.
|
Platform Type drop-down list
|
|
Tenant Network drop-down list
|
Choose one of the following tenant network types:
-
Linux Bridge/VXLAN
-
OVS/VLAN
-
VTS/VLAN
-
VPP/VLAN
-
ACI/VLAN
Note
|
when VTS/VLAN or ACI/VLAN is selected then respective tabs are available on
Blueprint setup
|
|
Pod Type drop-down list
|
Choose one of the following pod type :
-
Fullon(By Default)
-
Micro
-
UMHC
Note
|
UMHC pod type is only supported for OVS/VLAN tenant type.
|
Note
|
Pod type micro is supported for OVS/VLAN, ACI/VLAN,VPP/VLAN.
|
|
Ceph Mode drop-down list
|
Choose one of the following Ceph types:
|
Optional Features and Services checkbox.
|
Swiftstack, LDAP, Syslog Export Settings, Install Mode, TorSwitch Information,
TLS, Nfvmon, Pod Name, VMTP, Nfvbench, Auto Backup, Heat, Keystone v3, etc.
If
any one is selected, the corresponding section is visible in various Blueprint
sections.
By
default all options are disabled.
|
Import Existing YAML file
|
If
you have an existing C Series YAML file you can use this feature to upload the
file.
Insight will automatically fill in the fields and if any mandatory field is
missed then would highlight it in the respective section.
|
|
Step 5
| Click
Physical Setup to advance to the
Registry Setup configuration page. Fill in the
following details for Registry Setup.
Name
|
Description
|
Registry User Name text
field
|
User-Name for Registry (Mandatory).
|
Registry Password text field
|
Password for Registry (Mandatory).
|
Registry Email text field
|
Email ID for Registry (Mandatory).
|
Once all
Mandatory fields are filled, the
Validation Check Registry page will indicate a green
tick.
|
Step 6
| Click
CIMC
Common tab and complete the following fields:
Name
|
Description
|
User Name disabled
field
|
By
default value is Admin.
|
Password text field
|
Enter Password for UCSM Common (Mandatory).
|
|
Step 7
| Click
Networking to advance to the networking section of
the Blueprint.
Name
|
Description
|
Domain Name field.
|
Enter the domain name
(Mandatory).
|
NTP Servers field.
|
Enter a maximum of four and minimum of one IPv4 and/or IPv6 addresses in the
table.
|
Domain Name Servers field
|
Enter a maximum of three and minimum of one IPv4 and/or IPv6 addresses
|
HTTP Proxy Server field
|
If
your configuration uses an HTTP proxy server, enter the IP address of the
server.
|
HTTPS Proxy Server field.
|
If
your configuration uses an HTTPS proxy server, enter the IP address of the
server.
|
Networks table
|
Network table is pre-populated with segments. To add Networks you can either
clear all the table using
Delete all
or click
Edit icon for each segment and fill in the details.
You
can add, edit, or delete network information in the table.
|
|
Step 8
| Click
Edit to enter new entries (networks) to the table.
Specify the following fields in the
Edit Entry
to Networks dialog:
Name
|
Description
|
Segment drop-down list
|
Default is already selected.
When you add/edit the segment then the following are the segment types
available and you can select only one from dropdown list.
-
API
-
Management/provision
-
Tenant
-
Storage
-
External
-
Provider
-
ACIINFRA
Note
|
Aciinfra segment is available only when ACI/VLAN tenant type is selected)
Depending upon the segment some of the entries below are not needed. Please
refer to the example file in openstack-configs dir for details.
|
|
VLAN field
|
Enter the VLAN ID. For Segment - Provider , the VLAN ID value is always
none.
|
Subnet field
|
Enter the IPv4 address for the subnet.
|
IPv6 Subnet field
|
Enter Ipv6 Address. This field will be available only for Management provision
and API.
|
Gateway field
|
Enter the IPv4 address for the Gateway.
|
IPv6 Gateway field
|
Enter the IPv6 address for the Gateway. This will support for API and
management provision
|
Pool field
|
Enter the pool information in the required format, for example:
10.1.1.5-10.1.1.10,10.2.1.5-10.2.1.10
This field is only available for the Mgmt/Provision, Storage, and Tenant
segments.
|
IPv6 Pool field
|
Enter the pool information in the required format, for example:
10.1.1.5-10.1.1.10,10.2.1.5-10.2.1.10
This field is only available only for Management provision
|
Click
Save.
|
|
Step 9
| On the
Servers
and Roles page of the
Cisco
VIM Suite wizard, click
Add
(+) to add a new entry in the table, and complete the following
fields:
You can edit
or delete existing entries in the
Server and Roles table.
Name
|
Description
|
Add Entry to Servers and Roles
.
Note
|
when Pod type micro is selected then all the three servers will be associated
with control, compute and block storage role.
|
For
Example:
Roles
-
Block Storage
-
-Server 1
-
-Server 2
-
-Server 3
-
Control
-
-Server 1
-
-Server 2
-
-Server 3
-
Compute
-
-Server 1
-
-Server 2
-
-Server 3
Note
|
When Pod type UMHC is selected then auto ToR configuration is not supported and
the ToR info at server and roles level is not allowed to be entered.
|
|
Click
Edit or
+ to add a new server and role to the table.
Server Name
|
Entry the server name .
|
Rack
ID field
|
The rack ID for the server.
|
VIC
Slot field
|
Enter a VIC Slot.
|
Management IPv6field
|
This is optional field. Enter Ipv6 format address
|
CIMC IP field
|
Enter a IP address.
|
CIMC
Username field
|
Enter a Username.
|
CIMC Password field
|
Enter a Password for CIMC
|
Select the
Role from the drop down list
|
Choose Control or Compute or Block Storage from the drop-down
list.
|
Management IP
|
It is an optional field but if provided for one server then it
is mandatory to provide it for other servers.
|
|
Click
Save or Add .
|
On
clicking
Save or Add all information related to Servers and Roles
gets saved.
|
|
If
Configure ToR checkbox is
Truewith at-least one switch detail, these fields will be
displayed for each server and this is similar to DP Tor:
Port Channel and Switch Name (Mandatory if Configure ToR is
true)
|
-
Port
Channel field
-
Switch
Name field
-
Switch
Port Info field
|
|
DP
ToR (Only for Control and Compute) : Mandatory if Intel NIC and Configure TOR
is True.
|
-
Port
Channel field
-
Switch
Name field
-
Switch
Port Info field
|
|
SRIOV TOR INFO (Only for Compute Nodes). It is mandatory in server and
roles if Intel NIC and Configure TOR is True. Switch Name (Mandatory if
Configure ToR is true). This field appears only when Intel NIC support is
true, as Auto TOR config is not supported in VIC_NIC combo
|
-
Switch
Name field
-
Switch
Port Info field
|
|
Intel SRIOV VFS (valid for Intel NIC testbeds) and can be
integer.
|
For
SRIOV support for Intel NIC. By Default, SRIOV support is disabled. To enable,
define a value in the range # * 1-32 when INTEL_NIC_SUPPORT is set True (X710
Max VFs = 32) # * 1-63 when CISCO_VIC_INTEL_SRIOV is set True (X520 Max VFs =
63)
|
INTEL_SRIOV_PHYS_PORTS (valid for Intel NIC test beds) and can be of value 2 or
4 (default is 2)
|
In
some cases the # of Physical SRIOV port needed is 4; to meet that requirement,
define the following: # this is optional, if nothing is defined code will
assume it to be 2; the only 2 integer values this parameter # takes is 2 or 4
and is true when INTEL_NIC_SUPPORT is True and INTEL_SRIOV_VFS is valid
|
Click
Save or Add .
|
On
clicking
Save or Add all information related to Servers and Roles
gets saved.
|
Disable Hyper threading
|
Default value is false.
You can set it as true or false.
|
Click
Save or Add button.
|
If
all mandatory fields are filled, click
Save or Add button information for Servers and Roles.
|
Note
| Maximum
two ToR info needs to be configured for each connection type on each node
(control, compute and block_storage node).
|
Note
| If pod
type UMHC is selected then CISCO_VIC_INTEL_SRIOV is enabled to be TRUE.
|
Note
| For
Tenant type
ACI/VLAN, port channel for each ToR port will not be
available in servers and roles, as APIC will automatically assign port-channel
numbers.
|
|
Step 10
| Click
ToR Switch
checkbox in
Blueprint Initial Setup to enable the
TOR SWITCH
configuration page. It is an
Optional
section in Blueprint Setup but once all the fields are filled, it becomes a
part of the Blueprint.
Name
|
Description
|
Configure TOR
optional checkbox.
Note
|
If
UMHC is selected as podtype, configure TOR is not allowed.
|
|
If
you enable this checkbox configure tor section would be changed from false to
true.
Note
|
Configure tor is true then ToR switch info maps in servers
|
|
TOR Switch Information mandatory table if you want to enter
ToR information.
|
Click
+ to add information for ToR Switch.
Name
|
Description
|
Name
|
ToR Switch Name.
|
Username
|
TOR switch username
|
Password
|
ToR switch Password
|
SSH IP
|
TOR switch ssh ip
|
SSN Num
|
TOR switch ssn num
|
VPC Peer Keepalive
|
Peer Management IP. Do not define if there is no peer
|
VPC Domain
|
Do not define if there is no peer
|
VPC Peer Port Info
|
Interface for vpc peer ports
|
VPC Peer VLAN Info
|
vlan ids for vpc peer ports (optional)
|
BR Management Port Info
|
Management interface of build node
|
BR Management PO Info
|
Port channel number for management interface of build node
|
|
Click
Save.
|
Note
|
When
tenant type ACI/VLAN is selected, the TOR switch information table differs and
is mandatory.
|
Name
|
Description
|
Configure ToR
|
Is
not checked, as by default ACI will configure the ToRs
|
|
Click
+ to add information for ToR Switch
Name
|
Description
|
Host Name
|
ToR switch name.
|
VPC Peerkeep alive
|
Peer info must exist in pair.
|
VPC Domain
|
Enter an Integer.
|
BR Management Port Info
|
Enter Br management port info eg. Eth1/19, must have a pair in
the peer switch.
|
Enter Node ID
|
Entered Integer must be unique.
|
|
|
Step 11
| Click
OpenStack
Setup Tab to advance to the
OpenStack Setup page.
|
Step 12
| In the
OpenStack Setup page of the Cisco VIM Insight wizard,
complete the following fields:
Name
|
Description
|
Neutron
|
Neutron fields would change on the basis of
Tenant Network Type Selection from
Blueprint Initial Setup. Following are the options
available for Neutron:
Tenant Network Type
|
Auto Filled based on the Tenant Network Type selection in
Blueprint Initial Setup page.
|
Mechanism Drivers
|
Auto Filled based on the Tenant Network Type selection in
Blueprint Initial Setup page.
|
NFV Hosts
|
Auto filled with the Compute you added in Server and Roles. If
you select All in this section NFV_HOSTS: "ALL" will be added to the Blueprint
or else you can select particular computes as well for eg: NFV_HOSTS:
"compute-server-1, compute-server-2"
|
Tenant VLAN Ranges
|
Allowed with VTS/VLAN VPP/VLAN, OVS/VLAN, ACI/VLAN
|
Enable Jumbo Frames
|
Check Box default is false.
|
Huge page size Note : . This is available only when Compute
node is present in NFV host
|
The following are the drop-downs:
|
For
Tenant Network Type Linux Bridge everything will remain the same but
Tenant VLAN Ranges will be removed.
|
CEPH
|
Ceph
has two pre-populated fields
|
GLANCE
|
By
default populated for
CEPH Dedicated with Store Backend value as
CEPH.
|
CINDER
|
By
default Populated for
CEPH Dedicated with Volume Driver value as
CEPH.
|
HA Proxy
|
Enter the Mandatory fields:
External VIP Address
|
Enter IP Address of External VIP.
|
External VIP Address IPv6
|
Enter IP v6 Address of External VIP .
|
Virtual Router ID
|
Enter the Router ID for HA.
|
Internal VIP Address
|
Enter IP Address of Internal VIP.
|
Internal VIP Address
IPv6
|
Enter IP v6 Address for Internal VIP.
|
|
Keystone
|
Admin Username
|
admin
|
Admin Tenant Name
|
admin
|
|
LDAP
|
This is available only when Keystone v3 and LDAP both are enabled under
Optional Features and Services in Blueprint Initial Setup.
Domain Name field
|
Enter name for Domain name.
|
Object Class for Users field
|
Enter a string as input.
|
Object Class for Groups
|
Enter a string.
|
Domain Name Tree for
Users
|
Enter a string.
|
Domain Name Tree for Groups field
|
Enter a string.
|
Suffix for Domain Name field
|
Enter a string.
|
URL field
|
Enter a URL with ending port number.
|
Domain Name for Bind User field
|
Enter a string.
|
Password field
|
Enter Password as string format.
|
User Filter
|
Enter filter name as string.
|
User ID
Attribute
|
Enter a string.
|
User Name
Attribute
|
Enter a string.
|
User Mail
Attribute
|
Enter a string.
|
Group Name
Attribute
|
Enter a string.
|
|
VMTP optional section will only be visible once VMTP is
selected from Blueprint Initial Setup.
Note
|
For VTS, Provider network is only supported
|
|
Check one of the check boxes to specify a VMTP network:
-
Provider Network
-
External Network
For
the
Provider Network complete the following:
Network
Name field
|
Enter the name for the external network.
|
IP
Start field
|
Enter the starting floating IPv4 address.
|
IP
End field
|
Enter the ending floating IPv4 address.
|
Gateway field
|
Enter the IPv4 address for the Gateway.
|
DNS
Server field
|
Enter the DNS server IPv4 address.
|
Segmentation ID field
|
Enter the segmentation ID.
|
Subnet
|
Enter the Subnet for Provider Network.
|
For
External Network fill in the following details:
Network
Name field
|
Enter the name for the external network.
|
Network
IP Start field
|
Enter the starting floating IPv4 address.
|
Network
IP End field
|
Enter the ending floating IPv4 address.
|
Network
Gateway field
|
Enter the IPv4 address for the Gateway.
|
DNS
Server
field
|
Enter the DNS server IPv4 address.
|
Subnet
|
Enter the Subnet for External Network.
|
|
TLS This optional section will only be visible once TLS is
selected from Blueprint Initial Setup Page.
|
TLS has two options:
|
SwiftStack optional section will be visible once SwiftStack
is selected from
Blueprint Initial Setup Page. SwiftStack is only
supported with KeyStonev2 . If you select Keystonev3, swiftstack will not be
available for configuration.
|
Following are the options that needs to be filled for SwiftStack:
Cluster End Point
|
IP address of PAC (proxy-account-container) endpoint.
|
Admin User
|
Admin user for swift to authenticate in keystone.
|
Admin Tenant
|
The service tenant corresponding to the Account-Container used
by Swiftstack.
|
Reseller Prefix
|
Reseller_prefix as configured for Keysone Auth,AuthToken
support in Swiftstack E.g KEY_
|
Admin Password
|
swiftstack_admin_password
|
Protocol
|
http or https. Protocol that swiftstack is running on top
|
|
Note
|
When
tenant type ACI/VLAN is selected then ACI INFO tab is available in blueprint
setup.
|
Note
|
When
ACI/VLAN is selected then Tor switch from initial setup is mandatory.
|
Name
|
Description
|
APIC Hosts
field
|
Enter host input. Example: <ip1|host1>:[port] . max of 3, min of 1, not
2;
|
apic_username
field
|
Enter a string format.
|
apic_password
filed
|
Enter Password.
|
apic_system_id
field
|
Enter input as string. Max length 8.
|
apic_resource_prefix
field
|
Enter string max length 6.
|
apic_tep_address_ pool field
|
Allowed only 10.0.0.0/16
|
multiclass_address_pool
field
|
Allowed only 225.0.0.0/15
|
apic_pod_id
field
|
Enter integer(1- 65535)
|
apic_installer_tenant field
|
Enter String, max length 32
|
apic_installer_vrf field
|
Enter String, max length 32
|
api_l3out_network field
|
Enter String, max length 32
|
Note
|
When
Tenant Type is VTS/VLAN then VTS tab is available in blueprint setup.
|
Name
|
Description
|
VTS Day0 (checkbox)
|
True or false default is false.
|
VTS User name
|
Enter as string does not contain special characters.
|
VTS Password
|
Enter password
|
VTS NCS IP
|
Enter IP Address format.
|
VTC SSH Username
|
Enter a string
|
VTC SHH
Password
|
Enter password
|
Note
|
If vts
day0 is enabled then SSH username and SSH password is mandatory.
If
SSH_username is input present then SSH password is mandatory vice-versa
|
Under the
openstack setup tab, the
Vim_admins tab will only be
visible once Vim_admins is selected from the
Optional Features & Services
under the
Blueprint InitialSetup tab.
|
Following are the options that needs to be filled for
Vim Admins:
-
Username - Text Field
- Password
- Password field. Admin hash password should
always start with $6
|
|
Step 13
| If
Syslog
Export or
NFVBENCH
is selected in
Blueprint Initial Setup Page then,
Services
Setup page will be enabled for User to view. Following are the options
under Services Setup Tab:
Name
|
Description
|
Syslog Export
|
Following are the options for Syslog Settings:
Remote Host
|
Enter Syslog IP Address.
|
Protocol
|
Only UDP is supported.
|
Facility
|
Defaults to local5.
|
Severity
|
Defaults to debug.
|
Clients
|
Defaults to ELK
|
Port
|
Defaults to 514 but can be modified by the
User.
|
|
NFVBENCH
|
Enable checkbox which by default is
false.
Add ToR info connected to switch:
-
Select a TOR Switch. Switch- (switch name)
-
Enter the port number. For Example: eth1/5 . VTEP
VLANS (mandatory and needed only for VTS/VXLAN,): Enter 2 different VLANs for
VLAN1 and VLAN2.
-
NIC Ports: INT1 & INT2 Optional input, enter the
2 port numbers of the 4-port 10G Intel NIC at the management node used for
NFVBench.
|
|
Step 14
| Click
Offline validation button to initiate an offline
validation of the Blueprint.
|
Step 15
| Once the
Offline
validation is successful,
Save
option will be enabled for you which when clicked would redirect you to the
Blueprint Management Page.
|