4006: 802.1x support?

EOL has been announced for Cat 4006. Is anyone out there using 802.1x on these switches. If yes, could you please let me know what is the IOS.
The cisco feature selection tool (http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp) says 8.4(11)GLX is available on CAT4000 with 802.1x. Not sure if it's the same.
Thanks
Ravi

The 4006 can have either sup 1 or sup 2 which are no longer being sold, these run CatOS. 4006 Chassis can alos support Supervisor Engine III (WS-X4014), and Supervisor Engine IV (WS-X4515) which runs IOS. 802.1x feature was first supported in version 6.2 for CatOS and since 12.1(19)EW on IOS.
CatOS Release Notes:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat4000/relnotes/ol_2117.htm
CAt IOS Release Notes:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat4000/relnotes/ol_2170.htm
So, I hope this answers your questions:
Is anyone out there using 802.1x on these switches. If yes, could you please let me know what is the IOS.
A: Sup1 and Sup2 for Ca4000 can only run CatOS. 802.1x had been supported since 6.2. Sup2+, Sup3 and Sup4 runs IOS and 802.1x had been supported since 12.1(19)
The cisco feature selection tool (http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp) says 8.4(11)GLX is available on CAT4000 with 802.1x. Not sure if it's the same.
A: 802.1x is 802.1x for CatOS or Cat IOS just the CLI will change so one and the same
Please rate all posts.

Similar Messages

WinPE 5 802.1x Support with SCCM 2012 R2

Please see updated information a few posts down.
I am trying to get 802.1x support working to deploy windows 7-8 machines using MDT2012. I have checked IEEE 802.1x network authenication protocol under features of the deployment share properties. I am trying to follow the guide on the deploymentguys.
I have my files on the boot image and can do a net start dot3svc, we are not using certificates at the moment for our 802.1x so I am skipping that line. doing a netsh lan add profile filename="X:\8021x\ Local Area Connection.xml " interface="Ethernet2"
does work. I am having a problem with the third step when I run the following command netsh lan set eapuserdata filename=x:\8021x\Wired-WinPE-UserData-PEAP-MSChapv2.xml allusers=yes interface="Ethernet2" All i get is error setting
user data for interface ethernet2, the operation is not supported.
How does one get 802.1x working in WinPE 4.0?
Heres the latest updated in this first post so you dont have to scroll way to the bottom to get the latest relevant information:
So here's the current situation and hopefully someone has seen it before.
My boot image has the prestart command set to x:\8021x\configure8021x.cmd. If i make a USB boot media this command will run and work with an 8021x wire plugged in. If I PXE boot with a non8021x
wire plugged in this command will run. If I PXE Boot with an 8021x
wire plugged in it does not run the command. If the boot image gets staged from the windows software center it
also will not run my command.
Does anyone know why the staged boot image and booting from PXE are not running my prestart command? It seems that during PXE and staged boot that the network initializes BEFORE it runs any prestart commands?

Well progress on this issue has been made. So why I was getting the operation not supported is because I was exporting our corporate 8021x LAN profile which gets put in place by group policy, which i assumed would work. So i unjoined the windows
7 machine from the domain and was then able to modify the LAN profile to be what is exactly in the documentation with images.
Then the above command works and I no longer get the operation is not supported and I am able to move on to the next steps which is to create a script file which contains the net start and the netsh commands i was using above to test it. Great!
Now my next issue comes up when the instructions tell me to modify the winpeshl.ini file which it says is located at X:\windows\System32\Winpeshl.ini. So I mount the boot.wim file that I did earlier and I browse to the location in question however
the first thing I notice is that when I open the winpeshl.ini file to go to modify it I expect to see:
[LAUNCHAPPS]
“%SYSTEMDRIVE%\sms\bin\i386\TsBootShell.exe”
Instead what I find is it says:
[LAUNCHAPPS]
%Windir%\system32\netstart.exe, -prompt%SYSTEMDRIVE%\sources\recovery\recenv.exe
So I thought ok I will create a copy of this file and rename it to winpeshl.ini.bak and then modify it to say what It says it should be in the instructions which is:
[LAUNCHAPPS]
winpeinit.exe
%SYSTEMDRIVE%\Windows\System32\wscript.exe, %SYSTEMDRIVE%\8021x\Configure8021xUser.wsf
“%SYSTEMDRIVE%\sms\bin\i386\TsBootShell.exe”
Next I unmount the boot.wim file and overwrite the copy I had. Next I update the distribution points and PXE boot a test machine. What I see next is
what I dont understand. Upon booting and hiting F8 to get to a command line I cd into x:\windows\system32\ and notice that I do indeed still have my winpeshl.ini.bak file so I open the winpeshl.ini file I had thought I modified earlier and low and behold
it contains this which is different when I look at it when I mounted the wim file:
[LAUNCHAPPS]
“%SYSTEMDRIVE%\sms\bin\i386\TsBootShell.exe”
So something is modifying this file and setting it this way effectively overwriting what I put in so that my script can run and configure the 8021x user settings.
Is there some updated documentation somewhere, how do I proceed from here??
The next steps after this would be to modify the unattend.xml file at a certain location to run the Configure8021xUserWindows.wsf script which does the winpe script just instead
of running from X: it runs from C: as it says in the documentation. But I can't move on to test this yet without getting the winpe part working.

