ip route add not showing up

cstpierre4 · ‎05-31-2013

Hello,

we have a cisco 3750-48 port switch.

We have a few SVI's configured and some static routes configured.

I had created a new interface vlan and gave it an IP. I can ping the gateway.

Now I want to add a static route to go out that interface.

when I add:

ip route 10.x.x.x 255.255.255.0 10.52.10.1

it eccepts it (no errors) But, it does not show in the routing table nor in the config?

Any suggestions would be helpful as to how to add the static route to go out that vlan interface.

Thanks

Richard Burts · ‎05-31-2013

Some additional details would help us to understand the issue better and to be able to give you better suggestions.

As a start perhaps you could post the output of show ip interface vlan

HTH

Rick

HTH

Rick

cstpierre4 · ‎05-31-2013

Hi sure,

here it is.

switch#sho ip interface vlan153

Vlan153 is up, line protocol is up

Internet address is 10.52.159.69/26

Broadcast address is 255.255.255.255

Address determined by setup command

MTU is 1500 bytes

Helper address is not set

Directed broadcast forwarding is disabled

Outgoing access list is not set

Inbound access list is not set

Proxy ARP is enabled

Local Proxy ARP is disabled

Security level is default

Split horizon is enabled

ICMP redirects are always sent

ICMP unreachables are always sent

ICMP mask replies are never sent

IP fast switching is enabled

IP CEF switching is enabled

IP CEF switching turbo vector

IP Null turbo vector

IP multicast fast switching is enabled

IP multicast distributed fast switching is disabled

IP route-cache flags are Fast, CEF

Router Discovery is disabled

IP output packet accounting is disabled

IP access violation accounting is disabled

TCP/IP header compression is disabled

RTP/IP header compression is disabled

Probe proxy name replies are disabled

Policy routing is disabled

Network address translation is disabled

BGP Policy Mapping is disabled

Input features: MCI Check

Output features: Input interface drop, Check hwidb

the route being added is:

ip route 10.140.110.0 255.255.255.0 10.52.159.65

InayathUlla Sharieff · ‎05-31-2013

Hi,

I just tested on Cisco 3560 and its working fine for me.

Eg:

SW1--------------------SW2

Conf from SW2 ( Similar config exist on SW1 with just lo1 ip address 1.1.1.1 )

I will create the route on SW2.

Vlan10 10.10.10.2 YES manual up up

Vlan20 20.20.20.2 YES manual up up

Vlan30 30.30.30.2 YES manual up up

ip classless

ip route 1.1.1.1 255.255.255.255 10.10.10.1 >>>>> Tried both ways and its showing under the config.

Switch#sh ip route

Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP

Gateway of last resort is not set

1.0.0.0/32 is subnetted, 1 subnets

S 1.1.1.1 [1/0] via 10.10.10.1 >>>>>>>>>> Static route is showing now.

Action plan:

==========

Whats the version you are running on your switch?

Can you try configuring on other switch and provide us the result?

HTH

Regards

Inayath.

Akash Agrawal · ‎05-31-2013

Hi,

To see static route into routing table, you need to have

1. next-hop reachable (it is there in your case)

2. "ip routing" should be enabled on switch.

After configuring "ip routing" , please share output of "show ip route"

Richard Burts · ‎06-01-2013

The original poster describes the issue as this

I want to add a static route to go out that interface.

The next hop in the static route is 10.52.10.1

The interface address is 10.52.159.69/26

Pretty clearly the next hop does not go out that interface.

So the first problem is that the next hop is not out the interface where the original poster wants it to go. I suspect that there is another problem which is that the next hop of 10.52.10.1 may not be reachable. Perhaps the original poster can post the output of show ip route 10.52.10.1

HTH

Rick

HTH

Rick

cstpierre4 · ‎06-01-2013

Sorry about that. I was just using those IP's as examples..

Here is what they IPs are:

interface vlan153 and Ip address is =10.52.159.69/26

and the route being added is:

ip route 10.140.110.0 255.255.255.0 10.52.159.65

and the gateway is reachable. I can ping 10.52.159.65.

But when i add the below route. it looks like its added(no errors etc..) but it doesnt show in the config or in the route table

ip route 10.140.110.0 255.255.255.0 10.52.159.65

Richard Burts · ‎06-01-2013

Thanks for the clarification. So this reflects what you sent in a previous response to my request for information about the VLAN interface. I assume that the information in that post is still accurate (most especially the IP address and mask of the interface and that the status of the interface is up/up)? Can you verify that IP routing is enabled on the switch?

