Nexus aggregation switching

Hi All
Need abit help in implementing Nexus 5548UP and NExus 2K fex configuration, basicallay i have end of 2 row switching with Nexus 5K, is it wise to dual home nexus 2k to single 5K ??
Please help
Kumar

Hi Chien-Hsing Wu, I just ran into this post, sorry I couldn´t reply to your original one. Since I did not see an explanation on how to get 960 Mpps, I included one for you:
The 960 Mpps number you mentioned is calculated taking in account modules with one M1 forwarding engine, which is the case for modules such as N7K-M132XP-12, for example. Other modules use a M1 forwarding engine (some newer modules use even 2 forwarding engines).
The "M1" indicates the forwarding engine is M Series, first generation and is capable of delivering 60 Mpps of Layer 2 and 3 IPv4 unicast or 30 Mpps of IPv6 unicast for all ports on that module.
You can use up to 16 I/O Modules on the 7018, which brings the 16 (forwarding engines)* 60 (mpps if M1) = 960 Mpps.
Be aware that more recent modules use even dual M1-XL forwarding engines, delivering 120 Mpps L2 and 3 IPv4 unicast or 60 Mpps IPv6, and others use F1 forwarding engines, delivering 480 Mpps of distributed L2 unicast per module.
On the other hand, regarding the calculations you suggest with 230 Gbps, some documentation shows 7.8 Tbps as total switching capacity for the 7018. You get that number assuming you are using Fabric 1 modules, or Fabric modules from 1st generation. If this is the case, calculation is as follows:
     230 Gbps per slot for the I/O related slots
     115 Gbps for the supervisors
     (16 * 230) + (2 * 115) = 3910 Gbps, and taking in account full duplex transmission we multiply this by 2 and get the 7.8 Tbps.
As mentioned by Amit Singh, if we use Fabric 2 modules each slot could *potentially* use 550 Gbps (depending on the module), which is the total crossbar bandwidth available for each slot if your chassis is equiped with 5 Fabric 2 modules, as opposed to the 230 Gbps when the fabric modules are 1st generation modules.
HTH
Leo Pastor

Similar Messages

What are the major differences between a Access Switch and Aggregation Switch w.r.t Carrier Ethernet domain?

In a Carrier Ethernet domain,Could someone please help me understand what's the basic difference between Access Switch and Aggregation Switch both in terms of s/w and h/w functionalities. MEF deals OAM,CFM, EVC provisioning only at the access edge switches. Do we need to repeat all these at the aggregation level? or is it just used for routing purpose? Do we have a separate Fault Management at the aggregation level?

Duplicate posts. :P
Go here: https://supportforums.cisco.com/discussion/12137156/what-are-major-differences-between-access-switch-and-aggregation-switch-wrt

FCoE with Cisco Nexus 5548 switches and VMware ESXi 4.1

Can someone share with me what needs to be setup on the Cisco Nexus side to work with VMware in the following scenario?
Two servers with two cards dual port FCoE cards with two ports connected to two Nexus 5548 switches that are clusterd together. We want to team the ports together on the VMware side using IP Hash so what should be done on the cisco side for this to work?
Thanks...

Andres,
The Cisco Road Map for the 5010 and 5020 doesn't include extending the current total (12) FEX capabities. The 5548 and 5596 will support more (16) per 55xxk, and with the 7K will support upto 32 FEX's.
Documentation has been spotty on this subject, because the term 5k indicates that all 5000 series switches will support extended FEX's which is not the case only the 55xx will support more than 12 FEX. Maybe in the future the terminology for the 5k series should be term 5000 series and 5500 series Nexus, there are several differences and advancements between the two series.

Design thoughts: Replacing a L2 aggregation switch

