Protocol version of IEEE 802.1x

Hi,Sir.
I ask question of dot1x's protocol version.
I want to configure version 1 of IEEE802.1x.
But, defaut version is 2 from IOS 12.2(25)SEE.
Could you tell me, how to configure for version 1 fo IEEE 802.1x.
(I use WS-C2950G-48TC-L)
Ryusuke

Hi,
Our network is design for version 1 of IEEE 802.1X.
We have some Catalyst switch.
WS-C2970G-24TS-E
WS-C3560G-48TS-S
These are running IOS at 12.2(25)SEC.
(This protocol version of IEEE 802.1X is 1)
I can't anthenticate when WS-C2960G-48TC-L is running IOS 12.2(40)SE.
(This protocol viersion of IEEE 802.1X is 2)
I can't authenticate when WS-C3560G-48TS-S is running IOS at 12.2(40)SE.
But I can authenticate when WS-C3560G-48TS-S is running IOS at 12.2(25)SEC.
(These are same configuration)
I think this problem is version 2 of IEEE 802.1X.
(My configuration for version 1 of IEEE 802.1X)
I want to resolve this problem.
Best regards.
Ryusuke.

Similar Messages

National Instruments PXI with IEEE 802.15.4 standard (ZigBee)

Bonjour,
En fait, je travaille sur un projet qui a pour but d’implémenter un émetteur/récepteur Zigbee en bande de base reconfigurable sur la plateforme d'évaluation XUPV5-LX110T qui embarque un Virtex 5. Je suis actuellement dans la phase de test réel.
Premièrement, Je veux envoyer mes données venant d’un pc vers un FPGA et de les recevoir (pour traiter mes signaux sur Matlab). Est-ce-que cette tâche est faisable ou non ? Y a-t-il une solution pour ça en utilisant un média de communication (la liaison série par exemple)
Deuxièmement, Y a-t-il un équipement de mesure et de test de National Instruments à l’aide des PXI qui supporte le protocole sans fil Zigbee ou autrement la norme IEEE 802.15.4 (à savoir RF Vector Signal Generator et Vector Signal Analyzer) de la partie frontale analogique que ce soit en émission ou en réception?
Et merci d’avance pour tout le monde.
Hello,
In fact, I'm working on a project which aims to implement a reconfigurable Zigbee tranceiver on XUPV5-LX110T Evaluation platform which integrates a Virtex 5 FPGA. I am currently in the phase of real test.
First, I want to send my data from a PC to FPGA and receive it (to treat my signals on Matlab). Is this possible or not? If yes, Is there a solution for it using a medium of communication (e.g. serial link)
Second, is there a measuring equipment and testing National Instruments using PXI which supports the Zigbee wireless protocol or otherwise IEEE 802.15.4 standard (i.e. RF Vector Signal Generator and Vector Signal Analyzer) of the analog front-end either in transmission or reception?
And thanks a lot in advance for everyone.

Hello,
I am not sure what data you will be collecting, or how you intend on using the board. Perhaps you can explain your application a little bit more?
Is the FPGA code already developed for your application with the XUPV5-LX110T board? As long as the developed FPGA code is able to communicate with your PC via whatever protocol you choose, then you can use that as a channel to send data back and forth. Since the board is capable of many different I/O connections, you can pretty much sending/receive data over which ever connection you prefer, Ethernet, RS-232, etc.
Just to clear up any confusion, if you do not already have FPGA code for the board, this is not something you would be able to develop with LabVIEW FPGA programming. The XUPV5-LX110T board is not supported for programming its FPGA using LabVIEW FPGA. You can however, program in labVIEW to communicate data back and forth with the I/O you have chosen to connect with to your PC, such as Ethernet or RS-232, as mentioned above.
As far as measuring equipment NI offers for testing with the Zibee (IEEE 802.15.4) wireless protocol in the PXI platform, if your application requires you to both transmit to, and received from the board, and then you would need either both a Vector Signal Generator and Vector Signal Analyzer, or a Vector Signal Transceiver. See the list below for some examples of what we have to offer.
VSAs: NI PXI-5661, NI PXIe-5663E
VSGs: NI PXI-5671, NI PXIe-5672/5673E
VSTs: NI PXIe-5644R/5645R/5646R
From my knowledge of ZigBee, you would be capable of communicating with the board using any of these devices.
Matthew R.
Applications Engineer
National Instruments

