Nexus 7000 questions sampled NetFlow

Similar Questions

• Nexus 7000 - integrate FEX - identify ID ASIC

  Hi *.

  in reference to this the following guide, I would like to identify the Asic-ID, to plan the integration of a FEX 2248PQ to an interexploité in a context of F2e M1-xl-type F2 module.

  http://www.Cisco.com/en/us/docs/switches/Datacenter/nexus2000/SW/configuration/guide/rel_6_2/b_Configuring_the_Cisco_Nexus_2000_Series_Fabric_Extender_rel_6_2_chapter_010.html

  There is a note in the section "combining of a tissue Expander to a Module of the F2 series.

  Each port in the ASIC has an index. Allow only ports with similar indices across ASICs to be added to a port channel.
  For example, if port 1 has an index of 1 and port 2 has an index of 2, the following ports are supported and not supported:
  

  • Support: 1 1 ASIC and port 1 of 2 ASIC are added to a port channel.
  • Unsupported: Port 1 of 1 ASIC and port 2 2 ASIC to form a port channel.

  A set of ports to an ASIC that a set S, such as {1,2,4} Sub index, is authorized to add to a channel of port if the port channel has an equivalent, or an empty set.

  So is there a way to get the asic-id, as mentioned above, with a few appropriate show commands?

  Please be advised that the FEX are not yet installed.

  I need to check beforehand if the wiring is correct.

  Some useful answers in the next a few would be very much appreciated.

  Thanks in advance

  Sven

  Sven

  Take a look at this article, and if all goes well he will answer your questions.

  http://www.netcraftsmen.NET/blogs/entry/using-FEX-with-the-F2-card-in-a-Nexus-7000.html

  Jon

• L3 Nexus 7000 routing Proxy

  Hello

  I propose Nexsu 7000 as backbone switch for my client.

  But I do not understand why proxy L3 routing must be used under M & F2 mixed condition.

  But module F2 also bear all capacity of L3, L3 routing dosen't support of the F2 module with module of the M series.

  Could you tell me why this is happening and explain Nexus 7000 architecture?

  Thank you

  Yun.

  M2 + F2e in same VDC works dated 6.2 (2), in which case F2e module returns to the classic transmission L2 mode, leaving all L3 decisions up to the M2 module, so you still need L3 routing proxy.

  I think the reasoning behind this is because of the motor M2 L3 being much more potent than the freight forwarder F2e L3.  For example, the motor M2 can make OTV, the impossible F2e.  Logic to return L3 decisions for a more powerful card.

  What I find strange is that although F2e online map has an integrated transmission of L3 engine, that I can not configure the IP of L3 addresses directly on F2e ports.  Creating a VLAN SVI and by setting the port access mode F2e work, but if I only need a link point single point of L3 between the Nexus 7 K and another device, and I have configured the vPC, vPC then in an inconsistent with Type 2 State, because the VLAN and/or IVR is not present on the switch of peers.

• 6248up Nexus 7000 or 2000

  We have 2 core witches nexus 7000 and then downstream to 2 nexus 2000 is.

  then e have 6248up fi for the UCS. should he go to the nexus 2000 or directly at the base of 7000 nexus?

  What is the benefit or to the detriment of go to the nexus 2000 or 7000?

  You must join the Nexus 7000 6248.

  Nexus 2000 was created to connect to end-hosts and not the switches or the FI. Since all local switching is performed on N7k, if you connect FI N2k, ensuring the same between the blades will be sent through n2k to N7k, tissue link N2k - N7K will be oversubscribed and UCS will suffer poor performance.

  So FI must be connected to the N7K

  HTH,

  Alex

• MultiThreading using QtConcurrent question (sample)

  using an example I have configure QConcurrentRun & a watchman to create a new thread, deal with events & updated once.

  The only question is, when I click the button run in 10.2 I get a pop up error

  An internal error occurred during: "Executing run".
  Invalid thread access
  

  But if I right click on the project folder-> run as-> blackberry c / c ++ application that the application is built, lance deploys and everything seems to work properly.

  I have attached a sample project that demonstrates the issue & how a little easier to deal with events in other threads

  I discovered this momentics which caused the question of warning invalid thread, a reason any created another run configuration called qdelaunch, after you remove these configs, it allows the run button be clicked directly from the toolbar.

• Kitkat 4.4 Android - Skype Nexus 5 question

  Hi guys

  I try to sign in to Skype on my new Nexus 5 with Android 4.4 Kitkat and login screen return again and again, someone has an idea or face the same?

  Just installed the 4.5 update and the ms account problem is fixed :-)

