Nexus 5548 SPAN Destination- Dual Homed FEX

I understand that order to setup a SPAN monitor session, only 5K local ports can be destination ports. Our FEX are dual homed, so I know we have to have the monitor session configured on both 5K's. We are wanting to connect an Infinistream sniffer to the destination port. What I am confused about is do we also have to have 2 destination ports, one on each 5K connecting to the Infinsitream or can we just use one?

You cannot set more than one destination to a monitor session. You can have multiple source interfaces, but only one destination. Try this:
destination interface e2/14
You will need to create two more separate monitoring session with the same source interfaces but set the destination to the other two interfaces.
HQ-N5k-2(config-if-range)# monitor session 1
HQ-N5k-2(config-monitor)# source interface e1/17 both
HQ-N5k-2(config-monitor)# destination interface e2/14
HQ-N5k-2(config-if-range)# monitor session 2
HQ-N5k-2(config-monitor)# source interface e1/17 both
HQ-N5k-2(config-monitor)# destination interface e2/15
HQ-N5k-2(config-if-range)# monitor session 3
HQ-N5k-2(config-monitor)# source interface e1/17 both
HQ-N5k-2(config-monitor)# destination interface e2/16
Please rate if helpful

Similar Messages

Single Homed or Dual Homed FEX

With the ability to do enhanced VPCs now on the FEXs is there any benefit to have a mixture of having of single attached FEXs and dual homed FEXs?
Here are some benefits as I see them
Single homed FEX is easier to trouble shoot as the topology is not as complex.
A dual homed FEX will support both dual attached hosts and a single attached host. So this means we only have one topology to deal with (everything dual homed)
Any other pros or cons?
Thanks

If you have any servers with only one uplink, you want dual homed FEXes for redundancy.
Also, it depend on the number of FEXes you are connecting to the same set of switches. For example: the max number of FEXes that can be uplinked to a set of 6k switches is 24 if you are dual homed, but if you are single homed the max is 48 (24 per switch).
HTH

Dual-homed FEX

Looking for some guidance with a problem. I have 3 Nexus 2248T switches dual homed to 2 Nexus 5672 in the core. (See Attachment)
Problem: on one of the FEX I have an Exchange NLB cluster. Several of our systems that require POP3 mail to communicate messaging have experience connectivity issues (unable to send mail) and require the connection to be hard coded to one of the IP Address in a cluster server instead of the NLB address.
Configuration: I have not setup Spanning-tree on the trunk ports from the 5672s and am showing that BPDU guard is disabled for the edge ports.
Nexus5672-1# sh spanning-tree summary totals
Switch is in rapid-pvst mode
Root bridge for: none
Port Type Default is disable
Edge Port [PortFast] BPDU Guard Default is disabled
Edge Port [PortFast] BPDU Filter Default is disabled
Bridge Assurance is enabled
Loopguard Default is disabled
Pathcost method used is short
STP-Lite is enabled
Question: I am thinking I missed the "boat" on the configuration and need to include spanning-tree at the port level to correct the problem. Any advice please?

You don't need spanning tree config at the FEX level. You just need spanning tree on the 5762 devices to determine what device is the root and what device is the backup root.
HTH

Dual homed FEX configuration

Hi,
Have a question on dual homes FEX's
I have a FEX that's dual homed to 02 Nexus 5K'S
Lets say my FEX is 150 and if I want to configure port 150/1/1 to vlan 100, do I need to login to both Nexus 5K's and configure the port 150/1/1 to vlan 100?
OR Can config sync help
Thanks
stan

This is the wrong forum for this topic, but I'll assist.
Without configuration sync enabled, you would have to configure both Nexus 5K exactly the same for the FEX port before traffic will forward.
Configuration sync would help you in only having to configure it once, but I have had mixed results using configuration sync so I tend not to use it in my deployments.

Dual homes FEX's N5K upgarde to 6.0 version

Hi,
I am planning ot have upgrades for N5K's which have dual homed FEX's and some catalyst switches connections to N5K's using vpc's and spanning tree port type network topology.
Now I have feq small queries.
1]Does ISSU pre-upgarde commands cuase nay discruption in services ?
eg :
sh install all impact
show incompatibility command
2] If Fex's are dual homed and could support ISSU, but due to some topology issues N5K's could not support ISSU, what could be best way to upgrade.
Regards
Ajay