PPPoE Over IEEE 802.1Q VLANs in 12.4T

I am trying to configure PPPoE Over IEEE 802.1Q VLan on a 2811 router with (C2800NM-SPSERVICESK9-M), Version 12.4(24)T8
PPPoE client on FastEthernet0/0 works fine.
interface FastEthernet0/0
no ip address
duplex auto
speed auto
pppoe enable group global
pppoe-client dial-pool-number 1
But PPPoE session is not established on a subinterface with encapsulation dot1Q. It is not even trying to connect to the PPPoE server.
Cisco Feature Navigator says that this feature was added in 12.4T.
Can anybody confirm that 'PPPoE over IEEE 802.1Q VLANs' feature works fine on this IOS?
Thank you in advance!

Below works fine.
vpdn enable
vpdn-group 1
request-dialin
protocol pppoe
bba-group pppoe global
interface FastEthernet0/0
no ip address
duplex auto
speed auto
pppoe enable group global
pppoe-client dial-pool-number 1
But the same doesn't work over the subinterface:
interface FastEthernet0/0.2
encapsulation dot1Q 2
pppoe enable group global
pppoe-client dial-pool-number 1

IEEE 802.1x port-based authetication

I want to configure IEEE 802.1x port-based authentication on cisco switches, preferable 2960 series. Which models support this feature?. I have try with some older switches but it doesn't works properly on everyone.
I have upgraded them whitout better results, there is namely an issue with TLS handshaking on some switches which produces authentication to fail.

Hi Claudia,
do you mean that the EAP-TLS authentication fails only on some 2960 switches and it works on other 2960s?
What is the IOS version you're using there?
What is the RADIUS server in use?
What is the exact error message you see on the RADIUS side?
Usually, the reason for the EAP-TLS handshake failure is to be troubleshoot on the supplicant and AAA server, however, there may be something on the switch depending on the certificate size and MTU settings on the switch(es).
What is the server cert size and the MTU configured on the switches?
With the info you provided it's difficult to say what's the reason of this failure.
I would suggest to start looking into the above mentioned topics, else you would need to proceed with deeper debugging and sniffer traces, which may be better/easier to handle through a TAC case.
I hope this helps.
Regards,
Federico
If this answers your question please mark the question as "answered" and rate it, so other users can easily find it.

NAC - L2 IEEE 802.1x and NAC - L2 IP differences.

Hi,
My customer is having Cisco 4507R switch with IOS version 122.31-SG1 which deosnt supports NAC - L2 IEEE 802.1x but supports NAC - L2 IP.
What is the difference between these features and which features is required for proper authentication and posture assesment.
Thanks and regards,
Pulkit Sharma

Hello,sharma
can u be more clear abt ur question.What r u trying to achieve.

IEEE 802.1ad / 0x88a8

I have moved to another vendor at my edge, and I have continued to use 0x8100 as my ethertype which seems to play nice except for when a customer has a native vlan1 setup.
Vlan1 will get tagged into my SVLAN 301, but Cisco sees it as an incorrect BPDU, and shuts down the port. I also see customer CDP neighbor information, and other stuff when the customer doesnt prune his network down, or uses vlan1 on transparent lan services.
My new vendor told me to use the IEEE 802.1ad standard for the outter tag, (ethertype 0x88a8), but Cisco doesnt support it. Does anyone know why Cisco is not following the IEEE 802.1ad standard for provider bridges (Q-Q) tagging on the ME3400 series? I know they developed their own proprietary GBPT protocol for handling of L2 protocols but that doesnt help me now.
Just some quick searching, shows that the 7600 is supported with 12.2SR. ME3400's are not, its a 'future' release, but I dont know how long ago that document was written.
*May 10 18:30:30 MST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to up
*May 10 18:30:31 MST: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 1 on GigabitEthernet1/0/1 VLAN301.
*May 10 18:30:31 MST: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking GigabitEthernet1/0/1 on VLAN0301. Inconsistent local vlan.
show spanning-tree vlan 301
VLAN0301
Spanning tree enabled protocol rstp
Root ID Priority 4397
Address 0017.5aaf.f200
This bridge is the root
Hello Time 2 sec Max Age 10 sec Forward Delay 7 sec
Bridge ID Priority 4397 (priority 4096 sys-id-ext 301)
Address 0017.5aaf.f200
Hello Time 2 sec Max Age 10 sec Forward Delay 7 sec
Aging Time 300
Interface Role Sts Cost Prio.Nbr Type
Gi1/0/1 Desg BKN*4 128.1 P2p *PVID_Inc
Gi1/0/2 Desg BKN*4 128.2 P2p *PVID_Inc

