Nexus 5548UP - HSRP and vPC, tracking required?

Hi,
We've got two Nexus 5548UPs that are vPC and HSRP peers.
I've had some feedback that I should incorporate the tracking function to close the vPC down in the case of a layer 3 problem, the thing is I'm not sure it's required. I can see in this article it recommends implementing tracking when your L2 peer-link and L3 interfaces are on the same module (which it is in my case).. http://www.cisco.com/en/US/docs/switches/datacenter/sw/design/vpc_design/vpc_best_practices_design_guide.pdf
But in this article it says not to use tracking.. http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/design_guide_c07-625857.pdf
Any one got any real world experience and can offer some feedback.. I don't mind putting it in just want to understand why.
Thanks,
Nick.

Hi Nick
there is two tracking can be use din nexus enviroment
HSRP tracking and vPC tracking
for using one line card for the vPC peer link vPC tracking is recomnded
HSRP tracking is used to track L3 uplinks to the core
Using vPC with HSRP/VRRP object tracking may leads to traffic blackholing in case object tracking is triggered
its better to use separate L3 inter switch link instead of using HSRP tracking
hope this help

Similar Messages

Routing issue in Nexus 7009 due to vPC or hsrp

we have two site's, on first site we have two nexus 7009 switches (Nexus A & Nexus B) and other site is remote site having two 6500 switches. (design attached)
we are using hsrp on nexus switches and Active is Nexus A for all vlan’s
From one of my remote site user's (user's are in vlan 30 ) are not able to communicate with nexus site vlan 20 specially if host in vlan 20 take forwarding path from nexus switch B,
I can ping the vlan 20 both physical address's and gateway (vlan 20 configured in both nexus switch and using HSRP) from vlan 30 which configured on remote site 6500 switch
ospf with area 0 is the routing protocol running between both site.
vlan 10 we are using as a management vlan on both nexus switch that building neighbore ship with WAN router, it's means wan router have two neighbors nexus A and nexus B, but nexus B building the neigbhorship via a Nexus A because from WAN router we have single link which is terminated on Nexus A,
there is one layer 2 switch between nexus A and WAN router, nexus A site that switch port in vPC because we are planning to pull second link later to nexus B.
All user's are connected with edge switch and edge switch have a redundant uplink to nexus A and B with vPC configured
After troubleshooting we observe that if user in vlan 20 wants to communicate with vlan 30 (remote site), traffic is taking Nexus B is forwarding path, then gets drops.
I run the tracert from pc its showing route till SVI on Nexus B after that seems packets not finding route. Even vlan 30 routes are available in the routing table of Nexus B. we don’t have any access-list and Firewall between this path.

Hi,
I suspect in your scenario that traffic is being dropped due to the characteristics of vPC, the routing table on Nexus-B may reflect the next-hop address for the destination IP, however if that next-hop address is the address of the Nexus-A off of VLAN 20 then it will be forwarded across the vPC peer-link, this breaks the convention.
When you attach a Layer 3 device to a vPC domain, the peering of routing protocols using a VLAN also carried on the vPC peer-link is not supported. If routing protocol adjacencies are needed between vPC peer devices and a generic Layer 3 device, you must use physical routed interfaces for the interconnection.
You can configure VLAN Interfaces for Layer 3 connectivity on the vPC peer devices to link to Layer 3 of the network for such applications as HSRP and PIM. However, Cisco recommend that you configure a separate Layer 3 link for routing from the vPC peer devices, rather than using a VLAN network interface for this purpose.
Take a look at the following URL, this article helps to explain the characteristics of vPC and routing over the peer-link:
http://bradhedlund.com/2010/12/16/routing-over-nexus-7000-vpc-peer-link-yes-and-no/
Regards
Allan.
Hope you find this is helpful.
Sent from Cisco Technical Support iPad App

LMS User Tracking for NEXUS 5548UP

Dear,
A while ago I received a ticket from one of our customers because User Tracking was not working for NEXUS 5548UP on LMS 3.2. I opened a TAC case for this but this was normal since it is a Datacenter switch. Now the customer came back on this because they really want to see which server is connected to which switch port. I understood from the TAC engineer this is not on the roadmap to integrate in LMS 4.x. They want to know if there exists another product (they thought about DCNM) and wanted to know how this integrates or works together with LMS...
Kind regards,
Sven Laureyssens

