03-15-2015 04:50 PM - edited 03-07-2019 11:06 PM
Dears,
Please check below configuration for my catalyst switch 3560. The hosts in VLAN 30 (10.0.30.5) can't ping hosts in VLAN 50 (10.0.50.5), however the hosts in VLAN 30 can ping interface VLAN 50 (10.0.50.1) and vice verse. please check configuration of the switch and let me know if you have any suggestions for such a problem.
03-15-2015 05:55 PM
I don't see a default route on the 3560.
Just by looking at the 3560 and not knowing your network topology, I would change the default router on the dhcp pool(vlan 30 & 50) to 10.0.30.1 & 10.0.50.1 and add a default route to your 3560.
ip route 0.0.0.0 0.0.0.0 x.x.x.x
HTH
03-15-2015 07:04 PM
Hosts in vlan 30 and vlan 50 do not have the correct default gateways defined in the dhcp pools:
ip dhcp pool V30
default-router 10.0.30.254
!
ip dhcp pool V50
default-router 10.0.50.254
!
!
interface Vlan30
ip address 10.0.30.1 255.255.255.0
!
interface Vlan50
ip address 10.0.50.1 255.255.255.0
03-15-2015 11:55 PM
Like the other two members said your default gateway is not matching with the Vlan interface ip
For example
Switch(config)# interface vlan10
Switch(config-if)# ip address 10.1.10.1 255.255.255.0
Switch(config)# ip dhcp pool example10
Switch(config-dhcp)# network 10.1.10.0 255.255.255.0
Switch(config-dhcp)# default-router 10.1.10.1
Please let us know to which Interface/Port are you host getting connected.
Please make sure both the host ports are on their respective Vlans (VLan 30 and VLan 50)
Switch(config)# interface gigabitethernet XX/0/ZZ
Switch(config-if)# switchport mode access
Switch(config-if)# switchport access vlan Number
Please try these and let us know if it is working or not for you.
03-16-2015 12:37 AM
Thanks All !!
Actually, I have shared an old configuration, actually, the default gateway in the DHCP pool is configured to 10.0.30.1 & 10.0.50.1 as shown in the edit configurations mentioned above, but I'm still facing the same problem that the hosts in different VLANs cannot communicate with each other.
Also, I don't care about a default gateway to be configured on the switch (ip route 0.0.0.0 0.0.0.0) as I want to make sure first that the intervlan routing between hosts is successful before let hosts access the Internet
Below the ports connected to the hosts:
03-16-2015 01:09 AM
Can you post the output of a show vlan brief?
03-16-2015 01:46 AM
CoreSwitch#show vlan brief
VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
1 default active Gi1/0/3, Gi1/0/4, Gi1/0/5
Gi1/0/6, Gi1/0/7, Gi1/0/8
Gi1/0/11, Gi1/0/12, Gi1/0/13
Gi1/0/15, Gi1/0/16, Gi1/0/17
Gi1/0/18, Gi1/0/19, Gi1/0/20
Gi1/0/21, Gi1/0/22, Gi1/1/1
Gi1/1/2, Gi1/1/3, Gi1/1/4
30 VLAN0030 active Gi1/0/1, Gi1/0/2
40 VLAN0040 active Gi1/0/9
50 VLAN0050 active Gi1/0/14
100 VLAN0100 active
1002 fddi-default act/unsup
1003 token-ring-default act/unsup
1004 fddinet-default act/unsup
1005 trnet-default act/unsup
CoreSwitch#
03-16-2015 02:08 AM
Are your vlan interfaces up?
Also, as you posted an older config earlier, can you attach the output of a show run please.
edit: Can you also confirm whether your hosts can ping their default gateway?
03-16-2015 02:49 AM
The vlan interfaces are up as shown below
CoreSwitch#show ip int br
Interface IP-Address OK? Method Status Protocol
Vlan1 10.0.100.100 YES NVRAM up up
Vlan30 10.0.30.1 YES manual up up
Vlan40 10.0.40.1 YES manual up up
Vlan50 10.0.50.1 YES manual up up
Vlan100 192.168.100.1 YES manual up up
GigabitEthernet0/0 unassigned YES unset down down
GigabitEthernet1/0/1 unassigned YES unset up up
GigabitEthernet1/0/2 unassigned YES unset down down
GigabitEthernet1/0/3 unassigned YES unset down down
GigabitEthernet1/0/4 unassigned YES unset down down
GigabitEthernet1/0/5 unassigned YES unset down down
GigabitEthernet1/0/6 unassigned YES unset down down
GigabitEthernet1/0/7 unassigned YES unset down down
GigabitEthernet1/0/8 unassigned YES unset down down
GigabitEthernet1/0/9 unassigned YES unset up up
GigabitEthernet1/0/10 unassigned YES unset up up
GigabitEthernet1/0/11 unassigned YES unset down down
GigabitEthernet1/0/12 unassigned YES unset down down
GigabitEthernet1/0/13 unassigned YES unset down down
GigabitEthernet1/0/14 unassigned YES unset up up
GigabitEthernet1/0/15 unassigned YES unset down down
GigabitEthernet1/0/16 unassigned YES unset down down
GigabitEthernet1/0/17 unassigned YES unset down down
GigabitEthernet1/0/18 unassigned YES unset down down
GigabitEthernet1/0/19 unassigned YES unset down down
GigabitEthernet1/0/20 unassigned YES unset down down
GigabitEthernet1/0/21 unassigned YES unset down down
GigabitEthernet1/0/22 unassigned YES unset down down
GigabitEthernet1/0/23 unassigned YES unset up up
GigabitEthernet1/0/24 unassigned YES unset up up
GigabitEthernet1/1/1 unassigned YES unset down down
GigabitEthernet1/1/2 unassigned YES unset down down
GigabitEthernet1/1/3 unassigned YES unset down down
GigabitEthernet1/1/4 unassigned YES unset down down
CoreSwitch#
Actually, I have edit the post and applied the recent configuration as shown above.
yes, the hosts can ping their gateways, and even the other gateways:
For example:
Host : 10.0.40.20
Can ping 10.0.40.1 & 10.0.50.1 but can'y ping host 10.0.50.8
03-16-2015 03:03 AM
Please let us know the Role of the machine which is using the ip address 10.0.50.8
03-16-2015 03:04 AM
Also paste output of interface GigabitEthernet1/0/14
show interface GigabitEthernet1/0/14 (connecting to 10.0.50.8)
03-16-2015 03:20 AM
CoreSwitch#show interfaces gigabitEthernet 1/0/14
GigabitEthernet1/0/14 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 64f6.9d2e.330e (bia 64f6.9d2e.330e)
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:07, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 33000 bits/sec, 42 packets/sec
5 minute output rate 614000 bits/sec, 72 packets/sec
1327137 packets input, 225172894 bytes, 0 no buffer
Received 12863 broadcasts (6643 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 6643 multicast, 0 pause input
0 input packets with dribble condition detected
1690262 packets output, 806816097 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
CoreSwitch#
03-16-2015 04:27 AM
From the output provided we can see that there is traffic passing through the interface.
you can see the packet output and packet input.
Last input 00:00:07, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 33000 bits/sec, 42 packets/sec
5 minute output rate 614000 bits/sec, 72 packets/sec
1327137 packets input, 225172894 bytes, 0 no buffer
Received 12863 broadcasts (6643 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 6643 multicast, 0 pause input
0 input packets with dribble condition detected
1690262 packets output, 806816097 bytes, 0 underruns
what is the role of this host machine for eg is it a windows/linux/ip phone,
because from the configuration side it looks good.. the interface and the Vlan.
03-16-2015 04:35 AM
As I mentioned before that the host (windows machine) connected to this port can reach 10.0.40.1, 10.0.50.1 which are gateways that's why you can see traffic, but the problem when a host in VLAN 50 want to reach host in VLAN 40 which is not working.
Any ideas ???
03-16-2015 04:44 AM
can you ping the windows machine from the switch ?
check the mac address and the arp request from the switch side.
just to make my understanding clear, none of the host on vlan 50 is able to reach any other vlan on the switch, the host on Vlan 50 is only able to reach the gateways of the respective Vlans
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