04-30-2013 11:30 AM - edited 03-07-2019 01:06 PM
Hi,
i need help since i still couldn't figure out how to get Inter-Vlan Routing Work.
i have 2 Cisco SG200 Switches 48 ports (ACCESS L2 SWITCH) and 1 SG300 8 ports (CORE L3 SWITCH) and a Cisco 1941 Router (EDGE Router and Firewall).
i have created a Vlan 50 on all of my switches then assigned the needed port to Vlan 50, and configured the uplink ports as Trunk ports then turned on the IP Routing on my L3 Switch to route between my native Vlan (Vlan 1) and the newly created Vlan (Vlan 50) but ping between subnets still not working knowing that the default gateway on the Vlan 50 PC is the L3 Switch IP address as per the screenshot below.
Please advise since i found lot of difference between cisco native IOS and those switches.
04-30-2013 12:00 PM
Hello
Can you post your switch configs?
Usually all what is required is:
L3 switch
Int vlan 1
IP address x.x.x. y.y.y.y
Int vlan 50
IP address x.x.x. y.y.y.y
Vlan 50
Exit
Ip routing
Int xxx (connecting to l2 switch)
Switchport trunk encap dot
Switchport mode trunk
No shut
L2 switch
Int vlan 1
IP address x.x.x. y.y.y.y
Ip default-gateway x.x.x.x
Int xxx (connecting to l3 switch)
Switchport trunk encap dot
Switchport mode trunk
No shut
Int xx (access port)
Switchport mode access
Switchport acces vlan 50
Res
Paul
Sent from Cisco Technical Support iPad App
04-30-2013 06:58 PM
SWITCH-L3#sh run
vlan database
vlan 50
exit
voice vlan oui-table add 0001e3 Siemens_AG_phone________
voice vlan oui-table add 00036b Cisco_phone_____________
voice vlan oui-table add 00096e Avaya___________________
voice vlan oui-table add 000fe2 H3C_Aolynk______________
voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
voice vlan oui-table add 00d01e Pingtel_phone___________
voice vlan oui-table add 00e075 Polycom/Veritel_phone___
voice vlan oui-table add 00e0bb 3Com_phone______________
interface vlan 50
ip address 172.16.10.1 255.255.255.0
exit
interface vlan 1
ip address 192.168.10.10 255.255.255.0
exit
interface vlan 1
no ip address dhcp
exit
bonjour interface range vlan 1
hostname SWITCH-L3
management access-list AllowMgmt
permit
exit
management access-list telnet
permit service telnet
exit
management access-class AllowMgmt
aaa authentication enable Console enable
aaa authentication enable SSH enable
aaa authentication enable Telnet enable
aaa authentication login Console local
aaa authentication login SSH local
aaa authentication login Telnet local
line telnet
login authentication Telnet
enable authentication Telnet
exit
line ssh
login authentication SSH
enable authentication SSH
exit
line console
login authentication Console
enable authentication Console
exit
lege 15
ip ssh server
no snmp-server server
ip name-server 192.168.10.2 192.168.10.5
ip telnet server
banner login ^C
***********************************
Unauthorized access prohibited
^C
macro auto processing type host enabled
macro auto processing type router enabled
interface gigabitethernet1
switchport mode access
exit
interface gigabitethernet2
switchport mode access
exit
interface gigabitethernet3
switchport mode access
exit
interface gigabitethernet4
switchport mode access
exit
interface gigabitethernet5
switchport mode access
exit
interface gigabitethernet6
switchport mode access
exit
interface gigabitethernet7
switchport mode access
exit
interface gigabitethernet8
switchport mode access
exit
interface gigabitethernet9
switchport trunk allowed vlan add 50
exit
interface vlan 50
name Servers
exit
SWITCH-L3#
04-30-2013 07:30 PM
please check the screenshot below.
from the L3 switch i can ping all my internal resources (Servers, Printers, etc ...within the subnet 192.168.10.0/24)
from my VLAN 50 PC i can ping the L3 Switch on its both Vlan's (Vlan1 and Vlan50)
so the route is pretty clear now, but since i can reach the L3 Switch and the L3 Switch can reach all my internal network IP's why can't my VLAN 50 PC Ping the internal network (Servers, Printers, etc...) that is already pingable by the L3 Switch ?
04-04-2015 06:09 PM
how did you fixed it? I have the same problem
05-01-2013 05:14 AM
Fixed.
it was a routing issue.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide