Published On: August 6ᵗʰ, 2019 02:05
Cisco Enterprise Network Function Virtualization Infrastructure Software Command Reference
Networks and Bridges Commands
- bridge
- bridges bridge
- show running-config bridges
- show system networks
- show system packages
- ping
- ping-ipv6
- traceroute
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.
Syntax Description
Command Modes
Session configuration (config-session-2)#
Command History
| Release | Modification |
|---|---|
| 3.5.1 |
This command was introduced. |
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.
Examples
The following example shows how to attach a SPAN session to a bridge:
nfvis(config)# monitor session 2 nfvis(config-session-2)# bridge lan-br
bridges bridge
show running-config bridges
show system networks
To display the information of the networks in the system, use the show system networks command in privileged EXEC mode.
Syntax Description
| network network-name |
(Optional) Name of the network. |
| bridge |
(Optional) The bridge for the network. |
| port |
(Optional) The port for the network. |
| type |
(Optional) The type of network. |
Command History
show system packages
To display information on the packages in the system, use the show system packages command in privileged EXEC mode.
Syntax Description
| package package-name |
(Optional) Name of the package. |
| owner |
(Optional) Owner of the package. |
| version |
(Optional) Version of the package. |
Command History
Examples
nfvis# show system packages NAME VERSION OWNER -------------------------------------------------------------------- GeoIP.x86_64 1.5.0-9.el7 @anaconda NetworkManager.x86_64 1:1.0.6-27.el7 @anaconda NetworkManager-libnm.x86_64 1:1.0.6-27.el7 @anaconda NetworkManager-team.x86_64 1:1.0.6-27.el7 @anaconda NetworkManager-tui.x86_64 1:1.0.6-27.el7 @anaconda Twisted.x86_64 13.1.0-1 @esc-lite abrt.x86_64 2.1.11-36.el7.centos @anaconda abrt-addon-ccpp.x86_64 2.1.11-36.el7.centos @anaconda abrt-addon-kerneloops.x86_64 2.1.11-36.el7.centos @anaconda
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]
Syntax Description
| host-ip-address |
Specifies the address of the IPv4 host. |
| host-name |
Specifies the name of the IPv4 host. |
| count count |
Specifies the number of ping packets to be sent. |
| pktsize pktsize |
Specifies the packet size. The default is 64 bytes. |
| interval interval |
Specifies the number of seconds to wait between requests. |
| ttl ttl |
Specifies the hop limit. |
Command History
Examples
nfvis(config)# ping count 5 interval 2 pktsize 64 ttl 64 192.0.2.252 PING 192.0.2.252 (192.0.2.252) 64(92) bytes of data. 72 bytes from 192.0.2.252: icmp_seq=1 ttl=64 time=0.050 ms 72 bytes from 192.0.2.252: icmp_seq=2 ttl=64 time=0.041 ms 72 bytes from 192.0.2.252: icmp_seq=3 ttl=64 time=0.042 ms 72 bytes from 192.0.2.252: icmp_seq=4 ttl=64 time=0.033 ms 72 bytes from 192.0.2.252: icmp_seq=5 ttl=64 time=0.033 ms --- 192.0.2.252 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 8000ms rtt min/avg/max/mdev = 0.033/0.039/0.050/0.010 ms
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]
Syntax Description
| host-ip-address |
Specifies the address of the IPv6 host. |
| host-name |
Specifies the name of the IPv6 host. |
| count count |
Specifies the number of ping packets to be sent. |
| pktsize pktsize |
Specifies the packet size. The default is 64 bytes. |
| interval interval |
Specifies the number of seconds to wait between requests. |
| ttl ttl |
Specifies the hop limit. |
Command History
Examples
nfvis(config)# ping-ipv6 count 6 interval 2 pktsize 64 ttl 64 fe80::9c76:87ff:feba:5d40 PING fe80::9c76:87ff:feba:5d40(fe80::9c76:87ff:feba:5d40) 64 data bytes 72 bytes from fe80::9c76:87ff:feba:5d40%lan-br: icmp_seq=1 ttl=64 time=0.060 ms 72 bytes from fe80::9c76:87ff:feba:5d40%lan-br: icmp_seq=2 ttl=64 time=0.045 ms 72 bytes from fe80::9c76:87ff:feba:5d40%lan-br: icmp_seq=3 ttl=64 time=0.045 ms 72 bytes from fe80::9c76:87ff:feba:5d40%lan-br: icmp_seq=4 ttl=64 time=0.069 ms 72 bytes from fe80::9c76:87ff:feba:5d40%lan-br: icmp_seq=5 ttl=64 time=0.051 ms 72 bytes from fe80::9c76:87ff:feba:5d40%lan-br: icmp_seq=6 ttl=64 time=0.039 ms --- fe80::9c76:87ff:feba:5d40 ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 10000ms rtt min/avg/max/mdev = 0.039/0.051/0.069/0.012 ms
traceroute
To discover the routes that packets take when traveling to a destination, use the traceroute command in privileged EXEC mode.
traceroute { ip-address | host-name } interface interface-name [ source source-ip-address] [ max max] [ min min] [ probes probes] [ waittime waittime]
Syntax Description
| ip-address |
Specifies the destination IP address. |
| host-name |
Specifies the destination host name. |
| interface interface-name |
Specifies a source network interface. |
| source source-ip-address |
(Optional) Specifies a source IP address. |
| max max |
(Optional) Specifies the maximum time-to-live (TTL) used in the outgoing probe packets. The default value is 30. |
| min min |
(Optional) Specifies the minimum TTL used in the first outgoing probe packet. The default value is 1. |
| probes probes |
(Optional) Specifies the number of probes to be sent at each TTL level. The default value is 3. |
| waittime waittime |
(Optional) Specifies the probe timeout in seconds. The default value is 1. |