01-06-2014 09:02 AM - edited 07-04-2021 11:53 PM
Hi,
In one of our factory, there are handheld scanning devices which work over wireless to move data over to end servers.
The setup has two-5508 WLC in HA mode, about few 1500 series & 3500 series AP's.
handheld device is assigned an ip address & connected using copper cable to the ethernet port of 3502.
The 3502 here is functioning as a work bridge & connects to either other 3502/1500 which act as normal mesh AP's.
3502 shows connectivity to the wireless & back end infrastructure, however the handheld device can not be communicated from within our network.
Is there any special configuration required for this. Please help with suggestions.
Thanks in advance.
01-06-2014 09:37 AM
you may need to go and disable the IP mac binding
config network mac-ip-binding disable
HTH,
Steve
------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered
01-06-2014 10:31 AM
Pls provide the below output from your WLC
(WLC) >show wgb summary
(WLC) >show wgb detail
Other APs you mentioned are in MESH mode or LOCAL mode ?
Rasika
01-06-2014 05:06 PM
Thanks Steve & Rasika.
I'll get these outputs from the local folks & present it here.
Another thing to note is , the scanner ip can be pinged from within the bridge itself, but it can't be from the local network infrastructure. All Ap's are in mesh mode. Below is the configuration from a bridge that is used for this purpose.
we tried adding static arp entry on to the bridge itself, it works for sometimes but then stops.
WGB-FCT01#sh run
Building configuration...
Current configuration : 3333 bytes
!
! Last configuration change at 00:14:50 UTC Fri Mar 1 2002
version 15.2
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname WGB-FCT01
no aaa new-model
no ip routing
no ip cef
!
dot11 syslog
!
dot11 ssid FCT
authentication open
authentication key-management wpa version 2
wpa-psk ascii 7 xxxxxxx
!
!
dot11 guest
!
!
crypto pki trustpoint TP-self-signed-1702352480
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-1702352480
revocation-check none
rsakeypair TP-self-signed-1702352480
!
!
crypto pki certificate chain TP-self-signed-1702352480
certificate self-signed 01
3082022B 30820194 A0030201 02020101 300D0609 2A864886 F70D0101 05050030
31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
69666963 6174652D 31373032 33353234 3830301E 170D3032 30333031 30303136
35325A17 0D323030 31303130 30303030 305A3031 312F302D 06035504 03132649
4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D31 37303233
35323438 3030819F 300D0609 2A864886 F70D0101 01050003 818D0030 81890281
8100B8B0 03A52013 F4A279F0 7DC7C475 5E8B771A 6CD17488 4284CC9E 7CBD5EC4
A289EE48 668D3CE4 235DE1D0 2808058B 0EDDDE6B 173B200D F76B5CB7 B407BB90
60362339 34093203 E210C398 20D97B1F 64964273 B98F0B47 76DFF5AF DFE68C17
A36AD17A 0D32C043 FD430335 5D81B057 8C4EBB21 465D60AC E4C44A71 5EE824AB
AF550203 010001A3 53305130 0F060355 1D130101 FF040530 030101FF 301F0603
551D2304 18301680 14402E0D E6557607 6BC21EA3 409EA489 ECF4A734 BF301D06
03551D0E 04160414 402E0DE6 5576076B C21EA340 9EA489EC F4A734BF 300D0609
2A864886 F70D0101 05050003 8181003B 41C57C42 C1FF4894 A737EE62 26EBB3BD
7BB72DE6 FC76FA74 BE37655A E8CB4F3C 720BC72F 07F27FF2 52C6158C 0878D5D3
2B03ED70 35B32E8C 4B95862F D80FECA5 C1AC328E 74AA6595 53BCDB9D 281CDC2C
71035CEC 6003770A E91BDEFD 776692D1 8BAD98DC E12A3D48 BA84E30C 921F1FD2
01EF4D66 8B7DA134 956AABBB 784140
quit
!
!
bridge irb
!
!
!
interface Dot11Radio0
no ip address
no ip route-cache
!
encryption mode ciphers aes-ccm
!
ssid FCT
!
antenna gain 0
parent timeout 20
station-role workgroup-bridge
bridge-group 1
bridge-group 1 spanning-disabled
!
interface Dot11Radio1
no ip address
no ip route-cache
shutdown
!
encryption mode ciphers aes-ccm
antenna gain 0
peakdetect
no dfs band block
channel dfs
station-role root
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 spanning-disabled
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
!
interface GigabitEthernet0
no ip address
no ip route-cache
duplex auto
speed auto
bridge-group 1
bridge-group 1 spanning-disabled
!
interface BVI1
ip address 192.168.100.55 255.255.255.0
no ip route-cache
ipv6 address dhcp
ipv6 address autoconfig
ipv6 enable
!
ip default-gateway 192.168.100.254
ip forward-protocol nd
ip http server
ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
!
!
bridge 1 route ip
!
!
!
line con 0
line vty 0 4
login local
transport input all
!
end
WGB-FCT01#
WGB-FCT01#sh ip int brie
Interface IP-Address OK? Method Status Protocol
BVI1 192.168.100.101 YES NVRAM up up
Dot11Radio0 unassigned YES NVRAM up up
Dot11Radio1 unassigned YES NVRAM administratively down down
GigabitEthernet0 unassigned YES NVRAM up up
Virtual-Dot11Radio0 unassigned YES unset up up
appreciate all help.
01-07-2014 08:05 AM
Here are the outputs,
sho wgb summa
bc:17:55:67:d4:40 192.168.100.101 AP-Root02 Assoc 1 Yes 802.11n(2.4 GHz) 0
show wgb detail bc:17:55:67:d4:40
Number of wired client(s): 0
AP-Root2 refers to the root ap to which this bridge associates itself.
Appreciate all help.
01-07-2014 12:35 PM
Hi
I suspect compatibility issue with mesh mode AP & WGB connection. I have not tested that & not sure whether it is working.
For testing is it possible to check your WGB with local mode AP & you should see the wired client in "show wgb detail" command as shown here
http://mrncciew.com/2013/06/16/unified-ap-wgb-with-multiple-vlan/
HTH
Rasika
**** Pls rate all useful responses ****
01-07-2014 01:09 PM
Later I found this, so definetely mesh mode AP should support this WGB arrangement. Refer this guide & see you follow the guidelines when setup WGB in this scenario
http://www.cisco.com/en/US/docs/wireless/technology/mesh/7.0/design/guide/MeshAP_70.html#wp1962965
HTH
Rasika
01-08-2014 07:09 AM
use mac filtering for wgb and wired clients behind wgb on wlc.
01-08-2014 07:32 AM
We tried the above steps, but it doesn't help.
is there any other things that we can see in this.
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