B Nfvis Command Ref
B Nfvis Command Ref
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
© 2017–2023 Cisco Systems, Inc. All rights reserved.
CONTENTS
networks network 48
bridge 51
bridges bridge 52
show running-config bridges 53
show system networks 54
show system packages 55
ping 56
ping-ipv6 57
traceroute 58
vm_lifecycle flavors 60
vm_lifecycle images 61
vm_lifecycle networks 80
hostaction mgmt-dhcp-renew 82
hostaction wan-dhcp-renew 83
hostaction reboot 84
hostaction shutdown 85
show resources cpu-info allocation 86
show resources cpu-info cpus 87
show resources cpu-info vnfs 88
show resources precheck vnf 89
show system-monitoring host cpu 90
show system-monitoring host disk 92
show system-monitoring host memory 94
show system-monitoring host port 96
show system-monitoring vnf vcpu 98
show system-monitoring vnf disk 99
show system-monitoring vnf memory 101
show system-monitoring vnf port 103
source 138
destination 139
show system monitor session 140
monitor session 141
factory-default-reset 152
banner-motd
To configure a banner and message of the day (MOTD), use the banner-motd command in global configuration
mode. To remove the banner or MOTD, use the no form of the command.
Usage Guidelines To verify the configuration, use the show running-config banner-motd command. To delete both the banner
and the MOTD configuration, use the no banner-motd command without any keywords and arguments.
Example
The following example shows how to configure both the banner and the MOTD:
nfvis(config)# banner-motd banner "This is a new banner" motd "This is a new motd"
nfvis(config)# commit
nfvis(config)# end
show banner-motd
To display the system-defined banner, use the show banner-motd command in privileged EXEC mode.
Usage Guidelines This command displays only the system-defined banner. It does not display the user-defined banner or message
of the day.
Example
The following is a sample output of the show banner-motd command:
Example
The following is a sample output of the show running-config banner-motd command:
Example
The following command shows the number of PNICs:
show nic
Use the command show nic to view more details on the NICs supported on Cisco UCS C-Series M6 rack
servers.
show nic
Example
The following command shows the details of NICs:
---------------------------------------------------------------------------------------------------------------
1 Intel i350 Quad Port 1Gb Adapter 8086 1521 NA NA ['GE1-0', 'GE1-1',
'GE1-2', 'GE1-3']
2 Cisco-MLNX MCX623106AS-CDAT 15b3 101d NA NA []
4 Intel X710-DA4 Quad Port 10Gb SFP+ 8086 1572 NA NA ['GE4-0', 'GE4-1',
'GE4-2', 'GE4-3']
converged NIC
show license
Use the command show license to see more details on the Cisco smart license.
show license
Example
The following command shows the details of NICs:
Action Commands
Use the following actions commands that can help you release, sync and trust Cisco NFVIS licences:
• license smart release: Use this command to send a "License Usage 0" message to CSSM. This
action prompts the CSSM to release the license entitlement associated with your Cisco UCS C M6 Rack
servers. If the device continues to operate with Cisco NFVIS after the license release, a usage report,
also known as RUM, is sent to CSSM after a predetermined time interval. This report will indicate the
actual number of license units consumed, which will then be reserved again on CSSM. Following a
license release, a notification and system logging warning is issued, urging you to cease using Cisco
NFVIS as the license has been released. You receive this notification every 8 hours during the 24 hours
after a license release. If you continue to use Cisco NFVIS beyond this 24-hour period, a RUM report
will be generated reflecting the appropriate number of license units consumed by Cisco NFVIS. This
report is sent to the Licensing server based on the set periodic interval, after which the licensing server
will reserve the correct number of license units for the device again.
• license smart sync: Report a license usage to CSSM using this action command.
• license smart trust: Initiate the establishment of trust between the device and the CSSM. This
action can prove beneficial in various scenarios, including but not limited to the following:
1. If you delete the product instance from CSSM but wish to continue with Cisco NFVIS Licensing.
2. If you transfer your licenses from one Virtual Account to another.
3. If there is an asynchrony between the licensing state on CSSM and on the device.
4. If the licensing certificates on the device reach their expiry date.
Usage Guidelines To configure DHCP either on the WAN interface or the management interface, delete the default gateway.
Example
The following command sets the default gateway:
Syntax Description threshold value Specifies the threshold value in percentage for disk space usage. Valid range is from 1 to
100. When the disk space usage reaches the specified threshold, a notification is sent.
Example
Example
The following command changes the hostname of the system to nfvis-demo:
system settings ip-receive-acl source-ip-address [service {https | icmp | netconf | scpd | snmp |
ssh}] [priority priority] [action {accept | reject | drop}]
Syntax Description source-ip-address Specifies the IPv4 IP address of the source network. When the management ACL access
is enabled, only specified source networks can access the management interface. When
no ACL rule is defined, all types of traffic is allowed. If the source network is specified
as 0.0.0.0/0, the configuration is applicable to all source networks.
service Specifies the service type for the management ACL access. Valid values are:
• https: Includes port 80, port 443 and all ports to access the service console.
• icmp: Provides ability to ping the host.
• netconf: Includes port 2022. This port is required for communication between nodes
of a cluster.
• scpd: Provides ability to run the scp command from an external system.
Note To use the port 22222, you must run the system settings ip-receive-acl
command with scpd service. Starting with release 3.7.1, the port 22222
is closed by default.
You can specify one, more than one, or all service types in this parameter. To specify
multiple service types, enter the values within the square brackets []; for example, service
[ snmp https ]. If you do not specify any specific service, the configuration is applicable
to all services.
priority priority Specifies the priority for the ACL rule. Each ACL rule must have a unique priority value.
Valid range is from 0 to 65,535. ACL rule with priority 0 has the highest priority. Whenever
an ACL rule with priority 0 is matched, Cisco Enterprise NFVIS performs the action
associated with this ACL rule and does not look up any lower priority ACL rules.
action Specifies the action for the packets received from a source network. Valid values are:
• accept: Accept the packets.
• reject: Reject the packets and return the error to the source network.
• drop: Drop packets immediately and do not send any information to the source
network.
Example
The following example opens port 22222 for all IPs.
Example
The following example opens port 22222 for a specific IP.
Example
The following example configures the SSH service for a specific IP.
Example
Command Default By default, the management interface is assigned the static IP address 192.168.1.1.
Usage Guidelines You can configure DHCP either on the WAN interface or the management interface; you cannot configure
DHCP on both the interfaces simultaneously.
Before configuring the management interface with DHCP, delete the default gateway. After you configure
DHCP on the management interface, either reboot the system or enter the command hostaction
mgmt-dhcp-renew to renew the DHCP IP address.
Example
The following command sets the IP address and netmask for the management interface:
Usage Guidelines You can configure DHCP either on the WAN interface or the management interface; you cannot configure
DHCP on both the interfaces simultaneously.
Before configuring the WAN interface with DHCP, delete the default gateway. After you configure DHCP
on the WAN interface, either reboot the system or enter the command hostaction wan-dhcp-renew to renew
the DHCP IP address.
Example
The following command sets the IP address and netmask for the WAN interface:
system storage
To configure the system storage, use the system storage command in global configuration mode. Use the no
form of the command to delete the storage configuration.
storagetype storagetype Specifies the storage type. Valid values are internal, iscsi,
nfs, and not_enabled.
server_ip server_ip Specifies the IP address of the remote storage device server.
Example
nfvis(config-storage-nfs_storage)# commit
Example
show system settings-native [dns | domain | gateway | hostname | mgmt | wan vlan]
Examples
The following is a sample output of the show system settings-native command without any keywords:
The following is a sample output of the show system settings-native command to verify the VLAN
configuration details. If no VLAN is configured, the default setting (untagged) is displayed as shown
below:
Example
Example
Example
nfvis# show system file-handles
2848 0 780124
Example
Example
nfvis# show system services service auditd.service
UNIT LOAD ACTIVE SUB DESCRIPTION
------------------------------------------------------
auditd.service loaded active running Security
Command Default Show the status of all the entities in the system.
Example
nfvis# show system status diagnostics wan-br
NAME STATUS TYPE
--------------------------------
wan-br OK default-bridge
show platform-detail
To display the hardware information, port details, switch details and software packages related to the platform,
use the show platform-detail command in privileged EXEC mode.
show version
To display the name, version number and build date of the NFVIS software that is currently running in the
system, use the show version command in privileged EXEC mode
Command Default Displays the name, version number, and build date of Cisco Enterprise NFVIS.
Example
The following is the sample output from the show versioncommand:
nfvis# show version
version name "Enterprise NFV Infrastructure Software"
version version 3.5.1-FC4
show free-memory
To display information about free memory, use the show free-memory command in privileged EXEC mode.
show free-memory
Example
nfvis# show free-memory
total used free shared buff/cache available
Mem: 128660 2761 120879 15 5020 125222
Swap: 16383 0 16383
show certificate
To show all certificates and related files in the system, use the show certificate command in privileged EXEC
mode.
show certificate
Example
nfvis# show certificates
File Name Type Last Modified Size
ca-bundle.legacy.crt ca-trust Wed Mar 15 12:08:40 2017 59653
ca-bundle.trust.crt ca-trust Fri Oct 6 10:39:53 2017 346654
email-ca-bundle.pem ca-trust Fri Oct 6 10:39:53 2017 208874
tls-ca-bundle.pem ca-trust Fri Oct 6 10:39:53 2017 262042
objsign-ca-bundle.pem ca-trust Fri Oct 6 10:39:53 2017 208976
server.key nginx Fri Oct 6 11:06:12 2017 1679
server.crt nginx Fri Oct 6 11:06:12 2017 964
server.key self-signed Fri Oct 6 11:06:12 2017 1679
server.csr self-signed Fri Oct 6 11:06:12 2017 887
server.crt self-signed Fri Oct 6 11:06:12 2017 964
ca-bundle.crt tls Fri Oct 6 10:39:53 2017 262042
ca-bundle.trust.crt tls Fri Oct 6 10:39:53 2017 346654
cert.pem tls Fri Oct 6 10:39:53 2017 262042
show file
To show the contents of a file, use the show file command in privileged EXEC mode.
Syntax Description filepath_name Specifies the location and name of the file.
Example
nfvis# show file /data/intdatastore/logs/2017-10/confd_devel.log-20171008
<DEBUG> 7-Oct-2017::19:30:08.444 nfvis confd[3626]: devel-cdb connect from python
<DEBUG> 7-Oct-2017::19:30:08.444 nfvis confd[3626]: devel-cdb client python has pid 3724/174
<DEBUG> 7-Oct-2017::19:30:08.444 nfvis confd[3626]: devel-cdb new session on operational
for python
...
show cores
To show crash core files, run the show cores command in privileged EXEC mode.
show cores
show nfv_mode
To show the NFV mode, use the show nfv_mode command in privileged EXEC mode.
show nfv_mode
pnp action
To start, stop, and restart a PnP action,use the pnp action command in global configuration mode.
Example
The following example shows how to use the pnp action command:
pnp automatic
To enable or disable automatic mode for PnP discovery process, use the pnp automatic command in global
configuration mode. Use the no form of this command to put the automatic PnP discovery method in default
mode (enabled) with a retry timeout of 60 seconds.
pnp automatic {cco | cco-ipv6 | dhcp | dhcp-ipv6 | dns-ipv6 | dns | timeout value} {enable |
disable}
no pnp automatic
Syntax Description cco Specifies the use of the Cisco Cloud Device Redirect tool available in the Cisco Software
Central for automatic PnP discovery.
cco-ipv6 Specifies the use of the Cisco Cloud Device Redirect tool available in the Cisco Software
Central for automatic PnP discovery for IPv6.
dhcp Specifies the use of a IPv4 DHCP server for automatic PnP discovery.
dhcp-ipv6 Specifies the use of a IPv6 DHCP server for automatic PnP discovery.
dns Specifies the use of a IPv4 DNS server for automatic PnP discovery.
dns-ipv6 Specifies the use of a IPv6 DNS server for automatic PnP discovery.
timeout value Specifies the timeout value in seconds. The default value is 60.
Command Default The automatic discovery mode for DHCP, DNS, and CCO is enabled.
Usage Guidelines You can enable or disable the options as required. For example, you can enable all options or keep one enabled,
and the rest disabled. You cannot disable both static and automatic PnP discovery modes at the same time.
You must restart PnP action every time you make changes to the PnP discovery configuration. You can do
this using the pnp action command restart command.
Example
The following example shows how to enable automatic mode for PnP discovery process:
pnp static
To specify a static IP address for the Cisco Network PnP server, use the pnp static command in global
configuration mode. To remove the PnP static IP address configuration , use the no form of the command
with the static keyword. To clear any PnP static and automatic configurations, and put all the automatic
configurations in default mode, which is enabled, with a retry timeout of 60 seconds, use the no pnp command.
port number (Optional) Specifies the port number. Valid range is from 0 to 65535.
Usage Guidelines You cannot disable both static and automatic PnP discovery modes at the same time. You must restart PnP
action every time you make changes to the PnP discovery configuration. You can do this using the pnp action
command restart.
Example
The following example shows how to configure a static IP address for the Cisco Network PnP server:
show pnp
To verify the configuration of PnP discovery methods, use the show pnp command in privileged EXEC mode.
show pnp
Example
The following sample output of the show pnp command shows that the static discovery mode is
enabled, and the automatic discovery mode is disabled.
Example
The following is the sample output from the show resources cpu-info allocation command:
Command Default Display information on the VMs running in all the physical CPUs.
Example
The following is a sample output from the show resources cpu-info cpus cpu 7 command:
networks network
To add a bridge to a network, use the networks network command, in global configuration mode. To remove
the bridge from a network, use the no form of the command.
networks network networkname { bridge bridgename | sriov true | trunk true | trunk false |
vlan vlannumber | vlan-range range }
no networks network networkname
trunk false Removes the network from trunk mode and puts it in access mode.
vlan vlannumber Specifies the VLAN number to be associated with the network.
Example
The following example shows how to add a bridge to a network:
The following example shows how to add a network into trunk mode:
The following example shows how to remove a network from trunk mode:
nfvis(config)# networks network eth2-1-net bridge eth2-1-br vlan-range [ 100-103 200 205-207
]
nfvis(config-network-eth2-1-net)# commit
Note • A SRIOV network in trunk mode does not support VLAN tagging.
bridge
To attach a SPAN session to a bridge, use the bridge command in session configuration mode. To remove
the SPAN session association, use the no form of the command.
Usage Guidelines For VLAN mirroring, the bridge must be configured. Configuration is rejected if a SPAN session is not applied
to a bridge. The bridge configuration is optional if the source or destination interface is configured for the
SPAN session.
Example
The following example shows how to attach a SPAN session to a bridge:
bridges bridge
To add a port or port channel to a bridge, use the bridges bridge command. To remove a port or port channel
from a bridge, use the no form of the command.
Example
nfvis# config
nfvis(config)# bridges bridge test-br port pc
nfvis(config-bridge-test-br)# commit
nfvis(config-bridge-test-br) # end
Example
Example
Example
ping
To diagnose basic network connectivity to an IPv4 host, use the ping command in privileged EXEC mode.
ping {host-ip-address host-name} [count count] [pktsize pktsize] [interval interval] [ttl ttl]
Example
ping-ipv6
To diagnose basic network connectivity to an IPv6 host, use the ping-ipv6 command in privileged EXEC
mode.
ping-ipv6 {host-ip-address host-name} [count count] [pktsize pktsize] [interval interval] [ttl
ttl]
Example
traceroute
To discover the routes that packets take when traveling to a destination, use the traceroute command in
privileged EXEC mode.
Example
vm_lifecycle flavors
To create a flavor, use the vm_lifecycle flavors command in global configuration mode. To remove a flavor,
use the no form of the command.
Usage Guidelines When deploying or modifying a VM, you can specify a flavor in active state.
To verify that the VM flavor is created, use the following commands in privileged EXEC mode:
show running-config vm_lifecycle flavors [flavor flavor-name]
show vm_lifecycle opdata flavors [flavor flavor-name]
Example
vm_lifecycle images
To register a VM image, use the vm_lifecycle images command in global configuration mode. To remove
the VM registration, use the no form of the command.
vm_lifecycle images image image-name src file-path [properties property property-name value
value]
no vm_lifecycle images image image-name
property property-name Specifies the name of the property to replace the corresponding
value inside the tar.gz while registering the image. For detailed
information about all supported properties, see the Usage
Guidelines section.
value value Specifies the property value to be replaced inside the tar.gz.
Usage Guidelines A VM image registration is done only once per VM image. You can perform multiple VM deployments using
the registered VM image.
The following table provides information about the resources supported or required for the VM operation.
Property Description
Property Description
root_file_disk_bus Specifies the root image disk bus. Valid values are
virtio, scsi, and ide.
disk_x_file_disk_bus Specifies the disk bus for additional disk image. The
VM package supports up to 10 disks to be bundled
into the package such as disk_1_file_disk_bus,
disk_2_file_disk_bus, and disk_10_file_disk_bus.
Valid values are virtio, scsi, and ide.
root_image_disk_format Specifies the root image disk format. Valid values are
qcow2 and raw.
console_type_serial Enables the serial console. Valid values are true and
false.
Property Description
Property Description
To verify that the VM image is registered, use the following commands in privileged EXEC mode:
show running-config vm_lifecycle images [image image-name]
show vm_lifecycle opdata images [image image-name]
Example
The following example shows how to register a VM image:
bootup_time value Specifies the VM bootup time. Bootup time can vary depending on the
VM image that you have selected. For example, bootup time is 600 seconds
for a Cisco ISRv image. If no monitoring is required for the VM, set the
bootup time as -1.
Note A monitored VM must have a valid bootup time. The
corresponding KPI fields are mandatory for the monitored
VM. For an unmonitored VM, the KPI fields are optional.
image image-name Specifies the image name that was used for registering. The image must
be in ACTIVE state.
flavor flavor-name Specifies the flavor name. The flavor must be in ACTIVE state.
network network-name Specifies the name of the network attached to the NIC ID. All networks
(such as LAN and WAN), except the internal management network, require
an IP address.
The vNIC attachment to the internal management network is required only
for VMs that require monitoring. If this interface is used for monitoring,
network must be set to int-mgmt-net.
model model-name Specifies the model name. Possible values are: e1000, i82551, i82557b,
i82559er, ne2k_pci, pcnet, rtl8139, and virtio.
The default value is virtio. This is an optional parameter.
port port-type Specifies the port type. Possible values are SSH, HTTPS, TCP, and Telnet.
vnf_port port-num Specifies the port number corresponding to the specified protocol.
external_port_range Specifies the unique port number to specify the start and end range for
port-num-start port-num-end ports.
host placement-host-name Specifies the name of the placement datastore. For NFS, valid value is
nfs-storage. For Cisco ENCS external datastore, allowed values are
datastore2, datastore3. The default value is datastore1.
rules admin_rules Configures monitoring policy rule. These are the rules that an administrator
specifies when the service is registered.
This parameter is mandatory if the VM is a monitored VM, that is, its
bootup time is non-zero.
action actions Specifies the list of actions which this policy triggers.
• ALWAYS log—Whether the event is pingable or not, the details are
always logged.
• FALSE recover autohealing—The action identified by this keyword
is triggered, and the VM is recovered without the administrator's
intervention.
• TRUE servicebooted.sh—The action identified by this keyword in
the dynamic mapping file is triggered when the VM moves from a
non-pingable to a pingable state.
You can specify actions in the following format: action [ "ALWAYS log"
"FALSE recover autohealing" "TRUE servicebooted.sh" ].
metric_cond value Specifies the direction of the metric value change for the KPI. Valid values
are the following:
• GE and GT: An alarm is sent when the metric value increases from
a lower position to equal or exceed the specified value.
• LE and LT: An alarm is sent when the metric value decreases from
a higher position to equal or go down the specified value.
metric_type type Specifies the metric type. Valid metric types are INT8, UINT8, INT16,
UINT16, INT32, UINT32, FLOAT, DOUBLE, and STRING.
metric_collector Configures the metrics that needs to be monitored and at what frequency
should the monitoring happen.
type type Specifies the type to be monitored; for example, ICMPPing. If the image
boot-up time is provided, monitoring must be set to ICMPPing.
nicid vnic-id Specifies the card ID of the interface through which this VM is monitored.
It should be the ID specified for one of interfaces in the payload.
polling_unit unit Specifies the ICMP ping frequency unit. Possible values are minutes and
seconds.
continuous_alarm value Specifies that the continuous events need to be generated. Valid values are
true and false.
Example
The following example shows how to deploy a VM:
nfvis(config)# vm_lifecycle tenants tenant admin deployments deployment dep1 vm_group router1
bootup_time 600 image
isrv flavor ISRv-small
nfvis(config-vm_group-router1)# interfaces interface 0 network int-mgmt-net port_forwarding
port ssh protocol tcp
vnf_port 22 external_port_range 20024 20024
nfvis(config-port-ssh)# exit
nfvis(config-interface-0)# exit
nfvis(config-vm_group-router1)# interfaces interface 1 model virtio network lan-net
nfvis(config-interface-1)# exit
nfvis(config-vm_group-router1)# rules admin_rules rule VM_ALIVE action [ "ALWAYS log" "FALSE
recover autohealing"
"TRUE servicebooted.sh" ]
nfvis(config-rule-VM_ALIVE)# exit
nfvis(config-vm_group-router1)# kpi_data kpi VM_ALIVE metric_value 1 metric_cond GT
metric_type UINT32 metric_collector
type ICMPPing nicid 0 poll_frequency 3 polling_unit seconds continuous_alarm false
nfvis(config-kpi-VM_ALIVE)# exit
nfvis(config-vm_group-router1)# scaling min_active 1 max_active 1
nfvis(config-vm_group-router1)# placement zone_host host datastore1
nfvis(config-placement-zone_host)# exit
nfvis(config-vm_group-router1)# commit
vmAction
To specify a VM action, use the vmAction command in privileged EXEC mode.
Syntax Description action Specify the action. Valid values are DISABLE_MONITOR, ENABLE_MONITOR, REBOOT,
RECOVER, START, and STOP.
name Specify the VM name. This VM name is the internally-generated name. Use the show vm_lifecycle
opdata tenants tenant admin deployments command to get the VM NAME per deployment.
Example
nfvis# vmAction actionType STOP vmName
1513193832_ROUTER_0_15c32f49-0d95-4b7a-8a84-ba7de3c1d6f9
vmBackupAction
To back up a VM, use the vmBackupAction command in privileged EXEC mode.
Example
nfvis# vmBackupAction vmName isrvtest1 actionType EXPORT
vmConsole
To enable VM serieal console, use the vmConsole command in privileged EXEC mode.
vmConsole vm-domain-name
Usage Guidelines If the VM does not support a serial console, the vmConsole command returns this message, "Serial console
not available".
To exit the VM console you must enter ctrl+] and then enter send escape.
Example
The following example shows how a VM is connected to its domain using the serial console:
vncconsole start
To get information about the VNC console, use the vncconsole start command in privileged EXEC mode.
Example
show vm_lifecycle opdata [{flavors flavor flavor-name | images image image-name | networks
network network-name | stats | status | system-config | tenants tenant tenant-name
[deployments [vm_group vm-group-name]]}]
vm_group vm-group-name Displays the deployment status for the specified VM group.
Command Default Displays the overall operational status of the VM life cycle.
---------------------------------------------------------------------------------------------------------------
int-mgmt-net-subnet 004db62f-ae89-43f7-bc24-dfa2d9caa3eb 192.0.2.0/24 192.0.2.1 false
false 4
nfvis# show vm_lifecycle opdata tenants tenant admin deployments vm_group isrv1
deployments isrv1 - -
vm_group isrv1
vm_instance 57b9a63a-9c9d-4765-baa6-2d7086ad3262
name SystemAdminTena_isrv1_0_72619ffd-df8e-4c32-b24a-3d7b03a31303
host_id NFVIS
hostname nfvis
interfaces interface 0
model virtio
port_id vnic1
network int-mgmt-net
subnet N/A
ip_address 192.0.2.10
mac_address 52:54:00:f1:5f:d9
netmask 255.255.255.0
gateway 192.0.2.1
interfaces interface 1
model virtio
port_id vnic7
network wan-net
subnet N/A
mac_address 52:54:00:2b:41:e9
interfaces interface 2
model virtio
port_id vnic8
network lan-net
subnet N/A
mac_address 52:54:00:7a:27:25
netmask 255.255.255.0
gateway 198.51.100.1
Example
Example
vm_lifecycle networks
To create a new subnet, use the vm_lifecycle networks command in global configuration mode. To delete
an existing subnet, use the no form of this command.
Syntax Description network int-mgmt-net Specifies the network name. The network name must be set to int-mgmt-net.
subnet int-mgmt-net-subnet Specifies the management subnet name. The subnet name must be set to
int-mgmt-net-subnet.
dhcp Configures DHCP. The DHCP value must be set to false. The default value
is true.
Usage Guidelines The management subnet should be changed before deploying any VMs. You must first delete the subnet and
then add the new subnet.
The chosen subnet should have at least four IP addresses for network, broadcast, gateway and VM. If the
monitoring IP is passed in the deployment payload, it should be within the IP addresses available in the address
pool. Otherwise, the Cisco Enterprise NFVIS assigns the next available IP from the address pool.
Example
hostaction mgmt-dhcp-renew
To renew the DHCP IP address on the management interface, use the hostaction mgmt-dhcp-renew command
in privileged EXEC mode.
hostaction mgmt-dhcp-renew
Example
The following command renews the DHCP IP address on the management interface:
hostaction wan-dhcp-renew
To renew the DHCP IP address on the WAN interface, use the hostaction wan-dhcp-renew command in
privileged EXEC mode.
hostaction wan-dhcp-renew
Example
The following command renews the DHCP IP address on the WAN interface:
hostaction reboot
To reboot the Cisco NFVIS host, use the hostaction reboot command in privileged EXEC mode.
hostaction reboot
Usage Guidelines When you run this command, the connectivity is lost and the Cisco NFVIS host is rebooted. After the reboot
is complete, you can again connect to the Cisco NFVIS host.
Example
hostaction shutdown
To shut down the Cisco NFVIS host, use the hostaction shutdown command in privileged EXEC mode.
hostaction shutdown
Usage Guidelines After shutting down the Cisco NFVIS host, if you want to power it on again, use CIMC.
Example
Example
The following is the sample output from the show resources cpu-info allocation command:
Command Default Display information on the VMs running in all the physical CPUs.
Example
The following is a sample output from the show resources cpu-info cpus cpu 7 command:
Command Default Display information on the CPUs and VCPUs that are allocated to each of the VMs.
Example
The following is the sample output from the show resources cpu-info vnfs vnf
1472148662.ROUTER2 command:
0 2 10
Note In the example, when low latency is true, no VCPUs are assigned to this VM; instead CPUs 3, 11
and 10 are entirely reserved for this VM.
Syntax Description vm-name The name of the VM. For updating an existing VM, the VM name must be
deployment-name.vm-group-name
low-latency This can be either true or false. If true, the VM needs dedicated CPUs.
The following is a sample output from the show resources precheck vnf newvnf csr1kv-medium
true command:
The table below describes the significant fields shown in the display:
Field Description
show system-monitoring host cpu [{stats | table} [cpu-usage duration [state state]]]
cpu-usage duration Specifies the statistics duration. Valid values are 1min, 5min, 15min, 30min, 1h, 6h,
1d, 5d, and 30d. Default duration is 5min.
state state Specifies the CPU state. Valid states are non-idle, interrupt, nice, system, user, and
wait . Default state is non-idle.
This parameter is available only with stats parameter.
Example
-------------------------------------------------------------
5min 0 non-idle 1.25 3.38 1.93
interrupt 0.0 0.0 0.0
nice 0.0 0.0 0.0
softirq 0.0 0.09 0.0
steal 0.0 0.0 0.0
system 0.43 1.68 0.78
user 0.34 0.86 0.6
wait 0.0 1.86 0.58
1 non-idle 0.11 0.65 0.34
interrupt 0.0 0.0 0.0
nice 0.0 0.0 0.0
softirq 0.0 0.01 0.0
steal 0.0 0.0 0.0
system 0.01 0.28 0.14
user 0.02 0.37 0.19
wait 0.0 0.0 0.0
duration Specifies the statistics duration. Valid values are 1min, 5min, 15min, 30min, 1h,
6h, 1d, 5d, and 30d. Default duration is 5min.
collect-start-date-time Displays the statistics by the start date and time of data collection.
disk Displays the disk statistics by disk name. This parameter is available only with
disk-operations parameter.
mount-point Displays the disk statistics by mount name. This parameter is available only with
disk-space parameter.
Example
time-per-write-ms []
pending-ops [0.0, 0.0, 0.0]
...
mem-usage duration Specifies the statistics duration. Valid values are 1min, 5min, 15min, 30min, 1h, 6h,
1d, 5d, and 30d. Default duration is 5min.
Example
port-usage duration Specifies the statistics duration. Valid values are 1min, 5min, 15min, 30min, 1h, 6h,
1d, 5d, and 30d. Default duration is 5min.
Examples
----------------------------------------------------------------------------------------------------------
vcpu-usage duration Specifies the statistics duration. Valid values are 1min, 5min, 15min, 30min, 1h, 6h,
1d, 5d, and 30d. Default duration is 5min.
Example
disk-operations duration Specifies the statistics duration. Valid values are 1min, 5min, 15min, 30min,
1h, 6h, 1d, 5d, and 30d. Default duration is 5min.
Example
mem-usage duration Specifies the statistics duration. Valid values are 1min, 5min, 15min, 30min, 1h, 6h,
1d, 5d, and 30d. Default duration is 5min.
Example
4147.96, 4147.96]"
...
port-usage duration Specifies the statistics duration. Valid values are 1min, 5min, 15min, 30min, 1h, 6h,
1d, 5d, and 30d. Default duration is 5min.
Example
scp
To secure copy a file from the Cisco NFVIS to an external system or from an external system to Cisco NFVIS,
the admin user can use the scp command in privileged EXEC mode.
For detailed information about how to use this command to copy to or from supported locations, see the Usage
Guidelines section.
Syntax Description source To copy a file from an external system, specify the source in the following format:
user@remotehostip:file.
To copy a file to an external system, specify the NFVIS location and name of the file.
The external host can have an IPv4 or IPv6 address as described in the Usage Guidelines
section.
destination To copy a file to an external system, specify the the destination in the following format:
user@remotehostip:file.
To copy a file from an external system, specify the NFVIS location and name of the file.
The external host can have an IPv4 or IPv6 address as described in the Usage Guidelines
section.
Usage Guidelines Following are the guidelines for using the scp command:
• Supported Users: Only the admin user can run the scp command.
• Certain special characters are blacklisted from source and destination path, except in certain positions -
'*', '&', ';', ':', '@', '|', '..'
• Supported Locations
• The admin user can copy files to and from the intdatastore, extdatastore1,
extdatastore2, usb, and nfs locations in Cisco NFVIS. In addition, the admin user can copy
the log files from Cisco NFVIS to an external system.
Any attempt to SCP to NFVIS file system other than the mentioned list is prohibited by the command:
intdatastore - /data/intdatastore/uploads/
extdatastore1 - /mnt/extdatastore1/uploads/
extdatastore2 - /mnt/extdatastore2/uploads/
usb - /mnt-usb/
nfs - /data/mount/
logs - /data/intdatastore/logs
You can copy to and from extdatastore1, extdatastore2, usb, and nfs locations only
if they are available or mounted. The extdatastore1 and extdatastore2 locations are
available only in the Cisco ENCS 5400 Series.
• The admin user can copy the log files from the logs folder of Cisco NFVIS to an external system.
Copying files to the logs folder is not allowed. All SCP actions are logged into
/data/intdatastore/logs/nfvis_scp.log file.
• To copy to or from a USB, you must first mount the USB by using the system usb-mount mount
ACTIVE command. After the USB is mounted, use the show system file-list disk usb command
to find the exact USB name and provide the identified USB name in the scp command; for example,
scpuser@remotehostip:fileusb:usb_name/filename.
• To copy to or from NFS, you must first mount an NFS location by using the system storage
nfs_storage command. After the NFS is mounted, you must specify the name of the NFS mount in
the scp command; for example, scp user@remotehostip:filenfs: mount_name/filename.
• Supported Address Types: You can specify IPv4 or IPv6 address of an external system. The IPv6 address
of the external system must be specified within square brackets ([ ]); for example, scp user@[
remotehostip]:sourcefile destinationfile
Example
The following example copies the sample.txt file from intdatastore to an external system.
nfvis# scp intdatastore:sample.txt [email protected]:/Users/user/Desktop/sample.txt
Example
The following example copies the test.txt file from an external system to intdatastore.
nfvis# scp [email protected]:/Users/user/Desktop/test.txt intdatastore:test_file.txt
Example
The following example copies the test.txt file from an external system to USB.
nfvis# scp [email protected]:/user/Desktop/my_test.txt usb:usb1/test.txt
Example
The following example copies the sample.txt file to an NFS location.
nfvis# scp [email protected]:/user/Desktop/sample.txt nfs:nfs_test/sample.txt
Example
The following example copies the sample.txt file from an external system with IPv6 address.
nfvis# scp user@[2001:DB8:0:ABCD::1]:/user/Desktop/sample.txt intdatastore:sample.txt
Example
The following example copies the nfvis_scp.log file to an external system.
nfvis# scp logs:nfvis_scp.log [email protected]:/Users/user/Desktop/copied_nfvis_scp.log
Syntax Description file name string Specifies the file name of the VM image.
Example
The following example shows how to copy a VM image using the USB drive:
Syntax Description source Specifies the path for the file to be copied.
(Optional) checksum Specifies the SHA256 checksum for the file to be downloaded.
Example
The following example shows how to download a file to a specific location (/data/intdatastore/uploads)
on the host server, from the HTTP server:
Note Multiple files can be downloaded, either with or without checksum, at the same time.
system file-delete
To delete a file from the default location (/data/intdatastore/uploads) on the host server, use the system
file-delete command in global configuration mode.
Example
The following example shows how to delete a file from the default location on the host server:
system usb-mount
To mount the USB drive on the NFVIS server, use the system usb-mount command in global configuration
mode. To unmount, use the no form of this command.
no system usb-mount
Syntax Description mount active Mounts the USB drive on the NFVIS server.
Usage Guidelines Ensure that you have plugged the USB drive that contains the required images into the server before mounting
the USB drive.
Example
telnet
To open a telnet session to a local service on a serial port, use the telnet command in privileged EXEC mode.
telnet serial-port
Syntax Description serial-port Specifies the name of the serial port. The serial port must be enabled for the VM.
Example
Router>
Router>
Router>?
Exec commands:
access-profile Apply user-profile to interface
app-hosting Application hosting
appnav IOS Wide Area Application Services
clear Reset functions
connect Open a terminal connection
crypto Encryption related commands.
disable Turn off privileged commands
disconnect Disconnect an existing network connection
do-exec Mode-independent "do-exec" prefix support
enable Turn on privileged commands
ethernet Ethernet parameters
exit Exit from the EXEC
help Description of the interactive help system
ip IP SLA Exec Command
lat Open a lat connection
license Smart licensing Commands
lig LISP Internet Groper
lock Lock the terminal
login Log in as a particular user
logout Exit from the EXEC
mrinfo Request neighbor and version information from a multicast
--More--
Syntax Description disk Displays files from the specified disk type.
Example
nfvis# show system file-list
system file-list disk local 1
name nfvisvmpackagingtool.tar
path /data/intdatastore/uploads/vmpackagingutility
size 50K
type "VM Packaging Tool"
date-modified "2017-09-07 02:18:53"
system file-list disk local 2
name catalina.out-20171001.gz
path /data/intdatastore/logs/2017-10
size 40
type "Log File"
date-modified "2017-10-01 04:00:01"
system file-list disk local 3
name ovsdb-server.log-20171001.gz
path /data/intdatastore/logs/2017-10
size 276
type "Log File"
date-modified "2017-10-01 04:00:01"
system file-list disk local 4
name ovs-vswitchd.log-20171001.gz
path /data/intdatastore/logs/2017-10
size 204
type "Log File"
...
system time
To set the system time using the Network Time Protocol (NTP) server, use the system time command in
global configuration mode. Use the no form of the command to delete the time configuration.
Note When you enable and synchronize the system time clock using an NTP server, you must reboot the Cisco
Enterprise NFVIS so that the BMC or CIMC date and time get updated with the new hardware clock.
Syntax Description timezone zone-subzone Specifies the timezone using zone and subzone.
Usage Guidelines When you set the system time manually using the system set-manual-time command, the NTP is disabled
automatically. Similarly, when NTP is enabled, the manual time configuration is automatically disabled.
Example
The following example shows how to set system time using NTP IPv4 server:
Example
The following example shows how to set system time using NTP IPv6 server:
system set-manual-time
To set the system time clock manually, use the system set-manual-time command in privileged EXEC mode.
Syntax Description date-time Specifies the manual date and time in YYYY-MM-DDTHH:MM:SS format. The supported year
range for specifying the manual time is from 2016 to 2036.
Usage Guidelines When you set the system time manually, the NTP is disabled automatically. Similarly, when NTP is enabled
using the system-time command, the manual time configuration is automatically disabled.
Example
nfvis# system set-manual-time 2017-01-01T17:35:39
status Displays the NTP status. You can filter the status using any of the following fields:
delay, jitter, offset, poll, reach, refid, st, t, or when.
Usage Guidelines If the configured NTP server is not displayed in the command output, check that the NTP server is configured
correctly.
When a remote host is queried, if the response is not received before the timeout time, the request times out
and the information is not displayed in the command output.
Example
The following is a sample output of the show system time ntp status command:
Example
Example
The following example shows how to disable the portal access:
Example
The following is a sample output of the show system portal status command:
Example
dev device (Optional) The device interface that the route will use.
Usage Guidelines Though only the destination and prefix length are mandatory parameters for creating a route, a valid route
requires that you specify the gateway or the interface or both.
Example
The following command creates a system route to the destination 203.0.113.1:
Example
The following is a sample output from the show system routes command:
Example
Example
system set-log
To set the log level and log type of messages, use the system set-log command in privileged EXEC mode.
system set-log level {debug | info | warning | error | critical} logtype {configuration | operational
| all}
info Logs all messages that have info and higher severity level.
warning Logs all messages that have warning and higher severity level.
error Logs all messages that have error and higher severity level.
Command Default For the configuration log, info is the default level. For the operational log, warning is the default level.
Usage Guidelines After a system reboot, the modified logging configuration is reset to the default level, that is, info for the
configuration log and warning for the operational log.
Example
The following example shows how to configure a log level:
Syntax Description configuration (Optional) Log level for the configuration log type is displayed.
operational (Optional) Log level for the operational log type is displayed.
Command Default The log level for all log types is displayed.
Example
The following is a sample output of the show system logging-level command with the default log
level settings:
show log
To display a list of available log files or content of a specific log file, use the show log command in privileged
EXEC mode.
Syntax Description log-name Specifies the log file name. The log file name should be same as shown in the output of the show
log command.
Usage Guidelines In Release 3.6.1 and earlier releases, the exact directory path (/var/log) and exact filename is required to
run this command.
Starting with Release 3.7.1, this command is modified for the following:
• Display a list of all available log files (using show log).
• Display a list of log files that match the partial filename provided in the log-name parameter.
• Display the content of the specified log file if the filename matches exactly as shown in show log output.
To filter the content of a log file, you can use the show log log-name | ? command.
The following examples display all available log files matching a partial name.
Example 2
The following example filters the content of a log file.
stateMachineType:VM_STATE_MACHINE;
serviceStateMachineContextId:1a037a82-b248-4117-9156-aa26bc8e2ce1;
deploymentDetailsId:15fa65be-0775-47c3-aa46-d6eb1e428a93; previousState:VM_INERT_STATE;
currentState:
VM_ERROR_STATE; monitorSet:true; serviceDefinition:0; vmInstance:demo7; vmIndex:0;
classMetadata:SingleTableEntityPersister(com.cisco.esc.db.VMStateMachineDao);
02-Mar-2017 01:46:27,669 ERROR [StateMachineEngine.java:buildLogContext():75] [tid=] [cl=SM
] [tags=]
Unable to set log context, null values found for RequestDetails
02-Mar-2017 01:46:27,673 INFO [LogContextService.java:outputDecoratedLog():185] [tid=]
[cl=SM ]
[tags=threadName:RECOVERY_WORKFLOW_STATE_MACHINE-93cfacf5-9ee8-4e0e-9438-722944b4da2d,stateMachineType:
RECOVERY_WORKFLOW_STATE_MACHINE,stateMachineContextId:
93cfacf5-9ee8-4e0e-9438-722944b4da2d]
RECOVERY_WORKFLOW_STATE_MACHINE-93cfacf5-9ee8-4e0e-9438-722--More--
...
source
To configure the source interface for a SPAN session, use the source command in session configuration mode.
To remove the source configuration, use the no form of the command.
Syntax Description all Specifies all supported interfaces for a SPAN session.
Usage Guidelines In the case of virtio net or SRIOV VF, you have to specify the VM group name and NIC ID of the VM
interface. If the VM vNIC is virtio net type, then the SPAN session is applied on the OVS bridge. If VM vNIC
is SRIOV VF, then the mirror is applied to the hardware bridge. The interface name is specified for a physical
interface, for example, GE0-0 or eth0.
Example
The following configuration shows how to configure a source interface for a SPAN session:
destination
To configure the destination interface for a SPAN session, use the destination command in session configuration
mode. To remove the destination configuration, use the no form of the command
Usage Guidelines You must dedicate a destination port for SPAN use. Except for traffic that is required for the SPAN session,
destination ports do not receive or forward traffic. When the SPAN is configured on the system, there might
be some performance hit.
Example
The following configuration shows how to configure a destination interface for a SPAN session:
Example
The following is a sample output of the show system monitor session command:
monitor session
To create a SPAN session, use the monitor session command in global configuration mode. To remove the
SPAN session, use the no form of the command.
Syntax Description number Specifies the SPAN session number. Valid range: 1-64
Example
The following example shows how to create a SPAN session:
tcpdump port
To configure the packet capture feature on a physical port, use the tcpdump port command in global
configuration mode. Use the no form of the command to remove the packet capture.
tcpdump port port-name [{filter filter-name protocol {ARP ICMP TCP UDP} time seconds }]
no tcpdump port port-name
Syntax Description port port-name Specifies the name of the physical port.
protocol (Optional) Specifies the protocol to capture specific packets. Supported options are:
• Internet Control Message Protocol (ICMP)
• Address Resolution Protocol (ARP)
• TCP
• UDP
time seconds (Optional) Specifies the time period over which packets are captured. The default value
is 60 seconds.
Example
The following example shows how to configure packet capture on a physical port:
tcpdump vnic
To configure the packet capture feature on a virtual network interface controller, use the tcpdump vnic
command in global configuration mode. Use the no form of the command to remove the packet capture.
tcpdump vnic tenant-name name deployment-name name vm-name name vnic-id id [{filter
filter-name protocol {ARP ICMP TCP UDP} time seconds}]
no tcpdump vnic tenant-name name deployment-name name vm-name name vnic-id id
protocol (Optional) Specifies the protocol to capture specific packets. Supported options
are:
• Internet Control Message Protocol (ICMP)
• Address Resolution Protocol (ARP)
• TCP
• UDP
time seconds (Optional) Specifies the time period over which packets are captured. The
default value is 60.
Example
The following example shows how to configure packet capture on a vNIC:
Example
The following is a sample output of the show system upgrade apply-image command:
Example
The following is a sample output of the show system upgrade reg-info command:
The table below describes the significant fields shown in the display:
Field Description
scheduled-time hours Specifies the time of upgrade in hours. The valid range is from 0 to 24 hours.
Example
The following example shows how to upgrade to a registered Cisco Enterprise NFVIS image:
default-location (Optional) Specifies the default location (/data/upgrade/package) of the upgrade image.
non-default-location (Optional) Specifies the complete path of the folder that contains the upgrade image.
This is other than the default location.
Usage Guidelines Ensure that you download or copy the image to the NFVIS server default target directory
"/data/upgrade/package" before starting the upgrade process. If the image is downloaded or copied to a location
other than the default directory, you will have to specify the exact path of the image when registering the
image.
Example
The following example shows how to register the Cisco Enterprise NFVIS upgrade image on the
host server:
factory-default-reset
To reset the Cisco Enterprise NFVIS host server to the default factory setting, use the factory-default-reset
command in global configuration mode.
Syntax Description all Erases all configuration. Connectivity is lost, and the admin password is
changed to factory default password.
all-except-images Erases all configuration except images. Connectivity is lost, and the admin
password is changed to factory default password.
manufacturing Erases all configuration except images. Connectivity is lost, and the admin
password is changed to factory default password.
all-with-bios-password Erases all configuration along with the BIOS password. Connectivity is lost,
and the admin password and BIOS password is changed to factory default
password.
Usage Guidelines This command is used only for troubleshooting. We recommend you contact Cisco Technical Support before
using this command.
Example
The following is an example of how to reset to the default factory setting:
Syntax Description ip address Specifies the remote host address that can be IPv4/IPv6/hostname.
Example
The following example shows how to configure remote host.
nfvis(config)# system settings logging host 172.19.162.117 port 1635 transport tcp
nfvis(config)# system settings logging host 172.19.162.111 port 163 transport udp
Syntax Description local Specifies the facility number. You can configure any facility from local0 to local7.
Example
The following example shows how to configure facility.
system settings logging severity {alert | critical | debug | emergency | error | informational |
notice | warning}
Syntax Description alert Logs at alert severity level and higher severity levels are sent.
critical Logs at critical severity level and higher severity levels are sent.
debug Logs at debug severity level and higher severity levels are sent.
emergency Logs at emergency severity level and higher severity levels are sent.
error Logs at error severity level and higher severity levels are sent.
informational Logs at informational severity level and higher severity levels are sent.
notice Logs at notice severity level and higher severity levels are sent.
warning Logs at warning severity level and higher severity levels are sent.
Example
The following example shows how to configure the severity of syslogs.
Example
nfvis# show running-config system settings logging
system settings logging host 192.0.2.3
transport tcp
port 1635
!
system settings logging host 192.0.2.34
transport udp
port 163
!
system settings logging host 192.0.2.40
port 1523
!
Example
The following example configures the engine ID.
snmp agent engineID 00:22:33:22:22:22:55
Example
The following example configures the system name.
snmp agent sysName TestSystem
snmp community
To configure SNMP community, use the snmp community command in global configuration mode.
Example
The following example configures the community pub_com with read only access.
snmp community pub_comm community-access readOnly
Example
The following example enable linkup traps.
nfvis(config)# snmp enable traps linkup
commit
end
Example
The following example disables linkup traps.
nfvis(config)# snmp disable traps linkup
commit
end
snmp group
To configure SNMP group, use the snmp group command in global configuration mode.
Example
The following example configures the SNMP group.
snmp group testgroup snmp 2 noAuthNoPriv read read-access write write-access notify
notify-access
snmp host
To configure the SNMP host to receive traps, use the snmp host command in global configuration mode.
Example
The following example configures host2 to receive traps.
snmp host host2 host-ip-address 10.2.2.2 host-port 162 host-version 2 host-security-level
noAuthNoPriv host-user-name public
snmp user
To configure SNMP user, use the snmp user command in global configuration mode.
Example
The following example configures the SNMP user.
snmp user public auth-protocol md5 priv-protocol des passphrase pass123 user-group 2
user-version 2
Example
admin@nfvis show snmp agent
snmp agent sysDescr "Cisco NFVIS "
snmp agent sysOID 1.3.6.1.4.1.9.12.3.1.3.2376 //platform specific
Example
admin@nfvis show snmp stats
snmp stats sysUpTime 40930629
snmp stats sysServices 70
snmp stats sysORLastChange 0
snmp stats snmpInPkts 0
snmp stats snmpInBadVersions 0
snmp stats snmpInBadCommunityNames 0
snmp stats snmpInBadCommunityUses 0
snmp stats snmpInASNParseErrs 0
snmp stats snmpSilentDrops 0
snmp stats snmpProxyDrops 0
Example
admin@nfvis show snmp traps
NAME STATE
-------------------
linkDown enabled
linkUp enabled
Example
radius-server host
To configure a RADIUS server host, use the radius-server host command in global configuration mode. To
delete the specified RADIUS server host, use the no form of the command.
Syntax Description ip-address Specifies the RADIUS server host IP address. The IP address can be an
IPv4 or IPv6 address.
hostname Specifies the RADIUS server host name. The host name can either be
an IPv4 or IPv6 address or a DNS domain name.
admin-priv admin-priv-number Specifies the minimum privilege level for administrator. Valid range is
from 1 to 15.
key key-number Specifies a preshared key for RADIUS communication between the
device and the RADIUS server.
oper-priv oper-priv-number Specifies the minimum privilege level for operator. Valid range is from
1 to 15.
Command Default The default value for the admin-priv parameter is 15. The default value for the oper-priv parameter is 11.
Example
The following example specifies a RADIUS server host.
Example
nfvis# show running-config radius-server
radius-server host 198.51.100.10
key 0
shared-secret sec123
admin-priv 2
oper-priv 1
tacacs-server host
To configure the TACACS+ server, use the tacacs-server host command in global configuration mode. To
remove the configuration, use the no form of this command.
Usage Guidelines You must configure a TACACS+ server before the configured TACACS+ features on your network access
server are available.
Example
The following example shows how to configure the TACACS+ server:
key
To identify the share key encryption level for all communication between the TACACS+ server and Cisco
ENCS, use the key command in host configuration mode.
key key-id
Syntax Description key-id Specifies the identification number of an authentication key. It is either zero or one. It only supports
a clear text value.
Example
The following example shows how to configure the autehntication key for all communications
between the TACACS+ server and Cisco ENCS:
admin-priv
To assign the admin privilege level to the administrator role, use the admin-priv command in host configuration
mode. To remove the privilege level configuration, use the no form of the command.
admin-priv number
no admin-priv
Syntax Description number Specifies the privilege level for the admin. Valid range: 1-15.
Example
The following example shows how to configure the privilege level for the administrator role:
oper-priv
To assign the operator privilege level to the opeartor role, use the oper-priv command in host configuration
mode. To remove the privilege level configuration, use the no form of the command.
oper-priv number
no oper-priv
Syntax Description number Specifies the privilege level for the operator role. Valid range: 1-15.
Example
The following example shows how to configure the privilege level for the operator role:
Example
Syntax Description length Specifies the minimum length. The minimum length
must be between 7 to 128 characters.
Usage Guidelines Only the admin user can use this command.
Example
nfvis(config)# configure terminal
nfvis(config)# rbac authentication min-pwd-length 14
nfvis(config)# commit
nfvis(config)# end
Syntax Description enforce Enforces or removes the rule for password lifetime
validation. Valid values for this parameter are true
and false.
min-days min-days Specifies the number of days after which the users
can change the password.
max-days max-days Specifies the number of days before which the users
must change the password.
Command Default The default minimum lifetime value is set to 1 day and the default maximum lifetime value is set to 60 days.
Usage Guidelines • Only the admin user can use this command.
• The minimum and maximum lifetime values and the rule to check for these values are not applicable to
the admin user.
Example
nfvis(config)# configure terminal
nfvis(config)# rbac authentication password-lifetime enforce true min-days 1 max-days 30
nfvis(config)# commit
nfvis(config)# end
Syntax Description enforce Enforces or removes the rule for checking and
mark-ing unused user accounts as inactive. Valid
values for this parameter are true and false.
Usage Guidelines • Only the admin user can use this command.
• The inactivity period and the rule to check the inactivity period are not applicable to the admin user.
• When marked as inactive, a user cannot login to the system. To allow the user to again login to the system,
the ad-min user must reactivate the user account by using the rbac authentication users user username
activate command.
Example
nfvis(config)# configure terminal
nfvis(config)# rbac authentication account-inactivity enforce true inactivity-days 2
nfvis(config)# commit
nfvis(config)# end
Example
The following example shows how to create a new user:
nfvis(config)# rbac authentication users user admin2 password Cisco123* role administrators
nfvis(config)# commit
Usage Guidelines Only the admin user can use this command.
Example
nfvis(config)# configure terminal
nfvis(config)# rbac authentication users user guest_user activate
nfvis(config)# commit
nfvis(config)# end
Example
The following example shows how to change the password of an existing user:
rbac authentication users user user-name change-role old-role role-type new-role role-type
Example
The following example shows how to change the user role:
Syntax Description user user-name (Optional) The specified user's details are displayed.
Example
The following is a sample output of the show running-config rbac authentication users command:
Example
The following example configures the secondary WAN.
nfvis(config)# system settings wan secondary ip address 1.1.2.3 255.255.255.0
Example
The following example configures the source interface.
nfvis(config)# system settings source-interface 1.1.2.3
hostaction pnic-breakout
To change the PNIC mode from 2x40G to 4x10G or from 4x10G to 2x40G, use the hostaction pnic-breakout
device command in privileged EXEC mode.
Syntax Description pnic-breakout Changes the PNIC mode from 2x40G to 4x10G or vice-versa.
device number Specifies the number of devices on which the mode must be changed.
Example
nfvis# hostaction pnic-breakout device 1 mode 4x10
Warning: Will reboot the system after the mode is changed on the 40G PNIC. All PNIC
configuration like adminstatus, duplex, lldp, promiscuous, speed, sriov, track-state
will be lost and set to default.
Are you sure you want to perform the PNIC breakout? [no,yes] yes
The system is going down for reboot at Wed 2021-06-02 21:16:36 UTC!
Syntax Description pnic-breakout Changes the PNIC mode from 2x40G to 4x10G or vice-versa.
device number Specifies the number of devices on which the mode must be changed.
Example
nfvis# hostaction pnic-breakout force device 1 mode 4x10
Warning: Will reboot the system after the mode is changed on the 40G PNIC. All PNIC
configuration like adminstatus, duplex, lldp, promiscuous, speed, sriov, track-state
will be lost and set to default.
Are you sure you want to perform the PNIC breakout? [no,yes] yes
The system is going down for reboot at Wed 2021-06-02 21:39:53 UTC!
pnic
To modify the configuration of an Ethernet port or to create a port channel, use the pnic command. To set an
Ethernet port to its default settings or to delete a port channel, use the no form of the command.
adminstatus Brings a port up or down administratively. Valid values are up and down.
Note adminstatus is not supported on port channel.
type Specifies the type of the port. Valid values are ethernet and port_channel. To
create a port channel, you must specify the value as port_channel.
bond_mode Specifies the bond mode for a port channel. Valid values are active-backup,
balance-slb, and balance-tcp. Default is balance-tcp.
lacp_type Specifies the LACP type for a port channel. Valid values are off, active, and
passive. Default is off.
trunks vlan_num Specifies the VLANs. Valid range is from 1 to 4096. Default is VLAN 1. Enter
VLANs separated by commas, VLAN ranges separated by dashes, or a
combination of both.
lldp Enables or disables LLDP on a port. Valid values are enable and disable. Default
is disable.
Note lldp is not supported on port channel.
Example
nfvis# config
nfvis(config)# pnic pc type port_channel
nfvis(config-pnic-pc)# commit
nfvis(config-pnic-pc)# end
Example
nfvis# config
nfvis(config)# no pnic eth2 member_of pc
nfvis(config-pnic-eth2)# commit
nfvis(config-pnic-eth2)# end
show nic
To display the various NIC cards inserted in the CSP device, use the show nic command in privileged EXEC
mode.
show nic
Example
nfvis# show nic
SLOTID ADAPTER VENDOR DEVID MODE DEVNO PNICS
-------------------------------------------------------------------------------------------------------------------
1 Intel X520 dual port adapter 8086 10fb NA NA ['eth1-1', 'eth1-2']
3 Intel X710-DA4 Quad Port 10Gb SFP+ 8086 1572 NA NA ['eth3-1', 'eth3-2',
'eth3-3', 'eth3-4']
converged NIC
2 Intel XL710-QDA2 Dual Port 40Gb 8086 1583 2x40 1 ['eth2-1', 'eth2-2']
5 Intel i350 Quad Port 1Gb Adapter 8086 1521 NA NA ['eth5-1', 'eth5-2',
'eth5-3', 'eth5-4']
4 Intel X520 dual port adapter 8086 10fb NA NA ['eth4-1', 'eth4-2']
show pnic
To display all statistics or only specific information about a port or all ports, use the show pnic command in
privileged EXEC mode.
Syntax Description name Specifies the name of the port for which the information is displayed.
Example
nfvis# show pnic
Name Link Admin MTU Mac Passthrough Speed Op-speed Rx
Bytes Packets Errors Dropped Mbps Broadcast Multicast TX Bytes Packets
Errors Dropped Collisions Mbps Broadcast Multicast
================================================================================================================================================================================
eth0 up up 9000 d8:b1:90:ff:f5:88 none 1G 1000
1469476983 17749881 0 0 14156964 2888574 198310581
272571 0 0 40
68440
eth1 up up 9000 d8:b1:90:ff:f5:89 none 1G 1000
Example
nfvis# show pnic stats
Name Rx Bytes Packets Errors Dropped Mbps Broadcast Multicast TX Bytes
Packets Errors Dropped Collisions Mbps Broadcast Multicast
=========================================================================================================================================================================
eth0 1469743586 17753343 0 0 14159834 2889066 198318715
272603 0 0 40 68450
eth1 19830637 329428 0 0 0 325573 4181034
27591 0 0 0 27591
eth2 0 0 0 0 0 0 0
0 0 0 0 0
eth3 0 0 0 0 0 0 0
0 0 0 0 0
eth4 0 0 0 0 0 0 0
0 0 0 0 0
eth5 0 0 0 0 0 0 0
0 0 0 0 0
0
Example
nfvis# show pnic eth1 stats
stats receive bytes 19862257
stats receive packets 329955
stats receive errors 0
stats receive dropped 0
stats receive broadcast 0
stats receive multicast 326100
stats transmit bytes 4187361
stats transmit packets 27628
stats transmit errors 0
stats transmit dropped 0
stats transmit broadcast 0
stats transmit multicast 27628
show pnic-breakout
To display the 40G NIC mode and adapter information, use the show pnic-breakout command in privileged
EXEC mode.
show pnic-breakout
Example
-----------------------------------------------------------------------------------------------------
1 5e 8086 1583 Cisco(R) Ethernet Converged NIC XL710-QDA2 2x40 ['eth2-1',
'eth2-2']
show port-channel
To show configured port channels, use the show port-channel command in privileged EXEC mode.
show port-channel
Example
nfvis# show port-channel
---- bondtrue ----
bond_mode: active-backup
bond may use recirculation: no, Recirc-ID : -1
bond-hash-basis: 0
updelay: 0 ms
downdelay: 0 ms
lacp_status: off
active slave mac: 00:00:00:00:00:00(none)
Example
nfvis# show lldp stats
TX DISCARD ERROR RX DISCARDED UNREC
NAME FRAMES RX RX FRAMES TLVS TLVS AGEOUTS
-----------------------------------------------------------------
eth0 23 0 0 19667 0 0 0
eth1 0 0 0 0 0 0 0
eth2 0 0 0 0 0 0 0
eth3 0 0 0 0 0 0 0
eth4 0 0 0 0 0 0 0
eth5 0 0 0 0 0 0 0
Example
nfvis# show lldp neighbors
NAME DEVICE ID HOLDTIME CAPS PLATFORM PORTID DESCRIPTION
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
eth0 Switch1623 120 Bridge, Router Cisco IOS Software, Catalyst L3 Switch Software
(CAT3K_CAA-UNIVERSALK9-M),
Version 15.0(1)EX3, RELEASE SOFTWARE (fc2) Ifname: Gi1/0/4
GigabitEthernet1/0/4
eth1 None 0 None None None None
show secure-overlay
To display the secure overlay status, use the show secure-overlay command in privileged EXEC mode.
show secure-overlay
Example
The following is a sample output of the show secure-overlay command:
secure-overlay test
state up
active-local-bridge wan-br
selected-local-bridge wan-br
active-local-system-ip-addr 90.90.90.8
active-remote-interface-ip-addr 10.30.1.113
active-remote-system-ip-addr 90.90.90.1
active-remote-system-ip-subnet 90.90.90.1/32
active-remote-id "\"10.30.1.113\""
nfvis# show bgp ?
Possible completions:
ipv4 Address family
vpnv4 Address family
| Output modifiers
Command Default Information about local BGP status for BGP over IPSec tunnel is displayed.
Example
The following is a sample output of the show bgp vpnv4 unicast command:
Command Default Information about the BGP learned/announced routes for BGP over IPSec tunnel is displayed.
Example
The following is a sample output of the show bgp vpnv4 unicast route command:
Command Default Information about the BGP neighbor status for BGP over IPSec tunnel is displayed.
Example
The following is a sample output of the show bgp vpnv4 unicast summary command:
cluster cluster name { datastore [ intdatastore | extdatastore1 | extdatastore2 ] | size size number
| node ipv4 address addresstype ipv4 | node ipv4 address addresstype ipv4 | node ipv4 address addresstype
ipv4 }
Syntax Description cluster cluster name Specifies the name of the cluster.
node Specifies the address and address type of the device in the
cluster.
Note Three nodes must be added to the configuration, for the commit to be successful.
Example
cluster migrate-deployment
To migrate deployments from a source node to a destination node, use the cluster migrate-deployment
command in privileged EXEC mode.
Syntax Description cluster cluster name Specifies the cluster in which the deployments must be migrated.
source-node ip address Specifies the node from which the deployment must be migrated.
destination node ip address Specifies the node to which the deployment must be migrated.
Example
nfvis# cluster test migrate-deployment source-node 209.165.200.225 destination-node
209.165.201.31 all-deployments
nfvis# cluster test migrate-deployment source-node 209.165.200.225 destination-node
209.165.201.31 deployment-list [ centosvm4 centosvm5 ]
Example
nfvis# support show arp
IP address HW type Flags HW address Mask Device
203.0.113.1 0x1 0x2 00:25:b4:47:44:00 * wan-br
203.0.113.1 0x1 0x2 3c:ce:73:da:60:00 * wan-br
203.0.113.1 0x1 0x2 00:00:0c:9f:f0:15 * wan-br
Example
The following is a sample output of the support show bgp command:
Command Default Information about the BGP routes learnt through BGP is displayed.
Example
The following is a sample output of the support show bgp route command:
Example
nfvis# support show config-drive 12
-rw-r--r--. 1 qemu qemu 393216 Dec 1 00:25
/cisco/esc/esc_database/nodejs/VM/4e802bd4-c6e4-4c7b-a163-787927324967/
4e802bd4-c6e4-4c7b-a163-787927324967-hdd.config
Example
nfvis# support show config-drive content 12
<version text="1"/> <hypervisor text="nfvis"/> <guest text="TEST"/> <gateway addr="10.1.1.1"/>
<mgmt-intf text="Virtual2"/>
<data-intf text="SHARED"/> <localip addr="10.1.1.1" mask="10.1.1.1"/> <int-intf
text="Virtual1"/>
<intip addr="10.20.0.3" mask="255.255.255.0"/> <cm addr="10.1.1.1"/> <ntp addr="10.1.1.1"/>
</bootstrap>
vWAAS-6000R <bootstrap> <version text="1"/> <hypervisor text="nfvis"/> <guest text="TEST"/>
<gateway addr="10.1.1.1"/>
<mgmt-intf text="Virtual2"/> <data-intf text="SHARED"/> <localip addr="10.1.1.1"
mask="10.1.1.1"/>
<int-intf text="Virtual1"/> <intip addr="10.20.0.3" mask="255.255.255.0"/>
<cm addr="10.1.1.1"/> <ntp addr="10.1.1.1"/> </bootstrap>
vWAAS-6000R
{"files":[{"path":"bootstrap-cfg.xml","content_path":"/content/0000"},{"path":"model.txt","content_path":
"/content/0001"}]}
Example
nfvis# support show cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 79
model name : Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz
stepping : 1
microcode : 0xb00001f
cpu MHz : 1265.859
cache size : 25600 KB
physical id : 0
siblings : 20
core id : 0
cpu cores : 10
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 20
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts
acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon
pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64
monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat epb
pln pts dtherm intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle
avx2 smep bmi2 erms invpcid rtm cqm rdseed adx smap xsaveopt cqm_llc cqm_occup_llc
cqm_mbm_total cqm_mbm_local
bogomips : 4389.33
clflush size : 64
cache_alignment : 64
address sizes : 46 bits physical, 48 bits virtual
power management:
...
Example
nfvis# support show date-time
Thu Nov 16 10:50:52 UTC 2017
support show df
To display the amount of disk space used and available, use the support show df command in privileged
EXEC mode.
support show df
Example
nfvis# support show df
Filesystem Type 1024-blocks Used Available Capacity Mounted on
/dev/mapper/vg_nfv-lv_root ext4 8125880 1755256 5934812 23% /
devtmpfs devtmpfs 65863696 0 65863696 0% /dev
tmpfs tmpfs 65874332 12 65874320 1% /dev/shm
tmpfs tmpfs 65874332 1224 65873108 1% /run
tmpfs tmpfs 65874332 0 65874332 0% /sys/fs/cgroup
/dev/sda2 ext4 739536 112860 572916 17% /boot
/dev/mapper/vg_nfv-lv_var ext4 3997376 137112 3634168 4% /var
/dev/mapper/vg_nfv-lv_data ext4 2311085988 4765488 2305792116 1% /data
tmpfs tmpfs 13174868 0 13174868 0% /run/user/0
Example
nfvis# support show domainname
Example
nfvis# support show dmidecode
# dmidecode 3.0
Scanning /dev/mem for entry point.
SMBIOS 3.0.0 present.
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Cisco Systems Inc
Product Name: UCSC-C220-M4S
Version: A0
Serial Number: FCH2110V0DX
UUID: EB7C9CE9-9DF9-3142-898B-C84A16B10706
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Not Specified
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: Cisco Systems Inc
Product Name: UCSC-C220-M4S
Version: 74-12419-02
Serial Number: FCH2108JLC4
Asset Tag: Unknown
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: Not Specified
Chassis Handle: 0x0003
Type: Server Blade
Contained Object Handles: 0
Handle 0x0003, DMI type 3, 25 bytes
Chassis Information
Manufacturer: Cisco Systems Inc
Type: Rack Mount Chassis
Lock: Not Present
Version: 74-12502-02
Serial Number: FCH2110V0DX
Asset Tag: Unknown
Boot-up State: Safe
Example
nfvis# support show ethtool eth1
nfvis# support show ethtool eth1
Driver information for device eth1
driver: igb
version: 5.3.0-k
firmware-version: 1.63, 0x80000b15, 0.384.130
expansion-rom-version:
bus-info: 0000:01:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
highdma: on [fixed]
rx-vlan-filter: on [fixed]
vlan-challenged: off [fixed]
tx-lockless: off [fixed]
netns-local: off [fixed]
tx-gso-robust: off [fixed]
tx-fcoe-segmentation: off [fixed]
tx-gre-segmentation: off [fixed]
tx-ipip-segmentation: off [fixed]
tx-sit-segmentation: off [fixed]
tx-udp_tnl-segmentation: off [fixed]
tx-mpls-segmentation: off [fixed]
fcoe-mtu: off [fixed]
tx-nocache-copy: off
loopback: off [fixed]
rx-fcs: off [fixed]
rx-all: off
tx-vlan-stag-hw-insert: off [fixed]
rx-vlan-stag-hw-parse: off [fixed]
rx-vlan-stag-filter: off [fixed]
busy-poll: off [fixed]
tx-sctp-segmentation: off [fixed]
l2-fwd-offload: off [fixed]
hw-tc-offload: off [fixed]
Permanent address: 70:db:98:70:2f:6f
Pause parameters for eth1:
Autonegotiate: on
RX: off
TX: off
NIC statistics:
rx_packets: 0
tx_packets: 0
rx_bytes: 0
tx_bytes: 0
rx_broadcast: 0
tx_broadcast: 0
rx_multicast: 0
tx_multicast: 0
multicast: 0
collisions: 0
rx_crc_errors: 0
rx_no_buffer_count: 0
rx_missed_errors: 0
tx_aborted_errors: 0
tx_carrier_errors: 0
tx_window_errors: 0
tx_abort_late_coll: 0
tx_deferred_ok: 0
tx_single_coll_ok: 0
tx_multi_coll_ok: 0
tx_timeout_count: 0
rx_long_length_errors: 0
rx_short_length_errors: 0
rx_align_errors: 0
tx_tcp_seg_good: 0
tx_tcp_seg_failed: 0
rx_flow_control_xon: 0
rx_flow_control_xoff: 0
tx_flow_control_xon: 0
tx_flow_control_xoff: 0
rx_long_byte_count: 0
tx_dma_out_of_sync: 0
tx_smbus: 0
rx_smbus: 0
dropped_smbus: 0
os2bmc_rx_by_bmc: 0
os2bmc_tx_by_bmc: 0
os2bmc_tx_by_host: 0
os2bmc_rx_by_host: 0
tx_hwtstamp_timeouts: 0
rx_hwtstamp_cleared: 0
rx_errors: 0
tx_errors: 0
tx_dropped: 0
rx_length_errors: 0
rx_over_errors: 0
rx_frame_errors: 0
rx_fifo_errors: 0
tx_fifo_errors: 0
tx_heartbeat_errors: 0
tx_queue_0_packets: 0
tx_queue_0_bytes: 0
tx_queue_0_restart: 0
tx_queue_1_packets: 0
tx_queue_1_bytes: 0
tx_queue_1_restart: 0
tx_queue_2_packets: 0
tx_queue_2_bytes: 0
tx_queue_2_restart: 0
tx_queue_3_packets: 0
tx_queue_3_bytes: 0
tx_queue_3_restart: 0
tx_queue_4_packets: 0
tx_queue_4_bytes: 0
tx_queue_4_restart: 0
tx_queue_5_packets: 0
tx_queue_5_bytes: 0
tx_queue_5_restart: 0
tx_queue_6_packets: 0
tx_queue_6_bytes: 0
tx_queue_6_restart: 0
tx_queue_7_packets: 0
tx_queue_7_bytes: 0
tx_queue_7_restart: 0
rx_queue_0_packets: 0
rx_queue_0_bytes: 0
rx_queue_0_drops: 0
rx_queue_0_csum_err: 0
rx_queue_0_alloc_failed: 0
rx_queue_1_packets: 0
rx_queue_1_bytes: 0
rx_queue_1_drops: 0
rx_queue_1_csum_err: 0
rx_queue_1_alloc_failed: 0
rx_queue_2_packets: 0
rx_queue_2_bytes: 0
rx_queue_2_drops: 0
rx_queue_2_csum_err: 0
rx_queue_2_alloc_failed: 0
rx_queue_3_packets: 0
rx_queue_3_bytes: 0
rx_queue_3_drops: 0
rx_queue_3_csum_err: 0
rx_queue_3_alloc_failed: 0
rx_queue_4_packets: 0
rx_queue_4_bytes: 0
rx_queue_4_drops: 0
rx_queue_4_csum_err: 0
rx_queue_4_alloc_failed: 0
rx_queue_5_packets: 0
rx_queue_5_bytes: 0
rx_queue_5_drops: 0
rx_queue_5_csum_err: 0
rx_queue_5_alloc_failed: 0
rx_queue_6_packets: 0
rx_queue_6_bytes: 0
rx_queue_6_drops: 0
rx_queue_6_csum_err: 0
rx_queue_6_alloc_failed: 0
rx_queue_7_packets: 0
rx_queue_7_bytes: 0
rx_queue_7_drops: 0
rx_queue_7_csum_err: 0
rx_queue_7_alloc_failed: 0
rx-usecs: 3
rx-frames: 0
rx-usecs-irq: 0
rx-frames-irq: 0
tx-usecs: 0
tx-frames: 0
tx-usecs-irq: 0
tx-frames-irq: 0
rx-usecs-low: 0
rx-frame-low: 0
tx-usecs-low: 0
tx-frame-low: 0
rx-usecs-high: 0
rx-frame-high: 0
tx-usecs-high: 0
tx-frame-high: 0
Example
nfvis# support show ifconfig wan-br
wan-br: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9000
inet 172.19.181.196 netmask 255.255.255.0 broadcast 172.19.181.255
inet6 fe80::72db:98ff:fe70:2f6e prefixlen 64 scopeid 0x20<link>
ether 70:db:98:70:2f:6e txqueuelen 1000 (Ethernet)
RX packets 3373533 bytes 5021452007 (4.6 GiB)
RX errors 0 dropped 3945 overruns 0 frame 0
TX packets 337841 bytes 30441490 (29.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Example
nfvis# support show iostat
Major Minor Device Reads Reads Sectors Time (ms) Writes Writes Sectors Time (ms) IOs In
Time (ms) Weighted
Number Number Name Successful Merged Read Reading Completed Merged Written Writing Progress
Doing IOs Time(ms) IOs
-----------------------------------------------------------------------------------------------------------------------------------------
8 0 sda 34721 8 938752 149830 2713238 302897 37631784 84086836 0 1098844 84236605
8 1 sda1 52 0 416 156 0 0 0 0 0 156 156
8 2 sda2 437 0 49322 629 7 1 64 0 0 469 628
8 3 sda3 34054 8 884766 148345 2713231 302896 37631720 84086836 0 1098524 84238309
253 0 dm-0 17693 0 564042 101847 66698 0 694744 74520 0 40719 176366
253 1 dm-1 218 0 4456 832 0 0 0 0 0 810 832
253 2 dm-2 15066 0 261514 42646 2911495 0 36585456 84848114 0 1056312 84891060
253 3 dm-3 1055 0 53730 4699 37951 0 351520 246240 0 20556 250939
Example
The following is a sample output of the support show ipsec command:
Example
nfvis# support show loadavg
Avg CPU and IO Utilization (1m) : 0.40
Avg CPU and IO Utilization (5m) : 0.36
Avg CPU and IO Utilization (10m) : 0.33
Running/Total Num of Processes : 1/678
Last Proccess ID Used : 13411
Example
nfvis# support show meminfo
MemTotal: 131748668 kB
MemFree: 123779264 kB
MemAvailable: 128225916 kB
Buffers: 11800 kB
Cached: 4887312 kB
SwapCached: 0 kB
Active: 1842792 kB
Inactive: 4658692 kB
Active(anon): 1613936 kB
Inactive(anon): 13644 kB
Active(file): 228856 kB
Inactive(file): 4645048 kB
Unevictable: 184888 kB
Mlocked: 184888 kB
SwapTotal: 16777212 kB
SwapFree: 16777212 kB
Dirty: 5112 kB
Writeback: 0 kB
AnonPages: 1787960 kB
Mapped: 95852 kB
Shmem: 16156 kB
Slab: 240824 kB
SReclaimable: 172504 kB
SUnreclaim: 68320 kB
KernelStack: 11536 kB
PageTables: 22360 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 82651544 kB
Committed_AS: 7245188 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 507704 kB
VmallocChunk: 34291843068 kB
HardwareCorrupted: 0 kB
AnonHugePages: 1208320 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
DirectMap4k: 171680 kB
DirectMap2M: 7055360 kB
DirectMap1G: 128974848 kB
Example
nfvis# support show netstattcp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 127.0.0.1:7878 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:199 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:2023 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8008 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22222 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:4565 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:8888 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:830 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:8000 0.0.0.0:* LISTEN
tcp6 0 0 :::8001 :::* LISTEN
tcp6 0 0 127.0.0.1:8005 :::* LISTEN
tcp6 0 0 ::1:7878 :::* LISTEN
tcp6 0 0 :::8009 :::* LISTEN
tcp6 0 0 :::22222 :::* LISTEN
tcp6 0 0 :::111 :::* LISTEN
tcp6 0 0 :::8080 :::* LISTEN
tcp6 0 0 :::80 :::* LISTEN
tcp6 0 0 :::8081 :::* LISTEN
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 :::443 :::* LISTEN
tcp6 0 0 :::830 :::* LISTEN
Example
nfvis# support show netstatudp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
udp 0 0 0.0.0.0:161 0.0.0.0:*
udp 0 0 127.0.0.1:323 0.0.0.0:*
udp 0 0 0.0.0.0:1610 0.0.0.0:*
udp6 0 0 ::1:323 :::*
udp6 0 0 ::1:1610 :::*
Example
nfvis# support show procstat
cpu 155096 1 303421 267304458 50402 0 4774 0 52078 0
cpu0 29046 0 43045 6607705 3121 0 1175 0 0 0
cpu1 27238 0 39353 6562272 1857 0 2558 0 0 0
cpu2 0 0 231 6697805 0 0 0 0 0 0
cpu3 0 0 231 6698222 0 0 0 0 0 0
cpu4 0 0 231 6698222 0 0 0 0 0 0
cpu5 0 0 231 6698222 0 0 0 0 0 0
cpu6 0 0 231 6698222 0 0 0 0 0 0
cpu7 0 0 231 6698221 0 0 0 0 0 0
cpu8 0 0 231 6698221 0 0 0 0 0 0
cpu9 0 0 231 6698221 0 0 0 0 0 0
cpu10 0 0 262 6697886 0 0 0 0 0 0
cpu11 0 0 231 6698214 0 0 0 0 0 0
cpu12 0 0 231 6698213 0 0 0 0 0 0
cpu13 0 0 231 6698213 0 0 0 0 0 0
cpu14 0 0 231 6698212 0 0 0 0 0 0
cpu15 0 0 231 6698212 0 0 0 0 0 0
cpu16 0 0 231 6698212 0 0 0 0 0 0
cpu17 0 0 231 6698211 0 0 0 0 0 0
cpu18 0 0 231 6698211 0 0 0 0 0 0
cpu19 52484 0 27416 6600223 63 0 41 0 52078 0
cpu20 22792 0 95509 6572676 1530 0 368 0 0 0
cpu21 23533 0 89953 6524896 43829 0 631 0 0 0
cpu22 0 0 231 6698210 0 0 0 0 0 0
cpu23 0 0 231 6698210 0 0 0 0 0 0
cpu24 0 0 231 6698209 0 0 0 0 0 0
cpu25 0 0 231 6698209 0 0 0 0 0 0
cpu26 0 0 231 6698209 0 0 0 0 0 0
cpu27 0 0 231 6698209 0 0 0 0 0 0
cpu28 0 0 231 6698208 0 0 0 0 0 0
cpu29 0 0 231 6698207 0 0 0 0 0 0
cpu30 0 0 231 6698207 0 0 0 0 0 0
cpu31 0 0 231 6698207 0 0 0 0 0 0
cpu32 0 0 231 6698206 0 0 0 0 0 0
cpu33 0 0 231 6698206 0 0 0 0 0 0
cpu34 0 0 231 6698206 0 0 0 0 0 0
Example
Example
nfvis# support show snmp
Ip: Forwarding DefaultTTL InReceives InHdrErrors InAddrErrors ForwDatagrams InUnknownProtos
InDiscards InDelivers OutRequests
OutDiscards OutNoRoutes ReasmTimeout ReasmReqds ReasmOKs ReasmFails FragOKs FragFails
FragCreates
Ip: 1 64 6869229 0 0 0 0 0 3944160 3939158 407 0 0 0 0 0 0 0 0
Icmp: InMsgs InErrors InCsumErrors InDestUnreachs InTimeExcds InParmProbs InSrcQuenchs
InRedirects InEchos InEchoReps InTimestamps
InTimestampReps InAddrMasks InAddrMaskReps OutMsgs OutErrors OutDestUnreachs OutTimeExcds
OutParmProbs OutSrcQuenchs OutRedirects
OutEchos OutEchoReps OutTimestamps OutTimestampReps OutAddrMasks OutAddrMaskReps
Icmp: 9732 0 0 9732 0 0 0 0 0 0 0 0 0 0 9735 0 9735 0 0 0 0 0 0 0 0 0 0
IcmpMsg: InType3 OutType3
IcmpMsg: 9732 9735
Tcp: RtoAlgorithm RtoMin RtoMax MaxConn ActiveOpens PassiveOpens AttemptFails EstabResets
CurrEstab InSegs OutSegs RetransSegs
InErrs OutRsts InCsumErrors
Tcp: 1 200 120000 -1 15203 14161 1119 7 402 3931354 3927811 489 0 1127 0
Udp: InDatagrams NoPorts InErrors OutDatagrams RcvbufErrors SndbufErrors InCsumErrors
Udp: 0 9732 0 9732 0 0 0
UdpLite: InDatagrams NoPorts InErrors OutDatagrams RcvbufErrors SndbufErrors InCsumErrors
UdpLite: 0 0 0 0 0 0 0
Example
nfvis# support show system-version
Linux version 3.10.0-514.21.1.el7.x86_64 ([email protected]) (gcc version 4.8.5 20150623
(Red Hat 4.8.5-11) (GCC) )
#1 SMP Tue Aug 8 14:23:12 IST 2017
Example
nfvis# support show system-hostname
nfvis
Example
nfvis# support virsh all-info
support virsh list
Id Name State
----------------------------------------------------
1 1510117366.RouterUnmon running
2 1510085877.ubuntu running
3 1510095552.ROUTER running
4 isr1-dep.isr1-vg running
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<emulator>/usr/libexec/qemu-kvm</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2' cache='writethrough'/>
<source
file='/data/cisco/vm_lifecycle/volumes/2329b9ff-2a77-4e20-9cad-a5a5984bd4ba_0.img'/>
<backingStore type='file' index='1'>
<format type='qcow2'/>
<source
file='/data/cisco/vm_lifecycle/volumes/isrv-universalk9.16.06.01-vga.qcow2_0.img'/>
<backingStore/>
</backingStore>
<target dev='vda' bus='virtio'/>
<alias name='virtio-disk0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
</disk>
<controller type='usb' index='0'>
<alias name='usb'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
</controller>
<controller type='pci' index='0' model='pci-root'>
<alias name='pci.0'/>
</controller>
<interface type='bridge'>
<mac address='52:54:00:f7:06:89'/>
<source network='lan-net' bridge='lan-br'/>
<virtualport type='openvswitch'>
<parameters interfaceid='98b0908f-8ddc-4800-b970-b1a902f2f1ac'/>
</virtualport>
<target dev='vnic8'/>
<model type='virtio'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>
<interface type='bridge'>
<mac address='52:54:00:52:67:ba'/>
<source network='wan-net' bridge='wan-br'/>
<virtualport type='openvswitch'>
<parameters interfaceid='b42b7f81-37a8-45c5-b468-ec60074a5ec4'/>
</virtualport>
<target dev='vnic9'/>
<model type='virtio'/>
<alias name='net1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</interface>
<input type='mouse' bus='ps2'>
<alias name='input0'/>
</input>
<input type='tablet' bus='usb'>
<alias name='input1'/>
<address type='usb' bus='0' port='1'/>
</input>
<input type='keyboard' bus='ps2'>
<alias name='input2'/>
</input>
<graphics type='vnc' port='5900' autoport='yes' listen='0.0.0.0'>
<listen type='address' address='0.0.0.0'/>
</graphics>
<video>
<model type='cirrus' vram='16384' heads='1' primary='yes'/>
<alias name='video0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</video>
<memballoon model='none'/>
</devices>
<seclabel type='dynamic' model='selinux' relabel='yes'>
<label>system_u:system_r:svirt_t:s0:c379,c571</label>
<imagelabel>system_u:object_r:svirt_image_t:s0:c379,c571</imagelabel>
</seclabel>
<seclabel type='dynamic' model='dac' relabel='yes'>
<label>+107:+107</label>
<imagelabel>+107:+107</imagelabel>
</seclabel>
</domain>
...
Example
nfvis# support virsh capabilities
<capabilities>
<host>
<uuid>eb7c9ce9-9df9-3142-898b-c84a16b10706</uuid>
<cpu>
<arch>x86_64</arch>
<model>Broadwell</model>
<vendor>Intel</vendor>
<topology sockets='1' cores='10' threads='2'/>
<feature name='vme'/>
<feature name='ds'/>
<feature name='acpi'/>
<feature name='ss'/>
<feature name='ht'/>
<feature name='tm'/>
<feature name='pbe'/>
<feature name='dtes64'/>
<feature name='monitor'/>
<feature name='ds_cpl'/>
<feature name='vmx'/>
<feature name='smx'/>
<feature name='est'/>
<feature name='tm2'/>
<feature name='xtpr'/>
<feature name='pdcm'/>
<feature name='dca'/>
<feature name='osxsave'/>
<feature name='f16c'/>
<feature name='rdrand'/>
<feature name='arat'/>
<feature name='tsc_adjust'/>
<feature name='cmt'/>
<feature name='xsaveopt'/>
<feature name='mbm_total'/>
<feature name='mbm_local'/>
<feature name='pdpe1gb'/>
<feature name='abm'/>
<feature name='invtsc'/>
<arch name='x86_64'>
<wordsize>64</wordsize>
<emulator>/usr/libexec/qemu-kvm</emulator>
<machine maxCpus='240'>pc-i440fx-rhel7.0.0</machine>
<machine canonical='pc-i440fx-rhel7.0.0' maxCpus='240'>pc</machine>
<machine maxCpus='240'>rhel6.0.0</machine>
<machine maxCpus='240'>rhel6.1.0</machine>
<machine maxCpus='240'>rhel6.2.0</machine>
<machine maxCpus='240'>rhel6.3.0</machine>
<machine maxCpus='240'>rhel6.4.0</machine>
<machine maxCpus='240'>rhel6.5.0</machine>
<machine maxCpus='240'>rhel6.6.0</machine>
<domain type='qemu'/>
<domain type='kvm'>
<emulator>/usr/libexec/qemu-kvm</emulator>
</domain>
</arch>
<features>
<cpuselection/>
<deviceboot/>
<disksnapshot default='off' toggle='no'/>
<acpi default='on' toggle='yes'/>
<apic default='on' toggle='no'/>
</features>
</guest>
</capabilities>
Example
nfvis# support virsh cpu-stats 1512149985.ROUTER
Time used by the domain:
cpu_time : 55311955404 ns
system_time : 3910000000 ns
user_time : 810000000 ns
Example
nfvis# support virsh domiflist 2
Interface Type Source Model MAC
-------------------------------------------------------
vnic2 bridge wan-net virtio 52:54:00:db:4d:10
vnic3 bridge lan-net virtio 52:54:00:8a:58:f5
Example
nfvis# support virsh dumpxml 2
<domain type='kvm' id='2'>
<name>1505948272.vmdk</name>
<uuid>285b8c3f-9f10-4e6b-b9bc-e87caaf7d877</uuid>
<memory unit='KiB'>4456448</memory>
<currentMemory unit='KiB'>4456448</currentMemory>
<vcpu placement='static' current='2'>8</vcpu>
<cputune>
<vcpupin vcpu='0' cpuset='17'/>
<vcpupin vcpu='1' cpuset='16'/>
</cputune>
<resource>
<partition>/machine</partition>
</resource>
<os>
<type arch='x86_64' machine='pc-i440fx-rhel7.0.0'>hvm</type>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<cpu mode='host-passthrough'/>
<clock offset='utc'/>
<on_poweroff>restart</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
<emulator>/usr/libexec/qemu-kvm</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2' cache='writethrough'/>
<source
file='/data/cisco/vm_lifecycle/volumes/285b8c3f-9f10-4e6b-b9bc-e87caaf7d877_0.img'/>
<backingStore type='file' index='1'>
<format type='qcow2'/>
<source file='/data/cisco/vm_lifecycle/volumes/vwlc.vmdk_0.img'/>
<backingStore/>
</backingStore>
<target dev='vda' bus='virtio'/>
<alias name='virtio-disk0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
</disk>
<controller type='usb' index='0'>
<alias name='usb'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
</controller>
<controller type='pci' index='0' model='pci-root'>
<alias name='pci.0'/>
</controller>
<interface type='bridge'>
<mac address='52:54:00:db:4d:10'/>
<source network='wan-net' bridge='wan-br'/>
<virtualport type='openvswitch'>
<parameters interfaceid='ad1fb82a-b6c3-4f39-adc0-72788820e798'/>
</virtualport>
<target dev='vnic2'/>
<model type='virtio'/>
<alias name='net0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>
<interface type='bridge'>
<mac address='52:54:00:8a:58:f5'/>
<source network='lan-net' bridge='lan-br'/>
<virtualport type='openvswitch'>
<parameters interfaceid='58070073-58ab-4ec6-92e3-81da3f7468ad'/>
</virtualport>
<target dev='vnic3'/>
<model type='virtio'/>
<alias name='net1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</interface>
<input type='mouse' bus='ps2'>
<alias name='input0'/>
</input>
<input type='tablet' bus='usb'>
<alias name='input1'/>
<address type='usb' bus='0' port='1'/>
</input>
<input type='keyboard' bus='ps2'>
<alias name='input2'/>
</input>
<graphics type='vnc' port='5901' autoport='yes' listen='0.0.0.0'>
<listen type='address' address='0.0.0.0'/>
</graphics>
<video>
<model type='cirrus' vram='16384' heads='1' primary='yes'/>
<alias name='video0'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
</video>
<memballoon model='none'/>
</devices>
<seclabel type='dynamic' model='selinux' relabel='yes'>
<label>system_u:system_r:svirt_t:s0:c726,c919</label>
<imagelabel>system_u:object_r:svirt_image_t:s0:c726,c919</imagelabel>
</seclabel>
<seclabel type='dynamic' model='dac' relabel='yes'>
<label>+107:+107</label>
<imagelabel>+107:+107</imagelabel>
</seclabel>
</domain>
Example
nfvis# support virsh iface-list
Name State MAC Address
---------------------------------------------------
eth0 active 70:db:98:70:2f:6e
int-mgmt-net-br active c6:13:e5:4d:e1:46
lan-br active 70:db:98:07:1f:35
lo active 00:00:00:00:00:00
wan-br active 70:db:98:70:2f:6e
Example
Example
nfvis# support virsh list
Id Name State
----------------------------------------------------
2 1505948272.vmdk running
3 1505947515.raw running
- 1505946928.iso shut off
- 1505948274.iso2 shut off
Example
nfvis# support virsh memory-stats name 1510771542.OTHER
Memory used:
rss: 119808 KB
Example
nfvis# support virsh net-dumpxml wan-net
<network connections='1'>
<name>wan-net</name>
<uuid>e51f65c5-fec4-4b3c-a7cd-540b748bde57</uuid>
<forward mode='bridge'/>
<bridge name='wan-br'/>
<virtualport type='openvswitch'/>
</network>
Example
nfvis# support virsh net-list
Name State Autostart Persistent
----------------------------------------------------------
int-mgmt-net active yes yes
lan-net active yes yes
wan-net active yes yes
Example
nfvis# support virsh net-info wan-net
Name: wan-net
UUID: e51f65c5-fec4-4b3c-a7cd-540b748bde57
Active: yes
Persistent: yes
Autostart: yes
Bridge: wan-br
Example
nfvis# support virsh nodecpustats
usage: 0.1%
user: 0.0%
system: 0.0%
idle: 100.0%
iowait: 0.0%
Example
nfvis# support virsh pool-list
Name State Autostart
-------------------------------------------
cisco_datastore1 active no
Example
nfvis# support virsh pool-dumpxml cisco_datastore1
<pool type='dir'>
<name>cisco_datastore1</name>
<uuid>51487524-16fe-40c9-a598-6384c914e191</uuid>
<capacity unit='bytes'>2304488226816</capacity>
<allocation unit='bytes'>256696770560</allocation>
<available unit='bytes'>2047791456256</available>
<source>
</source>
<target>
<path>/data/cisco/vm_lifecycle/volumes</path>
<permissions>
<mode>0755</mode>
<owner>0</owner>
<group>0</group>
<label>system_u:object_r:etc_runtime_t:s0</label>
</permissions>
</target>
</pool>
Example
nfvis# support virsh sys-info
Sys info: <sysinfo type='smbios'>
<bios>
<entry name='vendor'>Cisco Systems, Inc.</entry>
<entry name='version'>C220M4.2.0.13g.0.1113162259</entry>
<entry name='date'>11/13/2016</entry>
<entry name='release'>5.11</entry>
</bios>
<system>
<entry name='manufacturer'>Cisco Systems Inc</entry>
<entry name='product'>UCSC-C220-M4S</entry>
<entry name='version'>A0</entry>
<entry name='serial'>FCH2110V0DX</entry>
<entry name='uuid'>EB7C9CE9-9DF9-3142-898B-C84A16B10706</entry>
<entry name='sku'>Not Specified</entry>
<entry name='family'>Not Specified</entry>
</system>
<baseBoard>
<entry name='manufacturer'>Cisco Systems Inc</entry>
<entry name='product'>UCSC-C220-M4S</entry>
<entry name='version'>74-12419-02</entry>
<entry name='serial'>FCH2108JLC4</entry>
<entry name='asset'>Unknown</entry>
<entry name='location'>Not Specified</entry>
</baseBoard>
<processor>
<entry name='socket_destination'>CPU1</entry>
<entry name='type'>Central Processor</entry>
<entry name='family'>Xeon</entry>
<entry name='manufacturer'>Intel(R) Corporation</entry>
<entry name='signature'>Type 0, Family 6, Model 79, Stepping 1</entry>
<entry name='version'>Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz</entry>
<entry name='external_clock'>100 MHz</entry>
<entry name='max_speed'>4000 MHz</entry>
<entry name='status'>Populated, Enabled</entry>
<entry name='serial_number'>Not Specified</entry>
<entry name='part_number'>Not Specified</entry>
</processor>
<processor>
<entry name='socket_destination'>CPU2</entry>
<entry name='type'>Central Processor</entry>
<entry name='family'>Xeon</entry>
<entry name='manufacturer'>Intel(R) Corporation</entry>
<entry name='signature'>Type 0, Family 6, Model 79, Stepping 1</entry>
<entry name='version'>Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz</entry>
<entry name='external_clock'>100 MHz</entry>
<entry name='max_speed'>4000 MHz</entry>
<entry name='status'>Populated, Enabled</entry>
<entry name='serial_number'>Not Specified</entry>
<entry name='part_number'>Not Specified</entry>
</processor>
<memory_device>
<entry name='size'>16384 MB</entry>
<entry name='form_factor'>DIMM</entry>
<entry name='locator'>DIMM_A1</entry>
<entry name='bank_locator'>NODE 0 CHANNEL 0 DIMM 0</entry>
<entry name='type'>DDR4</entry>
<entry name='type_detail'>Registered (Buffered)</entry>
<entry name='speed'>2400 MHz</entry>
<entry name='manufacturer'>0xCE00</entry>
<entry name='serial_number'>34E462C9</entry>
<entry name='part_number'>M393A2K40BB1-CRC</entry>
</memory_device>
<memory_device>
<entry name='size'>16384 MB</entry>
<entry name='form_factor'>DIMM</entry>
<entry name='locator'>DIMM_B1</entry>
<entry name='bank_locator'>NODE 0 CHANNEL 1 DIMM 0</entry>
<entry name='type'>DDR4</entry>
<entry name='type_detail'>Registered (Buffered)</entry>
<entry name='speed'>2400 MHz</entry>
<entry name='manufacturer'>0xCE00</entry>
<entry name='serial_number'>34E4536B</entry>
<entry name='part_number'>M393A2K40BB1-CRC</entry>
</memory_device>
<memory_device>
<entry name='size'>16384 MB</entry>
<entry name='form_factor'>DIMM</entry>
<entry name='locator'>DIMM_C1</entry>
<entry name='bank_locator'>NODE 0 CHANNEL 2 DIMM 0</entry>
<entry name='type'>DDR4</entry>
<entry name='type_detail'>Registered (Buffered)</entry>
<entry name='speed'>2400 MHz</entry>
<entry name='manufacturer'>0xCE00</entry>
<entry name='serial_number'>34E4539A</entry>
<entry name='part_number'>M393A2K40BB1-CRC</entry>
</memory_device>
<memory_device>
<entry name='size'>16384 MB</entry>
<entry name='form_factor'>DIMM</entry>
<entry name='locator'>DIMM_D1</entry>
<entry name='bank_locator'>NODE 0 CHANNEL 3 DIMM 0</entry>
<entry name='type'>DDR4</entry>
<entry name='type_detail'>Registered (Buffered)</entry>
<entry name='speed'>2400 MHz</entry>
<entry name='manufacturer'>0xCE00</entry>
<entry name='serial_number'>34E4544B</entry>
<entry name='part_number'>M393A2K40BB1-CRC</entry>
</memory_device>
<memory_device>
<entry name='size'>16384 MB</entry>
<entry name='form_factor'>DIMM</entry>
<entry name='locator'>DIMM_E1</entry>
<entry name='bank_locator'>NODE 1 CHANNEL 0 DIMM 0</entry>
<entry name='type'>DDR4</entry>
<entry name='type_detail'>Registered (Buffered)</entry>
<entry name='speed'>2400 MHz</entry>
<entry name='manufacturer'>0xCE00</entry>
<entry name='serial_number'>34E468CE</entry>
<entry name='part_number'>M393A2K40BB1-CRC</entry>
</memory_device>
<memory_device>
<entry name='size'>16384 MB</entry>
<entry name='form_factor'>DIMM</entry>
<entry name='locator'>DIMM_F1</entry>
<entry name='bank_locator'>NODE 1 CHANNEL 1 DIMM 0</entry>
<entry name='type'>DDR4</entry>
<entry name='type_detail'>Registered (Buffered)</entry>
<entry name='speed'>2400 MHz</entry>
<entry name='manufacturer'>0xCE00</entry>
<entry name='serial_number'>34E44191</entry>
<entry name='part_number'>M393A2K40BB1-CRC</entry>
</memory_device>
<memory_device>
<entry name='size'>16384 MB</entry>
<entry name='form_factor'>DIMM</entry>
<entry name='locator'>DIMM_G1</entry>
<entry name='bank_locator'>NODE 1 CHANNEL 2 DIMM 0</entry>
<entry name='type'>DDR4</entry>
<entry name='type_detail'>Registered (Buffered)</entry>
<entry name='speed'>2400 MHz</entry>
<entry name='manufacturer'>0xCE00</entry>
<entry name='serial_number'>34E46927</entry>
<entry name='part_number'>M393A2K40BB1-CRC</entry>
</memory_device>
<memory_device>
<entry name='size'>16384 MB</entry>
<entry name='form_factor'>DIMM</entry>
<entry name='locator'>DIMM_H1</entry>
<entry name='bank_locator'>NODE 1 CHANNEL 3 DIMM 0</entry>
<entry name='type'>DDR4</entry>
<entry name='type_detail'>Registered (Buffered)</entry>
<entry name='speed'>2400 MHz</entry>
<entry name='manufacturer'>0xCE00</entry>
<entry name='serial_number'>34E468D0</entry>
<entry name='part_number'>M393A2K40BB1-CRC</entry>
</memory_device>
</sysinfo>
Example
Example
nfvis# support virsh vol-list cisco_datastore1
Name Path
------------------------------------------------------------------------------
24ef7a32-4490-49ca-bbc8-c9a01ec20ae4_0.img
/data/cisco/vm_lifecycle/volumes/24ef7a32-4490-49ca-bbc8-c9a01ec20ae4_0.img
285b8c3f-9f10-4e6b-b9bc-e87caaf7d877_0.img
/data/cisco/vm_lifecycle/volumes/285b8c3f-9f10-4e6b-b9bc-e87caaf7d877_0.img
5db7f935-501b-4606-935b-bf650fefdc02_0.img
/data/cisco/vm_lifecycle/volumes/5db7f935-501b-4606-935b-bf650fefdc02_0.img
d4a8df33-3bc1-43db-9a82-b96dc8429fb3_0.img
/data/cisco/vm_lifecycle/volumes/d4a8df33-3bc1-43db-9a82-b96dc8429fb3_0.img
fattest_0.img /data/cisco/vm_lifecycle/volumes/fattest_0.img
TinyLinux.qcow2_0.img /data/cisco/vm_lifecycle/volumes/TinyLinux.qcow2_0.img
vwlc.vmdk_0.img /data/cisco/vm_lifecycle/volumes/vwlc.vmdk_0.img
Example
nfvis# support ovs all-info
support ovs vsctl show
c23984a8-7379-445d-9ca3-0980bf1db317
Bridge wan-br
Port "vnic4"
Interface "vnic4"
Port wan-br
Interface wan-br
type: internal
Port "vnic2"
Interface "vnic2"
Port "eth0"
Interface "eth0"
Port "vnic9"
Interface "vnic9"
Port "vnic0"
Interface "vnic0"
Bridge int-mgmt-net-br
Port "vnic3"
Interface "vnic3"
Port int-mgmt-net-br
Interface int-mgmt-net-br
type: internal
Bridge lan-br
Port lan-br
Interface lan-br
type: internal
Port "eth6"
Interface "eth6"
Port "eth7"
Interface "eth7"
Port "eth4"
Interface "eth4"
Port "eth2"
Interface "eth2"
Port "eth1"
Interface "eth1"
Port "vnic8"
Interface "vnic8"
Port "eth5"
Interface "eth5"
Port "vnic1"
Interface "vnic1"
Port "eth3"
Interface "eth3"
ovs_version: "2.5.2"
support ovs vsctl list-br
int-mgmt-net-br
lan-br
wan-br
...
Example
nfvis# support ovs appctl fdb-show wan-br
port VLAN MAC Age
1 0 00:24:14:de:0f:b0 275
1 0 00:19:2f:bc:f9:40 271
1 0 b4:14:89:cb:7a:18 252
1 0 a8:9d:21:04:2c:a1 228
1 0 c4:71:fe:60:51:40 211
1 0 00:d0:c9:bd:b1:ca 187
1 0 00:0c:29:25:71:45 176
1 0 0c:4d:e9:c7:14:eb 176
1 0 ac:87:a3:01:5d:38 175
1 0 00:1a:a1:21:a9:08 172
1 0 00:17:08:50:27:9b 153
1 0 00:50:56:87:24:11 150
1 0 00:1a:a1:df:48:70 143
1 0 00:6b:f1:25:13:f0 139
1 0 00:78:88:50:95:40 139
1 0 00:03:ba:85:a1:16 123
1 0 00:11:92:fa:07:d1 123
1 0 50:57:a8:e1:5f:48 122
1 0 70:db:98:c3:fb:00 110
1 0 a8:9d:21:f4:74:10 110
1 0 50:3d:e5:9d:5a:a8 107
1 0 00:17:95:42:67:e0 106
1 0 00:50:56:8b:01:37 105
1 0 a8:9d:21:ce:de:50 81
1 0 fa:9d:46:a0:61:ce 80
1 0 6c:ae:8b:15:f3:c6 61
1 0 4c:4e:35:44:25:ca 59
1 0 80:e0:1d:37:1c:68 54
1 0 00:f2:8b:c3:97:70 52
1 0 a2:6e:e7:10:a1:bb 50
1 0 00:6b:f1:25:13:fc 50
1 0 44:2b:03:16:db:83 50
1 0 80:e0:1d:36:e3:7d 50
1 0 d8:b1:90:40:7a:0f 49
1 0 70:db:98:70:0a:d9 47
1 0 a8:9d:21:93:65:06 46
1 0 bc:f1:f2:da:f9:41 40
1 0 5c:f3:fc:2b:2d:79 35
1 0 70:db:98:6f:fb:c0 33
1 0 ce:b2:05:54:47:82 32
1 0 84:b8:02:b8:5a:fc 32
1 0 00:f2:8b:c3:97:7c 32
1 0 10:05:ca:9d:8a:21 31
1 0 d4:6d:50:cf:9e:8d 31
1 0 84:b8:02:5b:cd:d9 29
1 0 00:1e:be:10:81:9a 29
1 0 80:e0:1d:37:2a:80 27
6 0 52:54:00:82:95:43 26
1 0 f8:66:f2:da:0a:80 26
1 0 da:eb:ea:3f:ed:04 25
1 0 50:3d:e5:17:b4:00 23
1 0 e4:c7:22:f0:16:f9 16
1 0 a8:9d:21:ce:de:4b 15
1 0 00:1d:70:7e:5d:80 14
1 0 f8:0b:cb:d6:a6:d5 14
1 0 00:6b:f1:25:13:7c 14
1 0 70:db:98:6f:fb:bb 14
1 0 d4:6d:50:cf:c1:81 13
1 0 80:e0:1d:36:e3:82 13
1 0 a8:9d:21:93:65:02 11
1 0 00:b0:64:fd:06:87 11
1 0 d4:6d:50:cf:c1:86 11
1 0 70:db:98:c3:fa:80 10
1 0 70:db:98:c3:f9:68 10
9 0 52:54:00:85:8a:7a 10
1 0 bc:f1:f2:da:f9:04 9
1 0 00:0c:29:3d:50:1e 7
1 0 00:0c:29:3d:50:0a 7
1 0 52:54:00:54:78:e4 7
1 0 d6:b2:96:90:eb:25 6
1 0 84:b8:02:b8:5a:f7 5
1 0 00:6b:f1:25:13:fd 5
1 0 00:0d:60:84:1e:c0 5
1 0 00:25:45:0e:c3:c0 5
1 0 00:05:73:a0:00:08 2
1 0 00:25:b4:47:44:00 0
1 0 00:09:e6:00:39:d6 0
1 0 68:bc:0c:5b:cb:01 0
1 0 00:00:0c:9f:f0:06 0
LOCAL 0 70:db:98:70:2f:6e 0
1 0 3c:ce:73:da:60:00 0
1 0 00:05:73:a0:00:01 0
1 0 00:00:0c:9f:f0:15 0
Example
nfvis# support ovs dpctl show
system@ovs-system:
lookups: hit:9883843 missed:715875 lost:0
flows: 27
masks: hit:38834243 total:4 hit/pkt:3.66
port 0: ovs-system (internal)
port 1: eth4
port 2: eth5
port 3: eth3
port 4: eth1
port 5: eth7
port 6: eth6
port 7: lan-br (internal)
port 8: eth2
port 9: eth0
port 10: wan-br (internal)
port 11: int-mgmt-net-br (internal)
port 12: vnic0
port 13: vnic1
port 14: vnic2
port 15: vnic3
port 16: vnic4
port 17: vnic5
port 18: vnic6
port 19: vnic7
Example
nfvis# support ovs ofctl dump-ports wan-br
OFPST_PORT reply (xid=0x2): 6 ports
port 10: rx pkts=0, bytes=0, drop=0, errs=0, frame=0, over=0, crc=0
tx pkts=513, bytes=80488, drop=5259654, errs=0, coll=0
port 8: rx pkts=0, bytes=0, drop=0, errs=0, frame=0, over=0, crc=0
tx pkts=2280, bytes=365070, drop=6185138, errs=0, coll=0
port 6: rx pkts=2315, bytes=97662, drop=0, errs=0, frame=0, over=0, crc=0
tx pkts=3153581, bytes=501088395, drop=31404, errs=0, coll=0
port 1: rx pkts=14451444, bytes=3479151791, drop=0, errs=0, frame=0, over=0, crc=0
tx pkts=1450836, bytes=167179629, drop=0, errs=0, coll=0
port LOCAL: rx pkts=8318452, bytes=11458196810, drop=6920, errs=0, frame=0, over=0, crc=0
Example
nfvis# support ovs ofctl dump-ports-desc wan-br
OFPST_PORT_DESC reply (xid=0x2):
1(eth0): addr:70:db:98:70:2f:6e
config: 0
state: 0
current: 1GB-FD COPPER AUTO_NEG
advertised: 10MB-HD 10MB-FD 100MB-HD 100MB-FD 1GB-FD COPPER AUTO_NEG
supported: 10MB-HD 10MB-FD 100MB-HD 100MB-FD 1GB-FD COPPER AUTO_NEG AUTO_PAUSE
speed: 1000 Mbps now, 1000 Mbps max
6(vnic2): addr:fe:54:00:82:95:43
config: 0
state: 0
current: 10MB-FD COPPER
speed: 10 Mbps now, 0 Mbps max
8(vnic1): addr:fe:54:00:3a:f1:c0
config: 0
state: 0
current: 10MB-FD COPPER
speed: 10 Mbps now, 0 Mbps max
9(vnic3): addr:fe:54:00:85:8a:7a
config: 0
state: 0
current: 10MB-FD COPPER
speed: 10 Mbps now, 0 Mbps max
10(vnic6): addr:fe:54:00:e4:a3:3a
config: 0
state: 0
current: 10MB-FD COPPER
speed: 10 Mbps now, 0 Mbps max
LOCAL(wan-br): addr:70:db:98:70:2f:6e
config: 0
state: 0
speed: 0 Mbps now, 0 Mbps max
Example
nfvis# support ovs vsctl list-br
int-mgmt-net-br
lan-br
wan-br
Example
nfvis# support ovs vsctl list interface wan-br
_uuid : be31801b-9729-41c4-8053-52534a59a9c4
admin_state : up
bfd : {}
bfd_status : {}
cfm_fault : []
cfm_fault_status : []
cfm_flap_count : []
cfm_health : []
cfm_mpid : []
cfm_remote_mpids : []
cfm_remote_opstate : []
duplex : []
external_ids : {}
ifindex : 12
ingress_policing_burst: 0
ingress_policing_rate: 0
lacp_current : []
link_resets : 1
link_speed : []
link_state : up
mac : []
mac_in_use : "70:db:98:70:2f:6e"
mtu : 1500
name : wan-br
ofport : 65534
ofport_request : []
options : {}
other_config : {}
statistics : {collisions=0, rx_bytes=11457008582, rx_crc_err=0, rx_dropped=6907,
rx_errors=0, rx_frame_err=0,
rx_over_err=0, rx_packets=8310154, tx_bytes=164896735, tx_dropped=0, tx_errors=0,
tx_packets=1415893}
status : {driver_name=openvswitch}
type : internal
Example
nfvis# support ovs vsctl list-ports wan-br
eth0
vnic1
vnic2
vnic3
vnic6
Example
nfvis# support ovs vsctl show
c9c52c5d-d0f3-4d8d-9ee2-ebd9728b83a6
Bridge wan-br
Port "vnic2"
Interface "vnic2"
Port "vnic3"
Interface "vnic3"
Port wan-br
Interface wan-br
type: internal
Port "eth0"
Interface "eth0"
Port "vnic6"
Interface "vnic6"
Port "vnic1"
Interface "vnic1"
Bridge int-mgmt-net-br
Port "vnic0"
Interface "vnic0"
Port int-mgmt-net-br
Interface int-mgmt-net-br
type: internal
Port "vnic5"
Interface "vnic5"
Bridge lan-br
Port "vnic4"
Interface "vnic4"
Port "eth3"
Interface "eth3"
Port "eth4"
Interface "eth4"
Port lan-br
Interface lan-br
type: internal
Port "eth2"
Interface "eth2"
Port "eth7"
Interface "eth7"
Port "eth1"
Interface "eth1"
Port "eth5"
Interface "eth5"
Port "vnic7"
Interface "vnic7"
Port "eth6"
Interface "eth6"
ovs_version: "2.3.2"