Ports of Nexus

Similar Questions

• 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.

• Configure ports on Nexus 5000/2000 for the grouping of network server adapters

  Hello

  I have two Nexus 5000 and Nexus two, 2000.  The 5000 s are peers of vpc.  I would like to connect my server with cluster NIC in a port on each 2000 and all have both be active.  Is this possible?  What are the steps?  I thought it should be this:

  CPR_NEXUS_5K01 (config) # int eth100/1/32

  CPR_NEXUS_5K01(Config-if) # channel - group 32

  CPR_NEXUS_5K01 (config) # int eth101/1/32

  CPR_NEXUS_5K01(Config-if) # channel - group 32

  on the Nexus two.

  Thank you, Jerry

• Configuration of the channel of port on nexus 1000V

  Hello

  I'm new on nexus 1000V, the configuration is as follows, UCS chassis with 4 blades full-width connected to 2 FI 6248UP.

  each FI's uplink to a n5k (no mail ORDER).

  is there any configuration model the nexus 1000v? How to configure port-channel?

  Thank you.

  Hello

  We recommend using mac pinning ("channel-group auto mode on mac - pinning") when N1KV is used on the blades of the UCS.

  Next doc provides good overview on best practices.

  Best practices in deploying Cisco Nexus 1000V switches in the Cisco UCS B and C series series Cisco UCS Manager servers

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

  HTH

  Padma

• Support of virtual channel of Port Cisco Nexus 9300

  Hello

  As I'm new to Nexus 9300 and I was wondering if the switch can support virtual port channel (VPC)? I was wondering if there is any matrix of functionality compared to the 9500/N7Ks/N5Ks

  Any suggestion is appreciated.

  Thank you.

  You can configure VPC on the 9300 series NX - OS mode. The selling point for the Nexus 9 k series is generally well mode of ACI, which would usually be deployed in one focused on the leaf tissue and the topology of the backbone.

  In a fabric that we use equal cost Multipath and don't have a VPC configuration designed to reduce some limitations of the spanning tree in classic Ethernet.

  Take a look at the Cisco Live presentation BRKARC-2222 for a good overview of the architecture and design of Nexus 9 k.

• ESXi 5 and Nexus 1000v

  Hello

  I have an ESXi 5 but only NIC I am migrating the VSS for Nexus 1000v. I installed Nexus VEM correctly and do primary and secondary, VSMs configured uplink port groups all according to the guides from Cisco. When I try to add a host under the link, I have first to migrate the vnic0 for the Group of appropriate uplink ports and it then asks me to migrate the management port (I think it is vmk0) so if I create a group of ports on Nexus to migrate a management port or do not migrate at all I always lose connectivity to ESXi.

  Can someone please share the configs of the Nexus 1000v and how to migrate properly vnic0 and vmk0 (with a single physical NETWORK adapter) so that I do not lose connectivity?

  Thanks in advacne.

  Remi

  control is vlan 152 and package is 153.

  You can make same vlan. We have supported using the same vlan for the control and the package for several years now.

  Louis

• Configuration of uplinks FC UCS

  Hello

  I'm confused on the configuration of the UCS CF uplinks.

  the configuration is the following UCS (2 fabric interconnects - 2 different VSAN)--> Nexus 5 k (2 for redundancy - each FI for Nexus one)--> EMC storage

  I have connected 2 ports CF since the interconnection fabric expansion module to the Nexus 5 K

  I'm confused about the configuration on the port in the nexus 5 K?

  Interconnection of fabric is in Normal mode (not switch mode), how do I configure my port on the nexus? What a F port? should I activate NPV on nexus?

  is - good port of EMC storage as F port (on nexus)?

  I'm still new to FC connectivity.

  I appreciate if you can include a configuration nexus 5K model

  Thank you

  The N5K should be mode Switch FC (in front of the NPV mode).  The FI will be NPV (aka host FC end Mode).

  On the N5K interfaces uplink FI both the EMC connection interfaces will be in mode F.  You must ensure that NPIV is enabled on the N5K (simple change without interruption).  Each FC on your N5K port must be assigned to the appropriate VSANS.  Don't forget to create the VSAN on UCS and the N5Ks respectfully.

  The FC interfaces between the UCS and the N5K must be in the same VSAN (except if you use VSAN trunking) or they will not come to the top.  For even if you want to create a channel of Port CF you do on both sides of the link.

  Once your links are pointing upwards, you need your zoning and masking on the table - including a whole other subject.

  Kind regards

  Robert

