DCNM SAN 6.2 + Nexus 5500 not using interface mgmt

When trying to discover a newly setup fabric we have set the SVI of one of the Nexus 5500 switches as seed device in DCNM SAN server. Problem do seem to be the same in DCNM 6.2 as in DCNM 5.x, one can not use a SVI.... After adding the seed switch with the IP adress of the SVI it appears in the Admin->Data sources->Fabric with the ip address of the mgmt interface. Thing is that this ip address can not be reached from the DCNM SAN server since we have only used a cross over ethernet cable for peer-keepalive over the mgmt interfaces.
Is there a way in DCNM SAN 6.2 to force SAN management over a SVI instead of the mgmt interface?

Here is the solution:
in the menubar on the top, in the lower one go to Admin > Server Properties
scroll to the middle of the list, locate “fabric.managementIpOverwrite” and set it to false
restart the DCNM Servers

Similar Messages

Why not use interfaces for constants?

Hi,
I have been getting conflicting views about why not use interfaces for constants?
Can anyone shed some light on it?
Piyush

How so?
If the constants are only used in a single classhow
does it help to put them in a separate structute?
(Ignoring the a type safe enumeration of course.)Well, mainly for readability. Suppose that you have a
web application which has a servlet class
"RedirectServlet", which takes a variable to redirect
to a given JSP file. In the JSP files, you want to
create forms which take this servlet as their action.
You could of course put all these "redirect"
constants in the RedirectServlet itself, but then
it's kind of weird that you have to import a
servlet in your jsp file to include these constants
and to be able to write
<form action="servlet/RedirectServlet?key=<%=
RedirectServlet.HOMEPAGE %>> or so.
Instead, you could create an interface called
"RedirectConstants", and then your servlet
RedirectServlet could implement this interface. Then
your JSP can also access these constants via this
interface.
But then again, this is merely a matter of style, I
fully agree that there is never a real _need_ to put
constants in a separate structure if they're only used
in a single class.Are you claiming that your example above is a single class?

Not using interface builder??

Hi all,
I'm new to Cocoa & Xcode and have noticed some examples (both Apples documentation & samples and some third party samples) that you can create your views, navigation controllers etc programatically and not use IB.
I'm wondering if some experienced cocoa & xcode progranners can let me know if their is anything I should be aware of before choosing a certain workflow method.
For instance a simple iphone app might have
1. Splash or Intro screen
2. Main menu + possible sub menus
3. Main app
4. Additional prefs or info screens
Is there any point to using IB if all I do is setup my initial window and UIView for the intro in IB and then all subsequent class files don't use IB?
Thanks for any pointers!
Message was edited by: david_lister

You can definitely mix methods. Use IB for situations where you are doing a lot of layout or connections, or just if you are more comfortable with it. Use code if the view is simple, or you are more comfortable with that. If you use IB, you will want to split your xib files up so the app doesn't have to load one big file.

Installing DCNM-SAN as a VSB in Nexus 1010

Hi everyone,
I'm trying to install DCNM-SAN as a VSB in Nexus 1010, as I've read on the release notes that since 5.2.x release the distribution is done via a single image and there's an image available right now for 5.2(2)...
But, although I've tried numerous times (together with reading a lot through the two available documents - Installation and licensing guide and Fundamentals), every time I create a new vsb with these images, it becomes a DCNM-LAN install.
I have yet to have any prior experience with DCNM, so I might be missing something.
Any ideas? What am I missing? Am I trying to do something that is not supported? Or, am I just missing a critical point there?
NOTE: This is currently a lab topology, but I have a customer that's very keen on using DCNM-SAN with their MDS switches. And I feel that having this on a the 1010 as a vsb is the best way to do it, if it can be done, with regards to having network staff not deal with servers etc.
Thanks,
Emre

Andrew,
We are a little frustrated with the VSB version of DCNM-SAN, it does not appear possible to manage fabric without advanced licensing for the switches, in the licensing guides for DCNM it lists essentials capability that should include port, switch, and fabric-level configuration. On the windows version we can manage the fabric unlicensed as long as we do it from the server direcly or in previous versions if we are running stand alone. These options do not appear to exist for the VSB version. Is there any plan to include any essentials capability in the VSB/OVF versions of the DCNM-SAN. If this is not planned, the documentation should be changed to state that essentials functions are only available in the Windows version.