No 802.11n support in macbook pro leopard install

I upgraded my MacBook Pro to Leopard last week (and then updated to 1.5.1 yesterday)
Other users here have claimed that they see 802.11n support in the Network utility (choosing en1 as the Network Interface). However, I do not. I only see a/b/g.
I also went ahead and purchased the 802.11n enabler (for $2.16). I got an error message that the software is incompatible with my hardware. My guess is that the enabler is probably incompatible with Leopard - although the Apple Store says nothing about this.
Why did others get 802.11n installed automatically via their Leopard upgrade but in my case it did not?
How do I upgrade my MacBook Pro (10.5.1) to 802.11n?
Thanks,
Bill

I just realized that I don't have the right mbpro for 802.11n as I don't have core 2 duo.
***** to be me I guess.
I'll look for an after market solution to upgrade to 802.11n.
Thanks.

Help Enabling 802.11b Support

Can anyone help? All I want to do is enable 802.11b support on my Cisco 877W. My 802.11g clients can see and attach to it no problems. My 802.11b clients cannot see it at all. I have tried all sorts but nothing has helped. My config looks like this:
interface Dot11Radio0
no ip address
encryption key 1 size 128bit 7 BC48CE99C4E9B683819990D3C1A5 transmit-key
encryption mode wep mandatory
ssid *****
authentication open
speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0
48.0 54.0
station-role root
no dot11 extension aironet
bridge-group 1
bridge-group 1 spanning-disabled
What do I need to add to make it visible and available to 802.11b clients?
Many Thanks,
Matt