• Nexus 7009 does not show the N7K-F248XP-25 modules ethernet ports n sh run

  Hello world

  I have a question...

  I'm going to install two Nexus 7009 with N7K-F248XP-25 three modules on each of them, I plan to create 3 VDC, but initial configuration, the system does not display the Ethernet ports of these modules, even with the inventory of show and show module that I can see that the modules are recognized and its status is OK. Is there something I need to do before you start to configure these modules...? allow some feature or the license in order to see the ports with show running CLI...?

  You can activate the F1, F2, M1, M1XL, and M2XL series modules. There is no restriction on the type of mixture allowed for the order of module-type system. Control module-type system allows a mixture of F1, F2, M1, M1XL and M2XL series of modules in the VDC.

  Note The module-type limit-resource command handles the restrictions on the types of module that can be mixed in the VDC.

  Note Use the f2 type module-system command to allow the F2E series modules in a VDC. The ports of F2 and F2E series modules can be distributed as all other ports.

  Note The modules that you do not select must not be powered on after you configure this feature and enter Yes. An error message will force you to manually disable these modules before you continue. You will avoid significant disruptions and problems of service within a VDC.

  No form of this command resets the configuration mode to enable all modules.

  hope this helps

• Double room Nexus 2348UPQ / Max ports for vPC links

  Hi people,

  Cisco Nexus 2348UPQ has 24 to 10 GB uplink interfaces. Supposedly on the distribution layer, we have a pair of Cisco Nexus 5548UP, how many ports we can group about 2348 for vPC for double-homing links.

  Thank you very much!!!

  Hi Chris,

  Using an Extender of fabric with a Cisco Nexus 5000 and 6000 Series Switch Cisco Nexus

  http://www.Cisco.com/c/en/us/TD/docs/switches/Datacenter/nexus2000/HW/installation/guide/nexus_2000_hig/overview.html#pgfId-1415984

  -If you decide to use the drop cable instead of the 40 G uplinks, please note the following limitation:

  The 2348TQ of Cisco Nexus and Nexus 2348UPQ FEX, if a port channel is used to connect a switch parent with a tissue Expander device, the port channels can have up to 8 ports.

  Nexus 2348 FEX devices have a total of 6 * 40 Gigabit Ethernet uplink ports to the parent switch. If these are used with native port of 40G uplinks on a switch of parent, there is no limitation. 6 ports can be used in a hosted configuration only hosted or double. You can also use 40 Gigabit Ethernet uplink ports on the extensor of N2348 fabric with 10 Gigabit Ethernet ports on the switch to parent when it is used with the appropriate wiring. A maximum of 8 ports can be added to the string of port between the parent switch and the fabric Extender. If it's a double hosted configuration, VPC for the extensor of fabric, only 4 ports per switch are allowed in the channel of the port.

  Cisco Nexus 5600 series NX - OS Layer 2 switching Configuration Guide, version 7.x - configuration of the fabric Extender

  http://www.Cisco.com/c/en/us/TD/docs/switches/Datacenter/nexus5600/SW/Layer2/7x/b_5600_Layer2_Config_7x/b_6k_Layer2_Config_7x_chapter_01110.html

  -SFP support and cables are listed in the Cisco Nexus 2300 platform fabric Extender card (http://www.cisco.com/c/en/us/products/collateral/switches/nexus-2000-series-fabric-extenders/datasheet-c78-731663.html).

  I'd be suspicious of this bug;

  https://Tools.Cisco.com/bugsearch/bug/CSCuu88175/?reffering_site=dumpcr

  "If it's a double configuration hosted, vpc for fex, that only 4 ports per switch are permitted in the Port-Channel"

  HTH,

  Qiese Sa'di

• Nexus 1000v and vmkernel ports

  What is the best practice to put on the nexus 1000v vmkernel ports? Is it a good idea to put all the ports of vms and vmkernel on nexus 1000v? switch or dvs or some vmkernel as management ports must be on a standard?  If something happens to the 1000v, all management and vms will be unreachable.

  any tips?

  Yep, that's correct. Port system profiles don't require any communication between the MEC and VSM.

• Remove the ' system VLAN "Nexus 1000V port-profile

  We have a Dell M1000e blade chassis with a number of Server Blade M605 ESXi 5.0 using the Nexus 1000V for networking.  We use 10 G Ethernet fabric B and C, for a total of 4 10 cards per server.  We do not use the NIC 1 G on A fabric.  We currently use a NIC of B and C fabrics for the traffic of the virtual machine and the other card NETWORK in each fabric for traffic management/vMotion/iSCSI VM.  We currently use iSCSI EqualLogic PS6010 arrays and have two configuration of port-groups with iSCSI connections (a physical NIC vmnic3 and a vmnic5 of NIC physical).

  We have added a unified EMC VNX 5300 table at our facility and we have configured three VLANs extra on our network - two for iSCSI and other for NFS configuration.  We've added added vEthernet port-profiles for the VLAN of new three, but when we added the new vmk # ports on some of the ESXi servers, they couldn't ping anything.   We got a deal of TAC with Cisco and it was determined that only a single port group with iSCSI connections can be bound to a physical uplink both.

  We decided that we would temporarily add the VLAN again to the list of VLANS allowed on the ports of trunk of physical switch currently only used for the traffic of the VM. We need to delete the new VLAN port ethernet-profile current but facing a problem.

  The Nexus 1000V current profile port that must be changed is:

  The DenverMgmtSanUplinks type ethernet port profile

  VMware-port group

  switchport mode trunk

  switchport trunk allowed vlan 2308-2306, 2311-2315

  passive auto channel-group mode

  no downtime

  System vlan 2308-2306, 2311-2315

  MGMT RISING SAN description

  enabled state

  We must remove the list ' system vlan "vlan 2313-2315 in order to remove them from the list" trunk switchport allowed vlan.

  However, when we try to do, we get an error about the port-profile is currently in use:

  vsm21a # conf t

  Enter configuration commands, one per line.  End with CNTL/Z.

  vsm21a (config) #-port ethernet type DenverMgmtSanUplinks profile

  vsm21a(config-port-Prof) # system vlan 2308-2306, 2311-2312

  ERROR: Cannot delete system VLAN, port-profile in use by Po2 interface

  We have 6 ESXi servers connected to this Nexus 1000V.  Originally they were MEC 3-8 but apparently when we made an update of the firmware, they had re - VEM 9-14 and the old 6 VEM and associates of the Channel ports, are orphans.

  By example, if we look at the port-channel 2 more in detail, we see orphans 3 VEM-related sound and it has no ports associated with it:

  Sho vsm21a(config-port-Prof) # run int port-channel 2

  ! Command: show running-config interface port-canal2

  ! Time: Thu Apr 26 18:59:06 2013

  version 4.2 (1) SV2 (1.1)

  interface port-canal2

  inherit port-profile DenverMgmtSanUplinks

  MEC 3

  vsm21a(config-port-Prof) # sho int port-channel 2

  port-canal2 is stopped (no operational member)

  Material: Port Channel, address: 0000.0000.0000 (bia 0000.0000.0000)

  MTU 1500 bytes, BW 100000 Kbit, DLY 10 usec,

  reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ARPA

  Port mode is trunk

  Auto-duplex, 10 Gb/s

  Lighthouse is off

  Input stream control is turned off, output flow control is disabled

  Switchport monitor is off

  Members in this channel: Eth3/4, Eth3/6

  Final cleaning of "show interface" counters never

  102 interface resets

  We can probably remove the port-channel 2, but assumed that the error message on the port-profile in use is cascading on the other channel ports.  We can delete the other port-channel 4,6,8,10 orphans and 12 as they are associated with the orphan VEM, but we expect wil then also get errors on the channels of port 13,15,17,19,21 and 23 who are associated with the MEC assets.

  We are looking to see if there is an easy way to fix this on the MSM, or if we need to break one of the rising physical on each server, connect to a vSS or vDS and migrate all off us so the Nexus 1000V vmkernel ports can clean number VLAN.

  You will not be able to remove the VLAN from the system until nothing by using this port-profile. We are very protective of any vlan that is designated on the system command line vlan.

  You must clean the canals of old port and the old MEC. You can safely do 'no port-channel int' and "no vem" on devices which are no longer used.

  What you can do is to create a new port to link rising profile with the settings you want. Then invert the interfaces in the new port-profile. It is generally easier to create a new one then to attempt to clean and the old port-profile with control panel vlan.

  I would like to make the following steps.

  Create a new port-profile with the settings you want to

  Put the host in if possible maintenance mode

  Pick a network of former N1Kv eth port-profile card

  Add the network adapter in the new N1Kv eth port-profile

  Pull on the second NIC on the old port-profile of eth

  Add the second network card in the new port-profile

  You will get some duplicated packages, error messages, but it should work.

  The other option is to remove the N1Kv host and add it by using the new profile port eth.

  Another option is to leave it. Unless it's really bother you no VMs will be able to use these ports-profile unless you create a port veth profile on this VLAN.

  Louis

• Definition of VLAN ID on vmkernel ports on dVS - Nexus 1000

  I noticed when adding vmkernel ports to a host on the dVS I'm not presented with an option to enter a VLAN ID. Is it because the VLANS is defined at the level of the port on the Nexus Group? Is there a need for me to create these ports on a vSwitch first to set the VLAN and then migrate them to the dVS?

  Thank you

  JD

  The VLAN ID is controlled by the port-profile on the VSMs 1000v. You don't have to specify it.

• Windows does not allow me to update the drivers for my Nexus 7 (USB port)

  I'm having a problem connecting my Nexus 7 compressed (version 2013) to my desktop. I've successfully connected to my laptop. The two computers running Win 7 (64).

  When I plug the USB cable in my office, says Windows is to install the device driver software. After a short interval, it pops up a message saying that the software has not been installed correctly.

  So of course I went on Google Nexus web site and downloaded the latest version of the driver and unzipped the file.

  I opened the Device Manager. The Nexus is not listed, but under "Portable devices", it a "MTP USB Device", which I think will turn out to be the Nexus.

  I right click on this point, then "Update Driver Software", then "Browse my computer...". "and"Search for driver software in this place"(and of course, I've come to the place where my file downloaded and unpacked.

  Click "next".

  INSTANTLY, I have "Windows has determined the driver software for your device is up to date. It seems there being no attempt to load the new driver. I maybe trying to load the drivers in the wrong place?

  FWIW, I checked to see if there are group policies that would prevent Windows update drivers, but there is not. I'm not aware of the problems of updating all drivers.

  I even tried to copy the drivers in my laptop, without success. When the Tablet is connected to my laptop (with success), it appears in device under portable devices-> Nexus management, but this does not happen on the desktop.

  This who should I try next, please?

  Hi TRHD,

  Depending on your answer update, I suggest to run the next fixit and check if it helps.

  Diagnose and automatically fix the Windows USB problems

  Please post back your results for assistance.

• Nexus 5000 ports do not convert in Ethernet

  Greetings. I'm trying to convert Ethernet ports 17-24 of FibreChannel. However, when I run the following commands, this is what happens:

   Aero5K(config)# slot 1 Aero5K(config-slot)# port 17-24 type ethernet ERROR: Invalid Port Range specified

  Here's the relevant current config. I hate usually pasting configs, but in this case, I want to give the answering machine the best chance to tell me my problem.

   version 7.0(5)N1(1) feature fcoe hostname Aero5K feature telnet feature interface-vlan feature lacp feature lldp slot 1 port 17-32 type fc slot 2 vrf context management vsan database vsan 11 name "fabric_aero5k" fcdomain fcid database vsan 11 wwn 50:06:01:60:36:e0:11:66 fcid 0x008400ef dynamic vsan 11 wwn 50:06:01:68:36:e0:11:66 fcid 0x008401ef dynamic interface Vlan1 interface Vlan100 no shutdown ip address 10.0.100.9/24 vsan database vsan 11 interface fc1/17 vsan 11 interface fc1/18 vsan 11 interface fc1/19 vsan 11 interface fc1/20 vsan 11 interface fc1/21 vsan 11 interface fc1/22 vsan 11 interface fc1/23 vsan 11 interface fc1/24 vsan 11 interface fc1/25 vsan 11 interface fc1/26 vsan 11 interface fc1/27 vsan 11 interface fc1/28 vsan 11 interface fc1/29 vsan 11 interface fc1/30 vsan 11 interface fc1/31 vsan 11 interface fc1/32 interface fc1/17 interface fc1/18 interface fc1/19 interface fc1/20 interface fc1/21 interface fc1/22 interface fc1/23 interface fc1/24 interface fc1/25 interface fc1/26 interface fc1/27 interface fc1/28 interface fc1/29 interface fc1/30 interface fc1/31 no shutdown interface fc1/32 no shutdown

  I guess you had ports slot 1 Ethernet 1-16 and 17-32 FC ports!

  Now you want ports 17-24 to become Ethernet as well.

  That's why you need

   port 1-24 type ethernet

• The Cisco Nexus 1000V VSM port group settings?

  I could not find the Group of port settings when executing the VSM in a virtual machine covered in the Cisco documentation... they say just 'create 3 groups of port '.   But, the configuration of VLANS to these pages are not clear to me.

  In the configuration of VSM, you set the VLAN on each network (Mgmnt, control, package).   This means that the VM VSM will be production of marked packets, so groups of port must be set as master / virtual tag comments.

  But, if this is the case, why they recommend 3 groups of ports?  You should be able to use a trunk port group and letting the physical switch the VLAN.  Thus, they rather waiting for assignment of VLAN will be on the Port groups?

  The Cisco config docs give much information on the Cisco command line configuration...  Some may give, or point, the settings on the VMware port groups when using MSM in a virtual machine?

  Hello

  VSM virtual machine generates no marked packets but depends on the configuration of the port group VLAN ID Vswitch to label.  It's done as having evacuated the computer host computer on the vmnic associated the Vswitch.