Nexus 5548 not responding to snmp

I've got a Nexus 5548 running 6.0(2)N2(3). It does not use the mgmt interface or management vrf. It's using a vlan interface for all my management access.
I have a simple snmp config set up:
snmp-server community mystring
My SNMP server is directly connected (no firewalls, no acls). I can ping my nexus from the SNMP host, but can't get SNMP replies.
I've done an SNMP debug, nothing happens when I run an snmpwalk. I also checked show snmp, and it's showing no SNMP input packets.
Could this have something to do with trying to use the management vrf? Or something simple I'm missing?
Thanks

Ha wow -- "sh run snmp" pointed me to the problem. There was a command:
no snmp-server protocol enable
That must be a default, I never entered that. Anyway a 'snmp-server protocol enable' fixed it. I should have caught that. Although an hour with TAC also didn't notice it hehe.
Thanks!

How can use interface in JSP?

hi! friends i have one dought in JSP? it's possible interface in JSP? how?
waiting for ur reply!

hi
i think u can not use interface in JSP but u can extend a class which implements an interface

DCNM-SAN as Nexus 1010 VSB

Does anybody know if (and when) DCNM-SAN will be available as a Nexus 1010 VSB, as it is with DCNM-LAN now?
PS: Here is my previous question on how (as I wrongly assumed it was possible, looking at the documentation), which was answered by Padma (a generous and kind Cisco employee).
Thanks,
Emre

Hi Andrew,
Great news, thanks... Looking forward for the release

DCNM-SAN supporting FI

Using DCNM-SAN with UCS (2.1.2a); I created on all FC devices (MDS and N5k) a user "dcnmuser" with netadmin rights. I also created a snmp v3 user "dcnmuser" with UCSM. Then I did a fabric discovery with DCNM-SAN; I see the fabric, MDS, N5k and FI, however, the FI have a red arrow, which means not manageable.
Q. what could be wrong ? or is this really supported ?

Understood, thanks Robert
We only want to monitor UCS-FI with DCNM-SAN.
The release notes 6.1.2
http://www.cisco.com/en/US/docs/switches/datacenter/sw/6_x/dcnm/release/notes/dcnm_6_1_relnotes.html
are quite misleading:
Introduction
Cisco Data Center Network Manager combines the management of Ethernet and storage networks into a single dashboard to help network and storage administrators manage and troubleshoot health and performance across the following product families that run Cisco NX-OS software:
•Cisco MDS 9500 Series Multilayer Directors and Cisco MDS 9200 and 9100 Series Multilayer Switches
•Cisco Nexus 1000V Series Switches and Cisco Nexus 1010 Virtual Services Appliance
•Cisco Nexus 2000 Series Fabric Extenders
•Cisco Nexus 3000, 4000, 5000, and 7000 Series Switches
•Cisco Catalyst 6500 Series Switches
•Cisco UCS 6100 and 6200 Series Fabric Interconnects
•Cisco FireWall Service Module (FWSM)
Cisco DCNM-SAN Release 6.1(1b) and later releases do not support Cisco Nexus 5000 Series switches and UCS devices running Cisco NX-OS Release 4.1(3) or an earlier release.
However, Table 9 Hardware Features Supported by Cisco DCNM Release 6.1
doesn't show UCS FI !

DCNM SAN Client - SNMP Timeout

Hello Everyone,
right now iam struggling with the configuration of a DCNM SAN Client.
The Installation and licensing (with some trouble) has been finished few days ago.The DCNM LAN Client is working well and there are no problems with connectivity or timeouts. SSH and SNMPv3 are working fine for both Clients (SAN&LAN).
Discovering Fabrics for the DCNM SAN Client is working very well to. But when I start the DCNM SAN Client and open a session to a fabric it looks like this:
If I try to "edit local full zone database" it looks like this:
Tried to troubleshoot this behaviour but at the moment I am not able to figure out the problem.
Maybe someone in this community does?
Best Regards,
Sascha

