Nexus 1000v - change of layer 2 to Layer 3 area transportation

Similar Questions

• Nexus 1000v - a pair of VSMs by cluster?

  Hello

  I'll start migrating some of our groups to Nexus 1000v pretty soon. The environment consists of two data centers at least 2 groups in each SC. In total, we have 5 clusters in different places.

  I plan on the deployment of the N1Kv in pairs for HA. Do I need a pair of N1Kv by cluster, or can I use the same for the different clusters?

  Thank you

  If this post was useful/solved your problem, please mark the points of wire and price as seem you. Thank you!

  I would deffinitely go with multiple VSM in a scenario HA. You mention different places and several clusters by DC. Here's what I'd do.

  First a Nexus 1000v VSM gets tied to a domain controller from VMware. You can have a Nexus 1000V manage multiple clusters as long as they are under the same VMware domain controller. You can add up to 64 ESX host to a single Nexus 1000V VSM.

  So I do a VSM HA pair by DC and did manage multiple clusters. If your clusters have a large number of ESX host it might make sense to use two independent installations of 1000V Nexus by DC. When I say large I mean 32 hosts per cluster.

  When you say that the clusters are in several places. I take that to mean different physical data centers. In this case I highly recommend that you install a Nexus 1000V at each location.

  Louis

• VMware and Nexus internal support for layer 2 priority vSwitch (802.1 p)?

  Hello

  Can someone provide a definitive answer on whether different types of vSwitch manage layer 2 priority internally (i.e. 802.1 p).  In other words, these switches internally generate queues waiting seprate, based on the received priority tag 802,1 p, then manage each of these queues at the specified priority (highest priority first transmitted). Or what's a queue internal so efectively not a priority within the vSwitch, just from any external switch (physical) marking in the path.

  Interested in the answer for each of: standard vSwitch, Distributed vSwitch, Nexus vSwitch.  In vSphere 5 and above.

  I asked similar questions before, and no real clear answer.  Apologies if I've simply not spotted, but I searched the docs of VMware and Nexus and of course google pretty bad too.

  Thanks for the answers or pointers,

  PeterB

  The Nexus 1000v using CB - WFQ

  With Cisco Nexus 1000V Series Switches Release 4.2 (1) SV1 (4) or more recent, virtualization environments can now also enjoy based on a class of weighted Fair Queuing for congestion management.

  Here is a white paper.

  http://www.Cisco.com/en/us/prod/collateral/switches/ps9441/ps9902/white_paper_c11-704041.html

• How change 1010 Nexus and Nexus 1000v IP address

  Hi Experts,

  We run two VSM and a NAM in the Nexus 1010. The version of Nexus 1010 is 4.2.1.SP1.4. And the Nexus 1000v version is 4.0.4.SV1.3c. Now we need to change the IP address of management in the other. Where can I find the model SOP or config? And nothing I need to remember?

  If it is only the mgmt0 you IP address change, you can simply enter the new address under the mgmt0 interface. It automatically syncs with the VC.

  I guess you are trying to change the IP address of the VC and the management VLAN. One way to do this is:

  -From the Nexus 1000v, disconnect the connection to the VC (connection svs-> without logging)

  -Change the IP address of the VC and connect (connection-> remote ip address svs)

  -Change the address for mgmt0 Nexus 1000v

  -Change the mgmt VLAN on the 1010

  -Change the address of the 1010 mgmt

  -Reconnect the Nexus 1000v to VC (connection-> connect svs)

  Therefore, to change the configuration of VLANS on the switch upstream, more connection to the VC as well.

  Thank you

  Shankar

• Change the maximum number of ports on Nexus 1000v vDS online with no distribution?

  Hello

  Change the maximum number of ports on Nexus 1000v vDS online with no distribution?

  
  

  I'm sure that's what the link

  VMware KB: Increase in the maximum number of vNetwork Distributed Switch (vDS) ports in vSphere 4.x

  not to say that

  I have 5.1 ESXi and vcenter

  Thank you
  Saami

  There is no downtime when you change quantity "vmware max-ports" a port profile. It can be done during production.

  You can also create a new profile of port with a test of the virtual machine and change the "vmware max-ports' If you want warm and ferrets.

