Multicast roaming

what is multicast roaming?

The below link wil explain u in depth..
http://www.cisco.com/en/US/docs/solutions/Enterprise/Mobility/emob41dg/ch6_Mcst.html#wp1010309
Lemme know if this answered ur question!!
Regards
Surendra

Similar Messages

  • Multicasting with a guest anchor configuration.

    Hi All
    First time posting. :-)
    I have a guest anchor controller in our DMZ servicing Apple devices. We are looking at options for using Apple TV to display/stream presentations from executive iPads and such. Since it uses bonjour (multicast) would I be able to utilize the new features available in 7.0.116.0 to implement this solution? I have 4 WiSM 1s servicing the headquarters building and one 4402 guest anchor. I believe this is possible based on the note in the document: VLAN Select and Multicast Optimization Features Deployment Guide; specifically the section:
    Note: In a Guest Tunneling scenario, roaming between export foreign and export foreign is supported. However, roaming between export foreign and export anchor is not supported with VLAN Select.
    In case of Auto Anchor:
    Clients joining a foreign WLC, which is exported to an anchor WLC and mapped to a interface group, will receive an IP address in round robin method inside the interface group.
    Clients joining a foreign WLC, which is exported to an anchor WLC and mapped to a interface only, will receive an IP address from that interface only.
    Clients roaming between two or more foreign controllers mapped to a single anchor WLC with an interface group configured will be able to maintain its IP address.
    Since I only have one guest anchor, I would assume based on this that I would fall under the export foreign - export foreign option and implementing this would be possible.
    Could someone advise?
    Thank you in advance!!

    Thank you for information, I have the same problem. So I made a search on EoIP tunnel and Multicast.
    http://www.cisco.com/en/US/products/ps6366/products_qanda_item09186a00808b4c61.shtml
    Q I have a guest tunneling, Ethernet over IP (EoIP) tunnel, configured between my 4400 Wireless LAN Controller (WLC), which acts as the anchor WLC, and several remote WLCs. Can this anchor WLC forward subnet broadcasts through the EoIP tunnel from the wired network to wireless clients associated with the remote controllers?
    A. No, the WLC 4400 does not forward IP subnet broadcasts from the wired side to the wireless clients across the EoIP tunnel. This is not a supported feature. Cisco does not support tunneling of subnet broadcast or multicast in guest access topology. Since the guest WLAN forces the client point of presence to a very specific location in the network, mostly outside the firewall, tunneling of subnet broadcast can be a security problem.
    unofortunately it seems that multicast over EoIP does not work.

  • 5508 MC with 3650 MA L2 roaming problem

    Hello,
    I am testing L2 roaming on an open SSID between 3650 (MA) and 2 x 5508 in SSO (MC).
    The output of the show wireless mobility summary on the 3650 is :
    3650-ERM-LT1#show wireless mobility summary
    Mobility Agent Summary:
    Mobility Role                                   : Mobility Agent
    Mobility Protocol Port                          : 16666
    Mobility Switch Peer Group Name                 : 3650-ERM-LT1
    Multicast IP Address                            : 0.0.0.0
    DTLS Mode                                       : Enabled
    Mobility Domain ID for 802.11r                  : 0x6549
    Mobility Keepalive Interval                     : 10
    Mobility Keepalive Count                        : 3
    Mobility Control Message DSCP Value             : 0
    Switch Peer Group Members Configured            : 1
    Central Management                              : Disabled
    Link Status is Control Link Status : Data Link Status
    The status of Mobility Controller:
    IP              Public IP            Link Status
    172.17.1.1      172.17.1.1           UP   : UP
    Switch Peer Group members:
    IP              Public IP            Data Link Status
    172.17.27.1     172.17.27.1          N/A
    The output of show mobility summary on 5508 is :
    (WLC5508-MAR-1) >show mobility summary
    New Mobility (Converged Access).................. Enabled
    Mobility Protocol Port........................... 16666
    Default Mobility Domain.......................... mobility
    Multicast Mode .................................. Disabled
    DTLS Mode ....................................... Enabled
    Mobility Domain ID for 802.11r................... 0x6549
    Mobility Keepalive Interval...................... 10
    Mobility Keepalive Count......................... 3
    Mobility Group Members Configured................ 1
    Mobility Control Message DSCP Value.............. 0
    Mobility Oracle.................................. Disabled
    Mobility MC public IP ........................... 172.17.1.1
    Mobility Oracle IP address ...................... 0.0.0.0
    Controllers configured in the Mobility Group
     IP Address       Public IP Address       Group Name         Multicast IP  MAC Address               Status
     172.17.1.1       172.17.1.1              mobility           0.0.0.0       f4:cf:e2:94:c0:00          Up
    Switch Peer Group Configuration:
      Switches configured in Switch Peer Group: 3650-ERM-LT1
     IP Address           Public IP Address    Status
        172.17.27.1           172.17.27.1          Up
    So the mobility domain ID is the same.
    The show wlan id :
    On 3650 :
    3650-ERM-LT1#sh run wlan testNXO
    wlan test 6 TEST
     no broadcast-ssid
     no mobility anchor sticky
     no security wpa
     no security wpa akm dot1x
     no security wpa wpa2
     no security wpa wpa2 ciphers aes
     session-timeout 1800
     no shutdown
    On 5508 :
    WLAN Identifier.................................. 6
    Profile Name..................................... test
    Network Name (SSID).............................. TEST
    Status........................................... Enabled
    Broadcast SSID................................... Disabled
    AAA Policy Override.............................. Disabled
    Exclusionlist Timeout............................ 60 seconds
    Session Timeout.................................. 1800 seconds
    User Idle Timeout................................ Disabled
    Sleep Client..................................... disable
    Sleep Client Timeout............................. 720 minutes
    User Idle Threshold.............................. 0 Bytes
    NAS-identifier................................... WLC5508-MAR-1
    CHD per WLAN..................................... Enabled
    I enabled fast-ssid-change on both side.
    So, on both side :
    - mobility domain and bridge domain ID are the same
    - WLAN settings are the same
    The coverage area for my test is OK.
    The wireless management interface on both 3650 and 5508 is on the same VLAN (172.17.0.0 /16).
    I test with android smartphone and windows laptop.
    The WLC version : 8.0.115.0
    The 3650 version : 03.07.00E
    Others elements to check ?
    From the config guide I don't see what I miss :
    http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3650/software/release/3se/mobility/configuration_guide/b_mobility_3se_3650_cg/b_mobility_3se_3650_cg_chapter_01001.html

    Going forward this setup not going to be supported. ie you cannot make 5508 (or AireOS) controller as MC for 3850/3650 MA. In AireOS 8.1 code this support is not there, so better to get a 5760 if you want a dedicated MC in converged access.
    Still you should be able to have roam between 5760 & 5508 set up in same mobility group.
    If you have to go ahead with this testing, first try to do it with single 5508 (without SSO) & see. I would suggest 3.6.2aE for 3650 ( 3.7 is latest, but there may be unknows issues)
    HTH
    Rasika
    *** Pls rate all useful responses ***

  • GUest WLAN with Anchor WLC - roaming problems

    Hello,
    my wireless network consists in 3 WLC 4402 which manage 40 APs.
    I have a fourth WLC which I installed on my DMZ for guest vlan anchoring and web autentication.
    Everiting works fine but I have a problem:
    If my client associates with an AP and then I authenticate I'm ready to make traffic. As soon as my client roams to an AP managed by a differnt WLC I need to authenticate again. If I roam back to the first AP i need to reauthenticate.
    In my guest WLAN I use WEB authentication provided by the internal web server of the Anchor WLC.
    Thnks everybody

    Here are the output of show mobility summary.
    The last WLC is the anchor.
    WLC1
    Symmetric Mobility Tunneling (current) .......... Disabled
    Symmetric Mobility Tunneling (after reboot) ..... Disabled
    Mobility Protocol Port........................... 16666
    Mobility Security Mode........................... Disabled
    Default Mobility Domain.......................... mob1
    Multicast Mode .................................. Disabled
    Mobility Domain ID for 802.11r................... 0x392f
    Mobility Keepalive Interval...................... 10
    Mobility Keepalive Count......................... 3
    Mobility Group Members Configured................ 2
    Mobility Control Message DSCP Value.............. 0
    Controllers configured in the Mobility Group
    MAC Address IP Address Group Name Multicast IP Sta
    tus
    00:23:04:7d:3e:e0 10.25.1.21 mob1 0.0.0.0 Up
    00:23:04:7d:73:20 10.20.1.21 mob1 0.0.0.0 Up
    WLC2
    Symmetric Mobility Tunneling (current) .......... Disabled
    Symmetric Mobility Tunneling (after reboot) ..... Disabled
    Mobility Protocol Port........................... 16666
    Mobility Security Mode........................... Disabled
    Default Mobility Domain.......................... mob1
    Multicast Mode .................................. Disabled
    Mobility Domain ID for 802.11r................... 0x392f
    Mobility Keepalive Interval...................... 10
    Mobility Keepalive Count......................... 3
    Mobility Group Members Configured................ 2
    Mobility Control Message DSCP Value.............. 0
    Controllers configured in the Mobility Group
    MAC Address IP Address Group Name Multicast IP Sta
    tus
    00:23:04:7d:3e:e0 10.25.1.21 mob1 0.0.0.0 Up
    00:23:04:7d:62:a0 10.20.1.22 mob1 0.0.0.0 Up
    WLC3
    Symmetric Mobility Tunneling (current) .......... Disabled
    Symmetric Mobility Tunneling (after reboot) ..... Disabled
    Mobility Protocol Port........................... 16666
    Mobility Security Mode........................... Disabled
    Default Mobility Domain.......................... mob1
    Multicast Mode .................................. Disabled
    Mobility Domain ID for 802.11r................... 0x392f
    Mobility Keepalive Interval...................... 10
    Mobility Keepalive Count......................... 3
    Mobility Group Members Configured................ 2
    Mobility Control Message DSCP Value.............. 0
    Controllers configured in the Mobility Group
    MAC Address IP Address Group Name Multicast IP Sta
    tus
    00:23:04:7d:3e:e0 10.25.1.21 mob1 0.0.0.0 Up
    00:23:04:7d:79:80 10.20.2.21 mob1 0.0.0.0 Up
    WLCAnchor
    (Cisco Controller) >show mobility summary
    Symmetric Mobility Tunneling (current) .......... Disabled
    Symmetric Mobility Tunneling (after reboot) ..... Disabled
    Mobility Protocol Port........................... 16666
    Mobility Security Mode........................... Disabled
    Default Mobility Domain.......................... mob1
    Multicast Mode .................................. Disabled
    Mobility Domain ID for 802.11r................... 0x392f
    Mobility Keepalive Interval...................... 10
    Mobility Keepalive Count......................... 3
    Mobility Group Members Configured................ 4
    Mobility Control Message DSCP Value.............. 0
    Controllers configured in the Mobility Group
    MAC Address IP Address Group Name Multicast IP Sta
    tus
    00:23:04:7d:3e:e0 10.25.1.21 mob1 0.0.0.0 Up
    00:23:04:7d:62:a0 10.20.1.22 mob1 0.0.0.0 Up
    00:23:04:7d:73:20 10.20.1.21 mob1 0.0.0.0 Up
    00:23:04:7d:79:80 10.20.2.21 mob1 0.0.0.0 Up

  • WLC L3 Roaming Using FlexConnect

    Hi everyone.
    A customer has a network with several buildings (each with a different VLAN/subnet), and a single WLC.
    The Access Points are grouped by AP groups, and on each building the clients are assigned to different VLANs.
    There is one single SSID with the users connect to on the entire campus, and it assigns (as expected) different ip address segments depending on which building the users are connecting into.
    The problem comes whenever a user is in a building and walks to another, since the buildings are not that far from each other, and the client machine is still connected to the network, it tries to roam but it doesn't know that it has to refresh its IP address.
    I know there's something that is not working here, but I can't find documentation about this. Is this a supported configuration? Is this an expected behaviour? How can I fix this?
    Thanks in advance for your help

    If you are using FlexConnect Local switching, then L3 roaming is unsupported feature.
    Here is some reference in the 7.6 configuration guide (see configuring FlexConnect section or page 926)
    http://www.cisco.com/c/dam/en/us/td/docs/wireless/controller/7-6/configuration/guide/b_cg76.pdf
    Here is another good reference about FlexConnect Design from a CiscoLive presentation.
    BRKEWN-2016 - Architecting Network for Branch Offices with CUWN
    As you can see on page 9, these are the advantages you get if you have a local WLC at your branch. L3 roaming is one
    * Cookie cutter configuration for every branch site 
    * Layer-3 roaming within the branch 
    * WGB support 
    * Reliable Multicast (filtering) 
    * IPv6 L3 Mobility 
    HTH
    Rasika
    **** Pls rate all useful responses. Each time you rate a response Cisco will donate $1 to Kiva ****

  • Multicast client on flexconnect AP

                       Hi !
    Is it possble for a client connected to a flexconnect AP to use multicast ?
    How do I enable that ? Will it be enough to enable Multicast VLAN on the SSID ?
    Apparently it do not work in default settings.
    My controller has no connection to the vlan my customer use for there clients. It is a pure
    flexconnect solution were WLC only handles management to the accesspoints.
    Mats Karlsson

    Hi, Saravanan
    The problem we faced is that Mac unable to discover printer via wireless LAN. Packet capture show that Mac2 sends MDNS query to 224.0.0.251 and printer sends MDNS reply to 224.0.0.251. But reply from printer is not coming to Mac2.
    Yes, all devices are in the same vlan (vlan 199), see topology enclosed. Vlan 199 is also allowed on all trunks from LAP to WLC. Currently IGMP snoping and multicast routing are disabled on all switches.
    WLC also have dynamic interface in vlan 199. AP manager interface is in vlan 101 and LAP BVI in vlan 124. Vlans 101 and 124 are being routed through L3 switch.
    Show wlan from WLC
    (Cisco Controller) >show wlan 3
    WLAN Identifier.................................. 3
    Profile Name..................................... wg-office-lan-201
    Network Name (SSID).............................. wg-office
    Status........................................... Enabled
    MAC Filtering.................................... Disabled
    Broadcast SSID................................... Enabled
    AAA Policy Override.............................. Enabled
    Network Admission Control
      Client Profiling Status ....................... Disabled
      Radius-NAC State............................... Disabled
      SNMP-NAC State................................. Disabled
      Quarantine VLAN................................ 0
    Maximum number of Associated Clients............. 0
    Maximum number of Clients per AP Radio........... 200
    Number of Active Clients......................... 62
    Exclusionlist.................................... Disabled
    Session Timeout.................................. Infinity
    CHD per WLAN..................................... Enabled
    Webauth DHCP exclusion........................... Disabled
    Interface........................................ office-wifi
    --More-- or (q)uit
    Multicast Interface.............................. Not Configured
    WLAN IPv4 ACL.................................... unconfigured
    WLAN IPv6 ACL.................................... unconfigured
    DHCP Server...................................... Default
    DHCP Address Assignment Required................. Disabled
    Static IP client tunneling....................... Disabled
    Quality of Service............................... Silver
    Scan Defer Priority.............................. 4,5,6
    Scan Defer Time.................................. 100 milliseconds
    WMM.............................................. Allowed
    WMM UAPSD Compliant Client Support............... Disabled
    Media Stream Multicast-direct.................... Disabled
    CCX - AironetIe Support.......................... Disabled
    CCX - Gratuitous ProbeResponse (GPR)............. Disabled
    CCX - Diagnostics Channel Capability............. Disabled
    Dot11-Phone Mode (7920).......................... Disabled
    Wired Protocol................................... None
    Passive Client Feature........................... Disabled
    Peer-to-Peer Blocking Action..................... Disabled
    Radio Policy..................................... 802.11b and 802.11g only
    DTIM period for 802.11a radio.................... 1
    DTIM period for 802.11b radio.................... 1
    Radius Servers
    --More-- or (q)uit
       Authentication................................ 10.128.0.101 1812
       Accounting.................................... 10.128.0.101 1813
          Interim Update............................. Disabled
       Dynamic Interface............................. Enabled
    Local EAP Authentication......................... Disabled
    Security
       802.11 Authentication:........................ Open System
       FT Support.................................... Disabled
       Static WEP Keys............................... Disabled
       802.1X........................................ Disabled
       Wi-Fi Protected Access (WPA/WPA2)............. Enabled
          WPA (SSN IE)............................... Disabled
          WPA2 (RSN IE).............................. Enabled
             TKIP Cipher............................. Disabled
             AES Cipher.............................. Enabled
                                                                   Auth Key Management
             802.1x.................................. Enabled
             PSK..................................... Disabled
             CCKM.................................... Disabled
             FT-1X(802.11r).......................... Disabled
             FT-PSK(802.11r)......................... Disabled
          FT Reassociation Timeout................... 20
    --More-- or (q)uit
          FT Over-The-DS mode........................ Enabled
          GTK Randomization.......................... Disabled
          SKC Cache Support.......................... Disabled
          CCKM TSF Tolerance......................... 1000
       Wi-Fi Direct policy configured................ Disabled
       EAP-Passthrough............................... Disabled
       CKIP ......................................... Disabled
       Web Based Authentication...................... Disabled
       Web-Passthrough............................... Disabled
       Conditional Web Redirect...................... Disabled
       Splash-Page Web Redirect...................... Disabled
       Auto Anchor................................... Disabled
       FlexConnect Local Switching................... Enabled
       FlexConnect Local Authentication.............. Enabled
       FlexConnect Learn IP Address.................. Enabled
       Client MFP.................................... Disabled
       Tkip MIC Countermeasure Hold-down Timer....... 60
    Call Snooping.................................... Disabled
    Roamed Call Re-Anchor Policy..................... Disabled
    SIP CAC Fail Send-486-Busy Policy................ Enabled
    SIP CAC Fail Send Dis-Association Policy......... Disabled
    KTS based CAC Policy............................. Disabled
    Band Select...................................... Disabled
    --More-- or (q)uit
    Load Balancing................................... Disabled
    Multicast Buffer................................. Disabled
    Mobility Anchor List
    WLAN ID     IP Address            Status
    802.11u........................................ Disabled
      Access Network type............................ Not configured
      Network Authentication type.................... Not configured
      Internet service............................... Disabled
      HESSID......................................... 00:00:00:00:00:00
    Hotspot 2.0.................................... Disabled
      WAN Metrics configuration
        Link status.................................. 0
        Link symmetry................................ 0
        Downlink speed............................... 0
        Uplink speed................................. 0
    Mobility Services Advertisement Protocol....... Disabled
    Saravanan Lakshmanan wrote:With local swtiching, Multicast traffic are still Multicast when it hits the AP from wired infrastructure, the AP encapsulates it on Unicast directed to that requesting client on that ssid/vlan.
    Do you mean that actually client recieve unicast packet with encapsulated multicast? but does it expect such packet from AP?
    Thanks
    BR, Ruslan

  • Airplay streams drop/skip when clients roam between Lightweight APs

    Hello,
    We are currently running a WLC2106 w/ 3 1131 APs and in areas where coverage over laps our client airplay streams are skipping. I think this is caused when the client (iphone/ipad) switches APs. All ap's are setup in local mode and should support fast roaming correct? I am thinking the multi-cast settings are not properly setup or my ap is not configured correctly?
    Controller --> General  Ap Multicast mode = multicast w/ 239.0.0.0 group address, broadcast forwarding enabled. 
    enable global multicast mode, and enable igmp snooping are both checked.
    Data rates on apps 1-11mbps disabled, 12 mandatory and all greater rates supported. P2p blocking action disabled
    Thanks for the help!

    We have two WLANS one with WPA2 PSK the other with WPA2 Auth 802.1X. The airplay devices are on the WPA2 SSID and the clients on the 802.1x, both go to the same vlan. Should I move all clients to the WPA2 SSID?
    Thanks for the response,
    David

  • Roaming issue

    Users complain that wireless device would lost wireless network connection when they moved from one AP coverage to another AP coverage.  They have to reconnect to the wireless network again.
    In our wireless environment, all APs are connecting to a single loacl controller which anchor to two remote controllers.  WLC 5508 with 7.2.11.3.
    Thanks,

    Configuring Client Roaming
    The Cisco UWN Solution supports seamless client roaming across lightweight access points managed by the same controller, between controllers in the same mobility group on the same subnet, and across controllers in the same mobility group on different subnets. Also, in controller software release 4.1 or later releases, client roaming with multicast packets is supported.
    You can adjust the default RF settings (RSSI, hysteresis, scan threshold, and transition time) to fine-tune the operation of client roaming using the controller GUI or CLI.
    CCX Layer 2 Client Roaming
    The controller supports five CCX Layer 2 client roaming enhancements:
    •Access point assisted roaming—This feature helps clients save scanning time. When a CCXv2 client associates to an access point, it sends an information packet to the new access point listing the characteristics of its previous access point. Roaming time decreases when the client recognizes and uses an access point list built by compiling all previous access points to which each client was associated and sent (unicast) to the client immediately after association. The access point list contains the channels, BSSIDs of neighbor access points that support the client's current SSID(s), and time elapsed since disassociation.
    • Enhanced neighbor list—This feature focuses on improving a CCXv4 client's roam experience and network edge performance, especially when servicing voice applications. The access point provides its associated client information about its neighbors using a neighbor-list update unicast message.
    • Enhanced neighbor list request (E2E)—The End-2-End specification is a Cisco and Intel joint program that defines new protocols and interfaces to improve the overall voice and roaming experience. It applies only to Intel clients in a CCX environment. Specifically, it enables Intel clients to request a neighbor list at will. When this occurs, the access point forwards the request to the controller. The controller receives the request and replies with the current CCX roaming sublist of neighbors for the access point to which the client is associated.
    For more information you can refer the following link-
    http://www.cisco.com/en/US/docs/wireless/controller/7.0/configuration/guide/c70ccfg.html#wp1098538

  • WLSM for L3 roaming

    Dear Sir,
    I would like your help on the following questions,
    1) Can I have redundancy if I have two Sup720 in two separate Cat 6000 but only one WLSM? What happens to the tunnel if the primary Sup720 fails? Can the WLSM establish/communicate to the second Sup720 on another Cat 6000
    2) How to implement and configure if I have 2 Cat 6000 with one unit of Sup720 and one unti of WLSM installed at each chassis?
    3) How should the interface tunnel be created if I have 2 Cat 600 with Sup720 and WLSM installed? Must I have same interface tunnel created on the Sup720 as we are allowed to put in one WDS IP address on the infrastructure AP?
    4) How is load balance of tunnel being handled by the Sup720 ? Any limitations?
    5) How HSRP is configured on second WLSM since tunnel is created in Sup720? What are the commands required to do so?
    6) What is the switchport configuration that connects to an AP to have L3 roaming using WLSM as WDS?
    7) I understand that native VLAN to the AP is used to establish the tunnel to the Sup720 and each AP across the campus should have an SSID map to a network-ID which corresponds to the tunnel created, can I have different subnet to the native VLAN across the campus but still have L3 roaming via WLSM-WDS device?
    8) If I configure a switchport that connects to an AP as VLAN 20 and another switchport as VLAN 30 to another AP,
    Both AP have the same SSID map to the same network-ID, can L3 roaming work? If not, what shall I do?
    Thank you,
    Delon

    1) Can I have redundancy if I have two Sup720 in two separate Cat 6000 but only one WLSM? What happens to the tunnel if the primary Sup720 fails? Can the WLSM establish/communicate to the second Sup720 on another Cat 6000
    Answer: Yes. Just set up HSRP on the Sup720.
    2) How to implement and configure if I have 2 Cat 6000 with one unit of Sup720 and one unti of WLSM installed at each chassis?
    Answer: Configure HSRP on the WLSM.
    3) How should the interface tunnel be created if I have 2 Cat 600 with Sup720 and WLSM installed?
    Both Sup720 creates the same tunnel interface. Assign different IP address on the tunnel interface.
    Must I have same interface tunnel created on the Sup720 as we are allowed to put in one WDS IP address on the infrastructure AP?
    Answer: Use the virtual HSRP IP address on the WLSM on the infrastructure AP.
    4) How is load balance of tunnel being handled by the Sup720 ? Any limitations?
    Answer: Load balance is not allowed.
    5) How HSRP is configured on second WLSM since tunnel is created in Sup720? What are the commands required to do so?
    Answer: Sample configuration as below:
    WLSM1 configuration
    wlan vlan 10
    standby address 10.10.10.10
    ip addr 10.10.10.11 255.255.255.0
    gateway 10.10.10.1
    admin
    Sup720-1 configuration
    interface vlan 10
    ip address 10.10.10.1/24
    interface tunnel 172
    ip address 172.16.1.1/24
    WLSM-2 configuration
    wlan vlan 10
    standby address 10.10.10.10
    ip addr 10.10.10.12 255.255.255.0
    gateway 10.10.10.2
    admin
    Sup720-2 configuration
    interface vlan 10
    ip address 10.10.10.2/24
    Interface tunnel 172
    ip address 172.16.1.2/24
    6) What is the switchport configuration that connects to an AP to have L3 roaming using WLSM as WDS?
    Answer: If the wireless clients only send unicast IP, you configure the switchport as an access port, whose VLAN is the native VLAN on the AP. If multicast traffic or non-IP traffic is sent by the wireless client, you need to configure the switchport as a trunk port.
    7) I understand that native VLAN to the AP is used to establish the tunnel to the Sup720 and each AP across the campus should have an SSID map to a network-ID which corresponds to the tunnel created, can I have different subnet to the native VLAN across the campus but still have L3 roaming via WLSM-WDS device?
    Answer: Yes, you can. As long as there is a IP route from the AP(native VLAN) to the WLSM and SUP720.
    8) If I configure a switchport that connects to an AP as VLAN 20 and another switchport as VLAN 30 to another AP,
    Both AP have the same SSID map to the same network-ID, can L3 roaming work? If not, what shall I do?
    Answer: It should.

  • ISSUES 7921G roaming whit push to talk

    Hello,
    We have a deployment with many Cisco AP around 100,  the AP are closer each other,This AP only works with 2.4 radio, because the radio of 5 don´t have anntenas to work so the only radio to cover the deplyment is the 2.4 Ghz.
    The network was designed and installed by another company, they mounted 20 Aps to cover offices and  80 Aps to cover a warehouse mounted higt around  65 feet and there are separates each other around 41 feet.
    I am having issues with 7921G phones roaming through a 802.11b/g, The phones do not seem to be moving on to nearby APs at the right time therfore alowing the call to degrade and drop out, I was hoping someone could give me some tips on WLC configuration and AP power to optimize the system already installed. I am really limited as to the amount and location of the APs
    This issue it´s more when use the 7921G the push to talk  ficture
    The WiFi network has plenty of APs installed. It certainly has -67dbm coverge in all areas and also a more than of 20% overlap.
    7921G  ver 1.3.2
    WLC 4400 ver 7.0.116.0
    CCM ver 4.0
    APs: AIR-LAP1242AG-N-K9
    Thanks you
    XU

    Hi,
    I Used the tool, but the only change it´s recomended  it´s in the 802.11a network  but this frecuency its not possible, because the 802.11a network was disabled.
    I upgrade WLC firmware to the  7.0.235.0, and the data rate there are available are 9  for mandatory and the other higher data rates are supported.
    The security for the phones are wep, and the multicast mode are Unicast, becuase if I configure the multicast in  Multicast mode don´t work with the PTT.
    I think in the Wired LAN dont have IP multicas routing. But I cant touch the LAN network.
    Best Regards

  • Huge ntuser.dat.LOG1 since upgrade to Windows 8.1 prohibits roaming of user profile

    Hello,
    a few days ago my PC (part of our domain) first started to have problems with my user profile. Our domain uses roaming profiles with a size limit of 30MB. My user.dat has a size of 12.5MB. Up to now this did not cause any problems (and does not cause any for
    most users of our domain having a user.dat of similar size). However, after upgrading to Windows 8.1 I repeadly have problems with my profile exceeding its maximum size. After checking my profile, I found a ntuser.dat.LOG1 with 12,5MB in size and a ntuser.dat.LOG2
    of 2MB. As far as I know these files are used to store temporary transactions for the user.dat. But why are they this large? Together they almost completely fill the profile. As an interesting side node the last modification of ntuser.dat.LOG1 dates back more
    then seven days.
    What is further puzzling me: ntuser.dat.LOG1 and ntuser.dat.LOG2 are not synchronized with the roaming profile on the server. At least they are not on the server. However there used to be much smaller versions of these files which could have been transfered
    before the profile size exceeded its limit. Since these file seem not to be part of the roaming part of the profile, they should not count for the roaming profile size. However, they definitely do. Neglecting the registry files the largest file in my profile
    is less than 500kb and there are very few files of this size. I checked locally as well as on our server.
    Deleting the local profile and starting fresh using the roaming profile from our server does work for a day or two but then I run into the same problem. Especially, loosing all local profile data is inconvenient. I could start a new with a completely new
    profile, but I am not convinced that it is a profile issue. In our organisation my computer is one of the first to move to Windows 8.1. Since my profile worked without problems for years now, I am worried that I ran into a Windows 8.1 issue. As users normally
    start to complain about a roaming profile not synchronizing only after their local copy broke, I'd like to make sure that this is a isolated issue.
    Anyone else experiencing similar issues? Any hint on how to solve the problem?
    Regards,
    Oliver

    No, I did not find a solution. However, we moved away from roaming profiles and rely on folder redirection only. That works for us. Since we can redirect the most important folders there is no more need for roaming profiles (at least in our case).

  • Disabling Multicast in Solaris 10

    Hi,
    I have been searching the internet all morning trying to figure out how to disable solaris 10 multicast. I have no need for it. The best information I could find was to modify the script /lib/svc/method/net-svc and comment out the adding of a route point for multicast near the end of the script.
    I thought that hand modifying the methods of SMF was a big no no in solaris 10. Is there a better way to disable multicast?
    For instance, if I do an ifconfig -a I see that all of my intefaces have the MULTICAST flag set. Is there a way in ifconfig to disable that flag?
    I have seen people put ifconfig options into their /etc/hostname.interface file. I think if I can find the correct ficonfig option I can disable the multicast flag during system boot and that should disable multicast.
    Any comments/suggestions would be welcome.
    Eric

    Now that I have done more research I guess I do not have to turn off the multicasting.
    This problem appeared because during snoop sessions I see MANY of the following messages:
    ? -> (multicast) ETHER Type = 022C ... 53 bytes
    I assumed that one of my machines was doing the multicast. However, I shut down all but one machine and then I removed the multicast route from the route table and the messages still appear. I think that either my cisco switch or cisco router is doing the multicast.
    So I guess I will not turn off the multicast on the machines.
    Does it make sense that the router and/or switch is sending out the multicasts?

  • Why does 8X always switch to "Roaming service"?

    Hello, I've had my HTC 8X for about a month now, since it came out, and I've noticed something kind of strange. For some reason, under the Cellular menu in the settings, it sometimes says my active network is "Roaming service" instead of Verizon Wireless. It happens pretty often, completely randomly. When I'm it's connected to the Roaming service, my data speeds seem to be slower, and I can't receive picture messages. Nothing else seems to be affected though. I can still send/receive calls and texts, and I still have access to a 3G data network. But why doesn't it stay on Verizon? It wouldn't really bother me much, but when I'm connected to Verizon it seems to be much faster.
    I know it's not my coverage, because I haven't had this problem on my previous HTC Trophy, and when I'm connected to Verizon, I have more bars than on Roaming service. Also, I don't live in an LTE covered area, so when on Verizon and Roaming, I'm always on 3G.
    And if I'm correct, Verizon and Sprint have a roaming agreement, so when I'm roaming, it's free and on Sprint's network.... just want to make sure I'm not being charged for this at all...
    So anyways, how can I fix this? I'd prefer to not have to do a factory reset.... Thanks for any replies!

    Hello cody503,
         Thank you for sharing your wireless question with the community. We understand how important it is to have consistent and reliable wireless service! After all, that’s why you chose us as your wireless provider! I would like the opportunity to clarify this for you! As we all know, Verizon Wireless have the largest coverage in the country but there are some areas that our customers roam off another carrier at. When roaming, you may see the verbiage that you spoke of in your post. Since your Verizon Wireless phone is designed to pick up our network over others, you will experience a HUGE difference in network performance. I would like to confirm that the area that you were in is indeed an extended area. May I ask what city, state, and zip code were you in when you got the “roaming service” notice? Can I assume that you device doesn’t have any liquid or physical damage? Once you provide me with this information then I can check the area and get back to you. I’m looking forward to your next reply.
    Thank you…
    ArnettH_VZW
    Follow us on Twitter @VZWSupport

  • Entro em Roam e meu iPhone perde sinal da operadora

    Pessoal,
    Preciso de ajuda.
    Tenho um iPhone 4 com o sistema operacional IOS 5.0.1 desbloqueado para a operadora OI. Toda a vez que viajo e entro em outro estado o iPhone perde o sinal da operadora e não retoma. Ja tentei de tudo (reset; reinstalação; etc..). Quando retorno ao meu estado ele volta a funcionar..
    Alguem já passou por isso e pode me ajudar?
    Obrigado amigos.
    Marcelo

    Você já verificou as configurações de roaming?
    Se elas estiverem normal, o problema pode ser com sua operadora.
    JP

  • Unable to receive multicast on a multi network interface host

    Can anyone please help?
    I am not able to receive multicast on a multi network interface host.
    This is the code:
    public class LegacyMulticast {
    public static void main(String[] args) throws IOException {
    InetSocketAddress group = new InetSocketAddress("224.10.20.30", 12345);
    NetworkInterface iface = NetworkInterface.getByName("eth3");
    MulticastSocket socket = new MulticastSocket();
    socket.setSoTimeout(5000);
    socket.joinGroup(group , iface);
    byte[] b = new byte[4096];
    DatagramPacket datagram = new DatagramPacket(b, b.length);
    try {
    socket.receive(datagram);
    System.out.println("Success");
    catch (SocketTimeoutException ste) {
    System.out.println("Failure");
    socket.leaveGroup(group, iface);
    The funny thing is that when I start this code, Wireshark detects IGMP join on the correct network interface caused by joinGroup call, followed by constant UDP traffic on correct port which I aim to receive and finally I see correct IGMP leave caused by leaveGroup call and the UDP traffic stops.
    I just don't receive anything on socket.receive call.
    I am trying to figure this one out for days now. Pls help someone :)
    P.S. I suspected security, but System.getSecurityManager() call returns null.
    P.P.S. I also tried implementing this with NIO, but with same result.

    public class LegacyMulticast {
    public static void main(String[] args) throws IOException {
    InetSocketAddress group = new InetSocketAddress("224.10.20.30", 12345);
    NetworkInterface iface = NetworkInterface.getByName("eth3");
    MulticastSocket socket = new MulticastSocket(12345);
    socket.setSoTimeout(5000);
    socket.joinGroup(group , iface);
    byte[] b = new byte[4096];
    DatagramPacket datagram = new DatagramPacket(b, b.length);
    try {
    socket.receive(datagram);
    System.out.println("Success");
    catch (SocketTimeoutException ste) {
    System.out.println("Failure");
    socket.leaveGroup(group, iface);
    This is still not working.
    The multicast is coming from the network (not localhost), OS is Windows 7.
    When I start a multicast stream localy via VLC application on this same group and port, I receive the traffic in this Java application OK.
    Once again, Wireshark detects IGMP join and leave and multicast traffic flow on eth3 network interface initiated by the Java application, but it just doesn't see the UDP datagrams.

Maybe you are looking for