Are you just replacing the Chassis? Or are you replacing all Supervisor line cards too? If you just replacing the chassis, and re-using the old supervisors you dont need to worry about you config. If you are replacing your supervisors, then you need to configure you VDC from the system first. i.e. copy past the system VDC, confirm you VDCs are created. Then copy paste each VDCs config back. Its pretty painless. Here is a link for additional reading http://www.cisco.com/en/US/docs/switches/datacenter/hw/nexus7000/installation/guide/n7k_replacing.html hth ... View more

Have you dual connected the FEX to two upstream N7K switches and perhaps looking only at the one? If so you would need to configure a VPC. HTH ... View more

Yes it is possible. But are you wanting to connect at 10Gb or at 1Gb. The SFPs type (1 or 10Gb) must match on both sides, as well as the port speed. hth ... View more

No, you can use VPC from a N7K to FEX. The only caveat is whether that particulat model of is supported on the N7K. hth ... View more

Hello Mustafa Your assumption is correct. You connect a FEX directly to a N7K without going via a Nexus 5000. But be sure to check the Nexus 7000 Data Sheet to see which FEX models are supported on the N7K. not all are yet. hth. ... View more

So I cannot say for certain that it would be disruptive. That does depend on the versions of code. What is listed in the release notes, are not the only methods, but it  has been test by cisco, and therefor it is safe to assume this will not  cause downtime. Look at this this way. Are you willing to risk downtime at the cost of customer experience, due to an uncertainty? Doing a bunny hop upgrade will take you perhaps an extra 30-40 minutes. Is this really too much time for a hitless upgrade and no risk? That is a business decision more than a technical decision. hth ... View more

Hello Alan Always refer to the Release notes as to what supported for ISSU and what not. The version jump you want to do will be disruptive. Refer to the notes If you however want to stay within ISSU, upgrade to 4.2.8 first using ISSU and then upgrade to 5.1.5 using ISSU again. That should allow hitless upgrade. hth ... View more

Hello Ajith Was this a configuration command entered outside of config sync? If so you can use "show account log | last 50" to see what was done. If this was a show command it will not reflect. IF this does not assist, please provide further details surrounding your problem. hth ... View more

Lo, A VRF provides Layer3 speration. This is done by a creating seperate table per VRF to the global tables. A VLAN provides layer2 seperation. A SVI is a layer3 interface for a VLAN on a given switch. When one switch has two SVI's on the same switch the prefixes of the SVI's would be present in the same routing table. Depending how Gateway/routing was setup, routing (layer3) between the SVI is possible. To illustrate this, trying to configure two SVI with the same IP prefix will produce an error. Where a VRF in the switching world might add benfit in certain designs, is by seperating the layer3 table on the same switch. Considering the above example where one switch has two SVIs configured, and each SVI is configured within its  own VRF, The prefixes from the SVI would be contained in SEPERATE routing tables. Routing between the two VRFs (although still possible) is not native enabled. Now since there is Layer3 seperation the same IP prefix could be configured on both SVI's. Lastly another difference between a VRF and a VLAN. A VRF is local to a router/switch, where the membership of a VRF is determine by the input interface. A VLAN is comunicated between device by encapsulating frame leaving the device. A VLAN membership is determined by the information in the encapsulation of the arriving frame. Lastly to address the MPLS side. The VRF functionality operate indepently of MPLS. MPLS protocols leverage of a VRF for the mentioned seperation. VRFs are however mostly used in MPLS network, but not required by MPLS. HTH ... View more

Lo, To connect Native FC/FCoE into any port on a N-5548 you would require the N-5548UP model, Short for Unified Ports meaning the ports can take FC/FCoE/Eth. If you have a N-5548P you will require one of the expansion cards for your SAN connectivity as all fixed port are Eth only. The expansion modules available is on the data sheet here. The configuration guides are available here. HTH ... View more

add the following to you config: aaa authentication login ascii-authentication hth ... View more

I have not done this with AD. But with TACACS there is the ability to set the role within the group configuration shell:roles="network-admin" or shell:roles="vdc-admin" Refer to this link http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/security/configuration/guide/Cisco_Nexus_7000_NX-OS_Security_Configuration_Guide__Release_5.x_chapter7.html#con_1473433 hth ... View more

Spanning tree and LACP generally use a switch's system MAC address for bridge ID field in the spanning tree BPDU and as part of LACP LAGID, respectively.  In a single chassis, the systemwide MAC address is used for this purpose. But with VPCs, using the systemwide MAC address would not work because the vPC peers needs to appear as a single entity, hence the purpose of the VPC MAC. Taking that a step further, the operational primary VPC device is responsible for answering and creating BPDUs. If the operational primary fails the secondary takes over the primary role as answers and sends the BPDU's. With VPCs the operational primary would be sending traffic sourced with the VPC MAC address, but only on VPC member ports. On non VPC ports it both switches will use their system MAC as source. Have a read through the following guides. Its explains this further http://www.cisco.com/en/US/products/ps9670/products_implementation_design_guides_list.html hth ... View more

lol, thanks but not really, just been spending lots of playing with the Nexus boxes. With regard to your question, the function of the VPC MAC should operate the same on both a pair of N7K, and N5K. Manually specifying the VPC system MAC should have the same behavior as using the default, but I have seen one or two funnies with that. For the most part it should work as you expected hth ... View more