Link Local Unicast Addresses and Link Local Multicast Addresses

I am trying to get a hold on Link Local Multicast addressing. I know that Link Local Unicast Addressing is the equivalent of an APIPA address but can anyone tell me what Local Link Multicast addressing is used for and hopefully provide an example of
it's use? Beg your pardon if this is a stupid question. Thanks.
Michael T. Glenn

Hi Michael,
Obviously, this is not a stupid question.
The link local multicast addresses are the equivalent of 224.0.0.0/24, which are reserved for the local subnet and are not forwarded by IP routers regardless of the Time to Live (TTL) in the IP header.
They are used for routing protocol or other well-known multicast based communication.
For detailed information, please refer to the link below,
IPv6 Multicast Address Assignments
http://tools.ietf.org/html/rfc2375
Best Regards.
Steven Lee
TechNet Community Support

Similar Messages

Ask the Expert: Enterprise Design and Deployment of Multicast

Welcome to this Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about Cisco enterprise design and deployment of multicast solutions.
The enterprise world is evolving to be overcome with large throughput capacity and record numbers of users connecting to the network. Mechanisms such as multicast, which allows for a minimization of throughput for multiple users subscribing to the same stream, are a welcome addition. Applications such as enterprise all-hands video streaming, trading applications, mass operating system deployment, and custom implementations can put a strain on the network if done via unicast. Multicast can minimize this strain by replicating a single stream for subscription by multiple parties who would like to receive the same information. For this Ask the Expert event, Patrick Lloyd, CCIE R&S no. 39750 and a network consulting engineer with Cisco’s Enterprise Advanced Services Delivery Team, will answer questions about multicast design and implementation based on best practices and prior experience with large enterprise deployments.
Patrick Lloyd is a network consulting engineer for Cisco’s Enterprise East Advanced Services team, working to support and lend his expertise to a number of financial, insurance, healthcare, and consulting customers. In his four years of experience, he has lent design expertise to multicast networks ranging from 500 Cisco devices and 20K users to upward of 4500 Cisco devices and 50K users. Patrick is certified with his Cisco Certified Internetworking Expert no. 39750 in the Routing and Switching track and also has achieved certification in CCNA Security and Securing Cisco Routers and Switches as part of the CCNP Security track. Patrick received his MS degree in networking and systems administration from Rochester Institute of Technology in Rochester, NY, and his BS degree in computer science from Eastern Connecticut State University. He frequently gives customer-based knowledge transfers.
Remember to use the rating system to let Patrick know if you have received an adequate response.
Because of the volume expected during this event, Patrick might not be able to answer every question. Remember that you can continue the conversation in Network Infrastructure under the subcommunity WAN, Routing & Switching shortly after the event. This event lasts through September 12, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Thanks for the question! This is actually a good one that I've encountered with a couple customers in the past, the tradeoff between a flood and prune type design, as opposed to the shared tree -> shortest path tree sequence. As per Cisco best practice, we are actively trying to get customers to implement sparse mode, going so far as to not support PIM dense mode in our data center products. And for good reason! The last thing you want is a chatty protocol within the data center which is flooding traffic out to receivers who may or may not be interested in it every 3 minutes. Instead, you're much better off having interested receivers join a stream, have your RP connect the interested senders and receivers, and then transition to the shortest path between source and destination.
That being said, if you're studying for CCIE or looking to get experience in how multicast works, dense mode should at least be a lab exercise!
Links for reference as to the difference in PIM modes:
Dense Mode Operation:
http://www.cisco.com/en/US/docs/ios/ipmulti/configuration/guide/imc_pim_dense_rfrsh.pdf
Pim Modes and explanation of each:
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3750x_3560x/software/release/12-2_53_se/configuration/guide/3750xscg/swmcast.html#wp1077051
A great slide deck to learn the operation of multicast:
https://www.ciscolive.com/online/connect/sessionDetail.ww?SESSION_ID=6633&backBtn=true
Troubleshooting Multicast:
https://www.ciscolive.com/online/connect/sessionDetail.ww?SESSION_ID=78578&backBtn=true
Let me know if this is the answer you're looking for!

