WiSM 7.0.240.0
Guyz while checking on all WCS in security tab , attacks detected and then wIPS Denial of Service Attacks also wIPS Security Penetration Attacks does that means i have build in Wips coz im confused when i try checking Wips profiles it says none or is it like a part of default prevent attacks and i'll have to buy Wips to do a further deep packet inspection.
The Issue which you have presented , is not that clear. However, what I understand , you are worried about default alarms. Please have a look over the alarm policies and pre configured profiles on below, it will clear your doubt.
http://www.cisco.com/en/US/docs/wireless/wcs/7.0MR1/configuration/guide/wips_ench.html
Similar Messages
-
AP wont change primary WLC w/o re-boot.
Hi all!
I have som problem with a WiSM2-wlc running 7.3.101.0. We have APs that should be moved to an other WLC and we want to to it as smooth as possible. But when changing the primary WLC for an AP, the AP will not move to newly configured WLC. As for moving a AP to the WiSM2, its not a problem, they move to within minutes.
I have tried some different scenarios, move from and to:
WiSM2(7.3.101.0) -> WiSM2 (7.3.101.0)
WiSM2(7.3.101.0) -> WiSM (7.0.240.0)
and also tested with differnt AP-models, AP1142, AP2602 and AP3602, but same "problem" with all AP-models. I thinik that there is something wrong with this WLC, we have re-booted it but there is no differnce.
Anyone have a clue where to continue the trouble shooting?
Thanks!You´re right! For the 2602 and 3602 I only have tested WiSM2->WiSM2
So what's the problem again?
WiSM2 are running different firmware than the WiSM1.
So when your 1140, 2600 and 3600 falls back from WiSM2 to WiSM1, only the 1140 and 3600 will go across. When the APs go across, they will download the firmware for WiSM1 and reboot.
Same holds true with the APs return back to the WiSM2.
Besides, what you are doing now is about to become obsolete due to High Availability, Stateful Switch Over (AP SSO) for WiSM2. -
Migrate AP from WiSM to Virtual WLC
Hello all,
We have WiSM installed in Core Switch 6500 having 300+ AP registered on it.
We want to migrate our AP's to new Virtual WLC. What is the best way to migrate AP to new vWLC with less down time.
Can we migrate AP's from WiSM to Virtual WLC in bulk ( all in one time)? I read some where in form that AP version 7.3 & above start supporting vWLC. I am not sure if this applies for WisM as well ( i am assuming WiSM & WLC are differnt) ?
My WiSM is running 7.0.240.0 & vWLC is 7.4. please check the WiSM attachments.
Also is there any way to take backup from WiSM and restore on vWLC ?
Regards.Hi,
First of all, in order to reduce downtime, I would recommend that you upload the 7.4 code on the WiSM and predownload it to all the APs. (Wireless -> Global Configuration - AP Image Pre-download).
Another thing would be to configure the vWLCs as back-up Primary & Secondary Controllers (Wireless -> Global Configuration - High Availabiliy). Doing this your APs will already know about the new WLC when the first will go down and will not have to go through discovery process. (test from AP CLI with show capwap client config)
For the AP mode "mass-conversion" to flexconnect I don't know a better way than from WLC CLI, using:
config ap mode flexconnect submode none AP_NAME_1
config ap mode flexconnect submode none AP_NAME_300
You could use text file to edit the the command with the AP names and than paste it all at once in the WLC. It would be wise to test it first with a few lines.
If you did all this, when your old WLC goes down all your APs should associate to the new WLCs.
Best regards,
Sebastian -
How many APs Can I join a WLC 4402 and WiSM?
I have a WLC with 20 APs joined into the same management VLAN and
I'll deploy other campus with 240 APs and 2 WiSMs Blade.
Is there any recomendation about how many APs Can I put on the same management VLAN?
thanks a lotCisco recommends 60 - 100 access points per vlan. Attached is the best pratices document
https://cisco.hosted.jivesoftware.com/docs/DOC-4204 -
Hello,
I'm going to be migrating my wireless controller from a WiSM module running 7.0.240.0 to a new 8510 which will be running the latest code 7.6.110.0. I would appreciate any help on the best game plan to make this happen as smoothly as possible. Required downtime isn't too big of an issue. Our AP's are mostly 1042n's and 1142n's with a few 1131AG's and 1262n's, which from what I can tell won't be an issue as of now. We currently have close to 200 AP's split between the 2 controllers on the WiSM.
I've never migrated a controller before so I'm not sure what the best approach to this will be, I realize there will be a hiccup since there is no way to run identical code on the old controller and the new. Would the best approch be to add the new controller's ip address to the High availability setting in the WiSM and then take the WiSM offline, let the AP's find the new controller and then download the latest image?
There will be no issues with bringing the new controller online before I'm ready to migrate the AP's to it correct?
Appreciate any help!I have not done this by myself.
But general advise I could give is bring your 8510 up with different managment IP & configure it with SSIDs, dynamic interfaces & put it on to the same mobility group. Here is some best practices you can follow when configuring a WLC
http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/82463-wlc-config-best-practice.html
Then take a small subset of AP & make 8510 as primary WLC for those. makesure everything is working as expected & then do a bulk cutover once you have tested services on your new controller.
HTH
Rasika
*** Pls rate all useful responses **** -
Hi,
I have WiSM with IOS version 7.0.240 (newest available - both controllers have the same version upgraded)
The problem is:
One laptop connected to AP "A" (CISCO 3502) which is connected to different cabinet using CISCO 2960S to WiSM A using CISCO .
This Laptop connects and can see clients in the room (in area of AP "A" with the access point wired too .
Another Laptop connected to AP "B" (CISCO 3502) which is connected to different cabinet to WiSM B.
This Laptop connects and can't see clients in the room (in area of AP "B" with the access point wired too.
Both laptops share the same SSID in the same subnet in the same 6509 core switch , but on different WiSM.
Broadcast forwarding is enabled
It's look like this:
Laptop A ---->>> AP "A" 3502 ------C2960S ----- WISM "A" on core 6509 WiSM "B" ------C2960S --------AP "B" 3502 <<<----Laptop "B"
All laptops are new, the same setup imaged, the same subnet.
The question:
- why laptop B can't see any clients in area of AP "B" but laptop "A" can.
There's no filtering between on core 6509, 2960S and any WiSM. All traffic is passed.
Regards
PiotrMake sure P2P is allowed and not set to drop. This is located on the WLAN SSID advanced tab.
Sent from Cisco Technical Support iPhone App -
WiSM having trouble getting the IP from service-vlan DHCP
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.
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 it by doing a session switch 1 slot 4 processor 1. I get the following upon attempting to do so:
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,wired client is working & able to get IP from vlan 300 DHCP pool.
Here is the complete configuration.
Core-Switch6509#sh run
Building configuration...
Current configuration : 21462 bytes
upgrade fpd auto
version 12.2
service timestamps debug datetime msec
service timestamps log datetime msec
service counters max age 5
hostname
boot-start-marker
boot system flash sup-bootdisk:
boot-end-marker
security passwords min-length 1
logging buffered 8192
no aaa new-model
ip subnet-zero
ip dhcp excluded-address 192.168.200.1 192.168.200.2
ip dhcp pool wism-service-port
network 192.168.200.0 255.255.255.0
default-router 192.168.200.1
ip dhcp pool voiceFLR1
network 10.39.103.128 255.255.255.128
default-router 10.39.103.254
option 150 ip 10.39.139.240 10.39.139.241
ip dhcp pool voiceFLR2
network 10.39.104.128 255.255.255.128
default-router 10.39.104.254
option 150 ip 10.39.139.240 10.39.139.241
ip dhcp pool voiceFLR3
network 10.39.105.128 255.255.255.128
default-router 10.39.105.254
option 150 ip 10.39.139.240 10.39.139.241
no ip domain-lookup
vtp domain
vtp mode transparent
switch virtual domain 100
switch mode virtual
mls netflow interface
mls cef error action reset
spanning-tree mode pvst
spanning-tree extend system-id
wism service-vlan 300
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
diagnostic bootup level minimal
redundancy
main-cpu
auto-sync running-config
mode sso
vlan internal allocation policy ascending
vlan dot1q tag native
vlan access-log ratelimit 2000
vlan 101
name Grd_FLR_Data_Vlan
vlan 102
name Grd_FLR_Voice_Vlan
vlan 103
name MZ_FLR_Data_Vlan
vlan 104
name MZ_FLR_Voice_Vlan
vlan 105
name 1st_FLR_Data_Vlan
vlan 106
name 1st_FLR_Voice_Vlan
vlan 107
name 2nd_FLR_Data_Vlan
vlan 108
name 2nd_FLR_Voice_Vlan
vlan 109
name 3rd_FLR_Data_Vlan
vlan 110
name 3rd_FLR_Voice_Vlan
vlan 111
name 4th_FLR_Data_Vlan
vlan 112
name 4th_FLR_Voice_Vlan
vlan 113
name 5th_FLR_Data_Vlan
vlan 114
name 5th_FLR_Voice_Vlan
vlan 115
name 6th_FLR_Data_Vlan
vlan 116
name 6th_FLR_Voice_Vlan
vlan 117
name 7th_FLR_Data_Vlan
vlan 118
name 7th_FLR_Voice_Vlan
vlan 119
name 8th_FLR_Data_Vlan
vlan 120
name 8th_FLR_Voice_Vlan
vlan 121
name 9th_FLR_Data_Vlan
vlan 122
name 9th_FLR_Voice_Vlan
vlan 123
name 10th_FLR_Data_Vlan
vlan 124
name 10th_FLR_Voice_Vlan
vlan 125
name Wireless_Users
vlan 126
name Wireless_Guest
vlan 150
name Printer
vlan 151
name v151
vlan 152
name v152
vlan 153
name v153
vlan 154
name v154
vlan 155
name v155
vlan 183
name Network_Management
vlan 300
name WiSM_Service_Vlan
interface Port-channel1
description *** For 1st Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel2
description *** For 2nd Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel3
description *** For 3rd Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel4
description *** For 4th Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel5
description *** For 5th Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel6
description *** For 6th Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel7
description *** For 7th Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel8
description *** For 8th Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel9
description *** For 9th Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel10
no switchport
no ip address
switch virtual link 1
mls qos trust cos
no mls qos channel-consistency
interface Port-channel11
description *** For 10th Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel12
description *** For Ground Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel13
description *** For MZ Floor ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface Port-channel20
no switchport
no ip address
switch virtual link 2
mls qos trust cos
no mls qos channel-consistency
interface TenGigabitEthernet1/1/1
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
shutdown
interface TenGigabitEthernet1/1/2
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
shutdown
interface TenGigabitEthernet1/1/3
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 1 mode on
interface TenGigabitEthernet1/1/4
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 2 mode on
interface TenGigabitEthernet1/1/5
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 3 mode on
interface TenGigabitEthernet1/1/6
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 4 mode on
interface TenGigabitEthernet1/1/7
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 5 mode on
interface TenGigabitEthernet1/1/8
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 6 mode on
interface TenGigabitEthernet1/2/1
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 7 mode on
interface TenGigabitEthernet1/2/2
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 8 mode on
interface TenGigabitEthernet1/2/3
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 9 mode on
interface TenGigabitEthernet1/2/4
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 11 mode on
interface TenGigabitEthernet1/2/5
description *** Connected to Juniper Port Ten 0 Inside ***
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
switchport nonegotiate
interface TenGigabitEthernet1/2/6
no switchport
no ip address
interface TenGigabitEthernet1/2/7
no switchport
no ip address
interface TenGigabitEthernet1/2/8
no switchport
no ip address
interface GigabitEthernet1/3/1
switchport
switchport access vlan 183
switchport mode access
interface GigabitEthernet1/3/2
switchport
switchport access vlan 183
switchport mode access
interface GigabitEthernet1/3/3
switchport
switchport access vlan 183
switchport mode access
interface GigabitEthernet1/3/4
switchport
switchport access vlan 183
switchport mode access
interface GigabitEthernet1/3/5
switchport
switchport access vlan 154
interface GigabitEthernet1/3/6
switchport
switchport access vlan 154
interface GigabitEthernet1/3/7
switchport
switchport access vlan 154
interface GigabitEthernet1/3/8
switchport
switchport access vlan 154
interface GigabitEthernet1/3/9
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/10
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/11
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/12
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/13
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/14
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/15
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/16
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/17
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/18
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/19
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/20
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/21
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/22
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/23
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/24
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/25
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/26
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/27
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/28
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/29
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/30
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/31
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/32
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/33
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/34
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/35
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/36
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/37
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/38
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/39
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/40
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/41
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/42
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/43
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/44
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/45
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/46
no switchport
no ip address
shutdown
interface GigabitEthernet1/3/47
switchport
switchport access vlan 107
switchport mode access
spanning-tree portfast edge
interface GigabitEthernet1/3/48
switchport
switchport access vlan 152
switchport mode access
interface GigabitEthernet1/5/1
no switchport
no ip address
shutdown
interface GigabitEthernet1/5/2
no switchport
no ip address
shutdown
interface GigabitEthernet1/5/3
no switchport
no ip address
shutdown
interface TenGigabitEthernet1/5/4
description *** Connected to CS-2 Port Ten 2/5/4 ***
no switchport
no ip address
mls qos trust cos
channel-group 10 mode on
interface TenGigabitEthernet1/5/5
description *** Connected to CS-2 Port Ten 2/5/5 ***
no switchport
no ip address
mls qos trust cos
channel-group 10 mode on
interface TenGigabitEthernet2/1/1
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
shutdown
interface TenGigabitEthernet2/1/2
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
shutdown
interface TenGigabitEthernet2/1/3
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 1 mode on
interface TenGigabitEthernet2/1/4
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 2 mode on
interface TenGigabitEthernet2/1/5
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 3 mode on
interface TenGigabitEthernet2/1/6
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 4 mode on
interface TenGigabitEthernet2/1/7
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 5 mode on
interface TenGigabitEthernet2/1/8
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 6 mode on
interface TenGigabitEthernet2/2/1
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 7 mode on
interface TenGigabitEthernet2/2/2
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 8 mode on
interface TenGigabitEthernet2/2/3
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 9 mode on
interface TenGigabitEthernet2/2/4
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 11 mode on
interface TenGigabitEthernet2/2/5
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface TenGigabitEthernet2/2/6
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface TenGigabitEthernet2/2/7
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface TenGigabitEthernet2/2/8
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface GigabitEthernet2/3/1
switchport
switchport access vlan 183
switchport mode access
interface GigabitEthernet2/3/2
switchport
switchport access vlan 183
switchport mode access
interface GigabitEthernet2/3/3
switchport
switchport access vlan 183
switchport mode access
interface GigabitEthernet2/3/4
switchport
switchport access vlan 183
switchport mode access
interface GigabitEthernet2/3/5
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/6
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/7
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/8
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/9
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/10
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/11
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/12
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/13
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/14
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/15
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/16
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/17
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/18
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/19
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/20
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/21
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/22
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/23
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/24
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/25
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/26
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/27
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/28
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/29
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/30
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/31
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/32
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/33
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/34
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/35
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/36
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/37
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/38
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/39
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/40
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/41
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/42
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/43
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/44
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/45
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/46
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/47
no switchport
no ip address
shutdown
interface GigabitEthernet2/3/48
no switchport
no ip address
shutdown
interface GigabitEthernet2/5/1
no switchport
no ip address
shutdown
interface GigabitEthernet2/5/2
no switchport
no ip address
shutdown
interface GigabitEthernet2/5/3
no switchport
no ip address
shutdown
interface TenGigabitEthernet2/5/4
description *** Connected to CS-1 Port Ten 1/5/4 ***
no switchport
no ip address
mls qos trust cos
channel-group 20 mode on
interface TenGigabitEthernet2/5/5
description *** Connected to CS-1 Port Ten 1/5/5 ***
no switchport
no ip address
mls qos trust cos
channel-group 20 mode on
interface Vlan1
no ip address
interface Vlan101
description *** Grd Floor Data Vlan ***
ip address 10.39.101.126 255.255.255.128
interface Vlan102
description *** Grd Floor Voice Vlan ***
ip address 10.39.101.254 255.255.255.128
interface Vlan103
description *** MZ Floor Data Vlan ***
ip address 10.39.102.126 255.255.255.128
interface Vlan104
description *** MZ Floor Voice Vlan ***
ip address 10.39.102.254 255.255.255.128
interface Vlan105
description *** 1st Floor Data Vlan ***
ip address 10.39.103.126 255.255.255.128
interface Vlan106
description *** 1st Floor Voice Vlan ***
ip address 10.39.103.254 255.255.255.128
interface Vlan107
description *** 2nd Floor Data Vlan ***
ip address 10.39.104.126 255.255.255.128
interface Vlan108
description *** 2nd Floor Voice Vlan ***
ip address 10.39.104.254 255.255.255.128
interface Vlan109
description *** 3rd Floor Data Vlan ***
ip address 10.39.105.126 255.255.255.128
interface Vlan110
description *** 3rd Floor Voice Vlan ***
ip address 10.39.105.254 255.255.255.128
interface Vlan111
description *** 4th Floor Data Vlan ***
ip address 10.39.106.126 255.255.255.128
interface Vlan112
description *** 4th Floor Voice Vlan ***
ip address 10.39.106.254 255.255.255.128
interface Vlan113
description *** 5th Floor Data Vlan ***
ip address 10.39.107.126 255.255.255.128
interface Vlan114
description *** 5th Floor Voice Vlan ***
ip address 10.39.107.254 255.255.255.128
interface Vlan115
description *** 6th Floor Data Vlan ***
ip address 10.39.108.126 255.255.255.128
interface Vlan116
description *** 6th Floor Voice Vlan ***
ip address 10.39.108.254 255.255.255.128
interface Vlan117
description *** 7th Floor Data Vlan ***
ip address 10.39.109.126 255.255.255.128
interface Vlan118
description *** 7th Floor Voice Vlan ***
ip address 10.39.109.254 255.255.255.128
interface Vlan119
description *** 8th Floor Data Vlan ***
ip address 10.39.110.126 255.255.255.128
interface Vlan120
description *** 8th Floor Voice Vlan ***
ip address 10.39.110.254 255.255.255.128
interface Vlan121
description *** 9th Floor Voice Vlan ***
ip address 10.39.111.126 255.255.255.128
interface Vlan122
description *** 9th Floor Voice Vlan ***
ip address 10.39.111.254 255.255.255.128
interface Vlan123
description *** 10th Floor Voice Vlan ***
ip address 10.39.112.126 255.255.255.128
interface Vlan124
description *** 10th Floor Voice Vlan ***
ip address 10.39.112.254 255.255.255.128
interface Vlan150
description *** Printer Vlan ***
ip address 10.39.120.254 255.255.255.0
interface Vlan151
description *** Connected to Juniper FW Port Ten 0 ***
ip address 10.39.121.1 255.255.255.240
interface Vlan183
description *** Network Management Vlan ***
ip address 10.39.139.254 255.255.255.0
interface Vlan300
ip address 192.168.200.1 255.255.255.0
ip classless
ip route 0.0.0.0 0.0.0.0 10.39.140.169
ip route 0.0.0.0 0.0.0.0 10.39.121.14
no ip http server
no ip http secure-server
control-plane
dial-peer cor custom
line con 0
login local
line vty 0 4
login local
line vty 5 15
login local
mac-address-table aging-time 480
no event manager policy Mandatory.go_switchbus.tcl type system
module provision switch 1
slot 1 slot-type 227 port-type 60 number 8 virtual-slot 17
slot 2 slot-type 227 port-type 60 number 8 virtual-slot 18
slot 3 slot-type 147 port-type 61 number 48 virtual-slot 19
slot 4 slot-type 242 port-type 31 number 10 virtual-slot 20
slot 5 slot-type 254 port-type 31 number 2 port-type 61 number 1 port-type 60 number 2 virtual-slot 21
module provision switch 2
slot 1 slot-type 227 port-type 60 number 8 virtual-slot 33
slot 2 slot-type 227 port-type 60 number 8 virtual-slot 34
slot 3 slot-type 147 port-type 61 number 48 virtual-slot 35
slot 4 slot-type 242 port-type 31 number 10 virtual-slot 36
slot 5 slot-type 254 port-type 31 number 2 port-type 61 number 1 port-type 60 number 2 virtual-slot 37
end
Thanks & Awaiting for response. -
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.
ThanksHave 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 -
Hi All,
Probably an easy question here.
I am just wondering what I should set my Session Timeout (secs) on my SSID's to int the WiSM's? Mine is currently set to 1800secs, but I sort of want to change it to 300 secs so that when people walk out of a particular building, they will need to re-associate and get a new IP address (If that makes Sense!)
Thanks,There is no exact definiton for session timeouts. In your case it could be 900 secs[15 mins] so hat its not too early session timeouts. Normally users need to reauthenticate if they move to different access points.
-
Captivate Six version 6.0.1.240 Updates not working.
Currently using a client's machine to complete a project. They are not a subscription customer but still surely released patches should work for all clients. Below are the issues encountered:
Most of the Stability items on patch for 240 that we’re already on don’t work properly
Stability
•Occasionally Adobe Captivate crashes when multiple projects are open and the library is clicked just after switching between projects. – Occasionally?? More like almost every time
•The Adobe Captivate menu becomes unresponsive at times. When you click a menu option, the option is not called. But, when Adobe Captivate is closed, the menu operation you called is carried out. This happens a lot
•Adobe Captivate workspace gets corrupted occasionally. As a result, Property Inspector and other panels do not get displayed in the workspace.
•Occasionally Adobe Captivate hangs while saving a project. This behavior is observed in all operations that involve progress bars. The progress bar gets stuck at zero percent and the operation is not completed. This happens a lot
•In some scenarios, Adobe Captivate crashes when you select multiple smart shapes and then try to resize them.
•Adobe Captivate crashes at the end of 'Additional Recording' if the project theme does not contain the Blank master slide
Please advise;
Thanks in advance.
Regards to all.This topic explains about setting up your PC to run Captivate with fewer issues (including how to set the Run As Administrator launch option):
http://www.infosemantics.com.au/adobe-captivate-troubleshooting/setting-up-your-computer-t o-work-with-captivate
This topic tells you all about setting up your Preferences:
http://www.infosemantics.com.au/adobe-captivate-troubleshooting/how-to-set-up-preferences -
Print tpage number/total page number in a report with width more than 240
Dear all,
I need to display total page number as following code sample.
But I need to put it after position 240.
this program can print total page number if it is placed at postion 239 or before.
WRITE: /234(10) 'Heading', 239 SY-PAGNO,'of ', '-----'.
Whenever I put 240 or more WRITE: /234(10) 'Heading', 240 SY-PAGNO,'of ', '-----'.
Total page num could not be displayed.
Please tell me the solution.
thanks
REPORT YPAGECOUNT NO STANDARD PAGE HEADING LINE-SIZE 276 LINE-COUNT 65.
DATA L_PAGE_COUNT(5) TYPE C.
TOP-OF-PAGE.
WRITE : /234(10) 'PAGE', SY-PAGNO,'/ ','-----', ''.
WRITE: /234(10) 'Heading', 239 SY-PAGNO,'of ', '-----'.
ULINE.
START-OF-SELECTION.
Real list output takes place here
DO 1000 TIMES.
WRITE: / 'Line #', SY-LINNO.
ENDDO.
Page count will be printed on each page here
WRITE SY-PAGNO TO L_PAGE_COUNT LEFT-JUSTIFIED.
DO SY-PAGNO TIMES.
READ LINE 1 OF PAGE SY-INDEX.
REPLACE '-----' WITH L_PAGE_COUNT INTO SY-LISEL.
MODIFY CURRENT LINE.
ENDDO.Using Values Greater than 255 for the LINE-SIZE of a List
If you define a fixed column width greater than 255 using the LINE-SIZE addition in the REPORT or NEW-PAGEstatement, the following notes apply:
Type definitions: The type group SLIST defines the valid maximum value for the list width (SLIST_MAX_LINESIZE), and contains a type for list lines with maximum width (SLIST_MAX_LISTLINE).
Accessing the entire contents of a line: To read or modify the entire contents of a wide line, you can use the ... LINE VALUE addition in the READ LINE or MODIFY LINE statements. This is an alternative to using SY-LISEL that is independent of the attributes of the system field (since the length of SY-LISEL is 255 characters).
Horizontal lines: With extra-wide lists, the "ULINE." statement corresponds to "WRITE / SY-ULINE.". So, for example, "ULINE AT 5(300)." corresponds to "WRITE AT 5(300) SY-ULINE.".
Output length: You can use the length specification in WRITE (or ULINE) to extend the output length of an extra-wide list up to the value of LINE-SIZE. If you want to output a whole field that is longer than 255 characters, you must use this, even if the field itself is defined as longer than 255 characters.
Example
NEW-PAGE LINE-SIZE 1000.
DATA: F1(500) VALUE 'F1'.
WRITE: / F1 COLOR COL_NORMAL. " Output with length 255
WRITE: /(500) F1 COLOR COL_NORMAL. " Output with length 500
Awrd Points if useful
Bhupal -
I got my mac book pro in the U.S., but I will be travelling to where there is 240 volt power. Does the mag safe power adapter switch automatically, so I just need a converter plug, or do I need a transformer to convert from 240 to 120 volts? Thanks.
Hi,
I too bought my Macbook Pro in the US and I live in the UK (its so much cheaper in the US! No 20% VAT!)
The power adapter does work on UK 230v power. You can also get a three pin extension lead (like the 2 pin US one that came with the MBP) for about £3 with free delivery from Amazon UK.
Another tip, whne you are back in the UK, and you are switching from a PC to a Mac, get in touch with your local Apple Shop who run one to one free courses on how to use your MBP.
Hope This Helps!! -
LEAP wireless clients work, then fail, Using WISM blades HELP
I am at a complete loss. Calls to Cisco, working with different vendors, nothing has worked to solve the problem. This is what we see, and we see this at every single one of our hospital sites.
All hospitals used to run just IOS code on their AP's. Some hospitals used the older 1200 series AP's, which have been upgraded from B only radios to A/B/G. Some hospitals were rolled out with newer 1240 series AP's. Every single hospital was just fine when using IOS code on the AP's. Users never disconnected or disassociated. They were fine. Clients run a mixture of the old Cisco 350 series cards, or Ubiquiti A/B/G cards.
Now, fast forward and we started installing WISM blades in all the 6509 distribution switches at each hospital. AP's were then upgraded to lightweight code and at first everything seemed great. Then the calls started.
All clients at all hospitals will just disassociate. It is completely random. Some machines can see it once, others 50 times a day, then tomorrow, totally different. I have witnessed the same thing with my laptop. We have 3 WLAN's in the hospitals. One that uses LEAP authentication, one that uses Certificates, and one that is our Patient WiFi. Both LEAP and Certs have the issue. I have never been kicked off of the Patient WiFi system. Not once.
LEAP clients use the same exact ACS servers they have always used. Nothing changed in the configs. Same goes for the clients using certificates.
I have upgraded code on the WISM blades 3 times now. Currently we are using the 5.187 code. I have tried forcing all AP's to use only B/G radios, tried using only A, doesn't matter. Same problem happens.
What is even worse, when this event happens, 50% of the time you have to actually reboot the workstation to get it to log back onto the wireless network. It fails the attempt and it just stops. This is not everyone at the same time either. There seems to be no event that I can find where all clients have the problem at the exact same time. I can have two devices side by side, same exact NIC, same software, everything. One will disassociate, the other is just fine.
I am out of ideas. Everyone I talk to at Cisco says never heard of this before. I just can't believe we are the only ones that have ever seen this problem.
I can take the same workstation that is breaking left and right on our wireless networks using the WISM blades, go to a site with AP's still in IOS mode, it will never disassociate and disconnect.
Has anyone heard of this, have any ideas of something I could try. Would you like to see any other information about this? I can post whatever you like to help. I am looking for any assistance on this.
I have been trying to do some searches on this forum, but for whatever reason it seems to be very slow so thought I might post my issue as I search around, maybe if it has already come up and there is a fix, someone could direct me right too it.
Thank you in advance.I tried that in the beginning. Put all ap power and channel as hard set. It did not change anything. I am not sure if we have tried the 4.2.207 code. I know we went through several 4.x.x codes in testing. Cisco recommended the lastest one that we are on now.
What really gets me is how everything worked just fine until the WISM upgrade. No AP placement changed, no additional AP installs, we just installed the WISM blades, migrated code to lightweight and everything started flaking out.
What other NIC's do people use? Maybe the brand we use is not any good? I have been up and down with the vendor, tried different drivers, nothing seemed to change anything.
It looks to me like the WISM sends out some kind of response that the workstation NIC's do not understand, so they just sit there. On wireless sniffer traces, you can see where the request goes out to the workstation, but the workstation just never responds, hence the lockup so to speak. It will just sit there until a reboot of the PC. -
Hi,
I'm seeing the following error on our clients WiSM (WS-SVC-WISM2-K9) installed in a 6500 chassis:
*dtlDataLowTask: Mar 10 08:50:21.088: %SYSTEM-3-MBUFF_ALL_USED: sysapi_if_net.c:223 No free Mbufs available.Shared memory allocation failed. Internal system error. *dtlArpTask: Mar 10 08:50:19.084: %SYSTEM-3-MBUF_ALLOC_FAIL: sysapi_if_net.c:602 Cannot allocate new Mbuf.Internal system error.
I've taken a look through cisco.com and there are known issues but no fixes but only on WLC's rather than WiSM. Has anyone ever seen this issue before on WiSM?
Regards
NeilMay be you are hitting a bug.
Must contatc TAC and provides the log.
Regards -
Satellite P100-240 - Doesn't boot properly
I'm posting on behalf of a friend who has this problem, we only have contact via mobile texts :( I may not be able to immediately provide all the answers you seek to resolve this problem.
Hi,
The laptop (P100-240) turned itself off whilst playing a game 2 days ago, since then the following problems have been experianced;
Loading windows in normal mode results in instant Blue Screen (specific info unavilable). Windows in normal mode has not been accessed since this problem began.
Loading windows in safe mode worked for a while, but internet access resulted in Blue Screen aswell, for a while this problem resolved itself, safe mode no longer works to my knowledge.
The visual display appears at all times distorted, a matrix like effect. I don't know wether this effect is passive, or only during windows or startup, details on how it looks or anything very specific.
A blue screen mentioned the file nv4_mini.sys, this is an nvidia driver file for laptops as far as I know. A gfx driver update cured nothing.
The current situation is total lack of access to the desktop, I think it blue screens just after the welcome screen. I don't know what the blue screen says atm, but the disabling of memory options in the bios was recommended by something... I don't know wether the option is even available to the p100-240s bios system, googling this problem came up with mentions of disabling video caching and shadowing options in the bios as the definition of bios memory options, and that these options don't always exist.
However, my diagnosis is that the video card is just fried :( which would be a worse problem than a software or options problem as far as a quick and simple solution is concerned.
Any solutions, advice or questions? I'm struggling to find and give useful advice, and learning the situation in detail is tricky aswell.
So far a registry clean has been done, an anti-virus scan has been done, a system restore has been done, a video card driver update has been done and a bios update has been done. In that order, for what relevance that has.
Help? :\
I've seen similar problems on the internet, but only once was it a near-identical problem with the same model of laptop.The Nvidia GeForce Go 7600 is a separate card that attaches to the bottom of the motherboard on the top left side.
The card itself has a fan/heat sink unit attached to it and measures about 3x5 inches. I have become intimately familiar with this card and the P100 in the apst few days.
Laptop worked until one day the screen went blank. Not dark black blank when its off, but rather when the backlight is on but no immage is available. The laptop starts in safe mode and also in the VGA mode. The problem can be seens even before windows starts up. There are vertical lines across the screen, they either distort color on the image (as in the toshiba welcome screen) or plainly black out letters as in the widnows start-up selection screen. Sometimes restarting after VGA mode removes these lines and system starts up normaly. Then once booted the screen goes blank either right away or in 5/10/20 minutes. I have replaced the video card and the system board to no avail.
I think I will try replacing the screen power inverter next, will see if it will help.
My unut is P100, PSPA3U-04501T
the screen is 1680x1050
GPU is GEForce Go 7600, 256 mb
Maybe you are looking for
-
Hello Experts, Can you please help me on understanding the RCTI flow in SAP and how do we configure? Please help. Regards, Rahul Moderator message: please search for available information/documentation. Edited by: Thomas Zloch on Nov 23, 2011 11:57 A
-
Where can I find windows trial version for SAP NetWeaver 7.0 (2004s)
Hi Where can I find windows trial version for SAP NetWeaver 7.0 (2004s)?, I can only see Linux version. Any help is appreciated.. - Jai
-
Simple but ..... (Master Detail Table)
HI, I'm developing database application with Form5 which It has master detail relationship. Let's say I have 3 blocks(A,B,C) that relate to the tables. Block A is the parent of all blocks and B is parent of block C. The problem is everytime user ente
-
I get my homepage or any website comes up twice whengoing to the internet. what do I need to do?
I am using firefox and when I go to the internet everything comes up twice instead of just one time.
-
Ipad Restore will not go past "preparing ipad for restore"
My ipad is frozen on the "connect to iTunes" screen. iTunes is stuck on "preparing ipad for restore" and will not continue, I have disconnected & turned off the ipad and started over several times. It always does the same thing.