Configuration Nexus 56128P and Nexus 2348UPQ

[jmp780718]

Hi All.

I will be configuring a new nexus 56128P in VPC domain, i need help to know if is the same configuration procedure like others Nexus on VPC?, and also i will configure Fex 2348UPQ is the same procedure like other fex like Nexus 2248TP?.

Thank you so Much for your Help. 

[InayathUlla Sharieff]

Hi,

Yes the configuration remains the same for connecting the Nexus 2348 to N56128P.

There is no special or change in the configuraiton. Please go ahead and configure the same as you do with the VPC config between the Nexus and FEX of other modules.

 Cisco Nexus 2300 Series Fabric Extenders single-connected to one upstream Cisco Nexus 5500, 5600, 6000, 7000^ῖ or 9000^ῖ Series Switch. In this deployment model, access-layer redundancy is achieved through redundant server connections to two upstream distributed modular systems using vPC (Cisco Nexus 5500, 5600 or 6000 Series) or server NIC teaming to two Cisco Nexus 2300 Series Fabric Extenders.

●   Cisco Nexus 2300 Series Fabric Extenders dual-connected to two upstream Cisco Nexus 5500, 5600 or 6000 Series Switches (vPC). In this deployment model, access-layer redundancy is achieved with a combination of Cisco Nexus 2300 Series Fabric Extenders dual-connected to an upstream parent switch and server NIC teaming.

●   Enhanced vPC (EvPC). In this deployment model, access layer redundancy is achieved in two ways: through redundant connections between the Cisco Nexus 2300 Fabric Extenders and the Cisco Nexus parent switches using vPC; and through redundant server connections to two fabric extenders using vPC and active-active server NIC teaming.

●   vPC+: In this deployment model, access-layer redundancy is achieved through server vPC, FEX vPC, and EvPC. In addition, a vPC+ domain allows the Cisco Nexus parent switch and the fabric extenders to be viewed as a single virtual switch in a Cisco FabricPath network.

Figure 8.      Cisco Nexus 2300 Series Fabric Extenders Design Models, from Left to Right: Server vPC, FEX vPC, EvPC, vPC+

HTH

Regards

Inayath

[jmp780718]

Hi InayathUlla Sharieff.

Is possible to use a 40Gbps interfaces to conecct the Fex?.

Thank you. 

[InayathUlla Sharieff]

yes but it depends on the Fabric extender model.

http://www.cisco.com/c/en/us/products/collateral/switches/nexus-2000-series-fabric-extenders/data_sheet_c78-507093.html

HTH

[jmp780718]

Hi  InayathUlla Sharieff.

Thank you so much for your help the information was so helpful. i have a last one, do you know a command to execute a hardware test on 5ks?.

Thank you.

[InayathUlla Sharieff]

Hi,

It depends on what kind of hardware test you would like to run on n5K?

HTH

***Please do not forget to rate all usefull posts*******

[jmp780718]

Hi InayathUlla Sharieff.

A test over port modules, sorry InayathUlla but have andother question how i can convert a FC interface to Ethernet?.

Thank you. 

[InayathUlla Sharieff · Accepted solution]

Please find below email to convert a FC to Ethernet:-

To use some of the ports as FC ports, we need to change the port type of the port(s) that we intent to use for FC connection. Here's an example of commands to change port type on the switch:

N5K(config)#slot 1

N5K(config-port)#port 41-48 type fc

N5K(config-port)#copy running-config startup-config

N5K(config-port)#Reload

!

As the above command example, we change ports 31 and 32 from the default "Ethernet" to "FC" type. Similarly, to convert back from FC to Ethernet port type:

N5K(config)#slot 1

N5K(config-port)#port 41-48 type ethernet

N5K(config-port)#copy running-config startup-config

N5K(config-port)#Reload

HTH

Regards

Inayath

***Please do not forget to rate all usefull posts*******