Multicast with AP1141N

Similar Questions

• Difficulty accessing speed N Wireless with AP1141N

  I have successfully installed my AIR-AP1141N-A-K9 with open authentication WPA secutiy but the fasting that connect our wireless devices is 54 Mbps. Can anyone shed some light as to why this is happening?

  Thank you

  Hi Jeff,

  What did you mean by "WPA secutiy open authentication? For speed N, you must configure the layer 2 as open authentication or WPA2/AES security. Check this doc to optimize the performance of N:

  http://www.Cisco.com/en/us/customer/products/ps6366/products_tech_note09186a0080a3443f.shtml

  Zhenning

• VSAN interrogator multicast with igmp snooping active requirement

  When the switch is "igmp snooping" enabled, I do not understand why VSAN Articles and book require a mrouter or interrogator to define.

  Nexus switch igmp debugs and newspapers, VSAN will send members unsolicited reports every 90 seconds at the address of the group 224.1.2.3 and 224.2.3.4. It is without worrying whether or not we have configured for VLAN mrouter or igmp snooping querier. As long as VSAN is coded so as to send the membership periodically reports, should we not there so a "questioning" on the virtual LAN to send Group/General requests.

  As in my tests, I have no igmp mrouter or defined vlan VSAN and VSAN applicant all communicate are good with igmp snooping enabled (default for NX - OS).

  DIA-N5K-02 # show ip igmp snooping-history of events vlan. I have 10.16.127.111

  2014, August 5, 21:31:46.915356 igmp [3465]: [3917]: SN: < 127 > v2 received report: Group 10.16.127.111 on Eth1/21 224.2.3.4

  2014, August 5, 21:31:46.915011 igmp [3465]: [3917]: SN: < 127 > v2 received report: group 224.1.2.3 10.16.127.111 on Eth1/21

  2014, August 5, 21:30:17.037868 igmp [3465]: [3917]: SN: < 127 > v2 received report: Group 10.16.127.111 on Eth1/21 224.2.3.4

  2014, August 5, 21:30:17.037606 igmp [3465]: [3917]: SN: < 127 > v2 received report: group 224.1.2.3 10.16.127.111 on Eth1/21

  2014, August 5, 21:28:46.950748 igmp [3465]: [3917]: SN: < 127 > v2 received report: Group 10.16.127.111 on Eth1/21 224.2.3.4

  2014, August 5, 21:28:46.950273 igmp [3465]: [3917]: SN: < 127 > v2 received report: group 224.1.2.3 10.16.127.111 on Eth1/21

  2014, August 5, 21:27:17.073420 igmp [3465]: [3917]: SN: < 127 > v2 received report: Group 10.16.127.111 on Eth1/21 224.2.3.4

  2014, August 5, 21:27:17.073042 igmp [3465]: [3917]: SN: < 127 > v2 received report: group 224.1.2.3 10.16.127.111 on Eth1/21

  2014, August 5, 21:25:46.985909 igmp [3465]: [3917]: SN: < 127 > v2 received report: Group 10.16.127.111 on Eth1/21 224.2.3.4

  DIA-N5K-02 # show ip igmp snooping vlan 127

  IGMP Snooping information vlan 127

  IGMP snooping active

  Search mode: IP

  Optimized multicast Flood (OMF) disabled

  Applicant IGMP no

  Switch-interrogator disabled

  Tracking explicit IGMPv3 is enabled

  IGMPv2 leave quickly disabled

  Delete report IGMPv1/v2 on

  Disabled removal of IGMPv3 report

  Removing local groups link activated

  Detection of router port using PIM Hello, queries IGMP

  Number of ports in the router: 1

  Number of groups: 2

  Function of vPC VLAN enabled

  Active ports:

  Eth1/21 Eth1/22 Eth1/23 Eth1/27

  Ros

  DIA-N5K-02 # show ip igmp snooping groups vlan 127

  Type: S - static, D - dynamic, R - port of the router, F - Fabricpath base port

  Group VLAN address worm Type port

  127   */*                -    R     Po1

  127 224.1.2.3 v2 D Eth1/22 Eth1/21 Eth1/23

  Eth1/27

  127 224.2.3.4 v2 D Eth1/21 Eth1/22 Eth1/27

  Eth1/23

  We found that for some providers of network switch, an interrogator is required when you enable IGMP snooping. If espionage works without an interrogator for your specific provider, then this is ideal. In all cases, we recommend that you consult your provider for their specific recommended configuration of switch of layer 2 multicast switch.

• Multicast with Air

  Hello

  From:

  http://forums.Adobe.com/message/2423240#2423240

  It was said:

  Remember that you'll need FP10.1 beta * and * the playerglobal.swc accompanying to compile with the Flex SDK.

  -mike

  I've got multicast works with FP 10.1 in accordance with the instructions.

  My question is;  What is required to compile multicast AIR?

  Flex 4?

  AIR 2?

  Stratus special airglobal.swc?

  See you soon,.

  Arnie

  I think that you need just to AIR 2 SDK.  that should give you access to all the new APIs.

  -mike

• MDT 2012 Multicast fails rc =-2147024891

  I'm trying to Setup multicast with MDT 2012 and WDS 2008 running on a Win 2008 Server.

  Whenever I have the image on a computer, I get the following in the BDD.log file
  Transfer multicast to the directory: C:\MININT\Operating Systems\Win 7 Ent SP1 x 64 LTIApply 28/01/13 29/01/2013 15:43:50 0 (0x0000)
  LTIApply 29/01/2013 15:43:50 0 (0x0000)
  Command has been started (process ID 1292) LTIApply 29/01/2013 15:43:50 0 (0x0000)
  ZTI Heartbeat: command worked for 0 minutes (process ID 1292) LTIApply 29/01/2013 15:43:50 0 (0x0000)
  Event 41003 sent: ZTI Heartbeat: command worked for 0 minutes (process ID 1292) LTIApply 29/01/2013 15:43:51 0 (0x0000)
  Console >
  LTIApply 29/01/2013 15:43:51 0 (0x0000)
  Console > transfer began.
  LTIApply 29/01/2013 15:43:51 0 (0x0000)
  Console >
  LTIApply 29/01/2013 15:43:51 0 (0x0000)
  Console > complete transfer [0x80070005].
  LTIApply 29/01/2013 15:43:51 0 (0x0000)
  Console > transfer failed. [0x80070005]. LTIApply 29/01/2013 15:43:51 0 (0x0000)
  Return code of command =-2147024891 LTIApply 29/01/2013 15:43:51 0 (0x0000)
  Multicast transfer could not be completed, rc =-2147024891, fall back using \\Falcon\deploymentshare$\Operating Systems\Win 7 SP1 Ent x 64 1-28-13\Win 7 Ent SP1 x 64 LTIApply 1-28 - 13.wim 29/01/2013 15:43:51 0 (0x0000)
  I googled the error code, but found nothing.
  Any help would be appreciated.
  Thank you

  Hello ESteiner,

  Microsoft Community has support for consumer issues in Windows 8, Windows 7. Windows Vista and Windows XP. You questions involves MDT 2012 and WDS 2008 running on a Windows 2008 Server. This would be better funded in the TechNet Forums for ITPros.  Click here for a link to transfer your question in TechNet.

  Experts it will be better able to solve your problems of deployment of Windows.

  Sincerely,

  Marilyn

• UCS and L2 multicast issues

  Hello

  I have 2 data centers connected through a tissue of spine / sheet using BGP EVPN. In a domain controller, I UCS and other legacy Dell ESX servers connected to catalyst switches. These are shared resources via a VPC local 9 k leafs to interconnect with the fabric. Some of VLANS have L2 multicast running. All the VLANS relevant are bridged through the fabric and presented to UCS/ESXi. When virtual machines have been vmotioned overall everything has worked well except the multicast broke. I created a policy of multicast in UCS and activated the interrogator with an IP address in one of VLAN relevant from the cisco documentation what UCS will not pass traffic unless there is a mrouter/interrogator. Then, I joined politics to the Vlan relevant under the section of LAN. However still does not. I don't see any questioning on the directly connected switches information upstream is. Should applicant IGMP allowed on switches?

  Thank you!

  https://supportforums.Cisco.com/document/12725606/setting-multicast-with...

  https://supportforums.Cisco.com/discussion/12111706/UCS-and-multicast

• Multicast problem

  Hello

  I try to install Oracle Clusterware ASM 11.2.0.4

  I get an error on the multicast:

  Cluvfy show me:

  Verification of the subnet "192.169.100.0" for multicast with '230.0.1.0 '... multicast group communication

  GLWB-11134: Interface "192.169.100.60" on the "server01" node is not able to communicate with the interface "192.169.100.60" on the node "server01".

  Verification of the subnet "192.169.100.0" for multicast with "224.0.0.251. multicast group communication

  GLWB-11134: Interface "192.169.100.60" on the "server01" node is not able to communicate with the interface "192.169.100.60" on the node "server01".

  Verification of the subnet "10.0.10.0" for multicast with '230.0.1.0 '... multicast group communication

  GLWB-11134: Interface '10.0.10.10"on the"server01"node is not able to communicate with the interface"10.0.10.10' on the node "server01".

  Verification of the subnet "10.0.10.0" for multicast with "224.0.0.251. multicast group communication

  GLWB-11134: Interface '10.0.10.10"on the"server01"node is not able to communicate with the interface"10.0.10.10' on the node "server01".

  Ifconfig:

  bond0	Link encap HWaddr 90: 1 B: 0E:44:AD:70
  	INET addr:192.169.100.60 Bcast:192.169.100.255 mask: 255.255.255.0
  	BROADCAST currently RUNNING MASTER MULTICAST MTU:1500 metric: 1
  	Dropped packets: 11681416 RX errors: 0:0 overruns: 0 frame: 0
  	Dropped packets: 11368315 TX errors: 0:0 overruns: 0 carrier: 0
  	collisions: 0 txqueuelen:0
  	RX bytes: 9427005938 (8.7 GiB) TX bytes: 8607168609 (8.0 GiB)

  bond1	Link encap HWaddr A0:36:9F:5F:FD:9 C
  	INET addr:10.0.10.10 Bcast:10.0.10.255 mask: 255.255.255.0
  	BROADCAST currently RUNNING MASTER MULTICAST MTU:1500 metric: 1
  	Fall of RX packets: 0 errors: 0:0 overruns: 0 frame: 0
  	Dropped TX packets: 0 errors: 0:0 overruns: 0 carrier: 0
  	collisions: 0 txqueuelen:0
  	RX bytes: 0 (0.0 b) TX bytes: 0 (0.0 b)

  Any ideas?

  Ok

  solved

  iptables is active.

• Clustering with Unicast

  We now use Multicast with Weblogic 9.2 for clustering but now migrate to Weblogic 10.3 and want to switch to unicast. The documentation seems kind of blurry for clustering of unicast. I have a few questions.
  
  (1) the Unicast broadcast channel. What is it and what is the format of one.
  (2) I need create a channel custom somewhere? I don't want to use the default channel, because we have many areas in the same server.
  (3) generally made Unicast work and how is it different from multicast.
  
  Thank you
  Tom.

  I hope it's that some useful:

  (1) this is the channel used for unicast traphic, if you leave it blank the channel by default (listening address) of managed servers are used

  (2) you can add strings under the Protocol-> channels-managed server
  A channel is connected to a host name and port, so it must be unique. I don't see how it would effect several areas on 1 machine since they must use unique host + port so combinations for each managed server.

  (3) http://en.wikipedia.org/wiki/Unicast

  Kind regards

  Jan

• Hi ALL, did any attempt on the virtual computer NETWORK load balancing using HYPERV on UCS blades

  I try to configure the CASE server cluster by using the Unicast NLB on the virtual machine on different blades on the UCS, it works for awhile, then he abandoned packages.

  I heard that this screenplay of unicast is not supported in the UCS when she used END-host mode in the fabric interconnet...? any attempted before.

  Would it, I use the multicast mode is that something needs to be done on the FBI62020 or the LAN switch upstream. ??

  Header note I found on the implementation of UCS for mulitcast NLBL:

  Microsoft NLB can be deployed in 3 modes:

  Unicast

  Multicast

  IGMP multicast

  For series B UCS deployments, we have seen that the multicast and IGMP multicast work.

  IGMP multicast mode seems to be the more reliable deployment mode.

  To do this, the monitoring settings:

  All NLB Microsoft value "Multicast IGMP" nodes.  Important!  Check ths by logging into EACH node independently.  Do not rely on the MMC of NLB snap.

  An IGMP applicant must be present on the VLAN of NLB.  If PIM is enabled on the VIRTUAL LAN that is your interrogator.  UCS cannot function as applicant IGMP.  If an interrogator of functioning is not present, NLB IGMP mode will not work.

  You must have a static ARP entry on cheating it upstream pointing IP address Unicast NLB on the multicast MAC address NETWORK load balancing.  This need will set up, of course, on the VLAN of the NLB VIP. The key is that the routing for the NLB VLAN interface must use this ARP entry as a unicast IP ARP response may not contain a multicast mac address. (Violation of the RFC 1812)  Hosts on the NLB VLAN must also use the static entry.  You may have several entries ARP.  IOS can use a function of 'alias' of ARP. (Google it.)

  How Microsoft NLB works. -The truncated for brevity Mac addresses.

  TOPOLOGY OF NLB MS

  NETWORK VLAN 10 = subnet 10.1.1.0/24 IP load balancing

  VIP = 10.1.1.10 NETWORK LOAD BALANCING

  Arp entry static switch advanced IP 10.1.1.10 upstream to MAC 01

  NLB VIP (MAC 01, IP 10.1.1.10)

  NODE-A (AA, MAC IP:10.1.1.88)

  NŒUD-B (MAC BB, IP:10.1.1.99)

  Using the IGMP snooping and interrogator VLAN snooping table is filled with the mac NLB address and groups pointing to the appropriate L2 ports.

  MS NLB nodes will send the responses of IGMP queries.

  This snooping table could take 30 to 60 seconds to complete.

  Host on VLAN 200 (10.200.1.35) sends traffic to NETWORK VIP (10.1.1.10) load balancing

  It goes of course to VLAN 10 interface that uses the static ARP entry to resolve to address MAC 01 VIP NETWORK load balancing.

  Since it is a multicast frame destination it will be forward by the IGMP snooping table.

  The framework will arrive at ALL NLB nodes. (NŒUD-A & NŒUD-B)

  NLB nodes will use its load balancing algorithm to determine which node will manage the TCP session.

  Only one NLB node will respond to this host with TCP ACK to start the session.

  NOTES

  This works in a VMware with N1k, standard vSwtich and vDS environment. Where surveillance IGMP is not enabled, the framing for VIP MAC NETWORK load balancing will be flooded.

  NLB can only work with TCP-based services.

  As stated previously mapping an IP unicast to a multicast mac address is a violation implied by RFC 1812.

  TROUBLESHOOTING

  Make sure your interrogator is working. Just to clarify that this does not mean that it is actually at work.

  Wireshark lets check that IGMP queries are received by the NLB nodes.

  Make sure that the ARP response works as expected.  Once Wireshark again is your friend.

  Look at the paintings IGMP snooping. Validate the L2 ports appearing as expected.

  CSCtx27555 [Bug-preview for CSCtx27555] Unknown multicast with destination outside the range MAC 01:xx: are deleted. (6200 FI fixed in 2.0.2m)

  IGMP mode not affected.

  CSCtx27555    Unknown multicast with destination outside the range MAC 01:xx: are deleted.

  http://Tools.Cisco.com/support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtx27555

  fixed in 2.0(2m)

  Solution: Change the NLB mode of operation of "Multicast" to "multicast IGMP', which modifies balancing load NETWORK VIP MAC at 0100.5exx.xxx Beach, allows to transfer occur as expected.

  Q: and if I switch to switch mode, which means all of the profile and the settings on the servers are completely exhausted and I need to recreate them. ???

  A:Cisco Unified Computing System Ethernet switching Modes

  http://www.Cisco.com/en/us/solutions/collateral/ns340/ns517/ns224/ns944/whitepaper_c11-701962.html

  -There is no impact on the configuration, you have done service profiles.  they will continue to work as expected.  Mode selector has the FI behave more like a conventional switch.  Most notable is that Spanning tree will be activated and if you have several uplinks yew, tree covering weight will begin to block redundant paths.

  You need to review your topology and what impact tree covering weight.  Generally, we at the switch port upstream defined as "edge master", you want to delete this line.

  For pre-production and laboratory environment, PDI can help qualified with the planning, design and implementation partners.  Given to review the IDP site and open a case if you need more detailed assistance.

• failure of the preliminary checks for Oracle Real Application Cluster 12 C.

  Hi all. Please, help to investigate and resolve. Thank you.

  [grid@orac1 grid] $./runcluvfy.sh stage pre - crsinst - orac1, orac2 n - correction-verbose

  Conducting due diligence to install cluster services

  Audit accessibility of node...

  Check: Accessibility of node of the node 'orac1 '.

  Accessible destination node?

  ------------------------------------  ------------------------

  orac1                                 yes

  orac2                                 yes

  Result: Check accessibility node from node 'orac1 '.

  Verify the equivalence of the user...

  Check: Equivalence for the user "grid."

  Status of node name

  ------------------------------------  ------------------------

  orac2 spent

  orac1 spent

  Result: Use CONTROL passed to user equivalence "grid."

  Verify node connectivity...

  Checking the configuration of the hosts file...

  Status of node name

  ------------------------------------  ------------------------

  orac1 spent

  orac2 spent

  The hosts config file verification successful

  Interface of the node information to "orac1".

  Name address IP subnet gateway Gateway bat HW address MTU

  ------ --------------- --------------- --------------- --------------- ----------------- ------

  eth0 10.154.137.101 10.154.137.0 0.0.0.0 10.0.4.2 08:00:27:28:D1:1F 1500

  eth1 10.154.138.101 10.154.138.0 0.0.0.0 10.0.4.2 08:00:27:51:E8:B9 1500

  eth2 10.0.4.15 10.0.4.0 0.0.0.0 10.0.4.2 08:00:27:5 B: D7:29 1500

  Interface of the node information to "orac2".

  Name address IP subnet gateway Gateway bat HW address MTU

  ------ --------------- --------------- --------------- --------------- ----------------- ------

  eth0 10.154.137.102 10.154.137.0 0.0.0.0 10.0.4.2 08:00:27:7F:C8:70 1500

  eth1 10.154.138.102 10.154.138.0 0.0.0.0 10.0.4.2 08:00:27:9 D: 27:D8 1500

  eth2 10.0.4.15 10.0.4.0 0.0.0.0 10.0.4.2 08:00:27:6E:92:43 1500

  Check: Subnet node connectivity "10.154.137.0."

  Source Destination connected?

  ------------------------------  ------------------------------  ----------------

  orac1 [10.154.137.101] orac2 [10.154.137.102] Yes

  Result: Connectivity node passed to subnet "10.154.137.0" with one or more nodes orac1, orac2

  Check: The subnet '10.154.137.0' TCP connectivity

  Source Destination connected?

  ------------------------------  ------------------------------  ----------------

  orac1:10.154.137.101 orac2:10.154.137.102 failed

  ERROR:

  PRVF-7617: node connectivity between "orac1: 10.154.137.101" and "orac2: 10.154.137.102" failed

  Result: Check failed for the '10.154.137.0' subnet TCP connectivity

  Check: Subnet node connectivity "10.154.138.0."

  Source Destination connected?

  ------------------------------  ------------------------------  ----------------

  orac1 [10.154.138.101] orac2 [10.154.138.102] Yes

  Result: Connectivity node passed to subnet "10.154.138.0" with one or more nodes orac1, orac2

  Check: The subnet '10.154.138.0' TCP connectivity

  Source Destination connected?

  ------------------------------  ------------------------------  ----------------

  orac1:10.154.138.101 orac2:10.154.138.102 failed

  ERROR:

  PRVF-7617: node connectivity between "orac1: 10.154.138.101" and "orac2: 10.154.138.102" failed

  Result: Check failed for the '10.154.138.0' subnet TCP connectivity

  Check: Subnet node connectivity "10.0.4.0."

  Source Destination connected?

  ------------------------------  ------------------------------  ----------------

  orac1 [10.0.4.15] orac2 [10.0.4.15] Yes

  Result: Connectivity node passed to subnet "10.0.4.0" with one or more nodes orac1, orac2

  Check: The subnet '10.0.4.0' TCP connectivity

  Source Destination connected?

  ------------------------------  ------------------------------  ----------------

  orac1:10.0.4.15 orac2:10.0.4.15 failed

  ERROR:

  PRVF-7617: node connectivity between "orac1: 10.0.4.15" and "orac2: 10.0.4.15" failed

  Result: Check failed for the '10.0.4.0' subnet TCP connectivity

  Interfaces available on subnet "10.0.4.0" who are likely candidates for VIP are:

  orac1 eth2:10.0.4.15

  orac2 eth2:10.0.4.15

  CAUTION:

  Could not find an appropriate interface for the private interconnection range

  Checking consistency of subnet mask...

  Verification of consistency for the subnet mask for subnet "10.154.137.0."

  Verification of consistency for the subnet mask for subnet "10.154.138.0."

  Verification of consistency for the subnet mask for subnet "10.0.4.0."

  Verification of consistency for the last subnet mask.

  ERROR:

  GLWB-1172: the IP "10.0.4.15" is on more than one interface 'eth2, eth2' nodes 'orac2, orac1 '.

  Result: Check the node has no connectivity

  Checking for multicast communication...

  Verification of the subnet "10.154.137.0" for multicast with "224.0.0.251. multicast group communication

  GLWB-11138: Interface '10.154.137.101' on 'orac1' node is not able to communicate with interface '10.154.137.101' on 'orac1' node to the multicast group "224.0.0.251.

  GLWB-11138: Interface '10.154.137.101' on 'orac1' node is not able to communicate with interface '10.154.137.102' on 'orac2' node to the multicast group "224.0.0.251.

  GLWB-11138: Interface '10.154.137.102' on 'orac2' node is not able to communicate with interface '10.154.137.101' on 'orac1' node to the multicast group "224.0.0.251.

  GLWB-11138: Interface '10.154.137.102' on 'orac2' node is not able to communicate with interface '10.154.137.102' on 'orac2' node to the multicast group "224.0.0.251.

  Verification of the subnet "10.154.138.0" for multicast with "224.0.0.251. multicast group communication

  GLWB-11138: Interface '10.154.138.101' on 'orac1' node is not able to communicate with interface '10.154.138.101' on 'orac1' node to the multicast group "224.0.0.251.

  GLWB-11138: Interface '10.154.138.101' on 'orac1' node is not able to communicate with interface '10.154.138.102' on 'orac2' node to the multicast group "224.0.0.251.

  GLWB-11138: Interface '10.154.138.102' on 'orac2' node is not able to communicate with interface '10.154.138.101' on 'orac1' node to the multicast group "224.0.0.251.

  GLWB-11138: Interface '10.154.138.102' on 'orac2' node is not able to communicate with interface '10.154.138.102' on 'orac2' node to the multicast group "224.0.0.251.

  Verification of the subnet "10.0.4.0" for multicast with "224.0.0.251. multicast group communication

  GLWB-11138: Interface '10.0.4.15' on 'orac1' node is not able to communicate with interface '10.0.4.15' on 'orac1' node to the multicast group "224.0.0.251.

  GLWB-11138: Interface '10.0.4.15' on 'orac1' node is not able to communicate with interface '10.0.4.15' on 'orac2' node to the multicast group "224.0.0.251.

  GLWB-11138: Interface '10.0.4.15' on 'orac2' node is not able to communicate with interface '10.0.4.15' on 'orac1' node to the multicast group "224.0.0.251.

  GLWB-11138: Interface '10.0.4.15' on 'orac2' node is not able to communicate with interface '10.0.4.15' on 'orac2' node to the multicast group "224.0.0.251.

  Checking configuration ASMLib.

  Status of node name

  ------------------------------------  ------------------------

  orac1 spent

  orac2 spent

  Result: Check the configuration of ASMLib passed.

  Check: Total memory

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  orac2 GB 5,714 (5991520,0 KB) increased from 4 GB (4194304,0 KB)

  orac1 GB 5,714 (5991520,0 KB) increased from 4 GB (4194304,0 KB)

  Result: The total past memory check

  Check: Available memory

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  transmitted orac2 Go 5,2293 (5483324,0 KB) 50 MB (51200,0 KB)

  transmitted orac1 Go 5,1456 (5395600,0 KB) 50 MB (51200,0 KB)

  Result: Available past memory check

  Check: Swap space

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  orac2 GB 6,125 (6422520,0 KB) from GB 5,714 (5991520,0 KB)

  orac1 GB 6,125 (6422520,0 KB) from GB 5,714 (5991520,0 KB)

  Result: Check the Swap space past

  Check: Disk space for "orac2: / usr, orac2: / var, orac2: / etc, orac2: / sbin, orac2: / tmp '.

  Path node name Mount point available requested State

  ----------------  ------------  ------------  ------------  ------------  ------------

  orac2/usr / 37,8398 GB GB 1,0635 spent

  orac2/var / 37,8398 GB GB 1,0635 spent

  orac2/etc / 37,8398 GB GB 1,0635 spent

  orac2/sbin / 37,8398 GB GB 1,0635 spent

  orac2/tmp / 37,8398 GB GB 1,0635 spent

  Result: Free past to check the disk space ' orac2: / usr, orac2: / var, orac2: / etc, orac2: / sbin, orac2: / tmp '.

  Check: Disk space for "orac1: / usr, orac1: / var, orac1: / etc, orac1: / sbin, orac1: / tmp '.

  Path node name Mount point available requested State

  ----------------  ------------  ------------  ------------  ------------  ------------

  orac1/usr / 32,4382 GB GB 1,0635 spent

  orac1/var / 32,4382 GB GB 1,0635 spent

  orac1/etc / 32,4382 GB GB 1,0635 spent

  orac1/sbin / 32,4382 GB GB 1,0635 spent

  orac1/tmp / 32,4382 GB GB 1,0635 spent

  Result: Free past to check the disk space ' orac1: / usr, orac1: / var, orac1: / etc, orac1: / sbin, orac1: / tmp '.

  Check: Existence of user for "grid".

  Name of State comment node

  ------------  ------------------------  ------------------------

  orac2 past exists (1100)

  orac1 past exists (1100)

  Check for multiple users with the value of the UID 1100

  Result: Check for multiple users with the value of the UID 1100 spent

  Result: Use existence CONTROL passed to 'grid '.

  Check: Existence of group 'oinstall '.

  Name of State comment node

  ------------  ------------------------  ------------------------

  orac2 passed exists

  orac1 passed exists

  Result: Existence of group check passed for "oinstall".

  Check: Existence of group for "dba".

  Name of State comment node

  ------------  ------------------------  ------------------------

  orac2 passed exists

  orac1 passed exists

  Result: Existence of group check passed for "dba".

  Check: the members of the user 'grid' group 'oinstall' [primary]

  Name of node user is group is user group primary status

  ----------------  ------------  ------------  ------------  ------------  ------------

  orac2 Yes Yes Yes Yes past

  orac1 Yes Yes Yes Yes past

  Result: Membership search for "grid" user in the group 'oinstall' [as Primary] spent

  Check: Membership of the user "grid" in a group 'dba '.

  Name of node user is group are users in a group situation

  ----------------  ------------  ------------  ------------  ----------------

  orac2 Yes Yes Yes past

  orac1 Yes Yes Yes past

  Result: Check for user "grid" in group membership 'dba' spent

  Tick: Run level

  Name of the node run status level required

  ------------  ------------------------  ------------------------  ----------

  orac2         5                         3,5                       passed

  orac1         5                         3,5                       passed

  Result: Run control the level of the past

  Check: Hard limits for "file descriptors open maximum".

  Node name Type requested State available

  ----------------  ------------  ------------  ------------  ----------------

  4096, 65536 failed hard orac2

  4096, 65536 failed hard orac1

  Result: Hard limits check failed for 'file descriptors open maximum.

  Check: Limits Soft for "file descriptors open maximum".

  Node name Type requested State available

  ----------------  ------------  ------------  ------------  ----------------

  1024 1024 soft orac2 spent

  sweet orac1 4096 1024 spent

  Result: Soft limits check passed for "file descriptors open maximum".

  Check: Hard limits for "maximum user processes.

  Node name Type requested State available

  ----------------  ------------  ------------  ------------  ----------------

  46654 16384 hard orac2 spent

  46654 16384 hard orac1 spent

  Result: Verification of limits hard to last for "maximum user process.

  Check: Limits Soft for "maximum user process.

  Node name Type requested State available

  ----------------  ------------  ------------  ------------  ----------------

  orac2 1024-2047 soft failed

  orac1 1024-2047 soft failed

  Result: Limits Soft check failed for 'maximum process of the user.

  Control: System Architecture

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  orac2 x86_64 x86_64 spent

  orac1 x86_64 x86_64 spent

  Result: Verification of the system architecture past

  Control: Kernel Version

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  orac2-2.6.32 - 279.el6.x86_64 2.6.32 spent

  orac1-2.6.32 - 279.el6.x86_64 2.6.32 spent

  Result: Last kernel version control

  Check: Parameter of kernel for 'semmsl.

  Current name configured node comment of the requested State

  ----------------  ------------  ------------  ------------  ------------  ------------

  orac1 250 250 250 spent

  orac2 250 250 250 spent

  Result: Check of kernel parameter passed to "semmsl.

  Check: Parameter of kernel for 'semmns.

  Current name configured node comment of the requested State

  ----------------  ------------  ------------  ------------  ------------  ------------

  32000 32000 32000 orac1 spent

  32000 32000 32000 orac2 spent

  Result: Check kernel parameter passed to "semmns.

  Check: Parameter of kernel for 'semopm.

  Current name configured node comment of the requested State

  ----------------  ------------  ------------  ------------  ------------  ------------

  orac1 100 100 100 spent

  orac2 100 100 100 spent

  Result: Check kernel parameter passed to "semopm.

  Check: Parameter of kernel for 'semmni.

  Current name configured node comment of the requested State

  ----------------  ------------  ------------  ------------  ------------  ------------

  orac1 128 128 128 spent

  orac2 128 128 128 spent

  Result: Check of kernel parameter passed to "semmni.

  Check: "Package" kernel parameter

  Current name configured node comment of the requested State

  ----------------  ------------  ------------  ------------  ------------  ------------

  4398046511104 4398046511104 3067658240 orac1 spent

  4398046511104 4398046511104 3067658240 orac2 spent

  Result: Check of kernel parameter passed to 'package '.

  Check: Parameter of kernel for "shmmni(5)."

  Current name configured node comment of the requested State

  ----------------  ------------  ------------  ------------  ------------  ------------

  4096-4096-4096 orac1 spent

  4096-4096-4096 orac2 spent

  Result: Check of kernel parameter passed to 'shmmni(5) '.

  Check: "Shmall" kernel parameter

  Current name configured node comment of the requested State

  ----------------  ------------  ------------  ------------  ------------  ------------

  4294967296 4294967296 599152 orac1 spent

  4294967296 4294967296 599152 orac2 spent

  Result: Check kernel parameter passed to "shmall.

  Check: Parameter of kernel "file-max.

  Current name configured node comment of the requested State

  ----------------  ------------  ------------  ------------  ------------  ------------

  6815744 6815744 6815744 orac1 spent

  6815744 6815744 6815744 orac2 spent

  Result: Check of kernel parameter passed to 'file-max.

  Check: "Ip_local_port_range" kernel parameter

  Current name configured node comment of the requested State

  ----------------  ------------  ------------  ------------  ------------  ------------

  orac1 between 9000 & 65500 between 9000 & 65500 between 9000 & 65535 passed

  orac2 between 9000 & 65500 between 9000 & 65500 between 9000 & 65535 passed

  Result: Check of kernel parameter passed to «ip_local_port_range»

  Check: Parameter of kernel for "rmem_default."

  Current name configured node comment of the requested State

  ----------------  ------------  ------------  ------------  ------------  ------------

  262144 262144 262144 orac1 spent

  262144 262144 262144 orac2 spent

  Result: Check of kernel parameter passed to 'rmem_default '.

  Check: "Rmem_max" kernel parameter

  Current name configured node comment of the requested State

  ----------------  ------------  ------------  ------------  ------------  ------------

  4194304 4194304 4194304 orac1 spent

  4194304 4194304 4194304 orac2 spent

  Result: Check of kernel parameter passed to «rmem_max»

  Check: Parameter of kernel for "wmem_default."

  Current name configured node comment of the requested State

  ----------------  ------------  ------------  ------------  ------------  ------------

  262144 262144 262144 orac1 spent

  262144 262144 262144 orac2 spent

  Result: Check of kernel parameter passed to 'wmem_default '.

  Check: "Wmem_max" kernel parameter

  Current name configured node comment of the requested State

  ----------------  ------------  ------------  ------------  ------------  ------------

  1048576 1048576 1048576 orac1 spent

  1048576 1048576 1048576 orac2 spent

  Result: Check kernel parameter passed to "wmem_max.

  Check: Parameter of kernel for "aio-max-nr.

  Current name configured node comment of the requested State

  ----------------  ------------  ------------  ------------  ------------  ------------

  1048576 1048576 1048576 orac1 spent

  1048576 1048576 1048576 orac2 spent

  Result: Check of kernel parameter passed to "aio-max-nr.

  Check: Existence of package for "binutils".

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  binutils - 2.20.51.0.2 - 5.34.el6 orac2 binutils - 2.20.51.0.2 spent

  binutils - 2.20.51.0.2 - 5.34.el6 orac1 binutils - 2.20.51.0.2 spent

  Result: Package of checking for "binutils".

  Check: Existence of package for "compat-libcap1.

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  orac2 compat-libcap1 - 1.10 - 1 compat-libcap1 - 1.10 spent

  orac1 compat-libcap1 - 1.10 - 1 compat-libcap1 - 1.10 spent

  Result: Package of checking for "compat-libcap1.

  Control: Existence of package for "compat-libstdc ++-33 (x86_64).

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  orac2 compat-libstdc ++ - 33 (x86_64) - 3.2.3 - 69.el6 compat-libstdc ++ - 33 (x86_64) - 3.2.3 spent

  orac1 compat-libstdc ++ - 33 (x86_64) - 3.2.3 - 69.el6 compat-libstdc ++ - 33 (x86_64) - 3.2.3 spent

  Result: Package of checking for "compat-libstdc ++-33 (x86_64).

  Control: Existence of package for 'libgcc (x86_64).

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  orac2 libgcc (x86_64) - 4.4.7 - 11.el6 libgcc (x86_64) - 4.4.4 spent

  orac1 libgcc (x86_64) - 4.4.7 - 11.el6 libgcc (x86_64) - 4.4.4 spent

  Result: Package of checking for 'libgcc (x86_64).

  Control: Existence of package for 'libstdc ++ (x86_64).

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  orac2 libstdc ++ (x86_64) - 4.4.7 - 11.el6 libstdc ++ (x86_64) - 4.4.4 spent

  orac1 libstdc ++ (x86_64) - 4.4.7 - 11.el6 libstdc ++ (x86_64) - 4.4.4 spent

  Result: Package of checking for 'libstdc ++ (x86_64).

  Control: Existence of package for 'libstdc ++ - devel (x86_64).

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  orac2 libstdc ++ - devel (x86_64) - 4.4.7 - 11.el6 libstdc ++ - devel (x86_64) - 4.4.4 spent

  orac1 libstdc ++ - devel (x86_64) - 4.4.7 - 11.el6 libstdc ++ - devel (x86_64) - 4.4.4 spent

  Result: Package of checking for 'libstdc ++ - devel (x86_64).

  Check: Existence of package for "sysstat".

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  sysstat - 9.0.4 - sysstat - 9.0.4 spent 20.el6 orac2

  sysstat - 9.0.4 - sysstat - 9.0.4 spent 20.el6 orac1

  Result: Package of checking for "sysstat".

  Check: Existence of package for 'gcc '.

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  4.4.7 - gcc - 11.el6 orac2 gcc - 4.4.4 spent

  4.4.7 - gcc - 11.el6 orac1 gcc - 4.4.4 spent

  Result: Package of checking for "gcc".

  Check: Package of existence 'gcc - c++.

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  orac2 gcc - c++ - 4.4.7 - 11.el6 gcc - c++ - 4.4.4 spent

  orac1 gcc - c++ - 4.4.7 - 11.el6 gcc - c++ - 4.4.4 spent

  Result: Package of checking for "gcc - c++.

  Check: Existence of package for 'ksh '.

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  ksh-20120801 - 21.el6.1 orac2 spent ksh...

  ksh-20120801 - 21.el6.1 orac1 spent ksh...

  Result: Package of checking for "ksh".

  Check: Existence of package to 'make it '.

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  make orac2 make - 3.81 - 20.el6 - 3.81 spent

  make orac1 make - 3.81 - 20.el6 - 3.81 spent

  Result: Package of verification of existence moved to 'make it '.

  Control: Existence of package for 'glibc (x86_64).

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  orac2 glibc (x86_64)-2, 12 - 1.149.el6 glibc (x86_64)-2,12 spent

  orac1 glibc (x86_64)-2, 12 - 1.149.el6 glibc (x86_64)-2,12 spent

  Result: Package of checking for "glibc (x86_64).

  Control: Existence of package for 'glibc-devel (x86_64).

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  orac2 glibc-devel (x86_64)-2, 12 - 1.149.el6 glibc-devel (x86_64)-2,12 spent

  orac1 glibc-devel (x86_64)-2, 12 - 1.149.el6 glibc-devel (x86_64)-2,12 spent

  Result: Package of checking for "glibc-devel (x86_64).

  Control: Existence of package for "libaio (x86_64).

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  orac2 (x86_64) - 0.3.107 - 10.el6 libaio libaio (x86_64) - 0.3.107 spent

  orac1 (x86_64) - 0.3.107 - 10.el6 libaio libaio (x86_64) - 0.3.107 spent

  Result: Package of checking for "libaio (x86_64).

  Control: Existence of package for "libaio-devel (x86_64).

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  orac2 libaio-devel (x86_64) - 0.3.107 - 10.el6 libaio-devel (x86_64) - 0.3.107 spent

  orac1 libaio-devel (x86_64) - 0.3.107 - 10.el6 libaio-devel (x86_64) - 0.3.107 spent

  Result: Package of checking for "libaio-devel (x86_64).

  Check: Existence of package for 'nfs-utils '.

  Requested State available node name

  ------------  ------------------------  ------------------------  ----------

  orac2 nfs-utils - 1.2.3 - 26.el6 nfs-utils - 1.2.3 - 15 past

  orac1 nfs-utils - 1.2.3 - 26.el6 nfs-utils - 1.2.3 - 15 past

  Result: Package of checking for 'nfs-utils '.

  Check the availability of the "6200,6100" ports required for the component 'Oracle Notification Service (ONS)'

  Name of the node Port number protocol status available

  ----------------  ------------  ------------  ------------  ----------------

  orac2 6200 TCP successful Yes

  orac1 6200 TCP successful Yes

  orac2 6100 TCP successful Yes

  orac1 6100 TCP successful Yes

  Result: Availability of Port Control passed to ports '6200,6100 '.

  Check for multiple users with the value of the UID 0

  Result: Check for multiple users with the value of the UID 0 past

  Check: The current group ID

  Result: Control of current past group ID

  Check the consistency of the main group of the root user from

  Status of node name

  ------------------------------------  ------------------------

  orac2 spent

  orac1 spent

  Check the consistency of the primary group of the user root past

  Starting synchronization check by using the Network Time Protocol (NTP)...

  Of NTP Configuration file check has started...

  The NTP configuration file "/ etc/ntp.conf" is available on all nodes

  Of NTP Configuration file check passed

  Checking delay of the devil...

  Check: Time for 'ntpd '.

  Node name race?

  ------------------------------------  ------------------------

  orac2                                 yes

  orac1                                 yes

  Result: Check time-out for 'ntpd '.

  Check for NTP daemon or service life spent on all nodes

  Check if NTP daemon or service using the 123 UDP port on all nodes

  Search the NTP daemon or service uses the port UDP 123

  Name of the node Port open?

  ------------------------------------  ------------------------

  orac2                                 yes

  orac1                                 yes

  Common NTP Time Server checks began...

  Time server NTP "193.27.209.1" is common to all nodes on which runs the NTP daemon

  Time server NTP "194.29.130.252" is common to all nodes on which runs the NTP daemon

  Registration of time server common NTP spent

  The clock offset record time server NTP began...

  Audit on the nodes '[orac2, orac1] "...

  Check: The Offset of the time clock to the time server NTP

  Time server: 193.27.209.1

  Time limit offset: 1000,0 ms

  Name of node time shift status

  ------------  ------------------------  ------------------------

  orac2 - 355.25 spent

  orac1 - 124.19 spent

  Time server "193.27.209.1" has time shifts that are within acceptable limits for the nodes "[orac2, orac1].

  Time server: 194.29.130.252

  Time limit offset: 1000,0 ms

  Name of node time shift status

  ------------  ------------------------  ------------------------

  orac2 - 358.87 spent

  orac1 - 109.63 spent

  Time server "194.29.130.252" has time shifts that are within acceptable limits for the nodes "[orac2, orac1].

  The clock offset check past

  Result: Control of synchronization using Network Time Protocol (NTP) spent

  Base file name consistency check model...

  Check the consistency of spent Core file name pattern.

  Check to make sure that the user "grid" is not in the group "root".

  Name of State comment node

  ------------  ------------------------  ------------------------

  There is no such thing as orac2 spent

  There is no such thing as orac1 spent

  Result: User "grid" is not part of the "root" group Check the past

  Audit default user file creation mask

  Name of node available comment required

  ------------  ------------------------  ------------------------  ----------

  0022-0022 orac2 spent

  0022-0022 orac1 spent

  Result: Mask by default user file creation passed Verification

  Checking the integrity of the file "/ /etc/resolv.conf ' overall of nodes

  Check the file "/ /etc/resolv.conf" to ensure that the only area and search for entries is defined

  CAUTION:

  PRVF-5640: both search and domain entries are present in the file ' / /etc/resolv.conf ' on the following nodes: orac1, orac2

  Checking if entry field in the file ' / /etc/resolv.conf ' is constant in knots...

  Check the file "/ /etc/resolv.conf ' to ensure that single domain entry is defined

  There is no more than a 'domain' entry in any ' / /etc/resolv.conf ' file

  All nodes have the same 'domain' entry defined in the file "/ /etc/resolv.conf.

  If control search entry in the file "/ /etc/resolv.conf ' is constant in knots...

  Check the file "/ /etc/resolv.conf ' to ensure that research that one entry is defined

  Several topics 'research' does not exist in any ' / /etc/resolv.conf ' file

  All nodes have the same order of 'search' defined in the file "/ /etc/resolv.conf.

  Checking the time of DNS response for an unreachable node

  Status of node name

  ------------------------------------  ------------------------

  orac1 spent

  orac2 spent

  The time of DNS response for an unreachable node is consistent with the acceptable limit on all nodes

  Check the integrity of the file "/ /etc/resolv.conf ' past

  Check: consistency of zone

  Result: the zone past consistency check

  Verifying the integrity of the name service switch configuration file ' / /etc/nsswitch.conf '...

  Check if "hosts" entry in the file "/ /etc/nsswitch.conf" is consistent in all nodes...

  Check the file "/ /etc/nsswitch.conf" to ensure that the single entry "hosts" is set

  More of an entry "hosts" does not none "/ /etc/nsswitch.conf ' file

  All nodes have even entered 'hosts' defined in the file "/ /etc/nsswitch.conf.

  Check the integrity of the name service switch configuration file ' / /etc/nsswitch.conf ' past

  Control the demon "avahi-daemon" is not configured and running

  Check: Daemon "avahi-daemon' not configured

  Name of the configured node status

  ------------  ------------------------  ------------------------

  orac2 Yes failed

  orac1 Yes failed

  Demon not configured has no process "avahi-daemon."

  Check: Daemon "avahi-daemon" does not

  Node name race?                  Status

  ------------  ------------------------  ------------------------

  orac2 Yes failed

  orac1 Yes failed

  Demon of the control does not have to process "avahi-daemon" works not

  From check for/dev/SHM mounted as a temporary file system...

  Check for/dev/shm mounted as a temporary last file system

  ******************************************************************************************

  Here is a list of pre-requisites fixable chose to fix at this session

  ******************************************************************************************

  --------------                ---------------     ----------------

  Check has failed.                 Failed on nodes of reboot needed?

  --------------                ---------------     ----------------

  Limit: maximum orac2 opened, orac1 not

  file descriptors

  The soft limit: maximum user orac2, orac1 not

  process

  Demon 'avahi-daemon' not orac2, orac1 not

  configured and running

  Run "/ tmp/CVU_12.1.0.1.0_grid/runfixup.sh" as root user on the nodes 'orac1, orac2' to perform correcting operations manually

  Press the ENTER key to continue after execution of ' / tmp/CVU_12.1.0.1.0_grid/runfixup.sh ' has finished on the nodes 'orac1, orac2 '.

  FIX: Strict limit: file descriptors open maximum

  Status of node name

  ------------------------------------  ------------------------

  orac2 failed

  orac1 failed

  ERROR:

  GLWB-9023: manual fixed command "/ tmp/CVU_12.1.0.1.0_grid/runfixup.sh" has been issued by the superuser on the node 'orac2 '.

  GLWB-9023: manual fixed command "/ tmp/CVU_12.1.0.1.0_grid/runfixup.sh" has been issued by the superuser on the node 'orac1 '.

  Result: "strict limit: file descriptors open maximum" could be fixed on nodes 'orac2, orac1 '.

  FIX: Soft limit: maximum user process

  Status of node name

  ------------------------------------  ------------------------

  orac2 failed

  orac1 failed

  ERROR:

  GLWB-9023: manual fixed command "/ tmp/CVU_12.1.0.1.0_grid/runfixup.sh" has been issued by the superuser on the node 'orac2 '.

  GLWB-9023: manual fixed command "/ tmp/CVU_12.1.0.1.0_grid/runfixup.sh" has been issued by the superuser on the node 'orac1 '.

  Result: "soft limit: maximum user process" could be fixed on nodes 'orac2, orac1 '.

  FIX: Daemon "avahi-daemon' not configured and running

  Status of node name

  ------------------------------------  ------------------------

  orac2 failed

  orac1 failed

  ERROR:

  GLWB-9023: manual fixed command "/ tmp/CVU_12.1.0.1.0_grid/runfixup.sh" has been issued by the superuser on the node 'orac2 '.

  GLWB-9023: manual fixed command "/ tmp/CVU_12.1.0.1.0_grid/runfixup.sh" has been issued by the superuser on the node 'orac1 '.

  Result: "Demon"avahi-daemon' not configured and running"could not set on the nodes 'orac2, orac1 '.

  Difficult operations for some prerequisites fixable failed nodes 'orac2, orac1 '.

  Check prior to the installation of cluster service failed on all nodes.

  SOLVED!

  The root cause was in iptables service works.

  Just forgot to arrest him and take off chkconfig!

  Issue can be closed.

• For the Stratus file replication latency

  Hi all

  
  I have create a component of contorlling and desktop sharing to online meeting request. I have test Adobe Stratus multicast and realized that there is a high 5-8 secons latency. If I would use the replication of the object or the Direct routing - would there be the same latency as multicast?

  Best regards and thanks for your time,.

  Marc

  object replication latency will be probably even higher than that.  In addition, the replication of the object sync settings cannot be tuned to ActionScript, but those multicast can.

  5-8 seconds is the latency expected for multicast with the settings default for the length of the window, period of extraction, etc.  These parameters can be adjusted to ActionScript, but right now we don't have any indication on how to do it.

• IMAQdx timeout with camera JAI multicast

  We have a JAI camera connected to a GigE card, displaying the image in a LabVIEW program, and it has worked reliably for months.  We would now like to save the image for short periods of time as well.  We have added a second computer on the GigE network to capture and save the image with a dedicated software stream.  We put the camera JAI multicast so that both computers receive the same image.  Now, we're getting timeout errors in the LabVIEW program: error-1074360293 to IMAQdx to Image.vi.  Increase the length of the timeout to 10 seconds (default is 5) has not helped.  No idea why IMAQdx does not multicast, but works correctly in unicast?  Y at - it a setting I missed?

  Hi nathand.

  It seems IMAQdx 3.9 added a bug that will leave multicast mode not working correctly (the camera is silently configured for unicast in some cases mode - Interior CAR # 318906). Can you confirm if you use this version, or if you use an earlier version? If you say it works for a little while but fails, I guess it's _not_ this bug.

  Do you know what type of switch you use between the camera and the two PC? If it is a managed switch he may use IGMP snooping to determine which of your interfaces is listening for multicast addresses. It is possible that a bug in implementation of this Protocol switch can cause the association to give up after a while. You may disable this Snooping and either assign manually multicast addresses are transmitted or move it to all ports.

  Eric

• Problems with multicast UDP passage from 2009 to 2010

  I have Windows 7 laptop computers of switching and reclassification of LABVIEW, LABVIEW 2010 2009. One of the vi, I developed in 2009 works fine on the old laptop, but with the new laptop and LABVIEW 2010 the UDP Multicast open read-only block throws error 59: the network is down, unreachable, or has been reset. The entries in the UDP Multicast Open are multicast addr: "224.0.0.1" (converted to an IP address with a chain of blocked IP addresses: 3758096385) and port: 20103.

  I can monitor the UDP traffic with wireshark and check that everything works correctly. I can even run the old system at the same time without any problem, but the new system gets error 59. I checked all network settings, including turning off the windows firewall.

  Anyone know of any questions that I might have missed?

  Try to build an EXE file of the machine running on the machine of 2010 and 2009.

  If it works OK, then the problem on the side of the barrier LabVIEW, if it fails, then it's a Windows problem.

  "Unreachable" almost always means a problem of installation of the system.

• Several VPN GET with Multicast clouds

  Hi all

  It is a recommended approach to use different multicast addresses if you use a key server to manage several groups GET VPN? It is not a provider environment hosted service but just for one customer in need of a logical separation.

  I think it would be a good idea to do it, but I'm not very familiar with multicasting on a set, so I would appreciate anyone sharing similar experiences or the potential pitfalls with this config. Is there something I need to watch out for?

  Xavier

  Xavier,

  given that we can separate the information at the level of the GDOI groups you should not need to use multiple addresses.

  However consider a scenario in which a GM is part of Group 1, but not in Group 2. He will receive discount at the key for both, but will not be able to understand group2 generate a new key, you will see the log messages that signals a problem once per hour.

  It makes sense to separate the addresses mcast especially if this deployment could grow/fork/expand in the future.

  M.

• How to detect 'real' rates to send to peers with the help of multicast?

  Hello, everyone.

  I have a question, I try the demo with

  http://www.Adobe.com/devnet/flashmediaserver/articles/p2p_rtmfp_groups.html

  and then I try to find the 'real' rate of sending data to peer with using multicast.

  I set a timer and it will work every second what app start with "_incomingSteam" (videopodcast )

  and I followed NetGroup.info and NetStream.multicast.info (_imcomingStream.multicast.info).

  who is the real rate outstream when Subscriber send video footage of other peers?
  

  multicastInfo.sendControlBytesPerSecond
  multicastInfo.sendDataBytesPerSecond
  multicastInfo.bytesPushedFromPeers
  multicastInfo.bytesPushedToPeers
  multicastInfo.bytesRequestedByPeers
  multicastInfo.bytesRequestedFromPeers

  Is sendDataBytesPerSecond or bytesPushedToPeers or?

  someone could help me?

  HOPE EVERYONE HAVE A GOOD DAY

  It depends on what you mean by 'real' rate of sending data to peers.

  "sendDataBytesPerSecond" represents the payload data rate, the real info sent.

  "sendControlBytesPerSecond" represents the flow of flight data that would be headers, control messages, etc.

  Sum of the 2 above should give you a measure of the 'outbound' peers; -What are you looking for?