Adapter-fex Supported VICs and Nexus Switches

HI,
I am thinking of using C220M4 in standalone mode. I have been reading about adapter-fex and I am wondering which Cisco VIC supports adapter-fex and which Nexus Switch will support adapter-fex.
I am thinking of using a VIC1225 and Nexus 3000.
Thanks.

I believe that adaptor fex is supported only with Nexus 5k and N2k:
Network Adapter Virtualization Design (Adapter-FEX) with Cisco Nexus 5500 Switches and Cisco Nexus 2232 Fabric Extenders
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/guide_c07-690080.html
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/data_sheet_c78-657397.html

Similar Messages

VPC between server and nexus switches

Hi all,
I would like to ask following question:
We are using virtual portchannels to connect e.g. ESXi-Servers with trunks on two Nexus switches. When the switch "rz2sw1" has gone faulty, we expect that the trunk connections between switch rz2sw2 would still work. That's the reason why they are built. But they didn't as you can see in the screenshot (attaced) former mail.
Do you know what can be problem.. thank you

It appears that the peer-link was down. If the peer-link is down and the keep-alive is still up, the secondary device will shutdown all of it's VPC links to ensure dual active (split brain) is avoided.
On a Nexus 7000, its recommended to use a front panel (data port) for the keep-alive instead of the management port. My assumption would be that you are using the MGMT0 for keep-alive and all front panel ports went off-line. If you use a front panel port for keep-alive and all line cards go off line on the primary, the secondary will take over as expected.

SNMP OIDs to identify port mode setting on 3750, 6509 and Nexus switches

Is there and OID I can use to determine if a port is setup as an access or trunk port?
Thanks

Hi Jeff,
for the c6500 I use CISCO-STACK-MIB::vlanPortIslOperStatus
vlanPortIslOperStatus.13.43 = notTrunking
vlanPortIslOperStatus.13.44 = trunking
and for the Catatlyst 2k/3k CISCO-VTP-MIB::vlanTrunkPortDynamicStatus:
vlanTrunkPortDynamicStatus.1 = notTrunking
vlanTrunkPortDynamicStatus.50 = trunking
! ifIndex
Unfortunately I don't have any Nexus yet.
HTH
Rolf

Store and Forward Switching

Hello,
Quick question, does a Cisco 3750 switch support store and forward switching? If so, is it default? If not, is there a command for it?
I know the 3550's support S&F as default and if the 3750's do then it may resolve my issue.
Thanks
Wayne

Thanks Bobby. In terms of raw switching is there any other differences between the 3550 and 3750?
The reason I ask is I ran a BERT test on two pieces of equipment over a 3750 and it fails the test. Over a 3550 is passes.
Both switches have an IP address for VLAN 1 and portfast and that's it, can't be simpler.
I'm just wondering whether something is on as default on the 3550 but off as default on the 3750????????
Many thanks,
Wayne

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

Adapter FEX and VM Fex

Hi!
I have a questions about Cisco Adapter FEX and VM Fex.
As i understand, Cisco Adapter FEX gives multiple vNIC on one mezzanine card, and each of them appears as virtual port on Fabric Interconnect.
Also, same thing for VM-FEX, each VM NIC appears as virtual port on Fabric Interconnect.
Am i right?
Thank you!