One thing to keep in mind if you use multiple computers. Songs purchased with iTunes 6 can't be used by iTunes 4. So if you upgrade one machine to iTunes 6 you should upgrade all your computers to iTunes 6. Atleast if you want to share music between them.
Other than that there have been some changes to iTunes 6, but I can't remember off hand what functionality was in iTunes 4.7.1 as compared to the latest version. Maybe Apple has a version checklist somewhere on their site.
I'm sure some others will chime in with more answers but I see no reason why you shouldn't upgrade to iTunes 6.

Nexus 7000 and 2000. Is FEX supported with vPC?

I know this was not supported a few months ago, curious if anything has changed?

Hi Jenny,
I think the answer will depend on what you mean by is FEX supported with vPC?
When connecting a FEX to the Nexus 7000 you're able to run vPC from the Host Interfaces of a pair of FEX to an end system running IEEE 802.1AX (802.3ad) Link Aggregation. This is shown is illustration 7 of the diagram shown on the post Nexus 7000 Fex Supported/Not Supported Topologies.
What you're not able to do is run vPC on the FEX Network Interface that connect up to the Nexus 7000 i.e., dual-homing the FEX to two Nexus 7000. This is shown in illustrations 8 and 9 of under the FEX topologies not supported on the same page.
There's some discussion on this in the forum post DualHoming 2248TP-E to N7K that explains why it's not supported, but essentially it offers no additional resilience.
From that post:
The view is that when connecting FEX to the Nexus 7000, dual-homing does not add any level of resilience to the design. A server with dual NIC can attach to two FEX so there is no need to connect the FEX to two parent switches. A server with only a single NIC can only attach to a single FEX, but given that FEX is supported by a fully redundant Nexus 7000 i.e., SE, fabrics, power, I/O modules etc., the availability is limited by the single FEX and so dual-homing does not increase availability.
Regards

How to replace Nexus5596 with dual-homing N2K

What is the correct process to replace a FEX parent switch with dual-homing fex?
Traffic should not be interrupted.

Hi
Do you have VPC between Parent Switches & are you running VPC on dual homed FEX fabric ports. ?
If yes Below is the procedure,
1) boot the replacement switch without VPC, peer-links & FEX ports connected to it.
2) Make sure it has same Software version matches with the peer switch.
3) enable Pre-Provisioning for slots with appropriate FEX model.
, here find the guide:
http://www.cisco.com/en/US/partner/docs/switches/datacenter/nexus5000/sw/system_management/521_n1_1/b_5k_System_Mgmt_Config_521N11_chapter_0100.html#task_05BB53AD7AFB49CF9A8E4A5C6C37CB38
So, on the replacement switch you will pre-provision the Fabric Extender and configure the ports so it will be ready when you add the module to the RMA SW.
Please make sure you put the appropriate FEX model on the provision slot, otherwise, when connected it will not come Online
Example, FEX 110:
N5K(config)# slot 110
N5K(config-slot)#provision model N2K-C2248T
4) Now keep all ports at Shut down state Then Configure Entire switch that includes FEX host ports, FEX Fabric Ports & VPC peer-link, VPC Domain Configuration.
keep FEX host ports in shut state.
5) keep VPC Role priority on existing switch lower than , new switch
6) Connect Peer-link ports to Peer switch & wait till VPC Comes up-
7) Then connect Fabric ports from FEX to the pre-configured ports on replacement switch
After it comes online Unshut FEX host ports.
I got similar steps here as well
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/operations/n5k_vpc_ops.html#wp425197
NOTE: I followed same process however, few ping drops were seen....arnd ( 5- 6 ping loss) only on few hosts...
Mazhar

N5K - N2K Image Upgrade Single vs Dual Homed

Hi,
The upgrade distuptive behaviour is not explained well in the following documentation link . Especially about single homed FEX topology.
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/upgrade/503_N1_1/n5k_upgrade_downgrade_503.html
1. I have just upgraded a dual homed Active / Active N2K to N5K environment as below. The downtime was exactly explained as above URL, just the time to reload the FEXs. Which was about 1.5 minutes or so...
Or should we NOT reload all the FEXs almost simultaneously by manual command (as mentioned in the upgrade guide) in this topology, in order to minimize the downtime ?
2.However I am curious if there would be any downtime in a single homed FEX topology as below. My guess is there would be just the downtime for the edge server to distribute the traffic to the other N2K.
I guess if the downtime is really a biggy, then the second topology is easier to manage.
Comments area very much appreciated.
Dumlu