• Change the layer containing

  I want to change a layer containing for any given layer. More generally, the layers of N relative to a containing layer. How can I do this?

  Hi Nik Ska,

  do you mean something like this?

  // LayersToSublayers.jsx
  
  // https://forums.adobe.com/thread/1620567
  // quick&dirty (but only for the first top level layer)
  // use it on your own risk
  // regards pixxxelschubser
  var aDoc = app.activeDocument;
  var theLayers = aDoc.layers;
  var newTopLevel = aDoc.layers.add();
  newTopLevel.name = "Top level"
  
  var sublayer = newTopLevel.layers.add();
  sublayer.name = theLayers[1].name;
  theLayers[1].visible = true;
  theLayers[1].locked = false;
  
  pI = theLayers[1].pageItems;
  
  for (k=pI.length-1; k>=0;k--) {
  pI[k].visible = true;
  pI[k].locked = false;
  pI[k].move(sublayer, ElementPlacement.PLACEATBEGINNING);
  }
  
  // remove the empty layer
  theLayers[1].remove();
  

  Note: all page elements will be visible and unlocked

  

  

  Have fun

  (Otherwise the two screenshots of your palette layers please (before and after))

• change the layer blending mode

  Im having real trouble, trying to change a layer by the linear burn blend mode.

  so far, ive got:

  var currentComp = app.project.item (i);

  var occLayer = currentComp.layer ("OliveOccLayer");

  currentComp.occLayer.BendingMode.LINEAR_BURN;

  Why this is not working, is anyone knows?

  Thanks, Sam

  Try changing the last line to this:

  occLayer.blendingMode = BendingMode.LINEAR_BURN;

  Dan

• Photoshop CS5 x 64 crash when changing the layer styles

  Hey there,

  I searched and searched through the entire interweb, but almost no one seems to have never had such a problem, so I think it is the right place to ask and hope to be helped . Short version is: Photoshop CS5 (x 64) is constantly crashing when you change a layer style.

  Recently, I installed my CS5 Design Premium on a new laptop (Fujitsu Lifebook AH351) and I have serious problems with Photoshop CS5. On the first run, everything was fine, and he keep like this for a while. Now every time I try to edit a layer style Photoshop crashes immediately. I did not need to change anything, just open the layer style, press OK and Photoshop has disappeared. I can work around by resetting the preferences that works until the next reboot, no matter if I change anything on the settings or not. Tried this on the initial version of the PS and the last update (12.0.4). Once I have reset settings yet, I can work again on the layer styles. Any of you have a similar problem or an allusion to what I could look at?

  The Lifebook has of a decent feature which I think somehow the culprit in this case: it has an on-board graphics unit and a separate GPU (nVidia GForce GT 525 M) that can be added in on a program basis. Indeed, Photoshop recognizes and allows me to enable the OpenGL functions as well, so from there, it seems. The internal GPU cannot be disabled because connect you your monitors.

  Some data on my system:

  Fujitsu Lifebook AH531

  • Intel® Core™ i5 - 2410M
  • RAM: 8 GB DDR3 1333 MHz
  • 750 GB SATA HDD 5400 U/Min
  • Windows 7 Home Premium x 64 (updated)
  • NVIDIA® GeForce® GT 525M with 1 GB of VRAM

  Photoshop CS5 x 64
  

  • no plugins to use/install
  • any settings not changed, not even shortcuts

  Thanks in advance

  enoversum
  

  WindowBlinds was probably to blame.  It's a bad app that changes the window settings and made generally bad things for the environment of the user interface to achieve a different look.

  There may be more options for things you can do (bad) to Windows, such as the screws of the metric of the display with the software from StarDock, simply because Windows is more popular - but if you don't about frivolous things with your system it can be as clean and steady work as a Mac system , if not better.  Mac have many of their own problems.

  -Christmas

