Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Connectivity between Cisco Switch and Motorolla Wireless Switch

Posted on 2015-01-27
5
Medium Priority
?
527 Views
Last Modified: 2015-02-09
Hi, So this might be a silly question, and I am likely missing something really simple but I am having problems connecting to a device on a trunked port. So interface Gi4/1 on the cisco switch is currently a trunked port with 1 as the native vlan. The switch is installed in a CISCO catalyst 4510R chassis and the IP address is 172.17.252.1. I am trying to connect a motorolla wireless switch to this port. I have configured the wireless switch to use eth 2, I have set it to trunk as well with a native vlan of 1, tagging enabled, and allowed vlans 1,2, 10 and 15. The IP address on the interface is 172.17.252.102 and it's the management interface. Once I have done all that, I cannot ping the device from any machine on vlan 10, or from the cisco cli. I also cannot ping from cli of the motorolla device. I think I am missing something simple? Any info would be greatly appreciated.
0
Comment
Question by:Josh Rowe
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
5 Comments
 
LVL 3

Expert Comment

by:Stephen Berk
ID: 40581097
What's the output of "show int trunk" on the Cisco switch? How about "show int G4/1 sw"? If you can paste the interface configs also, that would help.
0
 

Author Comment

by:Josh Rowe
ID: 40583035
MO-4510-CR01>show int gi4/1 switchport
Name: Gi4/1
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Administrative Native VLAN tagging: enabled
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk Native VLAN tagging: enabled
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk private VLANs: none
Operational private-vlan: none
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL

Unknown unicast blocked: disabled
Unknown multicast blocked: disabled
Appliance trust: none
0
 

Author Comment

by:Josh Rowe
ID: 40583037
Port        Mode         Encapsulation  Status        Native vlan
Gi1/2       on           802.1q         trunking      1
Gi2/2       on           802.1q         trunking      1
Gi3/1       on           802.1q         trunking      1
Gi3/2       on           802.1q         trunking      1
Gi3/5       on           802.1q         trunking      1
Gi3/6       on           802.1q         trunking      1
Gi3/7       on           802.1q         trunking      1
Gi3/8       on           802.1q         trunking      1
Gi3/9       on           802.1q         trunking      1
Gi4/1       on           802.1q         trunking      1
Gi4/17      on           802.1q         trunking      1
Gi5/15      on           802.1q         trunking      1
Po1         on           802.1q         trunking      1
Po2         on           802.1q         trunking      1

Port        Vlans allowed on trunk
Gi1/2       1-4094
Gi2/2       1-4094
Gi3/1       1-4094
Gi3/2       1-4094
Gi3/5       1-4094
Gi3/6       1-4094
Gi3/7       1-4094
Gi3/8       1-4094
Gi3/9       1-4094
Gi4/1       1-4094
Gi4/17      1-4094
Gi5/15      1-4094
Po1         1-4094
Po2         1-4094

Port        Vlans allowed and active in management domain
Gi1/2       1-15
Gi2/2       1-15
Gi3/1       1-15
Gi3/2       1-15
Gi3/5       1-15
Gi3/6       1-15
Gi3/7       1-15
Gi3/8       1-15
Gi3/9       1-15
Gi4/1       1-15
Gi4/17      1-15
Gi5/15      1-15
Po1         1-15
Po2         1-15

Port        Vlans in spanning tree forwarding state and not pruned
Gi1/2       1-15
Gi2/2       1-15
Gi3/1       1-15
Gi3/2       1-15
Gi3/5       1-15
Gi3/6       1-15
Gi3/7       1-15
Gi3/8       1-15
Gi3/9       1-15
Gi4/1       1-15
Gi4/17      1-15
Gi5/15      1-15

Port        Vlans in spanning tree forwarding state and not pruned
Po1         1-15
Po2         1-15
0
 

Accepted Solution

by:
Josh Rowe earned 0 total points
ID: 40589906
So I have figured it out. Basically, in our troubleshooting we have somehow created multiple vlans on the device, causing it to not work. Nothing that overlaps, but it just wouldn't talk to the switch it was directly attached to. So I decided to reset the unit (steps in attached doc), and configure the switchport eth2 with the correct config following the steps in the other attached doc. Worked perfectly.
Factory-Reset-Motorola-Wireless-LAN-Swit
WS5100-CLI-vlan-configuration.doc
0
 

Author Closing Comment

by:Josh Rowe
ID: 40597942
Upon looking into the device more, we found a configuration that simply wasn't working. So we sourced information for resetting and re configuring the device. After which the device now works as we want it to.
0

Featured Post

Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article is a collection of issues that people face from time to time and possible solutions to those issues. I hope you enjoy reading it.
Make the most of your online learning experience.
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…

715 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question