This can be closed.
I got all answers... For the benefit of others who are searching answers for the same question:
1) I just downloaded the dcnm client for LAN ... is there a seperate client for SAN ? I dont see any download links for SAN... --- Yes .. DCNM SAN has a seperate client. After installation, you can open the DCNM page on http, and you would find the download links on top right corner for DCNM-LAN, SAN and device manager.
2) Is it possible to add brocade switches to DCNM-SAN? Does it require additional licenses? - I dont think this is possible
3) Can we use the fabric manager license "N5000FMS1k9" for DCNM SAN, or do we need "DCNM-SAN-N5K-K9" license for the nexus 5000? - Yes.. Use the same license and generate the PAK file. FMS licenses do work in DCNM-SAN..
Good luck

Prime DCNM 6.1(2) - LAN client not working

Hello Everyone,
I've recently installed a Prime DCNM 6.1(2) to a Windows 2008 R2 SP1 64 bit version. It seems to be working fine, apart from the DCNM-LAN client.
If I login with the Java client, I got the GUI, however it remains blank - I can see the menu, but no data at all. It seems it cannot cummunicate with the DCNM server. DCNM-SAN client, the WEB client and the Device manager works fine, but I just cannot make this work.
Tested it from Win2k3 SP2, Windows 7, and the server itself, with Java 1.6.31, 1.6.37, 1.7.13.
Tried to install DCNM on our LAB as well, but I've experienced the same.
Any hints appreciated!
Kind regards,
Gabor

Hi All,
      I also have met this issue! However, I want to know whether the deep discovery must need SNMPV3 or not. My client just gave me the N7K username and password, I used the information to discovery the N7K successfully and the dcnm-lan client still can't display anything.
     DCNM version is 6.1(2) and window platform is win 2008 R2 standard 64 bit
    Thx in advance!
     After setting the SNMPv3, we still find nothing in the dcnm-lan client as given below:
Regards,
Tira
消息编辑者为：tira li

Cannot InterVlan on Cisco Nexus 5500

Dear All,
I have problem with my nexus 5500,
Intervlan on my nexus not work,
i dont know why..
Before i have only this kind of license:
Feature                      Ins Lic   Status Expiry Date Comments
                                 Count
FCOE_NPV_PKG                  No    -   Unused             -
FM_SERVER_PKG                 No    -   Unused             -
ENTERPRISE_PKG                Yes   -   Unused Never       -
FC_FEATURES_PKG               Yes   -   Unused Never       -
VMFEX_FEATURE_PKG             Yes   -   Unused Never       -
ENHANCED_LAYER2_PKG           No    -   Unused             -
LAN_BASE_SERVICES_PKG         No    -   Unused        -
LAN_ENTERPRISE_SERVICES_PKG   No    -   Unused             -
and feature i used is :
- feature privilege
- feature telnet
- feature interface-vlan
- feature hsrp
- feature dhcp
- feature lldp
I make few vlan on nexus and then i check the interface status and the result is all vlan Interface is UP but intervlan is not work.
And then, i install license for LAN_BASE_SERVICES_PKG, this is result for install licensed:
Feature                      Ins Lic   Status Expiry Date Comments
                                 Count
FCOE_NPV_PKG                  No    -   Unused             -
FM_SERVER_PKG                 No    -   Unused             -
ENTERPRISE_PKG                Yes   -   Unused Never       -
FC_FEATURES_PKG               Yes   -   Unused Never       -
VMFEX_FEATURE_PKG             Yes   -   Unused Never       -
ENHANCED_LAYER2_PKG           No    -   Unused             -
LAN_BASE_SERVICES_PKG         Yes   -   In use Never       -
LAN_ENTERPRISE_SERVICES_PKG   No    -   Unused             -
I used vlan configuration vlan before, but the interface VLAN is DOWN/DOWN.
and then i read this article:
http://www.layerzero.nl/blog/2012/10/nexus-5000-non-routable-vdc-mode/
Yes, thats solution work for 1 Vlan with "management" command on interface VLAN.
But, the other vlan is still DOWN. and Intervlan is not work to.
Anyone, can help me please?
I have experience configure Nexus 5000 with VPC, FEX, Storage, etc, and everything fine without isue in intervlan.
Thanks.

