Unsolved

This post is more than 5 years old

11323

January 8th, 2008 12:00

6024 Routing between VLANs on same switch

Hi, I have been trying to get routing between the current VLAN (1) and a new one I just created (10). I have given the switch an IP on both interfaces in the correct subnet , but show ip route gives only one network as directly connected. I can ping 192.168.1.253 from the router, but not 192.168.254.253. Strangely enough, from a port on vlan10 with an IP of 192.168.254.50 I can ping either.

console# sh ip route
Maximum Parallel Paths: 4 (4 after reset)

Codes: C - connected, S - static, R - RIP, O - OSPF, E - OSPF external

C 192.168.1.0/24 is directly connected vlan 1


From the config below, you can see vlan 10 is defined with IP 192.168.254.253.

Looking at
http://www.dellcommunity.com/supportforums/board/message?board.id=pc_managed&message.id=6193,
and reading
"So doing nothing more then just defining the IP addresses on those VLANs on the 6024 you actually created implicit routes on the 6024! So far you didn't even have to use the ip route command at all."

I think I have done everything correctly, what am I missing?


Router Configuration
-----------------------------

interface range ethernet g(23-24)
switchport mode general
exit
vlan database
vlan 10
exit
interface ethernet g23
switchport general pvid 2
exit
interface ethernet g24
switchport general pvid 2
exit
interface range ethernet g(17-22)
switchport access vlan 10
exit
interface vlan 1
ip address 192.168.1.253 255.255.255.0
exit
interface vlan 10
ip address 192.168.254.253 255.255.255.0
exit
router rip enable
management access-list SSH
permit service ssh
permit
exit
management access-class SSH
aaa authentication enable default line
aaa authentication login default line
line telnet
password BLAH encrypted
exit
line console
password BLAH encrypted
exit
enable password level 15 BLAH encrypted
username admin password BLAH level 15 encrypted
ip ssh server
ip ssh pubkey-auth


OOB host Configuration
-----------------------------

Empty configuration



Thanks in advance for any help,
Tom

PS I know the management ACL is too permissive, I messed it up in the web config and just enabled everything from the console while I fix this

Message Edited by thattommyhall on 01-08-2008 08:38 AM

Message Edited by thattommyhall on 01-08-2008 08:41 AM

184 Posts

January 9th, 2008 20:00

When you are having trouble pinging the second vlan, are there any devices connected to that second vlan? The vlan wont come up (niether will the routing interface) if there are no devices present in the vlan(the router doesnt count).
 

January 10th, 2008 06:00


@DRNO10 wrote:
When you are having trouble pinging the second vlan, are there any devices connected to that second vlan? The vlan wont come up (niether will the routing interface) if there are no devices present in the vlan(the router doesnt count).



Good point. There was, but now there isn't. Your post has made me realise that I have been very near a solution all along, just made a mistake by not troubleshooting thoroughly enough. I think it is some or all of of the following at different times during my frustrating few hours at the data centre:
  • Not being able to manage the switch from VLAN 10
  • Not having the switch as my default gateway (till we started using layer 3 features of the switch the pix was the default gateway)
  • Not having anything attached to VLAN10.


Thanks for the reply, I'll post back as soon as I can get down the data centre.

January 10th, 2008 19:00

Yep, that worked fine. Did not realise that the VLAN would go down when I unplugged my laptop. Just need to make sure you can administer the switch on all VLANs now.

Thanks for the prompting.

Tom
No Events found!

Top