WISM Interface

Hello
I am having trouble to upgrade our Catalyst 6509 from s72033-ipservicesk9-mz.122-33.SXH4.bin to 72033-ipservicesk9-mz.122-33.SXJ1.bin. I am upgrading because of installation of a WISM2 controller.
The Catalyst configuration is:
1   10 WiSM WLAN Service Module               WS-SVC-WISM-1-K9  
2   10 WiSM WLAN Service Module               WS-SVC-WISM-1-K9  
3   10 WiSM WLAN Service Module               WS-SVC-WISM-1-K9  
4   6 Firewall Module                                            WS-SVC-FWM-1    
5   2 Supervisor Engine 720 (Active)         WS-SUP720-BASE    
7   24 CEF720 24 port 1000mb SFP             WS-X6724-SFP      
The problem is with our WISM controllers, when rebooting with the new IOS 122.33.SXJ
The interface configuration in startup-config is erased completely for all WISM interface.
interface GigabitEthernet1/1
description WISM A
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 4060
switchport trunk allowed vlan 780-788
switchport mode trunk
no snmp trap link-status
no cdp enable
channel-group 8 mode on
The only way to keep the Interface konfuguration is witch IOS s72033-ipservicesk9-mz.122-33.SXH4.bin.
Regards
Johan

Johan,
We introduced the auto-configuration wism commands starting in 12.2(18)SXF5, and in the SXI code and later (SXJ included) it is now the only way to configure the WISM modules.
If you were previously using the manual port configuration, you will need to migrate to the new set of wism commands:
http://www.cisco.com/en/US/products/hw/modules/ps2706/products_tech_note09186a00808330a9.shtml#config
wism module controller <1/2> native-vlan x
wism module controller <1/2> allowed-vlan x,y,z...
-Patrick Croak
Wireless TAC

