Bpdguard and nexus portfast

Similar Questions

• OnPlus discovery and Nexus 5548

  Hello

  I just installed an OnPlus agent for a customer who has a Nexus with a 3 layer daugthter card 5548 as their central switch, but the agent is not discovered any device beyond the vlan in which he is sitting.  Does anyone have any experience with the OnPlus ageent and Nexus switches.  It is obviously not a Cisco device supported but I configured IDs connection and snmp access to the switch on the portal, but still nothing is discovered.  Any advice greatly appreciated.

  Concerning

  Ian

  Hi Ian,

  To discover the multi - VLAN, connect the On100 to an 802. 1 q trunk port. This will allow the On100 discover other VLANs. It is currently connected to an access port which is to limit the broadcast traffic of the other VLAN.

  Although the device is not currently supported, he discovered and enable basic support we provide for all detected devices.

  Thank you

  The OnPlus team

• Log InSight can work with Cisco Catalyst and Nexus devices?

  Hi guys,.

  someone at - it use Log Insight for catalyst devices and Nexus?

  Yes, the Insight journal will work with all the unstructured data sent via the syslog Protocol. Support for devices Cisco remote log to a syslog destination shipping as newspaper Insight.

• 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

• Connectivity HP C7000 and Nexus 5000

  We spend our ESX servers in a rack mount environment at C7000 enclosures with blades. Can someone talk about compatibility box blade HP and Nexus 5000? The little that I find seems to suggest that this match may not be 100% ready for primetime.

  I have a HP Virtual Connect modules or exactly what FCoE lokks like with HP blades. Does anyone have more information on this specific vegetables or aware of this configuration, used successfully?

  There is full compatibility between the HP 7000 and the Cisco Nexus 5000.

  What you need to make sure if it is that you are up-to-date with all HP firmware and drivers Nic ESX.

  Take a look on my blog that goes into this in detail:

  http://www.wooditwork.com/2010/08/09/Flex-10-ESX-pre-requisites/

  http://www.wooditwork.com/2011/02/17/Flex-10-ESX-design-with-simplicity-and-scalability-part-1/

  http://www.wooditwork.com/2011/02/17/Flex-10-ESX-design-with-simplicity-and-scalability-part-2/

  http://www.wooditwork.com/2011/02/18/scripting-Flex-10-ESX-design-with-PowerCLI/

  http://www.wooditwork.com/2010/10/19/HP-Virtual-connect-for-the-Cisco-network-administrator/

• Bike 360 and Nexus 4 not matching

  I just bought the bike 360 and expected type of plug-and-play with my Nexus 4 but no way behavior. When they try to pair, Moto 360 disconnects immediately. SmartWatch reset several times but nothing.

  Any idea?

  Thank you!

  Updated the porter Android app and it worked.

  Thank you very much!!!

• Not able to ping from EXSI and NEXUS of EXSI HOST default gateway

  Hello

  In my topology I use 2960 switch thanks to which are connected the my fabric for interconnection and the NEXUS, I am able to ping ESXI switch but when I ping the blade and the Nexus of ESXI HOST, is not ping and also not able to ping default gateway through EXSI.

  I use X Vlan for all devices.

  Please suggest...

  The first thing is to make sure the VLAN ESX is defined from the NETWORK adapter to the router. the 5K the routing in this case? Also the fabric of interconnections and the pool mgmt of blade must be on the same VLAN / subnet. It seems that the FIM is on

  .7/25 and blade MMIC in sur.100/25. They must be on the same subnet. for ESX, please ensure that your vNIC has the VLAN correct represented and that his license.

  Hope this helps,

  David Jarzynka

• 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

• Connectivity between Interconnect and Nexus 2000 fabric options

  Hello

  I would like to know what models of fabric nexus 2000 Extenders can I use if I want to connect them to a pair of interconnections 6248UP fabric in a FEX deployment, so I can move between blade and rack servers service profiles.

  Thanks for your replies.

  Christian

  Christian,

  Take a look at this guide.  It should answer all your questions:

  http://www.Cisco.com/en/us/customer/docs/unified_computing/UCS/c-series_integration/ucsm2.0.2/b_UCSM_202_C-integration.html

  Kind regards

  Robert