Adaptor FEX is I/O adaptor virtualization, which is agnostic to the OS and therefore works in virtualized as well as non virtualized environments.
VM-FEX (also called Hypervisor Bypass) is available for different Hypervisors
Cisco UCS Manager VM-FEX for Hyper-V CLI Configuration Guide, Release 2.2
Cisco UCS Manager VM-FEX for KVM CLI Configuration Guide, Release 2.2
Cisco UCS Manager VM-FEX for VMware CLI Configuration Guide, Release 2.2
Cisco UCS Manager VM-FEX for Hyper-V GUI Configuration Guide, Release 2.2
Cisco UCS Manager VM-FEX for KVM GUI Configuration Guide, Release 2.2
Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide, Release 2.2
Cisco UCS Manager VM-FEX for Hyper-V CLI Configuration Guide, Release 2.1
Cisco UCS Manager VM-FEX for KVM CLI Configuration Guide, Release 2.1
Cisco UCS Manager VM-FEX for VMware CLI Configuration Guide, Release 2.1
Cisco UCS Manager VM-FEX for Hyper-V GUI Configuration Guide, Release 2.1
Cisco UCS Manager VM-FEX for KVM GUI Configuration Guide, Release 2.1
Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide, Release 2.1
Cisco UCS Manager VM-FEX for KVM CLI Configuration Guide
Cisco UCS Manager VM-FEX for KVM GUI Configuration Guide
Cisco UCS Manager VM-FEX for VMware CLI Configuration Guide
Cisco UCS Manager VM-FEX for VMware GUI Configuration Guide
example VM-FEX for VMware ESX
VM-FEX (previously known as VN-link) is a method to extend the network fabric completely down to the VMs. With VM-FEX, the Fabric Interconnects handle switching for the ESXi host's VMs. UCSM utilizes the vCenter dVS Application Programming Interfaces (API) to this end. Therefore, VM-FEX shows as a dVS in the ESXi host.
There are many benefits to VM-FEX:
Reduced CPU overhead on the ESX host
Faster performance
VMware DirectPath I/O with vMotion support
Network management moved up to the FIs rather than on the ESXi host
Visibility into vSphere with UCSM

How to show module and SFP information include hardware serial number on Nexus switch?

How to show module and SFP information include hardware serial number on Nexus switch? Thanks.

Hi,
The show inventory command will give you details of the Nexus chassis, power supplies, Supervisor, Fabric, I/O modules (including FEX if you have them) etc. To get the details of the installed SFP/SFP+ then you'll need to use the show interface transceiver command.
Regards

3750 and Nexus 5548UP Support

I am working on a project that was handed down and several different engineers got their hands on. The project is (or should have been) a simple data storage/center. Fixing all the design problems has left me with very little time to research the security folks issues and I need help.
We are using Cisco Nexus 5548UP for our data center core and distribution/routing to encryptors connecting our remote sites which use Cisco 3750X series switches. The Nexus is running NOS 5.2(1)N1(4) and the 3750s use 12.2(55) IP base.
These are our particular issues:
1) For management and monitoring, what would be a good product to use to support this? If Cisco Prime Infrastructure, what ports would need to be allowed/opened through firewalls/ACLs (SNMP, syslog, etc)?
2) For switch login, the network security folks are reluctant to use TACACS and want to push for LDAP instead. Using Active Directory, is there any way to get the Cisco Nexus 5548UP and Cisco 3750Xs talking to Active Directory? I've found both 'yes' and 'no' answers online and am not sure. Do I need to use a different NOS and/or IOS? Are there specific directions somewhere? Or is it not possible?
3) Without TACACS, is there any way to implement command logging to a syslog server on the Nexus? On the 3750s, I make the following changes and all commands are relayed to our syslog server:
Enable
Configure terminal
Archive
Log config
Logging enable
Logging size 500
Hidekeys
Notify syslog
End
Is there anything similar for the Nexus?
4) In conjunction with #3, we need to be able to log each login attempt (success and failure) to a syslog server on the Nexus. On the 3750, using the "login on-[failure/success] log", it is can setup easy enough. On the Nexus, I haven't been able to find anything similar. I can't find any instructions on setting this up on the Nexus, though.
5) What IOS/NOS do we need to use to be able to lock out users after 3 failed logins (again, without using TACACS)?
If you need more information, please ask.
V/R,
Chris