I am not able to see the images you attached, could you please try reinserting them?
Also if I am understanding your question correctly, you are wanting to know if there will be downtime, if you upgrade a N5K with a 2K single homed. I assume you meaning something similar to this?
If so, yes the single home fex would be reloaded per the document it states: "Upgrade the first vPC switch (vPC primary switch) - during this upgrade, the switch will be reloaded. When the switch is reloaded, any dual-homed FEX will not be reloaded. Only singled-homed FEXs are reloaded. Servers connected to these dual-homed FEXs retain network connectivity via the second (vPC secondary) switch"

Nexus 2K FEX dual-homed to two Nexus 5K Configuration

Hi.
I am trying to look for Nexus 5K config when the nexus2K FEX is dual-homed into it.
What will be the configuration on both 5K especiall the pinning?
Assuming one N2K 10G port is connected to N5K-1 and another N2K 10G port connected to N5K-2?
N5Ks are also configured as dual-sided vpc with two N7K.
thanks

N5k-1 ====vpc peer==== N5k-2
\ E1/10 E1/10 /
\ Fex-100 /
N5k-1 & N5k-2 config:
===============
Interface po100
switchport mode fex-fabric
fex associat 100
vpc 100
int e1/10
switchport mode fex-fabric
channel-group 100

NX-OS firmware Upgradation in Nexus 5548 with Enhanced vPC with Dual Active FEX

Hi All,
Please tell me how to do "NX-OS firmware Upgradation in Nexus 5548 with Enhanced vPC with Dual Active FEX" without downtime for FEX.
The Server are connected to FEX.
Attached the diagram.

Hi,
If the 5500s are layer-2 with vPC running between them than you can use ISSU to upgade.
here is doc to follow:
ISSU Support for vPC Topologies
An ISSU is completely supported when two switches are paired in a vPC configuration. In a vPC configuration, one switch functions as a primary switch and the other functions as a secondary switch .They both run the complete switching control plane, but coordinate forwarding decisions to have optimal forwarding to devices at the other end of the vPC. Additionally, the two devices appear as a single device that supports EtherChannel (static and 802.3ad) and provide simultaneously data forwarding services to that device.
While upgrading devices in a vPC topology,you should start with the switch that is the primary switch. The vPC secondary device should be upgraded after the ISSU process completes successfully on the primary device. The two vPC devices continue their control plane communication during the entire ISSU process (except when the ISSU process resets the CPU of the switch being upgraded).
This example shows how to determine the vPC operational role of the switch:
link:
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/upgrade/513_N1_1/n5k_upgrade_downgrade_513.html
HTH

Reducing the fex time for N2K dual homed to N5K

Hi,
We have N2K dual homed to 2 N5K. The N2K registers the fex with one of the N5K. But when one of the N5K fails it takes more than a minute to register with the second N5K.
How can we reduce this delay so that there is minimum timeout between failover ?

Hi David,
I just noticed that the VPC is DOWN, I think this is the root problem. Any suggestions on this ?
DC-ACC-2# show vpc
Legend:
                (*) - local vPC is down, forwarding via vPC peer-link
vPC domain id                   : 5
Peer status                     : peer link is down
vPC keep-alive status           : Suspended (Destination IP not reachable)
Configuration consistency status: failed
Per-vlan consistency status     : success
Configuration consistency reason: Consistency Check Not Performed
Type-2 consistency status       : success
vPC role                        : none established
Number of vPCs configured       : 1
Peer Gateway                    : Disabled
Dual-active excluded VLANs      : -
Graceful Consistency Check      : Disabled (due to peer configuration)
vPC Peer-link status
id   Port   Status Active vlans
1    Po5    down   -
vPC status
id     Port        Status Consistency Reason                     Active vlans
5      Po1         down   failed      Consistency Check Not      -
                                      Performed

Nexus 5548 fex interface configuration in vPC scenario

