Adding a route to a Cisco 800 Switch

I am currently trying add a route on a Cisco 800 switch basically

I am trying to add an address to the dialer2

At first I tried for example

ip route 192.168.x.x. 255.255.255.0 (that didn't seem to work) as i still can't ping the device

So I tried

ip route 192.168.x.x. 255.255.255.0 Dialer2

I received the following error.

#ip route 192.168.x.x 255.255.255.0 dialer2
^
% Invalid input detected at '^' marker.

x is replaces the number (just incase anyone thinks I am using a x)

Am I using the right command's as usual don't admin cisco devices

Any help would be greatly appreaciated

THX ZL

p.s. I tried getting commands from Cisco however I need to register but can't for some reason as post code is flagging up as invalid.

Your creating a static route to the device in question thru the dialer2 interface for remote access, correct?

What version of IOS is the box running?

Also, are you sure that the interface for dialer2 is configured correctly and a dialing pool set up?

Just wondering...can't assume anything. Double check your interface configuration.

BTW: The 800 series are ROUTERS, not switches

cheers

Your trying to add a IP to dialer 2, and a route to the router?
Or is dialer 2 working, and pulling an IP, and all you need is the static route to it?

Cause what you said, and what your trying to do are two different things.


You are in the config tab as well right? .... config t




Edit:....bah you person with a long number in your name..you edited, before I posted...lol

The ip route command needs to be entered in global config mode, not priv exec (#)---this is why you get the error. Normally, you would add a static default route, like so...
router>en
router#conf t
router(config)#ip route 0.0.0.0 0.0.0.0 int di2
Posting a complete config would help---"sh run" from priv exec.

Tim

well what kind of interface is it, dialer sounds like a modem interface or something else, and also the error is at the beginning, meaning that the command isn't even a possible command, so at the least its a syntax error at the very beginning, you might want to try ? and go through the command trees to find the right command for setting up a route. Also i'm not so sure about the IOS on 800 series routers, but i know in 2600 series routers you set up routes from the global configuration (configure terminal). You didn't say what prompt you were at, but that too could be the source of your problem.

edit:maybe i should have refreshed before i replied...**shrug

From here: http://tazforum.**********.com/viewtopic.php?t=7756

you need to enter privileged exec mode - type "config t" and then try your command.

So your prompt will be;

<hostname>(config)#

Then the route command is usually:

ip route <Destination IP> <Destination IP prefix mask (subnet mask)> <forwarding routers address as an IP address or a hostname> <hop count>

eg:

ip route 192.168.1.0 255.255.255.0 192.168.2.2 1

Which says send all traffic destined to 192.168.1.0/24 to the host that has the IP of 192.168.2.2 and this host is 1 hop away.

If you use a host name then obviously you must have defined it first.

The best way for you to do it would be to use the TAB key and the ?.

So type ip rout and then press TAB, this will then complete the command for you, now enter a ? and press enter, it will come up and tell you what options you need. You can enter a ? after any complete word to see what is expected to follow the command.

Just C + P'd this from one of my switches to show you (this is for a basic route command, as you can see there are other options you can use):

Code:

---


3560-2(config)#ip route
3560-2(config)#ip route ?
  A.B.C.D  Destination prefix
  profile  Enable IP routing table profile
  static  Allow static routes

3560-2(config)#ip route 192.168.2.0 ?
  A.B.C.D  Destination prefix mask

3560-2(config)#ip route 192.168.2.0

3560-2(config)#ip route 192.168.2.0 255.255.255.0 ?
  A.B.C.D            Forwarding router's address
  Async              Async interface
  BVI                Bridge-Group Virtual Interface
  CTunnel            CTunnel interface
  Dialer            Dialer interface
  FastEthernet      FastEthernet IEEE 802.3
  Filter            Filter interface
  Filtergroup        Filter Group interface
  GigabitEthernet    GigabitEthernet IEEE 802.3z
  Lex                Lex interface
  LongReachEthernet  Long-Reach Ethernet interface
  Loopback          Loopback interface
  Null              Null interface
  Port-channel      Ethernet Channel of interfaces
  Portgroup          Portgroup interface
  Pos-channel        POS Channel of interfaces
  Tunnel            Tunnel interface
  Vif                PGM Multicast Host interface
  Virtual-TokenRing  Virtual TokenRing
  Vlan              Catalyst Vlans
  fcpa              Fiber Channel

3560-2(config)#ip route 192.168.2.0 255.255.255.0 192.168.2.1 ?
  <1-255>    Distance metric for this route
  name      Specify name of the next hop
  permanent  permanent route
  tag        Set tag for this route
 
3560-2(config)#ip route 192.168.2.0 255.255.255.0 192.168.2.1 1
3560-2(config)#

---

Sorry I meant router not switch - I am pretty cooked up my office at the moment it oviously affecting the few brain cells I have. Anyhow before I start playing with the router again. I want to add a route 192.168.x.x to the dialer. I want to this because I think the router has lost it routing table so from the local router I want traffic to route through the dialer to the 192.168.x.x range.

So would it just be a simple case of having my local ip 10.136.x.x to route to dialer2 192.168.x.x

in config t - ip route 10.136.x.x 255.255.255.0 192.168.x.x 1
Since it is one hop away - Is that right as I don't want to mess it up - I have very limited knowledge of routers.

Exactly right; the command is the same on switch or router (and the TAB and ? aids still work). You would rarely enter it on a switch though unless it was a layer 3 one.

Try it and if it doesn't work press the up arrow and put 'no' in front of it to remove the command, (i.e #no ip route ..........)

Quote:

---

Sorry I meant router not switch

---

I think most of us worked that out when you said it was 800 series :D

Thanks very much Nokia and everyone else - Unfortunately though it is still not working still as I cannot ping the device (router) even after adding the route. :(

I have got bt to test the link and according to them it is working fine. So that's me stumped

please post a sh run

Tim

Are there any ACL's on it? Any ICMP filtering devices? Have you tried pinging it from the router you are trying to configure, to see if that can get to it - if it can't then the problem is not the router config.

Are you getting ICMP timed out or destination unreachable errors when pinging?

No there is no ACL's (I gather that is access control list) or any ICMP filtering devices. I have tried ping the other router before and after adding the route (which should have already been there) ICMP timed out on both occassion's.

Unfortunately as well I can't check the config on the other router as I do not know the password (as I never it set)

The device was working fine on Monday went down tuesday - No power cuts to my knowledge.

From your computer could you run a traceroute to the IP you are trying to reach and post the resutls here? You IP's are internal so there is no problem putting them here as they won't mean anything to anyone outside of your network.

You could also try a pathping which gives a little more info than a traceroute.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\>tracert 192.168.254.254

Tracing route to 192.168.254.254 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.136.140.251
2 1 ms * * 10.136.140.250
3 * * * Request timed out.
4 * ^C
C:\Documents and Settings\

What is a pingpath I have never came across that word before - huh

Anyhow do I need to set the route on the dialer or by setting the route on the router, does that forward the IP Automatically thru the dialer?

Could you explain a little of yuor network? Ie where the dialler is in relation to the router etc.

From your traceroute I am presuming 10.136.140.250 and 251 are routers? Is 10.136.140.251 your default gateway? There could be a routing problem on 140.250 as it is not finding the 192.168.254.0 network. Do you have access to it?

A pathping is a broken down ping that gives info for each hop it passes. It's similar to traceroute but uses a slightly different protocol so sometimes can avoid any ICMP filtering. (pathping <IP Address> )

I am not sure what you mean by the dialer, is that the ISDN Line as the phycical device, the router .250 is according to the plans a Cisco 2600. I am not sure what .251 it is my default gateway. I do not have phyical access to .250 I think .251 is a Cisco 1800 I can see two of them. But I cannot see a Cisco 2600

It looks like you have this setup

Code:

---

You-->-->| 10.136.140.251 |-->-->| 10.136.140.250 |-->-->-->| Maybe Internet / firewall |                                                                           
                                        |
                                        |
                                        |
                              | 192.168.254.0/24 (NETWORK) |

---

It looks like you need the 10.136.140.250 router to route across to the 192.168.254.X network, so on this router you need to add the 'ip route 192.168.254.0 255.255.255.0 <IP of router/Gate way> <hop>

You client is configured with 251 as its gate way so it sends all non local traffic to this, then 251 has a route in it that tells it to send anything destined for 192.168.254.0/24 to the .250 router (or it could have a default route telling it to send any unknown traffic to .250).
The .250 router however either does not know where to send the traffic and is dropping it, has ACL's on it telling it to drop the packets, or whatever its default route is set to is dropping the packets (possibly a firewall)

I could have the topology wrong though and 140.250 could be a firewall - I am just going off what I presume it is from your traceroute and description.

If there was anyway you could do a sh run on the router, that would definitely help some....who controls the .250 router? Could you get them to send you a sh run from that router?

If we can see the routes on those 2 routers, it would make troubleshooting a little bit easier.


Definitely starting to sound like the .250 router might be missing a route to the 192.x.x.x network as nokia suggested.

I have found the route table on the router and the correct route to dialer is there - So since the second router cannot be pinged from router1 Then they must be a problem with router2 unfortunately I cannot logon to the second router (whoever set the password didn't log it)

Thanks for your help guide - But without the password for router2 I cannot go any further! :(

Pah, just unplug it! :D

You can find password recovery procedures on Cisco's site ;)

Can you not ask a network engineer to help you out? Someone must look after the router....

The guy who usual looks after it is abroad, and I think he got sick of me as he has stopped repling to my messages. I cannot seem to register on cisco either which I had tried previously before SirDice kindly suggested. I will try again and register with a different address, and see if that works.

We have never had problems with cisco's router's before - So some how I think the routing table or configeration has screwed up at the router2 (as Nokia suggested). They claim their haven't had a power cut, so I am stumped well it the weekend now. So I will have to have an go on Monday (my boss is back then too :) )

In the mean time I shall try to register on the cisco site again.

Thanks to everyone for the help so far. I have learned a bit more about Cisco command's which should provide useful should I ever need to admin a cisco router again.

For password recovery, you need to console into i, shut it off, turn it back on, and initiate a break sequence (either shift-pause/break or ctrl-pause/break)---this will get you to the
rommon1>
prompt. From there, do this...
rommon1>confreg 2142
rommon2>reset
The router reboots, and loads the default config, no passwords. When it comes all the way up, do this...
router>en
router#copy start run
Then you can
router#conf t
router(config)#no service password-encryption
router(config)#exit
router#sh run
This will show the passwords. If a secret is enabled, just enable a different one, like so...
router#conf t
router(config)#enable secret blablabla
Then make sure you do passwords for line con 0 and vty 0 4
router(config)#line con 0
router(config-line)#password bambam
router(config-line)#login
router(config-line)#exit
router(config)#line vty 0 4
router(config-line)#password bambam (or a different one, if you want)
router(config-line)#login
router(config-line)#exit
Then re-enable password encryption...
router(config)#service password-encryption
If there is a line like
username boom privelege 15 password (or secret) 7 xxxxxxxx
Then you will see it. This is normally set for authentication to a RADIUS/TACACS+ server, local AAA database in the router, or ssh/http/https logins. Hope this helps.

Tim

I forgot---set the config register back to 2102 like so...
router(config)#config-register 2102
router(config)#exit
router#wr
The "wr" command writes (or saves) the running-config to the startup-config.

Tim

Personally I think that if you don't administer the router and don't understand how it slots in functionality-wise into the network then you shouldn't do anything to it.

I certainly wouldn't try a password reset on it and most certainly would not power it down and back up again without understanding what it is used for, or speaking to the network manager first.

I would fire someone on the spot for doing that on any of my networks.

What is your position in relation with this company?

Is this a 1 man operation or a company with multiple IT staff?

I don't really have a choice the guy is normally sorts it away for 2 weeks, and I cannot any specialists in till Tuesday. The system is off the guys cannot do any stock checks or transactions.

I know exactly what the router is for too route the packet between two networks or more. In my case between my office and 3rd party warehouse. The thing is not working anyhow so I won't get sacked because I was given permisson from my colleague who is the cisco expert (devine entity to me :)

It would be a different case if I was just a office worker or shop floor staff, I would be same I would sack anyone for messing with I.T. equipment.

I haven't messed with cisco router's before that's why I was a bit dumb at first. I know alot now since you (Nokia and the other guys have helped me) I still don't know what I am doing in regards to config but I will muddle on. as the think is fooked, so I can't make it worse unless I loose the routes and dialer information on router2 - I will be shafted big style then, if that happens.

I have a small I.T. Deparment - my roll is just desktop support and server maintenance (just keeping them running with updates etc) I have three colleagues locally

3 Programmers - one of whom my colleagues look after the infrastructure of the network he's manages all com's routers/switches/firewalls/WiFi etc and servers. Unfortuantely everytime he goes on Holiday I am ****ed as I get more sense of a brick wall then asking the other two.

Well, I thought it was common sense to not just go and do this---I was assuming he is the admin, seen as how he is inquiring about how to look at and possibly modify the routing table. But yeah---what Nokia said. Come on, dude...

Tim

Careful you don't make matters worse for yourself though mate - taking routers off-line invariably has an impact of pretty much the whole network...

If you break it and get hauled into your boss you may at least be able to blag a Cisco course outta them :D

Good luck to ya, whatever you decide to do :)

//I have always found it good practice to hold your hands up and admit to management that you are in too deep, than to blunder in and hope it all works out. At worst the give they responsibility to someone else, at best they train you up - either way the outcome is better than having the network come crashing down around your ears because you made a mistake. -Bring a server off-line for a few minutes in all likelihood you will get away with no one noticing....bring the infrastructure down for a few minutes and all hell breaks loose :D

At least its Friday....lol

Have you tried talking to your supervisor?

Actually, zoro, I was directing that toward nokia, not you---I'm FOR you trying to fix it!

I would like to appologie c1sc0m4n. As you can tell I had a pretty bad week running the show. I didn't read your post correctly. I don't know if it is just me, but everytime someone is off I end up trying to resolve stuff that is out of my depth (usually I leave if it is unix related) In this case though I was told to sort it even though I didn't have the knowledge. My supervisor is back on Monday - So hopefully get something sorted. I think I might even ask to go on a cisco cource. The guy who look after it though is off for another week though (wished it was me)

Just what bugs me the most, is that I can't logon to router2. Well have the instructions provided by Nokia and you (c1scom4n) - so perhaps I can muddle through it tomorrow.

Thx n sorry

Solution found the line has been cancelled at the main site. I thought due to another location working fine, that the problem was at the warehouse.

Basically the other site has a different connection. The line here had just been cancelled by my Manager - Kind of important to check if connections are using the line before you cancel it.

Sorry to waste everyone's time, least I know a bit about cisco router's now.

Thanks to everyone

Is this by chance the same manager who told you to figure it out in the first place?
By the way, no need to apologize. Having a rough week is understandable, and it is easy to misconstrue what someone is trying to say, especially when two people are posting at the same time, and they end up "out of order", so to speak. Glad you have it fixed!

Tim