My latest understanding of User Tracking and Nexus 5K series is that it is not supported due to a limitation of the MIB support in the NX-OS.
The current DCNM (release 5.2) is distinct from the LMS and Cisco Prime umbrella but that wil be changing a bit moving forwad as DCNM is enhanced and rolled into the Cisco Prime family. Last I heard there should be some information coming out of Cisco Live this week and a new release will have some additional functionality and better integration. Still, I doubt we'll see UT for the 5K due to the NX-OS limitation.
One way to do what you're asking apart from use of any of the Cisco products is to enable LLDP on your Nexus and servers. That will at least give you the ability to pull the information from the NX-OS command line ("show lldp neighbor")

Nexus 5548UP and LACP

Hello,
I am trying to setup LACP on the Nexus 5548UP 10 Gig switch on Port-channel 3. However, when I setup LACP, eth ports 7 and 8 (on Port-channel 3) go into either inactive or down state (as below). The 10 gig ports (7 and 8) are connected to a server which has LACP capability.
ns5500(config-if)# do sh port-channel summary
Flags: D - Down        P - Up in port-channel (members)
        I - Individual H - Hot-standby (LACP only)
        s - Suspended   r - Module-removed
        S - Switched    R - Routed
        U - Up (port-channel)
        M - Not in use. Min-links not met
Group Port-       Type     Protocol Member Ports
      Channel
1     Po1(SU)     Eth      NONE      Eth1/15(P)   Eth1/16(P)
3     Po3(SD)     Eth      LACP      Eth1/7(D)    Eth1/8(D)
LACP setup as follows:
feature lacp
interface port-channel3
switchport access vlan 10
speed 10000
interface Ethernet1/7
switchport access vlan 10
channel-group 3 mode active
interface Ethernet1/8
switchport access vlan 10
channel-group 3 mode active
It would be great if anyone can help me with getting LACP up and running on the 10 Gig Nexus 5548UP. Please let me know if you need more information.
Thanks!

Thanks for your response. I do have vlan10 created and it is active. Thanks for correcting individual state instead of inactive.
I ran a few lacp commands below including "show lacp counters"
ns5500(config)# show lacp counters
                    LACPDUs         Marker      Marker Response    LACPDUs
Port              Sent   Recv     Sent   Recv     Sent   Recv      Pkts Err
port-channel3
Ethernet1/7        163655 13948    0      0        0      0        0
Ethernet1/8        161700 13976    0      0        0      0        0
By looking at LACP PDUs can we say that LACP is up and running?
ns5500(config)# show lacp port-channel
port-channel3
System Mac=54-7f-ee-8d-83-fc
Local System Identifier=0x8000,54-7f-ee-8d-83-fc
Admin key=0x2
Operational key=0x2
Partner System Identifier=0x0,0-0-0-0-0-0
Operational key=0x0
Max delay=0
VPC ID=0
Aggregate or individual=1
Member Port List=7-8
In the below command, it still says, interfaces 7 and 8 are down? What does that mean? An issue with the host? Is there anyway to test the nexus switch to check if it is doing its part and working correctly?
ns5500(config)# show port-channel summary
Flags: D - Down        P - Up in port-channel (members)
        I - Individual H - Hot-standby (LACP only)
        s - Suspended   r - Module-removed
        S - Switched    R - Routed
        U - Up (port-channel)
        M - Not in use. Min-links not met
Group Port-       Type     Protocol Member Ports
      Channel
1     Po1(SD)     Eth      NONE      --
3     Po3(SD)     Eth      LACP      Eth1/7(D)    Eth1/8(D)
Thanks.

Running HSRP between N5k 's and vPC between N2k and server

Dear All,
I have the following existing setup, i would like to run HSRP between N5k1 and N5k2. Also would lilke to run vPC between N2k1,N2k2 to the server farm which are dual homed. Please find the diagram attached.
Please advise the step by step process along with the commands to be entered. Thanks for your help

Hi,
If you don't have many vlans, there is no need to load balance. Make one of the 5ks the primary for HSRP and the other one stand-by.
here is good link on how to configure it. Make sure to run HSRP version 2. This way you can mach the HSRP group IDs with your vlan IDs. Also give a higher priority to the active 5k and enable preemption.
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5500/sw/unicast/7_x/cisco_n5500_layer3_ucast_cfg_rel_6x/l3_hsrp.html
HTH

Cisco Nexus 5548UP and FI6248UP compatibility with FC SFP

