cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5316
Views
7
Helpful
44
Replies

ip routing command doesn't work on cisco 9000v

nsom
Level 1
Level 1

Hi I am trying to enable routing on cisco 9000v for intervlan routing betwen two vlans.
I am trying to enable routing as explained in different articles using ip routing command however this command doesn't work as there are other options that need to be executed post this command and I ma not sure what to use. Please suggest
```

switch(config)# ip routing

event-history   internal        multicast       

switch(config)# ip routing

                           ^

% Incomplete command at '^' marker.

```

44 Replies 44

but this example use Catalyst. For Catalyst you just need to enable ip routing, create vlans, interface vlan with IP address and done.

Does that mean I would not be able to achieve what I am trying to achieve using a single cisco 9000v switch and two hosts trying to ping each other from different vlans?
Will these require additional routers or the samer switch can be used as a router, similar to what is done in the video for the catalyst switch?

I believe you can achieve for sure. But the way to do this is different. Catalyst is much more simple as you could see on the video you shared.

 Nexus is much mode complex. Did you try to follow the instruction of the video I shared?

This is from Nexus 9000 documment:

 

"You can route across VLAN interfaces to provide Layer 3 inter-VLAN routing by configuring a VLAN interface for each VLAN that you want to route traffic to and assigning an IP address on the VLAN interface. For more information about IP addresses and IP routing, see the Cisco Nexus 9000 Series NX-OS Unicast Routing Configuration Guide.

The following figure shows two hosts connected to two VLANs on a device. You can configure VLAN interfaces for each VLAN that allows Host 1 to communicate with Host 2 using IP routing between the VLANs. VLAN 1 communicates at Layer 3 over VLAN interface 1 and VLAN 10 communicates at Layer 3 over VLAN interface 10.

Figure 2. Connecting Two VLANs with VLAN interfaces

FlavioMiranda_2-1685287498491.jpeg

 

Changing VRF Membership for an Interface

When you enter the vrf member command under an interface, you receive an alert regarding the deletion of interface configurations and to notify the clients/listeners (such as CLI-Server) to delete configurations with respect to the interface.

Entering the system vrf-member-change retain-l3-config command (7.0(3)I4(1) and later) enables the retention of the Layer 3 configuration when the VRF member changes on the interface. It does this by sending notification to the clients/listeners to store (buffer) the existing configurations, delete the configurations from the old vrf context, and reapply the stored configurations under the new VRF context.

FlavioMiranda_3-1685287498491.gif

 

Note

When the system vrf-member-change retain-l3-config command is enabled, the Layer 3 configuration is not deleted and remains stored (buffered). When this command is not enabled (default mode), the Layer 3 configuration is not retained when the VRF member changes.


You can disable the retention of the Layer 3 configuration with the no system vrf-member-change retain-l3-config command. In this mode, the Layer 3 configuration is not retained when the VRF member changes."

Th video talks about the setup from the previos one where I guess the TEPS,VNIS are configured, I need some time to have an understanding of what's going in and then try to perform the same in my switch, will keep you posted, thanks for the pointers

Hi Flavio
the in the article above in option 
Connecting Two VLANs with VLAN interfaces

the figure it shows is quite basic, and I have done exactly what is mentioned in the figure, i.e creating two vlans assigning ip addreses to them assign these two interfaces making them access ports,It's not clear from the doc whether that's what was needed to perform this, and rest of the information is additional resources or the entire doc has to be gone through for intervlan routing to work.

I agree with you.

Did you try to use extend ping just make sure the problem is not the host only?

 Like ping the host and use source simlulating the esxi?

Hi Flavio,
ping is working from the host when I ping to other host in same subnet or the default gateway vlan belonging to the same host.
For example

[root@esxi-nested-04:~] ping 192.168.15.1

PING 192.168.15.1 (192.168.15.1): 56 data bytes

64 bytes from 192.168.15.1: icmp_seq=0 ttl=255 time=0.858 ms

64 bytes from 192.168.15.1: icmp_seq=1 ttl=255 time=2.719 ms

64 bytes from 192.168.15.1: icmp_seq=2 ttl=255 time=0.674 ms

 

--- 192.168.15.1 ping statistics ---

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max = 0.674/1.417/2.719 ms

 

[root@esxi-nested-04:~]

[root@esxi-nested-04:~]

[root@esxi-nested-04:~] ping 192.168.15.3

PING 192.168.15.3 (192.168.15.3): 56 data bytes

64 bytes from 192.168.15.3: icmp_seq=0 ttl=64 time=0.556 ms

64 bytes from 192.168.15.3: icmp_seq=1 ttl=64 time=0.489 ms

 

--- 192.168.15.3 ping statistics ---

2 packets transmitted, 2 packets received, 0% packet loss

round-trip min/avg/max = 0.489/0.522/0.556 ms

 

[root@esxi-nested-04:~] ping 192.168.20.1

PING 192.168.20.1 (192.168.20.1): 56 data bytes

 

--- 192.168.20.1 ping statistics ---