Perhaps you could post the output of show ip protocol and the output of show ip route from the 3750?

HTH

Rick

HTH

Rick

cstpierre4 · ‎06-05-2013

Hi sure,

here it is:

switch#sho ip protocol

^

% Invalid input detected at '^' marker.

switch#sho ip route

Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP

D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

E1 - OSPF external type 1, E2 - OSPF external type 2

i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2

ia - IS-IS inter area, * - candidate default, U - per-user static route

o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP

+ - replicated route, % - next hop override

Gateway of last resort is 10.3.95.1 to network 0.0.0.0

S* 0.0.0.0/0 [1/0] via 10.3.95.1

10.0.0.0/8 is variably subnetted, 6 subnets, 4 masks

C 10.3.95.0/25 is directly connected, Vlan149

L 10.3.95.4/32 is directly connected, Vlan149

C 10.52.159.64/26 is directly connected, Vlan153

L 10.52.159.69/32 is directly connected, Vlan153

C 10.133.192.16/28 is directly connected, Vlan105

L 10.133.192.20/32 is directly connected, Vlan105

213.212.68.0/32 is subnetted, 1 subnets

S 213.212.68.201 [1/0] via 10.133.192.17

213.212.72.0/32 is subnetted, 6 subnets

S 213.212.72.130 [1/0] via 10.133.192.17

S 213.212.72.143 [1/0] via 10.133.192.17

S 213.212.72.144 [1/0] via 10.133.192.17

S 213.212.72.151 [1/0] via 10.133.192.17

S 213.212.72.153 [1/0] via 10.133.192.17

S 213.212.72.171 [1/0] via 10.133.192.17

216.83.186.0/32 is subnetted, 6 subnets

S 216.83.186.57 [1/0] via 10.133.192.17

S 216.83.186.66 [1/0] via 10.133.192.17

S 216.83.186.79 [1/0] via 10.133.192.17

S 216.83.186.80 [1/0] via 10.133.192.17

S 216.83.186.87 [1/0] via 10.133.192.17

S 216.83.186.89 [1/0] via 10.133.192.17

216.203.1.0/32 is subnetted, 1 subnets

S 216.203.1.107 [1/0] via 10.133.192.17

S 216.203.5.0/24 [1/0] via 10.133.192.17

Its weird.

Ravi Singh · ‎06-01-2013

Static route only available in routing table if the following condtionb meets.

1. next-hop reachable (it is there in your case)

2. "ip routing" should be enabled on switch.

cstpierre4 · ‎06-05-2013

I dont see ip routing enabled.

But there are static routes on the switch.

switch#sho run | i rout

system mtu routing 1500

no ip source-route

ip host-routing

no ip route-cache cef

no ip route-cache

ip route 0.0.0.0 0.0.0.0 10.3.95.1

ip route 213.212.68.201 255.255.255.255 10.133.192.17

ip route 213.212.72.130 255.255.255.255 10.133.192.17

ip route 213.212.72.143 255.255.255.255 10.133.192.17

ip route 213.212.72.144 255.255.255.255 10.133.192.17

ip route 213.212.72.151 255.255.255.255 10.133.192.17

Richard Burts · ‎06-05-2013

Thanks for the additional information. I believe that fundamentally this problem reflects that fact that ip routing is not enabled. I believe that not having ip routing enabled has impact on things when you attempt to configure multiple layer 3 interfaces/multiple SVIs. And ultimately it impacts trying to add static routes with a next hop that is in a different subnet/different outbound interface than the static routes that you show which do work.

HTH

Rick

HTH

Rick

cstpierre4 · ‎06-05-2013

Got it.. Thanks for the response..

What impact if any would I see by enabling ip routing?

Thanks

InayathUlla Sharieff · ‎06-05-2013

There should not be any impact enabling ip routing on the device.

You just telling the device that we are enabling this feature and you should support all the respestive stuff on what that feature does.

HTH

Regards

Inayath

*Plz rate all usefull posts and mark as answered if it has resolved your query.

Richard Burts · ‎06-05-2013

I am a bit more cautious than Inayath about the possible impact of enabling ip routing. If the network has been implemented on the basis that this is a layer 2 switch and routing is done on some layer 3 device somewhere else in the network and then we turn this switch from a purely layer 2 switch into a layer 3 switch (and if there are some number of layer 3 SVIs already configured) then it is possible that some traffic flow patterns will be changed.

To make the recent set of changes work I agree that you need to enable ip routing on the switch. And I am not sure that the impact of enabling ip routing will be large. But I am not comfortable saying that there will be no impact.

HTH

Rick

HTH

Rick