The diagram below illustrates the default network configuration of Cisco Enterprise NFVIS with the Cisco ENCS.

• LAN ports—Eight physical Gigabit Ethernet ports for inbound and outbound traffic.

• WAN port—You can use one of the dual media Ethernet ports for DHCP connection.

• Bridges—They form a Layer 2 domain between virtual network interface controllers (vNICs) of VMs. A vNIC is used by a virtual machine to provide virtual network interfaces by defining a range of MAC addresses. The default management IP address (192.168.1.1) for the NFVIS host is configured on the management port. Multiple VMs can use the same LAN port for local connectivity.

• Network—It is a segment Layer 2 bridge domain where only the specific VLAN traffic is allowed.

Note	The following networks and bridges are automatically configured. You can configure more as required. A LAN network (lan-net) and a LAN bridge (lan-br) A WAN network (wan-net) and a WAN bridge (wan-br)

The default networks and bridges cannot be deleted.

Configuring the networks in Cisco Enterprise NFVIS allows inbound and outbound traffic and VMs to be service chained. The following diagram illustrates the default network configuration:

The following networks and bridges are created by default, and cannot be deleted. You can configure more as required.

• A LAN network (lan-net) and a LAN bridge (lan-br)—The default static management IP address (192.168.1.1) for the NFVIS host is configured on the LAN bridge. All other ports for inbound and outbound traffic are associated with the LAN bridge. Any LAN port can be used to access the default static IP address. By default, the hostname is set to "nfvis".

• A WAN network (wan-net) and a WAN bridge (wan-br)—This is created with the "eth0" port, and is configured to enable the DHCP connection.

By default, the first port on the device is associated with the WAN bridge. All the other ports on the device are associated with the LAN bridge.

For more details on the initial setup, see the Installing the Server chapter in the Cisco UCS C220 M4 Server Installation and Service Guide.

The following networks and bridges are created by default, and cannot be deleted. You can configure more as required.

• A LAN network (lan-net) and a LAN bridge (lan-br)—The default static management IP address (192.168.1.1) for the NFVIS host is configured on the LAN bridge. All other ports for inbound and outbound traffic are associated with the LAN bridge. By default, the hostname is set to "nfvis".
• A WAN network (wan-net) and a WAN bridge (wan-br)— The physical WAN ports are on the Cisco ISR module. They are not externally available on the Cisco UCS E server. The WAN traffic comes from the ISR WAN ports, and goes through the backplane to the Cisco UCS-E server. The backplane has one internal WAN interface (GE0) to establish connection with the Cisco UCS-E server. By default, the "GE0" interface is enabled for the DHCP connection.

For more details on the initial setup, see the Getting Started Guide for Cisco UCS E-Series Servers and the Cisco UCS E-Series Network Compute Engine.

For initial login, use admin as the default user name, and Admin123# as the default password. Immediately after the initial login, the system prompts you to change the default password. You must set a strong password as per the on-screen instructions to proceed with the application. All other operations are blocked until default password is changed. API will return 401 unauthorized error if the default password is not reset.

You must follow the rules to create a strong password:

• Must contain at least one upper case and one lower case letter.

• Must contain at least one number and one special character.

• Must contain seven characters or greater. Length should be between 7 and 32 characters.

• Cannot contain whitespace and some special characters ( ! @ : ; ,).

You can change the default password in three ways:

• Using the Cisco Enterprise NFVIS portal (for details, see the Cisco Enterprise NFVIS Portal Online Help)

• Using the rbac authentication users user change-password command.

• Using PnP (for details, see the Cisco Network Plug-n-Play Support).

Note

To commit the target configuration to the active (running) configuration, use the commit command in any configuration mode in Cisco Enterprise NFVIS Release 3.5.1 and later. Changes made during a configuration session are inactive until the commit command is entered. By default, the commit operation is pseudo-atomic, meaning that all changes must succeed for the entire commit operation to succeed.

Performing Static Configuration without DHCP

If you want to disable DHCP and use static configuration, initial configuration is done by setting the WAN IP address and/or management IP address, and the default gateway..

To perform initial configuration on the system without using DHCP:

configure terminal
system settings mgmt ip address 192.168.1.2 255.255.255.0 
system settings wan ip address 209.165.201.22 255.255.255.0
system settings default-gw 209.165.201.1
commit

Note	When an interface is configured with a static IP address, DHCP is automatically disabled on that interface.

Now you can either use the management IP or WAN IP to access the portal.

