Top Cisco Nexus Switches Interview Questions Part – 2
How Many Ospf Processes Can Be Run In A Virtual Device Context (vdc)?
There can be up to four (4) instances of OSPFv2 in a VDC.
Which Nexus 7000 Modules Support Fibre Channel Over Ethernet (fcoe)?
The Cisco Nexus 7000 Series 32-Port 1 and 10 Gigabit Ethernet Module support FCoE. The part number of the product is N7K-F132XP-15.
On A Nexus, Is The Metric-type Keyword Not Available In The “default-information Originate” Command?
On a Nexus, use a route-map command with a set clause of metric-type type-[½] in order to have the same functionality as in IOS using the default-information originate always metric-type [½] command.
For example:
switch(config)#route-map STAT-OSPF, permit, sequence 10
switch(config-route-map)#match interface ethernet 1/2
switch(config-route-map)#set metric-type {external | internal | type-1 | type-2}
How Do I Redistribute Connected Routes Into An Ospf Instance On A Nexus 7010 With A Defined Metric?
In NX-OS, a route-map is always required when redistributing routes into an OSPF instance, and you will also use this route-map to set the metric. Further, subnet redistribution is by default, so you do not have to add the subnets keyword.
For example:
switch(config)#access-list 101 permit ip any
switch(config)#access-list 101 permit ip any
switch(config)#access-list 101 permit ip any
switch(config)#access-list 101 deny any
!
Router(config)# route-map direct2ospf permit 10
Router(config-route-map)# match ip address 101
Router(config-route-map)# set metric
Router(config-route-map)# set metric-type type-1
!
switch(config)#router ospf 1
switch(config-router)#redistribute direct route-map direct2ospf
What Is The Equivalent Nx-os Command For The “ip Multicast-routing” Ios Command, And Does The Nexus 7000 Support Pim-sparse Mode?
The command is feature pim. In NX-OS, multicast is enabled only after enabling the PIM or PIM6 feature on each router and then enabling PIM or PIM6 sparse mode on each interface that you want to participate in multicast.
For example:
switch(config)#feature pim
switch(config)#interface Vlan[536]
switch(config-if)#ip pim sparse-mode
When I Issue The “show Ip Route Bgp” Command, I See My Routes Being Learned Via Ospf And Bgp. How Can I Verify On The Nx-os Which One Will Always Be Used And Which One Is A Backup?
Here is what is received:
Nexus_7010#show ip route bgp
IP Route Table for VRF “default”
‘*’ denotes best ucast next-hop
‘**’ denotes best mcast next-hop
‘[x/y]’ denotes [preference/metric]
172.20.62.0/23, ubest/mbest: 1/0
*via 10.194.160.2, [20/0], 18:53:35, bgp-[AS-Number], internal, tag [Number]
via 10.194.16.5, Vlan116, [110/1043], 18:43:51, ospf-1, intra
172.20.122.0/23, ubest/mbest: 1/0
*via 10.194.160.2, [20/0], 18:53:35, bgp-[AS-Number], internal, tag [Number]
via 10.194.16.5, Vlan116, [110/1041], 18:43:51, ospf-1, intra
By default, BGP selects only a single best path and does not perform load balancing. As a result, the route marked with the * will always be used, unless it goes down, at which point any remaining routes will become the preferred path.
How Do I Avoid Receiving The “failed To Process Kickstart Image. Pre-upgrade Check Failed” Error Message When Upgrading The Image On A Nexus 7000 Series Switch?
One potential reason for receiving this error message is if the file name specified is not correct.
For example:
switch#install all kickstart bootflash:n7000-sl-kickstart.5.1.1a.bin system
bootflash:n7000-sl-dk9.5.1.1a.bin
In this example, the file name contains “sl” (lowercase letter l) instead of “s1” (number 1).
How Can I Avoid Receiving The “configuration Does Not Match The Port Capability” Error Message When Enabling “switchport Mode Fex-fabric”?
This error message is generated because the port is not FEX capable:
N7K-2(config)#interface ethernet 9/5
N7K-2(config-if)#switchport mode fex-fabric
ERROR:
Ethernet9/5:
Configuration does not match the port capability
How Do I Enable/disable Logging Link Status Per Port Basis On A Nexus 7000 Series Switch?
All interface link status (up/down) messages are logged by default. Link status events can be configured globally or per interface. The interface command enables link status logging messages for a specific interface.
For example:
N7k(config)#interface ethernet x/x
N7k(config-if)#logging event port link-status
On A Nexus 7000 Running Nx-os 5.1(3), Can The Decnet Be Bridged On A Vlan?
All of the Nexus platforms support passing DecNet frames through the device from a layer-2 perspective. However, there is no support for routing DecNet on the Nexus.
Can A Nexus 7000 Be A Dhcp Server And Can It Relay Dhcp Requests To Different Dhcp Servers Per Vlan?
The Nexus 7000 does not support a DHCP server, but it does support DHCP relay. For relay, use the ip dhcp relay address x.x.x.x interface command.