• Nexus 1000v - Question about VSM and VEM compatibility update

  I am unable to find Cisco documentation on the backward compatibility of the MEC when you perform an upgrade of the VSM. I'm looking to improve the VSM of 4.2 (1) SV2(2.1a) to 5.2 (1) SV3 (1.15).

  Hosts must be upgraded simultaneously, or they will continue to work with the current MEC? I prefer to leave guests as is and upgrade the MEC as a bundle with the host ESXi 6.0 upgrade to eliminate having two separate windows of failure for the guests.

  ESXi hosts all running 5.5 with VEM cisco-vem-v162-esx (4.2.1.2.2.1a.0 - 3.2.1).

  Thanks for the help in advance!

  Greetings.

  Click on the link below, you can enter your version of esxi, N1k version and versions of destination and will get a high level not list.

  http://www.Cisco.com/c/dam/en/us/TD/docs/website/Datacenter/nexus1000/upgrade/n1kvmatrix.html

  You can go directly from the SV2(2.1a) to SV3 (1.15)

  VSM upgrade notes: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus1000/sw/5_2_1_s_v_3_1_15/install_upgrade/guide/b_Cisco_N1KV_VMware_Install_and_Upgrade_Guide_521SV3115/b_Cisco_N1KV_VMware_Install_and_Upgrade_Guide_521SV3115_chapter_010.html

  Please make sure that you check the required CPU, vram, virtual disk space requirements BEFORE, you upgrade the VSM, as demands increase for SV3 versions.

  After that the VSM is updated, your MEC will continue to operate at the older level, until you get updated MEC to level.  You usually don't want to change the major config will be running in this mixed level.

  After the upgrade of the MEC, remember to update the level of functionality of vem, or features that now get discharged to the VSM VEM (netflow, igmp snooping, lacp, etc.) will be continued to be run on the VSM.

  Take a look at http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus1000/sw/5_2_1_s_v_3_1_15/install_upgrade/guide/b_Cisco_N1KV_VMware_Install_and_Upgrade_Guide_521SV3115/b_Cisco_N1KV_VMware_Install_and_Upgrade_Guide_521SV3115_chapter_0100.html

  as it has some notes on the integration of the module vib VEM update esxi 6.0 install/upgrade ISO.

  Thank you

  Kirk...

• Clarification of Nexus VPC

  After a recent deployment of the switch, I see some very strange transmission problems layer 2.  I'm not sure if this is related to a problem of configuration on my part.  I would like clarification on the VPC, and I hope you can help me.

  It is my understanding that when you have a series of double-sided VPC between, say, a pair of N7700 and several pairs of Nexus 9 K or K 5 switches, that all the field of VPC ID must be different.  However, a contractor told me that each number VPC - associated with the uplink of etherchannel to the Nexus 7Ks - must also be unique.  A graph that shows my dilemma is attached.

  Question - I am ok to reuse the port-channel number 3 with the VPC 3 for all pairs of leaves, or if they should be different?

  Hello

  What you show, it's perfectible acceptable. The two areas of vPC in the Nexus 9000 layer, domain of the vPC 117 and 118 in your diagram, have no knowledge of the other, and so the same vPC and port channel number can be used.

  As you said, you obviously have a unique numbering to the layer of Nexus 7000.

  Concerning

• Nexus F2e series modules

  Can someone tell me what is the difference between F2 and new F2e?  All I can find is supportive effect. Isn't it?

  The biggest complaint (and Gotcha) when people bought the N7K-F248XP-25 (aka standard F2) is an inability of the online map to work with F1 and M1/M2 card.  The F2 has be in it's own little VDC.   No member of Cisco would have admitted that it was due to a technical fault (or disaster).

  Thus the F2e is born.  Whatever the standard F2 can do, the F2e can do as well.  And the F2e can work with M1/M2.  "And when that happens (as indicated on the data sheet)" when you deploy the Module Cisco Nexus 7000 F2e-series fiber has VCC with the Cisco Nexus 7000 M Series modules, the Nexus 7000 F2e - series Cisco Fiber Module will run in mode Layer 2 only, delegating all capabilities of layer 3 for the Cisco Nexus 7000 M-modules of the series present in the VDC. The initial version of the software does not support this feature. »

  The F2e comes in two "forms": 1/10BaseTx 48-ports or SFP / SFP +.

  As the "F2", the F2e still won't be able to support the OTV (integrating F2 series Modules in a Cisco Nexus 7000 Series System).

  Due to the release of the new map of F2e expect Cisco to announce (within 6 months) at the end of sale of the standard map of F2.  (My own opinion, read below for refutation of the management team Cisco Nexus 7000 Production.)

  I don't know what Cisco will do to customers who bought the standard F2 by mistake.  Cisco quietly will allow them to trade or swap for F2e?  Only people (like Jerry) in Cisco will know.

  Post edited by: Leo Laohoo

