Table of Contents 1 OSPF SCENARIOS WITH NEXUS 56128, NX-OS 7.0.5

Size: px

Start display at page:

Download "Table of Contents 1 OSPF SCENARIOS WITH NEXUS 56128, NX-OS 7.0.5"

Rosalind Gibbs
6 years ago
Views:

1 Scenarios with Nexus 56128, Table of Contents 1 SCENARIOS WITH NEXUS 56128, SCENARIO #1A SCENARIO #1B SCENARIO #2A SCENARIO #2B 5 1 SCENARIOS WITH NEXUS 56128, Here are different routing scenarios to interconnect 2 remote sites (A and B) with a Datacenter whose LAN Core switches are based on 2 Nexus with : 1. Scenario #1a SVI via Peer-Link between both N5K 2. Scenario #1b SVI via Peer-Link between both N5K + between and the 2 N5K 3. Scenario #2a Separated Layer 3 Link between both N5K 4. Scenario #2b Separated Layer 3 Link between both N5K + between and the 2 N5K SVI, in this document, stands for Switch Virtual Interface, corresponds to a definition of interface vlan xxx with an IP addresse assigned to this interface, as opposed to an L3 Link (used for Scenarios 2a, 2b) which corresponds to a physical interface defined with no switchport parameter and an IP address; Although it is not mentionned in the scenarios drawings, apart from the SVI interfaces which are used as a Point-to-Point IP subnets to route traffic between the different sites, there are also some extended (geographic) VLANs shared between Remote Sites A,B and (normally over WAN1 network only) Main objectives of this document are to explicit, as much as possible, the different supported and/or recommanded routing scenarios to interconnect 1 remote site (mainly Remote Site A in the different drawnings) with a Datacenter based on the cluster of the 2 Nexus Version 2.0 Page 1/5

2 Scenarios with Nexus 56128, 1.1 Scenario #1a 1) non VPC ==> int VLAN 301 allowed only on non PO Links between and ==> adjacency between and 2) SVI 302 non VPC ==> int VLAN 302 allowed only on non PO Links between and ==> 1 st adjacency between and 3) SVI 310 over Peer-Link ==> int VLAN 310 allowed only over Peer-Links between and ==> adjacency between and only via this SVI 310 4) non VPC ==> int VLAN 303 allowed only on non Link between and, via WAN2 network ==> 2 nd adjacency between and : backup path in case of WAN1 Failure Routing : Scenario #1a SVI via Peer-Link between both N5K SVI SVI 310 Peer-Link a) Is there any potential problem/restriction with having SVI 310 and associated adjacency between both N5K over Peer-Link? b) Are Multicast frames supported over Peer-Link? if yes, where is it clearly documented? can this problem be solved by using only ip ospf network point-to-point when configuring all concerned int VLAN (301, 302, 310), which should eliminate Multicat frames over those int VLANs? is there a problem or is it a pre-requisite to code peer-gateway parameter on vpc domain x of both N5K? c) to back up the SVI 310 over Peer-Link, an IP non interface could be set up between both N5K (with higher cost) : any problem with this backup IP link? Version 2.0 Page 2/5

3 Scenarios with Nexus 56128, 1.2 Scenario #1b 1) VPC ==> int VLAN 301 via PO Links between and both N5K ==> adjacencies between and each N5K over this 2) SVI 310 over Peer-Link ==> int VLAN 310 allowed only over Peer-Links between and ==> adjacency between and only via this SVI 310 3) non VPC ==> int VLAN 303 allowed only on non Link between and, via WAN2 network ==> 2 nd adjacency between and : backup path in case of WAN1 Failure Routing : Scenario #1b SVI via Peer-Link between both N5K + between and the 2 N5K LACP 0 SVI 310 Peer-Link This scenario is generally described as unsupported by CISCO for static routing (with ECMP) or dynamic routing : see here : But, it seems this is supported for Nexus 5500 : see penultimate scenario which indicates it is supported with N5500 for unicasttraffic only, here : a) Is it really supported with Nexus 5500? is it documented by CISCO anywhere? b) Is there any potential problem/restriction with this scenario 1b? Version 2.0 Page 3/5

4 Scenarios with Nexus 56128, 1.3 Scenario #2a 1) non VPC ==> int VLAN 301 allowed only on non PO Links between and ==> adjacency between and 2) SVI 302 non VPC ==> int VLAN 302 allowed only on non PO Links between and ==> 1 st adjacency between and 3) non Layer 3 int between both N5K ==> non IP interface between both N5K ==> adjacency between and only via this interface 4) non VPC ==> int VLAN 303 allowed only on non Link between and, via WAN2 network ==> 2 nd adjacency between and Routing : Scenario #2a Separated Layer 3 Link between both N5K SVI Peer-Link non L3 Link a) Is there any potential problem/restriction with this scenario 2a? Version 2.0 Page 4/5

5 Scenarios with Nexus 56128, 1.4 Scenario #2b 1) VPC ==> int VLAN 301 via PO Links between and both N5K ==> adjacencies between and each N5K over this 2) non Layer 3 int between both N5K ==> non IP interface between both N5K ==> adjacency between and only via this interface 3) non VPC ==> int VLAN 303 allowed only on non Link between and, via WAN2 network ==> 2 nd adjacency between and Routing : Scenario #2b Separated Layer 3 Link between both N5K + between and the 2 N5K LACP 0 Peer-Link non L3 Link Sames remarks as for Scenario #1b a) Is there any potential problem/restriction with this scenario 2b? Version 2.0 Page 5/5

ARCHITETTURA DATA CENTERS AS-IS

ARCHITETTURA DATA CENTERS AS-IS 7K1-VDC -AGGREG po1 7K2-VDC-AGGREG po100 po200 po100 po200 7K1-VDC-DIST1 po1 7K2-VDC-DIST1 po1 VDC-DIST3 po1 7K1-VDC-DIST2 7K2-VDC-DIST2 Distribution / Core level N7K-1-AGGREG