Currently, the default ether type is 0x8100 on a Cisco 7600 for the Q-in-Q outer tag. However, a few non-Cisco vendors use 0x9100 or 0x9200 ether type for the Q-in-Q outer tag. For Cisco 7600 router to operate seamlessly with other vendors it is required to provide a mechanism to change the default ethertype.
Moreover, there is a need to support ethertype 0x88A8 to support provider bridge defined by IEEE 802.1ad. Custom ethertype feature is proposed as a solution for this problem that enable change of ethertype as per requirements. Under the custom ethertype model, ethertype 0x9100, 0x9200 and 0x88A8 can be configured using "dot1q tunneling" CLI under a physical port.
Benefits
The explanation for the error message:
%SPANTREE-2-RECV_BAD_TLV: Received SSTP BPDU with bad TLV on [chars]
[chars].
Explanation The specified interface has received a Shared Spanning-Tree Protocol (SSTP) bridge protocol data unit (BPDU) that was missing the VLAN ID tag. The BPDU has been discarded.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Catalyst 2960 XR support standar IEEE 802.3i

Hi
The Catalyst 2960 XR support standar IEEE 802.3i?.
becouse the datasheet not is present.
Best regards.

Data Sheet doesnt cover this standard:
tandards
● IEEE 802.1D Spanning Tree Protocol
● IEEE 802.1p CoS Prioritization
● IEEE 802.1Q VLAN
● IEEE 802.1s
● IEEE 802.1w
● IEEE 802.1X
● IEEE 802.1ab (LLDP)
● IEEE 802.3ad
● IEEE 802.3af
● IEEE 802.3ah (100BASE-X single/multimode fiber only)
● IEEE 802.3x full duplex on 10BASE-T, 100BASE-TX, and 1000BASE-T ports
● IEEE 802.3 10BASE-T specification
● IEEE 802.3u 100BASE-TX specification
● IEEE 802.3ab 1000BASE-T specification
● IEEE 802.3z 1000BASE-X specification
Could you please open a TAC case so that we check with BU on the same?

National Instruments PXI avec IEEE 802.15.4 standard

Bonjour,
En fait, je travaille sur un projet qui a pour but d’implémenter un émetteur/récepteur Zigbee en bande de base reconfigurable sur la plateforme d'évaluation XUPV5-LX110T qui embarque un Virtex 5. Je suis actuellement dans la phase de test réel.
Premièrement, Je veux envoyer mes données venant d’un pc vers un FPGA et de les recevoir (pour traiter mes signaux sur Matlab). Est-ce-que cette tâche est faisable ou non ? Y a-t-il une solution pour ça en utilisant un média de communication (la liaison série par exemple)
Deuxièmement, Y a-t-il un équipement de mesure et de test de National Instruments à l’aide des PXI qui supporte le protocole sans fil Zigbee ou autrement la norme IEEE 802.15.4 (à savoir RF Vector Signal Generator et Vector Signal Analyzer) de la partie frontale analogique que ce soit en émission ou en réception?
Et merci d’avance pour tout le monde.

Bonjour,
Si vous utilisez LabVIEW ou Lab/WindowsCVI ou n'importe quel logiciel National Instruments et nos cartes FPGA c'est tout à fait possible de le faire.
En ce qui concerne la norme IEEE 802-15.4 vous pouvez communiquer avec un PXI 5660 par exemple.
Accelerating ZigBee and 802.15.4 Module Testing with LabVIEW and an NI RF Vector Signal Analyzer /
http://sine.ni.com/cs/app/doc/p/id/cs-744
Brice S.
National Instruments France

