Tier-1 Gateway 생성
Networking > Tier-1 Gateways > ADD TIER-1 GATEWAY
- Name : tier1-01
- Connected Gateway : tier0-01
- Edge Cluster : edge-cl01
- Route Advertisement : All Connected Segments & Service Ports, All NAT IP's, All LB VIP Routes
테스트용 Segment 생성
Networking > Segments > ADD SEGMENT
- Name : overlay-seg-3101
- Connected Gateway : tier1-01
- Transport Zone : overlay-tz
- Subnets : 172.31.1.1/24
- Additional Settings : VLAN 3101
신규 Segment를 위한 IP Pool 생성
Segment에서 IP Pool 설정 수정
Virtual Router에서 신규로 생성한 Segment의 Subnet 정보가 전파되었는지 확인
vyos@vyos:~$ show ip route Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP, T - Table, v - VNC, V - VNC-Direct, A - Babel, D - SHARP, F - PBR, f - OpenFabric, > - selected route, * - FIB route, q - queued route, r - rejected route S>* 0.0.0.0/0 [210/0] via x.x.x.254, eth0, 18:09:59 C>* x.x.x.0/20 is directly connected, eth0, 18:10:00 B>* 172.31.1.0/24 [20/0] via 192.168.12.11, eth4.1612, 00:01:27 ### <-- !! * via 192.168.13.11, eth5.1613, 00:01:27 C>* 192.168.1.0/24 is directly connected, eth1, 16:06:55 C>* 192.168.10.0/24 is directly connected, eth2.1610, 18:07:16 C>* 192.168.11.0/24 is directly connected, eth3.1611, 18:07:17 C>* 192.168.12.0/24 is directly connected, eth4.1612, 18:07:16 C>* 192.168.13.0/24 is directly connected, eth5.1613, 18:07:17 |
Edge에서도 Routing Table 정보 확인
C:\Users\Administrator>ssh admin@edge-node-01.contoso.com admin@edge-node-01.contoso.com's password: * TIPS: To reconfig management interface, please refer to these CLIs 1) stop service dataplane 2) set interface interface-name vlan vlan-id plane mgmt (for creating vlan sub-interface) 3) set interface interface-name ip x.x.x.x/24 gateway x.x.x.x plane mgmt (for static ip) set interface interface-name dhcp plane mgmt (for dhcp) 4) start service dataplane set interface interface-name dhcp plane mgmt (for dhcp) 4) start service dataplane To config in-band management interface, please refer to these CLIs 1) set interface mac mac-addr vlan vlan-id in-band plane mgmt 2) set interface eth0.vlan ip x.x.x.x/24 gateway x.x.x.x plane mgmt (for static ip) set interface eth0.vlan dhcp plane mgmt (for dhcp) NSX CLI (Edge 4.1.1.0.0.22224325). Press ? for command list or enter: help edge-node-01> get logical-router Mon Sep 11 2023 UTC 04:01:00.686 Logical Router UUID VRF LR-ID Name Type Ports Neighbors 736a80e3-23f6-5a2d-81d6-bbefb2786666 0 0 TUNNEL 4 5/5000 ec318044-8bd6-4269-aa47-544ee747f765 1 2 SR-tier0-01 SERVICE_ROUTER_TIER0 6 2/50000 73bdcf75-0251-4927-9c80-68a6d7265911 3 1 DR-tier0-01 DISTRIBUTED_ROUTER_TIER0 5 2/50000 064b8812-743c-427a-b0b6-801570118070 4 9 SR-tier1-01 SERVICE_ROUTER_TIER1 5 2/50000 92045476-c754-48e1-a86a-1ac4f9961112 5 8 DR-tier1-01 DISTRIBUTED_ROUTER_TIER1 4 0/50000 edge-node-01> vrf 1 edge-node-01(tier0_sr[1])> get route Flags: t0c - Tier0-Connected, t0s - Tier0-Static, b - BGP, o - OSPF t0n - Tier0-NAT, t1s - Tier1-Static, t1c - Tier1-Connected, t1n: Tier1-NAT, t1l: Tier1-LB VIP, t1ls: Tier1-LB SNAT, t1d: Tier1-DNS FORWARDER, t1ipsec: Tier1-IPSec, isr: Inter-SR, ivs: Inter-VRF-Static, > - selected route, * - FIB route Total number of routes: 11 b > * x.x.x.0/20 [20/0] via 192.168.12.1, uplink-279, 00:47:45 b > * x.x.x.0/20 [20/0] via 192.168.13.1, uplink-286, 00:47:45 t0c> * 100.64.0.0/31 is directly connected, downlink-293, 00:11:51 t0c> * 169.254.0.0/24 is directly connected, backplane-283, 00:48:10 t1c> * 172.31.1.0/24 [3/0] via 100.64.0.1, downlink-293, 00:04:22 b > * 192.168.1.0/24 [20/0] via 192.168.12.1, uplink-279, 00:47:45 b > * 192.168.1.0/24 [20/0] via 192.168.13.1, uplink-286, 00:47:45 b > * 192.168.10.0/24 [20/0] via 192.168.12.1, uplink-279, 00:47:45 b > * 192.168.10.0/24 [20/0] via 192.168.13.1, uplink-286, 00:47:45 b > * 192.168.11.0/24 [20/0] via 192.168.12.1, uplink-279, 00:47:45 b > * 192.168.11.0/24 [20/0] via 192.168.13.1, uplink-286, 00:47:45 t0c> * 192.168.12.0/24 is directly connected, uplink-279, 01:49:55 t0c> * 192.168.13.0/24 is directly connected, uplink-286, 01:49:39 t0c> * fc14:9b49:677c:6c00::/64 is directly connected, downlink-293, 00:11:51 t0c> * fe80::/64 is directly connected, backplane-283, 00:48:10 Mon Sep 11 2023 UTC 04:01:54.658 |
테스트 용도의 VM을 생성하고, VM Network Adatper에 overlay-seg-3101 port group 설정하고 VM Power On
172.31.1.2 IP Address를 할당
Gateway 주소인 172.31.1.1로 Ping 테스트
아래 환경에서 네트워크 연결 테스트
172.31.1.2(Overlay) → 192.168.1.2(VLAN)
192.168.1.2(VLAN) → 172.31.1.2(Overlay)
C:\Users\Administrator>tracert -d 172.31.1.1 Tracing route to 172.31.1.1 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 <1 ms <1 ms <1 ms 192.168.12.11 ### <-- !! Edge Uplink 3 2 ms <1 ms <1 ms 172.31.1.1 Trace complete. C:\Users\Administrator>tracert -d 172.31.1.2 Tracing route to 172.31.1.2 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 <1 ms <1 ms <1 ms 192.168.12.11 ### <-- !! Edge Uplink 3 <1 ms <1 ms <1 ms 100.64.0.1 ### <-- !! Tier0 <-> Tier1 Inter Routing 4 4 ms <1 ms <1 ms 172.31.1.2 Trace complete. C:\Users\Administrator>ping 172.31.1.2 Pinging 172.31.1.2 with 32 bytes of data: Reply from 172.31.1.2: bytes=32 time=1ms TTL=125 Reply from 172.31.1.2: bytes=32 time=1ms TTL=125 Reply from 172.31.1.2: bytes=32 time=1ms TTL=125 Reply from 172.31.1.2: bytes=32 time=1ms TTL=125 Ping statistics for 172.31.1.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms |
'Networking' 카테고리의 다른 글
BFD Overview (0) | 2023.09.25 |
---|---|
[NSX] NAT 설정 및 Traffic Flow (1) | 2023.09.16 |
[NSX] Setup - 7. Tier-0 Gateway 생성 및 BGP 연결 (0) | 2023.09.16 |
[NSX] Setup - 6. Edge Uplink Profile 생성과 Edge 설치 (0) | 2023.09.16 |
[NSX] Setup - 5. Host Uplink Profile 생성과 Transport Node 설치 (0) | 2023.09.16 |