Wireless Access

last person joined: 6 minutes ago 

Access network design for branch, remote, outdoor and campus locations with Aruba access points, and mobility controllers.
Expand all | Collapse all

Routing VLAN 1 on S2500

Jump to Best Answer
  • 1.  Routing VLAN 1 on S2500

    Posted Apr 29, 2014 04:25 PM

    It appears that routing VLAN 1 on the S2500 is disabled by default. I'm guessing VLAN 1 may be the default management VLAN so routing is disabled for security reasons.

     

    Can someone verify and tell me how to change the management VLAN or other configuration so that I can route VLAN 1?

     

    Thanks,



  • 2.  RE: Routing VLAN 1 on S2500

    Posted Apr 29, 2014 04:28 PM

    Are you getting an error message?

     

    Are you trying to do static routing or OSPF?



  • 3.  RE: Routing VLAN 1 on S2500

    Posted Apr 29, 2014 04:32 PM

    I use static routes but these vlans are local to the switch so it creates the routes itself. I can't ping or access devices in other VLAN's. There's no error message, it simply behaves as there is no routing.

     

    I can successfully PING and access devices within VLAN 1.



  • 4.  RE: Routing VLAN 1 on S2500

    Posted Apr 29, 2014 04:34 PM

    Also, other VLANs are routing as expected.



  • 5.  RE: Routing VLAN 1 on S2500

    Posted Apr 29, 2014 04:40 PM

    Mark,

    Can you provide a copy of your configuration?

     

    Best regards,

     

    Madani



  • 6.  RE: Routing VLAN 1 on S2500

    Posted Apr 29, 2014 04:40 PM

    Can you post the output of show ip route and show interface-config vlan 1?



  • 7.  RE: Routing VLAN 1 on S2500

    Posted Apr 29, 2014 04:42 PM

    Sure. Give me just a few minutes.



  • 8.  RE: Routing VLAN 1 on S2500

    Posted Apr 29, 2014 04:52 PM

    Here are the show commands:

     

    (CSS_S1) #show ip route

    Codes: C - connected, R - RIP
    O - OSPF, O(IA) - Ospf inter Area
    O(E1) - OSPF Ext Type 1, O(E2) - Ospf Ext Type 2
    M - mgmt, S - static, * - candidate default
    D - DHCP

    Gateway of last resort is 10.99.0.1 to network 0.0.0.0 at cost 39
    S * 0.0.0.0 /0 [39] via 10.99.0.1
    S 10.10.0.0/16 [0] via 10.255.254.10
    S 10.11.0.0/16 [0] via 10.255.254.11
    S 10.12.0.0/16 [0] via 10.255.254.12
    S 10.13.0.0/16 [0] via 10.255.254.13
    S 10.14.0.0/16 [0] via 10.255.254.14
    S 10.15.0.0/16 [0] via 10.255.254.15
    S 10.16.0.0/16 [0] via 10.255.254.16
    S 10.17.0.0/16 [0] via 10.255.254.17
    S 10.18.0.0/16 [0] via 10.255.254.18
    S 10.19.0.0/16 [0] via 10.255.254.19
    S 10.20.0.0/16 [0] via 10.255.254.20
    S 10.21.0.0/16 [0] via 10.255.254.21
    S 10.22.0.0/16 [0] via 10.255.254.22
    S 10.23.0.0/16 [0] via 10.255.254.23
    S 10.24.0.0/16 [0] via 10.255.254.24
    S 10.25.0.0/16 [0] via 10.255.254.25
    S 10.26.0.0/16 [0] via 10.255.254.26
    S 10.27.0.0/16 [0] via 10.255.254.27
    S 10.28.0.0/16 [0] via 10.255.254.28
    S 10.29.0.0/16 [0] via 10.255.254.29
    S 10.30.0.0/16 [0] via 10.255.254.30
    S 10.31.0.0/16 [0] via 10.255.254.31
    S 10.32.0.0/16 [0] via 10.255.254.32
    S 10.50.0.0/16 [0] via 10.255.254.50


    Codes: C - connected, R - RIP
    O - OSPF, O(IA) - Ospf inter Area
    O(E1) - OSPF Ext Type 1, O(E2) - Ospf Ext Type 2
    M - mgmt, S - static, * - candidate default
    D - DHCP

    S 10.51.0.0/16 [0] via 10.255.254.51
    S 10.52.0.0/16 [0] via 10.255.254.52
    S 10.53.0.0/16 [0] via 10.255.254.53
    S 10.54.0.0/16 [0] via 10.255.254.54
    S 10.55.0.0/16 [0] via 10.255.254.55
    S 10.56.0.0/16 [0] via 10.255.254.56
    S 10.70.0.0/16 [0] via 10.255.254.70
    S 10.71.0.0/16 [0] via 10.255.254.71
    S 10.72.0.0/16 [0] via 10.255.254.72
    S 10.73.0.0/16 [0] via 10.255.254.73
    S 10.74.0.0/16 [0] via 10.255.254.74
    S 10.75.0.0/16 [0] via 10.255.254.75
    S 10.76.0.0/16 [0] via 10.255.254.76
    S 10.96.0.0/16 [0] via 10.255.254.96
    S 10.97.0.0/16 [0] via 10.255.254.97
    S 10.98.0.0/16 [0] via 10.255.254.98
    C 10.99.0.0/20 is directly connected: vlan1
    C 10.99.0.10/32 is directly connected: vlan1
    C 10.99.16.0/20 is directly connected: vlan2
    C 10.99.16.1/32 is directly connected: vlan2
    C 10.99.32.0/20 is directly connected: vlan3
    C 10.99.32.1/32 is directly connected: vlan3
    C 10.99.48.0/20 is directly connected: vlan4
    C 10.99.48.1/32 is directly connected: vlan4
    C 10.99.64.0/20 is directly connected: vlan5


    Codes: C - connected, R - RIP
    O - OSPF, O(IA) - Ospf inter Area
    O(E1) - OSPF Ext Type 1, O(E2) - Ospf Ext Type 2
    M - mgmt, S - static, * - candidate default
    D - DHCP

    C 10.99.64.1/32 is directly connected: vlan5
    C 10.99.255.0/24 is directly connected: vlan45
    C 10.99.255.1/32 is directly connected: vlan45
    C 10.255.254.0/24 is directly connected: vlan20
    C 10.255.254.99/32 is directly connected: vlan20

     

     

    (CSS_S1) # show interface-config vlan 1

    vlan "1"
    --------
    Parameter Value
    --------- -----
    Interface OSPF profile N/A
    Interface PIM profile N/A
    Interface IGMP profile N/A
    Interface shutdown Disabled
    mtu 1500
    IP Address 10.99.0.10/255.255.240.0
    IPv6 Address N/A
    IPv6 link local Address N/A
    DHCP client Disabled
    DHCP relay profile N/A
    Interface description N/A

     

    Thanks for your help,



  • 9.  RE: Routing VLAN 1 on S2500
    Best Answer

    Posted Apr 29, 2014 05:28 PM

    Mark,

    Just an observation, your vlan 1 interface is a .10 while all your other vlans are .1. Just want to make sure your client DGs on VLAN 1 are correct.

     

    Best regards,

     

    Madani



  • 10.  RE: Routing VLAN 1 on S2500

    Posted Apr 29, 2014 08:07 PM

    This is just a test configuration. I can't remember why I selected .10 but my client IP's are in range. The vlan network is 10.99.0.0 /20 so my range is from 10.99.0.1 through 10.99.15.255.

     

    I can put a client on VLAN 3 and can't PING the gateway to VLAN 1.

    If I have a client in VLAN 1, I can PING the VLAN 1 gateway but can't ping other VLAN gateways.



  • 11.  RE: Routing VLAN 1 on S2500

    Posted Apr 29, 2014 08:12 PM

    Sometimes it's the dumbest things. I'm not at work so will have to verify tomorrow.

     

    I'm pretty sure my manual IP settings on the client had .1 rather than .10 as the gateway. Traffic won't go far without an appropriate gateway.

     

    Thanks everyone!!!!