DC Design

[Arjun Dabol]

We have a DC setup like below :

FEX-->N5K--N7K 

N7K is where all VLANs are configured.

Now customer want to remove N5K and replace it like this :

FEX-->N93180-EX---->Nexus9504---->N7K

I can understand that N5K config will be replicated on 9500 but my doubt is what will be configured on N93180 switch ..what is the use of it here ?

Thanks

[nazimkha]

If N7K is the core, Nexus 9504 can act as spine and Nexus 93180 can act as leaf.  Although not conventional

Many different combinations and applications with these devices. Depends upon the customer requirements and preference for this type of design.

Regards,

Nazim

[Dmitri Popkov]

It depends on what type of fabric in DC you are using - L2 or L3. 

If you are using L2 fabric it can be like: 

FEX-->N93180-EX---->Nexus9504 - Enc VPC + Back-to-Back VPC and N7K as you edge layer.

If you are using L3 fabric it can be like: 

FEX-->N93180-EX as Leaf, Nexus9504 as spine and N7K  as edge leaf N7K. In this type of fabric you can use simple L3 routed fabric (with eBGP/iBGP) or if you need span L2 segments you can use EVPN+BGP.

[sbhadrav@cisco.com]

The isolated private VLAN (PVLAN) support on Fabric Extender (FEX) host interface (HIF) feature enables users to configure PVLAN isolated host and secondary trunk ports on FEX ports, where the parent switch is a Cisco Nexus 7000 series switch. With this feature, users can create end-to-end private VLAN (PVLAN) domain from trunk till host interface ports.
Supported Topologies for Isolated PVLAN on FEX HIF.