N7K & N2K Connectivity
Hi All,
I would like to connect N2K with N7K for that do I need to have 10G port in dedeciated mode ?? or ports in shared mode will work ?? also If i want to connect N7K with another N7K switch do I need port in dedicated mode ???
Please clarify...
Thanks
Information About Using a Fabric Extender with a Cisco Nexus 7000 Series Switch
You can extend the Cisco Nexus 7000 Series switch architecture by connecting up to 32 Cisco Nexus 2248 FEXs as remote I/O modules. Each FEX provides top-of-the-rack connectivity for up to 48 hosts. Each FEX becomes an extension of the parent Cisco Nexus 7000 Series switch fabric, with the FEX and the switch becoming a virtual modular system. The FEX forwards all 1-Gigabit Ethernet traffic from the hosts to the switch over 10-Gbps uplinks. Traffic flows from the switch to the FEX over the 10-Gbps uplinks and to the individual hosts over 100/1000 Mb Ethernet downlinks.
You connect a FEX to the Cisco Nexus 7000 Series switch through the 32-port M1 series Ethernet I/O modules installed in the switch. We recommend that you connect each FEX to one port in a set of four shared ports to get the fully dedicated 10-Gb bandwidth.
Similar Messages
-
N7k N2K and n5k N2K design questions
Data Center with Dual N7K , want to add N2K for top of rack server access. I understand the model where I can set my servers up with a vPC Etherchannel to a pair of 2k with one 2k attached to each 7k. This model appears to meet all of the no single attached device rules of vPC. The question I have is how I can attach traditional server connectivity that doesn't support Etherchannel. In this model if I attach to a single 2k or team(without etherchannel) to both 2ks haven't I violated the no single attached device rule of vPC.
I have a similar issue with the 2232 and N5k model. In order to support FCOE on a 2232, the only supported configuration is to attach the 2232 to a single 5k, in all of the design models I have seen the server is depicted with a vPC etherchannel to the two 2232s that are attached to their respective 5k. In this design if my server doesn't support an Etherchannel, and I am forced to utilize traditional teaming I have broken the no single attached device rule of VPC again.
This no single attached device rule of vPC makes it really hard to utilize the FEX in either of these scenarios, What is the recommendation for connecting servers that don't support Etherchannel in these two modelsHi,
Take a look at the document Nexus 7000 Fex Supported/Not Supported Topologies and you'll see what options you currently have.
As I mentioned, up to and including NX-OS 6.2, a single FEX can only be connected to a single Nexus 7000. This is what is shown as Figures 8, 9 and 10 in the unsupported topologies section.
A server can be connected to two different FEX, and those two FEX could be connected to a single Nexus 7000 or two different Nexus 7000. The options are shown in Figures 6 and 7.
Regards -
My N2K connected to N5K, why some ports can set the port speed, and some cann't set the port speed?
int eth102/1/25 ！！！No speed command
(config-if)# ?
beacon Disable/enable the beacon for an interface
cdp Configure CDP interface parameters
channel-group Configure port channel parameters
description Enter description of maximum 80 characters
inherit Inherit a port-profile
ip Configure IP features
ipv6 Configure IPv6 features
lacp Configure LACP parameters
link Configure link
lldp Configure Interface LLDP parameters
logging Configure logging for interface
mvr-group MVR interface config
mvr-type MVR interface config
mvr-vlan Interface MVR Config
no Negate a command or set its defaults
rate-limit Set packet per second rate limit
service-policy Configure service policy for an interface
service-policy Policy Map
shutdown Enable/disable an interface
snmp Modify SNMP interface parameters
spanning-tree Spanning Tree Subsystem
switchport Configure switchport parameters
untagged Default to use for untagged packets on interface
end Go to exec mode
exit Exit from command interpreter
pop Pop mode from stack or restore from name
push Push current mode to stack or save it under name
where Shows the cli context you are in
(config-if)# int eth102/1/48 ！！！ include speed command
(config-if)# ?
bandwidth Set bandwidth informational parameter
beacon Disable/enable the beacon for an interface
cdp Configure CDP interface parameters
channel-group Configure port channel parameters
default Set a command to its defaults
delay Specify interface throughput delay
description Enter description of maximum 80 characters
duplex Enter the port duplex mode
fex Configure FEX fabric
flowcontrol Configure interface flowcontrol
hardware FEX Card type
inherit Inherit a port-profile
ip Configure IP features
ipv6 Configure IPv6 features
lacp Configure LACP parameters
link Configure link
lldp Configure Interface LLDP parameters
load-interval Specify interval for load calculation for an interface
logging Configure logging for interface
mac MAC
mac-address Configure interface mac address
mvr-group MVR interface config
mvr-type MVR interface config
mvr-vlan Interface MVR Config
negotiate Configure link negotiation parameters
no Negate a command or set its defaults
priority-flow-control Enable/Disable PFC
rate-limit Set packet per second rate limit
service-policy Configure service policy for an interface
service-policy Policy Map
shutdown Enable/disable an interface
snmp Modify SNMP interface parameters
spanning-tree Spanning Tree Subsystem
speed Enter the port speed
storm-control Configure Interface storm control
switchport Configure switchport parameters
untagged Default to use for untagged packets on interface
vpc Virtual Port Channel configuration
vtp Enable VTP on this interface
end Go to exec mode
exit Exit from command interpreter
pop Pop mode from stack or restore from name
push Push current mode to stack or save it under name
where Shows the cli context you are in
1,N5K version:
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_series_home.html
Copyright (c) 2002-2013, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
Software
BIOS: version 3.6.0
loader: version N/A
kickstart: version 6.0(2)N1(2)
system: version 6.0(2)N1(2)
Power Sequencer Firmware:
Module 1: version v5.0
Microcontroller Firmware: version v1.0.0.2
SFP uC: Module 1: v1.1.0.0
QSFP uC: Module not detected
BIOS compile time: 05/09/2012
kickstart image file is: bootflash:///n5000-uk9-kickstart.6.0.2.N1.2.bin
kickstart compile time: 3/14/2013 1:00:00 [03/14/2013 16:53:55]
system image file is: bootflash:///n5000-uk9.6.0.2.N1.2.bin
system compile time: 3/14/2013 1:00:00 [03/14/2013 19:28:50]
Hardware
cisco Nexus 5596 Chassis ("O2 48X10GE/Modular Supervisor")
Intel(R) Xeon(R) CPU with 8262944 kB of memory.
2,N5K port
Eth102/1/1 -- connected 101 full 1000 --
Eth102/1/2 -- connected 101 full 1000 --
Eth102/1/3 -- connected 101 full 1000 --
Eth102/1/4 -- connected 101 full 1000 --
Eth102/1/5 -- connected 101 full 1000 --
Eth102/1/6 -- connected 101 full 1000 --
Eth102/1/7 -- connected 101 full 1000 --
Eth102/1/8 -- connected 101 full 1000 --
Eth102/1/9 -- connected 101 full 1000 --
Eth102/1/10 -- connected 101 full 1000 --
Eth102/1/11 -- connected 101 full 1000 --
Eth102/1/12 -- connected 101 full 1000 --
Eth102/1/13 -- connected 101 full 1000 --
Eth102/1/14 -- connected 101 full 1000 --
Eth102/1/15 -- connected 104 full 1000 --
Eth102/1/16 -- connected 104 full 1000 --
Eth102/1/17 -- connected 104 full 1000 --
Eth102/1/18 -- connected 104 full 1000 --
Eth102/1/19 -- connected 104 full 1000 --
Eth102/1/20 -- connected 104 full 1000 --
Eth102/1/21 -- connected 104 full 1000 --
Eth102/1/22 -- connected 104 full 1000 --
Eth102/1/23 -- connected 104 full 1000 --
Eth102/1/24 -- connected 104 full 1000 --
Eth102/1/25 -- notconnec 102 auto auto --
Eth102/1/26 -- notconnec 102 auto auto --
Eth102/1/27 -- connected 106 full 1000 --
Eth102/1/28 -- connected 106 full 1000 --
Eth102/1/29 -- connected 104 full 1000 --
Eth102/1/30 -- connected 104 full 1000 --
Eth102/1/31 -- connected 104 full 1000 --
Eth102/1/32 -- connected 104 full 1000 --
Eth102/1/33 -- connected 104 full 1000 --
Eth102/1/34 -- connected 104 full 1000 --
Eth102/1/35 -- connected 104 full 1000 --
Eth102/1/36 -- connected 104 full 1000 --
Eth102/1/37 -- connected 104 full 1000 --
Eth102/1/38 -- connected 104 full 1000 --
Eth102/1/39 -- notconnec 1 auto auto --
Eth102/1/40 -- notconnec 1 auto auto --
Eth102/1/41 -- notconnec 1 auto auto --
Eth102/1/42 -- notconnec 1 auto auto --
Eth102/1/43 -- notconnec 1 auto auto --
Eth102/1/44 -- notconnec 1 auto auto --
Eth102/1/45 -- notconnec 1 auto auto --
Eth102/1/46 -- notconnec 1 auto auto --
Eth102/1/47 -- notconnec 1 auto auto --
Eth102/1/48 ZTC-Switch-48 connected 105 full 100 --
3,Fex
show fex 102 det
FEX: 102 Description: AO4-N2K-FEX102 state: Online
FEX version: 6.0(2)N1(2) [Switch version: 6.0(2)N1(2)]
FEX Interim version: 6.0(2)N1(2)
Switch Interim version: 6.0(2)N1(2)
Extender Serial: FOX1742G09B
Extender Model: N2K-C2248TP-E-1GE, Part No: 73-13671-02
Card Id: 149, Mac Addr: 64:e9:50:16:08:02, Num Macs: 64
Module Sw Gen: 21 [Switch Sw Gen: 21]
post level: complete
Pinning-mode: static Max-links: 1
Fabric port for control traffic: Eth1/3
FCoE Admin: false
FCoE Oper: true
FCoE FEX AA Configured: false
Fabric interface state:
Po102 - Interface Up. State: Active
Eth1/1 - Interface Up. State: Active
Eth1/2 - Interface Up. State: Active
Eth1/3 - Interface Up. State: Active
Eth1/4 - Interface Up. State: Active
Fex Port State Fabric Port
Eth102/1/1 Up Po102
Eth102/1/2 Up Po102
Eth102/1/3 Up Po102
Eth102/1/4 Up Po102
Eth102/1/5 Up Po102
Eth102/1/6 Up Po102
Eth102/1/7 Up Po102
Eth102/1/8 Up Po102
Eth102/1/9 Up Po102
Eth102/1/10 Up Po102
Eth102/1/11 Up Po102
Eth102/1/12 Up Po102
Eth102/1/13 Up Po102
Eth102/1/14 Up Po102
Eth102/1/15 Up Po102
Eth102/1/16 Up Po102show run int eth102/1/25 all
!Command: show running-config interface Ethernet102/1/25 all
!Time: Tue Apr 14 14:33:38 2009
version 6.0(2)N1(2)
interface Ethernet102/1/25
no description
lacp port-priority 32768
lacp rate normal
priority-flow-control mode auto
lldp transmit
lldp receive
no switchport block unicast
no switchport block multicast
no hardware multicast hw-hash
no hardware vethernet mac filtering per-vlan
cdp enable
switchport
switchport mode access
no switchport dot1q ethertype
no switchport priority extend
switchport access vlan 102
spanning-tree port-priority 128
spanning-tree cost auto
spanning-tree link-type auto
spanning-tree port type edge
spanning-tree bpduguard enable
no spanning-tree bpdufilter
speed auto
duplex auto
flowcontrol receive off
flowcontrol send on
no link debounce
no beacon
delay 1
snmp trap link-status
logging event port link-status default
logging event port trunk-status default
mdix auto
storm-control broadcast level 100.00
storm-control multicast level 100.00
storm-control unicast level 100.00
no shutdown lan
load-interval counter 1 30
load-interval counter 2 300
no load-interval counter 3
medium broadcast
channel-group 2025 mode active
no shutdown
show run int eth102/1/48 all
!Command: show running-config interface Ethernet102/1/48 all
!Time: Tue Apr 14 14:35:08 2009
version 6.0(2)N1(2)
interface Ethernet102/1/48
description ZTC-Switch-48
lacp port-priority 32768
lacp rate normal
priority-flow-control mode auto
lldp transmit
lldp receive
no switchport block unicast
no switchport block multicast
no hardware multicast hw-hash
no hardware vethernet mac filtering per-vlan
cdp enable
switchport
switchport mode access
no switchport dot1q ethertype
no switchport priority extend
switchport access vlan 105
spanning-tree port-priority 128
spanning-tree cost auto
spanning-tree link-type auto
spanning-tree port type edge
spanning-tree bpduguard enable
no spanning-tree bpdufilter
speed auto
duplex auto
flowcontrol receive off
flowcontrol send on
no link debounce
no beacon
delay 1
snmp trap link-status
logging event port link-status default
logging event port trunk-status default
mdix auto
storm-control broadcast level 100.00
storm-control multicast level 100.00
storm-control unicast level 100.00
no shutdown lan
load-interval counter 1 30
load-interval counter 2 300
no load-interval counter 3
medium broadcast
no shutdown
Ports are connected, there is no relationship with the speed option, such as port 102/1/1 is connected, but no speed option, port 102/1/47 is notconnected, there speed options.
show int eth102/1/1
Ethernet102/1/1 is up
Belongs to Po2001
Hardware: 100/1000 Ethernet, address: 64e9.5016.0802 (bia 64e9.5016.0802)
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is access
full-duplex, 1000 Mb/s
Beacon is turned off
Input flow-control is off, output flow-control is on
Switchport monitor is off
EtherType is 0x8100
Last link flapped 1d02h
int eth102/1/1
(config-if)# ?
beacon Disable/enable the beacon for an interface
cdp Configure CDP interface parameters
channel-group Configure port channel parameters
description Enter description of maximum 80 characters
inherit Inherit a port-profile
ip Configure IP features
ipv6 Configure IPv6 features
lacp Configure LACP parameters
link Configure link
lldp Configure Interface LLDP parameters
logging Configure logging for interface
mvr-group MVR interface config
mvr-type MVR interface config
mvr-vlan Interface MVR Config
no Negate a command or set its defaults
rate-limit Set packet per second rate limit
service-policy Configure service policy for an interface
service-policy Policy Map
shutdown Enable/disable an interface
snmp Modify SNMP interface parameters
spanning-tree Spanning Tree Subsystem
switchport Configure switchport parameters
untagged Default to use for untagged packets on interface
end Go to exec mode
exit Exit from command interpreter
pop Pop mode from stack or restore from name
push Push current mode to stack or save it under name
where Shows the cli context you are in
show int eth102/1/47
Ethernet102/1/47 is down (Link not connected)
Hardware: 100/1000 Ethernet, address: 64e9.5016.0830 (bia 64e9.5016.0830)
MTU 1500 bytes, BW 0 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is access
auto-duplex, auto-speed
Beacon is turned off
Input flow-control is off, output flow-control is on
Switchport monitor is off
EtherType is 0x8100
int eth102/1/47
(config-if)# ?
bandwidth Set bandwidth informational parameter
beacon Disable/enable the beacon for an interface
cdp Configure CDP interface parameters
channel-group Configure port channel parameters
default Set a command to its defaults
delay Specify interface throughput delay
description Enter description of maximum 80 characters
duplex Enter the port duplex mode
fex Configure FEX fabric
flowcontrol Configure interface flowcontrol
hardware FEX Card type
inherit Inherit a port-profile
ip Configure IP features
ipv6 Configure IPv6 features
lacp Configure LACP parameters
link Configure link
lldp Configure Interface LLDP parameters
load-interval Specify interval for load calculation for an interface
logging Configure logging for interface
mac MAC
mac-address Configure interface mac address
mvr-group MVR interface config
mvr-type MVR interface config
mvr-vlan Interface MVR Config
negotiate Configure link negotiation parameters
no Negate a command or set its defaults
priority-flow-control Enable/Disable PFC
rate-limit Set packet per second rate limit
service-policy Configure service policy for an interface
service-policy Policy Map
shutdown Enable/disable an interface
snmp Modify SNMP interface parameters
spanning-tree Spanning Tree Subsystem
speed Enter the port speed
storm-control Configure Interface storm control
switchport Configure switchport parameters
untagged Default to use for untagged packets on interface
vpc Virtual Port Channel configuration
vtp Enable VTP on this interface
end Go to exec mode
exit Exit from command interpreter
pop Pop mode from stack or restore from name
push Push current mode to stack or save it under name
where Shows the cli context you are in -
Adding N2K to existing infrastructure
Hi,
I have to add a pair of N2Ks to Existing N5Ks. There is already a pair of N2Ks attached to N5Ks.
What are the steps required to perform this task ? Also, can I combine FETs with SFPs for N2K connection on a single switch.
Do I need any downtime for the already connected N2K and N5K or any service disruption during this activity?
ThanksHi,
What are the steps required to perform this task ? Rack the 2ks and run the cables to 5ks and plug in the SFP+s or FETs on both sides. If the link comes up create your VPC config and than do a "sh fex" if all configured correctly you should see the new FEXs online.
can I combine FETs with SFPs for N2K connection on a single switch.
No, use FETs or 10Gig SFP+. Every 2k comes 4 FETs in the box so that should be enough to connect the FEX to both 5ks using 10Gigs.
Do I need any downtime for the already connected N2K and N5K or any service disruption during this activity?
No, no need for any downtime. Your old FEXs should be untouched.
HTH -
Hi,
I have following Queries in the Nexus. Please help me with information.
•1. M1, M2 & F2 cards in N7K, which one will be used for Routing & Switching?
•2. vPC primary Nexus 7K & vPC secondary Nexus 5K. It will support? & why?
•3. Port-channel between N7K & N2K mandatory to communicate hosts connected to N2Ks?
•4. By default why VTP mode is Transparent in Nexus Switches? But in IOS by default Server mode.
Thanks
VenkatWhen configuring a single sided vPC both switches must be the same model, ie a pair of N5Ks or a pair of N7Ks. With vPC each switch retains its own control plane and data plane. Control messages and data frames flow between the active and standby switches via the peer link.
With double sided vPC you can have a pair of N5Ks and a pair of N7Ks. See the link below for details:
https://supportforums.cisco.com/docs/DOC-20836 -
Hello,
i have a pair of N7k's connected to each other by fabricpath. Southbound the n7k's are connected to n5k's, also connected by fabricpath. Northbound the n7k's are connected to the ip core routers. The connection to the IP core router is an SVI100 (vlan mode ce) that is attached to a port-channel
I have created a fabricpath vlan 101 on all the switches and the SVI is on both n7k's and i'm running HSRPv2 between the n7k's. The left n7k is the active node.
n7k (left)
interface Vlan101
no shutdown
vrf member public
no ip redirects
ip address 1.1.1.2/26
hsrp version 2
hsrp 101
preempt
priority 105
ip 1.1.1.1
interface port-channel1
description peer-link to n7k right
switchport mode fabricpath
bandwidth inherit
vpc peer-link
n7k (right)
interface Vlan101
no shutdown
vrf member public
no ip redirects
ip address 1.1.1.3/26
hsrp version 2
hsrp 101
ip 1.1.1.1
On both n7k's the arp table is filled. Only from the n7k left i can't ping the 1.1.1.3 with a source ip address from vlan 100 (uplink ce vlan). When i don't use the source vlan 100 ip address, the ping works.
Why can't i ping the ip address 1.1.1.3 from the n7k left when i'm using the source ip address from vlan 100?
kind regards,
Pascal LacroixHi,
Yes this is possible, and indeed we're doing something very similar to what you're proposing.
We have Nexus 7K spine switches, which are also the L3 boundary running vPC+, and these are connected via standard IEEE 802.1Q trunks to standard STP capable switches.
The area to be mindful of is that a FabricPath CE (Classic Ethernet) ports behave as if running STP "root guard" and as such will become disabled if they receive a superior STP BPDU e.g., one with a lower priority. You'll see a SYSLOG message along the lines of %STP-2-L2GW_BACKBONE_BLOCK if this occurs.
There's more detail on this in the FabricPath Versus Classical Ethernet Networks section of the Cisco Nexus 5000 Series NX-OS Operations Guide.
The other document on FP that would be worth looking through is Mark Stinnette's Quick Start Guide :: FabricPath. This is a cook book style configuration guide, and some of the "recipes" shown deal with exactly this and need to ensure the FP domain is the STP root.
Regards -
N5K - single point of failure?
When both N5K (running 4.2(1)N1(1b) are powered down, if one of them fails to power up, all N2K connected to the two N5K fails to power up. This scenario could happen in situation where there is a power maintainence when both N5K are brought down. It looks like it is related to the below. Beginning with Cisco NX-OS Release 5.0(2)N1(1), you can configure the Cisco Nexus 5000 Series switch to restore vPC services when its peer switch fails to come online by using the reload restore command. You must save this setting in the startup configuration. On reload, Cisco NX-OS Release 5.0(2)N1(1) starts a user-configurable timer (the default is 240 seconds). If the peer-link port comes up physically or the peer-keepalive is functional, the timer is stopped. Can anyone confirm that ? Thanks Eng Wee
This design option works
However keep in mind that your design has single point of failure in the nexus side if you need it end to end redundant you need to consider adding a second switch to the topology
Hope this help
Sent from Cisco Technical Support iPad App -
Hi
We are trying to set up a vPC between a HP server and two N2K (connected to Nexus 7009).
vPC does not work if we plug HP server NIC1 and NIC2 into the same port on both N2Ks like Eth 101/1/1
vPc works when we if we plug HP serve NIC1 and NIC2 into diffrent port on both N2Ks like N2K1 port Eth101/1/1 and N2K2 port Eth 101/1/32
Please advise
Regards,
NomiPlease show vpc config and interface config of switch
-
Nexus 7004 with N2K-B22HP-P FEX won't connect
Hello
I'm trying to connect an HP Blade server with an N2K-B22HP-P to our Nexus 7004 but it stays in de download mode.
# sh fex
FEX FEX FEX FEX
Number Description State Model Serial
116 FEX0116 Image Download N2K-B22HP-P FOCxxxxxxxx
# sh fex detail
FEX: 116 Description: FEX0116 state: Image Download
FEX version: 5.2(1)N1(1a) [Switch version: 6.1(4)]
FEX Interim version: 5.2(1)N1(1a)
Switch Interim version: 6.1(4)
Module Sw Gen: 12594 [Switch Sw Gen: 21]
pinning-mode: static Max-links: 1
Fabric port for control traffic: Eth3/44
Fabric interface state:
Po116 - Interface Up. State: Active
Eth3/44 - Interface Up. State: Active
Fex Port State Fabric Port
Logs:
08/07/2013 18:04:24.424401: Requesting satellite to download image
08/07/2013 18:04:46.442690: Module register received
08/07/2013 18:04:46.443233: Registration response sent
08/07/2013 18:04:46.443516: Requesting satellite to download image
08/07/2013 18:05:10.475657: Module register received
08/07/2013 18:05:10.476109: Registration response sent
08/07/2013 18:05:10.476390: Requesting satellite to download image
08/07/2013 18:05:36.703639: Module register received
08/07/2013 18:05:36.704118: Registration response sent
08/07/2013 18:05:36.704434: Requesting satellite to download image
08/07/2013 18:06:04.741774: Module register received
08/07/2013 18:06:04.742505: Registration response sent
08/07/2013 18:06:04.742628: Requesting satellite to download imageHi Martin,
At this point in time the N2K-B22-HP FEX is not supported with the Nexus 7000 series switches as the parent switch. If you look at Table 2 in the Cisco Nexus B22 Blade Fabric Extender Data Sheet you'll see it only lists the following:
Cisco Nexus parent switch model or line card
Cisco Nexus 5010 or 5020 Switch for Cisco Nexus B22HP and B22F
Cisco Nexus 5548P Switch
Cisco Nexus 5548UP Switch
Cisco Nexus 5596UP Switch
Cisco Nexus 6001 Switch
Cisco Nexus 6004 Switch
Regards -
Can you Connect Cisco switch modules for to N2K?
I have not seen anything about connecting Cisco Switch modules for Blade Chassis to fex. Does anybody now if you can do that?
thank you.thank you Lucien.
I think you got a right name for N2Ks, a NIC card extender. In my opion N2K should be able to support Blade switches. Not every company has just rack mount servers, most enviroment is mixed. In my case, I run out ports on N5K, but plenty available on N2K. I want add two more blade centers with gig switch modules in them. now I have to buy a N5K!!!. I'm sure Cisco can make N2K to support switches too. -
LACP suspended between N7K and N2K
Hi
we have a creation trouble between N7K and N2K on port-channel, the port-channel is suspended because LACP receive PDUsWith FEX you use don't use the mode active.
Interface eth5/33
switchport mode fex-fabric
channel-group 70
The FEX uses a "Fabric" header on the link, and doesn't require LACP. You can use LACP on any host ports on the FEX, just not on the fabric links. -
Multicast clustering IBM servers with N7K and 2k
i have two severs IBM are working as a cluster and connected to Fiber fabric extender 2K using VPC as per attached diagram
two IBM server are woriking fine for network connectivity with N2k but the servers have a multicast named ( power HA 7.1) to work as acluster
but i tried to configue multicat in N7K and N2k to server working as acluster but the servers are not working
please advice me about the configuration in N7K and N2k to working IBM servers as a cluster .One option is the IGMP querier:
config t
ip igmp snooping
vlan 2
switch(config-vlan-config)# ip igmp snooping querier 10.0.10.253
(or a good source address of the interface)
The other option is run PIM on the VLAN interface:
feature pim
vlan 2
ip pim sparse-mode
Both has the same purpose: combined with IGMP snooping, the L3 interface will flood the VLAN with IGMP queries that traverse the inter-switch links. As a result, the inter-switch links will be included in the snooping port list. In turn,
packets destined to 228.5.10.5 will be sent out the inter-switch link and reach the other server.
Without the IGMP queries, 228.5.10.5 packets will not be sent from one switch to the other as it is not in the 224.0.0.0/24 range. -
Nexus 7000 w/ 2000 FEX - Interface Status When N7K has power issues
I have multiple nexus 2Ks connected to two N7Ks with my servers connecting to multiple N2Ks accordingly with dual NIC failover capability.
What happens, or what state do the N2K interfaces go into if one of my N7K's looses power given the N2K is effectivly still receiving power?Hi Ans,
You are rigth, I have defaulted againt the port, now configured with switchport mode FEX, and now the FET-10G is validated
NX7K-1-VDC-3T-S1-L2FP(config-if)# description FEX-101
NX7K-1-VDC-3T-S1-L2FP(config-if)# switchport
NX7K-1-VDC-3T-S1-L2FP(config-if)# switchport mode fex-fabric
NX7K-1-VDC-3T-S1-L2FP(config-if)# fex associate 101
NX7K-1-VDC-3T-S1-L2FP(config-if)# medium p2p
NX7K-1-VDC-3T-S1-L2FP(config-if)# channel-group 101
NX7K-1-VDC-3T-S1-L2FP(config-if)# no shutdown
NX7K-1-VDC-3T-S1-L2FP(config-if)#
NX7K-1-VDC-3T-S1-L2FP(config-if)# sh int e7/33 status
Port Name Status Vlan Duplex Speed Type
Eth7/33 FEX-101 notconnec 1 auto auto Fabric Exte
NX7K-1-VDC-3T-S1-L2FP(config-if)#
Thanks for your help, and have a nice weekend.
Atte,
EF -
WAN Router Connection to Data Center
We have a WAN router that needs to connect to our Data Center network. The Data Center consists of two N7K core switches, with a pair of N5K switches as aggregation, and each N5K has twelve N2K fabric extenders. The N2Ks are single-homed to the N5Ks. The N5Ks are vPC connected to the N7Ks.
We would like to attach the WAN router to both N7K switches in the Data Center. The N7K switches only have 10G ports in them, so we can't terminate the WAN router directly to the N7Ks.
I was considering creating one dedicated VLAN on each N7K, and assigning an SVI to each VLAN, to correspond to the L3 connections between the N7Ks and the WAN router. Then, we could trunk these VLANs to each of the N5Ks, and configure one 1G port on each N5K for the VLAN, and connect the WAN router to the N5Ks.
Two questions regarding this design:
1) Is there a problem in connecting the L3 WAN router to the N7K via the N5K?
2) Does vPC connectivity between the N7K and N5K pose a problem for the proposed WAN connectivity?
Thanks in advance for any feedback.
-rbThe vPC between N5K and N7K is the catch here. Layer-3 routing over vPC member ports is currently not supported so I will advise you to stay away from this approach.
Atif -
Connecting 4 Nexus 2000 with Nexus 7000
Hi ,
I have two N7K-F248XP-25 going to be installed in one Nexus 7009 and I have 4 N2K-C2248TP-1GE (48x100/1000-T+4x10GE) .
In simple way, I have two F2 line cards within one N7K and 4 N2Ks. The N7K will be used as a parent switch and it has NX-OS version 6.0
So I want to connect the 4 N2K to the two F2 line cards in a redundant fasion, can some one tell me the best practice of how to connect those N2Ks?
I have read somewhere that I can only use two ports from each 4 shared ports but I am not sure if this is true. I will appreciate any input or a link.
ThanksThat was Awesome link! Thanks indeed.
So can you please confirm if I am following the F2 + FEX rule
Again, I have only one Nexus 7009 and 4 x N2K , so I have two F2 cards on the Nexust 7009. Here is my connectivity plan:
1st N2K to port 1 on the first F2
1st N2K to port 1 on the second F2
2nd N2K to port 2 on the first F2
2nd N2K to port 2 on the second F2
3rd N2K to port 3 on the first F2
3rd N2K to port 3 on the second F2
4rth N2K to port 4 on the first F2
4rth N2K to port 4 on the second F2
So eventually , I am planning to use one group (4 ports) on each F2 card for all the connectivity to those N2K Switches.
Also, I will have a total of 4 port channels .. right ? 1 Port channel for each N2K
I will appreciate your feedback!
Maybe you are looking for
-
I forgot my username for my iMac
Hi, I am completely untechnical, so please help me in simple language!! I just returned from vacation and my MacBook had run out of battery. I haven't signed in for ages, as it was always turned on up til now and I had no need to sign in. I had to ch
-
How to read a txt file and update DB table
I have to read a table which has some entries in it as plain text file, then I should update my table if the table entries and the data in text file are NOT MATCHING o.w. keep the table entry as it is
-
I want to put a HTML webpage into a certain field that is scrollable and when a link is clicked that box will change to give the content from the new page in that field ... please help, and also can javascript hover-off links from a webpage be put in
-
Emptying iPhoto trash causes iP crash
and it rhymes! Using latest version of iPhoto, I was deleting a number of photos a week ago or so when iPhoto crashed. When I re-opened iP after a restart, everything seemed okay, so I proceeded to add more photos to the trash folder and tried again.
-
Any key to quickly switch between controllers in Piano Roll?
in the LPX PIano Roll, can we use key commands or ipad Remote app to quicly switch between different midi controllers? Like switch between modulation/foot control, etc.