Hello Forum Team!
I have a pair of Nexus 5548UP configured as a vPC domain active-standby couple with six Nexus 2248TP Fex's in a dual-homed scenario (each fex is connected to each 5548UP). At the same time, both 5548UP are dual-homed to a pair of VSS Catalyst 6509.
I have a couple of questions regarding performance and configuration:
1. When configuring a fex interface, I've noticed that if the configuration is not the same or replicated on both 5548UP, the fex interface won't come up; is this normal behaviour? For now I am replicating manually the configuration on both 5548UP (not confyg-sync).
2. When performing ICMP tests from the 2248TP to the VSS, the response time is around 1ms to 2ms; from the 5548UP to the VSS pair is approximately 0.5ms. Is that normal delay response time from the 2248TP? I was expecting less response time from the 2248TP (the fex's have 20 Gigs of uplink bandwidth to the 5548UP pair and the 5548UP pair have 40 gig's of bandwidth to the VSS pair).
Thanks in advanced team!

Hi,
1. When configuring a fex interface, I've noticed that if the configuration is not the same or replicated on both 5548UP, the fex interface won't come up; is this normal behaviour?
Yes, that is a normal behavior. Since yours FEXes are connected to BOTH 5ks, you have to configure both 5Ks in order for the FEX to come up. If you connect your FEX physically to only one 5k, then you only configurethat one 5k, but in your case you need to configure both 5ks exactly the same.
2. When performing ICMP tests from the 2248TP to the VSS, the response time is around 1ms to 2ms; from the 5548UP to the VSS pair is approximately 0.5ms. Is that normal delay response time from the 2248TP? I was expecting less response time from the 2248TP (the fex's have 20 Gigs of uplink bandwidth to the 5548UP pair and the 5548UP pair have 40 gig's of bandwidth to the VSS pair).
I have never tested this, but I would think since the 2k needs to to 5k for every packet including talking to another host on the same 2k, the delay would slightly be higher then when you ping directly from the 5k.
HTH

SPAN in Nexus 5548

Hello All,
Please find the attached diagram.
In N7K has SVI for VLAN 115 & 135 and N5Ks has L2 VLAN for 115 & 135.
Requirement is to SPAN all the traffic leaving IN/OUT of both VLANS needs to forwarded to Ethanalyzer which is connected in N5K.
If I configure SPAN in 5K will it capture all the traffic both IN/OUT traffic in those both VLANS. Nexus 7K has the gateway but no servers are connected on that switch. By configuring SPAN in 5K will it fulfil our requirement ?
If not then can i configure ERSPAN source in Nexus 5K and move my Ethanalyzer to Nexus 7K and make that port as ERSPAN destination ? Will this work out ?
Thanks in advance.

span in general is oversubscribed feature. span traffic gets rate limited only during period of congested span. Congestion of span could occur under following circumstances:
- when we have total of more than 10gig traffic being monitored over multiple 10gig ports to one 10gig port (span destination oversubscription)
- when we are monitoring more than 5gig per port with multiple such ports to single 10gig port (fabric link oversubscription)
if this is just single 10gig to single 10gig port span, then we should be able to span upto 5gig
without a problem, after which rate limiting would kick in for the reasons you mentioned before.
Vin

Dual homed server to dual homed Nexus fabric extenders

I don't see anything in Cisco docs that explicitly say that this is a supported setup so I just wanted to see if anyone here has any insight on this.
Is it supported to dual home a server via etherchannel to a pair of Nexus fabric extenders that are themselves dual homed two a pair of Nexus 5Ks?
Thanks!

If i understand correctly i think what you are referring to is Enhanced vPC. See this link for details -
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/mkt_ops_guides/513_n1_1/n5k_enhanced_vpc.html
Jon

FCoE with Cisco Nexus 5548 switches and VMware ESXi 4.1

Can someone share with me what needs to be setup on the Cisco Nexus side to work with VMware in the following scenario?
Two servers with two cards dual port FCoE cards with two ports connected to two Nexus 5548 switches that are clusterd together. We want to team the ports together on the VMware side using IP Hash so what should be done on the cisco side for this to work?
Thanks...

Andres,
The Cisco Road Map for the 5010 and 5020 doesn't include extending the current total (12) FEX capabities. The 5548 and 5596 will support more (16) per 55xxk, and with the 7K will support upto 32 FEX's.
Documentation has been spotty on this subject, because the term 5k indicates that all 5000 series switches will support extended FEX's which is not the case only the 55xx will support more than 12 FEX. Maybe in the future the terminology for the 5k series should be term 5000 series and 5500 series Nexus, there are several differences and advancements between the two series.

Nexus 5548 SPAN Destination- Dual Homed FEX

Similar Messages

Maybe you are looking for