• VM - FEX and Nexus 1000v relationship

  Hello

  I'm new in the world of virtulaization and I need to know what the relationship between Cisco Nexus 1000v and Cisco VM - FEX? and when to use VM - FEX and when to use Nexus 1000v.

  Concerning

  Ahmed,

  Nexus 1000v is a Distributed Switch that allows you to manage your VEM, see this relationship as a supervisor-LineCard relationship.

  VM - FEX gives you the opportunity to bypass the vSwitch embarked on each host ESXi (VEM) for example.

  With VM - FEX, you see the virtual machines as if they were directly connected to the Parent switch (N7K / 5K for example), making it the parent spend management (cause there is more no vSwitch in the middle).

  This is a good topic that can be discussed and is difficult to summarize in a few lines, you read something in particular? any questions or doubts we can help clarify?

  -Kenny

• Please tell me how to connect with FCoE mini-UCS and Nexus N5k (N5K-C5548UP-B-S32)

  I have UCS 5108 chassis of Server Blade (with two blades B200 M3 inside and two FI 6324) connected to the switch of Nexus N5k 4x10GE links.

  I want to set both aggregated channels FCoE (vFC) of chassi to pass.

  All the instructions I've seen mention that UCS-mini needs to be mode end-host FC, but version 3.0 UCSM does not support this mode, what should you do?

  I put in place following the www.cisco.com/c/en/us/support/docs/switches/nexus-5000-series-switches/116248-configure-fcoe-00.html instructions

  But after the installation, I get an error on the fabric: FCoE or FC uplink is down on Vsan 500;

  And the Nexus program: Vsan 500 is declining (pending flogi)

  When I ' display interface vfc 1 ' CLI nexus I don't see "Trunk VSAN (high)", but

  "VSANS trunk (boot) (500).

  Unfortunately, I can't find the technical notes for mini UCS (with UCSM v. 3.0), so maybe you can promt guides or suggestion for this?

  Thank you in advance!

  Same question here.

  TIA

• 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

• set up to bring the Fibre Channel between UCS of interconnection fiber and Nexus 5548UP.

  by using the following configuration between Nexus5k and UCS FI. the status of channel comes to ini and change to notConnected.

  -------------------------------------------------------------------------------
  FC1/31 431 notConnected swl - 100 F
  FC1/32 431 notConnected swl - 100 F

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

  The system version: 5.2 (1) N1(1b)

  1 on FCoE
  1 active FEX
  active toy-channel-trunk 1
  interface vlan 1 on
  1 active LACP
  1 active LLDP
  1 active NPIV
  1 active sshServer
  1 on GANYMEDE
  1 active telnetServer
  Uni-directional active 1
  1 active VPC

  san-port-channel interface, 100
  active channel mode
  switchport mode F
  switchport trunk allowed vsan 431

  interface fc1/31
  switchport 'SAN PO to UCS - one' description
  channel-group 100
  no downtime

  interface fc1/32
  switchport 'SAN PO to UCS - one' description
  channel-group 100
  no downtime

  interface fc1/31
  switchport mode F
  interface fc1/32
  switchport mode F

  Help, please

  You must update your 5 k at least

  6.0 (2) N1 (2)

