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?
Are you getting an error message?
Are you trying to do static routing or OSPF?
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.
Also, other VLANs are routing as expected.
Can you provide a copy of your configuration?
Can you post the output of show ip route and show interface-config vlan 1?
Sure. Give me just a few minutes.
Here are the show commands:
(CSS_S1) #show ip route
Codes: C - connected, R - RIPO - OSPF, O(IA) - Ospf inter AreaO(E1) - OSPF Ext Type 1, O(E2) - Ospf Ext Type 2M - mgmt, S - static, * - candidate defaultD - DHCP
Gateway of last resort is 10.99.0.1 to network 0.0.0.0 at cost 39S * 0.0.0.0 /0  via 10.99.0.1S 10.10.0.0/16  via 10.255.254.10S 10.11.0.0/16  via 10.255.254.11S 10.12.0.0/16  via 10.255.254.12S 10.13.0.0/16  via 10.255.254.13S 10.14.0.0/16  via 10.255.254.14S 10.15.0.0/16  via 10.255.254.15S 10.16.0.0/16  via 10.255.254.16S 10.17.0.0/16  via 10.255.254.17S 10.18.0.0/16  via 10.255.254.18S 10.19.0.0/16  via 10.255.254.19S 10.20.0.0/16  via 10.255.254.20S 10.21.0.0/16  via 10.255.254.21S 10.22.0.0/16  via 10.255.254.22S 10.23.0.0/16  via 10.255.254.23S 10.24.0.0/16  via 10.255.254.24S 10.25.0.0/16  via 10.255.254.25S 10.26.0.0/16  via 10.255.254.26S 10.27.0.0/16  via 10.255.254.27S 10.28.0.0/16  via 10.255.254.28S 10.29.0.0/16  via 10.255.254.29S 10.30.0.0/16  via 10.255.254.30S 10.31.0.0/16  via 10.255.254.31S 10.32.0.0/16  via 10.255.254.32S 10.50.0.0/16  via 10.255.254.50
S 10.51.0.0/16  via 10.255.254.51S 10.52.0.0/16  via 10.255.254.52S 10.53.0.0/16  via 10.255.254.53S 10.54.0.0/16  via 10.255.254.54S 10.55.0.0/16  via 10.255.254.55S 10.56.0.0/16  via 10.255.254.56S 10.70.0.0/16  via 10.255.254.70S 10.71.0.0/16  via 10.255.254.71S 10.72.0.0/16  via 10.255.254.72S 10.73.0.0/16  via 10.255.254.73S 10.74.0.0/16  via 10.255.254.74S 10.75.0.0/16  via 10.255.254.75S 10.76.0.0/16  via 10.255.254.76S 10.96.0.0/16  via 10.255.254.96S 10.97.0.0/16  via 10.255.254.97S 10.98.0.0/16  via 10.255.254.98C 10.99.0.0/20 is directly connected: vlan1C 10.99.0.10/32 is directly connected: vlan1C 10.99.16.0/20 is directly connected: vlan2C 10.99.16.1/32 is directly connected: vlan2C 10.99.32.0/20 is directly connected: vlan3C 10.99.32.1/32 is directly connected: vlan3C 10.99.48.0/20 is directly connected: vlan4C 10.99.48.1/32 is directly connected: vlan4C 10.99.64.0/20 is directly connected: vlan5
C 10.99.64.1/32 is directly connected: vlan5C 10.99.255.0/24 is directly connected: vlan45C 10.99.255.1/32 is directly connected: vlan45C 10.255.254.0/24 is directly connected: vlan20C 10.255.254.99/32 is directly connected: vlan20
(CSS_S1) # show interface-config vlan 1
vlan "1"--------Parameter Value--------- -----Interface OSPF profile N/AInterface PIM profile N/AInterface IGMP profile N/AInterface shutdown Disabledmtu 1500IP Address 10.99.0.10/255.255.240.0IPv6 Address N/AIPv6 link local Address N/ADHCP client DisabledDHCP relay profile N/AInterface description N/A
Thanks for your help,
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.
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.
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.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.