Marvin,
This is the output.
`show module`
Mod Ports Module-Type                       Model                  Status
1   48    O2 48X10GE/Modular Supervisor     N5K-C5596UP-SUP        active *
Mod Sw              Hw      World-Wide-Name(s) (WWN)
1    5.2(1)N1(1b)    1.0     --
`show interface brief`
Ethernet      VLAN    Type Mode   Status Reason                   Speed     Port
Interface                                                                    Ch #
Eth1/1        1       eth trunk up      none                        10G(D) --
Eth1/2        1       eth trunk up      none                        10G(D) --
Eth1/3        1       eth trunk up      none                        10G(D) --
Eth1/4        1       eth trunk up      none                        10G(D) --
Eth1/5        1       eth trunk down    Link not connected          10G(D) --
Eth1/6        1       eth trunk up      none                        10G(D) --
Eth1/7        1       eth trunk up      none                        10G(D) --
Eth1/8        1       eth trunk down    Link not connected          10G(D) --
Eth1/9        1       eth access down    SFP not inserted            10G(D) --
Eth1/10       1       eth access down    SFP not inserted            10G(D) --
Eth1/11       1       eth access down    SFP not inserted            10G(D) --
Eth1/12       1       eth access down    SFP not inserted            10G(D) --
Eth1/13       1       eth access down    SFP not inserted            10G(D) --
Eth1/14       1       eth access down    SFP not inserted            10G(D) --
Eth1/15       1       eth access down    SFP not inserted            10G(D) --
Eth1/16       1       eth access down    SFP not inserted            10G(D) --
Eth1/17       1       eth access down    SFP not inserted            10G(D) --
Eth1/18       1       eth access down    SFP not inserted            10G(D) --
Eth1/19       1       eth access down    SFP not inserted            10G(D) --
Eth1/20       1       eth access down    SFP not inserted            10G(D) --
Eth1/21       1       eth access down    SFP not inserted            10G(D) --
Eth1/22       1       eth access down    SFP not inserted            10G(D) --
Eth1/23       1       eth access down    SFP not inserted            10G(D) --
Eth1/24       1       eth access down    SFP not inserted            10G(D) --
Eth1/25       1       eth access down    SFP not inserted            10G(D) --
Eth1/26       1       eth access down    SFP not inserted            10G(D) --
Eth1/27       1       eth access down    SFP not inserted            10G(D) --
Eth1/28       1       eth access down    SFP not inserted            10G(D) --
Eth1/29       1       eth access down    SFP not inserted            10G(D) --
Eth1/30       1       eth access down    SFP not inserted            10G(D) --
Eth1/31       1       eth access down    SFP not inserted            10G(D) --
Eth1/32       1       eth access down    SFP not inserted            10G(D) --
Eth1/33       1       eth access down    SFP not inserted            10G(D) --
Eth1/34       1       eth access down    SFP not inserted            10G(D) --
Eth1/35       1       eth access down    SFP not inserted            10G(D) --
Eth1/36       1       eth access down    SFP not inserted            10G(D) --
Eth1/37       1       eth access down    SFP not inserted            10G(D) --
Eth1/38       1       eth access down    SFP not inserted            10G(D) --
Eth1/39       1       eth access down    SFP not inserted            10G(D) --
Eth1/40       1       eth access down    SFP not inserted            10G(D) --
Eth1/41       1       eth access down    SFP not inserted            10G(D) --
Eth1/42       1       eth access down    SFP not inserted            10G(D) --
Eth1/43       1       eth access down    SFP not inserted            10G(D) --
Eth1/44       1       eth access down    SFP not inserted            10G(D) --
Eth1/45       1       eth access down    SFP not inserted            10G(D) --
Eth1/46       1       eth access down    SFP not inserted            10G(D) --
Eth1/47       1       eth trunk down    SFP not inserted            10G(D) --
Eth1/48       1       eth trunk down    SFP not inserted            10G(D) --
Port   VRF          Status IP Address                              Speed    MTU
mgmt0 --           down   --                                      --       1500
Interface Secondary VLAN(Type)                    Status Reason
Vlan1     --                                      down   Administratively down
Vlan199   --                                      up     --
Vlan999   --                                      down   Non-routable VDC mode
sh ip int bri
IP Interface Status for VRF "default"(1)
Interface            IP Address      Interface Status
Vlan199              192.168.36.10   protocol-up/link-up/admin-up
Vlan999              192.168.99.1    protocol-down/link-down/admin-up
sh vlan
VLAN Name                             Status    Ports
1    default                          active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/9, Eth1/10, Eth1/11
                                                Eth1/12, Eth1/13, Eth1/14
                                                Eth1/15, Eth1/16, Eth1/17
                                                Eth1/18, Eth1/19, Eth1/20
                                                Eth1/21, Eth1/22, Eth1/23
                                                Eth1/24, Eth1/25, Eth1/26
                                                Eth1/27, Eth1/28, Eth1/29
                                                Eth1/30, Eth1/31, Eth1/32
                                                Eth1/33, Eth1/34, Eth1/35
                                                Eth1/36, Eth1/37, Eth1/38
                                                Eth1/39, Eth1/40, Eth1/41
                                                Eth1/42, Eth1/43, Eth1/44
                                                Eth1/45, Eth1/46, Eth1/47
                                                Eth1/48