The LRM is s special case transceiver which supports 10 Gbps over older FDDI grade multimode fiber when used with a mode conditioning patch cord. It is not supported on the Nexus 5548UP.
The SFP-10G-LR is used with single mode fiber for spans up to 10 km in length. It is supported on the 5548UP (and most every platform of Cisco's that takes SFPs).
Please see the product data sheet here.

I just downloaded Firefox 5 and it said that my Yahoo toolbar will not work with it. Is this true? If so I will not use this new version and will switch to another browser if Firefox stops supporting the Yahoo toolbar. Thank you.

I just downloaded Firefox 5 and it said that my Yahoo toolbar will not work with it. Is this true? If so I will not use this new version and will switch to another browser if Firefox stops supporting the Yahoo toolbar. Thank you.

Add-ons contain a range of compatible Firefox versions, and Firefox honors the listed range by disabling the add-on if you are trying to run it on an unlisted version.
I'm sure Yahoo! will update its toolbar eventually, but not every add-on maker supports beta versions of software.

When I open about this mac - more info and I switch through the tabs (display,memory,storage,support,service) it lags (fps drops, animation looks choppy not smooth). Why does this happen? (over 300 gb free,same programs installed,free desk-downloads)

When I open about this mac -> more info and I switch through the tabs (display,memory,storage,support,service) it lags (fps drops, animation looks choppy not smooth) even though all the mac (programs , interface ) works smooth . Why does this happen? (over 300 gb free,same programs installed,free desktop-downloads -no garbage there- everything neat and tidy.) Need some help. Only there it the animations goes like 2 fps and is not smooth. I do not understand why because the programs are the same so its the usage. Nothing is changed, yet i experience this little issue for a couple of days.

OK, I'm confused. When I do About this Mac > More Info in OS10.9, I don't see any animation other than the window resizing. Is that the animation you are describing?
Which if any of the following apply to your computer:
1) Are you running any anti-virus/internet security applications?
2) Are you running any "cleaning/tune-up/optimizations" applications?
3) Any peer-to-peer or torrent downloading software?
4) Any third-party disk backup software that came bundled with an external hard drive?
5) Any online backup scheme other than iCloud (Carbonite; GoogleDrive; MS One Drive)?
6) Did your financial institution ask you to install Trusteer EndPoint Protection (also known as Trusteer Rapport)?

Thoughs on interconnecting Nexus 3548 and 3750 switches

Hi,
I have two nexus 3548 switches.
I have created port-group 1 on both switches to group eth1/47 with eth1/48.
I have 4 sfps, 2 per switch. to connect to a single 3750 that I want to group together as well.
So I have gi1/0/31 going to eth1/1 on nexus1 and gi1/0/32 going to eth1/2 on nexus1
I have gi1/0/33 goin to eth1/1 on nexus2 and gi1/0/32 goin to eth1/2 on nexus2
When I create the port group on the 3750 do I create one group with all 4 ports or will I have to create 2, one per nexus switch?
Thanks

Thanks for the replies. I finally got to test the hardware and config yesterday.
Just so I am clear. the vpc and peer to peer links are only for interconnecting the two Nexus switches. I think I got that right. sho VPC br seems to say it is up. I am using Po5
vPC domain id : 1
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
Configuration consistency status : success
Per-vlan consistency status : success
Type-2 consistency status : success
vPC role : secondary
Number of vPCs configured : 0
Peer Gateway : Disabled
Dual-active excluded VLANs : -
Graceful Consistency Check : Enabled
Auto-recovery status : Disabled
vPC Peer-link status
id Port Status Active vlans
1 Po5 up 1
Next do I create a port channel on Nex1 and Nex2 for the two ports that connect to the 3750 (Po6 for example) or do I add the two links to the 3750s to Po5 ? I thought I add them to Po 5 but since I am mixing 1000 and 10G ports it doesnt seem to like it.

Converged 10gig server adapters and Cisco switches

I have little network with 4 vsphere servers connected to clustered 3750x with 4*1Gig NICs per server.
Servers are connected to central storage with two 8Gbps FC links per server. I don’t have FO switches cause central storage is equipped with 4 FO ports per controller.
I want to upgrade servers and central storage. Servers will have two converged 10gig (HP FlexFabric) and 4*1 Gig interfaces
I need to upgrade 3750x switches with new one with 10 gig interfaces.
I am looking for two new Cisco switches that can handle converged traffic from server 10gig interfaces (iSCSI, FCoE).
Nice feature will be if it is possible to connect existing FC storage to the new switches.
Kind regards,
Vice Lacmanovic