Transport protocol version error in Integration Directory API

Hi All,
I am trying to create SOAP receiver communication channel using Java-only PI 7.31 directory APIs. I have passed all the required parameters to the CommunicationChannelIn service, but it's throwing error - "Enter at least one object key for operation 'create'".
When I tried to test the service through WS Navigator, it's giving exception - "Enter a value for attribute 'Transport Protocol Version'" which doesn't exists in case of SOAP adapter creation.
Has anybody come across this issue? If the adapter metadata does not specify any transport protocol version, then shouldn’t the validation checks in CommunicationChannelIn service provider proceed without errors on a blank value for this attribute?
Note: I have gone through all the SCN blogs, discussion threads we have on topics related to Integration Directory API.
Thanks in advance for all the help and suggestions.
Regards,
Yashu Vyas

Hi All,
I am trying to create SOAP receiver communication channel using Java-only PI 7.31 directory APIs. I have passed all the required parameters to the CommunicationChannelIn service, but it's throwing error - "Enter at least one object key for operation 'create'".
When I tried to test the service through WS Navigator, it's giving exception - "Enter a value for attribute 'Transport Protocol Version'" which doesn't exists in case of SOAP adapter creation.
Has anybody come across this issue? If the adapter metadata does not specify any transport protocol version, then shouldn’t the validation checks in CommunicationChannelIn service provider proceed without errors on a blank value for this attribute?
Note: I have gone through all the SCN blogs, discussion threads we have on topics related to Integration Directory API.
Thanks in advance for all the help and suggestions.
Regards,
Yashu Vyas

Question about ssh login warning: Bad protocol version identification

I set up ssh on my computer according to Tim Haigh's suggestions given here:
http://discussions.apple.com/thread.jspa?threadID=1674968&tstart=0
But when I log in from my iPhone, secure.log shows this:
sshd[534]: Bad protocol version identification 'GET / HTTP/1.1' from 208.54.83.51
Although I do log in successfully, how can I resolve this error?

GET / HTTP/1.1
Looks more like a Web browser handshake, than ssh.

IEEE 802.1x Authentication with RADIUS failed

Hello guys,
I've a little strange Situation.
If user start his Computer (Windows 7 enterprise) and computer is connected via LAN it works fine.
If user start his Computer (Windows 7 enterprise) and computer is connected via WLAN it works also fine.
But if user start his Computer (Windows 7 enterprise) that is connected via LAN it is not more possible to connect to WLAN (parallel). I've implemented an IEEE 802.1 RADIUS authenticiation.
It does not work with this special user account. I've tested it already successful with couple other accounts.
Does someone has experience with such Situation?
Regards
Rodik

It does not work with this special user account. I've tested it already successful with couple other accounts.
Hi,
Did you mean that this problem just occures to the single User Account but others works fine at same computer, isn't it?
When it connect Wlan failed, is there any error message? Have you tried to reinstall the WLan device driver for test?
it would be better to provide more details about the Wlan connect failed.
Roger Lu
TechNet Community Support

Incompatible protocol versions

I am attempting to run an iphone application on an iphone 4.3 simulator. I have confirmed that I can talk to the Unwired Server by seeing that my client is contacting the server in the logs. However, I am getting the following message in the xcode console:
[INFO] [CallbackHandler.m:46] =============================
[ERROR] [CallbackHandler.m:47] Message Exception
[ERROR] [CallbackHandler.m:48] SUPPersistenceException: Device and server are not using compatible protocol versions: client protocol version = 1, server protocol version = -1.
[INFO] [CallbackHandler.m:49] =============================
I saw a similar question regarding this in the context of a blackberry app in the forums, but the error was a bit different and the solution (simply resetting the simulator) did not work for me. Has anyone encountered this issue before? If so can you explain what is going on here and how you got past it?
Thanks!
Jesse

Please check the MBO deployed in the server is same as what you were using in the client side development.
Regards,
Ram

The vm and host networking components failed to negotiate protocol version '4.0'

