Options

Inter Vlan Routing (SVI). Can you spot a problem?

daniel280187daniel280187 Member Posts: 37 ■■□□□□□□□□
Hi guys,

I am setting up a basic a Inter Vlan Scenario but I am having a problem with my VLAN 50.

I managed for all the Vlans to communicate between each other except VLAN 50. I reckon that there might be a problem in the Routing Process for this VLAN since the host in Vlan 50 is able to ping its gateway but it is not able reach any host outside its Subnet.

Can you please give me some ideas and the reasoning behind to troubleshoot.

I have already checked:

- IP Addressing (same Subnet)
- Vlan 50 is configured in the switch and already associate it to Fa 0/5 as an Access port.
-Routing table has all the subnets required to communicate
- Interface VLAN 50 is UP (Layer 1 and 2) and Interface FastE 0/5 is up as well (Layer 1 and 2)

This is the lab I am trying to Setup:




Please let me know if you need any additional information.


Thanks for your help.

Comments

  • Options
    DCDDCD Member Posts: 473 ■■■■□□□□□□
    If you use the appropriate show command it would easy to troubleshoot. From the information provided I would say user error.
  • Options
    daniel280187daniel280187 Member Posts: 37 ■■□□□□□□□□
    DCD wrote: »
    If you use the appropriate show command it would easy to troubleshoot. From the information provided I would say user error.

    Hi, here are some of the commands I used to Troubleshoot. Let me know if I missing an important one that might give us more information.



    SW1_MANC#sh ip route
    Gateway of last resort is not set


    172.16.0.0/20 is subnetted, 8 subnets
    C 172.16.16.0 is directly connected, Vlan10
    C 172.16.32.0 is directly connected, Vlan20
    C 172.16.48.0 is directly connected, Vlan30
    C 172.16.64.0 is directly connected, Vlan40
    C 172.16.80.0 is directly connected, Vlan50
    C 172.16.96.0 is directly connected, Vlan60
    C 172.16.112.0 is directly connected, Vlan70
    C 172.16.128.0 is directly connected, Vlan80


    SW1_MANC#sh ip int brief
    Interface IP-Address OK? Method Status Protocol

    FastEthernet0/1 unassigned YES unset up up

    FastEthernet0/2 unassigned YES unset up up

    FastEthernet0/3 unassigned YES unset up up

    FastEthernet0/4 unassigned YES unset up up

    FastEthernet0/5 unassigned YES unset up up

    FastEthernet0/6 unassigned YES unset up up

    FastEthernet0/7 unassigned YES unset up up

    FastEthernet0/8 unassigned YES unset up up

    FastEthernet0/9 unassigned YES unset down down
    .
    .
    .
    .
    Vlan1 unassigned YES unset administratively down down

    Vlan10 172.16.16.1 YES manual up up

    Vlan20 172.16.32.1 YES manual up up

    Vlan30 172.16.48.1 YES manual up up

    Vlan40 172.16.64.1 YES manual up up

    Vlan50 172.16.80.1 YES manual up up

    Vlan60 172.16.96.1 YES manual up up

    Vlan70 172.16.112.1 YES manual up up

    Vlan80 172.16.128.1 YES manual up up






    SW1_MANC#sh vlan brief


    VLAN Name Status Ports
    ----


    1 default active Fa0/9, Fa0/10, Fa0/11, Fa0/12
    Fa0/13, Fa0/14, Fa0/15, Fa0/16
    Fa0/17, Fa0/18, Fa0/19, Fa0/20
    Fa0/21, Fa0/22, Fa0/23, Fa0/24
    Gig0/1, Gig0/2
    10 VLAN10 active Fa0/1
    20 VLAN20 active Fa0/2
    30 VLAN30 active Fa0/3
    40 VLAN40 active Fa0/4
    50 VLAN50 active Fa0/5
    60 VLAN60 active Fa0/6
    70 VLAN70 active Fa0/7
    80 VLAN80 active Fa0/8

    Thanks again.
  • Options
    Syntax_ninja*Syntax_ninja* Member Posts: 8 ■□□□□□□□□□
    It appears that you have a typo for the default gateway on the pc.
  • Options
    daniel280187daniel280187 Member Posts: 37 ■■□□□□□□□□
    Thanks for taking the time!! Such a stupid mistake and was troubleshooting it for almost 2 hours haha. Really appreciate it mate.
  • Options
    DCDDCD Member Posts: 473 ■■■■□□□□□□
    Like Syntax_ninja said most likely the default gateway on the PC. Also could you add the router show interface brief and thePC iconfig as well.
  • Options
    seigexseigex Member Posts: 105
    Thanks for taking the time!! Such a stupid mistake and was troubleshooting it for almost 2 hours haha. Really appreciate it mate.

    If this bothered you, don't ever become a software engineer! 24 hours gone over a dumb mistake! :)
Sign In or Register to comment.