configure terminal
no system settings default-gw
system settings mgmt dhcp
commit
exit
hostaction mgmt-dhcp-renew

configure terminal
no system settings default-gw
system settings wan dhcp
commit
exit
hostaction wan-dhcp-renew

system settings-native mgmt ip-info interface lan-br
system settings-native mgmt ip-info ipv4_address 192.168.1.2
system settings-native mgmt ip-info netmask 255.255.255.0
!
!
!
system settings-native mgmt dhcp disabled
system settings-native wan ip-info interface wan-br
system settings-native wan ip-info ipv4_address 209.165.201.22 
system settings-native wan ip-info netmask 255.255.255.0
!
!
!
system settings-native wan dhcp disabled
!
!
system settings-native gateway ipv4_address 209.165.201.1
system settings-native gateway interface wan-br

system settings-native mgmt ip-info interface MGMT
system settings-native mgmt ip-info ipv4_address 192.168.1.2
system settings-native mgmt ip-info netmask 255.255.255.0
!
!
!
system settings-native mgmt dhcp enabled
system settings-native wan ip-info interface wan-br
system settings-native wan ip-info ipv4_address 209.165.201.22
system settings-native wan ip-info netmask 255.255.255.0
!
!
!
system settings-native wan dhcp disabled

system settings-native mgmt ip-info interface lan-br
system settings-native mgmt ip-info ipv4_address 209.165.201.2 
system settings-native mgmt ip-info netmask 255.255.255.0
!
!
!
system settings-native mgmt dhcp disabled
system settings-native wan ip-info interface wan-br
system settings-native wan ip-info ipv4_address 209.165.201.22
system settings-native wan ip-info netmask 255.255.255.0
!
!
!
system settings-native wan dhcp enabled

Role based access enables the administrator to manage different levles of access to the system's compute, storage, database, and application services. It uses the access control concepts such as users, groups, and rules, which you can apply to individual API calls. You can also keep a log of all user activities.

For security reasons, the administrator can restrict access to the host server by enabling trusted IP connection using the management port. This feature helps you specify a single IP address or a range of IP addresses as trusted source IP address or addresses to prevent unauthorized access to the host server.

To configure the trusted IP connection:

configure terminal
system settings trusted-source 192.0.2.0/24
commit

nfvis# show system settings-native trusted-source 
system settings-native trusted-source [ 192.0.2.0/24 ]

Cisco Enterprise NFVIS supports two types of banners: system-defined and user-defined banners. You cannot edit or delete the system-defined banner, which provides copyright information about the application. Banners are displayed on the login page of the portal.

You can post messages using the Message of the Day option. The message is displayed on the portal's home page when you log into the portal.

To configure your banner and message:

configure terminal
banner-motd banner "This is a banner" motd "This is the message of the day"
commit

Note	Currently, you can create banners and messages in English only. You can view the system-defined banner using the show banner-motd command. This command does not display the user-defined banner or message.

You can configure the Cisco Enterprise NFVIS system time manually or synchronise with an external time server using Network Time Protocol (NTP).

To set the system time manually:

configure terminal
system time manual_time 
2016-11-22T11:38:00
commit

Note	NTP is automatically disabled when the time clock is set manually.

To set the system time using NTP:

configure terminal
system time  ntp preferred_server 
209.165.201.20 backup_server 1.ntp.esl.cisco.com
commit

nfvis# show system time 
system time date 2016-11-24T02:48:38-00:00
system time timezone "America/Chicago (CST, -0600)"
system time ntp-status synchronised
system time preferred-server 171.68.38.65
system time backup-server ntp.esl.cisco.com
system time ntp current-server 171.68.38.65
system time ntp stratum-level "stratum 2"
system time ntp time-correct-within "18 ms"
system time ntp polling-server-every "512 s"

The Cisco Enterprise NFVIS portal access is enabled by default. You can disable the access if required.

To disable the portal access:

configure terminal
system portal access disabled 
commit

Note	You can enable the portal access using the enable keyword with the system portal access command.

nfvis# show system portal status
system portal status "access disabled"

You can set system logs for troubleshooting purpose. There are two log types and five log levels. The two log types are configuration and operational.

The following table explains the log levels:

Note	The INFO and WARNING log levels are set by default respectively for the configuration and operational log types. You can change them as required. However, the change to the log level is not persisted across a reboot. After a reboot, the default log levels are used.

You can configure system logs using the system set-log command in global configuration or privileged EXEC mode:

system set-log level error logtype configuration

nfvis# show system logging-level
system logging-level configuration error