1700 does not route

[james.curran]

Having trouble with a 1700 routing in production.

In the initial test bed I had a Desktop set at 192.9.100.250  connected to port4 of the layer 2 switch on the 1700. The Vlan1 of the switch is set at 192.9.100.194.

The FastEthernet0 port of the router is set at 156.52.42.194 and was connected to a desktop set at 156.52.42.10.

I could ping from the 192.9.100.250 desktop to the 156.52.42.10 desktop across the router without problem. Ping in the other direction also worked.

Note:  System does not need internet access. It is an internal router only. Connection bridges from an 0vation swtch 192.x.x.x to a Hirschman Ethernet switch .152.x.x.x

When placed into production it looks like this

Hirschman Ethernet Switch 156.9.52.42.10 --->media converter---->| 1700 Router FastEthernet0 (156.52.42.194) <==> Vlan1 port 4 (192.9.100.194) | -------> Cisco 2820 (192.9.100.117 concentrator ---> Cisco Bridge PCC Ovation 192.9.100.250

From the switch (Hyperterminal)  I can ping in either direction. From the Hirschman (156.x.x.x) I can ping to the FE0 Side but not to Port 4 of the interior switch (192.9.100.194).

I started to set up NAT in the Lab but since I was successful without using it left the inside/Outside statements off.

using ping 192.9.100.194 source 156.52.42.194 is successful

using ping 156.52.42.194 source 192.9.100.194 is successful.

Ping either direction from the outside returns only reachs the associated port on the router ether Port4 vlan or FE0 but does not continue to the other side.

Any assistance would be appreciated. Router is located in a remote location (Incinerator) so trips to it are difficult.

[Antonio Knox]

Remove

ip route 156.52.42.0 255.255.255.0 192.9.100.0

ip route 192.9.100.0 255.255.255.0 156.52.42.0

When you place ip addresses on interface fa0 and vlan1 routes are created for those networks automatically.

[james.curran]

Antonio Thank you for answering. I did recently delete those statements wihout any improvement.

sh route indicates below.

Router#sh ip int br
Interface                  IP-Address      OK? Method Status                Protocol
Async1                     unassigned      YES NVRAM  down                  down   
FastEthernet0              156.52.42.194   YES NVRAM  up                    up     
FastEthernet1              unassigned      YES unset  up                    down   
FastEthernet2              unassigned      YES unset  up                    down   
FastEthernet3              unassigned      YES unset  up                    down   
FastEthernet4              unassigned      YES unset  up                    up     
NVI0                       unassigned      YES unset  up                    up     
Vlan1                      192.9.100.194   YES manual up                    up     
Router#sh route

Router#sh ip route
Codes: 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

Gateway of last resort is not set

     156.52.0.0/24 is subnetted, 1 subnets
C       156.52.42.0 is directly connected, FastEthernet0
C    192.9.100.0/24 is directly connected, Vlan1

We are also curretly checking the 2820 to insure that it has a route back to 192.9.100.194.  I sure it does but cannot test because someone turned the 1711 unit off.  Have an engineer going onsite to reset the router.

will post with the results.

[james.curran]

June 8, 2011

Logged to the 2820 and found that it did have a route to the 192.9.100.194 (1711). Can ping to the 192.9.100.194 side of the router but not to the 156.52.42.194 (FEO) Side. Can also ping 192.9.100.250 the next router upstream.

[Antonio Knox]

Make sure that the 2820 also has a route to 156.52.42.0/24 as well.  If not, he won't know how to reach that network.  I'm assuming the Hirschman Ethernet Switch has a default route pointing to 156.52.42.194, if it doesn't then it needs one.

[james.curran]

I have looked at the 2820 Switch IOS and cannot determine how to set the route up to the 1700. What commands should I use to set the route. looking at the cmd's available I don't think that is an option.

The Hirschman does not have a default route. I do see how to set one up.

Thanks for responding.

[vmiller]

Try this:

http://www.cisco.com/en/US/docs/switches/lan/catalyst2900xl_3500xl/catalyst1900_2820/version6.x_7.x/cat2820/icg/28icoutb.html#wp63474

IP configuration menu.

[Antonio Knox]

for the 2820

ip route 156.52.42.0 0.0.0.255 192.9.100.194

for hirschman switch here's a guide:

http://www.wwsinternational.com.au/Hirschmann/pdf/quickstart.pdf

[james.curran]

The 2820 does not have the IP Route Command. I have gone thru the CLI list with no luck. Entering the IP ROUTE 156.XXX cmd that you recommended came back in error.  Any other recommendations. Should the route cmd be further up the food chain like on the 3560.

Thanks

[vmiller]

Doesn't this have the menu driven configuration /

[james.curran]

The 2820  does have menu driven configuration  ( ver 9.0.0.6). I have gone thru all the menu opportunities without success. The cli cmd level allows me to enter the route cmd but returns an error with the cavet on router. 

[vmiller · Accepted solution]

Move your vlan1 config to FE 0/4. cable FE0/4 to the 2820. give it an address on the 192 xx subnet(the old vlan1), and default gateway of the ip address you moved to FE 0/4. 

[cadet alain]

Hi,

James Curran a écrit:
 The 2820  does have menu driven configuration  ( ver 9.0.0.6). I have gone thru all the menu opportunities without success. The cli cmd level allows me to enter the route cmd but returns an error with the cavet on router.  

This is because

ip route 156.52.42.0 0.0.0.255 192.9.100.194  has an invalid subnet mask, it should be 255.255.255.0

Regards.

Alain.

[james.curran]

Cmd responce is

IP ROUTE 156.52.42.0

    ^

The 2820 is a switch and does not allow routing statements evidently. I have looked everyware on the menu and typed the cmd with no acceptance.

The 2920 does see the 1700 router and responds to the 192.9.100.194 ip on the vlan 1 port 4. It does not see the 152.52.42.194 segment on port Fastethernet0 on the 1711.  Using CDP shows connection between the 1711 and this 2920.

Sorry for the delay in responding but the system can only be accessed from a secure terminal - many many many feet away.

[cadet alain]

Hi,

I thought it was a 28xx serie router not a switch, I had never heard of this switch model  before.

Regards.

Alain.