DualHoming 2248TP-E to of N7K?

Similar Questions

• EC to the server through to a single 7009 2 2248TP

  We are looking at buying server and NAS connectivity to a new data center project. We plan on buying a unique NX7009 for the core and our VAR initially quoted us 3850 s to use for Server/NAS connectivity. But now I just think using 2248 s aircraft (cheaper) but my question is, can I create a contraceptive among an edge on a fex port and a port of edge on the other for the high-end devices? As in the photo below (gross). We plan get

  Sup2s with the 7 k. I've seen a few posts similar to this one, but they are all involved 2 7ks...

  

  This topology is not supported on N7K. You can have THIS active/active between host and 2K in this design.

  Only active connections / standby are supported by the server.

• N7K - image size see command

  Hello

  on a Cisco Nexus 6 k, you can have a perfect look at the frame size through your Interface

  SH material internal bigsur ethernet port 1/1

  Statistics of the MAC:
  MAC statistics | Value
  -------------------------------+-----------------------------------
  TX_PKT_SIZE_LT_64 | 0
  TX_PKT_SIZE_IS_64 | 6607344
  TX_PKT_SIZE_IS_65_TO_127 | 72920088
  TX_PKT_SIZE_IS_128_TO_255 | 2341094
  TX_PKT_SIZE_IS_256_TO_511 | 1508120
  TX_PKT_SIZE_IS_512_TO_1023 | 19494
  TX_PKT_SIZE_IS_1024_TO_1518 | 3639395
  TX_PKT_SIZE_IS_1519_TO_2047 | 0

  [.. Snip...]

  Anyone happen to know a similar command on the N7K? I can't find something of enough :(

  THX

  We do not have an exact equivalent command for 7 k.

  It's something that we use (not on a regular basis) to check packets hit the asic

  Tested for module F3

  Att mod 1

  module-1 # sh intern statistical device mac hard any port 17 (17 is the port of the façade)
  |------------------------------------------------------------------------|
  | Feature: Flanker Eth Mac Driver role: MAC Mod: 1 |
  | Last reset @ Fri Jan 29 03:33:07 2016
  | Statistical device category: all THE
  |------------------------------------------------------------------------|
  Instance: 2
  Ports of value for name Cntr
  ----- ----                                          -----             -----
  4 Gap igr: receipt 0000366343705031 17 cnt bytes.
  16 egr on upm: transmitted bytes cnt 0000001447333726 17.
  IGR 400 gap: total pkts rcvd 0000000453959483 17.
  IGR 401 to upm: total 64 bytes pkts rcvd 0000000000004907 17.
  402 igr Gap: pkts rcvd, len(> 64B,)<= 127b)   ="" 0000000014976353 ="" 17="">
  403 igr Gap: pkts rcvd, len(> 127B,)<= 255b)  ="" 0000000039953289 ="" 17="">
  404 igr Gap: pkts rcvd, len(> 255B,)<= 511b)  ="" 0000000079892281 ="" 17="">
  IGR 405 to upm: pkts rcvd, len(> 511B,)<= 1023b) ="" 0000000159689978 ="" 17="">
  IGR 406 to upm: pkts rcvd, len(> 1023B,)<= 1518b)="" 0000000154452499 ="" 17="">
  IGR 407 gap: pkts rcvd, len(> 1518B,)<= 1522b)="" 0000000001246846 ="" 17="">
  408 igr Gap: pkts rcvd, len(> 1522B,)<= 1548b)="" 0000000003743330 ="" 17="">
  IGR 425 to upm: pkts rcvd, RALIGN with good 0000000448969307 17 crc.
  IGR 430 to upm: linking remote flaws rcvd 0000000547357955 17 -.
  656 egr on upm: total pkts with good CRC 0000000007259086 17.
  658 egr on upm: pkts group, len (> 64 b,<= 127b) ="" 0000000007138214 ="" 17="">
  659 egr on upm: pkts group, len(> 127B,)<= 255b) ="" 0000000000020751 ="" 17="">
  660 egr on upm: pkts group, len(> 255B,)<= 511b) ="" 0000000000032542 ="" 17="">
  661 egr on upm: pkts group, len(> 511B,)<= 1023b)="" 0000000000001633 ="" 17="">
  662 egr on upm: pkts group, len(> 1023B,)<= 1518b)="" 0000000000000558 ="" 17="">
  667 egr on upm: pkts group, len(> 2500B,)<= mtu) ="" 0000000000065388 ="" 17="">
  668 egr on upm: pkts group, len(> cfg0,)<= mtu)="" with="" good="" crc="" 0000000000065388 ="" 17="">

  You can disable the use of statistics-

  att mod 1

  device of clear statistics all the

  -Raj

