Puzzled! ... and that doesn't happen often!

DeathmageDeathmage Banned Posts: 2,496
in CCNA & CCENT
So I'm setting up OSPF in the lab and now the left/right side of my lab won't ping the farthest reaches of my network network, my gateway which lets say is 192.225.225.15 it's odd!!! However the 1721 has the correct routes and can ping the 192.225.225.0 range on all addresses and can ping every address deeper down into the switching fabric, but R3 and R4 can only ping as far as the 1721 and the 192.225.225.6 address which is static on the 1721, that's the farthest it will go... I'm perplexed because of the fact the 1721 can route perfectly fine and the 2600's are,by design, suppose to route to the 1721 which then routes it to the 192.225.225.0 subnet.

I've been looking it over for an hour now and I'm just not seeing it...

as shown below:



Also I'm going to attach my router configs maybe one of you talented guru's will see the problem and then I can see why it's broken!

So you guys know, when you read the information below, the 172.16.4.0/27 range is for OSPF, hence why the weight on the route is 110 and the default primary route has a weight of 10 (the default primary is 1 or blank, but for the sake of making it obvious I made them a weight of 10 so it's easier to read) - I'm sure I don't have OSPF fully configured yet, but it's a work in progress but it should still route over the primary route.


Cisco 1721:

Cisco-1721-Core>
Cisco-1721-Core>
Cisco-1721-Core>enable
Password:
Cisco-1721-Core#show config
Using 1116 out of 29688 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Cisco-1721-Core
!
boot-start-marker
boot-end-marker
!
enable secret 5 $1$i00D$l4ummZ8K22JkAVJq9ka1S1
!
no aaa new-model
ip cef
!
!
!
!
!
!
!
!
!
!
interface FastEthernet0
ip address 192.225.225.6 255.255.255.224
speed auto
!
interface Serial0
ip address 192.168.120.2 255.255.255.0
fair-queue
!
interface Serial1
ip address 192.168.130.5 255.255.255.0
fair-queue
!
ip route 0.0.0.0 0.0.0.0 192.225.225.15
ip route 172.16.7.0 255.255.255.0 192.168.120.1
ip route 172.16.8.0 255.255.255.0 192.168.130.6
ip route 192.168.102.0 255.255.255.0 192.168.120.1
ip route 192.168.104.0 255.255.255.0 192.168.120.1
ip route 192.168.106.0 255.255.255.0 192.168.130.6
ip route 192.168.108.0 255.255.255.0 192.168.130.6
ip route 192.168.120.0 255.255.255.0 192.168.120.1
ip route 192.168.130.0 255.255.255.0 192.168.130.6
ip route 192.225.225.0 255.255.255.224 192.225.225.15
!
no ip http server
no ip http secure-server
!
!
control-plane
!
!
line con 0
line aux 0
line vty 0 4
login
!
end



Cisco-1721-Core#
Cisco-1721-Core#
Cisco-1721-Core#ping 192.225.225.1



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.225.225.1, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 1/1/4 ms
Cisco-1721-Core#ping 192.225.225.1



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.225.225.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
Cisco-1721-Core#ping 192.225.225.5



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.225.225.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
Cisco-1721-Core#ping 192.225.225.15



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.225.225.15, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
Cisco-1721-Core#ping 192.168.130.5



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.130.5, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Cisco-1721-Core#
*Mar 2 00:24:09.831: %LINK-3-UPDOWN: Interface Serial1, changed state to up
*Mar 2 00:24:10.831: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
*Mar 2 00:24:34.455: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
*Mar 2 00:24:44.643: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
Cisco-1721-Core#
Cisco-1721-Core#ping 192.168.130.5



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.130.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 120/126/144 ms
Cisco-1721-Core#ping 192.168.130.6



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.130.6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 60/63/64 ms
Cisco-1721-Core#ping 192.168.120.2



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.120.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Cisco-1721-Core#ping 192.168.120.2



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.120.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Cisco-1721-Core#ping 192.168.120.1



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.120.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Cisco-1721-Core#
*Mar 2 00:28:38.815: %LINK-3-UPDOWN: Interface Serial0, changed state to up
*Mar 2 00:28:39.815: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to up
Cisco-1721-Core#ping 192.168.120.1



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.120.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 60/62/64 ms
Cisco-1721-Core#ping 192.168.120.2



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.120.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 120/126/140 ms
Cisco-1721-Core#ping 192.225.225.1



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.225.225.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
Cisco-1721-Core#ping 192.225.225.5



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.225.225.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
Cisco-1721-Core#ping 192.225.225.15



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.225.225.15, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
Cisco-1721-Core#


Cisco 2600 R3:

 Cisco-2600-R3>
Cisco-2600-R3>
Cisco-2600-R3>enable
Password:
Cisco-2600-R3#show config
Using 1909 out of 29688 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Cisco-2600-R3
!
boot-start-marker
boot-end-marker
!
enable secret 5 $1$Yams$xS86wm2z/aVZLJUwzcsWz/
enable password cisco
!
no aaa new-model
!
resource policy
!
no network-clock-participate slot 1
no network-clock-participate wic 0
ip cef
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
username ******** password 0 ****************
!
!
!
!
!
!
!
interface FastEthernet0/0
description To_Cisco-2950(LAN 1)
no ip address
speed auto
full-duplex
!
interface FastEthernet0/0.80
encapsulation dot1Q 80
ip address 172.16.7.9 255.255.255.0
!
interface FastEthernet0/0.100
encapsulation dot1Q 100
ip address 192.168.102.12 255.255.255.0
!
interface FastEthernet0/0.200
encapsulation dot1Q 200
ip address 192.168.104.12 255.255.255.0
!
interface Serial0/0
description To_Cisco-CORE-1721
ip address 192.168.120.1 255.255.255.0
fair-queue
clock rate 28800
!
interface Serial0/1
description OSPF to Cisco-2600-R4
ip address 172.16.4.7 255.255.255.224
fair-queue
clock rate 28800
!
ip route 0.0.0.0 0.0.0.0 192.225.225.6
ip route 192.168.102.0 255.255.255.0 172.16.7.10
ip route 192.168.104.0 255.255.255.0 172.16.7.10
ip route 192.168.106.0 255.255.255.0 192.168.120.2 10
ip route 192.168.106.0 255.255.255.0 172.16.4.8 110
ip route 192.168.108.0 255.255.255.0 192.168.120.2 10
ip route 192.168.108.0 255.255.255.0 172.16.4.8 110
ip route 192.168.130.0 255.255.255.0 192.168.120.2 10
ip route 192.168.130.0 255.255.255.0 172.16.4.8 110
ip route 192.225.225.0 255.255.255.224 192.168.120.2 10
ip route 192.225.225.0 255.255.255.224 172.16.4.8 110
!
!
ip http server
no ip http secure-server
!
!
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
!
!
line con 0
exec-timeout 5 30
line aux 0
line vty 0 4
password cisco
login local
line vty 5 15
password cisco
login local
!
!
end



Cisco-2600-R3#
Cisco-2600-R3#
Cisco-2600-R3#ping 192.225.225.6



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.225.225.6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 60/63/65 ms
Cisco-2600-R3#ping 192.225.225.5



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.225.225.5, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Cisco-2600-R3#ping 192.225.225.1



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.225.225.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Cisco-2600-R3#ping 192.225.225.15



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.225.225.15, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Cisco-2600-R3#ping 192.168.120.2



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.120.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 60/62/64 ms
Cisco-2600-R3#ping 192.168.120.1



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.120.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 124/127/140 ms
Cisco-2600-R3#ping 172.16.4.7



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.4.7, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 124/128/145 ms
Cisco-2600-R3#ping 172.16.4.8



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.4.8, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 60/62/64 ms
Cisco-2600-R3#

Cisco-2600-R4:

Cisco-2600-R4#
Cisco-2600-R4#show config
Using 1701 out of 29688 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Cisco-2600-R4
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
!
resource policy
!
no network-clock-participate slot 1
no network-clock-participate wic 0
ip cef
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface FastEthernet0/0
description To_Cisco-2950(LAN 2)
no ip address
speed auto
full-duplex
!
interface FastEthernet0/0.90
encapsulation dot1Q 90
ip address 172.16.8.9 255.255.255.0
!
interface FastEthernet0/0.300
encapsulation dot1Q 300
ip address 192.168.106.12 255.255.255.0
!
interface FastEthernet0/0.400
encapsulation dot1Q 400
ip address 192.168.108.12 255.255.255.0
!
interface Serial0/0
description To_Cisco-CORE-1721
ip address 192.168.130.6 255.255.255.0
fair-queue
clock rate 28800
!
interface Serial0/1
description OSPF to Cisco-2600-R3
ip address 172.16.4.8 255.255.255.224
fair-queue
!
ip route 0.0.0.0 0.0.0.0 192.225.225.15
ip route 192.168.102.0 255.255.255.0 192.168.130.5 10
ip route 192.168.102.0 255.255.255.0 172.16.4.7 110
ip route 192.168.104.0 255.255.255.0 192.168.130.5 10
ip route 192.168.104.0 255.255.255.0 172.16.4.7 110
ip route 192.168.106.0 255.255.255.0 172.16.8.10
ip route 192.168.108.0 255.255.255.0 172.16.8.10
ip route 192.168.120.0 255.255.255.0 192.168.130.5 10
ip route 192.168.120.0 255.255.255.0 172.16.4.7 110
ip route 192.225.225.0 255.255.255.224 192.168.130.5 10
ip route 192.225.225.0 255.255.255.224 172.16.4.7 110
!
!
no ip http server
no ip http secure-server
!
!
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
!
!
line con 0
line aux 0
line vty 0 4
login
!
!
end



Cisco-2600-R4#
Cisco-2600-R4#
Cisco-2600-R4#ping 172.16.4.7



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.4.7, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 60/63/64 ms
Cisco-2600-R4#ping 172.16.4.8



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.4.8, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 124/138/196 ms
Cisco-2600-R4#ping 192.168.130.6



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.130.6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 120/123/125 ms
Cisco-2600-R4#ping 192.168.130.5



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.130.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 60/64/68 ms
Cisco-2600-R4#ping 192.225.225.1



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.225.225.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Cisco-2600-R4#ping 192.225.225.15



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.225.225.15, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Cisco-2600-R4#ping 192.225.225.6



Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.225.225.6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 60/63/64 ms
Cisco-2600-R4#
· Share on FacebookShare on Twitter

Comments

  • OfWolfAndManOfWolfAndMan Member Posts: 923 ■■■■□□□□□□
    There is no OSPF configured on any of these routers. All static routes. Please post the topology with appropriate subnets in a diagram.

    Also, why do you have Weighted Fair Queueing enabled on some of the interfaces? It won't do anything until you mark your traffic.
    :study:Reading: Lab Books, Ansible Documentation, Python Cookbook 2018 Goals: More Ansible/Python work for Automation, IPSpace Automation Course [X], Build Jenkins Framework for Network Automation []
    · Share on FacebookShare on Twitter
  • Switch1Switch1 Member Posts: 37 ■■□□□□□□□□
    How exactly did you configure your OSPF? Could you do a show ip protocols/show ip ospf on each Router? icon_silent.gif
    Currently Reading :study:
    100-101 ICND1 Official Cert Guide
    CCNA in 60 Days
    CCENT Study Guide Exam 100-101
    OSPF: Anatomy of an Internet Routing Protocol
    · Share on FacebookShare on Twitter
  • mikeybinecmikeybinec Member Posts: 484 ■■■□□□□□□□
    I didn't closely look at your running config but the if the static routes point to your distant networks, they would be installed in the routing table instead of the OSPF routes because of the admin cost being better.

    Also, this looks like a flapping interface. (maybe check to see if clock rate is set):

    *Mar 2 00:24:09.831: %LINK-3-UPDOWN: Interface Serial1, changed state to up
    *Mar 2 00:24:10.831: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
    *Mar 2 00:24:34.455: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
    *Mar 2 00:24:44.643: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
    Cisco NetAcad Cuyamaca College
    A.S. LAN Management 2010 Grossmont College
    B.S. I.T. Management 2013 National University
    · Share on FacebookShare on Twitter
  • DeathmageDeathmage Banned Posts: 2,496
    I did state in the message in the last sentence of the last paragraph that OSPF isn't finished yet icon_wink.gif
    mikeybinec wrote: »
    I didn't closely look at your running config but the if the static routes point to your distant networks, they would be installed in the routing table instead of the OSPF routes because of the admin cost being better.

    Also, this looks like a flapping interface. (maybe check to see if clock rate is set):

    *Mar 2 00:24:09.831: %LINK-3-UPDOWN: Interface Serial1, changed state to up
    *Mar 2 00:24:10.831: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up
    *Mar 2 00:24:34.455: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to down
    *Mar 2 00:24:44.643: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up

    as for flapping, it would be flapping if the serial cable was firmly attached, however I nudged it when I was moving the rack and I was lazy last night and never screwed it in, so it was partially secure, hence why the above ^^^^^^ looks like it's flapping because I was reseating the cable. icon_wink.gif
    OfWolfAndMan wrote: »
    There is no OSPF configured on any of these routers. All static routes. Please post the topology with appropriate subnets in a diagram.

    Also, why do you have Weighted Fair Queueing enabled on some of the interfaces? It won't do anything until you mark your traffic.

    see the main response in this post above, I just started working on OSPF, but I was going with the weighted routes, since for instance as far as I've learned so far in this cisco book:

    'ip route 192.168.108.0 255.255.255.0 192.168.4.2' has a default weight of 1 if it's not weighted

    ...if...

    'ip route 192.168.108.0 255.255.255.0 192.168.5.2 110' is used it has a weight of 110 which is the default weight for OSPF.

    so with that being said, I did state above I made the primary route a 10 and the failover route (OSPF) a weight on 110, my knowledge of routes is the lower the weighed number the higher the priority in the route. So with this being said if the route with a weight of 10 dies, traffic will then go over the next lowest, the one with the 110, which will be used for OSPF once I get to that point.

    However with this being said, I'm trying to figure out why the 1721 router won't route the traffic through it to the 192.225.225.0 subnet when the 2600's send traffic to the 1721 to pass along to my HP Procurve. As you can see the 1721 in the config above can ping 192.225.225.1 (Sonicwall), 192.225.225.15 (HP Procurve), and 192.225.225.5 (this PC)

    Again even though OSPF isn't finished, in my mind it still shouldn't prevent the 1721 from routing traffic through it from the 2600's to the next hop past the 1721 which is the Procurve. I have the Cisco lab blocked from outside contact by default on the Sonicwall, But again since the 1721 can access every device on the 192.225.225.0/27 subnet something else must be funky.

    if you look at the static routes on the 1721 there is a route 'ip route 192.225.225.0 255.255.255.224 192.225.225.15' (The IP address of 192.225.225.6 is on the Fastethernet0/0 on the 1721 and the next hop on that connection is 192.225.225.15 [the HP Procurve's IP]) so that should in essence allow traffic to be funneled to the Procurve and I can sent traffic from the 1721 to the Procurve without a problem, it's just the 2600's seem to have an issue, not sure if I'm missing something config wise or what...

    Here is a picture of it's physical layout (the white cable from the 1721 is the uplink to the Procurve:



    As far as a screenshot of the topology (since it won't let me attach a zip of the visio chart, here you go:



    at this point if OSPF is configured incorrectly, it no worries was going to make a OSPF area tomorrow and finalize OSPF, merely getting it to route traffic is what I'd like to figure out. The cabling is all wired correctly so it's literally a routing issue...

    Does this make sense so far?
    · Share on FacebookShare on Twitter
  • pevangelpevangel Member Posts: 342
    Does the procurve have a route to 192.168.x.x? Is 192.225.225.6 the default gateway of the PC?

    You really don't need that static route on the 1721 since it's directly connected.
    · Share on FacebookShare on Twitter
  • DeathmageDeathmage Banned Posts: 2,496
    pevangel wrote: »
    Does the procurve have a route to 192.168.x.x? Is 192.225.225.6 the default gateway of the PC?

    You really don't need that static route since on the 1721 since it's directly connected.

    The default gateway of the 192.225.225.0 subnet is my Sonicwall (192.225.225.1), my PC is GW'd to the Sonicwall.

    Here is layout of the procurve (Picture 1), all routes go back to the IP address of 192.225.225.6; however for shits and giggles I'll added the 192.168.120.0/24 and 192.168.130.0/24 subnets into the procurve, I just don't think there needed though since that's past the 1721, here is a picture of the 120 and 130 (Picture 2) so you know what I'm referring too:

    Picture 1:



    Picture 2:

    · Share on FacebookShare on Twitter
  • EdTheLadEdTheLad Member Posts: 2,111 ■■■■□□□□□□
    After looking at your topology and configs it's clear that you don't understand networking basics, so my advice would be too work on a simple 3 router setup and learn how routing works.
    Without going into too much analysis, have the remote devices that you are trying to ping from R3 and R4 got a route back to 192.168.120.0 and 192.168.130.0 ?
    Networking, sometimes i love it, mostly i hate it.Its all about the $$$$
    · Share on FacebookShare on Twitter
  • DeathmageDeathmage Banned Posts: 2,496
    EdTheLad wrote: »
    After looking at your topology and configs it's clear that you don't understand networking basics, so my advice would be too work on a simple 3 router setup and learn how routing works.
    Without going into too much analysis, have the remote devices that you are trying to ping from R3 and R4 got a route back to 192.168.120.0 and 192.168.130.0 ?

    Yup, they have. I think I figured out the issue. I changed the IP scheme on the 2600 ' s but then didn't update the HP Procurve. I've figured out what happened, silly mistake but only takes one.

    Did a trace route and found the issue, slammed my head on the desk when I found it.

    I forgot to add:

    IP route 192.168.120.0 255.255.255.0 192.225.225.6
    ip route 192.168.130.0 255.255.255.0 192.225.225.6

    As soon as I did that whalla...

    As edthelad points out, the traffic would go to the Procurve but since there was no route back it failed.

    After thinking about it with a drawing on my sketch board on the wall it clicked. Lol this is what happens when I pick up my lab from 5 months ago...when the ICM class started in September I had just removed another 1721 from the layout that was mimicing a MLPS and I changed the IP scheme and then got sidetracked by VCP5-DCV and never finished the config changes on the Procurve!!!

    Thanks for all you're help everyone. Sometimes even I miss things. icon_smile.gif
    · Share on FacebookShare on Twitter
  • pevangelpevangel Member Posts: 342
    That only fixes the issue with pinging the Procurve from the 2600s. I bet pinging your PC (192.225.225.5) from the 2600s still doesn't work.
    · Share on FacebookShare on Twitter
  • DeathmageDeathmage Banned Posts: 2,496
    pevangel wrote: »
    That only fixes the issue with pinging the Procurve from the 2600s. I bet pinging your PC (192.225.225.5) from the 2600s still doesn't work.

    It works, the HP Procurve 2910al is a L3, the 192.225.225.5 is in the ARP table. No need to define it, I can ping as deep as the 4 2950's at L2 from my PC now.

    Oops I misread your post! ...let me try from the router to the PC.

    It's working, I wouldn't be able to ping to the 2950 ' s if it wasn't. But also because I setup the Sonicwall even though it's capable of routing, I pointed it to use the Procurve as the routing switch for the 192.225.225.0/27 subnet. If I didn't you're correct it wouldn't work, however if I was to do it a different way I could set my default gateway to 192.225.225.15 on my PC and since the GW of last resort on the Procurve is 192.225.225.1 it would still go out to the Internet. I'm just using the Sonicwall in the current manner for my VPN.

    Well now that figured out, going to see what other nifty things I can add. But I think for the rest of the night I'm just going to do subnetting.
    · Share on FacebookShare on Twitter
  • DeathmageDeathmage Banned Posts: 2,496
    Thanks everyone for your insight again, and EdtheLad, thanks for your criticism, I've gone back to the basic and did the Pearson Vue Simulator last night for 4 hours (picking up again today) while listening to Chris Bryant's videos over at udemy till 3 am. I'll get back on track with these before I dive deeper into this hardware-based lab. I honestly think I made it more complex than it needs to be for CCNA, but that's me, over-complicating things icon_wink.gif

    I honestly should have finished the changes 5 months ago before I started into VCP5-DCV, so that a situation like this could have been avoided, it's the problem when your doing so much all at once sometimes!

    Changed my Sonicwall configuration to fall back onto a different policy for VPN's, a little more work than I wanted to do, but I can route traffic more smoothly now with the procurve and the load on the TZ is a lot lower now.

    Anyways, Proof of Concept below:

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Windows\System32>ipconfig /all

    Windows IP Configuration

    Host Name . . . . . . . . . . . . : Trevor-PC
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter iSCSI LAN (NAS Connection):

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
    Physical Address. . . . . . . . . : 00-25-22-B2-0A-2D
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv4 Address. . . . . . . . . . . : 172.16.27.20(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.224
    Default Gateway . . . . . . . . . :
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Primary LAN:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Bigfoot Networks 2100 Killer Ethernet Controller
    Physical Address. . . . . . . . . : 00-19-03-04-37-A3
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv4 Address. . . . . . . . . . . : 192.225.225.5(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.224
    Default Gateway . . . . . . . . . : 192.225.225.15
    DNS Servers . . . . . . . . . . . : 167.206.10.178
    8.8.8.8
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter 6TO4 Adapter:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft 6to4 Adapter
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv6 Address. . . . . . . . . . . : 2002:c0e1:e105::c0e1:e105(Preferred)
    Default Gateway . . . . . . . . . :
    DNS Servers . . . . . . . . . . . : 167.206.10.178
    8.8.8.8
    NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{05DB3510-336A-4FFB-AFF9-2F7EA480B41A}:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{939984D7-5BDC-4632-8302-D4516164E4B4}:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    C:\Windows\System32>ipconfig /flushdns

    Windows IP Configuration

    Successfully flushed the DNS Resolver Cache.

    C:\Windows\System32>ipconfig /registerdns

    Windows IP Configuration

    Registration of the DNS resource records for all adapters of this computer has b
    een initiated. Any errors will be reported in the Event Viewer in 15 minutes.

    C:\Windows\System32>nslookup google.com
    Server: vdnssec1.srv.whplny.cv.net
    Address: 167.206.10.178

    Non-authoritative answer:
    Name: google.com
    Addresses: 2607:f8b0:4006:80a::1000
    167.206.145.89
    167.206.145.108
    167.206.145.109
    167.206.145.123
    167.206.145.93
    167.206.145.98
    167.206.145.119
    167.206.145.88
    167.206.145.118
    167.206.145.113
    167.206.145.99
    167.206.145.114
    167.206.145.84
    167.206.145.103
    167.206.145.104
    167.206.145.94


    C:\Windows\System32>nslookup worldofwarcraft.com
    Server: vdnssec1.srv.whplny.cv.net
    Address: 167.206.10.178

    Non-authoritative answer:
    Name: worldofwarcraft.com
    Address: 12.129.242.22


    C:\Windows\System32>ping 192.225.225.5

    Pinging 192.225.225.5 with 32 bytes of data:
    Reply from 192.225.225.5: bytes=32 time<1ms TTL=128

    Ping statistics for 192.225.225.5:
    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
    Control-C
    ^C
    C:\Windows\System32>ping 192.225.225.1

    Pinging 192.225.225.1 with 32 bytes of data:
    Reply from 192.225.225.1: bytes=32 time=2ms TTL=64
    Reply from 192.225.225.1: bytes=32 time<1ms TTL=64

    Ping statistics for 192.225.225.1:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 2ms, Average = 1ms
    Control-C
    ^C
    C:\Windows\System32>ping 192.225.225.15

    Pinging 192.225.225.15 with 32 bytes of data:
    Reply from 192.225.225.15: bytes=32 time=11ms TTL=255
    Reply from 192.225.225.15: bytes=32 time=1ms TTL=255
    Reply from 192.225.225.15: bytes=32 time=1ms TTL=255
    Reply from 192.225.225.15: bytes=32 time=1ms TTL=255

    Ping statistics for 192.225.225.15:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 11ms, Average = 3ms

    Ping statistics for :
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 11ms, Average = 3ms
    Control-C
    ^C
    C:\Windows\System32>ping 192.225.225.6

    Pinging 192.225.225.6 with 32 bytes of data:
    Reply from 192.225.225.6: bytes=32 time=1ms TTL=255
    Reply from 192.225.225.6: bytes=32 time=1ms TTL=255

    Ping statistics for 192.225.225.6:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms
    Control-C
    ^C
    C:\Windows\System32>ping 192.168.120.5

    Pinging 192.168.120.5 with 32 bytes of data:
    Control-C
    ^C
    C:\Windows\System32>ping 192.168.120.1

    Pinging 192.168.120.1 with 32 bytes of data:
    Reply from 192.168.120.1: bytes=32 time=39ms TTL=254
    Reply from 192.168.120.1: bytes=32 time=39ms TTL=254
    Reply from 192.168.120.1: bytes=32 time=39ms TTL=254

    Ping statistics for 192.168.120.1:
    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 39ms, Maximum = 39ms, Average = 39ms
    Control-C
    ^C
    C:\Windows\System32>ping 192.168.120.2

    Pinging 192.168.120.2 with 32 bytes of data:
    Reply from 192.168.120.2: bytes=32 time=1ms TTL=255
    Reply from 192.168.120.2: bytes=32 time=1ms TTL=255

    Ping statistics for 192.168.120.2:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms
    Control-C
    ^C
    C:\Windows\System32>ping 192.168.130.5

    Pinging 192.168.130.5 with 32 bytes of data:
    Reply from 192.168.130.5: bytes=32 time=1ms TTL=255
    Reply from 192.168.130.5: bytes=32 time=1ms TTL=255

    Ping statistics for 192.168.130.5:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms
    Control-C
    ^C
    C:\Windows\System32>ping 192.168.130.6

    Pinging 192.168.130.6 with 32 bytes of data:
    Reply from 192.168.130.6: bytes=32 time=39ms TTL=254
    Reply from 192.168.130.6: bytes=32 time=39ms TTL=254

    Ping statistics for 192.168.130.6:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 39ms, Maximum = 39ms, Average = 39ms
    Control-C
    ^C
    C:\Windows\System32>
    · Share on FacebookShare on Twitter
Sign In or Register to comment.