I'd start by defaulting the AP back to factory default, no WEP, no authentication.
Check to see if the 802.11b clients can connect.
If all the 802.11b clients are running the same software, check to see that they are up-to-date drivers & client software. If you're using the MS client software (Zero Wireless Config) try a client using the vendor's client software instead.
If the clients are not eve associating, look at the basic parameters: things like preamble length (legacy default is "long" which is a one meg data rate)
If you can get the 802.11b client to connect whith all open parameters, then add WEP. Be advised that some clients need the WEP entered as HEX, not ASCII.
For example ASCII "ABCD" would be "41 42 43 44" in hex ... make sure you're using the same system. IF youre using something like "12345abcde" that can be a valid (but incorrect) hex string when ou really intend for it to be ASCII.
Also note that leading or training spaces (ASCII 20) are valid characters. Make sure you do not have leading or training spaces in your WEP (unless you really want them there, in whch case, make sure they're there)
Make sure the Ethernet format is correct: use the Web GUI to set up. Check the parameters on the "Interfaces" page and do not (at least initially) use the "Best throughput" or "Best Range" settings, leave it at "Default Settings"
If your 802.11b clients are PDAs, bar-code scanners, or other hand-held devices, check that they are at default settings for the standard 802.11b protocols; some use proprietary protocols for better performance or security.
That's about it for me ... let us know if any of that changes (works / doesn't work, but acting differently / doesn't work, looks the same).
Good Luck
Scott

Clarification on 802.1x support for 3560

Hi all: have a question on support of 802.1x support in 3560.
This (http://www.cisco.com/en/US/products/hw/switches/ps5528/products_configuration_guide_chapter09186a00801e85c4.html) one talks about 802.1x configuration on a 3560 with 12.1(19)EA1
But this tool http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp tells me that IEEE 802.1x-VLAN Assignment is supported only on ED Releases 12.2(25)SEE1, 12.2(25)SED1, 12.2(25)SEC2, 12.2(25)SEB4, 12.2(25)SEA, 12.2(25)SE for 3560.
Does this mean Cisco is recommending using 12.2.(25) for 802.1x for these switches eventhough 12.1(19) supports it?
Thanks
Ravi

Only the following 3560 are supported in 12.1.19EA1:
Catalyst 3560-24PS
Catalyst 3560-48PS
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3560/12119ea1/ol510401.htm#84866
The rest of 3560 have different minimum IOS requirements:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3750/125see1/ol9586.htm#wp84866
So, wht I am trying to say is, the feature, 802.1x-Vlan Assignment is supported in 12.1(19)EA1 but depending on what kind of 3560, it will require a minimum IOS. If your 3560 is either Catalyst 3560-24PS or Catalyst 3560-48PS, you can run 802.1x-Vlan Assignment on it.
Please rate all posts.

How fast can Broadcom 802.11n support for maximum?

hey everybody,i got U160 yesterday that the WLAN adapter is Broadcom 802.11n but i just got a connection speed of 65Mbps but i can get 150 Mbps with my G230 with intel 5100 bgn ,connecting to the same N-Router,so i am wondering how fast can Broadcom 802.11n support for maximum.......

if readycomm installed, remove it.
check your firewall is active and using high performance.
by the way, which model of broadcom are you using?

Can't connect to Time Capsule + no 802.11n support

I just got my new 13" MacBook (late 2008). Originally, I thought I couldn't connect to my wireless N router which happens to be Apple Time Machine. According to network utility program, my MacBook only supports a/b/g - this is not right! Now, I discover that in addition to the N problem I can't even connect to my Time Capsule wirelessly! Good thing I have 2 separate wireless routers (linksys).
My other Macs (white MacBook and 20" iMac) have no problem connecting to Time Capsule over 802.11n. Both machine indicates 802.11n support under network utility program.
Compound this problem with stuck 'a' key on my keyboard.
I really, don't get this problem. I spent an hour with Apple tech with no avail. I am thinking about returning this new MacBook.

I have the exact same problem you have described. Unable to find a solution. Odd because I have a 2007 MacBook Pro and it works fine wirelessly. Wireless-N on the MacBook works fine and it can connect to other wireless networks, just not it's home one.
If anybody is interested, here's a dump from the console log when airport attempts to connect. Our wireless station doesn't broadcast.
Macintosh-6 airportd[6001]: Could not find any preferred networks; trying broadcast requests..
Macintosh-6 airportd[6001]: Broadcast requests also failed..
Macintosh-6 airportd[6001]: Probing highest ranked networks via directed scan..
Macintosh-6 kernel[0]: AirPort: Link Up on en1
Macintosh-6 kernel[0]: AirPort: Link Down on en1
Macintosh-6 airportd[6001]: Error: Apple80211Associate() failed -25
Macintosh-6 mDNSResponder[20]: setsockopt - IPMULTICASTIF error 169.254.141.134 -1 errno 49 (Can't assign requested address)
Macintosh-6 configd[14]: rtmsg: error writing to routing socket

Extreme 802.11n support for POE 802.3af?

Can anyone confirm if the new (current) generation Airport Extreme 802.11n supports PoE installation? There was a special -- also called education -- version of the previous generation Extreme based station for POE installation.
thanks.
* Nevermind, found previous posts!

jheiliger, Welcome to the discussion area!
The new square 802.11b/g/n AirPort Extreme base station (AEBS) apparently does NOT support POE (Power over Ethernet).

802.1x support Preboot Execution Environment (PXE)

Hi,
I'd like to know if 802.1x support Preboot Execution Environment (PXE) and how its configured?
Anyone have implemented that?
Thanks
BR

Some info in an FAQ will help:
<http://www.cisco.com/application/pdf/en/us/guest/netsol/ns75/c685/ccmigration_09186a0080259020.pdf>
The Guest-VLAN is an alternative for dealing with this if your machines are not capable of supporting the new EFI from Intel (hence lack of 802.1x for PXE).

Cad ver 8 NIC test for 802.1q support

Hi Pros,
UCCX SRND ver 8 mentions that "appendix C on Cisco CAD Installation Guide" describes a way to test whether a computer NIC supports 802.1q for monitoring and recording services.
Couldnt find appendix C on the guide
Anyone knows about where I can find this info or way to test the 802.1q support?
Regards,
Pratik

Hi Pratik,
IP Communicator (in SCCP) is indeed supported as one of the monitoring devices, this is listed in the Hardware/Software compatiblity matrix for UCCX. (http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_compatibility/matrix/crscomtx.pdf)
As your CIPC will be installed on the same PC as the CAD, the RTP packets will be received on this PC and CAD will be able to access them.
Regards,
Angelique

Why doesn't the AEBS 802.11n support NTFS?

I am wondering why users need to go through hoops to make the $200 AEBS 802.11n recognize NTFS formatted disks. Is it really that complicated for Apple engineers to add this support? Is there any way to reach Apple tech and request this? Or is asking for NTFS support utterly ludicrous and fundamentally not feasible. If it is futile to hope for Apple to add support for NTFS to the AEBS 802.11n, then how does one go about returning - who to contact to return and get the money refunded.

Hello durlov. Welcome to the Apple Discussions!
... how does one go about returning - who to contact to return and get the money refunded.
Here is Apple's Return and Refund Policy.

802.1x support for windows 98

Hi,
Just want to know if there is an offical service pack from microsoft supports 802.1x for Windows 98 ? Is there other 802.1x client software that supports windows 98 client ?

I've heard of it, but AFAIK this is based on partnership level with MSFT. It effectively doesn't exist. Funk, and Meetinghouse both support 802.1x supplicants for Windows '98 though, so this is an alternative.
Hope this helps.

Wireless: 802.1X support

Hello
as a student my university supplies me with wlan via the 802.1X standard. Sadly, PRS-T2 can't connect to that (I've read that it can after being rooted, as it's already supported by the given android version, but I want to avoid that). So I'd wish the PRS-T2 user interface to allow access to 802.1X to be able to download lecture notes etc. at university.
You can find some more information about the technology on
http://www.eduroam.org/index.php?p=faq#technology
Regadrs,
Phi

Hi there
thank you for your answer.
I didn't know what exactly I was talking about. Now I have informed myself and can tell you what is actually missing: eduroam needs EAP-TTLS or PEAP/MSCHAPv2 authentification.
I've heard that android can do this but for now the PRS-T2 user interface doesn't support it (needs setting a certificate to authenticate the access point and username with password to grant access).
You can read some technical details on http://www.eduroam.org/index.php?p=faq#technology
Don't hesitate to get back to me if you have further questions.
Regards
Phi

Identify 802.1x support wireless adapter

hi guys:
IS there any good ways to detect if the client's computer support 802.1x(OS or adapter)?We would rather not check each client's computer one by one.Thaks for help.
regards

No, not really. You'll just get a string of "Cannot Associate" type messages.
The other danger there is things like .... Intel had a series of drivers for the BG2200 that would cause MIC errors .... if the AP sees two MIC errors in sixty seconds, by default, by spec, it will shut down for a while. The radio goes off-air .... everything drops.
There is a timer / setting / parameter you can tweak to keep that from happening (I don't remember which one), but thoses are the kinds of risks you run when you don't / can't control the client specification.
Good Luck
Scott

802.1x support on Aironet 340/350 for Win CE

Does the current Aironet 340/350 drivers for Win CE support 802.1x?

Read through this document about matching 802.1X protocol drafts http://www.cisco.com/univercd/cc/td/doc/product/wireless/airo_350/350cards/windows/firmrn/pcmfmwrn/fmw42523.htm#xtocid5

4006: 802.1x support?

Similar Messages

Maybe you are looking for