- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 07:13 AM - edited 03-08-2019 04:13 PM
We have purchased a Cisco 3650 switch. The switch is working fine and I can access it through an IP address in the default VLAN but I am unable to access it through out management VLAN (254). I have 4 other Cisco 3560 switches that I can access just fine through 254 VLAN. I have allowed the 254 VLAN in the trunk but that didn't help. I am not sure what I am missing here.
Solved! Go to Solution.
- Labels:
-
LAN Switching
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-25-2018 11:50 AM
Hello
Are you able to wr erase that switch, delete its vlan.dat file and reload it then recreate the trunk and svi;s
wr erase
delete flash:vlan.dat
reload
..............
conf t
hostname ChangAn-SwitchInt5
vlan 254
exit
interface Vlan1
ip address 10.80.1.23 255.255.255.0
interface Vlan254
ip address 10.80.254.5 255.255.255.0
ip default-gateway 10.80.1.85
interface GigabitEthernet1/1/4
switchport trunk encapsulation dot1q
switchport mode trunk
no shut
Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.
Kind Regards
Paul

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 07:27 AM
Hello,
what is the difference between the working switches and this one ? Which template are you running (sh sdm prefer) ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 08:07 AM
other than switch model, I cant see any differences. As for the running template, it is the desktop default template for older switches and the advanced (low scale) template for the new one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 08:35 AM
Perhaps changing the default gateway of the switch to appropriate host on VLAN1 and not that of VLAN254 may have something to do with it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 09:50 AM
the default gateway is handled to route traffic from both VLANs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 09:30 AM
Hello
conf t
ip routing
ip route 0.0.0.0 0.0.0.0 10.80.254.1
Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.
Kind Regards
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 09:54 AM
Paul,
I've tried that but still not accessible through management VLAN.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 10:25 AM
Hello
apologies that wasn’t you core switch was it?
Can you post your core switch config and remove the ip routing I asked you to apply on that access switch
Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.
Kind Regards
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 10:31 AM
no worries, I have deleted the route and attached configuration of core switch.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 10:46 AM
Hello
Can you ping 10.80.254.5 fro the core?
Also looks like you have enable QinQ tunneling on sw5 - do you need it?
ChangAn-SwitchInt5
on interface GigabitEthernet1/1/4
no switchport mode dot1q-tunnel
Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.
Kind Regards
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 11:30 AM
Paul,
cannot ping 10.80.254.8 from core switch. I have enabled QinQ tunneling because I thought that I might need it for communication between 2 different model switches.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 11:44 AM - edited 09-24-2018 01:39 PM
Hello
Can you remove it and just create a normal trunk between core and L3 switch, then test again.
Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.
Kind Regards
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 12:03 PM
Paul,
I've already tried it with a normal trunk with the same result.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 12:53 PM - edited 09-24-2018 02:31 PM
Hello
I suspect one of the l3 interfaces are not active on one or both of the switches., can you post -
sh ip int brief | in Vlan
Also make sure the respective l2 vlans are created on each switch.
Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.
Kind Regards
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 01:34 PM
Adding @paul driver suggested, can you also post out of below command.
show interface status | in connected