• What does Nexus 1000v Version number Say

  Can any body provide long Nexus 1000v version number, for example 5.2 (1) SV3 (1.15)

  And what does SV mean in the version number.

  Thank you

  SV is the abbreviation of "Swiched VMware"

  See below for a detailed explanation:

  http://www.Cisco.com/c/en/us/about/Security-Center/iOS-NX-OS-reference-g...

  The Cisco NX - OS dialing software

  Software Cisco NX - OS is a data-center-class operating system that provides a high thanks to a modular design availability. The Cisco NX - OS software is software-based Cisco MDS 9000 SAN - OS and it supports the Cisco Nexus series switch Cisco MDS 9000 series multilayer. The Cisco NX - OS software contains a boot kick image and an image of the system, the two images contain an identifier of major version, minor version identifier and a maintenance release identifier, and they may also contain an identifier of reconstruction, which can also be referred to as a Patch to support. (See Figure 6).

  Software NX - OS Cisco Nexus 7000 Series and MDS 9000 series switches use the numbering scheme that is illustrated in Figure 6.

  Figure 6. Switches of the series Cisco IOS dial for Cisco Nexus 7000 and MDS 9000 NX - OS

  

  For the other members of the family, software Cisco NX - OS uses a combination of systems independent of the platform and is dependent on the platform as shown in Figure 6a.

  Figure 6 a. software Cisco IOS NX - OS numbering for the link between 4000 and 5000 Series and Nexus 1000 switches virtual

  

  The indicator of the platform is N for switches of the 5000 series Nexus, E for the switches of the series 4000 Nexus and S for the Nexus 1000 series switches. In addition, Nexus 1000 virtual switch uses a designation of two letters platform where the second letter indicates the hypervisor vendor that the virtual switch is compatible with, for example V for VMware. Features there are patches in the platform-independent code and features are present in the version of the platform-dependent Figure 6 a above, there is place of bugs in the version of the software Cisco NX - OS 4.0(1a) are present in the version 4.0(1a) N1(1a).

• Question of vPC NEXUS7K

  Guyz please correct me if im wrong, I have 2 x Nexus7k and lets say 1 3750 switch now I need to have the connected and active also vPC inter - vlan routing for VLAN10 on the two Nexus switches as follows: -.

  SW1 - 2x10G - SW2 Nexus nexus

  (Gi0/3)-/(Gi0/2)

  3750 Switch3

  |

  VLAN 10

  Requirements on the Nexus two, SWs

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

  (1) turn on vPC on both switches to Nexus

  (2) create vPC area 8 on the two switches

  management interface 3) the use of two switches to configure the peer of vPC keepalive

  (4) (4) configurer set up on links two 10 G on both sides on the port channel 5, turn on the trunk and spanning tree-type network

  (5) activate vPC Peer to the port-channel 5 on both sides

  (6) create VLAN 10 on Nexus SW1< by="" doing="" this="" shouldnt="" vlan="" 10="" be="" created="" on="" nexus="" sw2="" by="" default="">

  (7) create the Vlan 10 interface and IP address assignment< is="" there="" anything="" i="" need="" to="" add="" here="" other="" than="" this="" also="" the="" interface="" vlan="" will="" be="" added="" automatically="" on="" the="" other="" switch="" with="" the="" same="" ip="" address="">

  (8) create port channel 7, assign Gi0/3 and Gi0/2 and allow both the trunk

  (9) select vPC 101 to the channel port 7 on both sides

  Requirements on the two 3750 SW1

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

  (1) create a vlan 10

  (2) assign the interface vlan Access 10

  (3) to activate the trunk Gi0/3 and Gi0/2

  (4) create port channel 7 and add the two links

  -NOW assume that everything is configured correctly, all links between the switches that none should be blocked by STP and VLAN 10 traffic should be secured by two Nexus switches?

  Hello

  Most of the steps you outlined is correct, although a few comments:

  (3) use the two switches management interface to configure the peer of vPC keepalive

  A point to note here is that if you have a supervisor engine double (SE) in your Nexus 7 K, then you need to install the management between the two interface IS active that is current and wait for SE, since the two N7K to the same local network. This way you will always have peer connectivity vPC regardless of who is active.

  (6) create VLAN 10 on Nexus SW1< by="" doing="" this="" shouldnt="" vlan="" 10="" be="" created="" on="" nexus="" sw2="" by="" default="">

  VLANs are not created on the second switch unless you use the switch profiles i.e., config-sync, and this feature is not supported on the Nexus 7 K.

  (7) create the Vlan 10 interface and IP address assignment< is="" there="" anything="" i="" need="" to="" add="" here="" other="" than="" this="" also="" the="" interface="" vlan="" will="" be="" added="" automatically="" on="" the="" other="" switch="" with="" the="" same="" ip="" address="">

  I guess the obvious thing is to allow a first Hop Router Protocol as HSRP. Note that when you use HSRP jointly with vPC, while the control plan continues to operate as active / standby, in a perspective of data plan, both routers are capable of transmitting data in VLAN that is, assets.

  With regard to the SVI created automatically, according to the note to point 6 above, the IVR will not be created as there is not of the Sync feature of config on the Nexus 7 K.

  -NOW assume that everything is configured correctly, all links between the switches that none should be blocked by STP and VLAN 10 traffic should be secured by two Nexus switches?

  Fix. You should probably also follow best practices spanning tree as Setup providing the bridge root is located on one of the Nexus 7 K, the root of the backup is the second Nexus 7 K etc.

  This and much more are covered in the Configuration and Design Guide: best practices for Virtual Port channels (vPC) on switches Cisco Nexus 7000 Series on CCO. It is a very good reference and well worth taking a look through.

  Concerning

