I know the WiSM 2 is like the 5500 WLC regarding the fact that you do not need to configure an ap-manager interface for CAPWAP packets because by default the managment interface acts like an ap-manager interface.
Any major advantages or disadvantages by letting the default action occur?
I've just reset our WISM2 in the test lab back to factory default as I needed to reconfigure the 6500 and the WISM2 itself. Bearing in mind I had it working before.I've just renamed and re-addressed some of the vlans so things flow better and make it easier to add more WISM2s in the future.Now I've run through the initial configuration and it's rebooted ok and show WISM status is showing Oper-Up and there's a port channel 407 been created as I would expect. However, I am unable to get to the management interface via GUI or SSH. In fact from the 6500 I can't even ping the management interface (but I can the service port).The Vlans have been changed in the 6500 config so it knows the native-vlan and service vlan etc and all the vlans are up/up.
View 17 Replies View RelatedI'm getting familiar with an existing, working wireless installation that uses a 2504 controller (recently upgraded to 7.3.101.0).
From the documentation, it looks like there should be a "AP-manager" interface by default (static). There is not one.
Configuring the Management Interface (GUI) #
Step 1 Choose Controller > Interfaces to open the Interfaces page.
###
Figure 3-3 Interfaces Page
#
According to that document, there are 4 Static interfaces. On the one I'm working on, there are only two: "management" and "virtual." (There are also a couple of "Dynamic" interfaces that have been set up.)From reading the documentation, it sounds like there should be an AP-manager interface, and that this would have been there by default.
It also sounds like an AP-manager interface is needed:Information About the AP-Manager Interface ## A controller has one or more AP-manager interfaces, which are used for all Layer 3 communications between the controller and lightweight access points after the access points have joined the controller. The AP-manager IP address is used as the tunnel source for CAPWAP packets from the controller to the access point and as the destination for CAPWAP packets from the access point to the controller.
Question 1: If I do not have an AP-Manager interface, are the APs connecting at L2? Is there some way to tell on these controllers whether APs are connecting at L2 or at L3 using udp?
Question 2: Is it not the case that one AP-manager interface should be there by default? (I see in the docs that more than one can be created, but in that case I expect that the additional interface(s) would show in the list as "Dynamic" and not "Static.")
A bit of background: The customer network is largely one flat network now, and I'm planning on subnetting it, and routing from the closets up. I want to make sure what may need to be changed in this wireless setup before proceeding. (The main wireless users are also getting IP addresses on the same flat network, at this point. That obviously will change so that they are on their own subnet.)
Yesterday I was in one of our client premises configuring a WLC 5508 with software 7.2, went through the initial configuration wizard with no problem whatsoever, my issue began when trying to configure a ap-manager interface.In many WLC configuration guides cisco states that for 5508 it is not required to configure an ap-manager interface because the management will suffice, but then they put a side note recommending it's configuration for best practices and better performance. OK so I saw that in an earlier version document and now they do not make the recommendation but the still use the word required and for me that's still is not a limitation. I can't create the ap manager interface because when I put the VLAN ID it says the it is being used by another interface.
View 5 Replies View Relatedat the moment we are using as default the manager interface as ap-manager interface.
Now I have to change the IP. I would like to change that very smooth with all our locations. My question, is it possible to add a ap-manager interface with a new vlan and IP Range, so that I can move the AP's to the second interface as as soon as it is planed with the location. Sometimes in special cases we have hard coded the WLC IP oder we just need to change the DHCP option but this needs to be planed and I see problem to do that in a hard cut.
I have inherited a site where the builders have installed a 2504 controller with 8 access points. Unfortunately they have not created an ap-manager interface when they did the set up. Is there any way I can do this via GUI or command line without going back to defaults?
View 7 Replies View Relatedadministrator wants to manage ASA 5500 using inside interface.{telnet or ssh].Allowed telnet and ssh in ASA 5500 but unable to get access from administrator PC..Is there a way to do it without enabling NAT on the ASA? Will a specific rule on ASA allow adminstrator to access ASA 5500 inside interface via ssh or telnet?
View 2 Replies View RelatedCustomer is running LMS 2.6.Scheduled backup was running perfect. But it is no more happening.When we checked we found that the "License Manager/ Deamon Manager is down" message pop ups.
We reset the casuser password, and then restarted the services. It becomes ok.But only the immediate backup is successful. Scheduled task fails for all those devices."License Manager/ Deamon Manager is down" happens quite often.
We have some new WISM2 running 7.0.116.0, but now we need to upgrade their license to suport 1000 APs. So I am looking at upgrading the software to 7.2.110.0. We are running WCS at the moment and got NCS with the new WISM2, so going to 7.3 and buying Prime Infrastructure is not an option at the moment, thus we are going for 7.2.
The thing is I can't seem to find much info about this upgrade. Is 7.0->7.2 a smooth upgrade? Do we need to do any configuration changes to the WISM2 or LAP1242? We are running H-REAP, will the change to FlexConnect be affected? I can't seem to find anything regarding requirements for 6500/SUP for running WISM2 7.2, do I need a certain software for that?
We have just installed lms 4.2 and are having problems collecting config and inventory from ws-svc-wism2-k9. The response from TAC was that this is not supported. And it also says this in
[URL]
Is this really the case ? Will there be released packeges to support this. It would be really useful if this was supported in lms4.2.
I have a question regarding WISM2 DP and licensing.
Suppose i have a WISM2 with 7.0, 500AP license today and i activate WISM2-DP by upgrading to 7.2,Do i get 500 AP capacity for free (total 1000AP) or do i get 250APs on each WISM2-blade ?
If i get 500APs for free, why is Cisco selling an expensive licensed 1000 AP WISM2 ? I better buy a single-plane 500AP-WISM2 and upgrade it myself then...50% profit.
Is this the same for a WISM2-300 (supporting 300 APs) ?When i activate WISM2-DP here, do i get an extra 300 AP or an extra 500 APs ? Or 150AP on each blade ?
I having an issue with WCS and the new code 7.4 on my WiSM2 blade. When I try to refresh configuration from/to controller it fails. I just upgraded from 7.01 and it worked before the upgrade.
Is this not supported?
I am able to change configuration from WCS to the WiSM2 and it works fine just cant copy config.
I am confused about the cisco docs:What is the minimum WLC/WCS version to support WISM2 controllers ?
The datasheet of WISM2 says "minimum 7.0.116.0"
URL
However the release notes of 7.0.116.0 do not mention the WISM2 module ?
URL
The release notes of 7.0.220.0 do mention the WISM2:
URL
I need to be absolutely sure as there are other software dependencies between 7.0.116.0 and 7.0.220 (regarding required MSE and Aeroscout versions).
With WCS 7.0.172.0 and WLC 7.0.116.0, will we have WISM2 support ?
I have just been setting up a WISM2 in a test lab and for some reason the Supervisor is not creating a port channel on my 6500 as suggested in the WISM2 Deployment Guide. WISM2 is installed in an appropriate slot (according to same doco) and have attempted reset to factory defaults, removing and power cycling several times.
View 1 Replies View RelatedI have installed WiSM2 with ver 7.4 and Bonjour works great with instruction provided, But…… 2 problems. I cant get it to work on the same subnet. (odd since the whole problem was not able to work across subnets), More important the new Code function / password function on the airplay wont work. I get the code on the projector, but the ipad never pop up the login box it just errors out.
View 2 Replies View RelatedI am about to migrate WISM1 to WISM2, The image of WISM1 is 6.0.199.4 and the image of WISM2 is 7.2.111.3.
Do i need to upgrade WISM1 to 7.2.111.3 before i export the configuration and import it into WISM2? Or can i just export the configuration from WISM1 on 6.0.199.4 and import directly to WISM2 which is on 7.1.111.3?
I have purchased a new WiSM 2 and my catalyst 6509-E is failing to detect it. Here are the details of the switch:
1. supervisor engine: vs-s720-10g-3cxl
2. ios image: s72033-advipservicesk9_wan-mz.122-33.SXI10.bin
3.
Mod Ports Card Type Model Serial No.
--- ----- -------------------------------------- ------------------ -----------
1 8 Intrusion Detection System WS-SVC-IDSM-2 SAD103501HP
2 4 FRU type (0x6003, 0x3B2(946)) WS-SVC-WISM2-K9 SAL1648T81L
[code]....
My company has been contracted to upgrade the 2 WiSM1 modules on a 6509 for a customer. The hardware isn't changing but the software is being upgraded to WiSM2. The cutsomer has HUNDREDS of AP's and dozens of VLANs and subnets (large municipality and school district).
Cisco SE's have been pushing the customer to purchase the WCS 7 software (they've been managing these Controllers independantly) stating there is no mechanism to upgrade WiSM1 configs to WiSM2. I am vaguely familiar with the cisco controllers but have little WiSM experience. So i feel like i'm working without a net here.
So,
1) Any way to migrate from 1 to 2 without the WCS and without having to reinvent the wheel?
2) How does the WCS make this transition easier? What does it do to the WiSM1 configs to make them WiSM2 compatable?
Just loaded the 7.2.103.0 software onto the brand new WiSM2. Going throught the options and have found that under the global parameters for 802.11a/n, 802.11b/g/n radios is now the "Maximum Allowed Clients" option. The allowed setting is from 1 - 200 clients.
Does that mean only 200 clients will be allowed to associate to the WLC on that radio at a maximum?
Doesn't seems to make sense... I have the 500 AP license on this WiSM2... I know this option used to be an optional setting under a WLAN in previous releases.
I have a wireless network running with Controller WISM2 and I also have a NCS.I want to know if there is any way to look of individual log of CAPWAP and LAPWAP Access Points. It is better if I can see it through NCS.
View 1 Replies View RelatedI have a situation where a customer doesn't have the required power units installed in their 6500 for me to provision a WiSM2.They use a VSS pair with a single Sup720 in each. They have no intention of adding a second Sup to each chassis.
I need to justify why they can't use slot 6 (which has power reserved) if I am to get them to upgrade the PSU's. The documentation I've found says it is supported but not recommended.
I've installed our previous WISMs and other WISM2s previously and never had a problem.
6500 running SXJ2. WISM2 running 7.3.101.0 (which is what the rest of our WISM2s are on)
Insert WISM and go through initial setup. Run a show wism status on the 6500, and show sysinfo on the WISM. All looks good. Service port and management vlans are up. From the 6500 I can ping the service port IP, but not the management IP. From the WISM I can't ping the managment default gw but I can the service port. Unable to get anything back from the GUI..not surprising as not even ping works.
Now, as I said I've done it this way many times before...in fact I'm following my documentation from the last successful implementation and even adding in Cisco docs.
how to safely remove the WiSM2 from the Catalyst 6500 series switch? According to the documentation "Catalyst 6500 Series Wireless Services Module 2 Installation and Verification Note":
To remove the WiSM2, perform these steps:
Step1 Shut down the module by one of these methods: In privileged mode from the router prompt, enter the hw-mod module mod shutdown command. NoteIf you enter this command to shut down the module, you must enter the following commands in global configuration mode to restart (power down, and then power up) the module: Router# no power enable module modRouter# power enable module mod If the module does not respond to any commands, press the SHUTDOWN button located on the front panel of the module.
Step2 Verify that the WiSM2 shuts down. Do not remove the module from the switch until the POWER LEDis off.
But, in the case of Step1 (1st methods) I do not see a option "shutdown" in the command "hw-mod module 3"...
All I prompted to enter is: c6500#hw-module module 3 ?
boot Specify boot options for the module through Power Management Bus control register
reset Reset specified component
simulate Simulate options for the module Is it hidden options?
IOS version of c6500 is 12.2(33)SXJ1
In the case of Step2 (2nd methods) there is not any button on the front panel of the module?
And yet, it is better to remove the module configuration manually or use the command module clear-config prior to removing the module?
it is normal for the WISM2 time to be resetted to default of 1 Jan 2000 after rebooting the 6506E if no NTP is configured?I had to configure it back to the correct time. If not, the APs will not come up.Also, does the ap or wlc keep track of the ap group the ap is provisioned to?
View 3 Replies View Relatedwe are running callManager 7.1 (user accounts are tied to AD)... one night our call manager got rebooted by IT. upon reboot, CM failed over to the Subscriber node. Some how IT got Callmanger back over to the Publisher node.....No now of us can log into CallManager using our AD accounts...
View 2 Replies View RelatedWe got recently a Cisco Secure ACS 1120 and i upgraded the Appliance to 5.1 from 5.0 with all your support
Now I need to integrate Cisco ACS 5.1 with RSA Authentication Manager 6.1 . I Successfully Downloaded config file from RSA ACE Server and exported into ACS 1120.
I also Added ACS as a NetOS Agent in the RSA Server , during the process i found few warnings . The ACE Server is not able to Resolve the IP Address to NAme ( DOes it Necessary ?? ).
I havent created any secret Key file for communication between ACS and RSA and encryption i used is DES.
Now when I log into ACS and search for Devices in the Identity Store Sequences i am not able to Look for RSA Token Sever .
I want to know if the Cisco 2900 series can do UC without having to buy any other hardware.I read through the 2900 series datasheet, and i can understand it does.But will want to clarify if i do not need any other hardware except the Unified Communications License for Cisco 2901-295.Does this mean all i need to activate UC is buying this license?My organisation wants to do UC, especially Voice and Wireless.It requires APs, IP Phones(both wired and wireless).To achieve this on a 2900 series, is all i need just the UC license to work, and then my IP Phones both wired and wireless once plugged to the switch connected to the 2900 series starts working?Or do i still need to buy another hardware for the Unified communication Manager Express ?
View 1 Replies View RelatedI am having Cisco LMS 3.2.I want to give an access to some desktop administrators so that they can pull the report of User Tracking in campus manager. Is there any way so that I can restric users to campus manager only?
View 9 Replies View RelatedUTLite33.exe from Campus Manager 3.3 does not want to start, it gives the following:
"UTLite33.exe is not a valid Win32 application".
i have a 1841 cisco router and i recently purchased a 1 port HWIC wan interface card. My problem is that I cannot see the interface in my config file. Is there something i am missing?
View 8 Replies View RelatedI have a Cisco ASA 5505 and I have my internal and external interfaces configured but I currently cannot ping from the inside to an IP Address on the outside. I had this setup and working and I have another set of equirement that I am replacing that is working with my service provider so I know it is a configuration issue. When I ping 4.2.2.2 for example I get:
Destination host unreachable
Do I need to add a static route from my inside interface to my outside interfaces?
: Saved
:
ASA Version 8.2(5)
!
hostname pxasa
[Code].....
Is it possible to set up a WAN interface on a FastEthernet interface of a Cisco 877 Adsl Router ?Due to my ISP, i've to use an external VDSL modem and must connect it to my cisco 877 router (and leave it's adsl interface unused).But i don't know how to set up a wan port, other than the adsl interface itself (dialer0), on my cisco.
View 7 Replies View RelatedWe are having Cisco ASA 5540 having Cisco Adaptive Security Appliance Software Version 8.0(5)23 at certain time of moment daily wer are facing latency and packetdrop wherin when I checked for ASA Interface which gives me " Input Errors" on outside interface ,so can any one tell me what are the causes to get input errors on cisco asa outisde interface.
View 2 Replies View Related