Hello, vlacmanov.
I recommend at least the Nexus 5000 to support iSCSI and FCoE over your 10GE interface. (http://cs.co/9001SoyL) Do you already have any existing Cisco Nexus on your network?
Let me know if you have additional concerns or e-mail ([email protected]) me directly. Kind regards.

Design question, UCS and Nexus 5k - FCP

Hi,
I need some advice from (Mainly a Nexus person); I have drawn and attached the proposed solution (below).
I am designing a solution with 3 UCS chassis, Nexus 5K and 2X NetApp 3240 (T1 and T2). FC will be used to access disk on the SAN. Also, Non UCS compute will need access to the T2 SAN only. (UCS will access T1 and T2). It is a requirement for this solution that non UCS devices do not connect to the same Nexus switches that the UCS chassis use.
UCS Compute:
the 3 X chassis will connect to 2 X 6296 FIs which will cross connect to the a 2 X Nexus 5K through a FC port channel, the Nexus 5Ks will be configured in NPIV mode to provide access to the SAN. FC from each Nexus 5K to the NetApp controllers will be provided through a total of 4 X FC Port Channels (2 FC member ports per PC) from each nexus 5K one going to controller A and the other to controller B.
Non UCS compute:
These will connect directly through their HBAs to their own Nexus 5Ks and then to the T2 SAN, these will be zoned to never have access to the T1 SAN.
Questions:
1-      As the UCS compute will need to have access to the T1, what is the best way to connect the Nexus 5Ks on the LHS in the image below to the Nexus on the RHS (This should be FC connection).
2-      Can fiber channel be configured in a vPC domain as Ethernet? Is this a better way for this solution?
3-      Is FC better than FCoE for this solution? I hear FCoE is still not highly recommended.
4-      Each NetApp controller is only capable of pushing 20GBps max, this is why each port channel connecting to each controller is only 2 members. However, I’m connecting 4 port channel members from each Fabric Interconnect (6296) to each Nexus switch. Is this a waste? Remember that connectivity form each FI is also required to the T2 SAN.

Max,
What you are implementing is traditional FlexPod design with slight variations.
I recommend to look at FlexPod design zone for some additional material if you have not done so yet.
http://www.cisco.com/en/US/solutions/ns340/ns414/ns742/ns743/ns1050/landing_flexpod.html
To answer your questions:
1) FC and FCoE do not support vPC. If UCS needs to have access to T1, then there is no need to have ISL between sites. If UCS needs to have access to T1 and T2, then best option would be to set up VSAN trunking on N5K and UCS and configure vHBAs accordingly.
2) Both should work just fine. If you go with FCoE, then UCS would need to be on the latest version for multi-hop FCoE support.
3) If you only worried about storage throughput then yes, you will never utilize 40Gb PO if your source will be 20Gb PO. What are your projected peak and average loads on this network?

SAP XI support SFTP and FTPS?

Hi Gurus,
I would like to find out if SAP XI supports both SFTP and FTPS. If yes, how do I perform the configuration?
Thanks in advance.