• groups of IP addresses are supported on Nexus-5000 and models down?

  Looking online, I see the ip address of the object-group is explicitly listed as

  supprted on Nexus 7000 but on other model documents command is confusing.

  For example, for Nexus-5000 references to IP address source/destination to refuse the order group objects exist in the documentation older versions of NX - OS 4.0 and 4.1 (with no explicit object-group command is listed in the same CLI reference) but in v5.x current source/destination shows no Group of IP addresses as available choice.

  Can one with access to the Nexus 5000 or 3000 check if the ip address of the object-group is an order valid on this platform?

  It seems full support (like on IOS), using the IP address groups was established in v6 NX - OS (which only works on platform 7000).

  There was also presented on the lower models?

  Thank you.

  Hi Alexandre

  This feature is not currently supported on N5k/N3k

  If you have specific requirements for this feature, please join your team has to describe your network design. And they will be able to help you.

  HTH,

  Alex

• Nexus MTBF

  Hello

  Are there MTBF values available for switches of Nexus and components (line cards, sup, fabrics, etc.)? I could not find on the data sheets.

  Thank you in advance.

  Hi Andras,

  Thanks for the note. In fact, I just found a few more which covers modules e/s in the Nexus 7000 Linecards feature comparison document.

  Concerning

• Nexus NX of VDC update - isolated OS

  Hey guys Nexus!

  I received a Virtual Device context (VDC) with administrator privileges to use for research and development. Can I switch my Nexus 7000 series NX of VDC - OS without affecting the other TDC on this box?

  Thank you

  Frank

  Hi Frank,.

  You are unable to pass the Cisco NX - OS for an individual VDC software because when you upgrade the software for Nexus NX - OS he witches upgraded software for the VDC in the switch.

  Discover the VDC upgrade confirmation document

  It could be that useful...

  -GI

  Rate if this can help

• Nexus 5 k with L3

  Hello

  Could you explain the following paragraph, located at the following ADDRESS:

  http://www.Cisco.com/c/en/us/TD/docs/switches/Datacenter/nexus5000/SW/operations/interfaces/602_n1_1/N5K_Interfaces_Ops_Guide/L3_w_vpc_5500platform.html#wp1014116

  «In some circumstances, you might consider having a distinct link between both vPC switches, to form the layer 3 Protocol Routing peering or transport traffic VLAN no - vPC.» * While this design is compatible with the Cisco Nexus 7000 Series switch, it does not work on the Cisco Nexus 5000 series switch *. With the Cisco Nexus 5000 Series switch, we recommend using a link of vPC for Layer 3 peering peers in order to perform the vPC and non - vPC VLAN. »

  I have deployments of Nexus 5 k with L3 cards which have separate links for L3 and no vpc VLAN instead of having them on the link of peers VPC and they seem to work well. This is a mistake in the documentation or could I have problems?

  Thank you

  Eric Lauriault, CCIE 27521

  Hi Eric,.

  In the URL you have specified http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/n5k_L3_w_vpc_5500platform.html

  Take a look at Figure 3-10 and now add another layer 3 linking N5K N5K-1-2.

  1 multicast is sent on N5K - 1

  2. multicast routing on N5K - 1.  A copy is sent to the interface of L3 and another copy is sent to the peer-link in vlan reserved (in the vpc bin - vrf default vlan xxxx).

  3. the packet received on the interface of layer 3 multicasting will still get replicate by the peers-Link.

  Thank you

  -KL