• Design/implementation of Nexus 1000V

  Hi team,

  I have a premium partner who is an ATP on Data Center Unified Computing. He has posted this question, I hope you can help me to provide the resolution.

  I have questions about nexus 1KV design/implementation:

  -How to migrate virtual switches often to vswitch0 (in each ESX server has 3 vswitches and the VMS installation wizard will only migrate vswicht0)? for example, to other vswitchs with other vlan... Please tell me how...
  -With MUV (vmware update manager) can install modules of MEC in ESX servers? or install VEM manually on each ESX Server?
  -Assuming VUM install all modules of MEC, MEC (vib package) version is automatically compatible with the version of vmware are?
  -is the need to create port of PACKET-CONTROL groups in all THE esx servers before migrating to Nexus 1000? or only the VEM installation is enough?
  -According to the manual Cisco VSM can participate in VMOTION, but, how?... What is the recommendation? When the primary virtual machines are moving, the secondary VSM take control? This is the case with connectivity to all virtual machines?
  -When there are two clusters in a vmware vcenter, how to install/configure VSM?
  -For the concepts of high availability, which is the best choice of design of nexus? in view of the characteristics of vmware (FT, DRS, VMOTION, Cluster)
  -How to migrate port group existing Kernel to nexus iSCSI?... What are the steps? cisco manual "Migration from VMware to Cisco Nexus 1000V vSwitch" show how to generate the port profile, but
  How to create iSCSI target? (ip address, the username/password)... where it is defined?
  -Assuming that VEM licenses is not enough for all the ESX servers, ¿will happen to connectivity of your virtual machines on hosts without licenses VEM? can work with vmware vswitches?

  I have to install nexus 1000V in vmware with VDI plataform, with multiple ESX servers, with 3 vswitch on each ESX Server, with several machinne virtual running, two groups defined with active vmotion and DRS and the iSCSI storage Center

  I have several manuals Cisco on nexus, but I see special attention in our facilities, migration options is not a broad question, you you have 'success stories' or customers experiences of implementation with migration with nexus?

  Thank you in advance.

  Jojo Santos

  Cisco partner Helpline presales

  Thanks for the questions of Jojo, but this question of type 1000v is better for the Nexus 1000v forum:

  https://www.myciscocommunity.com/Community/products/nexus1000v

  Answers online.  I suggest you just go in a Guides began to acquire a solid understanding of database concepts & operations prior to deployment.

  jojsanto wrote:
  Hi Team,
  I have a premium partner who is an ATP on Data Center Unified Computing. He posted this question, hopefully you can help me provide resolution.
  I have questions about nexus 1KV design/implementation:
  -How migrate virtual switchs distint to vswitch0 (in each ESX server has 3 vswitches and the installation wizard of VMS only migrate vswicht0)?? for example others vswitchs with others vlan.. please tell me how...
  [Robert] After your initial installation you can easily migrate all VMs within the same vSwitch Port Group at the same time using the Network Migration Wizard.  Simply go to Home - Inventory - Networking, right click on the 1000v DVS and select "Migrate Virtual Machine Networking..."   Follow the wizard to select your Source (vSwitch Port Groups) & Destination DVS Port Profiles
  -With VUM (vmware update manager) is possible install VEM modules in ESX Servers ??? or must install VEM manually in each ESX Server?
  [Robert] As per the Getting Started & Installation guides, you can use either VUM or manual installation method for VEM software install.
  http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_0_4_s_v_1_3/getting_started/configuration/guide/n1000v_gsg.html
  -Supposing of VUM install all VEM modules, the VEM version (vib package) is automatically compatible with build existen vmware version?
  [Robert] Yes.  Assuming VMware has added all the latest VEM software to their online repository, VUM will be able to pull down & install the correct one automatically.
  
  
  -is need to create PACKET-MANAGEMENT-CONTROL port groups in ALL esx servers before to migrate to Nexus 1000? or only VEM installation is enough???
  [Robert] If you're planning on keeping the 1000v VSM on vSwitches (rather than migrating itself to the 1000v) then you'll need the Control/Mgmt/Packet port groups on each host you ever plan on running/hosting the VSM on.  If you create the VSM port group on the 1000v DVS, then they will automatically exist on all hosts that are part of the DVS.
  -According to the Cisco manuals VSM can participate in VMOTION, but, how? .. what is the recommendation?..when the primary VMS is moving, the secondary VSM take control?? that occurs with connectivity in all virtual machines?
  [Robert] Since a VMotion does not really impact connectivity for a significant amount of time, the VSM can be easily VMotioned around even if its a single Standalone deployment.  Just like you can vMotion vCenter (which manages the actual task) you can also Vmotion a standalone or redundant VSM without problems.  No special considerations here other than usual VMotion pre-reqs.
  -When there two clusters in one vmware vcenter, how must install/configure VSM?
  [Robert] No different.  The only consideration that changes "how" you install a VSM is a vCenter with multiple DanaCenters. VEM hosts can only connect to a VSM that reside within the same DC.  Different clusters are not a problem.
  -For High Availability concepts, wich is the best choices of design of nexus? considering vmware features (FT,DRS, VMOTION, Cluster)
  [Robert] There are multiple "Best Practice" designs which discuss this in great detail.  I've attached a draft doc one on this thread. A public one will be available in the coming month. Some points to consider is that you do not need FT.  FT is still maturing, and since you can deploy redundany VSMs at no additional cost, there's no need for it.  For DRS you'll want to create a DRS Rule to avoid ever hosting the Primar & Secondary VSM on the same host.
  -How to migrate existent Kernel iSCSI port group to nexus? .. what are the steps? in cisco manual"Migration from VMware vSwitch to Cisco Nexus 1000V" show how to generate the port-profile, but
  
      how to create the iSCSI target? (ip address, user/password) ..where is it defined?
  [Robert] You can migrate any VMKernel port from vCenter by selecting a host, go to the Networking Configuration - DVS and select Manage Virtual Adapters - Migrate Existing Virtual Adapter. Then follow the wizard.  Before you do so, create the corresponding vEth Port Profile on your 1000v, assign appropriate VLAN etc.  All VMKernel IPs are set within vCenter, 1000v is Layer 2 only, we don't assign Layer 3 addresses to virtual ports (other than Mgmt).  All the rest of the iSCSI configuration is done via vCenter - Storage Adapters as usual (for Targets, CHAP Authentication etc)
  -Supposing of the licences of VEM is not enough for all ESX servers,, ¿will happen to the connectivity of your virtual machines in hosts without VEM licences? ¿can operate with vmware vswitches?
  [Robert] When a VEM comes online with the DVS, if there are not enough available licensses to license EVERY socket, the VEM will show as unlicensed.  Without a license, the virtual ports will not come up.  You should closely watch your licenses using the "show license usage" and "show license usage " for detailed allocation information.  At any time a VEM can still utilize a vSwitch - with or without 1000v licenses, assuming you still have adapters attached to the vSwitches as uplinks.
  I must install nexus 1000V in vmware plataform with VDI, with severals Servers ESX, with 3 vswitch on each ESX Server, with severals virtual machinne running, two clusters defined with vmotion and DRS active and central storage with iSCSI
  I have severals cisco manuals about nexus, but i see special focus in installations topics, the options for migrations is not extensive item, ¿do you have "success stories" or customers experiences of implementation with migrations with nexus?
  [Robert] Have a good look around the Nexus 1000v community Forum.   Lots of stories and information you may find helpful.
  Good luck!
  