5    A                       active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/47, Eth1/48
199 B                          active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/47, Eth1/48
391 C                     active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/47, Eth1/48
392 D                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/47, Eth1/48
393 E                       active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/47, Eth1/48
394 F                        active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/47, Eth1/48
395 G                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/47, Eth1/48
500 H                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/47, Eth1/48
526 I                      active    Eth1/1, Eth1/2, Eth1/3, Eth1/4
                                                Eth1/5, Eth1/6, Eth1/7, Eth1/8
                                                Eth1/47, Eth1/48
VLAN Type Vlan-mode
1    enet CE
5    enet CE
199 enet CE
391 enet CE
392 enet CE
393 enet CE
394 enet CE
395 enet CE
500 enet CE
526 enet CE
Remote SPAN VLANs
Primary Secondary Type             Ports

Nexus 5500 to Nexus 5500 Fiber Etherchannel with different lengths

Hi,
I'm in the very first phase of designing a small datacenter infrastructure based on the Nexus 5500 series. I haven't got any hands-on nexus experience yet so please forgive me if I'm asking a silly question here...
What I would like to build is a 4 unit, redundant datacenter design. Two units in one DC, and two units in the other. I would like to connect both DCs together using a redundant darkfiber. One link is 10 miles, the other is 20 miles.
The Nexus switches are going to be connected "back-to-back" with and the redundant etherchannel between the DCs, like this http://www.netcraftsmen.net/component/content/article/69-data-center/859-configuring-back-to-back-vpcs-on-cisco-nexus-switches.html
Can I expect any problems with this design? In particular with the different lengths of fiber, like buffering issues or failing transmissions?
Thanks!

That should not be an issue. You will need single mode fiber and single mode optics, and as long as all your optics support distance of 20 miles or more, then you should be fine.
HTH

The payment method R in country SM is not used in any company code

Hello.
In transaction FBZP I choose "Payment Method/Country overview"
I open SM (San Marino) and I choose "Use in company code" I obtain the message:
The payment method R in country SM is not used in any company code
What have I to do?
Thanks.
Mario
Edited by: Ferruccio Galli on May 7, 2009 10:41 AM
No news for me, please?

Hi ,
Go through below path for confiquration patteren
Path: SPRO  Financial Accounting  Accounts receivable and accounts payable  Business transactions  out going payments  Automatic out going payments  Payment method/ bank  selection for payment program (Transactions code: FBZP)
set up payments method per country for payment transactions
Set up Payment methods for company code for payment transactions
Set up All Company codes for payment transactions:
Set up paying company code for payment transactions:
Bank determination:
Regards
Surya

Nexus 5500 - Fabricpath Core Port - Error disabled. Reason:DCX-No ACK in 100 PDUs

