07-30-2018 07:32 AM - edited 03-08-2019 03:46 PM
Hello,
I have a VLAN created on the core switch first and assigned some ports on the Access switches, the ports or not functioning so then i started troubleshooting the issue then i found VLAN is not showing in the access switches so i matched the VTP version of the core with the access switch then it started showing it on Access switches, but the problem is i'm not able to ping the VLAN IP from different location and when i connect something to the port where the VLAN is configured i'm not getting the network. Please help me. Thanks
interface Vlan613
ip address 10.87.185.1 255.255.255.0
no ip redirects
no ip unreachables
no ip proxy-arp
end
07-30-2018 02:34 PM
In reading through the discussion again I want to go back to the post where you tell us that the access switch is able to ping the gateway. Can you tell us after the access switch has successfully pinged the gateway is the access switch able to ping the connected device in vlan 613?
Also can you tell us whether the core switch is able to ping the device connected on the access switch to vlan 613?
HTH
Rick
07-30-2018 10:55 AM
Can you configure a port on the Core Switch in access 613 and plug a host in and ping the gateway? another L3 SVI?
This will at least isolate the problem to the subnet/VLAN or to the access switch.
07-31-2018 01:06 AM - edited 07-31-2018 01:45 AM
Hello
Disable ip routing on the access switch and test again.
Please show vtp status from both core and access
res
Paul
07-31-2018 05:42 AM
Hello Ric,
The switch is in production will that effect if i disable the ip route?
following is the VTP status from core and access switch
Core switch
USRICSWCO001#sh vtp st
VTP Version capable : 1 to 3
VTP version running : 3
VTP Domain Name : USRIC
VTP Pruning Mode : Enabled
VTP Traps Generation : Enabled
Device ID : cc98.9160.ea80
Feature VLAN:
--------------
VTP Operating Mode : Primary Server
Number of existing VLANs : 18
Number of existing extended VLANs : 0
Maximum VLANs supported locally : 4096
Configuration Revision : 3
Primary ID : cc98.9160.ea80
Primary Description : USRICSWCO001
MD5 digest : 0xD3 0xB4 0x5A 0x89 0x81 0xEC 0xF1 0x78
0x94 0xEC 0x72 0x8B 0x0D 0x56 0x98 0xA1
Feature MST:
--------------
VTP Operating Mode : Transparent
Feature UNKNOWN:
--------------
VTP Operating Mode : Transparent
Access switch
USRICSWAC002#sh vtp st
VTP Version capable : 1 to 3
VTP version running : 3
VTP Domain Name : USRIC
VTP Pruning Mode : Enabled
VTP Traps Generation : Enabled
Device ID : cc98.9106.0e80
Feature VLAN:
--------------
VTP Operating Mode : Client
Number of existing VLANs : 18
Number of existing extended VLANs : 0
Maximum VLANs supported locally : 1005
Configuration Revision : 3
Primary ID : cc98.9160.ea80
Primary Description : USRICSWCO001
MD5 digest : 0xD3 0xB4 0x5A 0x89 0x81 0xEC 0xF1 0x78
0x94 0xEC 0x72 0x8B 0x0D 0x56 0x98 0xA1
Feature MST:
--------------
VTP Operating Mode : Transparent
Feature UNKNOWN:
--------------
VTP Operating Mode : Transparent
and my colleague told me that may be the subnet is not propagated on the router, how to check and how to propagate?Please help me. Thanks
07-31-2018 09:32 AM
We do not know enough about your environment to be sure whether disabling ip routing will impact things but it is certainly possible that it would have an impact. If this is a production environment I would be worried about disabling ip routing.
Can you answer these questions
Can you tell us after the access switch has successfully pinged the gateway is the access switch able to ping the connected device in vlan 613?
Also can you tell us whether the core switch is able to ping the device connected on the access switch to vlan 613?
HTH
Rick
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