Hi,
I have the problem that when I start a VM with windows server 2012 on a hyper-v v2 host, it takes very long till the VM get bind the static or dynamic ip adress. I tried both, static and dynamic. In every case I see at the event viewer the following error:
the vm and host networking components failed to negotiate protocol version '4.0'
After a few minutes the VM gets bind the IP an everything works fine. But at the next time I reboot the machine the same failure appear.
Trying to use legacy network adapter results in the same problem. After this I tried to export the vm to a hyper-v v3 host. At first boot time
the problem didn't appear and the vm get's bind the ip adress without problems. Then after upgrading the integration services to hyper-v v3
version the same problem appears but without register it in the event viewer.
Does anybody know how I can fix this problem?
Kind Regards,
Marcus

Hi,
A MS KB records an issue when you run Windows 8 or Windows Server 2012 based Virtual machine in Windows Server 2008 or in Windows Server 2008R2:
http://support.microsoft.com/kb/2744129
There is a Microsoft update in this KB, you may install this KB in your Windows Server 2008 R2 and check the result.
While about this issue after you migrate the guest VM to Windows Server 2012 host, will it still has such error message after you remove all network adapters of the guest VM?
Install Windows update for the Hyper-V host, after that upgrade Integration service for the guest VM again to check the result.
For more information please refer to following MS articles:
"Unsupported configuration" warning when you run a Windows 8-based or Windows Server 2012-based virtual machine in Windows Server 2008 R2
http://support.microsoft.com/kb/2737297
Hyper-V Overview
http://technet.microsoft.com/en-us/library/hh831531.aspx
Lawrence
TechNet Community Support

Which protocol version is really used?

In the JSSE reference guide, Appendix A: Standard Names, is said, that the protocol name passed to the getInstance method of the SSLContext class maybe one of the following: SSL, SSLv2, SSLv3, TLS, TLSv1. But it does not specify which protocol version will actually be used, it is always said that it supports one or some specific protocols, but it may support other protocol versions as well.
And what does the setEnabledProtocols method of the SSLSocket class do? May an application specify here exactly, which protocols should be used?

JSSE currently supports SSL v3.0 and TLS v1.0 (SSL v3.1).
The protocol agreeded with the server depends on your client/server configuration, and always is the lower protocol supported by both of them.
For example:
Server -> TLS v1.0
Client -> SSL v3.0
The shared protocol will be SSL v3.0.
About the getEnabledProtocols() method, give a look here:
http://java.sun.com/j2se/1.4/docs/guide/security/jsse/JSSERefGuide.html#NewMethods
Hope this helps.

The VM and host networking components failed to negotiate protocol version '5.0'

I have been searching for a fix for this issue for sometime.
The VM and host networking components failed to negotiate protocol version '5.0'
and
The VM and host networking components failed to negotiate protocol version '4.0'
this error have been posting on the host server 2008 R2, with a hyper-V running server 2012 R2, which is the eval version vhd from Microsoft.
I have tried the patch on the server 2008 R2 host and the nic delete and rescan option with varied reboots and such between each step of the process just to try every possible combination.
The error persists. Are there any other suggested solutions for fixing this problem. Also the drivers have all been updated along with the system firmware.
thanks,

The hotfix states Server 2012 in the VM. You stated Server 2012 R2 in the VM. MSFT is very precise in this language - Server 2012 != Server 2012 R2.
Two distinctly different releases of Windows Server.
In this case the N = the running release of Hyper-V. In this case your Hyper-V Server at release version 2008 R2.
The +2 = the current version of Windows. In this case that is 2012 R2. Two releases ahead of the version of the hypervisor you are running.
I tossed in the link to Ben Armstrong's blog article as that is the ONLY (and still definitive statement) support statement regarding this configuration. He posted that article at my request after many folks posting in this forum with strange behavior
in this configuration.
"supported" in this context means that if you call CSS, you will be told the following: 'yes, you have errors in the event log. We will not fix that. This is an unsupported configuration. But that does not block the OS in the
VM running. If you want the errors to go away, we suggest you upgrade your Hyper-V Server to 2012 R2. That configuration is supported.'
That said, it can impact other functionality of the VM that rely on Integration Components in the VM and the Services of the hypervisor. There is most likely small things that will not work.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

Protocol version of IEEE 802.1x

Similar Messages

Maybe you are looking for