Hi,
I have purchased a 4507R switch to replace a 2924M-XL switch that acts as an aggregation switch in our network. Let me explain further what I plan to do.
I have 20 remote sites connected point to point via 100 Mbps dark fibre to the 2924M-XL. Most of the sites have only a handful of users but 5 of them are bigger (ie. 20-70 users). Some of the larger remote sites (small campuses really) have 2-5 switches in a star topology with the "hub" switch connecting back to the 2924M-XL. Each site has 1 or 2 user VLANs and a management VLAN. The 2924M-XL trunks all VLANs back to a 6513 at the core of our network.
I will be connecting the 4507R along 2 seperate dark fibre runs (for layer 1 redundancy) to 2 6513s in our core. This will give us fault-tolerence should our primary 6513 fail.
My problem is I'm struggling with the decision to go layer 2 or layer 3 between the 4507R and the 6513s. Layer 2 would be alot easier to implement and support (I'm the sole administrator of this rather large network) but then I'd have RSTP to deal with among the 2 6513s and 4507. I'm comfortable with RSTP since I run it between 2950G switches dual connected to the 6513s but my gut feeling is that I should be putting in layer 3 between the 6513s and the 4507.
We will be implementing VoIP is the next 2 years and I'm unsure how that affects my decision.
One last comment. Would layer 2 trunking of VLANs from the 4507 to the 6513s WITHOUT trunking these VLANs between the 6513s be a viable optionand would HSRP between the 2 6513s still work OK for layer 3 redundany? The remotes sites are setup with unique user VLANs but there is a special use VLAN that spans 4 of the sites and my manegement VLAN spans all the sites (I'm planning to change this).
Thanks everyone for your thought/opinions.
Ian.

Hi there Ian,
I'm a big fan of routing over switching, which I read is becoming Cisco's recommended way of doing things.
I would route between the 2 x 6513's and the 4507 as it will not only give you fault tolerance, but also load balancing, plus cutting down on broadcast domains and all those other nice things.
As far as configuration goes, onec you've got it up and running, then it'll just keep running. It seems like you will only need straight forward routing here and nothing too complex. Setting it up would be a simple affair.
VoIP, in my experience, is much better implemented over a routed network than a switched one. There are loads more things that you can do at layer 3 than you can at layer 2. Think about all the QoS that you'll be able to implement, with shaping and policing, etc. Much more security can be built in at layer 3 too. You'll get the likes of NBAR and all other features that you'll be able to (over time) tweak you network with.
As for performance, you'll never spot a difference. The 4507 will be lots faster than the 2924 and using cef, the 4507 will keep a forwarding table for ip's the same way a 2900 keeps a mac table.
You will not regret routing it.
Hope this helps - if so, please give it a rating.
LH

6504E Aggregation Switch (VS-C6504E-S720-10G)

Hi,
I am in the process of understanding the 6504E in terms of technically feasible option as a Provider Class Aggregation Switch. (specifically looking at VS-C6504E-S720-10G, which is bundled option)
This 6504E switch will aggregate our Provider Edge (PE) routers and then connect to Core routers via uplink ports. Multiple PE routers (each via 1G port) would be aggregated to 6504E. The aggregation switch would then connect to core routers via 10G uplink port.
While short listing the aggregation switch, I come across VS-C6504E-S720-10G which has Catalyst Chassis + Fan Tray+Sup720-10G; IP Base ONLY; NO VSS. Though this looks a better choice for provider class switch .But, I am still not clear if this bundle option can support all the below requirements.
1. Multiple 1Gig/10Gig for Access/Uplink on aggregation - this is supported.
2. OIR feature for line card , modules, power supply - this is supported.
Not sure if VS-C6504E-S720-10G support all the below mandatory requirement
3. Traffic from PE will be MPLS labelled or non-MPLS labelled traffic so Aggregation Switch must have capable to look MPLS header ( i.e Lable, MPLS EXP bit) and IP header ( dscp, src SA, dst SA etc) when configured as Layer 2 port facing to PE - Not sure if VS-C6504E-S720-10G can support it.
4. Aggregation switch should support link aggregation for N*10G uplink to Core router with various load-balancing method like MPLS label based, src-IP, dst-IP, src-dst-IP, hashing of layer 3 and layer 4 info , L2 S-mac & d-mac etc - - Not sure if VS-C6504E-S720-10G can support it.
5. QOS on L2 switches for strict priority queue, WRR/SRR Queue to support policing and shaping with WRED with miinimum 8 egress queue per port.
6. QoS classification based on 802.1P, MPLS EXP, IP DSCP on layer 2 ports for MPLS and non MPLS traffic.
7. Multicast - IGMP V1/V2/V3, IGMP Snooping, PIM snooping.

Pradeep,
This is a loaded question. I would suggest you get in touch with the system engineer assigned to your company in order for him to run through all these requirements and validate that this piece of equipment meets them all.
Regards

Cisco Nexus 5596T Switch question

when did the Cisco Nexus 5596T Switch hit the market?

I don't remember exactly, but it's been a while.
Looking at the release notes it shows support as of Cisco NX-OS Release 5.2(1)N1(1b) and looking at the software download page this was released as of 25-September 2012.
Regards

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.

The meaning of Interface Ethernet250/1 under the Nexus 2000 is connected to Nexus 5000 switch

Dear all,
Recently, I prepared and deploy a network monitoring system to monitor the new generation Nexus connected network. With using snmpwalk to query the interfacs information from the Nexus 5000 switch (one Nexus 2000 is connected to it via FlexLink), I found that other than normal Nexus 5000 and 2000 ports(ifName to be Ethernet1/1, Ethernet1/2, ... Ethernet190/1/1, Ethernet190/1/2...), a series of interface with ifName Ethernet250/1, Ethernet250/2, .... to be appeared in the interface SNMP tree. With logged into the Nexus 5000 and issue display interface command, I can only found the information on the normal interfaces but not the abnormal interface Ethernet250/1, ...
Would someone know what is it (do E250/1 is a logical interface like port channel or VLAN) and how to monitor it ? Thanks in advances.
HC Wong

I've not seen that myself. Could it perhaps be a VPC (Virtual Portchannel)?

Nexus 5596 switch-profile synchronization problem

hi
I can't synchronize switch-profile
System version: 5.1(3)N1(1)
Sync-status: Not yet merged
Merge Flags: pending_merge:0 rcv_merge:1 pending_validate:1
Status: Verify Failure
Error(s):
Following commands failed parsing: If the error is 'Command Parsing Failed', please check if some conditional feature(s) needs to be enabled
switchport mode trunk (Command Parsing Failed)
how to find the source of the problem ?

Hello Pawel
Can you attach following from both Nexus 5596 switches in question
term length 0
show version
show run
show tech-support port-profile

Nexus 3548 Switch doesn't recognize command " vtp mode Server / Client"

Hi Community.
I have a brand new Nexus 3548 switch. And I did the vtp setup:
vtp version 2
vtp password ******
vtp domain *****
Every thing is ok, but If I use the command "vtp mode server" the switch doesn't know that command. Even it doesn't know the "vtp mode" subcommand?
What's the problem ?
Best regards patrick

The Nexus 3548 supports only Transparent mode:
Step 5 vtp mode {transparent| off} Sets the VTP mode to transparent or off.
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3548/sw/layer_2_switching/b_Cisco_N3548_Layer_2_Switching_Config_503A1.pdf
I have no clue why.
Patrick

Nexus 3064 switch: Can't get MAC addresses through SNMP

Hello Everyone!
I'm seeing an issue in our Nexus 3064 switch where we can't get the MAC address table using SNMP. At the same time, I can see MAC addresses of all the ports from the switch command line (show mac address-table). I've verified that SNMP is enabled and I can fetch other switch information (such as VLANs) using SNMP.
I did an SNMP walk to get the mac (
snmpwalk -v2c -c <communityString>@<VlanID> <ManagementIP> 1.3.6.1.2.1.17.4.3.1), and it didnt return anything.
Could any of you please let me know what can be potentially wrong here? Really appreciate your help.
Thanks for your time!

Greetings Vipins,
This could be caused by CSCto56055 "not getting any value for dot1dtpFdbTable objects", resolved in 5.0(3)U1(2) and later releases.
Kind Regards,
/Phil

Cisco Nexus 5548UP Switch Current Version 5.2(1)N1(4)

Hi, we're currently have Cisco Nexus 5548UP Switch Current Version 5.2(1)N1(4)
It's not listed as affected version:
Known Affected Releases:
(5)
5.2(1)N1(8a)
6.0(2)N2(5)
7.0(3)N1(0.125)
7.0(4)N1(1)
7.1(0)N1(0.349)
The Known Fixed Releases as follow:
Known Fixed Releases:
(7)
6.0(2)N2(4.3)
6.0(2)N2(5a)
7.0(1)ZN(0.615)
7.0(5)N1(0.173)
7.0(5)N1(1)
7.1(0)N1(0.371)
7.1(0)N1(1)
Do we need to update to the latest releases?
If yes, which version of the known fixed release is best suit our current version
Cisco Nexus 5548UP Switch Current Version 5.2(1)N1(4)
Thanks.

I had the same question, so I opened a TAC case to find the right software version. I was told that the software listed as available on the bug report were custom NX-OS builds and that there are no patched versions available for the 5548p. The support engineer also said that the Nexus 5k upgrades were not expected until November or December. The best advice I could get was to subscribe to the bug report and wait to be notified of an available upgrade.

FCoE using Brocade cards CNA1020 and Cisco Nexus 5548 switches

All,
I have the following configuration and problem that I am not sure how to fix:
I have three Dell R910 servers with 1TB of memory and each has two brocade 1020 CNA cards dual port. I am using distributed switches for the VM network and a second distributed switch for VMotion. I have two of the 10G ports configured in each distributed switch using IP Hash. The management network is configured using a standard switch with two 1G ports.
The Nexus configuration is we have two nexus 5548 switch connected together with a trunk. We have two VPC's configured to each ESX hosts consisting of two 10gig ports in each VPC with one port going to each switch. The VPC is configured for static LAG.
What I am seeing is that after a few hours the virtual machines will not be accessible via network anymore. So if you ping the VM it will not work and if you get on the console of the VM then ping the gateway then nothing as well but if you try to ping another virtual machine on the same host on the same VLAN then it will work so traffic is going through the ESX backplane. If I reboot the ESX host then things will work again for another few hours or so then the problem repeats.
The version of vSphere I am using is ESXi4.1
Please assist I am stuck.
Thanks...

Here is the link for Nexus and Brocade interoperability Matrix
http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/Matrix7.html#wp313498
usually this table would show those models those have been tested and verified
However I do not see Brocade 5300 listed in the table . It could be, interoperability may have not been tested by both vendors perticularly to 5300 type Model.

Very low transfer speed issue on SUN4270 M2 server connected with nexus 5548 switch on 10GB fiber.

                   Hi,
I have 2 SUN 4270 M2 servers connected with Nexus 5548 switch over 10Gb fiber card. I am getting performance of just 60 MB per second while transfer of 5Gb file across 2 servers. The similar speed i use to get on 1Gb network also. Please suggest how to improve the tranfer speed. On servers, ports ET4 and ETH5 are bonded in bond0 with mode=1. The server envrionment will be used for OVS 2.2.2.
Below are the details of network configuration on server. I quick help will be highly appriciated--
[root@host1 network-scripts]# ifconfig eth4
eth4      Link encap:Ethernet HWaddr 90:E2:BA:0E:22:4C
          UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1
          RX packets:5648589 errors:215 dropped:0 overruns:0 frame:215
          TX packets:3741680 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2492781394 (2.3 GiB) TX bytes:3911207623 (3.6 GiB)
[root@host1 network-scripts]# ifconfig eth5
eth5      Link encap:Ethernet HWaddr 90:E2:BA:0E:22:4C
          UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1
          RX packets:52961 errors:215 dropped:0 overruns:0 frame:215
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3916644 (3.7 MiB) TX bytes:0 (0.0 b)
[root@host1 network-scripts]# ethtool eth4
Settings for eth4:
        Supported ports: [ FIBRE ]
        Supported link modes:   1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes: 1000baseT/Full
                                10000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 10000Mb/s
        Duplex: Full
        Port: FIBRE
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000007 (7)
        Link detected: yes
[root@host1 network-scripts]# ethtool eth5
Settings for eth5:
        Supported ports: [ FIBRE ]
        Supported link modes:   1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes: 1000baseT/Full
                                10000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 10000Mb/s
        Duplex: Full
        Port: FIBRE
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000007 (7)
        Link detected: yes
[root@host1 network-scripts]#
[root@host1 network-scripts]# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.2.4 (January 28, 2008)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth4
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth4
MII Status: up
Link Failure Count: 0
Permanent HW addr: 90:e2:ba:0e:22:4c
Slave Interface: eth5
MII Status: up
Link Failure Count: 0
Permanent HW addr: 90:e2:ba:0e:22:4d
[root@host1 network-scripts]# modinfo ixgbe | grep ver
filename:       /lib/modules/2.6.18-128.2.1.4.44.el5xen/kernel/drivers/net/ixgbe/ixgbe.ko
version:        3.9.17-NAPI
description:    Intel(R) 10 Gigabit PCI Express Network Driver
srcversion:     31C6EB13C4FA6749DF3BDF5
vermagic:       2.6.18-128.2.1.4.44.el5xen SMP mod_unload Xen 686 REGPARM 4KSTACKS gcc-4.1
[root@host1 network-scripts]#brctl show
bridge name     bridge id               STP enabled     interfaces
vlan301         8000.90e2ba0e224c       no              bond0.301
vlan302         8000.90e2ba0e224c       no              vif1.0
                                                        bond0.302
vlan303         8000.90e2ba0e224c       no              bond0.303
vlan304         8000.90e2ba0e224c       no              bond0.304
[root@host2 test]# ifconfig eth5
eth5      Link encap:Ethernet HWaddr 90:E2:BA:0F:C3:15
          UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1
          RX packets:4416730 errors:215 dropped:0 overruns:0 frame:215
          TX packets:2617152 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:190977431 (182.1 MiB) TX bytes:3114347186 (2.9 GiB)
[root@host2 network-scripts]# ifconfig eth4
eth4      Link encap:Ethernet HWaddr 90:E2:BA:0F:C3:15
          UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1
          RX packets:28616 errors:3 dropped:0 overruns:0 frame:3
          TX packets:424 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4982317 (4.7 MiB) TX bytes:80029 (78.1 KiB)
[root@host2 test]#
[root@host2 network-scripts]# ethtool eth4
Settings for eth4:
        Supported ports: [ FIBRE ]
        Supported link modes:   1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes: 1000baseT/Full
                                10000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 10000Mb/s
        Duplex: Full
        Port: FIBRE
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000007 (7)
        Link detected: yes
[root@host2 test]# ethtool eth5
Settings for eth5:
        Supported ports: [ FIBRE ]
        Supported link modes:   1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes: 1000baseT/Full
                                10000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 10000Mb/s
        Duplex: Full
        Port: FIBRE
        PHYAD: 0
        Transceiver: external
        Auto-negotiation: on
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000007 (7)
        Link detected: yes
[root@host2 network-scripts]# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.2.4 (January 28, 2008)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth5
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Slave Interface: eth5
MII Status: up
Link Failure Count: 0
Permanent HW addr: 90:e2:ba:0f:c3:14
Slave Interface: eth4
MII Status: up
Link Failure Count: 0
Permanent HW addr: 90:e2:ba:0f:c3:15
[root@host2 network-scripts]# modinfo ixgbe | grep ver
filename:       /lib/modules/2.6.18-128.2.1.4.44.el5xen/kernel/drivers/net/ixgbe/ixgbe.ko
version:        3.9.17-NAPI
description:    Intel(R) 10 Gigabit PCI Express Network Driver
srcversion:     31C6EB13C4FA6749DF3BDF5
vermagic:       2.6.18-128.2.1.4.44.el5xen SMP mod_unload Xen 686 REGPARM 4KSTACKS gcc-4.1
[root@host2 network-scripts]#brctl show
bridge name     bridge id               STP enabled     interfaces
vlan301         8000.90e2ba0fc315       no              bond0.301
vlan302         8000.90e2ba0fc315       no              bond0.302
vlan303         8000.90e2ba0fc315       no              bond0.303
vlan304         8000.90e2ba0fc315       no              vif1.0
       bond0.304
Thanks....
Jay

Hi,
Thanks for reply..but the RX errors count is keep on increasing and the transfer speed between 2 servers are max 60MB/ps on 10GB FC card. Even on storage also, i am getting the same speed when i try to transfer data from server to storage on 10GB FC card. Servers and storage are connected through Nexus 5548 switch.
#ifconfig eth5
eth5      Link encap:Ethernet HWaddr 90:E2:BA:0E:22:4C
          UP BROADCAST RUNNING SLAVE MULTICAST MTU:9000 Metric:1
          RX packets:21187303 errors:1330 dropped:0 overruns:0 frame:1330
          TX packets:17805543 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:624978785 (596.0 MiB) TX bytes:2897603160 (2.6 GiB)
JP

Nexus 5000 switch-profile sync via SVI?

Hi,
is it possible to use a Vlan interface (SVI) for syncing the switch profile on two 5596?
I tried this:
2 x 5596UP with NX-OS 5.2(1)N1(3)
Connected with 2 x Twinax on ports Eth1/15 and /16, portchannel 3.
The Po3 is a trunk, allowed Vlan is 439. Both 5596 have a SVI in Vlan439 with an IP. I can ping between the two 5596.
# ping 10.9.8.4
PING 10.9.8.4 (10.9.8.4): 56 data bytes
64 bytes from 10.9.8.4: icmp_seq=0 ttl=254 time=0.887 ms
When I try to to this:
switch-profile k
sync-peers destination 10.9.8.4
I get:
# sh switch-profile status
switch-profile : k
Start-time: 831222 usecs after Thu Aug 15 17:57:53 2013
End-time: 834086 usecs after Thu Aug 15 17:57:53 2013
Profile-Revision: 7
Session-type: Initial-Exchange
Session-subtype: Init-Exchange-All
Peer-triggered: No
Profile-status: -
Local information:
Status: -
Error(s):
Peer information:
IP-address: 10.9.8.4
Sync-status: Not yet merged
Merge Flags: pending_merge:1 rcv_merge:0 pending_validate:0
Status: Peer not reachable
Error(s):
As soon as I change the sync-peers destinations to use the IPs on the mgmt0 interface everything works fine:
# sh switch-profile status
switch-profile : k
Start-time: 723075 usecs after Thu Aug 15 18:04:23 2013
End-time: 475957 usecs after Thu Aug 15 18:04:25 2013
Profile-Revision: 7
Session-type: Commit
Session-subtype: -
Peer-triggered: No
Profile-status: Sync Success
Local information:
Status: Commit Success
Error(s):
Peer information:
IP-address: 10.0.0.4
Sync-status: In sync
Status: Commit Success
Error(s):

No, if you want a short answer.
Or...
Switch-Profiles feature will only work using mgmt0 interface. Here's the quote from
Cisco Nexus 5500 Series NX-OS System Management Configuration Guide, Release 6.x
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5500/sw/system_management/6x/b_5500_System_Mgmt_Config_602N12_chapter_011.html
Guidelines and Limitations for Switch Profiles
Consider the following guidelines and limitations when configuring switch profiles:
You can only enable configuration synchronization using the mgmt0 interface.
-- the rest of output is cut for brevity --
Cheers
Tim
P.S. Please rate this post.

Nexus aggregation switching

Similar Messages

Maybe you are looking for