2 packets transmitted, 0 packets received, 100% packet loss

Got hold of this article, going through it now
https://www.networkstraining.com/cisco-nexus-layer2-layer3-intervlan-routing/

What I meant actually was from nexus use the command ping with source

Or extend ping to simulate the packet leaving one vlan and going to the other

You put the source as one vlan and the destination the other vlan, it ping fails is nexus problem, if not, is host problem

switch# ping 192.168.15.2 source 192.168.20.1

PING 192.168.15.2 (192.168.15.2) from 192.168.20.1: 56 data bytes

64 bytes from 192.168.15.2: icmp_seq=0 ttl=63 time=0.746 ms

64 bytes from 192.168.15.2: icmp_seq=1 ttl=63 time=0.538 ms

64 bytes from 192.168.15.2: icmp_seq=2 ttl=63 time=1.099 ms

64 bytes from 192.168.15.2: icmp_seq=3 ttl=63 time=0.625 ms

64 bytes from 192.168.15.2: icmp_seq=4 ttl=63 time=0.617 ms

 

Is this what you were looking for?
Does that mean there is no issue with configuration on switch side and it lies with the host side?

nsom
Level 1
Level 1

switch(config)# show license usage

Feature                      Ins  Lic   Status Expiry Date Comments

                                 Count

--------------------------------------------------------------------------------

ACI-STRG                      No    -   Unused             -

ACI-AD-GF                     No    -   Unused             -

ACI-AD-XF                     No    -   Unused             -

ACI-ES-GF                     No    -   Unused             -

ACI-ES-XF                     No    -   Unused             -

ACI-AD-XF2                    No    -   Unused             -

ACI-ES-XF2                    No    -   Unused             -

ACI-SEC-GF                    No    -   Unused             -

ACI-SEC-XF                    No    -   Unused             -

ACI-SEC-XM                    No    0   Unused             -

N9K_LIC_1G                    No    -   Unused             -

VPN_FABRIC                    No    -   Unused             -

ACI-STRG-GF                   No    -   Unused             -

ACI-STRG-XF                   No    -   Unused             -

NXOS_OE_PKG                   No    -   Unused             -

FCOE_NPV_PKG                  No    -   Unused             -

SECURITY_PKG                  No    0   Unused             -

ACI-PREMIER-GF                No    -   Unused             -

ACI-PREMIER-XF                No    -   Unused             -

N9K_UPG_EX_10G                No    -   Unused             -

ACI-PREMIER-XF2               No    -   Unused             -

NXOS-PREMIER-M4               No    -   Unused             -

TP_SERVICES_PKG               No    -   Unused             -

NXOS-PREMIER-M816             No    -   Unused             -

NXOS_ADVANTAGE_GF             No    -   Unused             -

NXOS_ADVANTAGE_M4             No    -   Unused             -

NXOS_ADVANTAGE_XF             No    -   Unused             -

NXOS_ESSENTIALS_GF            No    -   Unused             -

NXOS_ESSENTIALS_M4            No    -   Unused             -

NXOS_ESSENTIALS_XF            No    -   Unused             -

NXOS_ESSENTIALS_XM            No    -   Unused             -

SAN_ENTERPRISE_PKG            No    -   Unused             -

PORT_ACTIVATION_PKG           No    0   Unused             -

NETWORK_SERVICES_PKG          No    -   Unused             -

NXOS_ADVANTAGE_M8-16          No    -   Unused             -

NXOS_ESSENTIALS_M8-16         No    -   Unused             -

FC_PORT_ACTIVATION_PKG        No    0   Unused             -

LAN_ENTERPRISE_SERVICES_PKG   No    -   In use             Honor Start 2D 4H

--------------------------------------------------------------------------------

switch(config)#

switch(config)#

switch(config)#

switch(config)#

switch(config)# show run int Eth1/1

 

!Command: show running-config interface Ethernet1/1

!Running configuration last done at: Sun May 28 13:43:43 2023

!Time: Sun May 28 14:25:46 2023

 

version 9.3(7a) Bios:version 

 

interface Ethernet1/1

  switchport access vlan 2003

 

switch(config)# show run int Eth1/3

 

!Command: show running-config interface Ethernet1/3

!Running configuration last done at: Sun May 28 13:43:43 2023

!Time: Sun May 28 14:25:52 2023

 

version 9.3(7a) Bios:version 

 

interface Ethernet1/3

  switchport access vlan 2004

nsom
Level 1
Level 1

switch(config)# show ip interface brief

 

IP Interface Status for VRF "default"(1)

Interface            IP Address      Interface Status

Vlan2003             192.168.15.1    protocol-up/link-up/admin-up       

Vlan2004             192.168.20.1    protocol-up/link-up/admin-up       

Vlan2005             192.168.12.1    protocol-down/link-down/admin-up   

 show policy-map type control-plane
and please also do
ethanalyzer local interface inband
then do ping 