Pulling a stream from external FMS and publishing in Multicast

Hi. I'm developping a FMS 4 application that read an external stream, and then, republish it in multicast:
1.- So, first of all I open a NetConnection to the remote application. And I associate it to a new Stream created in the application. Then I have the stream available in my application.
nc = new NetConnection();
nc.connect(REMOTE_APPLICATION);
nc.onStatus = function(info)
trace("REMOTE_APPLICATION->NetConnection> code: " + info.code);
if (info.code == "NetConnection.Connect.Success")
rebroadcast_s = new Stream.get("tempStream");
rebroadcast_s.onStatus = function(info)
   trace("Stream> code: " + info.code);
   trace("Stream> details: " + info.details);
   if (info.code == "NetStream.Publish.Start")
          trace("REMOTE_STREAM->The stream is now publishing");
rebroadcast_s.play(REMOTE_STREAM, -1, -1, true, nc);
2.- I would like to use the same methods of native multicast.as application, for managing the multicast publishing: registerStream, openMulticastConnection, ...
var MULTICAST_PARAMETERS = "fms.multicast.type=2&fms.multicast.groupspec=G%3A0101210558cc3408e77326e2fa1c53c52697d73 e1b02182c358c57075cd9a58ed1a25241010d160e666d732e6d756c7469636173742e6578616d706c65210e855 5a813f0c73cd8f5384e0fba657163ab87e76c25b6f82be9b94777b2d52cfe00070aefff00fe7530051576706f6 4&fms.multicast.address=239.255.0.254%3A30000";
var params = parseQueryString(MULTICAST_PARAMETERS);
var streamContext = registerStream(CLIENT??????, MULTICAST_STREAM_NAME, params);
openMulticastConnection(streamContext);
But, I don't know who would be the client in the registerStream method. Which reference should I add there? Is it possible in this way?
I made another different script that republish that stream in localhost using NetConnection.publish(localhost/sameapplication). It works properly. But I would like to be able of managing it in the other way.
Thank you,
Iván

1.- Tried adding NULL, and there's an error trying to access to the properties of the parameter, and finally the multicast publication is not done:
Registered multicast context for source stream: livestream
Sending error message: /opt/adobe/fms/applications/vpodmulticast2/main.asc: line 308: TypeError: streamContext.client has no properties
2.- Tried adding the nc reference, and there's no error in the logs, but the multicast publication is not done neither.
3.- Going deeply in the code, I discovered that client object is only used for getting the client.uri (the uri where the client is publishing the stream) and the client.ip (for internal connection managing). So I created a client object with these two attributes, and It's working properly:
var params = parseQueryString(MULTICAST_PARAMETERS);
var client = new Object();
client.uri = "rtmp://localhost/"+application.name;
client.ip = "localhost";
var streamContext = registerStream(client, MULTICAST_STREAM_NAME, params);
openMulticastConnection(streamContext);
Thank you,
Iván

Link-local multicasting

