cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
291
Views
0
Helpful
0
Replies
Highlighted
Beginner

Issue while adding four Nexus 5548UP-FA to an existing fabricpath

Hello,

a client of us has suffered a strange problem when they have connected the three new pairs of Nexus 5548UP-FA to their existing fabricpath network made by Nexus 7k (version 6.1(4a)) and Nexus 5k (version 5.2(1)N1(6)). I don't know the exactly models, but I can ask if needed.

In the existing fabricpath, there was 2 N7k and 6 N5k pairs (with vPC).

They have tried to add 3 N5k pairs (with vPC too) but only 1 pair were added without problems. The other two launched the next block of messages and caused problems in the multicast traffic causing a bad behaviour in the fabricpath network (which is their core).

Note: the next is the block related to one N5k.

May  8 02:05:45 NEX-N7k_1 : 2015 May  8 02:05:45 CEST: %CDP-5-NEIGHBOR_ADDED: Device NEX-N5k-71.cm.es(SSI18450262) discovered of type N5K-C5548UP with port Ethernet1/3 on incoming port Ethernet4/37 with ip addr 172.31.1.57 and mgmt ip 10.64.72.239
May  8 02:05:45 NEX-N7k_1 : 2015 May  8 02:05:45 CEST: %ISIS_FABRICPATH-5-ADJCHANGE:  isis_fabricpath-default [7859]  P2P adj L1 NEX-N5k-71 over Ethernet4/37 - DOWN (New) on MT-0
May  8 02:05:45 NEX-N7k_1 : 2015 May  8 02:05:45 CEST: %ISIS_FABRICPATH-5-ADJCHANGE:  isis_fabricpath-default [7859]  P2P adj L1 NEX-N5k-71 over Ethernet4/37 - INIT on MT-0
May  8 02:05:45 NEX-N7k_1 : 2015 May  8 02:05:45 CEST: %ISIS_FABRICPATH-5-ADJCHANGE:  isis_fabricpath-default [7859]  P2P adj L1 NEX-N5k-71 over Ethernet4/37 - UP on MT-0
May  8 02:05:47 NEX-N7k_1 : 2015 May  8 02:05:47 CEST: %ETHPORT-5-IF_UP: Interface Ethernet4/37 (description:NEX-N5k-71-1/3) is up in mode fabricpath
May  8 02:05:47 NEX-N7k_1 : 2015 May  8 02:05:47 CEST: %L3VM-5-FP_TPG_INTF_UP: Interface Ethernet4/37 up in fabricpath topology 0
May  8 02:06:04 NEX-N7k_1 : 2015 May  8 02:06:04 CEST: %ARP-4-INVAL_IP:  arp [7667]  Received packet with invalid destination IP address (10.64.226.255) from 0010.18e9.2599 on Vlan296
May  8 02:06:14 NEX-N7k_1 : 2015 May  8 02:06:14 CEST: %ARP-4-SYSLOG_SL_MSG_WARNING: ARP-4-INVAL_IP: message repeated 2 times in last 718 sec 
May  8 02:06:38 NEX-N7k_1 : 2015 May  8 02:06:38 CEST: %CDP-5-NEIGHBOR_REMOVED: CDP Neighbor NEX-N5k-71.cm.es(SSI18450262) on port Ethernet4/37 has been removed
May  8 02:06:38 NEX-N7k_1 : 2015 May  8 02:06:38 CEST: %ETHPORT-5-IF_DOWN_CFG_CHANGE: Interface Ethernet4/37 (description:NEX-N5k-71-1/3) is down(Config change)
May  8 02:06:38 NEX-N7k_1 : 2015 May  8 02:06:38 CEST: %L3VM-5-FP_TPG_INTF_DOWN: Interface Ethernet4/37 down in fabricpath topology 0 - Interface down
May  8 02:06:40 NEX-N7k_1 : 2015 May  8 02:06:40 CEST: %ISIS_FABRICPATH-5-ADJCHANGE:  isis_fabricpath-default [7859]  P2P adj L1 NEX-N5k-71 over Ethernet4/37 - TOPO-ADJ UP on MT-0
May  8 02:06:41 NEX-N7k_1 : 2015 May  8 02:06:41 CEST: %ISIS_FABRICPATH-5-ADJCHANGE:  isis_fabricpath-default [7859]  P2P adj L1 NEX-N5k-71 over Ethernet4/37 - DOWN (Delete All) on MT-0
May  8 02:06:42 NEX-N7k_1 : 2015 May  8 02:06:42 CEST: %ETHPORT-5-IF_DOWN_ADMIN_DOWN: Interface Ethernet4/37 (description:NEX-N5k-71-1/3) is down (Administratively down)


It is very weird that a N5k pair, with exactly the same configuration than the other two, has casued no issues. 

Do you think they have reached a limitation? Where? 
Summary:
Old topology: 2 N7k + 12 N5k
New topology: 2 N7k + 14 N5k
Failed topology: 2 N7k + 18 N5k

Thank you very much for your help.

 

 

 

Everyone's tags (1)