Business Case:
In many implementations Business requirement is to "secure" the file/data transfer between XI and any third-party system. So there is a need of secured connection between XI/PI and any file based third-party legacy systems.
Following solutions are proposed to cater secure connection between XI/PI and any third party systems.
1) SFTP (Secure File Transfer Protocol)
"SSH File Transfer Protocol" or SFTP is a network protocol that provides file transfer and manipulation functionality over any reliable data stream. It is typically used with the SSH-2 protocol to provide secure file transfer. SFTP encrypts the session, preventing the casual detection of username, password or anything that is being transmitted. One key benefit to SFTP is its ability to handle multiple secure file transfers over a single encrypted pipe. By using a single encrypted pipe, there are fewer holes in the corporate firewall.
2) FTPS (FTP over SSL)
FTPS (FTP-SSL) is a real ftp that uses TSL/SSL to encrypt the control session and if required the data session. With FTPS, the control session is always encrypted, but the data session may not be always encrypted. FTPS is a file transport layer on top of SSL. SSL, or Secure Sockets Layer, is a method by which an encrypted u2018pipe' or tunnel is established between the FTP client and FTP server. Once the secure tunnel has been established (which is done using 128-bit encryption techniques), standard FTP is used to transfer data over the secure connection.
Feasibility of SFTP and FTPS in XI:
SFTP:
As per the latest SAP PI/XI support pack, it does not support SFTP via File Adapter.
So alternative approach to cater this requirement from XI is to make use of Unix Script at OS level to transfer the files from/to third-party systems.
Inbound Interface - i.e. third-party system ->XI->SAP:
File is transferred to a folder in SAP XI landscape from the third-party legacy system using UNIX Script with secured protocol. Once the file is ready in the XI landscape, File Adapter will poll this directory and file is picked up by NFS protocol.
Outbound Interface u2013 i.e. SAP->XI->third-party system:
XI is responsible for writing a file into a folder in the XI landscape. These files are transferred to the third-party system by executing UNIX scripts with secured protocol i.e. via sFTP.
Pre-Requisites:
Public key should be exchanged between external systems and the PI system.
UNIX shell script has to be developed and scheduled.
Advantages:
Highly Secured.
Ability to handle multiple secure file transfers over a single encrypted pipe .By using a single encrypted pipe, there are fewer holes in the corporate firewall.
Disadvantages:
Two-Step process i.e. XI>Temporary folder>External System and vice-versa
Files have to be temporarily stored in XI server.
Multiple failure points i.e. XI and Unix script execution
Maintenance of an external UNIX script.
Difficulty in monitoring the execution of the shell script as it cannot be monitored thru XI.
Need to generate keys and install it in the SFTP site as a pre-requisite i.e. SFTP clients must install keys on the server.
SFTP uses keys rather than certificates. This means that it can't take advantage of the "chains of trust" paradigm facilitated through Certificate Authorities.
Files from the XI server should be deleted/archived in a periodic manner to increase the disc space so that it will increase the performance.
Note: UNIX shell Script can be executed as a background job u2018or' can be triggered from SAP XI through OS command at File adapter level.
FTPS (File Transfer Protocol Using SSL/TLS):
This is a built-in feature of File adapter in XI. But SAP Java Cryptographic Toolkit must be deployed as a prerequisite. (Refer to note https://service.sap.com/sap/support/notes/821267 Question 28). By default following ports are used:
Implict FTPs 990 (Control) and 989 (Data)
Explicit FTPs 21 (Control) and 20 (Data)
Both use cases can be combined with active and passive mode.
Advantages:
Direct transfer of files to/from third-party systems. It is not required to store the files in the XI server temporarily.
Built-In feature from XI File adapter
No extra effort in development and maintenance of Unix Script.
Centralized Monitoring tool from XI
FTPS uses certificates and therefore can take advantage of "chains of trust" paradigm facilitated through Certificate Authorities. This paradigm makes it possible for two entities to establish a trust relationship without directly exchanging security information, which is important for some applications.
Disadvantages:
Requires opening multiple ports forenabling SSLin the firewall. So there are multiple holes in the corporate firewall.
Not every FTP server supports FTPS and many that do, require a configuration change to activate the FTPS protocol extension.
Cryptographic toolkit should be installed in XI system though it is not very complex or expensive.
Conclusion:
Though SFTP seems more secure as it works through one port, FTPS is easier to configure, monitor and maintain from XI point of view. However, the decision depends on many parameters like, cost/effort, flexibility in use, ease of maintenance, company security policy, failure possibilities etc.
regards
kummari

Fex 2000 connecting to nexus 7k/5k

Hello All,
We are connecting one fex 2000 to two nexus 5k. I have prepared a simple configuration after consulting the various cisco pages on this.
On first nexus 5k:-
int Po100
des FEX-2232-1
vpc 100
switchport mode fex-fabric
fex associa 100
no shut
int eth1/1
des FEX-2232-1
switch mode fex-fabr
fex associ 100
channe-gr 100
no shut
================
On second nexus 5k:-
int Po100
des FEX-2232-1
vpc 100
switchport mode fex-fabric
fex associa 100
no shut
int eth1/1
des FEX-2232-1
switch mode fex-fabr
fex associ 100
channe-gr 100
no shut
Is the above configuration correct?
The other doubt is; when configuring is it required to create the Po100 first before applying the channel-group command on the physical interfaces?
Or can the channel-group be directly applied to physical interface ( without the Po being created )?
Appreciate help on this please. Thanks in advance.

suthomas1,
The config is correct. I'm using the same config here so stable and resilient.
No, its not required to create the po100 before applying the channel-group command on the phy-int.
Be careful with bpdu in fex access ports.
Reagards,
Gus Magno

Adapter-fex Supported VICs and Nexus Switches

Similar Messages

Maybe you are looking for