I'm trying to do multicast imaging in an environment without practical access to a DHCP server.
I have a 48-port switch which I'm assured is configured as a "flat" switch.
If I connect two or more computers to this switch (without connecting the switch to an uplink), boot them to the ZENworks Imaging Preboot Environment, and run 'dhcpcd -d -t 1 eth0' to get them link-local IP addresses, they can ping one another without issues.
After having confirmed that the pings succeed, if I attempt to initiate a multicast via 'img s flat m' on one computer and 'img s flat cl' on the others, img exits almost instantly with a "network is unreachable" / "could not contact the server" message and an elapsed-time report of 00:00. This happens as soon as the command is issued, not when the clients connect or when the "start multicast" button is pressed.
If I instead attempt to initiate the multicast via the menus of the curses interface to the 'img' program, as soon as I hit Next after selecting the "master" role, img segfaults. (I haven't yet tested selecting the 'client' role, but I expect it would be much the same.) I got a similar segfault on master machine for the first try with the command-line variant, but haven't been able to reproduce it since.
This is with ZENworks 11.2.2, and a preboot environment manually updated to use a more recent version of the Linux kernel (3.8 or later, I think - I haven't checked lately), which is needed for driver support.
Is multicast imaging across a "flat" switch using link-local IP addresses expected to work?
If it is, any idea what may be going wrong (or how to figure out the same), and/or how to get this working?
If it is not, is there any means of multicast imaging without an available DHCP server which *is* expected to work?

This turns out to be another manifestation of the problem described in TID 7011873.
The workaround described in that TID appears to assume that there is an available DHCP server, and that it just isn't handing out a default-gateway address when it hands out IP addresses to its clients.
In our scenario, there is no DHCP server at all, and no gateway as far as I'm aware; this is an entirely isolated network. It might be possible to get things working by specifying a default-gateway address anyway, but I have no idea what address to specify, since in that situation there is no machine with any special role (except for the multicast master itself, which is special for a different reason); I tried specifying 0.0.0.0, as a known-unused address, and the route command quite reasonably rejected it. There might be an IP address for the "flat" switch itself, but if so I don't know what it is and don't have any apparent way of finding out.
I managed to get this working anyway, at least to the point of the clients getting multicast-session numbers. To do that, I booted the SLAMPP live-CD server environment on a spare machine connected to the "flat" switch (from a USB drive), brought up the installed DHCP server in that live-CD environment, and specified the IP address of the live-CD machine (192.168.0.1) as the default gateway on the clients using the command described in that TID.
(The SLAMPP DHCP server does not appear to have any option to specify a default gateway address, so it still has to be specified manually as far as I've been able to tell.)
This approach means we have to have two machines connected to the switch in addition to the ones actually being imaged (the DHCP-server machine and the multicast master), but at least it should mean we can get imaging done outside of the realm of our normal network.
That TID is a year and a half old, and is still listed as "Reported to Engineering". Is there any indication of possible progress towards a fix?
At the least, I'd like to see some acknowledgement of the fact that this also applies to environments with no DHCP server, rather than just to ones where the DHCP server doesn't behave as the imaging client expects.

Link-local multicast on autonomous APs

Hi,
I have a 877 which I am troubleshooting some mDNS (224.0.0.251:5353) issues.
One client sends a mDNS request, the router sees it (packet debug) but the packet is not received by any other client on the wireless LAN.
Given it is link local I don't believe that enabling PIM (which I have done anyway).
I have investigated if there is anything that I would have to do to enable multicast for my wireless clients, on WLCs there is a multicast and broadcast config command which explicitly enables it.
Any directions would be appreciated.
Regards
Adam

Make sure that do not use the 239.0.0.X address range or the 239.128.0.X address range. Addresses in these ranges overlap with the link local MAC addresses and will flood out all switch ports even with IGMP snooping turned on.
Use the show network command to verify the multicast mode on the controller and show lwapp mcast to verify the group on the AP. I hope it may help you

Deploymentshare : local or DFS? What is best for performance and failures? And what about multicast in relation to DFS?

Hi,
we use MDT 2013 on MS Server 2012 Standard. We deploy LTI's. We have only one (virtual) MDT-server and that has only one deploymentshare. I'm having now a discussion with my colleague about where to put the deploymentshare. He says that we should put it
on our fileservers (which use DFS) because it's more safe and more dynamic (no idea what he means with that). But to me it appears quite strange to separate an application and its main folder structure. I have this idea that those two need to be as close
as possible, like to avoid network problems for instance. It's also a fact that our MDT-server is backed up every night, so if something bad happens we just ask our colleagues to restore the latest snapshot. Can someone explain which option is the better and
why : local or DFS?
Second thing which is related to my first question: I've read on this forum about multicast not being possible when the deploymentshare is not local on the server? Am I correct? Anymore info about this issue would be nice too. Awaiting your answers I'll
keep looking for more clues everywhere.
thanks,
Paul

IN addition to what is mentioned here.
MDT works great with DFS. However note that MDT is *NOT* supported with Domain DFS, only stand-alone DFS, because Domain DFS implies that the client is joined to a domain when you make the call, and MDT needs to run within WinPE, where there is no domain
infrastructure.
Multicast should be on the same machine as your DeploymentShare, wherever that may be. If you have DFS, your deployment share would be the root.
Another idea is to use DFS to replicate out to your DFS leaf nodes, and each Leaf node would be it's own WDS Server with Multicasting being done from there.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

70-410 Lab 10 Unique local unicast address

how do i find the IPv6 address for 12-AA-BC-32-23-12, 12-AA-BC-32-23-11, AND 00-15-5D-01-01-C1.
Im having a problem understanding on how convert the interface ID. Am i always switching my seventh by either from 0 to 1 or 1 to 0, or is it specifically the seventh bit is supposed to change from 0 to 1 and if it is already 1 it stays 1?

how do i find the IPv6 address for 12-AA-BC-32-23-12, 12-AA-BC-32-23-11, AND 00-15-5D-01-01-C1.
Im having a problem understanding on how convert the interface ID. Am i always switching my seventh by either from 0 to 1 or 1 to 0, or is it specifically the seventh bit is supposed to change from 0 to 1 and if it is already 1 it stays 1?

Ipv6 HSRP gloabl unicast address on cisco 3560 switch

Dear Team,
We are using cisco 3560 switch. Now we are going to implement ipv6 in our network. But we are not disturbing to existing ipv4. my question is 1) Can we confiure the global unicast ipv6 address in ipv6 HSRP and 2) can cisco 3560 switch will support ipv4 and ipv6 standby group on same SVI ?

YES

Configuring SG500 to work with UCAC-CE and BE3K for multicast paging

I need help configuring multicast on my SG500 swtiches. One is L3 no router involved. The Attendant works fine paging in Unicast. but I need to set it up for Multicast. I have no experience working with Multicast and I'm not sure what to do.. I dont even know if I need a router.. since the Switch is acting as a L3.

Hello,
While I've not personally set this up, I did run across Smart Tip that may aid in your quest.
https://supportforums.cisco.com/docs/DOC-13461
Good luck,
Albert

What is Best Practice for Publishing and Subscribing to Multicast Video P2P

Please, could someone help with an issue I am having in developing a peer to peer video chatting application? My application uses multicast to publish and subscribe to video streams of NetGroup members. I'm listening for the NetGroup.Neighbor.Connect event, and I'm calling the following function:
protected function onPeerConnect(event:NetStatusEvent):void{
                var peerID:String = event.info.peerID;
                // create user vo here
                // user Value Object for incoming stream
                userVO = new User();
                userVO.peerID = peerID;
                netGroup.addNeighbor(peerID);
                receiveStream(userVO);
protected function receiveStream(userVO:User):void{
                // init netstream
                var stream:NetStream = new NetStream(nc,groupspec.groupspecWithAuthorizations());
                stream.receiveVideo(true);
                stream.addEventListener(NetStatusEvent.NET_STATUS,netStatus);
                // init panel
                // alter to use custom component instead
                var panel:Panel = new Panel();
                panel.id = "panel" + panel_seq;
                panel.title = "Panel" + panel_seq;
                panel.width=322;
                panel.height=281;
                panel.x = 50 * panel_seq + 200;
                panel.y = 25 * panel_seq + 200;
                var cpanelContent:Array = new Array();
                panel.controlBarContent=cpanelContent;
                panel.controlBarVisible=true;
                // init video
                var video:Video = new Video();
                video.width=320;
                video.height=240;
                video.attachNetStream(stream);
                stream.play("media");
                // init videoWrapper
                var videoWrapper:UIComponent = new UIComponent();
                videoWrapper.id = "wrapper" + panel_seq;
                videoWrapper.addChild(video);
                // add to display list
                addElement(panel);
                panel.addElement(videoWrapper);
                // drag and drop panel
                panel.addEventListener(MouseEvent.MOUSE_DOWN,function(event:MouseEvent):void{
                    panel.startDrag();
                    addElement(panel);
                panel.addEventListener(MouseEvent.MOUSE_UP,function(event:MouseEvent):void{
                    panel.stopDrag();
                panel_seq++;// used for unique panel id
                userVO.panel = panel;// reference to the panel
                userVO.stream = stream;
                userVO.video = video;
                peers.addItem(userVO);
I am confused on this:
var stream:NetStream = new NetStream(nc,groupspec.groupspecWithAuthorizations());
What should I pass as the second parameter to establish an incoming NetStream with the publishing peer? I've seen people put in the farID but I haven't figured out how to access it. What is the difference between event.info.peerID and event.info.neighbor? And since I'm multicasting to the group do I need to pass in the groupspec or the farID? I would love some clarification on this.
What is happening is this:
When I join the group, and there are two members in the group already, I'll get three panels with videos. However, duplicate video streams are being attached. When I inspect the peerStreams array I'm seeing a length of 0, so does that mean that no one is subscribing to my published netstream? If so, how do I specifically subscribe to each published stream in the group? Sometimes if I step through in debug mode, I get three separate camera feeds in their prospective panels, but if I run it will have duplicates. I thought at first that this was a referencing error because all of the NetGroup.Neighbor.Connect events where happening all at the same time and perhaps that is the reason for the duplicates?
My only other thought is that maybe I'm multicasting one guys stream to the whole group, but I'm getting varying results so I want to know what is the correct way to grab, in sequence, a NetGroup members' published netstream and be sure that all other members are subscribing to my NetStream as well?
Also, I am using Value Objects to keep track of who my group members are, is that data shared with the group or is it not accessible to all members?   or should I use another method of keeping track of my group members?
Please help! Thank you in advance!

it appears you posted an identical message in two threads. i've responded in the other thread:
http://forums.adobe.com/message/3701380#3701380

ARD and Cisco switches (multicast storm issue)?

We had Cisco bring in an engineer to look into our problem where ARD stalls/fails to push packages or pull reports (etc.). We never have a problem remotely controlling computers.
They told us "Multicast" needs to be on at every switch that has Macs connected. In one environment all Macs are on the 10.100.9.xx subnet, and Macs are at different locations. All the switches these dot-9 subnet Macs are connected to need "Multicast" turned on.
I've read numerous threads regarding how Macs drift in and out and ARD is not able to do what it's advertised to do. Has anyone run into this issue where Cisco switch configuration caused ARD to not perform properly?
I will summarize once Cisco resolves the issue. They're due in for another test or two before we can make the necessary switch adjustments.
Thanks,
Don

I have 3COM switches and they appear to be performing as your CISCOs are. I have computers drift in and out all day as well as my task server not responding to input at all. When trying to browse the LAN for computers, I don't receive any information regarding my computers, or I only get 5 out of 2100. I will talk with my Network Administrator and find out if Multicast is turned on. I have sent Apple 300 crash reports over the past 3 months, but have not received any word on a fix for ARD issues.

Issues with Multicast MOH with CUCM SRST Sites

Hi there,
I am having an issue streaming multicast music on hold at remote sites by sourcing the music on hold from the local flash of the Cisco 2951.
I am running CUCM 9.1(2) SU1, I have 1 x PUB and 1 x SUB. I have enabled the PUB to stream unicast MOH and have enabled multicast MOH on the SUB. Base IP: 239.1.1.1 and Port 16384.
I have set the MOH Region to all remote sites regions to G.711 and have put the SUB into an MRG and have enabled MOH at the MRG and Audio Source Level as per documentation. The MRGL for remote sites contain the local sites hardware resources such as MTP, CFB and XCODE. Second to that MRG, I have set the MOH_MRG containing the SUB enabled for multicast.
When a remote site user put the PTSN caller on hold, I can see an active multicast music on hold session active on the local router but the PSTN caller hears silence !!! The number of In/Out packet on the multicast session does not increase at all.
Could you please help me guys? I have tried all options and still I am getting silence all the times.
Below is the configuration on the local gateway at remote sites:
XX-XXX-VG01#sh run | s call-m
call-manager-fallback
max-conferences 4 gain -6
transfer-system full-consult
ip source-address 10.114.80.1 port 2000
max-ephones 58
max-dn 120
transfer-pattern 031580....
keepalive 10
call-forward pattern 031580....
moh "music-on-hold.au"
multicast moh 239.1.1.1 port 16384 route 10.114.80.1 1.1.1.1
time-zone 29
time-format 24
date-format dd-mm-yy
Please note that when the PSTN caller is on hold, when I issue the # show ccm-manager music-on-hold, I get the following output all the times:
XX-XXX-VG01#sh voice call status
CallID     CID ccVdb      Port        Slot/DSP:Ch Called #   Codec    MLPP Dial-peers
0x17740    22AA 0x3D1D09A4 0/0/0:15.4       0/1:2   4312      g711ulaw 200/202
1 active calls found
XX-XX-VG01#sh ccm-manager music-on-hold
Current active multicast sessions : 1
Multicast       RTP port   Packets       Call   Codec    Incoming
Address         number     in/out        id              Interface
===================================================================
239.1.1.1         16384   0/0              96064 g711ulaw
XX-XXX-VG01#sh ephone summary
hairpin_block:
Max 58, Registered 0, Unregistered 0, Deceased 0 High Water Mark 59, Sockets 0
ephone_send_packet process switched 0
Max Conferences 32 with 0 active (4 allowed)
Skinny Music On Hold Status - group 0
Active MOH clients 0 (max 210), Media Clients 0, B-ACD Clients 0
File music-on-hold.au (not cached) type AU Media_Payload_G711Ulaw64k 160 bytes
Moh multicast 239.1.1.1 port 16384 route 10.114.80.1 1.1.1.1
I can confirm that the flash of the local router has indeed the music-on-hold.au file
XX-XXX-VG01#dir flash:
Directory of flash0:/
247 -rw-      496521 Sep 20 2014 10:30:06 +02:00 music-on-hold.au
263 -rw-    90063932 Sep 22 2014 11:24:06 +02:00 c2951-universalk9-mz.SPA.152-4.M6a.bin
256503808 bytes total (141819904 bytes free)

Hi Rachel,
The IP address CUCM selects is based on the codec and the audio stream.
See the following URL. http://voiceonbits.com/2010/06/29/moh-issues-and-resolution/
I borrowed this table from that URL and cleaned up the port numbers. Hopefully this helps.
Inc. Multicast on IP Address
Inc. Multicast on Port Number
Audio Stream
Codec
Dst. IP Address
Dst. Port
Dst. IP Address
Dst. Port
1
G.711 ulaw
239.1.1.1
16384
239.1.1.1
16384
1
G.711 Alaw
239.1.1.2
16384
239.1.1.1
16386
1
G.729
239.1.1.3
16384
239.1.1.1
16388
1
Wideband
239.1.1.4
16384
239.1.1.1
16390
2
G.711 ulaw
239.1.1.5
16384
239.1.1.1
16392
2
G.711 Alaw
239.1.1.6
16384
239.1.1.1
16394
2
G.729
239.1.1.7
16384
239.1.1.1
16396
2
Wideband
239.1.1.8
16384
239.1.1.1
16398

MulticastSocket. To whom MC message was sent?

Hi All,
My scenarion is:
1. I created MulticastSocket on port XXXX. (Server side)
2. Socket was joined to Multicast groups 228.5.6.7 AND 228.5.6.8 (Server side)
3. Multicast message was sent from another PC to group 228.5.6.7 Client side)
4. Message received by my MulticastSocket. (Server side)
The question is How i can to know to which group this message was sent on Server side?
Continue...
5. Broadcast message was sent from another PC to "255.255.255.255" (Client side)
6. Message received by my MulticastSocket. (Server side)
The question is How i can to know what this is Broadcast message and not from multicast group?
Continue...
7. Unicast message was sent from another PC to Server directly by IP (Client side)
8. Message received by my MulticastSocket. (Server side)
The question is How i can to know what this is Unicast message and not from multicast group and not from Broadcast?
I tried to create several MulticastSocket object on same port XXXX and each one was joined to its own multicast group. (First one to 228.5.6.7, and second to 228.5.6.8)
But then both of then received multicast messages which was sent to 228.5.6.7 OR 228.5.6.8 !!!
Please Help!!!
Thanks.

OK, after spending some time and searching in this forum i found how to fix several of my problems (i bind all sockets to port only and because of this all sockets got everything...)
But one problem i can't solve.
The problem that i can't separate from Broadcast messages and multicast messages. So, if i have two Multicast sockets, where one was bound to 228.5.6.8:XXXX and joined to group 228.5.6.8
and second is for Broadcast only (bound to 0.0.0.0:XXXX) then when i send message to 228.5.6.8 then both of then accept it.
Is it possible to get only Broadcast message on socket which was bound to 0.0.0.0?

Hellp on Nokia E61i associating with Cisco WLC 4402

I met some problem with associate Nokia's dual mode mobile phone E61i with Cisco WLC 4402, hope someone can help me on it:
I setup a VOICE WLAN in 4402(v5.0.148), Layer2 security is WPA1+WPA2, Key management using 802.1x, WPA1 policy enable both TKIP and AES, Radius server using ACS engine(v4.1.1.23)(enable PEAP-MSCHAPv2);
I can use my laptop to join this WLAN(my laptop configure with PEAP/MSCHAPv2, WPA-TKIP, not validate server certificate), but can't let E61i join it, each time it will remind me âunable to connect, WPA authenticate failed).
In E61i, I select WPA/WPA2 as WLAN security mode, enable EAP-PEAP, under EAP-PEAP, I enable EAP-MSCHAPv2; however under Cipher, there's a lot of options such as âRSA,3EDS,SHAâ, âRSA,AES,SHAâ, but there's no TKIP, I have tried to enable all of them and tried only enable those items which include AES, but I failed each time with the same reminder âunable to connect, WPA authenticate failedâ. I checked ACS's failed log, there's no record; In 4402, there also have no record.
If I change the security to open or static WEP for VOICE WLAN, then the E61i can connect to the WLAN.
I think the problem maybe relate to encryption or certificate, right now I just do the test in lab, not in customer's real environment, so I use ACS to generate a self signed certificate and installed it in ACS.
Pls. help to point me what I need to adjust to make it work. Thanks!

Hello,
CCKM Key Management mode on Nokia E61i phone can be used
against Cisco LWAPP AP's with TKIP encryption
Nokia E61i (and other E-series WLAN enabled phones) are supporting CCKM key management method with both dynamic WEP and TKIP ciphers.
On the phone configuration, 802.1X security mode needs to be in use in order to enable CCKM support.Â WPA/WPA2 security mode on the phone is dedicated to standards basedÂ WPA and WPA2 methods and it does not allow usage of proprietary CCKM key management method.
Phone's 802.1X security mode does not mean that phone would only support dynamic WEP encryption method in this mode although in contexts term "802.1X" may be attached to pure dynamic WEP (legacy / pre WPA era)security methods.
Â 802.1X security mode can be seen on Nokia Eseries phones as sort of an "everything with EAP based authentication is allowed" mode, meaning that following key management and cipher configurations are supported:
- WPA-EnterpriseÂ = WPA Key Management (EAP based authentication) with TKIP encryption
- WPA2-EnterpriseÂ = WPA2 Key Management (EAP based authentication) with AES encryption
- Mixed WPA/WPA2-Enterprise = I.e. WPA/WPA2 Mode Migration WPA2 Key Management (EAP based authentication) with AES (for unicast data) and TKIP (for multicast data) ciphers
- 802.1X dynamic WEP = legacy (pre-WPA era) 802.1XÂ based dynamic WEP (EAP based authentication with dynamic WEP encryption)
Supported:
- CCKM with WEP = CCKM Key Management (EAP based authentication) with dynamic WEP encryption
- CCKM with TKIP = CCKM Key Management (EAP based authentication) with TKIP encryption
Not supported:
- CCKM with AES = CCKM Key Management (EAP based authentication) with AES encryption
Please note that CCKM-AES mode (CCKM Key Management with AES cipher) is not working properly due to some incompatibilities between Cisco and Nokia implementations thus it must not be listed as a supported combination on the current Nokia E-series devices. We are also seeing CCKM-Fast
Re-authentication failures with Cisco autonomous AP's when AES encryption is used althoughÂ initial authentication to autonomous AP's is successful.Â Nokia is currently working with Cisco to get CCKM-AES based authentications and roaming working properly with both LWAPP and autonomous Cisco AP's.
Â Also note that Nokia E-SeriesÂ does not support Cisco proprietary CKIP/CMIC encryption/data integrity methods. CKIP/CMIC is supported at least by Cisco autonomous AP's and it seems to be available also
at least on LWAPP AP version 4.1.171.0.
Â CCKM on E-Series devices has been tested against Cisco LWAPP (ver. 4.1.171.0) and it works when TKIP encryption is in use (WPA Policy + TKIP encryption in Cisco LWAPP configuration terms).
In practice this means Cisco LWAPP is configured in a following manner: WLAN -> Edit -> Security->Â
Layer 2 Security = WPA+WPA2
WPA+WPA2 Parameters:
-WPA Policy = enabled
-WPA Encryption = TKIP enabled, AES disabled
-WPA2 policy = disabled
-Auth.Key Mgmt = CCKM
Br,
-Pasi-

Is there any sizing guide line for Coherence ?

Is there any sizing guide line for Coherence ?

Thanks Robert! It appears we could make a concession and work with unicast UDP (and TCP). Multicast needs to be turned off as leaving it enable has been known to flood our networks and needs to be avoided at all cost.
We are looking for an option to have "the lowest guaranteed delivery of data and events" with consistent low latency so we need a smart use of the available network bandwidth... (general overview goal).
That brings me to the next three topics I am trying to really better understand: serialization options, cache server heap sizes, and scalability boundaries.
Heap Sizes -- It has been suggested in the forums to use 1024m cache server heap sizes (so gc pauses are low enough to "provide" consistent low latencies), and, have 75% of the heap for actual object storage... What are the largest CS heap sizes in production, 4GB, in a 64-bit platform?
Serialization -- I am trying com.tangosol.io.ExternalizableLite and I am interested in quantifying possible gains (i.e. CPU, network bandwidth, storage size impact). Anybody tried their own serialization with better results than ExternalizableLite?
Scalability -- Let's say I go with 1024m CS heap sizes, and my 800 clients (growing rapidly to x4 x6), I will probably end very quickly with a significant amount of cache members. Coherence uses their own "P2P" implementation for their cache topologies (TCMP), right?.. What is the realistic limit in terms of maximum cache member number in a Coherence Cluster? Not sure many clusters connected together can provide the latency/data consistency performance scalable use cases need. Anybody can comment on that (with realistic numbers please). Any benchmarks available with 1,000, 2,000, or 4,000+ members?
Thanks
Martin --

Link Local Unicast Addresses and Link Local Multicast Addresses

Similar Messages

Maybe you are looking for