• Cisco Nexus 1000v switch

  Hi, I have 2 questions about the Switch Cisco Nexus 1000v.

  First of all, why use it rather than the standard vswitch distributed?

  Second, if an environment currently works using distributed vswitches, what are the impacts and the problems likely to introduce a Switch Cisco Nexus 1000v? Is there a process for the upgrade?

  See you soon

  Here is a comparison for the most up-to-date between the optioins network:

  http://www.Cisco.com/en/us/prod/collateral/switches/ps9441/ps9902/solution_overview_c22-526262.PDF

  The great driver with most of the people running the 1000v I talked to is give visibility to the network team and streamlining changes made to the virtual network environment. In a great organazation with a network operations team, they will create an IVR to route a new VLAN, and then create the new VLAN on all switches distribution and access in the area of layer 2, just 1000v allows them to move forward and it create on the hypervisor using a set of commands that they already know.

• Configuring network DMZ, internal using Nexus 1000v

  Hello peoples, this is my first post in the forums.

  I am trying to build a profile for my customer with the following configuration;

  4 x ESXi hosts on the DL380 G7 each with 12 GB of RAM, CPU Core X 5650 of 2 x 6, 8 x 1 GB NIC

  2 x left iSCSI SAN.

  The hardware components and several design features, on that I have no control, they were decided and I can't change, or I can't add additional equipment. Here's my constraints;

  (1) the solution will use the shared for internal, external traffic and iSCSI Cisco network switches.

  (2) the solution uses a single cluster with each of the four hosts within that group.

  (3) I install and configure a Nexus 1000v in the environment (something I'm not want simply because I have never done it before). The customer was sold on the concept of a solution of cheap hardware and shared because they were told that using a N1Kv would solve all the problems of security.

  Before I learned that I would have to use a N1Kv my solution looked like the following attached JPG. The solution used four distributed virtual switches and examples of how they were going to be configured is attached. Details and IP addresses are examples.

  My questions are:

  (1) what procedure should I use to set up the environment, should I build the dvSwtiches as described and then export it to the N1Kv?

  (2) how should I document place this solution? In general in my description I will have a section explaining each switch, how it is configured, vital details, port groups etc. But all of this is removed and replaced with uplink ports or something is it not?

  (3) should I be aiming to use a different switch by dvSwitch, or I can stem the heap and create groups of different ports, is it safe, is there a standard? Yes, I read the white papers on the DMZ and the Nexus 1000v.

  (4) is my configuration safe and effective? Are there ways to improve it?

  All other comments and suggestions are welcome.

  Hello and welcome to the forums,

  (1) what procedure should I use to set up the environment, should I build the dvSwtiches as described and then export it to the N1Kv?

  N1KV replace dvSwitch, but there isn't that a N1KV ONLY where there are many dvSwitches N1KV would use the same rising in the world.

  (2) how should I document place this solution? In general in my description I will have a section explaining each switch, how it is configured, vital details, port groups etc. But all of this is removed and replaced with uplink ports or something is it not?

  If you use N1KV you rising the pSwitch to the N1KV.

  If you use dvSwitch/vSwitch you uplink to the pSwitches to the individual dvSwitch/vSwitch in use.

  (3) should I be aiming to use a different switch by dvSwitch, or I can stem the heap and create groups of different ports, is it safe, is there a standard? Yes, I read the white papers on the DMZ and the Nexus 1000v.

  No standard and Yes in many cases, it can be considered secure. If your existing physical network relies on VLANs and approves the Layer2 pSwitches, then you can do the exact same thing in the virtual environment and be as safe as your physical environment.

  However, if you need separation to the layer of pSwitch then you must maintain various vSwitches for this same separation. Take a look at this post http://www.virtualizationpractice.com/blog/?p=4284 on the subject.

  (4) is my configuration safe and effective? Are there ways to improve it?

  Always ways to improve. I would like to start looking into the defense-in-depth the vNIC and layers of edge within your vNetwork.

  Best regards
  Edward L. Haletky VMware communities user moderator, VMware vExpert 2009, 2010

  Now available: url = http://www.astroarch.com/wiki/index.php/VMware_Virtual_Infrastructure_Security'VMware vSphere (TM) and Virtual Infrastructure Security' [/ URL]

  Also available url = http://www.astroarch.com/wiki/index.php/VMWare_ESX_Server_in_the_Enterprise"VMWare ESX Server in the enterprise" [url]

  Blogs: url = http://www.virtualizationpractice.comvirtualization practice [/ URL] | URL = http://www.astroarch.com/blog Blue Gears [url] | URL = http://itknowledgeexchange.techtarget.com/virtualization-pro/ TechTarget [url] | URL = http://www.networkworld.com/community/haletky Global network [url]

  Podcast: url = http://www.astroarch.com/wiki/index.php/Virtualization_Security_Round_Table_Podcastvirtualization security Table round Podcast [url] | Twitter: url = http://www.twitter.com/TexiwillTexiwll [/ URL]

• iSCSI MPIO (Multipath) with Nexus 1000v

  Anyone out there have iSCSI MPIO successfully with Nexus 1000v? I followed the Cisco's Guide to the best of my knowledge and I tried a number of other configurations without success - vSphere always displays the same number of paths as it shows the targets.

  The Cisco document reads as follows:

  Before you begin the procedures in this section, you must know or follow these steps.

  •You have already configured the host with the channel with a port that includes two or more physical network cards.

  •You have already created the VMware kernel NIC to access the external SAN storage.

  •A Vmware Kernel NIC can be pinned or assigned to a physical network card.

  •A physical NETWORK card may have several cards pinned VMware core network or assigned.

  That means 'a core of Vmware NIC can be pinned or assigned to a physical NIC' average regarding the Nexus 1000v? I know how to pin a physical NIC with vDS standard, but how does it work with 1000v? The only thing associated with "pin" I could find inside 1000v was with port channel subgroups. I tried to create a channel of port with manuals subgroups, assigning values of sub-sub-group-id for each uplink, then assign an id pinned to my two VMkernel port profiles (and directly to ports vEthernet as well). But that doesn't seem to work for me

  I can ping both the iSCSI ports VMkernel from the switch upstream and inside the VSM, so I know Layer 3 connectivity is here. A strange thing, however, is that I see only one of the two addresses MAC VMkernel related on the switch upstream. Both addresses show depending on the inside of the VSM.

  What I'm missing here?

  Just to close the loop in case someone stumbles across this thread.

  In fact, it is a bug on the Cisco Nexus 1000v. The bug is only relevant to the ESX host that have been fixed in 4.0u2 (and now 4.1). Around short term work is again rev to 4.0u1. Medium-term correction will be integrated into a maintenance for the Nexus 1000V version.

  Our implementation of code to get the multipath iSCSI news was bad but allowed in 4.0U1. 4.0U2 no longer our poor implementation.

  For iSCSI multipath and N1KV remain 4.0U1 until we have a version of maintenance for the Nexus 1000V

• Nexus 1000v, UCS, and Microsoft NETWORK load balancing

  Hi all

  I have a client that implements a new Exchange 2010 environment. They have an obligation to configure load balancing for Client Access servers. The environment consists of VMware vShpere running on top of Cisco UCS blades with the Nexus 1000v dvSwitch.

  Everything I've read so far indicates that I must do the following:

  1 configure MS in Multicast mode load balancing (by selecting the IGMP protocol option).

  2. create a static ARP entry for the address of virtual cluster on the router for the subnet of the server.

  3. (maybe) configure a static MAC table entry on the router for the subnet of the server.

  3. (maybe) to disable the IGMP snooping on the VLAN appropriate in the Nexus 1000v.

  My questions are:

  1. any person running successfully a similar configuration?

  2 are there missing steps in the list above, or I shouldn't do?

  3. If I am disabling the snooping IGMP on the Nexus 1000v should I also disable it on the fabric of UCS interconnections and router?

  Thanks a lot for your time,.

  Aaron

  Aaron,

  The steps above you are correct, you need steps 1-4 to operate correctly.  Normally people will create a VLAN separate to their interfaces NLB/subnet, to prevent floods mcast uncessisary frameworks within the network.

  To answer your questions

  (1) I saw multiple clients run this configuration

  (2) the steps you are correct

  (3) you can't toggle the on UCS IGMP snooping.  It is enabled by default and not a configurable option.  There is no need to change anything within the UCS regarding MS NLB with the above procedure.  FYI - the ability to disable/enable the snooping IGMP on UCS is scheduled for a next version 2.1.

  
  
  This is the correct method untill the time we have the option of configuring static multicast mac entries on
  
  the Nexus 1000v.  If this is a feature you'd like, please open a TAC case and request for bug CSCtb93725 to be linked to your SR.
  
  This will give more "push" to our develpment team to prioritize this request.
  Hopefully some other customers can share their experience.
  Regards,

  Robert

• VXLAN on UCS: IGMP with Catalyst 3750, 5548 Nexus, Nexus 1000V

  Hello team,

  My lab consists of Catalyst 3750 with SVI acting as the router, 5548 Nexus in the vpc Setup, UCS in end-host Mode and Nexus 1000V with segmentation feature enabled (VXLAN).

  I have two different VLAN for VXLAN (140, 141) to demonstrate connectivity across the L3.

  VMKernel on VLAN 140 guests join the multicast fine group.

  Hosts with VMKernel on 141 VLAN do not join the multicast group.  Then, VMs on these hosts cannot virtual computers ping hosts on the local network VIRTUAL 140, and they can't even ping each other.

  I turned on debug ip igmp on the L3 Switch, and the result indicates a timeout when he is waiting for a report from 141 VLAN:

  15 Oct 08:57:34.201: IGMP (0): send requests General v2 on Vlan140

  15 Oct 08:57:34.201: IGMP (0): set the report interval to 3.6 seconds for 224.0.1.40 on Vlan140

  15 Oct 08:57:36.886: IGMP (0): receipt v2 report on 172.16.66.2 to 239.1.1.1 Vlan140

  15 Oct 08:57:36.886: IGMP (0): group record received for group 239.1.1.1, mode 2 from 172.16.66.2 to 0 sources

  15 Oct 08:57:36.886: IGMP (0): update EXCLUDE group 239.1.1.1 timer

  15 Oct 08:57:36.886: IGMP (0): add/update Vlan140 MRT for (*, 239.1.1.1) 0

  15 Oct 08:57:38.270: IGMP (0): send report v2 for 224.0.1.40 on Vlan140

  15 Oct 08:57:38.270: IGMP (0): receipt v2 report on Vlan140 of 172.16.66.1 for 224.0.1.40

  15 Oct 08:57:38.270: IGMP (0): group record received for group 224.0.1.40, mode 2 from 172.16.66.1 to 0 sources

  15 Oct 08:57:38.270: IGMP (0): update EXCLUDE timer group for 224.0.1.40

  15 Oct 08:57:38.270: IGMP (0): add/update Vlan140 MRT for (*, 224.0.1.40) by 0

  15 Oct 08:57:51.464: IGMP (0): send requests General v2 on Vlan141<----- it="" just="" hangs="" here="" until="" timeout="" and="" goes="" back="" to="">

  15 Oct 08:58:35.107: IGMP (0): send requests General v2 on Vlan140

  15 Oct 08:58:35.107: IGMP (0): set the report interval to 0.3 seconds for 224.0.1.40 on Vlan140

  15 Oct 08:58:35.686: IGMP (0): receipt v2 report on 172.16.66.2 to 239.1.1.1 Vlan140

  15 Oct 08:58:35.686: IGMP (0): group record received for group 239.1.1.1, mode 2 from 172.16.66.2 to 0 sources

  15 Oct 08:58:35.686: IGMP (0): update EXCLUDE group 239.1.1.1 timer

  15 Oct 08:58:35.686: IGMP (0): add/update Vlan140 MRT for (*, 239.1.1.1) 0

  If I do a show ip igmp interface, I get the report that there is no joins for vlan 141:

  Vlan140 is up, line protocol is up

  The Internet address is 172.16.66.1/26

  IGMP is enabled on the interface

  Current version of IGMP host is 2

  Current version of IGMP router is 2

  The IGMP query interval is 60 seconds

  Configured IGMP queries interval is 60 seconds

  IGMP querier timeout is 120 seconds

  Configured IGMP querier timeout is 120 seconds

  Query response time is 10 seconds max IGMP

  Number of queries last member is 2

  Last member query response interval is 1000 ms

  Access group incoming IGMP is not defined

  IGMP activity: 2 joints, 0 leaves

  Multicast routing is enabled on the interface

  Threshold multicast TTL is 0

  Multicast designated router (DR) is 172.16.66.1 (this system)

  IGMP querying router is 172.16.66.1 (this system)

  Multicast groups joined by this system (number of users):

  224.0.1.40 (1)

  Vlan141 is up, line protocol is up

  The Internet address is 172.16.66.65/26

  IGMP is enabled on the interface

  Current version of IGMP host is 2

  Current version of IGMP router is 2

  The IGMP query interval is 60 seconds

  Configured IGMP queries interval is 60 seconds

  IGMP querier timeout is 120 seconds

  Configured IGMP querier timeout is 120 seconds

  Query response time is 10 seconds max IGMP

  Number of queries last member is 2

  Last member query response interval is 1000 ms

  Access group incoming IGMP is not defined

  IGMP activity: 0 joins, 0 leaves

  Multicast routing is enabled on the interface

  Threshold multicast TTL is 0

  Multicast designated router (DR) is 172.16.66.65 (this system)

  IGMP querying router is 172.16.66.65 (this system)

  No group multicast joined by this system

  Is there a way to check why the hosts on 141 VLAN are joined not successfully?  port-profile on the 1000V configuration of vlan 140 and vlan 141 rising and vmkernel are identical, except for the different numbers vlan.

  Thank you

  Trevor

  Hi Trevor,

  Once the quick thing to check would be the config igmp for both VLAN.

  where did you configure the interrogator for the vlan 140 and 141?

  are there changes in transport VXLAN crossing routers? If so you would need routing multicast enabled.

  Thank you!

  . / Afonso

• Authentication of connection Cisco AAA to shelf (MS IAS) Nexus 1000v

  Hey

  I have a link, I'll add to my radius for the logon server.

  On a sw IOS, I need to do more

  Number of attribute change to '1 '.
  Set the Format of the attribute to "String".
  Type "shell: priv-lvl = 15" in the value of the attribute field

  But should I put in the "shell", so I'll work on a Nexus 1000v

  Shell: roles = "network-admin".

  (or replace any role to assign the user to network-admin)