Has anyone seen Fabricpath Core Interfaces between two Nexus 5596UP switches error-disabled because of missing DCBX Acks after 50mins?
I do not see interface errors and the peer is another 5500.
Both switches are running 5.1(3)N2(1) with this port config:
int e1/3
switchport mode fabricpath
! Cisco 5m Twinax cables
Log messages
2012 May 25 17:40:59 nexus1 %L3VM-5-FP_TPG_INTF_DOWN: Interface Ethernet1/3 down in fabricpath topology 0 - Interface down
2012 May 25 17:40:59 nexus1 %ETHPORT-5-IF_DOWN_NONE: Interface Ethernet1/3 is down (None)
2012 May 25 17:40:59 nexus1 %ISIS_FABRICPATH-5-ADJCHANGE: isis_fabricpath-default [3365] P2P adj L1 nexus5 over Ethernet1/3 - DOWN (Delete All) on MT-0
2012 May 25 17:40:59 nexus1 %CDP-5-NEIGHBOR_REMOVED: CDP Neighbor nexus5(FOX1550GDH1) on port Ethernet1/3 has been removed
2012 May 25 17:40:59 nexus1 %LLDP-5-SERVER_REMOVED: Server with Chassis ID 547f.ee63.fa88 Port ID Eth1/1 on local port Eth1/3 has been removed
2012 May 25 17:40:59 nexus1 %ETHPORT-2-IF_DOWN_ERROR_DISABLED: Interface Ethernet1/3 is down (Error disabled. Reason:DCX-No ACK in 100 PDUs)
Robert

Can you send the output of
show lldp interface ethernet 1/3
show lldp dcbx interface ethernet 1/3
a workaround may be to disable lldp on both sides on these physical interfaces

Nexus 5500 duplicate ICMP echo-replay

I am experiencing inconsistent echo-replay from devices connected via VPC to Nexus 5500s while pinging from the Nexus exec prompt.
In some cases I receive normal response when pinging from one Nexus, but no response when pinging from the other switch. In other instance I receive normal response to one Nexus, and duplicate replays to the other. It looks like a VPC related bug. NXOS is 5.1.3.N2.1
5501# ping 10.12.12.232
PING 10.12.12.232 (10.12.12.232): 56 data bytes
64 bytes from 10.12.12.232: icmp_seq=0 ttl=253 time=8.585 ms
64 bytes from 10.12.12.232: icmp_seq=0 ttl=254 time=9.227 ms (DUP!)
64 bytes from 10.12.12.232: icmp_seq=1 ttl=253 time=1.011 ms
64 bytes from 10.12.12.232: icmp_seq=2 ttl=253 time=8.097 ms
64 bytes from 10.12.12.232: icmp_seq=2 ttl=254 time=9.429 ms (DUP!)
64 bytes from 10.12.12.232: icmp_seq=3 ttl=253 time=18.195 ms
64 bytes from 10.12.12.232: icmp_seq=4 ttl=253 time=8.807 ms
5502# ping 10.12.12.232
PING 10.12.12.232 (10.12.12.232): 56 data bytes
64 bytes from 10.12.12.232: icmp_seq=0 ttl=254 time=0.985 ms
64 bytes from 10.12.12.232: icmp_seq=1 ttl=254 time=0.884 ms
64 bytes from 10.12.12.232: icmp_seq=2 ttl=254 time=0.875 ms
64 bytes from 10.12.12.232: icmp_seq=3 ttl=254 time=3.105 ms
64 bytes from 10.12.12.232: icmp_seq=4 ttl=254 time=8.378 ms
Thanks
Jarek

Hi
I found this in the configuration guide for the Nexus 7000 configuring VPCs
"When you enable this feature (peer-gateway), Cisco NX-OS automatically disables IP redirects on all interface VLANs mapped over a vPC VLAN to avoid generation of IP redirect messages for packets switched through the peer gateway router."
However this is not happening automatically on the 5K, so you need to manually add "no ip redirects" on each VPC vlan interface to prevent duplicate pings.

DCNM SAN 6.2 + Nexus 5500 not using interface mgmt

Similar Messages

Maybe you are looking for