• 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

• Connection to a FEX N7K

  Hello

  N7K configuration in one of our domain controllers, we have several aircraft that are connected to this N7K. I'm a little confused on a particular configuration and hoping someone can explain this configuration for me.

  Here's the part on the N7K I would like clarification on:

  E2/2 ports and E3/2 are configured as Port of L2, which are related to a FEX channel

  interface port-channel107
  switchport
  switchport mode fex-fabric
  FEX associate 107

  VLAN 202

  name of genius

  interface Vlan202
  Member of the VRF Engineering
  IP address 10.16.116.1/24
  IP router eigrp Eng
  IP passive-interface eigrp Eng
  PIM sparse-mode IP

  interface Ethernet107/1/47
  Description link to WAN
  no downtime

  interface Ethernet107/1/47.21
  Description link to Remote Site
  encapsulation dot1q 202
  Member of the VRF Engineering
  IP address 10.16.116.1/24
  IP router eigrp Eng
  IP passive-interface eigrp Eng
  PIM sparse-mode IP
  no downtime

  My question is, why do we not have the same IP address routed (10.16.116.1/24 as a SVI and another on the interface on the FEX?

  Thanks in advance.

  ~ zK

  I don't think that if you need the Ethernet107/1/47.21 you already have L3 vlan 202. You can just do port Ethernet107/1/47 as trunk and allowed vlan 202.

  int Ethernet107/1/47

  switchport trunk

  switchport trunk allow vlan 202.

• It has been awhile, N7k now supports EvPC?

  As far as I know, in an environment of Nexus double 5 k, w/c are configured to the vPC. EvPC is available for FEX in double room, a single connection type for each of the switches to Nexus. Like the image below.

  1. jpg

  

  BUT, but but but, as documentation goes, model Nexus 7 k still do NOT support this kind of functionality that is, we cannot double home a FEX as 2 k nexus one or Nexus two, 7 k in vPC, w/c these switches NX7k are in vPC

  the question therefore, its been a while, it stand now?
  As far as my research goes, n7k still hate.
  My research, I met actually a post from 3 months ago, w/c says 'no' to my question T.T
  LINK: click ME

  Any guy entered? : D

  Hello

  You are right, but the Aru said the right thing. It supports dual domicile that see you in the diagram, but not an improved vpc.

  To be clearer, here is an explanation of the improved VVS - thanks to steve fuller on another post.

  "Improved VPC is a method that allows the connection of active way FEX using vPC between the FEX and switch upstream of Nexus and at the same time to connect a device to the host with a vPC FEX. interfaces"

  For more details, please see below.

  http://www.Cisco.com/c/en/us/TD/docs/switches/Datacenter/nexus5000/SW/op...

  Hope that this clearly indicates.

  Thank you

  Madhu

  Please note the useful messages *.

• Port-channel problem between fabric Interconnect and vPC N7K

  Hi all

  I have a problem with the Port Uplink channel between fabric interconnect with N7K using vPC

  It's my network for the UCS deployment topology

  

  N7K I configured vPC for red link and green linkto the fabric Interconnect A I has configured the Port-Channel with Member is Port 1 and Port 2, uplink is red link. Interconnection fabric B, I have configured the Port-Channel with Member's Port 1 and Port 2, uplink's green link.

  The interface port-channel on N7K show is good, each port-channel upwards and have all members. But the fabric Interconnnect, when I see in the UCS Manager, the status of the Port-Channel on Fabic A and fabric B dysfunction not more info: no operational Member. Although all the link is a link to the top and I've got the status of the Port Channel is enabled in the UCS Manager. When I see the properties Port 1, Port to Port-Channel 2, I see the number of members status is: individual. This means channel port is not up and no member in this configuration. I want to using the port-channel load balance and more bandwidth for the uplink of 20Gig. I don't understand why?

  Please help me solve this problem, I have to send the screenshot of UCS Manager when I show the status of the Port-Channel and Port-member in port-channel to reach items.

  Can someone help me solve this problem, thanks a lot. References, please include elements for more details on the fault.

  Thank you

  Trung.

  Hello Nguyen,

  Since the two N7k please collect:

  SH cdp nei

  SH run membership in. X int

  SH sum port-chan

  Thank you

  Matthew

• Evolution of the data center: N7k or C6500

  Hello

  I am curretnly studying how our data centers evolve.

  For physical physical architecture:

  -We have 2 data centers, L2 interconnected at 10 Gbps.

  -On each data center, 2 x C6500 serve basic and distribution at the same time.

  -The access layer is to C3750G, connected to the chassis base with 3x1Gbps etherchannels.

  -No server rack blade for the moment.

  For the logical aspect:

  -L2: we use STP lying on the 2 DC

  -L3: Core are connected directly to the MPLS cloud. We use the VRF.

  The next evolution of the server would be to replace the stand-alone servers by blade, connected with 10 Gbps.

  I was hesitant on how to improve the current design, and I'm not sure the + and - 2 (except that Nexus need investment)

  (1) keep the C6500 and:

  -Add maps to 10 Gbps on the C6500 (16-port cards)

  -use VSS on the two site to simplify the design STP (even though we have had no problems with it so far)

  (2) replace C6500 by Nexus7K for greater flexibility with 10 Gbps

  (3) as an option, add a distribution layer N5K which would simplify the wiring and allow a possible evolution FCoE (in this solution, I would keep C6500 as base or evolve N7k).

  What do you think?

  Thank you

  P.

  This is going to be a very controversial topic.

  Let's not talk about budget here because it could become very dark.

  The 6500 Sup720 or Sup2T (I still prefer the latter), is very good when you aggregate a significant amount of some 10 Gbps and 1 Gbps and a handful of 40 Gbit/s.

  The Nexus family is very good when you want to consider a few 100 Gbit/s, but a significant amount of 10 Gbps.  NEXUS is also the way to go if you want to connect your Fibre Channel switch DC as Nexus will support 1, 2, 4 - and 8 Gbps FC.

  Nexus 7 K can support 100 Gbps (two per card online), 40 Gbps (six per card online) and of course 10 Gbit/s (up to 48 by card online).

  Very quickly, the will be some service modules that will be introduced for the Nexus 7 K.  They are WAAS, ASA and a NAM.

  There will be life with the 6500?  In some cases, Yes.  It is still is not clear if ALL the 6500 service modules will evolve into the Nexus.  In my view, the three modules, I have just mentioned is to "test" the waters.  Once the momentum has been achieved, the others could follow.

  There are rumours abound that there could be a possibility of Nexus 2 K which will support the PoE.

  Attached something for your perusal.

• 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

• "Nexus 7010 - SFP message validation ' failure 'with SFP - 10 G - SR.

  Hello everyone, I have 2 Nexus 7010 with 32 Port 10GbE Module (N7K-M132XP-12). I put a few FPS - 10 G - SR transceiver in the different interface, but I get the following message "SFP Validation failed" when I enter the show interface ethernet command. This message can appear when the speed of the interface and the transceiver is incompatible, but I also tried to force the speed of the interface in 10,000 and the problem remains the same.

  Don't know not if it helps but I noticed on the 5020's that if you put a 1 G SFP in a slot that is capable of 1/10, you then have to enter 'speed 1000' in the interface or you get the error "FPS of Validation failed" in an interface to see the. If you try to specify the speed in the configuration interface.

  I don't like specifying the speed (or duplex also) that auto-negotiation is necessary for the proper functioning of 1 G and now that auto-negotiation is pretty standard I have more problems caused by people "hard coding" these than not. But in this case, it was necessary to make it work.

  EDIT: Heck, it was a necro-post! Laughing out loud. Well, I hope it helps someone.

  Post edited by: Mark DeLong

• EEM with Nexus 5020?

  Hello

  I wonder if it is possible to use the cmdlets to EEM with the Nexus 5000? Based on http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/fundamentals/513_n2_1/b_Cisco_Nexus_5000_Series_NX-OS_Fundamentals_Configuration_Guide_Release_513_N21.pdf of this document, it should be possible, but my 5020 does not know the command "event manager applet. Is there a feature that I need to activate it first?

  Best regards

  Pille

  EEM is supported only on the N7K right now.  While I pushed to get it on the 5K, I don't have any ETA.

• The strange script

  Hello:

  I have a N7K which has strange behavior for me

  When I connect to the console once the welcome a message command is executed

  In my case is "terminal color:

  User access audit

  N7K1 login: admin

  Password:

  Operating system (NX - OS) Cisco Nexus software

  TAC support: http://www.cisco.com/tac

  Copyright (c) 2002-2012, Cisco Systems, Inc. All rights reserved.

  The copyright in certain works contained in this software are

  owned by others and used and distributed under

  license. Some components of this software are licensed

  the GNU Public License (GPL) version 2.0 or GNU

  Lesser General Public License (LGPL) Version 2.1. A copy of each

  This license is available at

  http://www.opensource.org/licenses/GPL-2.0.php and

  http://www.opensource.org/licenses/LGPL-2.1.php

  "terminal color."

  N7K1 #.

  I do not see this command in the running configuration

  The question is where is - this command?

  I get a default script and I found there is a called Phyton scripting language that allows you to write scripts to fancy

  But I did not thing is tha case because the bootflash:scripts folder is empty

  Clues?

  Thanks in advance

  Al

  Hi Al,.

  Take a look at the bootflash and check if you have a file called. RC.CLI. this file is added when you run the terminal color persists and are then executed every time that connects to the switch.

  If the file exists, delete it and the terminal color command must be executed when a user connects.

  Concerning

• 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

• Design of 7K question

  I have a single 7009 with double Sup - 2 running 6.1 (3) for a replacement of the base, the modules include a N7K-M148GT - 11 L and two modules N7K-F248XP-25. I'm looking to create several committees and will finally connect my DR via OTV site using the card of the M1.

  My question (s) is / are, how you attach the M1 card back in the VDC if maps M1 and F2 are not compatible in the same VDC? It seems a bit pointless to do not be able to access my copper ports in a VDC. Even if I place a VDC for just the M1 card, do I need an external device to connect to other ports CDV F2 or can I use a VRF to achieve internal linking?

  Any suggestion would be useful and thanks!

  Dave

  As Andras mentioned that you need to separate the M1 and F2 in two different VDC

  If you want to deploy OVT, you will need a third VDC for the OVT using the recommended device OVT design

  see the third example the below document I posted before CSC

  https://supportforums.Cisco.com/docs/doc-27427

  Remember that you must have a good traffic engineering link L2/L3 good ability of planing in a topology of this kind and try to keep things simple as three CDV topology is quite complex!

  HTH

• Licensen advanced to N7700

  Hi all, I bought a pair of N7706, and I want to use the VDC feature on them, so I also bought the N77-VDC1K9 license.

  At the time, where I worked with N7K series, when I want to restart or to suspend a VCC of VDC1, I need an ADV1K9 N7K be installed. Now, when you go to the N7706, I also have these features too. And I guess I don't need some sort of license N77-ADV1K9, but it is there no such license!

  So my question is: do I need a permit separate order to use functionality like suspending a VDC on N77 series (except the N77-VDC1K9 license)

  Best regards

  Hi Tranviettu

  Yes, you should be

  Kind regards

  Sandip