Similar Messages

  • WISM Interface Grouping with different subnets

    WISM v7.0 VLAN Select.
    Anyone can confirm if the VLANs subnet to be configured under interface group MUST be having the same subnet.
    Eg. VLAN1 - mask 255.255.255.248
          VLAN2 - mask 255.255.255.120
    Would these two VLANs be able to work together in interface grouping?
    Thanks in advance.
    Cheers,
    Wong

    The subnet mask doesn't matter, but the smaller subnet will ge marked dirty first since it is a smaller subner.
    Sent from Cisco Technical Support iPad App

  • Wism interfaces gone after switch-upgrade

    Hi,
    I've a 6509 with a sup720 (ordinary, not a 10GE) and a wism blade in slot 3.
    It worked fine until i did a upgrade of the IOS on the 6509.  I went from s72033-ipservicesk9_wan-mz.122-18.SXF13 to s72033-advipservicesk9_wan-mz.122-33.SXI3.
    Now i cannot reach my Wism-blade any more. When i look in the running config on the switch there are no gigabit-interfaces on module 3, in the config there is even no mention of a module 3.
    However when i do a "show module" the wism is reported with a status "ok".  Also when i do a "show wism module 3 controller 1 status" it tells me that its "Oper-up" and all the adresses are in place, even the service IP-adres (which i do not understand because it can only get this adres by DHCP from the switch).
    The Wism is running 6.0.188.0.
    Anyone ever seen such behavior?
    Thx

    Elie, the service-vlan was (and is) indeed different, so that was not the problem.  I got a good clue in the posting of dampcampb: he wrote that there was a difference in behavior between the SXI- and the SXF-versions of the IOS.  I checked and there was also a SXF-version with the features i wanted.  I used that version of the IOS and all was working fine again. Thx however for the reply.

  • WiSM interface vlan requirement

    Can anyone tell me why the AP-Manager and Management interfaces have to be on the same VLAN? I'm probably missing something about WiSM operations but if I'd appreciate the input.
    thanks
    js

    That is the only supported way. Any other way will not work. This goes for any WLC configuration and not just the WiSM. The management interface so you can manange the wlc it is aslo the defaut interface used when an ap first joins the wlc and then the ap-manager is used for the lwapp tunnel. If you have the management and ap-manager interfaces on a different subnet, then you will see a vlan mismatch on the switch. Also it is important to note that both these interfaces need to be native vlan on the trunk port.

  • WiSM - Interface Vlan Overlapping within AP Group

    Hi there,
    Need help on this. Wism that deployed on the network had found issue in interface vlan overlapping. Had configured the vlan interface and assign to a group. The group had been define on specific lwapp APs. However user that manage to associate with the particular AP had used the different group that not specify to that APs. It had been using the group that been specify to other APs that located at different location.
    Any ideas on this? Is this internal bugs? I had checked with the bugs listed in Cisco software. But not mentioned about this. Fyi, we are running on software version 4.1.171.0. and also we are operates almost of 80 Aps under 40 interface vlan assign to the groups.

    Could you provide the details of the wism configuration?

  • Wism2 redundancy in two C6513 chassis - Lost heartbeat with the Supervisor

    I get a lot of messages in the trap log "Lost heartbeat with the Supervisor"
    The controller seems to be up and running. Failover works perfectly.
    Why do I get these messages?
    Rgds Snorre

    HI Snorre,
    I get a lot of messages in the trap log "Lost heartbeat with the Supervisor"The controller seems to be up and running. Failover works perfectly.Why do I get these messages?
    There are several possible reasons that this error message is generated. From the WiSM's perspective, the most common reason is an incorrect configuration of the service port on the Supervisor Engine.
    In the case of a WiSM, the service port is used solely for communication between the Supervisor and the WiSM.
    Complete these steps in order to get rid of this error message:
    1. Create a new VLAN for the WiSM service ports on the Supervisor Engine that does not exist anywhere on the network.
    2. Create a DHCP scope setup on your Supervisor  to assign IP addresses to the service ports of the controllers.
    Note: It is recommended that you create a DHCP scope for the service port of the Catalyst WiSM. Alternatively, you can also session (session slot X process 1 or 2 ) or console directly into the WiSM and set the static IP addresses with the configure interface address service-port command.
    3. Assign the WiSM service ports to this newly created VLAN with the command wism service-vlan new VLAN ID on the Supervisor Engine.
    This VLAN is used for the Supervisor Engine to communicate with the service port of the WiSM. Refer to Configure Communication Between the Supervisor and Cisco WiSM for more information on how to configure the procedure mentioned here.
    Cisco bug ID CSCsg59144 is also associated with this error message.
    Other possible reasons might be with the backplane connection of the module to the chassis This can be verified by first moving the WiSM to another slot and see if it continues. Sometimes, this might be an issue with the module itself. But these are rare circumstances.
    Example:
    Configure Communication Between the Supervisor 720 and Cisco WiSM
    After the Cisco WiSM controller is installed in a slot and detected by the Supervisor, these configurations are made on the Supervisor Engine to communicate with WiSM.
    1. Create a DHCP scope for the Service-Port of the Catalyst WiSM.
    ip dhcp excluded-address 192.168.10.1 192.168.10.2
    ip dhcp pool wism-service-port
    network 192.168.10.0 255.255.255.0
    default-router 192.168.10.1
    Alternatively, you can also session (session slot X proc 1 or 2 ) or console directly into WiSM and set static IP addresses (config Interface Address Service-Port).
    Make sure that the service port IP address is not a routable IP address in your network because it is only used for communication between the Sup 720 and the WiSM.
    Note: VLSM is supported on all ports, which includes the Service port.
    2. Create the WiSM Service Port Gateway and assign the IP address.
    Create a VLAN in the Supervisor 720. This VLAN is local to the chassis and is used for communication between Cisco WiSM and Catalyst Supervisor 720 over a Gigabit Interface on the Supervisor and a service port in the Cisco WiSM.
        interface Vlan192
        Description WiSM Service Port Gateway
        ip address 192.168.10.1 255.255.255.0
    Note: There should already be a network management VLAN interface to reach the Cat6k.
    3. Assign the WiSM Service Ports to a VLAN.
    Configure this command to use VLAN 192 to communicate with the service-port.
        wism service-vlan 192
    Hope it helps.
    Reagrds

  • WiSM, unable to see Interface after adding.

    We have an up and running WiSM, for about 9 months.  It resides in a 6509 chassis.
    I needed to add a new interface for another subnet (previous one was getting over ran, and we have a new project)
    I went through the process of adding the interface.  I ensured it was active.
    At present, from the 6509 I am unable to ping the interface's IP, but I am able to ping that networks gateway.
    From the WiSM, I am able to ping the interface's IP, but unable to ping the gateway.
    I was not the original configurator of the WiSM and the 6509 build.  That person is no longer around.
    On the 6509 I have ensured that the :  show interface trunk shows the VLAN in question.
    I have searched numerous times, and I feel like there is just some nefarious item I am missing on the creation of new Interfaces between the WiSM and 6509.
    Any input would be appreciated.
    Thanks

    Have you double checked the vlan tag, subnet mask, etc for the new interface on the WLC?  Usually when you cannot ping an interface on the WLC (although pings are the lowest priority) it is a configuration error on the above, or the trunk not allowing that interface, etc.
    Thanks,
    Lee

  • WISM : vlans and interface limitation

    We have a WISM within our 6509. On the 2 different controllers within the WISM, we have 2 different VLAN's that are attached to 2 different interfaces, can we have each interface attach to the same VLAN?

    Yes. 

  • WiSM version 6 Cannot modifiy service interface

    Can any body help me with this
    although cisco sw advisor said that the best IOS for my hardware 6509 Sup720 IOS: (s72033_rp-IPSERVICESK9_WAN-M), Version 12.2(18)SXF16 suits the WiSM; And I tested it already with WiSM version 5.0 but when I've upgraded the WiSM to version 6.0 the service interface from the switch side says:
    B5_Noc2_CS1(config)#int gig 4/9
    % This interface cannot be modified
    can anyone solve this issue; as the customer refuse to upgrade the switch IOS & He wants to use the latest ED WiSM sw 6.0; so please Help !!!!!

    This is normal, you cannot modify those ports "i guess the Wism is on slot 4" try to change it to slot 3 and you will be able to configure 4/ interfaces...i once got somthing like this.
    the solution is to follow this guide.
    http://www.cisco.com/en/US/products/hw/modules/ps2706/products_tech_note09186a00808330a9.shtml#config

  • WiSM Status LED 1 & Status LED 2 showing off. Is it normal?

    Hi,
    WiSM WLAN Service Module WS-SVC-WISM-1-K9 in 6509e running VSS IOs s72033-ipservicesk9_wan-mz.122-33.SXI2a.bin having trouble to get the IP from service-vlan DHCP also status LED 1 & Status LED 2 showing off.
    The pertinent config is as follows.
    vlan 300
    name WiSM_Service_Vlan
    interface Vlan300
    description *** WiSM Service-Vlan
    ip address 192.168.200.1 255.255.255.0
    ip dhcp excluded-address 192.168.200.1
    ip dhcp pool WiSM_Service-Vlan_300
       network 192.168.200.0 255.255.255.0
       default-router 192.168.200.1
    wism service-vlan 300
    vlan 183
    name WiSM_Management
    interface Vlan183
    description *** WiSM Management Vlan ***
    ip address 10.39.139.254 255.255.255.0
    wism switch 1 module 4 controller 1 allowed-vlan 125,126,183,300
    wism switch 1 module 4 controller 2 allowed-vlan 125,126,183,300
    wism switch 2 module 4 controller 1 allowed-vlan 125,126,183,300
    wism switch 2 module 4 controller 2 allowed-vlan 125,126,183,300
    wism switch 1 module 4 controller 1 native-vlan 183
    wism switch 1 module 4 controller 2 native-vlan 183
    wism switch 2 module 4 controller 1 native-vlan 183
    wism switch 2 module 4 controller 2 native-vlan 183
    HO2NET0001#sh wism status
    Service Vlan : 300, Service IP Subnet : 192.168.200.1/255.255.255.0
          WLAN
    Slot  Controller  Service IP       Management IP    SW Version  Status
    ----+-----------+----------------+----------------+-----------+---------------
    20    1           0.0.0.0          0.0.0.0                      Service Port Up
    20    2           0.0.0.0          0.0.0.0                      Service Port Up
    HO2NET0001#sh module
    Mod Ports Card Type                              Model              Serial No.
      1    8  CEF720 8 port 10GE with DFC            WS-X6708-10GE      SAL13442Q5N
      2    8  CEF720 8 port 10GE with DFC            WS-X6708-10GE      SAL13442GAL
      3   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     SAL13410N8P
      4   10  WiSM WLAN Service Module               WS-SVC-WISM-1-K9   SAD133101UY
      5    5  Supervisor Engine 720 10GE (Active)    VS-S720-10G        SAL13442JE4
    Mod MAC addresses                       Hw    Fw           Sw           Status
      1  0025.84f1.55b8 to 0025.84f1.55bf   2.1   12.2(18r)S1  12.2(33)SXI2 Ok
      2  0025.84f1.4e58 to 0025.84f1.4e5f   2.1   12.2(18r)S1  12.2(33)SXI2 Ok
      3  0027.0da7.c240 to 0027.0da7.c26f   3.2   12.2(18r)S1  12.2(33)SXI2 Ok
      4  0023.5e25.7168 to 0023.5e25.7177   2.3   12.2(14r)S5  12.2(33)SXI2 Ok
      5  001f.9e2a.2608 to 001f.9e2a.260f   3.1   8.5(3)       12.2(33)SXI2 Ok
    Mod  Sub-Module                  Model              Serial       Hw     Status
      1  Distributed Forwarding Card WS-F6700-DFC3C     SAL13442EG9  1.4    Ok
      2  Distributed Forwarding Card WS-F6700-DFC3C     SAL13442H9T  1.4    Ok
      3  Centralized Forwarding Card WS-F6700-CFC       SAL13442HU9  4.1    Ok
      4  Centralized Forwarding Card WS-SVC-WISM-1-K9-D SAD133200D6  2.1    Ok
      5  Policy Feature Card 3       VS-F6K-PFC3C       SAL13442E5S  1.1    Ok
      5  MSFC3 Daughterboard         VS-F6K-MSFC3       SAL13421AJZ  2.0    Ok
    Mod  Online Diag Status
      1  Pass
      2  Pass
      3  Pass
      4  Pass
      5  Pass
    HO2NET0001#sh vlan
    300  WiSM_Service_Vlan                active    Gi1/4/9, Gi1/4/10
    The service IP is supposed to have been populated with an address from the dhcp pool. I am also unable to connect to access it by console as well as doing a session switch 1 slot 4 processor 1. I get the following upon attempting to do so:
    Through Console.
    It is giving following & then got stuck.
    Bootloader 3.2.202.0 (Nov 13 2007 - 19:35:12)
    Motorola PowerPC ProcessorID=00000000 Rev. PVR=80200020
            CPU: 999 MHz
            CCB: 333 MHz
            DDR: 166 MHz
            LBC: 41 MHz
    L1 D-cache 32KB, L1 I-cache 32KB enabled.
    I2C:   ready
    DTT:   1 is 33 C
    DRAM:  DDR module detected, total size:512MB.
    512 MB
    8540 in PCI Host Mode.
    8540 not PCI Arbiter.
    Memory Test PASS
    FLASH:
      Flash Bank 0: portsize = 2, size = 8 MB in 142 Sectors
    8 MB
    L2 cache enabled: 256KB
    Card Id: 1537
    Card Revision Id: 1
    Card CPU Id: 1287
    Number of MAC Addresses: 32
    Number of Slots Supported: 4
    Serial Number: FAM133200D6
    Manufacturers ID: 30464
    Board Maintenance Level: 00
    In:    serial
    Out:   serial
    Err:   serial
                          .o88b. d888888b .d8888.  .o88b.  .d88b.
                         d8P  Y8   `88'   88'  YP d8P  Y8 .8P  Y8.
                         8P         88    `8bo.   8P      88    88
                         8b         88      `Y8b. 8b      88    88
                         Y8b  d8   .88.   db   8D Y8b  d8 `8b  d8'
                          `Y88P' Y888888P `8888Y'  `Y88P'  `Y88P'
                        Model SVC-WiSM   S/N: FAM133200D6
    Net:   TSEC ETHERNET
    IDE:   Bus 0: OK
      Device 0: Model: STI Flash 8.0.0 Firm: 01/17/07 Ser#: STI1MMJ109198093647
                Type: Removable Hard Disk
                Capacity: 488.7 MB = 0.4 GB (1000944 x 512)
      Device 1: not available
    Booting Primary Image...
    Press <ESC> now for additional boot options...
    Detecting Hardware . . .
    Cryptographic library self-test....passed!
    XML config selected
    Validating XML configuration
    Cisco is a trademark of Cisco Systems, Inc.
    Software Copyright Cisco Systems, Inc. All rights reserved.
    Cisco AireOS Version 5.2.178.0
    Initializing OS Services: ok
    Initializing Serial Services: ok
    Initializing Internal Interfaces: ok
    Initializing Network Services: ok
    Initializing Licensing Services: ok
    Starting ARP Services: ok
    Starting Trap Manager: ok
    Starting Network Interface Management Services: ok
    Starting System Services: ok
    Starting FIPS Features: ok : Not enabled
    Starting Fast Path Hardware Acceleration: ok
    Starting Switching Services: ok
    Starting QoS Services: ok
    Starting Policy Manager: ok
    Starting Data Transport Link Layer: ok
    Starting Access Control List Services: ok
    Starting System Interfaces: ok
    Starting Client Troubleshooting Service: ok
    Starting Management Frame Protection: ok
    Starting LWAPP: ok
    Starting CAPWAP: ok
    Starting Certificate Database: ok
    Starting VPN Services: ok
    Starting Security Services: ok
    Starting Policy Manager: ok
    Starting Authentication Engine: ok
    Starting Mobility Management: ok
    Starting LOCP: ok
    Starting Virtual AP Services: ok
    Starting AireWave Director: ok
    Starting Network Time Services: ok
    Starting Cisco Discovery Protocol: ok
    Starting Broadcast Services: ok
    Starting Logging Services: ok
    Starting DHCP Server: ok
    Starting IDS Signature Manager: ok
    Starting RFID Tag Tracking: ok
    Starting WLAN Control Protocol (WCP): ok
    Starting Mesh Services:  ok
    Starting TSM: ok
    Starting CIDS Services: ok
    Starting Ethernet-over-IP: ok
    Starting DTLS server:  enabled in CAPWAP
    Starting FMC HS: ok
    Starting WIPS: ok
    Starting SSHPM LSC PROV LIST: ok
    Starting Management Services:
       Web Server: ok
       CLI: ok
       Secure Web: Web Authentication Certificate not found (error). If you cannot access management interface via HTTPS please reconfigure Virtual Interface.
    (Cisco Controller)
    Welcome to the Cisco Wizard Configuration Tool
    Use the '-' character to backup
    Would you like to terminate autoinstall? [yes]:
    AUTO-INSTALL: starting now...
    Through Session
    HO2NET0001##session switch 1 slot 4 proc 1
    The default escape character is Ctrl-^, then x. You can also type 'exit' at the remote prompt to end the session Trying 0.0.0.0 ...
    Any assistance or ideas offered will be greatly appreciated.
    Thanks,

    Hi Tabish,
    How many times do you have to open this same topic?
    In my opinion, this is your THIRD thread for the same topic.

  • Controllers in the same WISM module in the 6500, i'm trying to make one of them anchor controller for guest internet

    I have 2 controller in the same WISM module and I'm trying to make one of them Anchor controller for guest WLAN, but when I give put the anchor controller in a separated non-routed VLAN and connect it to an outside switch by creating VLAN 192 on the core. ( the Internet router is connected to the same switch).-it is showing path down... ( VLAN 192 visitor Internet and VLAN 224 my internal controller management VLAN are not talking)
    there is no routing between these 2 VLAN ( because of security), but i can't get the controller to communicate.
    -if I connect my laptop to this switch I'm able to go out on Internet but my visitor WLAN is not able to get IP address from the router connected to this switch.
    - I called Cisco and one the guys told me that i can leave the management in VLAN 224 for the controller to communicate ( which they did), but the issue I'm having right now is that my visitors are not getting IP addresses from this VLAN at all
    some one please advise
      vlan192   4/1 vlan 192              int g0/0 192.168.2.201
      6500 ----- switch ---- router---------  (outside)
        |         |   |
        |        DHCP server
       WLC

    A couple of questions, is VLAN 192 allowed across the trunk link to the wlc?  Do you have an interface tagged for vlan 192, with a valid address?  What is providing the DHCP?
    Cheers,
    Steve
    If  this helps you and/or answers your question please mark the question as "answered" and/or rate it, so other users can easily find it.

  • After adding 2nd WiSM and failing over AP's some apps don't work

    We have a dual core made up of 2 6513's. In 6513#1 we have WiSM#1 which we have had for sometime now. We have added a 2nd WiSM in 6513#2 for redundancy purposes also we are going to be re-configuring the WiSM in 6513#1 to more match that of the new WiSM in 6513#2. We have installed the new WiSM and failed over the AP's from 6513#1 so we can re-configure it's WiSM. The failover went great and no issues, with the exception that a web application or two didn't function from wireless clients and users were having issues getting to some mapped drives. The only difference from the new WiSM config vs the old WiSM is that on the old WiSM the AP's were in the same VLAN as the controller management interfaces. Now with the new WiSM it's configuration has the controllers AP mgt interfaces ip addresses in a different VLAN from the AP's, we are doing this based on Cisco best practices. If we revert the AP's back to the original WiSM/controllers the PC's where they are on the same vlan/subnet the applications and shares that were having issues the other way work. We have placed a call with Cisco TAC and they say our configs look good and we even sent them some packet captures and they said everything looks normal. The wireless clients can ping and resolve the server hosting the application database just fine.
    Thanks

    We did create the mobility groups, and we are using DHCP opt 43. The AP's find the 2nd WiSM#2 just fine and associate to the controllers and all the WLAN's work just fine. The only issue is that after the AP's are on the new WiSM and controllers there is an application or 2 that is having trouble locating it's database server and that some share's are not working. Again the only difference in this new setup in that now the AP's are on a different subnet/vlan from the controller mgt addresses where as before they were in the same subnet/vlan and the application and shares worked fine. It's almost like it is a bit of a routing issue?
    Thanks

  • Mgmt Via Dynamic Interface not working on 5505 version 7.2.111.3

    Folks,
             I have posted this question a couple of times on the forum but did not get a solution. I am trying to manage my 5508 controller from a dynamic interface which is assigned to port 7 of the controller. I have a switch connected to that port which has a PC on the same subnet as the dynamic interface. From the PC, I can ping the dynamic interface IP Address, but can not telnet,SSH,http or https to it. There is no clear doc that specifics how to effectly use the command "config network mgmt-via-dynamic-interface" command.
    Mgmt Via Wireless Interface................. Enable
    Mgmt Via Dynamic Interface.................. Enable
    Interface Name                   Port Vlan Id  IP Address      Type    Ap Mgr Guest
    173                                      7    173      172.16.101.100  Dynamic Yes    No
    management                         1    172      172.16.100.100  Static  Yes    No
    service-port                           N/A  N/A      0.0.0.0         DHCP    No     No
    virtual                                    N/A  N/A      1.1.1.1         Static  No     No
    7  Normal  Forw Enable  Auto       1000 Full  Up     Enable  N/A     1000BaseTX
    Any guidence would be highly appreciated.

    Im having a similar issue and have 2 TAC cases open.
    TAC CASE#1:  issue is that even when disbaled I can still access the dynmic interface via HTTPS/HTTPS/TELNET/SSH. But this is on a WISM1.
    Thanks a lot for your quick and prompt response, I see that there is an internal Bug with an ID CSCty32586.
    I see that the bug is fixed told be fixed in 7.0.230.0, but it’s not fixed. The bug is fixed in 7.2.x version.
    I understand that you are using Wism on which 7.1.x version and above is not supported.
    As 7.0.235.3 is released recently to overcome some of the changes and to fix some of the Bugs with older version on these devices.
    Kindly try to upgrade the software version of the WLC to 7.0.235.3 and check the compatibility.
    Please do let me know in case of any concerns and I will be glad to assist you.
    TAC CASE#2: Just like you I can not access the dynamic interface. Still working that one .. The holiday dropped when I just opened that case.
    "Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
    ‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

  • Unable to access the secondary WISM from the diffrent VLAN

    Hi,
    We have got 2 WISM,We are able to access the primary WISM from the diffrent VLAN through GUI mode,But we are not able to access the secondary WISM from diffrent VLAN through GUI mode.We are able to access the secondary WISM from WISM management VLAN.I am attaching the WISM management config below.
    Core1
    VLAN 4 ---- Wism Management
    ip address 172.16.10.2/24
    HSRP 172.16.10.1
    Primary WISM IP address 172.16.10.4
    Core2
    VLAN 4 ---- Wism Management
    ip address 172.16.10.3/24
    HSRP 172.16.10.1
    Secondary WISM IP address 172.16.10.5
    Can any one get me the solution for this.
    Regds
    Saji k.s

    Check if the routing from VLAN is enabled . Make sure Management and Ap-Manager interface must be un-tagged for example Vlan 0 when they are on the Native Vlan of the trunk. Remove the tags from the management interface.
    Also check if you have Filters created that blocks access to secondary WiSM.

  • WLAN Controller learning IP/MAC on wrong virtual interface

    Hello
    I believe since I upgraded my WiSM to 7.0.250.0 is it learning a MAC address on the wrong virtual interface.
    The setup:
    - a Linux server with 2 virtual interfaces, both use the same MAC address, one is the gateway of VLAN 116 and one is the gateway of VLAN 240
    - a WiSM with several virtual interfaces, including one in 116 and one in 240
    Here the arp table with the problem:
        MAC Address        IP Address     Port   VLAN   Type
    00:50:56:BD:32:92   172.16.240.9     29     240    Host
    00:1E:4A:FA:87:8B   172.16.102.12    29     0      Permanent
    00:1E:4A:FA:50:0B   172.16.102.13    29     0      Permanent
    00:1E:4A:FA:81:2B   172.16.102.14    29     0      Permanent
    00:50:56:BD:32:92   172.16.116.9     29     240    Host
    00:1D:E0:31:55:23   172.16.116.185   29     116    Client
    58:94:6B:68:50:E8   172.16.118.201   29     116    Client
    1C:B0:94:B7:38:08   172.16.118.234   29     116    Client
    And here after I made a PING from the controller to the listed ip address:
        MAC Address        IP Address     Port   VLAN   Type
    00:50:56:BD:32:92   172.16.240.9     29     240    Host
    00:1E:4A:FA:87:8B   172.16.102.12    29     0      Permanent
    00:1E:4A:FA:50:0B   172.16.102.13    29     0      Permanent
    00:1E:4A:FA:81:2B   172.16.102.14    29     0      Permanent
    00:50:56:BD:32:92   172.16.116.9     29     116    Host
    00:1D:E0:31:55:23   172.16.116.185   29     116    Client
    38:E7:D8:D3:7C:FA   172.16.118.92    29     116    Client
    58:94:6B:68:50:E8   172.16.118.201   29     116    Client
    1C:B0:94:B7:38:08   172.16.118.234   29     116    Client
    18:AF:61:12:E9:FB   192.168.1.59     29     117    Client
    Has anybody else the same problem?
    The host 172.16.116.9 is also the configured DHCP server on VLAN 116.
    Is there a way to statically configure this IP address on that VLAN? Because it causes every few days a service outage on that VLAN (which is bound to an SSID).

    Yup, I'd say still valid. Seeing as it is the gateway, if it had different mac addresses per interface, it might still work.
    No, clients in the same subnet can communicate, but it is not recommended to 'bridge' wired and wireless with a WLC. The WLC doesn't like to bridge the communication by default, though there are work arounds.
     I might also say that as it uses the same MAC address for both virtual interfaces L2 is going to be messed up as each time there were an ARP the entry would change.
    Take a look and see if you can manually change the mac for one of the interfaces and test again.
    HTH,
    Steve

Maybe you are looking for