Skip to content

J
joohanhong
Commit 9465b991 authored by JooHan Hong's avatar JooHan Hong
Browse files
Options

Static Routing 작성

parent 76eac4cc
Pipeline #5104 passed with stages
      in 3 seconds
      Hide whitespace changes
      Inline Side-by-side
      Showing with 655 additions and 0 deletions
      NETWORKING/STATIC/README.md 0 → 100644
      View file @ 9465b991
      [![logo](https://www.hongsnet.net/images/logo.gif)](https://www.hongsnet.net)
      # www.hongsnet.net Internal Networking
      > 내부 관리망으로 사용되는 네트워킹 구성요소의 구축내역이며, 여기서 사용되는 기술은 Static Routing Protocol 이다.
      ## Overview
      ![source_overview](./images/static-routing.png)
      ## 구성목적 (**Current**)
      - www.hongsnet.net 내부 네트워크 구조를 **Static Routing Protocol**로 변경한다.
      - **Deprecated** 된 Dynamic Roting Protocol의 이슈인 혼재된 1G / 100M bps 구성을 모두 `1G bps`로 변경한다.
      - 라우팅테이블의 경우 관리자가 직접 호스트(32비트) IP를 기준으로 관리를 한다.
      - 사용자가 Default G/W로 라우팅테이블을 설정해도, 비인가된 경우 Exchange에서의 라우팅테이블이 존재하지 않기 때문에 다른 대역으로의 통신이 불가능하다(**보안적 측면**).
      ## Network Switch 구성요소
      | NO | 역할 | IP | ServiceIP | 모델명 | 비고 |
      | ------ | ------ | ------ | ------ | ------ | ------ |
      | 1 | 유저서비스용 | 10.10.10.2 | 192.168.200.0/24 | Cisco WS-C3560G-48TS, 12.2(58)SE2 (C3560-IPSERVICESK9-M) | |
      | 2 | 관리자용 | 20.20.20.2 | 172.24.0.0/16 | Cisco WS-C3560G-24T, 12.2(58)SE2 (C3560-IPSERVICESK9-M) | |
      | 3 | 개발용 | 30.30.30.2 | 172.16.0.0/16 | Cisco WS-C3750G-48TS, 12.2(35)SE5 (C3750-IPSERVICES-M) | |
      | 4 | Swtich Exchange | 10.10.10.1<br>20.20.20.1<br>30.30.30.1<br>40.40.40.1 | N/A | Cisco WS-C3750-48TS, 12.2(44)SE3 (C3750-IPSERVICESK9-M) | |
      | 5 | DBMS Routing | 40.40.40.2 | N/A | Cisco WS-C3750-48TS, 12.2(50)SE3 (C3750-IPSERVICESK9-M) | |
      | 6 | DBMS | N/A | 180.180.180.0/24 | Cisco WS-C2960G-24TC-L, 12.2(53)SE1 (C2960-LANBASEK9-M) | Layer 2 |
      ## Network Review **Key-Point**
      * [ ] `서로 다른 라우팅 프로토콜 간에는 재분배가 발생`되며, 이 설정이 반드시 존재해야 한다.
      * [ ] OSPF 프로토콜의 hello packet은 OSPF 네이버를 형성하고 유지하는데 사용되는 패킷 이다.
      * [ ] OSPF의 `DR`(Designated Router)는 프로토콜의 중심 라우터이며, `멀티액세스 네트워크`(이더넷과 같은 브로드캐스트가 지원되는 네트워크) 기반에서 동작된다. 즉, 위 구성과 같이 L3 Switch로 이루어진 OSPF 네트워크에서는
      * [ ] OSPF의 `BDR`(Backup DR)는 DR 라우터의 역할을 이어받을 수 있는 라우터 이다. 즉, `DR이 다운`되면, BDR이 DR이되며 BDR은 새로 선출한다. 만약 BDR이 다운되면, BDR을 새로 선출 한다.
      * [ ] OSPF의 `DROTHER`는 DR, BDR이 아닌 라우터를 뜻한다. 그리고 DROTHER 라우터끼리는 라우팅 정보를 교환하지 않는다.
      * [ ] OSPF의 Area1은 논브로드캐스트 네트워크로 구성되어 있으며, 시리얼로 서로 연결되어 있다.
      * [ ] 위의 구성과 같이 두 개 이상의 Area로 구성된 환경에서는 그 중 하나는 반드시 에어리어 번호를 0으로 설정해야 한다.
      ## Network Configuration
      > 아래의 내역은 `show running-config` 등과 같이 전체 내역을 표현하지않고, 핵심적인 부분만을 명시한다.
      - **유저서비스용**(192.168.200.1) 설정내역
      ```plaintext
      interface GigabitEthernet1/0/49
      description TO-IX-Gi1/0/49
      no switchport
      ip address 10.10.10.2 255.255.255.252
      !
      ...중략
      ip classless
      ip route 172.16.0.158 255.255.255.255 10.10.10.1 name TB3-WEBSERVER
      ip route 172.16.0.170 255.255.255.255 10.10.10.1 name HOSTING170
      ip route 172.16.0.221 255.255.255.255 10.10.10.1 name TB3-WIN10
      ip route 172.16.0.228 255.255.255.255 10.10.10.1 name TB3-ELK-DEMO-MASTER
      ip route 172.16.0.235 255.255.255.255 10.10.10.1 name TB3-DOCKER-TEST-NODE01
      ip route 172.16.0.236 255.255.255.255 10.10.10.1 name TB3-DOCKER-TEST-NODE02
      ip route 172.16.0.251 255.255.255.255 10.10.10.1 name TB3-DOCKER
      ip route 172.16.254.1 255.255.255.255 10.10.10.1 name TB3
      ip route 172.16.254.254 255.255.255.255 10.10.10.1 name CLASSROOM
      ip route 172.24.0.145 255.255.255.255 10.10.10.1 name TB2-REDMINE
      ip route 172.24.0.151 255.255.255.255 10.10.10.1 name TB2-WEBSERVER
      ip route 172.24.0.238 255.255.255.255 10.10.10.1 name TB2-DOCKER-TEST-MANAGER01
      ip route 172.24.0.239 255.255.255.255 10.10.10.1 name TB2-DOCKER-TEST-MANAGER02
      ip route 172.24.0.245 255.255.255.255 10.10.10.1 name TB2-DOCKER
      ip route 172.24.3.250 255.255.255.255 10.10.10.1 name TB2-VIRT-WORKSTATION
      ip route 172.24.254.1 255.255.255.255 10.10.10.1 name TB2
      ip route 172.24.254.250 255.255.255.255 10.10.10.1 name TB2-CONTENT
      ip route 180.180.180.143 255.255.255.255 10.10.10.1 name DBMS-LVS-VIP
      ip route 180.180.180.226 255.255.255.255 10.10.10.1 name DBMS-MASTER-A
      ip route 180.180.180.231 255.255.255.255 10.10.10.1 name DBMS-MASTER-B
      ip route 180.180.180.235 255.255.255.255 10.10.10.1 name DBMS-LVS-MASTER
      ip route 180.180.180.236 255.255.255.255 10.10.10.1 name DBMS-LVS-SLAVE
      ip route 180.180.180.237 255.255.255.255 10.10.10.1 name DBMS-SLAVE03
      ip route 180.180.180.239 255.255.255.255 10.10.10.1 name DBMS-MASTER
      ip route 180.180.180.242 255.255.255.255 10.10.10.1 name DBMS-SLAVE01
      ip route 180.180.180.243 255.255.255.255 10.10.10.1 name DBMS-SLAVE02
      ip route 180.180.180.246 255.255.255.255 10.10.10.1 name DBMS-ZABBIX
      ip route 180.180.180.250 255.255.255.255 10.10.10.1 name DBMS-WRITE
      ip route 180.180.180.251 255.255.255.255 10.10.10.1 name DBMS-READ
      ```
      다음은 **라우팅테이블**의 내역이다.
      ```plaintext
      #sh ip route
      Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
      D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
      N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
      E1 - OSPF external type 1, E2 - OSPF external type 2
      i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
      ia - IS-IS inter area, * - candidate default, U - per-user static route
      o - ODR, P - periodic downloaded static route
      Gateway of last resort is not set
      100.0.0.0/24 is subnetted, 1 subnets
      C 100.100.100.0 is directly connected, Vlan100
      172.16.0.0/32 is subnetted, 9 subnets
      S 172.16.0.170 [1/0] via 10.10.10.1
      S 172.16.0.158 [1/0] via 10.10.10.1
      S 172.16.254.1 [1/0] via 10.10.10.1
      S 172.16.0.251 [1/0] via 10.10.10.1
      S 172.16.0.236 [1/0] via 10.10.10.1
      S 172.16.0.235 [1/0] via 10.10.10.1
      S 172.16.0.228 [1/0] via 10.10.10.1
      S 172.16.0.221 [1/0] via 10.10.10.1
      S 172.16.254.254 [1/0] via 10.10.10.1
      172.24.0.0/32 is subnetted, 8 subnets
      S 172.24.0.151 [1/0] via 10.10.10.1
      S 172.24.0.145 [1/0] via 10.10.10.1
      S 172.24.0.245 [1/0] via 10.10.10.1
      S 172.24.254.1 [1/0] via 10.10.10.1
      S 172.24.3.250 [1/0] via 10.10.10.1
      S 172.24.0.238 [1/0] via 10.10.10.1
      S 172.24.0.239 [1/0] via 10.10.10.1
      S 172.24.254.250 [1/0] via 10.10.10.1
      C 192.168.200.0/24 is directly connected, Vlan192
      10.0.0.0/30 is subnetted, 1 subnets
      C 10.10.10.0 is directly connected, GigabitEthernet1/0/49
      180.180.0.0/32 is subnetted, 12 subnets
      S 180.180.180.143 [1/0] via 10.10.10.1
      S 180.180.180.246 [1/0] via 10.10.10.1
      S 180.180.180.242 [1/0] via 10.10.10.1
      S 180.180.180.243 [1/0] via 10.10.10.1
      S 180.180.180.250 [1/0] via 10.10.10.1
      S 180.180.180.251 [1/0] via 10.10.10.1
      S 180.180.180.231 [1/0] via 10.10.10.1
      S 180.180.180.226 [1/0] via 10.10.10.1
      S 180.180.180.236 [1/0] via 10.10.10.1
      S 180.180.180.237 [1/0] via 10.10.10.1
      S 180.180.180.239 [1/0] via 10.10.10.1
      S 180.180.180.235 [1/0] via 10.10.10.1
      ```
      - **관리자용**(172.24.0.0/16) 설정내역
      ```plaintext
      interface GigabitEthernet0/25
      description TO-IX-SWITCH-Gi/49
      no switchport
      ip address 20.20.20.2 255.255.255.252
      !
      ...중략
      ip route 10.10.10.0 255.255.255.252 20.20.20.1 name HONGS-SWITCH
      ip route 30.30.30.0 255.255.255.252 20.20.20.1 name TB3-SWITCH
      ip route 40.40.40.0 255.255.255.252 20.20.20.1 name DBMS-SWITCH
      ip route 172.16.0.158 255.255.255.255 20.20.20.1 name TB3
      ip route 172.16.0.170 255.255.255.255 20.20.20.1 name TB3-170HOSTING
      ip route 172.16.0.226 255.255.255.255 20.20.20.1 name TB3-CUBETEST-CUBE05
      ip route 172.16.0.227 255.255.255.255 20.20.20.1 name TB3-CUBETEST-CUBE06
      ip route 172.16.0.228 255.255.255.255 20.20.20.1 name TB3-ELK-DEMO-MASTER
      ip route 172.16.0.230 255.255.255.255 20.20.20.1 name TB3-DOCKER-ELK
      ip route 172.16.0.235 255.255.255.255 20.20.20.1 name TB3-DOCKER-TEST-NODE01
      ip route 172.16.0.236 255.255.255.255 20.20.20.1 name TB3-DOCKER-TEST-NODE02
      ip route 172.16.0.251 255.255.255.255 20.20.20.1 name TB3-DOCKER
      ip route 172.16.254.254 255.255.255.255 20.20.20.1 name TB3-CLASSROOM
      ip route 180.180.180.143 255.255.255.255 20.20.20.1 name DBMS-LVS
      ip route 180.180.180.205 255.255.255.255 20.20.20.1 name DBMS-KEEPALIAVED-MASTER
      ip route 180.180.180.208 255.255.255.255 20.20.20.1 name DBMS-KEEPALIAVED-BACKUP
      ip route 180.180.180.209 255.255.255.255 20.20.20.1 name DBMS-KEEPALIAVED-VIP
      ip route 180.180.180.226 255.255.255.255 20.20.20.1 name DBMS-WRITE-ACTIVE
      ip route 180.180.180.228 255.255.255.255 20.20.20.1 name MHA-TEST-MASTER-ACTIVE
      ip route 180.180.180.229 255.255.255.255 20.20.20.1 name MHA-TEST-MASTER-BACKUP
      ip route 180.180.180.230 255.255.255.255 20.20.20.1 name MHA-TEST-SLAVE01
      ip route 180.180.180.231 255.255.255.255 20.20.20.1 name DBMS-WRITE-BACKUP
      ip route 180.180.180.235 255.255.255.255 20.20.20.1 name DBMS-LVS-MASTER
      ip route 180.180.180.236 255.255.255.255 20.20.20.1 name DBMS-LVS-SLAVE
      ip route 180.180.180.237 255.255.255.255 20.20.20.1 name DBMS-SLAVE03
      ip route 180.180.180.238 255.255.255.255 20.20.20.1 name DBMS-MHA
      ip route 180.180.180.239 255.255.255.255 20.20.20.1 name DBMS-MASTER
      ip route 180.180.180.240 255.255.255.255 20.20.20.1 name MHA-TEST-VIP
      ip route 180.180.180.242 255.255.255.255 20.20.20.1 name DBMS-SLAVE01
      ip route 180.180.180.243 255.255.255.255 20.20.20.1 name DBMS-SLAVE02
      ip route 180.180.180.250 255.255.255.255 20.20.20.1 name DBMS-WRITE
      ip route 180.180.180.251 255.255.255.255 20.20.20.1 name DBMS-READ
      ip route 180.180.180.254 255.255.255.255 20.20.20.1 name DBMS-L2-SWITCH
      ip route 192.168.200.62 255.255.255.255 20.20.20.1 name HONGSNET
      ip route 192.168.200.148 255.255.255.255 20.20.20.1 name USERS-PROXY
      ip route 192.168.200.211 255.255.255.255 20.20.20.1 name USERS-PROXY-SLAVE
      ip route 192.168.200.216 255.255.255.255 20.20.20.1 name USERS-PROXY-VIP
      ip route 192.168.200.217 255.255.255.255 20.20.20.1 name HONGSNET-STAG
      ip route 192.168.200.220 255.255.255.255 20.20.20.1 name DEV-220
      ip route 192.168.200.224 255.255.255.255 20.20.20.1 name DEV-224
      ip route 192.168.200.233 255.255.255.255 20.20.20.1 name HAPROXY-MASTER
      ip route 192.168.200.234 255.255.255.255 20.20.20.1 name HAPROXY-SLAVE
      ip route 192.168.200.242 255.255.255.255 20.20.20.1 name ADMIN-PROXY-MASTER
      ip route 192.168.200.243 255.255.255.255 20.20.20.1 name ADMIN-PROXY-SLAVE
      ip route 192.168.200.244 255.255.255.255 20.20.20.1 name HAPROXY-VIP
      ip route 192.168.200.249 255.255.255.255 20.20.20.1 name UTILS-POSTFIX
      ```
      다음은 **라우팅테이블**의 내역이다.
      ```plaintext
      #sh ip route
      Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
      D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
      N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
      E1 - OSPF external type 1, E2 - OSPF external type 2
      i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
      ia - IS-IS inter area, * - candidate default, U - per-user static route
      o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
      + - replicated route, % - next hop override
      Gateway of last resort is not set
      10.0.0.0/30 is subnetted, 1 subnets
      S 10.10.10.0 [1/0] via 20.20.20.1
      20.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
      C 20.20.20.0/30 is directly connected, GigabitEthernet0/25
      L 20.20.20.2/32 is directly connected, GigabitEthernet0/25
      30.0.0.0/30 is subnetted, 1 subnets
      S 30.30.30.0 [1/0] via 20.20.20.1
      40.0.0.0/30 is subnetted, 1 subnets
      S 40.40.40.0 [1/0] via 20.20.20.1
      172.16.0.0/32 is subnetted, 10 subnets
      S 172.16.0.158 [1/0] via 20.20.20.1
      S 172.16.0.170 [1/0] via 20.20.20.1
      S 172.16.0.226 [1/0] via 20.20.20.1
      S 172.16.0.227 [1/0] via 20.20.20.1
      S 172.16.0.228 [1/0] via 20.20.20.1
      S 172.16.0.230 [1/0] via 20.20.20.1
      S 172.16.0.235 [1/0] via 20.20.20.1
      S 172.16.0.236 [1/0] via 20.20.20.1
      S 172.16.0.251 [1/0] via 20.20.20.1
      S 172.16.254.254 [1/0] via 20.20.20.1
      172.24.0.0/16 is variably subnetted, 2 subnets, 2 masks
      C 172.24.0.0/16 is directly connected, Vlan172
      L 172.24.254.1/32 is directly connected, Vlan172
      180.180.0.0/32 is subnetted, 20 subnets
      S 180.180.180.143 [1/0] via 20.20.20.1
      S 180.180.180.205 [1/0] via 20.20.20.1
      S 180.180.180.208 [1/0] via 20.20.20.1
      S 180.180.180.209 [1/0] via 20.20.20.1
      S 180.180.180.226 [1/0] via 20.20.20.1
      S 180.180.180.228 [1/0] via 20.20.20.1
      S 180.180.180.229 [1/0] via 20.20.20.1
      S 180.180.180.230 [1/0] via 20.20.20.1
      S 180.180.180.231 [1/0] via 20.20.20.1
      S 180.180.180.235 [1/0] via 20.20.20.1
      S 180.180.180.236 [1/0] via 20.20.20.1
      S 180.180.180.237 [1/0] via 20.20.20.1
      S 180.180.180.238 [1/0] via 20.20.20.1
      S 180.180.180.239 [1/0] via 20.20.20.1
      S 180.180.180.240 [1/0] via 20.20.20.1
      S 180.180.180.242 [1/0] via 20.20.20.1
      S 180.180.180.243 [1/0] via 20.20.20.1
      S 180.180.180.250 [1/0] via 20.20.20.1
      S 180.180.180.251 [1/0] via 20.20.20.1
      S 180.180.180.254 [1/0] via 20.20.20.1
      192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks
      C 192.168.1.0/24 is directly connected, Vlan192
      L 192.168.1.1/32 is directly connected, Vlan192
      192.168.200.0/32 is subnetted, 13 subnets
      S 192.168.200.62 [1/0] via 20.20.20.1
      S 192.168.200.148 [1/0] via 20.20.20.1
      S 192.168.200.211 [1/0] via 20.20.20.1
      S 192.168.200.216 [1/0] via 20.20.20.1
      S 192.168.200.217 [1/0] via 20.20.20.1
      S 192.168.200.220 [1/0] via 20.20.20.1
      S 192.168.200.224 [1/0] via 20.20.20.1
      S 192.168.200.233 [1/0] via 20.20.20.1
      S 192.168.200.234 [1/0] via 20.20.20.1
      S 192.168.200.242 [1/0] via 20.20.20.1
      S 192.168.200.243 [1/0] via 20.20.20.1
      S 192.168.200.244 [1/0] via 20.20.20.1
      S 192.168.200.249 [1/0] via 20.20.20.1
      ```
      - **개발용**(172.16.0.0/16) 설정내역
      ```plaintext
      interface GigabitEthernet0/49
      description TO-IX-SWITCH-Gi1/0/51
      no switchport
      ip address 30.30.30.2 255.255.255.252
      !
      ...중략
      ip route 10.10.10.0 255.255.255.252 30.30.30.1 name IX
      ip route 20.20.20.0 255.255.255.252 30.30.30.1 name IX
      ip route 30.30.30.0 255.255.255.252 30.30.30.1 name IX
      ip route 40.40.40.0 255.255.255.252 30.30.30.1 name IX
      ip route 50.50.50.0 255.255.255.252 30.30.30.1 name IX
      ip route 172.24.0.151 255.255.255.255 30.30.30.1 name TB2
      ip route 172.24.0.222 255.255.255.255 30.30.30.1 name TB2-DOCKER-CUBETEST-CUBE01
      ip route 172.24.0.223 255.255.255.255 30.30.30.1 name TB2-DOCKER-CUBETEST-CUBE02
      ip route 172.24.0.224 255.255.255.255 30.30.30.1 name TB2-CUBETEST-CUBE03
      ip route 172.24.0.225 255.255.255.255 30.30.30.1 name TB2-CUBETEST-CUBE04
      ip route 172.24.0.229 255.255.255.255 30.30.30.1 name TB2-ELK
      ip route 172.24.0.238 255.255.255.255 30.30.30.1 name TB2-DOCKER-TEST-MANAGE01
      ip route 172.24.0.239 255.255.255.255 30.30.30.1 name TB2-DOCKER-TEST-MANAGE02
      ip route 172.24.0.245 255.255.255.255 30.30.30.1 name TB2-DOCKER
      ip route 180.180.180.143 255.255.255.255 30.30.30.1 name DBMS-LVS
      ip route 180.180.180.226 255.255.255.255 30.30.30.1 name DBMS-LVS-MASTER-ACTIVE
      ip route 180.180.180.231 255.255.255.255 30.30.30.1 name DBMS-LVS-MASTER-BACKUP
      ip route 180.180.180.235 255.255.255.255 30.30.30.1 name DBMS-LVS-MASTER
      ip route 180.180.180.236 255.255.255.255 30.30.30.1 name DBMS-LVS-MASTER
      ip route 180.180.180.237 255.255.255.255 30.30.30.1 name DBMS-SLAVE03
      ip route 180.180.180.239 255.255.255.255 30.30.30.1 name DBMS-MASTER
      ip route 180.180.180.242 255.255.255.255 30.30.30.1 name DBMS-SLAVE01
      ip route 180.180.180.243 255.255.255.255 30.30.30.1 name DBMS-SLAVE02
      ip route 180.180.180.250 255.255.255.255 30.30.30.1 name DBMS-WRITE
      ip route 180.180.180.254 255.255.255.255 30.30.30.1 name DBMS-L2-GW
      ip route 192.168.200.62 255.255.255.255 30.30.30.1 name HONGSNET
      ip route 192.168.200.148 255.255.255.255 30.30.30.1 name USERS-PROXY
      ip route 192.168.200.208 255.255.255.255 30.30.30.1 name REDIS-MASTER
      ip route 192.168.200.209 255.255.255.255 30.30.30.1 name REDIS-MASTER
      ip route 192.168.200.211 255.255.255.255 30.30.30.1 name USERS-PROXY-SLAVE
      ip route 192.168.200.212 255.255.255.255 30.30.30.1 name REDIS-SLAVE
      ip route 192.168.200.216 255.255.255.255 30.30.30.1 name USERS-PROXY-VIP
      ip route 192.168.200.217 255.255.255.255 30.30.30.1 name HONGSNET-STAG
      ip route 192.168.200.233 255.255.255.255 30.30.30.1 name HAPROXY-MASTER
      ip route 192.168.200.234 255.255.255.255 30.30.30.1 name HAPROXY-SLAVE
      ip route 192.168.200.242 255.255.255.255 30.30.30.1 name ADMIN-PROXY-MASTER
      ip route 192.168.200.243 255.255.255.255 30.30.30.1 name ADMIN-PROXY-SLAVE
      ip route 192.168.200.244 255.255.255.255 30.30.30.1 name HAPROXY-VIP
      ip route 192.168.200.249 255.255.255.255 30.30.30.1 name UTILS-POSTFIX
      ```
      다음은 **라우팅테이블**의 내역이다.
      ```plaintext
      #sh ip route
      Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
      D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
      N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
      E1 - OSPF external type 1, E2 - OSPF external type 2
      i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
      ia - IS-IS inter area, * - candidate default, U - per-user static route
      o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
      + - replicated route, % - next hop override
      Gateway of last resort is not set
      10.0.0.0/30 is subnetted, 1 subnets
      S 10.10.10.0 [1/0] via 30.30.30.1
      20.0.0.0/30 is subnetted, 1 subnets
      S 20.20.20.0 [1/0] via 30.30.30.1
      30.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
      C 30.30.30.0/30 is directly connected, GigabitEthernet0/49
      L 30.30.30.2/32 is directly connected, GigabitEthernet0/49
      40.0.0.0/30 is subnetted, 1 subnets
      S 40.40.40.0 [1/0] via 30.30.30.1
      50.0.0.0/30 is subnetted, 1 subnets
      S 50.50.50.0 [1/0] via 30.30.30.1
      172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks
      C 172.16.0.0/16 is directly connected, Vlan172
      L 172.16.254.1/32 is directly connected, Vlan172
      172.24.0.0/32 is subnetted, 9 subnets
      S 172.24.0.151 [1/0] via 30.30.30.1
      S 172.24.0.222 [1/0] via 30.30.30.1
      S 172.24.0.223 [1/0] via 30.30.30.1
      S 172.24.0.224 [1/0] via 30.30.30.1
      S 172.24.0.225 [1/0] via 30.30.30.1
      S 172.24.0.229 [1/0] via 30.30.30.1
      S 172.24.0.238 [1/0] via 30.30.30.1
      S 172.24.0.239 [1/0] via 30.30.30.1
      S 172.24.0.245 [1/0] via 30.30.30.1
      180.180.0.0/32 is subnetted, 11 subnets
      S 180.180.180.143 [1/0] via 30.30.30.1
      S 180.180.180.226 [1/0] via 30.30.30.1
      S 180.180.180.231 [1/0] via 30.30.30.1
      S 180.180.180.235 [1/0] via 30.30.30.1
      S 180.180.180.236 [1/0] via 30.30.30.1
      S 180.180.180.237 [1/0] via 30.30.30.1
      S 180.180.180.239 [1/0] via 30.30.30.1
      S 180.180.180.242 [1/0] via 30.30.30.1
      S 180.180.180.243 [1/0] via 30.30.30.1
      S 180.180.180.250 [1/0] via 30.30.30.1
      S 180.180.180.254 [1/0] via 30.30.30.1
      192.168.200.0/32 is subnetted, 14 subnets
      S 192.168.200.62 [1/0] via 30.30.30.1
      S 192.168.200.148 [1/0] via 30.30.30.1
      S 192.168.200.208 [1/0] via 30.30.30.1
      S 192.168.200.209 [1/0] via 30.30.30.1
      S 192.168.200.211 [1/0] via 30.30.30.1
      S 192.168.200.212 [1/0] via 30.30.30.1
      S 192.168.200.216 [1/0] via 30.30.30.1
      S 192.168.200.217 [1/0] via 30.30.30.1
      S 192.168.200.233 [1/0] via 30.30.30.1
      S 192.168.200.234 [1/0] via 30.30.30.1
      S 192.168.200.242 [1/0] via 30.30.30.1
      S 192.168.200.243 [1/0] via 30.30.30.1
      S 192.168.200.244 [1/0] via 30.30.30.1
      S 192.168.200.249 [1/0] via 30.30.30.1
      ```
      - **Swtich Exchange**(10.10.10.0/30) 설정내역
      ```plaintext
      interface GigabitEthernet1/0/1
      description FROM-HONGS-SWITCH-Gi1/0/49
      no switchport
      ip address 10.10.10.1 255.255.255.252
      !
      interface GigabitEthernet1/0/2
      description FROM-ADMIN-SWITCH-Gi0/49
      no switchport
      ip address 20.20.20.1 255.255.255.252
      !
      interface GigabitEthernet1/0/3
      description FROM-TB3-SWITCH-Gi0/49
      no switchport
      ip address 30.30.30.1 255.255.255.252
      !
      interface GigabitEthernet1/0/4
      description FROM-DBMS-SWITCH-Gi1/0/49
      no switchport
      ip address 40.40.40.1 255.255.255.252
      !
      ...중략
      ip classless
      ip route 100.100.100.1 255.255.255.255 10.10.10.2 name HONGSNET-IPMI
      ip route 100.100.100.2 255.255.255.255 10.10.10.2 name TB2-ADMIN-IPMI
      ip route 100.100.100.4 255.255.255.255 10.10.10.2 name TB3-IPMI
      ip route 172.16.0.158 255.255.255.255 30.30.30.2 name TB3-WEBSERVER
      ip route 172.16.0.170 255.255.255.255 30.30.30.2 name HOSTING170
      ip route 172.16.0.221 255.255.255.255 30.30.30.2 name TB3-WIN10
      ip route 172.16.0.226 255.255.255.255 30.30.30.2 name TB3-CUBETEST-CUBE05
      ip route 172.16.0.227 255.255.255.255 30.30.30.2 name TB3-CUBETEST-CUBE06
      ip route 172.16.0.228 255.255.255.255 30.30.30.2 name TB3-ELK-DEMO-MASTER
      ip route 172.16.0.230 255.255.255.255 30.30.30.2 name TB3-DOCKER-ELK
      ip route 172.16.0.235 255.255.255.255 30.30.30.2 name TB3-DOCKER-TEST-NODE01
      ip route 172.16.0.236 255.255.255.255 30.30.30.2 name TB3-DOCKER-TEST-NODE02
      ip route 172.16.0.251 255.255.255.255 30.30.30.2 name TB3-DOCKER
      ip route 172.16.254.254 255.255.255.255 30.30.30.2 name TB3-CLASSROOM
      ip route 172.24.0.145 255.255.255.255 20.20.20.2 name TB2-REDMINE
      ip route 172.24.0.151 255.255.255.255 20.20.20.2 name TB2-WEBSERVER
      ip route 172.24.0.199 255.255.255.255 20.20.20.2 name TB2-NGINX1
      ip route 172.24.0.202 255.255.255.255 20.20.20.2 name TB2-NGINX2
      ip route 172.24.0.222 255.255.255.255 20.20.20.2 name TB2-DOCKER-CUBETEST-CUBE01
      ip route 172.24.0.223 255.255.255.255 20.20.20.2 name TB2-DOCKER-CUBETEST-CUBE02
      ip route 172.24.0.224 255.255.255.255 20.20.20.2 name TB2-CUBETEST-CUBE03
      ip route 172.24.0.225 255.255.255.255 20.20.20.2 name TB2-CUBETEST-CUBE04
      ip route 172.24.0.229 255.255.255.255 20.20.20.2 name TB2-ELK
      ip route 172.24.0.238 255.255.255.255 20.20.20.2 name TB2-DOCKER-TEST-MANAGER01
      ip route 172.24.0.239 255.255.255.255 20.20.20.2 name TB2-DOCKER-TEST-MANAGER02
      ip route 172.24.0.245 255.255.255.255 20.20.20.2 name TB2-DOCKER
      ip route 172.24.3.250 255.255.255.255 20.20.20.2 name TB2-VIRT-WORKSTATION
      ip route 172.24.254.250 255.255.255.255 20.20.20.2 name TB2-CONTENT
      ip route 180.180.180.143 255.255.255.255 40.40.40.2 name DBMS-LVS
      ip route 180.180.180.205 255.255.255.255 40.40.40.2 name DBMS-KEEPALIVED-MASTER
      ip route 180.180.180.208 255.255.255.255 40.40.40.2 name DBMS-KEEPALIVED-BACKUP
      ip route 180.180.180.209 255.255.255.255 40.40.40.2 name DBMS-KEEPALIVED-VIP
      ip route 180.180.180.226 255.255.255.255 40.40.40.2 name DBMS-MASTER-A
      ip route 180.180.180.228 255.255.255.255 40.40.40.2 name MHA-TEST-MASTER-ACTIVE
      ip route 180.180.180.229 255.255.255.255 40.40.40.2 name MHA-TEST-MASTER-BACKUP
      ip route 180.180.180.230 255.255.255.255 40.40.40.2 name MHA-TEST-SLAVE01
      ip route 180.180.180.231 255.255.255.255 40.40.40.2 name DBMS-MASTER-B
      ip route 180.180.180.235 255.255.255.255 40.40.40.2 name DBMS-LVS-MASTER
      ip route 180.180.180.236 255.255.255.255 40.40.40.2 name DBMS-LVS-SLAVE
      ip route 180.180.180.237 255.255.255.255 40.40.40.2 name DBMS-SLAVE03
      ip route 180.180.180.238 255.255.255.255 40.40.40.2 name DBMS-MHA
      ip route 180.180.180.239 255.255.255.255 40.40.40.2 name DBMS-MASTER
      ip route 180.180.180.240 255.255.255.255 40.40.40.2 name MHA-TEST-VIP
      ip route 180.180.180.242 255.255.255.255 40.40.40.2 name DBMS-SLAVE01
      ip route 180.180.180.243 255.255.255.255 40.40.40.2 name DBMS-SLAVE02
      ip route 180.180.180.250 255.255.255.255 40.40.40.2 name DBMS-WRITE
      ip route 180.180.180.251 255.255.255.255 40.40.40.2 name DBMS-READ
      ip route 180.180.180.254 255.255.255.255 40.40.40.2 name DBMS-L2-SWITCH
      ip route 192.168.200.62 255.255.255.255 10.10.10.2 name HONGSNET
      ip route 192.168.200.148 255.255.255.255 10.10.10.2 name USERS-PROXY
      ip route 192.168.200.211 255.255.255.255 10.10.10.2 name USERS-PROXY-SLAVE
      ip route 192.168.200.216 255.255.255.255 10.10.10.2 name USERS-PROXY-VIP
      ip route 192.168.200.217 255.255.255.255 10.10.10.2 name HONGSNET-STAG
      ip route 192.168.200.233 255.255.255.255 10.10.10.2 name HAPROXY-MASTER
      ip route 192.168.200.234 255.255.255.255 10.10.10.2 name HAPROXY-SLAVE
      ip route 192.168.200.242 255.255.255.255 10.10.10.2 name ADMIN-PROXY-MASTER
      ip route 192.168.200.243 255.255.255.255 10.10.10.2 name ADMIN-PROXY-SLAVE
      ip route 192.168.200.244 255.255.255.255 10.10.10.2 name HAPROXY-VIP
      ip route 192.168.200.249 255.255.255.255 10.10.10.2 name UTILS-POSTFIX
      ```
      다음은 **라우팅테이블**의 내역이다.
      ```plaintext
      #sh ip route
      Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
      D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
      N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
      E1 - OSPF external type 1, E2 - OSPF external type 2
      i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
      ia - IS-IS inter area, * - candidate default, U - per-user static route
      o - ODR, P - periodic downloaded static route
      Gateway of last resort is not set
      100.0.0.0/32 is subnetted, 3 subnets
      S 100.100.100.4 [1/0] via 10.10.10.2
      S 100.100.100.1 [1/0] via 10.10.10.2
      S 100.100.100.2 [1/0] via 10.10.10.2
      20.0.0.0/30 is subnetted, 1 subnets
      C 20.20.20.0 is directly connected, GigabitEthernet1/0/2
      172.16.0.0/32 is subnetted, 11 subnets
      S 172.16.0.170 [1/0] via 30.30.30.2
      S 172.16.0.158 [1/0] via 30.30.30.2
      S 172.16.0.251 [1/0] via 30.30.30.2
      S 172.16.0.236 [1/0] via 30.30.30.2
      S 172.16.0.235 [1/0] via 30.30.30.2
      S 172.16.0.228 [1/0] via 30.30.30.2
      S 172.16.0.230 [1/0] via 30.30.30.2
      S 172.16.0.226 [1/0] via 30.30.30.2
      S 172.16.0.227 [1/0] via 30.30.30.2
      S 172.16.0.221 [1/0] via 30.30.30.2
      S 172.16.254.254 [1/0] via 30.30.30.2
      172.24.0.0/32 is subnetted, 14 subnets
      S 172.24.0.151 [1/0] via 20.20.20.2
      S 172.24.0.145 [1/0] via 20.20.20.2
      S 172.24.0.245 [1/0] via 20.20.20.2
      S 172.24.3.250 [1/0] via 20.20.20.2
      S 172.24.0.229 [1/0] via 20.20.20.2
      S 172.24.0.224 [1/0] via 20.20.20.2
      S 172.24.0.225 [1/0] via 20.20.20.2
      S 172.24.0.238 [1/0] via 20.20.20.2
      S 172.24.0.239 [1/0] via 20.20.20.2
      S 172.24.0.222 [1/0] via 20.20.20.2
      S 172.24.0.223 [1/0] via 20.20.20.2
      S 172.24.0.199 [1/0] via 20.20.20.2
      S 172.24.0.202 [1/0] via 20.20.20.2
      S 172.24.254.250 [1/0] via 20.20.20.2
      192.168.200.0/32 is subnetted, 11 subnets
      S 192.168.200.148 [1/0] via 10.10.10.2
      S 192.168.200.233 [1/0] via 10.10.10.2
      S 192.168.200.234 [1/0] via 10.10.10.2
      S 192.168.200.242 [1/0] via 10.10.10.2
      S 192.168.200.243 [1/0] via 10.10.10.2
      S 192.168.200.244 [1/0] via 10.10.10.2
      S 192.168.200.249 [1/0] via 10.10.10.2
      S 192.168.200.211 [1/0] via 10.10.10.2
      S 192.168.200.216 [1/0] via 10.10.10.2
      S 192.168.200.217 [1/0] via 10.10.10.2
      S 192.168.200.62 [1/0] via 10.10.10.2
      40.0.0.0/30 is subnetted, 1 subnets
      C 40.40.40.0 is directly connected, GigabitEthernet1/0/4
      10.0.0.0/30 is subnetted, 1 subnets
      C 10.10.10.0 is directly connected, GigabitEthernet1/0/1
      30.0.0.0/30 is subnetted, 1 subnets
      C 30.30.30.0 is directly connected, GigabitEthernet1/0/3
      180.180.0.0/32 is subnetted, 20 subnets
      S 180.180.180.143 [1/0] via 40.40.40.2
      S 180.180.180.240 [1/0] via 40.40.40.2
      S 180.180.180.242 [1/0] via 40.40.40.2
      S 180.180.180.243 [1/0] via 40.40.40.2
      S 180.180.180.254 [1/0] via 40.40.40.2
      S 180.180.180.250 [1/0] via 40.40.40.2
      S 180.180.180.251 [1/0] via 40.40.40.2
      S 180.180.180.228 [1/0] via 40.40.40.2
      S 180.180.180.229 [1/0] via 40.40.40.2
      S 180.180.180.230 [1/0] via 40.40.40.2
      S 180.180.180.231 [1/0] via 40.40.40.2
      S 180.180.180.226 [1/0] via 40.40.40.2
      S 180.180.180.236 [1/0] via 40.40.40.2
      S 180.180.180.237 [1/0] via 40.40.40.2
      S 180.180.180.238 [1/0] via 40.40.40.2
      S 180.180.180.239 [1/0] via 40.40.40.2
      S 180.180.180.235 [1/0] via 40.40.40.2
      S 180.180.180.208 [1/0] via 40.40.40.2
      S 180.180.180.209 [1/0] via 40.40.40.2
      S 180.180.180.205 [1/0] via 40.40.40.2
      ```
      - **DBMS Routing**(180.180.180.0/24) 설정내역
      ```plaintext
      interface GigabitEthernet1/0/1
      description TO-IX-SWITCH-Gi0/44
      no switchport
      ip address 40.40.40.2 255.255.255.252
      !
      interface GigabitEthernet1/0/2
      description TO-DATABASE-L2-Gi1/0/24
      switchport access vlan 180
      switchport mode access
      !
      ...중략
      ip classless
      ip route 100.100.100.1 255.255.255.255 40.40.40.1 name HONGSNET-IPMI
      ip route 100.100.100.2 255.255.255.255 40.40.40.1 name TB2-ADMIN-IPMI
      ip route 100.100.100.4 255.255.255.255 40.40.40.1 name TB3-IPMI
      ip route 172.16.0.158 255.255.255.255 40.40.40.1 name TB3-WEBSERVER
      ip route 172.16.0.170 255.255.255.255 40.40.40.1 name HOSTING170
      ip route 172.16.0.228 255.255.255.255 40.40.40.1 name TB3-ELK-DEMO-MASTER
      ip route 172.16.0.251 255.255.255.255 40.40.40.1 name TB3-DOCKER
      ip route 172.16.254.254 255.255.255.255 40.40.40.1 name TB3-CLASSROOM
      ip route 172.24.0.145 255.255.255.255 40.40.40.1 name TB2-REDMINE
      ip route 172.24.0.151 255.255.255.255 40.40.40.1 name TB2-WEBSERVER
      ip route 172.24.0.199 255.255.255.255 40.40.40.1 name TB2-NGINX1
      ip route 172.24.0.202 255.255.255.255 40.40.40.1 name TB2-NGINX2
      ip route 172.24.0.238 255.255.255.255 40.40.40.1 name TB2-DOCKER-TEST-MANAGER01
      ip route 172.24.0.240 255.255.255.255 40.40.40.1 name TB2-MATTERMOST
      ip route 172.24.0.245 255.255.255.255 40.40.40.1 name TB2-DOCKER
      ip route 172.24.254.250 255.255.255.255 40.40.40.1 name TB2-CONTENT
      ip route 192.168.200.62 255.255.255.255 40.40.40.1 name HONGSNET
      ip route 192.168.200.217 255.255.255.255 40.40.40.1 name HONGSNET-STAG
      ip route 192.168.200.242 255.255.255.255 40.40.40.1 name ADMIN-PROXY-MASTER
      ip route 192.168.200.243 255.255.255.255 40.40.40.1 name ADMIN-PROXY-SLAVE
      ip route 192.168.200.249 255.255.255.255 40.40.40.1 name HONGSNET-MAIL
      ```
      다음은 **라우팅테이블**의 내역이다.
      ```plaintext
      #sh ip route
      Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
      D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
      N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
      E1 - OSPF external type 1, E2 - OSPF external type 2
      i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
      ia - IS-IS inter area, * - candidate default, U - per-user static route
      o - ODR, P - periodic downloaded static route
      Gateway of last resort is not set
      100.0.0.0/32 is subnetted, 3 subnets
      S 100.100.100.4 [1/0] via 40.40.40.1
      S 100.100.100.1 [1/0] via 40.40.40.1
      S 100.100.100.2 [1/0] via 40.40.40.1
      172.16.0.0/32 is subnetted, 5 subnets
      S 172.16.0.170 [1/0] via 40.40.40.1
      S 172.16.0.158 [1/0] via 40.40.40.1
      S 172.16.0.251 [1/0] via 40.40.40.1
      S 172.16.0.228 [1/0] via 40.40.40.1
      S 172.16.254.254 [1/0] via 40.40.40.1
      172.24.0.0/32 is subnetted, 8 subnets
      S 172.24.0.151 [1/0] via 40.40.40.1
      S 172.24.0.145 [1/0] via 40.40.40.1
      S 172.24.0.245 [1/0] via 40.40.40.1
      S 172.24.0.240 [1/0] via 40.40.40.1
      S 172.24.0.238 [1/0] via 40.40.40.1
      S 172.24.0.199 [1/0] via 40.40.40.1
      S 172.24.0.202 [1/0] via 40.40.40.1
      S 172.24.254.250 [1/0] via 40.40.40.1
      192.168.200.0/32 is subnetted, 5 subnets
      S 192.168.200.242 [1/0] via 40.40.40.1
      S 192.168.200.243 [1/0] via 40.40.40.1
      S 192.168.200.249 [1/0] via 40.40.40.1
      S 192.168.200.217 [1/0] via 40.40.40.1
      S 192.168.200.62 [1/0] via 40.40.40.1
      40.0.0.0/30 is subnetted, 1 subnets
      C 40.40.40.0 is directly connected, GigabitEthernet1/0/1
      180.180.0.0/24 is subnetted, 1 subnets
      C 180.180.180.0 is directly connected, Vlan180
      ```
      Markdown is supported
      0% or
      You are about to add 0 people to the discussion. Proceed with caution.
      Finish editing this message first!
      Please register or to comment