show policy-map type control-plane

 

  policy-map type control-plane copp-system-p-policy-strict

    class copp-system-p-class-l3uc-data

      set cos 1

      police cir 250 pps bc 32 packets conform transmit violate drop

    class copp-system-p-class-critical

      set cos 7

      police cir 19000 pps bc 128 packets conform transmit violate drop

    class copp-system-p-class-important

      set cos 6

      police cir 3000 pps bc 256 packets conform transmit violate drop

    class copp-system-p-class-openflow

      set cos 5

      police cir 2000 pps bc 32 packets conform transmit violate drop

    class copp-system-p-class-multicast-router

      set cos 6

      police cir 3000 pps bc 128 packets conform transmit violate drop

    class copp-system-p-class-multicast-host

      set cos 1

      police cir 2000 pps bc 128 packets conform transmit violate drop

    class copp-system-p-class-l3mc-data

      set cos 1

      police cir 3000 pps bc 32 packets conform transmit violate drop

    class copp-system-p-class-normal

      set cos 1

      police cir 1500 pps bc 32 packets conform transmit violate drop

    class copp-system-p-class-ndp

      set cos 6

      police cir 1500 pps bc 32 packets conform transmit violate drop

    class copp-system-p-class-normal-dhcp

      set cos 1

      police cir 300 pps bc 32 packets conform transmit violate drop

    class copp-system-p-class-normal-dhcp-relay-response

      set cos 1

      police cir 400 pps bc 64 packets conform transmit violate drop

    class copp-system-p-class-normal-igmp

      set cos 3

      police cir 6000 pps bc 64 packets conform transmit violate drop

    class copp-system-p-class-redirect

      set cos 1

      police cir 1500 pps bc 32 packets conform transmit violate drop

    class copp-system-p-class-exception

      set cos 1

      police cir 50 pps bc 32 packets conform transmit violate drop

    class copp-system-p-class-exception-diag

      set cos 1

      police cir 50 pps bc 32 packets conform transmit violate drop

    class copp-system-p-class-management

      set cos 2

      police cir 3000 pps bc 512000 packets conform transmit violate drop

    class copp-system-p-class-monitoring

      set cos 1

      police cir 300 pps bc 128 packets conform transmit violate drop

    class copp-system-p-class-l2-unpoliced

      set cos 7

      police cir 20000 pps bc 8192 packets conform transmit violate drop

    class copp-system-p-class-undesirable

      set cos 0

      police cir 15 pps bc 32 packets conform transmit violate drop

    class copp-system-p-class-fcoe

      set cos 6

      police cir 1000 pps bc 32 packets conform transmit violate drop

    class copp-system-p-class-nat-flow

      set cos 7

      police cir 100 pps bc 64 packets conform transmit violate drop

    class copp-system-p-class-l3mcv6-data

      set cos 1

      police cir 3000 pps bc 32 packets conform transmit violate drop

    class copp-system-p-class-undesirablev6

      set cos 0

      police cir 15 pps bc 32 packets conform transmit violate drop

    class copp-system-p-class-l2-default

      set cos 0

      police cir 50 pps bc 32 packets conform transmit violate drop

    class class-default

      set cos 0

      police cir 50 pps bc 32 packets conform transmit violate drop

 

switch(config)# ethanalyzer local interface inband

Capturing on inband

2023-05-28 14:43:19.940948 00:00:00:00:00:00 -> 14:00:02:00:0f:00 MDS Header [Malformed Packet]

2023-05-28 14:43:19.941111 00:00:00:00:00:00 -> 14:00:02:00:0f:00 MDS Header [Malformed Packet]

2023-05-28 14:43:19.941183 00:00:00:00:00:00 -> 14:00:02:00:0f:00 MDS Header [Malformed Packet]

2023-05-28 14:43:20.691116 00:00:00:00:00:00 -> 14:00:02:00:0f:00 MDS Header [Malformed Packet]

2023-05-28 14:43:20.691154 00:00:00:00:00:00 -> 14:00:02:00:0f:00 MDS Header [Malformed Packet]

2023-05-28 14:43:21.940696 00:00:00:00:00:00 -> 14:00:02:00:0f:00 MDS Header [Malformed Packet]

2023-05-28 14:43:21.940733 00:00:00:00:00:00 -> 14:00:02:00:0f:00 MDS Header [Malformed Packet]

2023-05-28 14:43:21.940744 00:00:00:00:00:00 -> 14:00:02:00:0f:00 MDS Header [Malformed Packet]

2023-05-28 14:43:22.690717 00:00:00:00:00:00 -> 14:00:02:00:0f:00 MDS Header [Malformed Packet]

2023-05-28 14:43:22.690784 00:00:00:00:00:00 -> 14:00:02:00:0f:00 MDS Header [Malformed Packet]

10 packets captured

enable the ethanalyzer then ping directly I need the frame punt to CPU of NSK 
please also show arp in NSK

Hi not sure if I followed here.
The output I sent was after running the ethanalyzer command and then started ping from host1 to vlan2004 ip.
Could you also let me know what is the command to run
"show arp in NSK"