• NSX design with cisco UCS/fabric interconnects and Nexus switches

  Hi Experts

  I am new to NSX design and deployment and working on a project. We deploy NSX for applications of level 4 (web, app, db, DC). I use logic, DLR, ESG and DFW switches. I next we intend to use roads static confusion..

  1. do we cover all the VLAN from the virtual to the physical environment? for example mgmt VLAN, level vlans(web,app,db), vxlan transport vlan or it should be only a VLAN specific?  which means would be I have set all the VLANS in environment NSX in my physical switching environment?

  2 vds? don't we create not only 1 vds initially during the deployment of vcenter or more? Should we take any special consideration while deploying to the deployment of the NSX?

  3 static routes - we configure static routes on the DLR and the GSS? Should I use the default routes upstream? on the physical router should we be routing all subnets from virtual environment to the GSS.

  4. where and who should create virtual machines? Via vCenter or before the deployment of the nsx NSX?

  5. we have a level of domain controller. Should it be part of 3 or separate applications with allow any any rule on DFW?

  Thank you

  Sam

  (1) the VLANs which exist for physical Machines span the logical switch VXLAN NSX in the following cases:

  • If the current deployment there are physical Machines in the same Vlan and subnet IP with Virtual Machines. If this common Port Vlan group is migrated to a switch logic VXLAN Backed port group and not possible to change the IP addresses of the virtual machines, and then a bridge DLR (Distributed logical router) works as the conversion between Vlan physical and virtual VXLAN
  • If Conversion of P-to-V of the physical Machines continue on this Vlan

  VLAN which cover only the virtual machines or virtual local networks which cover only physical Machines must not be delayed.

  (2) for the deployment of the NSX, there may be more than 1 dVS or only 1 vDS according to the design. There may be another type of traffic other VXLAN base of virtual machines such as backup, storage, VMotion and the overall design, management, best practices apply here as well.  A requirement of the NSX is a common VDS that spans the entire Cluster. For each Cluster, this "common VDS' may be different. Yet once this VDS maybe a separate VDS dedicated VTEP or VTEP features functionality can be added to the existing VDS. It may be best to separate the VTEP vDS.

  (3) for the DLR, a default gateway is usually sufficient. If static routes are used, the GSS must then drive by default upstream and the static routes with the next hop of the DLR downstream for the subnets in the subnets IP VM logical switch. On the physical router static route to the VM, but also DLR - ESG logical subnets Subnet switch is required. Management of static routes is easier if route summarization is possible, or if necessary, close to the IP subnets, so it may be a good idea to use the dynamic routing such as Ospf or BGP protocol. There are also features of IP address management in Vrealize and other IPAM solutions if Automation is necessary for large and dynamic environments.

  (4) NSX has no functionality in the creation of the VM, it only creates Services network such as switches, routers, Firewalls, Load Balancing. The creation of the part VM continiues the same way as before. A point to note is maybe the logic is created appear as VXLAN named port groups on the VDS. NSX Manager creates groups of ports on the VDS, the only difference is that the name includes VXLAN. The virtual machine is like before added to this group of VXLAN Backed Port settings, or added to the logical switch from NSX Manager interface that appears again as a Plugin for VCenter. VCENTER is so point to create virtual machines and add these VMs to the logic is.

  (5) level of domain controller can be a separate layer, or other third party, may be preferable to upgrade separated except 3 applications. Usually, it's the same design without NSX. dFW rules can help protect the domain controller with allowing only ports of the virtual machine or physical Machines being admitted. dFW rules can apply to VXLAN based logical switches NSX so that VLAN based DVS Port groups because it's the kernel module.

• vCenter Converter support for dvSwitch and Nexus 1000v

  Nothing changed since it was published in May 2009:

  http://www.VMware.com/support/vSphere4/doc/vsp_vcc_41_rel_notes.html

  VMware vCenter Converter vCenter Server 4.0 | May 21, 2009 | Build 161418

  Document last updated: May 21, 2009

  Import and export tasks fail when a vNetwork Distributed Switch is selected as the network for the virtual machine target

  When you create an import or export tasks and select a vNetwork Distributed Switch in the choice of the network for the virtual machine target, the task begins but does not immediately with the following error message: unknown error returned from agent vCenter Converter. This problem appears when you use the wizards to import or export or the convert Command Line Interface (CLI) tool to create the task.

  Solution: Select a network to the computer virtual target that is not a vNetwork Distributed Switch.

  We had this problem a few weeks back and see how this problem exists since last year, vCenter 4.0 Update 1 or 2 this address?  Thank you.

  Hi Terran0925,

  According to the "Known issues" section in the release notes for "VMware vCenter Converter vCenter Server 4.0 Update 1 | November 19, 2009 | Build 206170 "to http://www.vmware.com/support/vsphere4/doc/vsp_vcc_41u1_rel_notes.html#resolvedissues , the question was always present.

  There is no mention of the issue on the VMware vCenter Converter vCenter Server 4.1 release notes. The release notes can be found at http://www.vmware.com/support/vsphere4/doc/vsp_vcc_42_rel_notes.html

  The details of this version are;

  VMware vCenter Converter 4.2 | July 13, 2010 | Generation 254483

  vCenter Server 4.1 | July 13, 2010 | Build 258902

  Note: in order to get this version of VMware vCenter Converter vCenter Server, you must upgrade your vCenter server for "vCenter Server 4.1 | July 13, 2010 | Build 258902.

  I hope this helps.

  Kind regards

  Graham Daly

  Champion of knowledge

  VMware Inc.