...
A Nexus 9000 device running NX-OS software release 9.3(3) will display a VLAN SVI interface's IP address on the same line as the interface's description in the output of the "show interface" command: N9K# show run interface vlan3600 !Command: show running-config interface Vlan3600 !Running configuration last done at: Fri Feb 21 15:08:13 2020 !Time: Mon Mar 2 07:41:47 2020 version 9.3(3) Bios:version 05.39 interface Vlan3600 description VPC-Peer-Link SVI no shutdown mtu 9216 bfd interval 50 min_rx 50 multiplier 3 bfd echo-rx-interval 50 bfd ipv4 interval 50 min_rx 50 multiplier 3 bfd ipv6 interval 50 min_rx 50 multiplier 3 no ip redirects ip address 192.0.2.1/30 no ipv6 redirects ip ospf network point-to-point ip router ospf UNDERLAY area 0.0.0.0 ip pim sparse-mode N9K# show interface vlan3600 Vlan3600 is up, line protocol is up, autostate enabled Hardware is EtherSVI, address is 00de.fbfb.50e7 Description: VPC-Peer-Link SVI Internet Address is 192.0.2.1/30 <<< MTU 9216 bytes, BW 1000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive not supported ARP type: ARPA Last clearing of "show interface" counters never L3 in Switched: ucast: 0 pkts, 0 bytes L3 out Switched: ucast: 0 pkts, 0 bytes Alternatively, a VLAN SVI interface that does not have an IP address configured will show interface MTU, bandwidth, and delay characteristics on the same line as the interface's description: N9K# show running-config interface vlan3600 !Command: show running-config interface Vlan3600 !Running configuration last done at: Mon Mar 2 07:47:00 2020 !Time: Mon Mar 2 07:53:32 2020 version 9.3(3) Bios:version 05.39 interface Vlan3600 description VPC-Peer-Link SVI no shutdown mtu 9216 bfd interval 50 min_rx 50 multiplier 3 bfd echo-rx-interval 50 bfd ipv4 interval 50 min_rx 50 multiplier 3 bfd ipv6 interval 50 min_rx 50 multiplier 3 no ip redirects no ipv6 redirects ip ospf network point-to-point ip router ospf UNDERLAY area 0.0.0.0 ip pim sparse-mode N9K# show interface vlan 3600 Vlan3600 is up, line protocol is up, autostate enabled Hardware is EtherSVI, address is 00de.fbfb.50e7 Description: VPC-Peer-Link SVI MTU 9216 bytes, BW 1000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive not supported ARP type: ARPA Last clearing of "show interface" counters never L3 in Switched: ucast: 0 pkts, 0 bytes L3 out Switched: ucast: 0 pkts, 0 bytes
1. Nexus 9000 device running NX-OS software release 9.3(3) 2. VLAN SVI interfaces are \configured with a description
Remove the VLAN SVI interface's description configuration to restore the output to normal: N9K# configure Enter configuration commands, one per line. End with CNTL/Z. N9K(config)# interface vlan 3600 N9K(config-if)# no description N9K(config-if)# end N9K# N9K# show run interface vlan 3600 !Command: show running-config interface Vlan3600 !Running configuration last done at: Mon Mar 2 07:54:44 2020 !Time: Mon Mar 2 07:54:47 2020 version 9.3(3) Bios:version 05.39 interface Vlan3600 no shutdown mtu 9216 bfd interval 50 min_rx 50 multiplier 3 bfd echo-rx-interval 50 bfd ipv4 interval 50 min_rx 50 multiplier 3 bfd ipv6 interval 50 min_rx 50 multiplier 3 no ip redirects ip address 192.0.2.1/30 no ipv6 redirects ip ospf network point-to-point ip router ospf UNDERLAY area 0.0.0.0 ip pim sparse-mode N9K# show interface vlan3600 Vlan3600 is up, line protocol is up, autostate enabled Hardware is EtherSVI, address is 00de.fbfb.50e7 Internet Address is 192.0.2.1/30 MTU 9216 bytes, BW 1000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive not supported ARP type: ARPA Last clearing of "show interface" counters never L3 in Switched: ucast: 0 pkts, 0 bytes L3 out Switched: ucast: 0 pkts, 0 bytes
This defect only impacts VLAN SVI interfaces. Physical interfaces, loopback interfaces, and other Layer 3 interfaces are not impacted by this issue. This defect is particularly impactful to network automation software that "screen scrapes" CLI output. Network automation software may incorrectly consider the IP address, MTU, bandwidth, or delay characteristics of VLAN SVI interfaces to be part of the interface description as a direct result of this issue. Furthermore, network automation software may throw an exception or return empty output as a direct result of this issue if they are unable to identify the aforementioned VLAN SVI interface characteristics.