Cisco Nexus 5548UP and FI 6248UP comes with Unified Ports. What are the SFP types this port can take? 1Gig, 10Gig and 2/4/8FC. Could you please clarify?
Thanks,
Cheriyan

Hi Cheriyan,
Here is te URL to the 6200 series FI data sheet:
http://www.cisco.com/en/US/prod/collateral/ps10265/ps11544/data_sheet_c78-675245.pdf
Check for the table to supported SFPs.
Same for the 5500 switches
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/data_sheet_c78-618603.html.
Hope this helps!
./Abhinav

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.

[Java and all else] Requirements tracking, testing, and versioning

Hello,
as a semi-experimental subject, I am considering managing requirements and test documents in the same version control system as the code.
For some reasons, this versioning policy doesn't seem mainstream, so I'd like to have your opinion on that.
+N.B.: the prefix "java and all else" refers to the fact that I'm using this area to post a message that is related not only to Java but also to other topics (people, processes, tools,...) that help program in Java - so this post is not really off-topic either. For the record, I filed a suggestion to open a dedicated forums to discuss topics like that, although it hasn't received enthusiastic support so far :o(...+
Here is how I had imagined to proceed:
- requirements document gets edited and stored as text in the VCS
- test plan (basically a matrix of which tests cover which requirements) goes into the VCS as well, text or binary
- test instructions (detailed steps, actions, expected results) are stored as text in the VCS
- test results - I do'nt know yet, but I planned to store them as text (lists of testId=result) in the VCS (I'm not sure indeed, that those would go into the VCS)
The advantage of versioning those as text is that all VCS clients support easy-as-a-click history browsing and diff capabilities.
Diffs and logs are useful to trace when and why a requirement has appeared, evolved, obsolated,... Especially in long-lived systems whose maintenance crew rarely embeds "historical" pioneers who developed the original systems.
My questions:
1) Is it good practice to version such docs in the same repository as the code?
I've never seen this done.
- In half of the shops I've been these docs are not really versioned (the PM considered it enough that the latest applicable version of the docs was available)
- The other half has used versioning systems ranging from ad-hoc (shared folder acting as repository of all versions) to "document management systems". I found such tools to be developer-unfriendly (poor diff capability, poor text searching), and developers to be office-document-reluctant (mostly because of the shortcomings of the doc format and doc management systems).
- The third half <wink to aficionados of French cinema> used dedicated softwares (Test Director, RQM,...) to manage requiremetns, test plans, test cases, test results,... The drawback is that the developers were hardly involved in using such tools, and even when they were, were not trained to use the administrative and metadata capabilities (who modified the test steps, when and why?).
On the contrary, developers would easily and gladly browse histiry, check diffs, etc... on text documents versioned using their daily-used source control system.
2) Are there "standard", preferrably text-based, formats, for the documents listed above?
Each and every organization I've seen had its own format, but most items have equivalents in all organizations, even if disguised under different terminologies. I have no formal education or training in quality assurance, but I guess some ISO or CMM norms define those recurring items, and I expect some abstract XML format might exist
3) Are there tools already that cover edition and exploitation of such formats, or why not, of the versioning of such formats (naive example, graphing the pass rate of tests over time)?
A pet project of mine is to develop and open-source some Swing UI to do this, but existing tools would save me the trouble.
I'm looking forward to reading about your own experience.
Best regards,
Jerome.
Edited by: jduprez on Jun 4, 2010 10:33 PM
Fixed link.

I don't have data on comparative bug rates because we did not do studies focused on that. This stuff was mostly driven by convenience #) considerations.
Subjectively, yes it seemed to have lower bug rate compared to maintaining documents in, say, pdf format (like our doc writers did with User/Dev guides). BTW doc writers are another kind of guys who dislike plain text.
As for using test results history the way you describe - agree, that makes some sense. Now that you mention it I recall using it myself that way, in one of the projects where testers managed to establish really convenient way to assess test execution history. After I figured how easy it was, I began using it. Quite helpful indeed.
Regarding "tool or format that mapped tests to specific requirements" in your original post - did you consider Polarion? IIRC it supports mapping requirements to test descriptions. Telelogic DOORS are maybe also capable of that but I am not completely certain.
#) convenience -- BTW we maintained test descriptions not in plain text but in simple HTML (you know few tags one can use in javadocs). With limited line length, it is almost as VCS friendly as plain text, even with tables:
<!DOCTYPE "stuff to make HTML validator happy">
<html><title>test description</title>
<body>
<table>
<tr>
    <td>test id</td>
    <td>synchronized.10988343</td>
</tr>
<tr>
    <td>instructions</td>
    <td>
      <ul>
        <li>sacrifice a goat
          <ul><li>under the full moon</li></ul>
        </li>
        <li>twirl counterclockwise
          <ul><li>until you barf</li></ul>
        </li>
    </td>
</tr>
<tr>
    <td>pass criteria</td>
    <td>
      <ul>
        <li><b>pass</b> if method is synchronized</li>
        <li><b>fail</b> otherwise</li>
      </ul>
    </td>
</tr>
<tr>
    <td>comments</td>
    <td>
       <a href="http://forums.sun.com/thread.jspa?messageID=10988343#10988343">
       click here for details</a>
    </td>
</tr>
</table>
</body>
</html>
{code}
We were also using [HTML validator|http://validator.w3.org/|tool] tool to automatically catch simple syntax mistakes like missing tags.

Nexus 5K OSPF with vPC

Hi,
I know it is well documented using IGP's, more specifically OSPF with 7K's and vPC's but when it comes to the same thing on 5K's I am still a little confused.
My topology is:
5K01 and 5K02 are connected and are vPC peers, I currently have a management network on VLAN 114, both 5k's have SVI's on this and are currently OSPF neighbors over their vPC using this vlan.
I have an MPLS router (service provider PE) which is 2 routers but clustered so logically in this instance it is one router, the 5 k's will be conecting to this PE router via some switches over a vPC and needs to become a OSPF neighbor to both the 5K's.
Looking at this post:
http://adamraffe.com/2013/03/08/l3-over-vpc-nexus-7000-vs-5000/
It suggests that I can just add VLAN 114 to the vPC up to tyhe PE and turn OSPF on on the interface on the PE, although this will not support Multicast and I don't really want to restrict myself as this may be a future requirement.
What I thought might be a better solution would be to designate a new vlan and allow it on the vPC up to the PE and use that for the OSPF neighborships between the 5K's and the PE and not allowing it over the vPC peer link - leaving the 5K's neighborship over vlan 114.
Can someone tell me what the best practice/supported topology is here and maybe provide some cisco links?
Thanks a lot in advance.

You have to be very careful when configuring L3 services and interfaces while using VPC.
Take a look at this document:
http://www.cisco.com/c/dam/en/us/td/docs/switches/datacenter/sw/design/vpc_design/vpc_best_practices_design_guide.pdf
Also, take a look at this post:
http://bradhedlund.com/2010/12/16/routing-over-nexus-7000-vpc-peer-link-yes-and-no/
You can create a vlan used exclusively for Nexus-to-Nexus iBGP peering. Use a new 'access' link between the two switches and place them on the new vlan. Make sure that this VLAN does not traverse the VPC peer link. Then, create SVIs on each switch for that VLAN and peer over that link. Then, you can create a L3 link on each nexus to peer with your eBGP neighbors.
The point you want to make sure you understand is the VPC loop prevention mechanism that says "If a packet is received on a VPC port, traverses the VPC peer link, it is not allowed to egress on a VPC port."

Do we have a built-in option for web based tool in Nexus 5548UP switches for management purpose?

I have purchased Nexus 5548UP switch, i want to know if we have a built-in option for web based tool to manage and configur it just as ASA have ASDM. If there is no such options then what are the options available that can be freely available and can be used to get performance monitoring done.
Message was edited by: Praveen Varun

DCNM (Data Center Network Manager) runs on a server (Windows, RHEL or Solaris) and can be used to manage Nexus devices. It's free for Nexus 1K through 5K devices (paid license required for Nexus 7K management).
http://www.cisco.com/en/US/products/ps9369/index.html
There is not a "built-in" management product like ASDM for ASA.

Nexus 5548UP ISSU upgrade

Hi all,
I want to upgrade our 2 5548UP nexusses with Nexus 2000 attached with VPC.
Our current version is 5.2(1)N1(7) and we want to upgrade to version 7.0(5)N1(1).
Is there a possibility to do this without interruption? Is this setup eligible for ISSU?
Does anyone have experience with this?
Thanks,
Best Regards,
Joris

Hi Joris,
The FEXes *shouldn't* reboot when you upgrade the primary. Please see the following link for reference on exact instructions (ref: "Upgrading a Dual-Homed FEX Access Layer")
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/upgrade/503_N1_1/n5k_upgrade_downgrade_503.html
During this procedure your server's network connections should be maintained through the secondary 5K.
However, if you are not comfortable with this upgrade method, there is another that I have discussed with Cisco as being workable where you shut down half your FEX ports on the primary 5K prior to the primary 5K upgrade. This allows you to upgrade half the FEXes at a time. This is useful if you have two FEXes per rack, and your hosts/servers are dual homed to these FEXes. The procedure would look like this.
1.On the primary 5K shut down half of the FEX ports. In this situation you would shut down the ports to one FEX per rack, leaving another FEX online in that rack to maintain host reachability.
2.Upgrade the primary 5K. This will result in the primary 5K and half of the FEXes it can reach to be upgraded and rebooted, but leaving half of the FEXes and the secondary 5K as available.
3.Verify the secondary 5K is now operational primary. If it’s not then it will not be able to upgrade. Reboot the primary 5K again if the secondary is not operational primary. (in order for FEXes to grab upgrade files from the parent 5K being upgraded, it must either be primary or in operational primary mode)
4. Upgrade secondary 5K. This will result in the secondary 5K and the other half of the FEXes to be upgraded and rebooted.
5.Turn up all FEX ports the on primary 5K.
6.Verify stabilized and upgraded network.
Hope that helps.
Logan

UCS Uplinks and vPC

Hello,
I try to build virtual Portchannels on 2 Nexus 5548UP and 2 UCS 6248FI. With standalone links (without vPC) the communication between some ESX-Server and my Network is working. When I build vPCs on the N5k the vPC all portchannels (on N5K and FIs) are up.
The Portchannels are pinned to the vNICs and all looks fine. But there is no communication between my ESXs and my network. My configuration is like this:

Hi Roberts,
Are the VLANs allowed on the peer link? because if they work in standalone then that means trunk is fine but if they don't have them allowed on the peer link then it will stay up but wont talk

Connect Nexus 5548UP-L3 to Catalyst 3750G-24T-E Layer 3 Switch

Please help!
Could anyone out there please assist me with basic configuration between Nexus Switch and Catalyst Switch, so that devices connected on the catalyst switch can talk to devices connected on nexus switch and vice-versa? In my current setup all servers on VLAN 40 are connected on the Catalyst Switch A as shown in the diagram below, and all desktops and all other peripherals are connected on the Catalyst Switch B. I am required to implement/add a new Nexus Switch 5548 that in the future will replace the Switch A. From now I just need to connect both switches together and start moving the server from Switch A to the Nexus Switch.
The current network setup is shown as per diagram below:
SWITCH A – this is a layer 3 switch. All servers are connected to this switch on the VLAN 40.
SWITCH B – all desktops, VoIP telephones, and printers are connected on tis switch. This switch is also a layer 3 switch.
I have connected together the Nexus 5548UP and SWITCH A (3750G) using the GLC-T= 1000BASE-T SFP transceiver module for Category 5 copper wire. The new network is shown as per diagram below:
Below is the configuration I have created in both Switches:
SWITCH A - 3750G
interface Vlan40
description ** Server VLAN **
ip address 10.144.40.2 255.255.255.128
ip helper-address 10.144.40.39
ip helper-address 10.144.40.40
interface Vlan122
description connection to N5K-C5548UP Switch mgmt0
ip address 172.16.0.1 255.255.255.128
no ip redirects
interface Port-channel1
description UpLink to N5K-C5548UP Switch e1/1-2
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,30,40,100,101,122
switchport mode trunk
interface GigabitEthernet1/0/3
description **Connected to server A**
switchport access vlan 40
no mdix auto
spanning-tree portfast
interface GigabitEthernet1/0/20
description connection to N5K-C5548UP Switch mgmt0
switchport access vlan 122
switchport mode access
spanning-tree portfast
interface GigabitEthernet1/0/23
description UpLink to N5K-C5548UP Switch e1/1
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,30,40,100,101,122
switchport mode trunk
channel-group 1 mode active
interface GigabitEthernet1/0/24
description UpLink to N5K-C5548UP Switch e1/2
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,30,40,100,101,122
switchport mode trunk
channel-group 1 mode active
N5K-C5548UP Switch
feature interface-vlan
feature lacp
feature dhcp
feature lldp
vrf context management
ip route 0.0.0.0/0 172.16.0.1
vlan 1
vlan 100
service dhcp
ip dhcp relay
interface Vlan1
no shutdown
interface Vlan40
description ** Server VLAN **
no shutdown
ip address 10.144.40.3/25
ip dhcp relay address 10.144.40.39
ip dhcp relay address 10.144.40.40
interface port-channel1
description ** Trunk Link to Switch A g1/0/23-24 **
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,122
speed 1000
interface Ethernet1/1
description ** Trunk Link to Switch A g1/0/23**
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,12
speed 1000
channel-group 1 mode active
interface Ethernet1/2
description ** Trunk Link to Switch A g1/0/24**
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,122
speed 1000
channel-group 1 mode active
interface Ethernet1/3
description **Connected to server B**
switchport access vlan 40
speed 1000
interface mgmt0
description connection to Switch A g2/0/20
no ip redirects
ip address 172.16.0.2/25
I get a successful response from Server A when I ping the N5K-C5548UP Switch (VLAN 40 interface (10.144.40.3) .But if I try to ping from Server A to Server B or vice-versa the ping fails. From N5K-C5548UP I can ping successful either Server A or Server B. What am I doing wrong here? Is there any additional configuration that I need to add on the Nexus Switch? Please Help. Thank you.

no, no secret aukhadiev
I made a mistake without realising and the interface e1/3 was showing "Interface Ethernet1/3 is down (Inactive)". After spending sometime trying to figure out what was wrong with that interface or switch, it turned out to be that i forgot to add the vlan 40. Now the config looks like this:
N5K-C5548UP Switch
feature interface-vlan
feature lacp
feature dhcp
feature lldp
vrf context management
ip route 0.0.0.0/0 172.16.0.1
vlan 1
vlan 40
vlan 100
service dhcp
ip dhcp relay
interface Vlan1
no shutdown
interface Vlan40
description ** Server VLAN **
no shutdown
ip address 10.144.40.3/25
ip dhcp relay address 10.144.40.39
ip dhcp relay address 10.144.40.40
interface port-channel1
description ** Trunk Link to Switch A g1/0/23-24 **
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,122
speed 1000
interface Ethernet1/1
description ** Trunk Link to Switch A g1/0/23**
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,12
speed 1000
channel-group 1 mode active
interface Ethernet1/2
description ** Trunk Link to Switch A g1/0/24**
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,122
speed 1000
channel-group 1 mode active
interface Ethernet1/3
description **Connected to server B**
switchport access vlan 40
speed 1000
interface mgmt0
description connection to Switch A g2/0/20
no ip redirects
ip address 172.16.0.2/25
Thank you,
JN

Cisco Nexus 5548UP connect to dual NetApp controllers using FCOE

Here is my setup, I have two 5548UP's connected via VPC peer link. I am tring to use VPC to connect to a NetApp with dual 10gb ports using FCOE, with each 5548 getting one of the connections.
I then want to use VPC to connect to a dell server that has dual 10gb ports using FCOE as well with each 5548 getting a connection. I am new to FCOE, any help would be appreciated. I am getting confused in the configuration for both. Thanks

Erik,
Can you check the deployment guides from links pasted below -
http://www.cisco.com/en/US/solutions/ns340/ns414/ns742/ns743/ns1050/landing_flexpod.html
http://www.cisco.com/en/US/docs/solutions/SBA/February2013/Cisco_SBA_DC_NetAppStorageDeploymentGuide-Feb2013.pdf
Head to the Nexus 5k section and check how FCoE is configured, how vPC is configured..
Once you tackle 5k, depending on your Environment (from Netapp perspective), check how to create Interface groups.

Cisco Nexus 5548UP upgrade path

Hi,
I'm planning to upgrade Nexus 5548UP (no L3 services) from 5.2(1)N1(6) to 7.0(5)N1(1). Is this upgrade path vaild? or is there any intermediate version; also advise if ISSU is possible.
Regards,
Navin RK

Hi,
Yes you can upgrade directly from 5.2(1)N1(6) to 7.0(5)N1(1). ISSU is possible, provided you meet the requirements. You can copy the kickstart and system image to bootflash, then run the "show install all impact" command to see whether or not ISSU will be possible with your configuration.
Here is a document supporting the statements above: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5500/sw/upgrade/705_N1_1/n5500_upgrade_downgrade_700.html#pgfId-640981

Nexus 5548UP - HSRP and vPC, tracking required?

Similar Messages

Maybe you are looking for