Cisco CSR1000v（IOS XE）でOTV検証 2/3

OTV（Overlay Transport Virtualization）Cisco,仮想化

はじめに

前回第一回目の検証では、『2サイトのシングル構成』によるOTV検証を実施しました。今回は2サイトのマルチホーミング冗長構成で検証します。また、負荷分散の確認と、障害試験を行い切り替わ時間についても計測してみます。

第二回目の検証

検証概要

OTV検証 にあたって使用する機器と構成は下記のとおりです。

用途ホスト名機種OS Version
エッジデバイスCSR1000ｖ-01/02/04/05CSR1000v03.16.06.S
–VyOS-01/02VyOS1.3-rolling-202006120643
クライアントN9Kv-V9-01/02Nexus 9000v9.2(3)

■要件は下記の通りとします。

  • サイト数はSiteAとSiteBの2サイトとする。
  • CSR1000v-01/04とCSR1000v-02/05間でOTVトンネルを構成する。
  • 各サイトではVlan100とVlan101のセグメントを用意する。
  • アンダーレイネットワークのVlan11/14とVlan12/15間はVyOS-01でOSPFルーティングをする。

なお、第一回目の記事でも説明しましたが、CSR1000vのインタフェースのMTUサイズはデフォルト値から変更してます。※参考：『Cisco Nexus 7000 シリーズ NX-OS OTV 設定ガイド』の「OTV の注意事項と制約事項」参照。

設定内容

OTVを構成するエッジデバイスのコンフィグ

OTVに関連する設定箇所と、アンダーレイネットワークのrouter ospfを記載します。

CSR1000v-01#show running-config
＜省略＞
!
hostname CSR1000v-01
!
＜省略＞
!
otv site bridge-domain 100
 otv isis hello-interval 3
!
otv site-identifier 0000.0000.0001
＜省略＞
!
interface Overlay1
 description Overlay Network
 no ip address
 otv join-interface GigabitEthernet2.11
 otv vpn-name Site-A
 otv adjacency-server unicast-only
 otv isis hello-interval 3
 service instance 100 ethernet
  encapsulation dot1q 100
  bridge-domain 100
 !
 service instance 101 ethernet
  encapsulation dot1q 101
  bridge-domain 101
 !
!
＜省略＞
!
interface GigabitEthernet2
 mtu 9000
 no ip address
 no ip redirects
 negotiation auto
!
interface GigabitEthernet2.11
 description OTV Layer 3 to Distribution
 encapsulation dot1Q 11
 ip address 192.168.11.1 255.255.255.0
 no ip redirects
 no ip proxy-arp
 ip ospf network point-to-point
 ip ospf hello-interval 1
!
interface GigabitEthernet3
 mtu 9216
 no ip address
 negotiation auto
 service instance 100 ethernet
  encapsulation dot1q 100
  bridge-domain 100
 !
 service instance 101 ethernet
  encapsulation dot1q 101
  bridge-domain 101
 !
!
＜省略＞
!
router ospf 1
 router-id 192.168.11.1
 timers throttle spf 5 1000 1000
 network 192.168.11.0 0.0.0.255 area 0
!
＜省略＞
CSR1000v-01#
CSR1000v-04#show running-config
＜省略＞
!
hostname CSR1000v-04
!
＜省略＞
!
otv site bridge-domain 100
 otv isis hello-interval 3
!
otv site-identifier 0000.0000.0001
＜省略＞
!
interface Overlay1
 description Overlay Network
 no ip address
 otv join-interface GigabitEthernet2.14
 otv vpn-name Site-A
 otv use-adjacency-server 192.168.11.1 192.168.12.1 unicast-only
 otv isis hello-interval 3
 service instance 100 ethernet
  encapsulation dot1q 100
  bridge-domain 100
 !
 service instance 101 ethernet
  encapsulation dot1q 101
  bridge-domain 101
 !
!
＜省略＞
!
interface GigabitEthernet2
 mtu 9000
 no ip address
 no ip redirects
 negotiation auto
!
interface GigabitEthernet2.14
 description OTV Layer 3 to Distribution
 encapsulation dot1Q 14
 ip address 192.168.14.1 255.255.255.0
 no ip redirects
 no ip proxy-arp
 ip ospf network point-to-point
 ip ospf hello-interval 1
!
interface GigabitEthernet3
 mtu 9216
 no ip address
 negotiation auto
 service instance 100 ethernet
  encapsulation dot1q 100
  bridge-domain 100
 !
 service instance 101 ethernet
  encapsulation dot1q 101
  bridge-domain 101
 !
!
＜省略＞
!
router ospf 1
 router-id 192.168.14.1
 timers throttle spf 5 1000 1000
 network 192.168.14.0 0.0.0.255 area 0
!
＜省略＞
CSR1000v-04#
CSR1000v-02#show running-config
＜省略＞
!
hostname CSR1000v-02
!
＜省略＞
!
otv site bridge-domain 100
 otv isis hello-interval 3
!
otv site-identifier 0000.0000.0002
＜省略＞
!
interface Overlay1
 description Overlay Network
 no ip address
 otv join-interface GigabitEthernet2.12
 otv vpn-name Site-B
 otv use-adjacency-server 192.168.11.1 unicast-only
 otv adjacency-server unicast-only
 otv isis hello-interval 3
 service instance 100 ethernet
  encapsulation dot1q 100
  bridge-domain 100
 !
 service instance 101 ethernet
  encapsulation dot1q 101
  bridge-domain 101
 !
!
＜省略＞
!
interface GigabitEthernet2
 mtu 9000
 no ip address
 no ip redirects
 negotiation auto
!
interface GigabitEthernet2.12
 description OTV Layer 3 to Distribution
 encapsulation dot1Q 12
 ip address 192.168.12.1 255.255.255.0
 no ip redirects
 no ip proxy-arp
 ip ospf network point-to-point
 ip ospf hello-interval 1
!
interface GigabitEthernet3
 mtu 9216
 no ip address
 negotiation auto
 service instance 100 ethernet
  encapsulation dot1q 100
  bridge-domain 100
 !
 service instance 101 ethernet
  encapsulation dot1q 101
  bridge-domain 101
 !
!
＜省略＞
!
router ospf 1
 router-id 192.168.12.1
 timers throttle spf 5 1000 1000
 network 192.168.12.0 0.0.0.255 area 0
!
＜省略＞
CSR1000v-02#
CSR1000v-05#show running-config
＜省略＞
!
hostname CSR1000v-05
!
＜省略＞
!
otv site bridge-domain 100
 otv isis hello-interval 3
!
otv site-identifier 0000.0000.0002
＜省略＞
!
interface Overlay1
 description Overlay Network
 no ip address
 otv join-interface GigabitEthernet2.15
 otv vpn-name Site-B
 otv use-adjacency-server 192.168.11.1 192.168.12.1 unicast-only
 otv isis hello-interval 3
 service instance 100 ethernet
  encapsulation dot1q 100
  bridge-domain 100
 !
 service instance 101 ethernet
  encapsulation dot1q 101
  bridge-domain 101
 !
!
＜省略＞
!
interface GigabitEthernet2
 mtu 9000
 no ip address
 no ip redirects
 negotiation auto
!
interface GigabitEthernet2.15
 description OTV Layer 3 to Distribution
 encapsulation dot1Q 15
 ip address 192.168.15.1 255.255.255.0
 no ip redirects
 no ip proxy-arp
 ip ospf network point-to-point
 ip ospf hello-interval 1
!
interface GigabitEthernet3
 mtu 9216
 no ip address
 negotiation auto
 service instance 100 ethernet
  encapsulation dot1q 100
  bridge-domain 100
 !
 service instance 101 ethernet
  encapsulation dot1q 101
  bridge-domain 101
 !
!
＜省略＞
!
router ospf 1
 router-id 192.168.15.1
 timers throttle spf 5 1000 1000
 network 192.168.15.0 0.0.0.255 area 0
!
＜省略＞
CSR1000v-05#

アンダーレイのVyOSのコンフィグ

次にVyOSです。

vyos@VyOS-01# show
 interfaces {
＜省略＞
     ethernet eth1 {
         hw-id 00:0c:29:9c:fb:3f
         vif 99 {
             address 192.168.99.1/24
             ip {
                 ospf {
                     dead-interval 40
                     hello-interval 10
                     network point-to-point
                     priority 1
                     retransmit-interval 5
                     transmit-delay 1
                 }
             }
         }
     }
     ethernet eth2 {
         hw-id 00:0c:29:9c:fb:49
         mtu 9000
         vif 11 {
             address 192.168.11.254/24
             ip {
                 ospf {
                     dead-interval 4
                     hello-interval 1
                     network point-to-point
                     priority 1
                     retransmit-interval 5
                     transmit-delay 1
                 }
             }
             mtu 9000
         }
         vif 12 {
             address 192.168.12.254/24
             ip {
                 ospf {
                     dead-interval 4
                     hello-interval 1
                     network point-to-point
                     priority 1
                     retransmit-interval 5
                     transmit-delay 1
                 }
             }
             mtu 9000
         }
     }
＜省略＞
 }
 protocols {
     ospf {
         area 0 {
             network 192.168.11.0/24
             network 192.168.12.0/24
             network 192.168.99.0/24
         }
     }
＜省略＞
vyos@VyOS-01#
vyos@VyOS-02# show
 interfaces {
＜省略＞
     ethernet eth1 {
         hw-id 00:0c:29:96:75:4d
         vif 99 {
             address 192.168.99.2/24
             ip {
                 ospf {
                     dead-interval 40
                     hello-interval 10
                     network point-to-point
                     priority 1
                     retransmit-interval 5
                     transmit-delay 1
                 }
             }
         }
     }
     ethernet eth2 {
         hw-id 00:0c:29:96:75:57
         mtu 9000
         vif 14 {
             address 192.168.14.254/24
             ip {
                 ospf {
                     dead-interval 4
                     hello-interval 1
                     network point-to-point
                     priority 1
                     retransmit-interval 5
                     transmit-delay 1
                 }
             }
             mtu 9000
         }
         vif 15 {
             address 192.168.15.254/24
             ip {
                 ospf {
                     dead-interval 4
                     hello-interval 1
                     network point-to-point
                     priority 1
                     retransmit-interval 5
                     transmit-delay 1
                 }
             }
             mtu 9000
         }
     }
＜省略＞
 }
 protocols {
     ospf {
         area 0 {
             network 192.168.14.0/24
             network 192.168.15.0/24
             network 192.168.99.0/24
         }
     }
＜省略＞
vyos@VyOS-02#

クライアントのN9Kvのコンフィグ

次にクライアントとして機能するN9Kvのコンフィグです。

N9Kv-V9-01# show running-config
＜省略＞
vlan 1,100-101
＜省略＞
interface Vlan1

interface Vlan100
  no shutdown
  no ip redirects
  ip address 192.168.100.1/24

interface Vlan101
  no shutdown
  no ip redirects
  ip address 192.168.101.1/24

interface Ethernet1/1
  switchport mode trunk
  switchport trunk allowed vlan 100-101
＜省略＞
N9Kv-V9-01#
N9Kv-V9-02# show running-config
＜省略＞
vlan 1,100-101
＜省略＞
interface Vlan1

interface Vlan100
  no shutdown
  no ip redirects
  ip address 192.168.100.2/24

interface Vlan101
  no shutdown
  no ip redirects
  ip address 192.168.101.2/24

interface Ethernet1/1
  switchport mode trunk
  switchport trunk allowed vlan 100-101
＜省略＞
N9Kv-V9-02#

設定は以上です。

ステータス確認

アンダーレイネットワークのルーティング情報

まずはアンダーレイネットワークが正常に組めていることを確認します。（主にOSPFルーティング）

CSR1000v-01#show ip route
＜省略＞
      192.168.11.0/24 is variably subnetted, 2 subnets, 2 masks
C        192.168.11.0/24 is directly connected, GigabitEthernet2.11
L        192.168.11.1/32 is directly connected, GigabitEthernet2.11
O     192.168.12.0/24
           [110/11] via 192.168.11.254, 01:27:51, GigabitEthernet2.11
O     192.168.14.0/24
           [110/21] via 192.168.11.254, 00:01:52, GigabitEthernet2.11
O     192.168.15.0/24
           [110/21] via 192.168.11.254, 00:01:52, GigabitEthernet2.11
O     192.168.99.0/24
           [110/11] via 192.168.11.254, 01:27:51, GigabitEthernet2.11
CSR1000v-01#
CSR1000v-04#show ip route
＜省略＞
O     192.168.11.0/24
           [110/21] via 192.168.14.254, 00:01:52, GigabitEthernet2.14
O     192.168.12.0/24
           [110/21] via 192.168.14.254, 00:01:52, GigabitEthernet2.14
      192.168.14.0/24 is variably subnetted, 2 subnets, 2 masks
C        192.168.14.0/24 is directly connected, GigabitEthernet2.14
L        192.168.14.1/32 is directly connected, GigabitEthernet2.14
O     192.168.15.0/24
           [110/11] via 192.168.14.254, 01:27:37, GigabitEthernet2.14
O     192.168.99.0/24
           [110/11] via 192.168.14.254, 01:27:37, GigabitEthernet2.14
CSR1000v-04#
CSR1000v-02#show ip route
＜省略＞
O     192.168.11.0/24
           [110/11] via 192.168.12.254, 01:27:52, GigabitEthernet2.12
      192.168.12.0/24 is variably subnetted, 2 subnets, 2 masks
C        192.168.12.0/24 is directly connected, GigabitEthernet2.12
L        192.168.12.1/32 is directly connected, GigabitEthernet2.12
O     192.168.14.0/24
           [110/21] via 192.168.12.254, 00:01:53, GigabitEthernet2.12
O     192.168.15.0/24
           [110/21] via 192.168.12.254, 00:01:53, GigabitEthernet2.12
O     192.168.99.0/24
           [110/11] via 192.168.12.254, 01:27:52, GigabitEthernet2.12
CSR1000v-02#
CSR1000v-05#show ip route
＜省略＞
O     192.168.11.0/24
           [110/21] via 192.168.15.254, 00:01:53, GigabitEthernet2.15
O     192.168.12.0/24
           [110/21] via 192.168.15.254, 00:01:53, GigabitEthernet2.15
O     192.168.14.0/24
           [110/11] via 192.168.15.254, 01:27:37, GigabitEthernet2.15
      192.168.15.0/24 is variably subnetted, 2 subnets, 2 masks
C        192.168.15.0/24 is directly connected, GigabitEthernet2.15
L        192.168.15.1/32 is directly connected, GigabitEthernet2.15
O     192.168.99.0/24
           [110/11] via 192.168.15.254, 01:27:37, GigabitEthernet2.15
CSR1000v-05#
vyos@VyOS-01:~$ show ip route
＜省略＞
O   192.168.11.0/24 [110/10] is directly connected, eth2.11, 01:29:31
C>* 192.168.11.0/24 is directly connected, eth2.11, 01:29:36
O   192.168.12.0/24 [110/10] is directly connected, eth2.12, 01:29:31
C>* 192.168.12.0/24 is directly connected, eth2.12, 01:29:36
O>* 192.168.14.0/24 [110/20] via 192.168.99.2, eth1.99, 00:03:27
O>* 192.168.15.0/24 [110/20] via 192.168.99.2, eth1.99, 00:03:27
O   192.168.99.0/24 [110/10] is directly connected, eth1.99, 00:03:41
C>* 192.168.99.0/24 is directly connected, eth1.99, 01:29:36
vyos@VyOS-01:~$
vyos@VyOS-02:~$ show ip route
＜省略＞
O>* 192.168.11.0/24 [110/20] via 192.168.99.1, eth1.99, 00:03:22
O>* 192.168.12.0/24 [110/20] via 192.168.99.1, eth1.99, 00:03:22
O   192.168.14.0/24 [110/10] is directly connected, eth2.14, 01:29:12
C>* 192.168.14.0/24 is directly connected, eth2.14, 01:29:16
O   192.168.15.0/24 [110/10] is directly connected, eth2.15, 01:29:12
C>* 192.168.15.0/24 is directly connected, eth2.15, 01:29:16
O   192.168.99.0/24 [110/10] is directly connected, eth1.99, 00:03:42
C>* 192.168.99.0/24 is directly connected, eth1.99, 01:29:17
vyos@VyOS-02:~$

OTVのステータス確認

次にオーバーレイネットワークが正常に組めていることを確認します。

『show otv』は自身のOTV状態を示します。
『show otv site』は自サイトのエッジデバイスを表示します。今回の検証はマルチホーミング構成で各サイトにエッジデバイスが2台あります。なので2台表示されます。
『show otv adjacency』は同じOTVで結ばれている全エッジデバイスが表示されます。今回は2サイトのエッジデバイス4台になるので、自エッジデバイスを除く3台表示されます。
『show otv vlan』はエッジデバイスの内部インタフェースで定義しているVlanが表示されます。内部インタフェースとは、Gi3で定義したVlan100と101のLAN側インタフェースのことです。
『show otv route』はOTVのルーティングテーブルです。L2なので宛先のMACアドレスを持つノードは、どのエッジデバイスの先にいるか、が分かるテーブルです。

CSR1000v-01#show otv
Overlay Interface Overlay1
 VPN name                 : Site-A
 VPN ID                   : 1
 State                    : UP
 Fwd-capable              : Yes
 Fwd-ready                : Yes
 AED-Server               : Yes
 Backup AED-Server        : No
 AED Capable              : Yes
 Join interface(s)        : GigabitEthernet2.11
 Join IPv4 address        : 192.168.11.1
 Tunnel interface(s)      : Tunnel0
 Encapsulation format     : GRE/IPv4
 Site Bridge-Domain       : 100
 Capability               : Unicast-only
 Is Adjacency Server      : Yes
 Adj Server Configured    : No
 Prim/Sec Adj Svr(s)      : None

CSR1000v-01#
CSR1000v-01#
CSR1000v-01#
CSR1000v-01#show otv site
Site Adjacency Information (Site Bridge-Domain: 100)

Overlay1 Site-Local Adjacencies (Count: 2)

  Hostname       System ID      Last Change Ordinal    AED Enabled Status
* CSR1000v-01    001E.E62F.5D00 01:29:53    0          site       overlay
  CSR1000v-04    001E.E6AD.8500 01:28:27    1          site       overlay


CSR1000v-01#
CSR1000v-01#
CSR1000v-01#
CSR1000v-01#show otv adjacency
Overlay Adjacency Database for overlay 1
Hostname                       System-ID      Dest Addr       Site-ID        Up Time   State
CSR1000v-04                    001e.e6ad.8500 192.168.14.1    0000.0000.0001 00:03:59  UP
CSR1000v-05                    001e.e529.5f00 192.168.15.1    0000.0000.0002 00:04:00  UP
CSR1000v-02                    001e.bd50.2a00 192.168.12.1    0000.0000.0002 01:29:57  UP

CSR1000v-01#
CSR1000v-01#
CSR1000v-01#
CSR1000v-01#show otv vlan
Key:  SI - Service Instance, NA - Non AED, NFC - Not Forward Capable.

Overlay 1 VLAN Configuration Information
 Inst VLAN BD   Auth ED              State                Site If(s)       
 0    100  100  *CSR1000v-01         active              Gi3:SI100
 0    101  101   CSR1000v-04         inactive(NA)        Gi3:SI101
 Total VLAN(s): 2

CSR1000v-01#
CSR1000v-01#
CSR1000v-01#
CSR1000v-01#show otv route

Codes: BD - Bridge-Domain, AD - Admin-Distance,
       SI - Service Instance, * - Backup Route

OTV Unicast MAC Routing Table for Overlay1

 Inst VLAN BD     MAC Address    AD    Owner  Next Hops(s)
----------------------------------------------------------
 0    100  100    000c.2916.2320 50    ISIS   CSR1000v-02
 0    100  100    000c.29d4.1d6d 40    BD Eng Gi3:SI100
 0    100  100    001e.e529.5fbc 50    ISIS   CSR1000v-02
 0    100  100    001e.e6ad.85bc 40    BD Eng Gi3:SI100
 0    101  101    000c.2916.2320 50    ISIS   CSR1000v-05
 0    101  101    001e.bd50.2abc 50    ISIS   CSR1000v-05

6 unicast routes displayed in Overlay1

----------------------------------------------------------
6 Total Unicast Routes Displayed

CSR1000v-01#
CSR1000v-04#show otv
Overlay Interface Overlay1
 VPN name                 : Site-A
 VPN ID                   : 1
 State                    : UP
 Fwd-capable              : Yes
 Fwd-ready                : Yes
 AED-Server               : No
 Backup AED-Server        : Yes
 AED Capable              : Yes
 Join interface(s)        : GigabitEthernet2.14
 Join IPv4 address        : 192.168.14.1
 Tunnel interface(s)      : Tunnel0
 Encapsulation format     : GRE/IPv4
 Site Bridge-Domain       : 100
 Capability               : Unicast-only
 Is Adjacency Server      : No
 Adj Server Configured    : Yes
 Prim/Sec Adj Svr(s)      : 192.168.11.1/192.168.12.1

CSR1000v-04#
CSR1000v-04#
CSR1000v-04#
CSR1000v-04#show otv site
Site Adjacency Information (Site Bridge-Domain: 100)

Overlay1 Site-Local Adjacencies (Count: 2)

  Hostname       System ID      Last Change Ordinal    AED Enabled Status
  CSR1000v-01    001E.E62F.5D00 01:28:42    0          site       overlay
* CSR1000v-04    001E.E6AD.8500 01:29:27    1          site       overlay


CSR1000v-04#
CSR1000v-04#
CSR1000v-04#
CSR1000v-04#show otv adjacency
Overlay Adjacency Database for overlay 1
Hostname                       System-ID      Dest Addr       Site-ID        Up Time   State
CSR1000v-01                    001e.e62f.5d00 192.168.11.1    0000.0000.0001 00:03:59  UP
CSR1000v-05                    001e.e529.5f00 192.168.15.1    0000.0000.0002 01:29:30  UP
CSR1000v-02                    001e.bd50.2a00 192.168.12.1    0000.0000.0002 00:03:59  UP

CSR1000v-04#
CSR1000v-04#
CSR1000v-04#
CSR1000v-04#show otv vlan
Key:  SI - Service Instance, NA - Non AED, NFC - Not Forward Capable.

Overlay 1 VLAN Configuration Information
 Inst VLAN BD   Auth ED              State                Site If(s)
 0    100  100   CSR1000v-01         inactive(NA)        Gi3:SI100
 0    101  101  *CSR1000v-04         active              Gi3:SI101
 Total VLAN(s): 2

CSR1000v-04#
CSR1000v-04#
CSR1000v-04#
CSR1000v-04#show otv route

Codes: BD - Bridge-Domain, AD - Admin-Distance,
       SI - Service Instance, * - Backup Route

OTV Unicast MAC Routing Table for Overlay1

 Inst VLAN BD     MAC Address    AD    Owner  Next Hops(s)
----------------------------------------------------------
 0    100  100    000c.2916.2320 50    ISIS   CSR1000v-02
 0    100  100    001e.e529.5fbc 50    ISIS   CSR1000v-02
 0    101  101    000c.2916.2320 50    ISIS   CSR1000v-05
 0    101  101    000c.29d4.1d6d 40    BD Eng Gi3:SI101
 0    101  101    001e.bd50.2abc 50    ISIS   CSR1000v-05
 0    101  101    001e.e62f.5dbc 40    BD Eng Gi3:SI101

6 unicast routes displayed in Overlay1

----------------------------------------------------------
6 Total Unicast Routes Displayed

CSR1000v-04#
CSR1000v-02#show otv
Overlay Interface Overlay1
 VPN name                 : Site-B
 VPN ID                   : 1
 State                    : UP
 Fwd-capable              : Yes
 Fwd-ready                : Yes
 AED-Server               : Yes
 Backup AED-Server        : No
 AED Capable              : Yes
 Join interface(s)        : GigabitEthernet2.12
 Join IPv4 address        : 192.168.12.1
 Tunnel interface(s)      : Tunnel0
 Encapsulation format     : GRE/IPv4
 Site Bridge-Domain       : 100
 Capability               : Unicast-only
 Is Adjacency Server      : Yes
 Adj Server Configured    : Yes
 Prim/Sec Adj Svr(s)      : 192.168.11.1

CSR1000v-02#
CSR1000v-02#
CSR1000v-02#
CSR1000v-02#show otv site
Site Adjacency Information (Site Bridge-Domain: 100)

Overlay1 Site-Local Adjacencies (Count: 2)

  Hostname       System ID      Last Change Ordinal    AED Enabled Status
* CSR1000v-02    001E.BD50.2A00 01:29:53    0          site       overlay
  CSR1000v-05    001E.E529.5F00 01:28:28    1          site       overlay


CSR1000v-02#
CSR1000v-02#
CSR1000v-02#
CSR1000v-02#show otv adjacency
Overlay Adjacency Database for overlay 1
Hostname                       System-ID      Dest Addr       Site-ID        Up Time   State
CSR1000v-04                    001e.e6ad.8500 192.168.14.1    0000.0000.0001 00:03:59  UP
CSR1000v-01                    001e.e62f.5d00 192.168.11.1    0000.0000.0001 01:29:57  UP
CSR1000v-05                    001e.e529.5f00 192.168.15.1    0000.0000.0002 00:04:00  UP

CSR1000v-02#
CSR1000v-02#
CSR1000v-02#
CSR1000v-02#show otv vlan
Key:  SI - Service Instance, NA - Non AED, NFC - Not Forward Capable.

Overlay 1 VLAN Configuration Information
 Inst VLAN BD   Auth ED              State                Site If(s)        
 0    100  100  *CSR1000v-02         active              Gi3:SI100
 0    101  101   CSR1000v-05         inactive(NA)        Gi3:SI101
 Total VLAN(s): 2

CSR1000v-02#
CSR1000v-02#
CSR1000v-02#
CSR1000v-02#show otv route

Codes: BD - Bridge-Domain, AD - Admin-Distance,
       SI - Service Instance, * - Backup Route

OTV Unicast MAC Routing Table for Overlay1

 Inst VLAN BD     MAC Address    AD    Owner  Next Hops(s)
----------------------------------------------------------
 0    100  100    000c.2916.2320 40    BD Eng Gi3:SI100
 0    100  100    000c.29d4.1d6d 50    ISIS   CSR1000v-01
 0    100  100    001e.e529.5fbc 40    BD Eng Gi3:SI100
 0    100  100    001e.e6ad.85bc 50    ISIS   CSR1000v-01
 0    101  101    000c.29d4.1d6d 50    ISIS   CSR1000v-04
 0    101  101    001e.e62f.5dbc 50    ISIS   CSR1000v-04

6 unicast routes displayed in Overlay1

----------------------------------------------------------
6 Total Unicast Routes Displayed

CSR1000v-02#
CSR1000v-05#show otv
Overlay Interface Overlay1
 VPN name                 : Site-B
 VPN ID                   : 1
 State                    : UP
 Fwd-capable              : Yes
 Fwd-ready                : Yes
 AED-Server               : No
 Backup AED-Server        : Yes
 AED Capable              : Yes
 Join interface(s)        : GigabitEthernet2.15
 Join IPv4 address        : 192.168.15.1
 Tunnel interface(s)      : Tunnel0
 Encapsulation format     : GRE/IPv4
 Site Bridge-Domain       : 100
 Capability               : Unicast-only
 Is Adjacency Server      : No
 Adj Server Configured    : Yes
 Prim/Sec Adj Svr(s)      : 192.168.11.1/192.168.12.1

CSR1000v-05#
CSR1000v-05#
CSR1000v-05#
CSR1000v-05#show otv site
Site Adjacency Information (Site Bridge-Domain: 100)

Overlay1 Site-Local Adjacencies (Count: 2)

  Hostname       System ID      Last Change Ordinal    AED Enabled Status
  CSR1000v-02    001E.BD50.2A00 01:28:41    0          site       overlay
* CSR1000v-05    001E.E529.5F00 01:29:28    1          site       overlay


CSR1000v-05#
CSR1000v-05#
CSR1000v-05#
CSR1000v-05#show otv ad
CSR1000v-05#show otv adjacency
Overlay Adjacency Database for overlay 1
Hostname                       System-ID      Dest Addr       Site-ID        Up Time   State
CSR1000v-04                    001e.e6ad.8500 192.168.14.1    0000.0000.0001 01:29:29  UP
CSR1000v-01                    001e.e62f.5d00 192.168.11.1    0000.0000.0001 00:03:59  UP
CSR1000v-02                    001e.bd50.2a00 192.168.12.1    0000.0000.0002 00:03:59  UP

CSR1000v-05#
CSR1000v-05#
CSR1000v-05#
CSR1000v-05#show otv vlan
Key:  SI - Service Instance, NA - Non AED, NFC - Not Forward Capable.

Overlay 1 VLAN Configuration Information
 Inst VLAN BD   Auth ED              State                Site If(s)
 0    100  100   CSR1000v-02         inactive(NA)        Gi3:SI100
 0    101  101  *CSR1000v-05         active              Gi3:SI101
 Total VLAN(s): 2

CSR1000v-05#
CSR1000v-05#
CSR1000v-05#
CSR1000v-05#show otv route

Codes: BD - Bridge-Domain, AD - Admin-Distance,
       SI - Service Instance, * - Backup Route

OTV Unicast MAC Routing Table for Overlay1

 Inst VLAN BD     MAC Address    AD    Owner  Next Hops(s)
----------------------------------------------------------
 0    100  100    000c.29d4.1d6d 50    ISIS   CSR1000v-01
 0    100  100    001e.e6ad.85bc 50    ISIS   CSR1000v-01
 0    101  101    000c.2916.2320 40    BD Eng Gi3:SI101
 0    101  101    000c.29d4.1d6d 50    ISIS   CSR1000v-04
 0    101  101    001e.bd50.2abc 40    BD Eng Gi3:SI101
 0    101  101    001e.e62f.5dbc 50    ISIS   CSR1000v-04

6 unicast routes displayed in Overlay1

----------------------------------------------------------
6 Total Unicast Routes Displayed

CSR1000v-05#

ステータス確認は以上です。

負荷分散の確認

OTV負荷分散の説明

OTVの負荷分散は、エッジデバイスの内部インタフェースで定義しているVlan単位で分散します。例えば、本検証環境の場合、SiteAとSiteBのエッジデバイスは内部インタフェースでVlan100とVlan101を定義しています。その場合の分散は下記となります。

Vlan100のパケット転送処理は、CSR1000v-01とCSR1000v-02間によって行われる
Vlan101のパケット転送処理は、CSR1000v-04とCSR1000v-05間によって行われる

各エッジデバイスがどのVlanを担当するかは『show otv vlan』の「State」を確認し「active」かどうかで確認できます。

OTVの負荷分散確認

実際に負荷分散が行われているかを確認します。現時点でのステータスは下記のとおりです。

■CSR1000v-01
Inst VLAN BD Auth ED State Site If(s)
0 100 100 *CSR1000v-01 active Gi3:SI100
0 101 101 CSR1000v-04 inactive(NA) Gi3:SI101

■CSR1000v-04
Inst VLAN BD Auth ED State Site If(s)
0 100 100 CSR1000v-01 inactive(NA) Gi3:SI100
0 101 101 *CSR1000v-04 active Gi3:SI101

■CSR1000v-02
Inst VLAN BD Auth ED State Site If(s)
0 100 100 *CSR1000v-02 active Gi3:SI100
0 101 101 CSR1000v-05 inactive(NA) Gi3:SI101

■CSR1000v-05
Inst VLAN BD Auth ED State Site If(s)
0 100 100 CSR1000v-02 inactive(NA) Gi3:SI100
0 101 101 *CSR1000v-05 active Gi3:SI101

Vlan100のパケットは『CSR1000v-01<–>CSR1000v-02』で行われ、Vlan101のパケットは『CSR1000v-04<–>CSR1000v-05』で行われます。

次に負荷分散が実際に行われているかを確認します。手順は下記とします。
　①VyOS-01とVyOS-02でtcpdumpを行う
　②Vlan100で大量のトラフィックを発生させる
　③VyOS-01のVlan11とVlan12でGREパケットが大量に転送されていることを確認する
　④Vlan101で大量のトラフィックを発生させる
　⑤VyOS-02のVlan14とVlan15でGREパケットが大量に転送されていることを確認する
（※OTVはパケットをGREでカプセルします）

以下で実施してみます。

『①VyOS-01とVyOS-02でtcpdumpを行う』
対象インタフェースは各エッジデバイス向けインタフェースとします。

vyos@VyOS-01:~$ tcpdump -i eth2.11 -n proto 'gre'
vyos@VyOS-01:~$ tcpdump -i eth2.12 -n proto 'gre'
vyos@VyOS-02:~$ tcpdump -i eth2.14 -n proto 'gre'
vyos@VyOS-02:~$ tcpdump -i eth2.15 -n proto 'gre'

『②Vlan100で大量のトラフィックを発生させる』

N9Kv-V9-01# ping 192.168.100.2 interval 0 timeout 1 count unlimited
PING 192.168.100.2 (192.168.100.2): 56 data bytes
64 bytes from 192.168.100.2: icmp_seq=0 ttl=254 time=6.891 ms
64 bytes from 192.168.100.2: icmp_seq=1 ttl=254 time=7.039 ms
64 bytes from 192.168.100.2: icmp_seq=2 ttl=254 time=7.204 ms
64 bytes from 192.168.100.2: icmp_seq=3 ttl=254 time=6.653 ms
64 bytes from 192.168.100.2: icmp_seq=4 ttl=254 time=11.102 ms
64 bytes from 192.168.100.2: icmp_seq=5 ttl=254 time=19.908 ms
64 bytes from 192.168.100.2: icmp_seq=6 ttl=254 time=19.073 ms
64 bytes from 192.168.100.2: icmp_seq=7 ttl=254 time=19.955 ms
64 bytes from 192.168.100.2: icmp_seq=8 ttl=254 time=19.858 ms
64 bytes from 192.168.100.2: icmp_seq=9 ttl=254 time=23.397 ms
64 bytes from 192.168.100.2: icmp_seq=10 ttl=254 time=15.893 ms
64 bytes from 192.168.100.2: icmp_seq=11 ttl=254 time=19.89 ms
64 bytes from 192.168.100.2: icmp_seq=12 ttl=254 time=18.938 ms
64 bytes from 192.168.100.2: icmp_seq=13 ttl=254 time=19.979 ms
64 bytes from 192.168.100.2: icmp_seq=14 ttl=254 time=20.086 ms
64 bytes from 192.168.100.2: icmp_seq=15 ttl=254 time=19.683 ms
64 bytes from 192.168.100.2: icmp_seq=16 ttl=254 time=19.14 ms
つづく…

『③VyOS-01のVlan11とVlan12でGREパケットが大量に転送されていることを確認する』
pingを実施したと同時に、VyOS-01側でGREパケットが大量に転送されていることが確認できました。（対してVyOS-02は微量なGREパケットのみの転送であり、上記の大量のpingは明らかにVlan11とVlan12側を通っている）

vyos@VyOS-01:~$ tcpdump -i eth2.11 -n proto 'gre'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth2.11, link-type EN10MB (Ethernet), capture size 262144 bytes
09:16:24.464238 IP 192.168.11.1 > 192.168.12.1: GREv0, length 64: gre-proto-0x8848
09:16:24.464282 IP 192.168.11.1 > 192.168.15.1: GREv0, length 64: gre-proto-0x8848
＜省略＞
09:17:21.616710 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.620184 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.625716 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.629151 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.632741 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.636205 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.639720 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.643144 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.646728 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.654145 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.657730 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.674135 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.677676 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.693143 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.697727 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.713147 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.717709 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.733123 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.738680 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.754935 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.760761 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.772326 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.776727 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.792140 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.795715 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.811148 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.814984 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.831302 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.835837 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.851175 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.855777 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.871145 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.874678 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.890136 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.894730 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.910154 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.914725 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.930145 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.934674 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.949149 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.953720 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.969199 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.973684 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.989141 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.992672 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.008132 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.011680 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.028149 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.032698 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.048207 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.051664 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.067151 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.071676 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.087144 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.091675 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.107169 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.111681 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.126131 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.129684 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.146151 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.150737 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.166144 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.169699 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.185143 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.188677 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.205135 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.209700 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.225126 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.229684 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.244133 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.247716 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.264177 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.268673 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.284188 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.287677 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.303124 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.307670 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.323132 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.326672 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.343128 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.346748 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.363157 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.367688 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.382130 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.385667 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.402423 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.405667 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.422127 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.429672 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.441126 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.448750 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.461138 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.468679 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.610127 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.613815 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.630109 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.633732 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.649111 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.653700 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.669138 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.673649 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.689125 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.761668 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.765098 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.781663 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.785111 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.800666 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.804124 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.820678 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.825100 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.840666 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.845138 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.859845 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.863122 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.879664 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.883117 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.899655 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.903159 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.918663 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.922117 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.938655 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.942172 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.958646 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.962123 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.977651 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.981144 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.997644 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
つづく…
vyos@VyOS-01:~$ tcpdump -i eth2.12 -n proto 'gre'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth2.12, link-type EN10MB (Ethernet), capture size 262144 bytes
09:15:01.005866 IP 192.168.12.1 > 192.168.11.1: GREv0, length 64: gre-proto-0x8848
09:15:01.005917 IP 192.168.12.1 > 192.168.15.1: GREv0, length 64: gre-proto-0x8848
＜省略＞
09:17:21.772295 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.776767 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.792112 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.795751 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.811119 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.815017 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.831256 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.835868 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.851154 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.855808 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.871114 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.874707 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.890106 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.894766 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.910125 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.914756 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.930109 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.934706 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.949117 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.953748 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.969169 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.973711 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:21.989111 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:21.992700 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.008105 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.011706 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.028118 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.032730 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.048178 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.051693 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.067116 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.071736 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.087114 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.091703 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.107140 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.111719 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.126098 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.129718 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.146121 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.150770 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.166103 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.169730 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.185111 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.188703 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.205105 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.209734 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.225100 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.229713 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.244101 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.247746 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.264148 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.268703 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.284159 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.287712 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.303095 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.307698 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.323103 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.326706 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.343098 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.346786 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.363128 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.367722 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.382102 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.385698 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.402392 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.405696 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.422101 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.429709 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.441094 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.448778 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.461108 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.468707 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.610092 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.613849 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.630080 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.633762 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.649078 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.653747 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.669108 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.673686 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.689096 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.761700 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.765070 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.781694 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.785081 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.800707 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.804091 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.820708 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.825072 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.840697 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.845101 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.859876 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.863094 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.879692 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.883088 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.899678 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.903130 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.918689 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.922086 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.938690 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.942142 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.958676 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.962093 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.977678 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
09:17:22.981114 IP 192.168.12.1 > 192.168.11.1: GREv0, length 106: gre-proto-0x8848
09:17:22.997672 IP 192.168.11.1 > 192.168.12.1: GREv0, length 106: gre-proto-0x8848
つづく…

『④Vlan101で大量のトラフィックを発生させる』

N9Kv-V9-01# ping 192.168.101.2 interval 0 timeout 1 count unlimited
PING 192.168.101.2 (192.168.101.2): 56 data bytes
64 bytes from 192.168.101.2: icmp_seq=0 ttl=254 time=110.919 ms
64 bytes from 192.168.101.2: icmp_seq=1 ttl=254 time=20.436 ms
64 bytes from 192.168.101.2: icmp_seq=2 ttl=254 time=18.825 ms
64 bytes from 192.168.101.2: icmp_seq=3 ttl=254 time=19.611 ms
64 bytes from 192.168.101.2: icmp_seq=4 ttl=254 time=20.239 ms
64 bytes from 192.168.101.2: icmp_seq=5 ttl=254 time=18.996 ms
64 bytes from 192.168.101.2: icmp_seq=6 ttl=254 time=20.475 ms
64 bytes from 192.168.101.2: icmp_seq=7 ttl=254 time=19.384 ms
64 bytes from 192.168.101.2: icmp_seq=8 ttl=254 time=18.986 ms
64 bytes from 192.168.101.2: icmp_seq=9 ttl=254 time=19.756 ms
64 bytes from 192.168.101.2: icmp_seq=10 ttl=254 time=20.015 ms
64 bytes from 192.168.101.2: icmp_seq=11 ttl=254 time=21.713 ms
64 bytes from 192.168.101.2: icmp_seq=12 ttl=254 time=17.554 ms
64 bytes from 192.168.101.2: icmp_seq=13 ttl=254 time=22.107 ms
64 bytes from 192.168.101.2: icmp_seq=14 ttl=254 time=138.768 ms
64 bytes from 192.168.101.2: icmp_seq=15 ttl=254 time=27.884 ms
64 bytes from 192.168.101.2: icmp_seq=16 ttl=254 time=19.232 ms
つづく…

『⑤VyOS-02のVlan14とVlan15でGREパケットが大量に転送されていることを確認する』
pingを実施したと同時に、VyOS-02側でGREパケットが大量に転送されていることを確認できます。

vyos@VyOS-02:~$ tcpdump -i eth2.14 -n proto 'gre'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth2.14, link-type EN10MB (Ethernet), capture size 262144 bytes
09:26:28.320665 IP 192.168.11.1 > 192.168.14.1: GREv0, length 64: gre-proto-0x8848
09:26:30.326489 IP 192.168.14.1 > 192.168.15.1: GREv0, length 64: gre-proto-0x8848
＜省略＞
09:26:38.343421 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.347045 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.363414 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.367029 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.383421 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.387070 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.402411 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.406074 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.422426 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.426061 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.442429 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.446044 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.461418 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.466056 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.481420 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.485217 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.501550 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.574037 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.650420 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.654082 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.669425 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.673049 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.689432 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.693139 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.709413 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.713083 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.728411 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.732148 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.748402 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.752055 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.768448 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.772049 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.788423 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.792057 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.807409 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.811053 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.827409 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.831059 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.847420 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.851065 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.866456 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.870047 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.886409 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.890053 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.258418 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:39.262062 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.278409 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:39.282076 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.297473 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:39.604052 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.608999 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:39.624063 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.628426 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:39.644060 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.649413 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:39.663093 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.668418 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:39.683045 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.687413 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:39.703068 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.707448 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:39.722042 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.989119 IP 192.168.15.1 > 192.168.14.1: GREv0, length 64: gre-proto-0x8848
つづく…
vyos@VyOS-02:~$ tcpdump -i eth2.15 -n proto 'gre'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth2.15, link-type EN10MB (Ethernet), capture size 262144 bytes
09:26:28.320646 IP 192.168.11.1 > 192.168.15.1: GREv0, length 64: gre-proto-0x8848
09:26:30.326520 IP 192.168.14.1 > 192.168.15.1: GREv0, length 64: gre-proto-0x8848
＜省略＞
09:26:38.343463 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.347017 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.363443 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.367005 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.383449 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.387045 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.402439 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.406041 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.422456 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.426027 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.442459 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.446016 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.461447 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.466019 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.481448 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.485189 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.501596 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.574009 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.650449 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.654044 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.669455 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.673020 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.689458 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.693114 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.709440 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.713046 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.728444 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.732114 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.748428 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.752019 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.768482 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.772014 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.788451 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.792024 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.807438 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.811021 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.827442 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.831027 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.847449 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.851037 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.866486 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.870019 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:38.886438 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:38.890024 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.258449 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:39.262028 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.278438 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:39.282044 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.297504 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:39.604020 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.609047 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:39.624030 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.628455 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:39.644030 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.649441 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:39.663067 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.668446 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:39.683016 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.687441 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:39.703032 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.707478 IP 192.168.14.1 > 192.168.15.1: GREv0, length 106: gre-proto-0x8848
09:26:39.722021 IP 192.168.15.1 > 192.168.14.1: GREv0, length 106: gre-proto-0x8848
09:26:39.989067 IP 192.168.15.1 > 192.168.11.1: GREv0, length 64: gre-proto-0x8848
09:26:39.989100 IP 192.168.15.1 > 192.168.12.1: GREv0, length 64: gre-proto-0x8848
09:26:39.989114 IP 192.168.15.1 > 192.168.14.1: GREv0, length 64: gre-proto-0x8848
つづく…

Vlan単位で負荷分散が行われていることが確認できました。
以上で負荷分散の確認を終えます。

障害試験

障害試験ではエッジデバイスをパワーオフ/オンを行い、切り替わり時間と復旧時間を確認します。

障害試験の流れは下記の通り。
　①N9Kv-V9-01からN9Kv-V9-02に対して、Vlan100とVlan101にpingを実施
　②CSR1000v-01のパワーオフを実施（ESXi上で仮想的にパワーオフ）
　③pingの断時間を計測
　④CSR1000v-01のパワーオンを実施（ESXi上で仮想的にパワーオン）
　⑤pingの断時間を計測

以下で障害試験を実施します。

『①N9Kv-V9-01からN9Kv-V9-02に対して、Vlan100とVlan101にpingを実施』

N9Kv-V9-01# ping 192.168.100.2 interval 1 timeout 1 count unlimited
PING 192.168.100.2 (192.168.100.2): 56 data bytes
64 bytes from 192.168.100.2: icmp_seq=0 ttl=254 time=387.047 ms
64 bytes from 192.168.100.2: icmp_seq=1 ttl=254 time=7.312 ms
つづく…

『②CSR1000v-01のパワーオフを実施（ESXi上で仮想的にパワーオフ）』

『③pingの断時間を計測』
下記の通り、9秒ほどの通信断が発生しました。なお、同タイミングでVlan101のほうでもpingを実施していましたがこちらはエッジデバイスのCSR1000v-04を経由しているので無影響でした。

64 bytes from 192.168.100.2: icmp_seq=285 ttl=254 time=8.236 ms
64 bytes from 192.168.100.2: icmp_seq=286 ttl=254 time=149.477 ms
64 bytes from 192.168.100.2: icmp_seq=287 ttl=254 time=7.114 ms
Request 288 timed out
Request 289 timed out
Request 290 timed out
Request 291 timed out
Request 292 timed out
Request 293 timed out
Request 294 timed out
Request 295 timed out
Request 296 timed out
64 bytes from 192.168.100.2: icmp_seq=297 ttl=254 time=8.383 ms
64 bytes from 192.168.100.2: icmp_seq=298 ttl=254 time=7.169 ms
64 bytes from 192.168.100.2: icmp_seq=299 ttl=254 time=9.411 ms

続けて他エッジデバイスのステータス確認をします。
CSR1000v-04がSiteAでシングル構成になっており、「show otv vlan」でVlan100とVlan101の両方がactiveになっていることが分かります。つまり、Vlan100がCSR1000v-04へと切り替わりました。

CSR1000v-04#show otv
Overlay Interface Overlay1
 VPN name                 : Site-A
 VPN ID                   : 1
 State                    : UP
 Fwd-capable              : Yes
 Fwd-ready                : Yes
 AED-Server               : Yes
 Backup AED-Server        : No
 AED Capable              : Yes
 Join interface(s)        : GigabitEthernet2.14
 Join IPv4 address        : 192.168.14.1
 Tunnel interface(s)      : Tunnel0
 Encapsulation format     : GRE/IPv4
 Site Bridge-Domain       : 100
 Capability               : Unicast-only
 Is Adjacency Server      : No
 Adj Server Configured    : Yes
 Prim/Sec Adj Svr(s)      : 192.168.11.1/192.168.12.1

CSR1000v-04#
CSR1000v-04#
CSR1000v-04#
CSR1000v-04#show otv site
Site Adjacency Information (Site Bridge-Domain: 100)

Overlay1 Site-Local Adjacencies (Count: 1)

  Hostname       System ID      Last Change Ordinal    AED Enabled Status
* CSR1000v-04    001E.E6AD.8500 05:10:05    0          site       overlay


CSR1000v-04#
CSR1000v-04#
CSR1000v-04#
CSR1000v-04#show otv adjacency
Overlay Adjacency Database for overlay 1
Hostname                       System-ID      Dest Addr       Site-ID        Up Time   State
CSR1000v-05                    001e.e529.5f00 192.168.15.1    0000.0000.0002 05:10:10  UP
CSR1000v-02                    001e.bd50.2a00 192.168.12.1    0000.0000.0002 03:44:39  UP

CSR1000v-04#
CSR1000v-04#
CSR1000v-04#
CSR1000v-04#show otv vlan
Key:  SI - Service Instance, NA - Non AED, NFC - Not Forward Capable.

Overlay 1 VLAN Configuration Information
 Inst VLAN BD   Auth ED              State                Site If(s)
 0    100  100  *CSR1000v-04         active              Gi3:SI100
 0    101  101  *CSR1000v-04         active              Gi3:SI101
 Total VLAN(s): 2

CSR1000v-04#
CSR1000v-04#
CSR1000v-04#
CSR1000v-04#show otv route

Codes: BD - Bridge-Domain, AD - Admin-Distance,
       SI - Service Instance, * - Backup Route

OTV Unicast MAC Routing Table for Overlay1

 Inst VLAN BD     MAC Address    AD    Owner  Next Hops(s)
----------------------------------------------------------
 0    100  100    000c.2916.2320 50    ISIS   CSR1000v-02
 0    100  100    000c.29d4.1d6d 40    BD Eng Gi3:SI100
 0    100  100    001e.e529.5fbc 50    ISIS   CSR1000v-02
 0    101  101    000c.2916.2320 50    ISIS   CSR1000v-05
 0    101  101    000c.29d4.1d6d 40    BD Eng Gi3:SI101
 0    101  101    001e.bd50.2abc 50    ISIS   CSR1000v-05
 0    101  101    001e.e62f.5dbc 40    BD Eng Gi3:SI101

7 unicast routes displayed in Overlay1

----------------------------------------------------------
7 Total Unicast Routes Displayed

CSR1000v-04#
CSR1000v-02#show otv
Overlay Interface Overlay1
 VPN name                 : Site-B
 VPN ID                   : 1
 State                    : UP
 Fwd-capable              : Yes
 Fwd-ready                : Yes
 AED-Server               : Yes
 Backup AED-Server        : No
 AED Capable              : Yes
 Join interface(s)        : GigabitEthernet2.12
 Join IPv4 address        : 192.168.12.1
 Tunnel interface(s)      : Tunnel0
 Encapsulation format     : GRE/IPv4
 Site Bridge-Domain       : 100
 Capability               : Unicast-only
 Is Adjacency Server      : Yes
 Adj Server Configured    : Yes
 Prim/Sec Adj Svr(s)      : 192.168.11.1

CSR1000v-02#
CSR1000v-02#
CSR1000v-02#
CSR1000v-02#show otv site
Site Adjacency Information (Site Bridge-Domain: 100)

Overlay1 Site-Local Adjacencies (Count: 2)

  Hostname       System ID      Last Change Ordinal    AED Enabled Status
* CSR1000v-02    001E.BD50.2A00 05:10:32    0          site       overlay
  CSR1000v-05    001E.E529.5F00 05:09:06    1          site       overlay


CSR1000v-02#
CSR1000v-02#
CSR1000v-02#
CSR1000v-02#show otv adjacency
Overlay Adjacency Database for overlay 1
Hostname                       System-ID      Dest Addr       Site-ID        Up Time   State
CSR1000v-04                    001e.e6ad.8500 192.168.14.1    0000.0000.0001 03:44:40  UP
CSR1000v-05                    001e.e529.5f00 192.168.15.1    0000.0000.0002 03:44:40  UP

CSR1000v-02#
CSR1000v-02#
CSR1000v-02#
CSR1000v-02#show otv vlan
Key:  SI - Service Instance, NA - Non AED, NFC - Not Forward Capable.

Overlay 1 VLAN Configuration Information
 Inst VLAN BD   Auth ED              State                Site If(s)        
 0    100  100  *CSR1000v-02         active              Gi3:SI100
 0    101  101   CSR1000v-05         inactive(NA)        Gi3:SI101
 Total VLAN(s): 2

CSR1000v-02#
CSR1000v-02#
CSR1000v-02#
CSR1000v-02#show otv route

Codes: BD - Bridge-Domain, AD - Admin-Distance,
       SI - Service Instance, * - Backup Route

OTV Unicast MAC Routing Table for Overlay1

 Inst VLAN BD     MAC Address    AD    Owner  Next Hops(s)
----------------------------------------------------------
 0    100  100    000c.2916.2320 40    BD Eng Gi3:SI100
 0    100  100    000c.29d4.1d6d 50    ISIS   CSR1000v-04
 0    100  100    001e.e529.5fbc 40    BD Eng Gi3:SI100
 0    100  100    001e.e6ad.85bc 50    ISIS   CSR1000v-04
 0    101  101    000c.29d4.1d6d 50    ISIS   CSR1000v-04
 0    101  101    001e.e62f.5dbc 50    ISIS   CSR1000v-04

6 unicast routes displayed in Overlay1

----------------------------------------------------------
6 Total Unicast Routes Displayed

CSR1000v-02#
CSR1000v-05#show otv
Overlay Interface Overlay1
 VPN name                 : Site-B
 VPN ID                   : 1
 State                    : UP
 Fwd-capable              : Yes
 Fwd-ready                : Yes
 AED-Server               : No
 Backup AED-Server        : Yes
 AED Capable              : Yes
 Join interface(s)        : GigabitEthernet2.15
 Join IPv4 address        : 192.168.15.1
 Tunnel interface(s)      : Tunnel0
 Encapsulation format     : GRE/IPv4
 Site Bridge-Domain       : 100
 Capability               : Unicast-only
 Is Adjacency Server      : No
 Adj Server Configured    : Yes
 Prim/Sec Adj Svr(s)      : 192.168.11.1/192.168.12.1

CSR1000v-05#
CSR1000v-05#
CSR1000v-05#
CSR1000v-05#show otv site
Site Adjacency Information (Site Bridge-Domain: 100)

Overlay1 Site-Local Adjacencies (Count: 2)

  Hostname       System ID      Last Change Ordinal    AED Enabled Status
  CSR1000v-02    001E.BD50.2A00 05:09:19    0          site       overlay
* CSR1000v-05    001E.E529.5F00 05:10:06    1          site       overlay


CSR1000v-05#
CSR1000v-05#
CSR1000v-05#
CSR1000v-05#show otv adjacency
Overlay Adjacency Database for overlay 1
Hostname                       System-ID      Dest Addr       Site-ID        Up Time   State
CSR1000v-04                    001e.e6ad.8500 192.168.14.1    0000.0000.0001 05:10:10  UP
CSR1000v-02                    001e.bd50.2a00 192.168.12.1    0000.0000.0002 03:44:40  UP

CSR1000v-05#
CSR1000v-05#
CSR1000v-05#show otv vlan
Key:  SI - Service Instance, NA - Non AED, NFC - Not Forward Capable.

Overlay 1 VLAN Configuration Information
 Inst VLAN BD   Auth ED              State                Site If(s)
 0    100  100   CSR1000v-02         inactive(NA)        Gi3:SI100
 0    101  101  *CSR1000v-05         active              Gi3:SI101
 Total VLAN(s): 2

CSR1000v-05#
CSR1000v-05#
CSR1000v-05#
CSR1000v-05#show otv route

Codes: BD - Bridge-Domain, AD - Admin-Distance,
       SI - Service Instance, * - Backup Route

OTV Unicast MAC Routing Table for Overlay1

 Inst VLAN BD     MAC Address    AD    Owner  Next Hops(s)
----------------------------------------------------------
 0    100  100    000c.29d4.1d6d 50    ISIS   CSR1000v-04
 0    101  101    000c.2916.2320 40    BD Eng Gi3:SI101
 0    101  101    000c.29d4.1d6d 50    ISIS   CSR1000v-04
 0    101  101    001e.bd50.2abc 40    BD Eng Gi3:SI101
 0    101  101    001e.e62f.5dbc 50    ISIS   CSR1000v-04

5 unicast routes displayed in Overlay1

----------------------------------------------------------
5 Total Unicast Routes Displayed

CSR1000v-05#

『④CSR1000v-01のパワーオンを実施（ESXi上で仮想的にパワーオン）』

『⑤pingの断時間を計測』
切り戻りが発生しているので少なからず断は発生する想定ですが今回の検証では通信断は確認できませんでした。「interval 1 timeout 1」とわりと緩い条件でpingを実施していたからかもしれません。

では最終的にステータス確認を行い、最初の状態に戻ったことを確認します。

CSR1000v-01#show otv
Overlay Interface Overlay1
 VPN name                 : Site-A
 VPN ID                   : 1
 State                    : UP
 Fwd-capable              : Yes
 Fwd-ready                : Yes
 AED-Server               : No
 Backup AED-Server        : Yes
 AED Capable              : Yes
 Join interface(s)        : GigabitEthernet2.11
 Join IPv4 address        : 192.168.11.1
 Tunnel interface(s)      : Tunnel0
 Encapsulation format     : GRE/IPv4
 Site Bridge-Domain       : 100
 Capability               : Unicast-only
 Is Adjacency Server      : Yes
 Adj Server Configured    : No
 Prim/Sec Adj Svr(s)      : None

CSR1000v-01#
CSR1000v-01#
CSR1000v-01#
CSR1000v-01#show otv site
Site Adjacency Information (Site Bridge-Domain: 100)

Overlay1 Site-Local Adjacencies (Count: 2)

  Hostname       System ID      Last Change Ordinal    AED Enabled Status
* CSR1000v-01    001E.E62F.5D00 00:08:48    0          site       overlay
  CSR1000v-04    001E.E6AD.8500 00:09:22    1          site       overlay


CSR1000v-01#
CSR1000v-01#
CSR1000v-01#
CSR1000v-01#show otv adjacency
Overlay Adjacency Database for overlay 1
Hostname                       System-ID      Dest Addr       Site-ID        Up Time   State
CSR1000v-04                    001e.e6ad.8500 192.168.14.1    0000.0000.0001 00:09:23  UP
CSR1000v-05                    001e.e529.5f00 192.168.15.1    0000.0000.0002 00:09:23  UP
CSR1000v-02                    001e.bd50.2a00 192.168.12.1    0000.0000.0002 00:09:23  UP

CSR1000v-01#
CSR1000v-01#
CSR1000v-01#
CSR1000v-01#show otv vlan
Key:  SI - Service Instance, NA - Non AED, NFC - Not Forward Capable.

Overlay 1 VLAN Configuration Information
 Inst VLAN BD   Auth ED              State                Site If(s)       
 0    100  100  *CSR1000v-01         active              Gi3:SI100
 0    101  101   CSR1000v-04         inactive(NA)        Gi3:SI101
 Total VLAN(s): 2

CSR1000v-01#
CSR1000v-01#
CSR1000v-01#
CSR1000v-01#show otv route

Codes: BD - Bridge-Domain, AD - Admin-Distance,
       SI - Service Instance, * - Backup Route

OTV Unicast MAC Routing Table for Overlay1

 Inst VLAN BD     MAC Address    AD    Owner  Next Hops(s)
----------------------------------------------------------
 0    100  100    000c.2916.2320 50    ISIS   CSR1000v-02
 0    100  100    000c.29d4.1d6d 40    BD Eng Gi3:SI100
 0    100  100    001e.e529.5fbc 50    ISIS   CSR1000v-02
 0    100  100    001e.e6ad.85bc 40    BD Eng Gi3:SI100
 0    101  101    000c.2916.2320 50    ISIS   CSR1000v-05
 0    101  101    001e.bd50.2abc 50    ISIS   CSR1000v-05

6 unicast routes displayed in Overlay1

----------------------------------------------------------
6 Total Unicast Routes Displayed

CSR1000v-01#
CSR1000v-04#show otv
Overlay Interface Overlay1
 VPN name                 : Site-A
 VPN ID                   : 1
 State                    : UP
 Fwd-capable              : Yes
 Fwd-ready                : Yes
 AED-Server               : Yes
 Backup AED-Server        : No
 AED Capable              : Yes
 Join interface(s)        : GigabitEthernet2.14
 Join IPv4 address        : 192.168.14.1
 Tunnel interface(s)      : Tunnel0
 Encapsulation format     : GRE/IPv4
 Site Bridge-Domain       : 100
 Capability               : Unicast-only
 Is Adjacency Server      : No
 Adj Server Configured    : Yes
 Prim/Sec Adj Svr(s)      : 192.168.11.1/192.168.12.1

CSR1000v-04#
CSR1000v-04#
CSR1000v-04#
CSR1000v-04#show otv site
Site Adjacency Information (Site Bridge-Domain: 100)

Overlay1 Site-Local Adjacencies (Count: 2)

  Hostname       System ID      Last Change Ordinal    AED Enabled Status
  CSR1000v-01    001E.E62F.5D00 00:07:48    0          site       overlay
* CSR1000v-04    001E.E6AD.8500 05:24:02    1          site       overlay


CSR1000v-04#
CSR1000v-04#
CSR1000v-04#
CSR1000v-04#show otv adjacency
Overlay Adjacency Database for overlay 1
Hostname                       System-ID      Dest Addr       Site-ID        Up Time   State
CSR1000v-01                    001e.e62f.5d00 192.168.11.1    0000.0000.0001 00:09:23  UP
CSR1000v-05                    001e.e529.5f00 192.168.15.1    0000.0000.0002 05:24:07  UP
CSR1000v-02                    001e.bd50.2a00 192.168.12.1    0000.0000.0002 03:58:36  UP

CSR1000v-04#
CSR1000v-04#
CSR1000v-04#
CSR1000v-04#show otv vlan
Key:  SI - Service Instance, NA - Non AED, NFC - Not Forward Capable.

Overlay 1 VLAN Configuration Information
 Inst VLAN BD   Auth ED              State                Site If(s)
 0    100  100   CSR1000v-01         inactive(NA)        Gi3:SI100
 0    101  101  *CSR1000v-04         active              Gi3:SI101
 Total VLAN(s): 2

CSR1000v-04#
CSR1000v-04#
CSR1000v-04#
CSR1000v-04#show otv route

Codes: BD - Bridge-Domain, AD - Admin-Distance,
       SI - Service Instance, * - Backup Route

OTV Unicast MAC Routing Table for Overlay1

 Inst VLAN BD     MAC Address    AD    Owner  Next Hops(s)
----------------------------------------------------------
 0    100  100    000c.2916.2320 50    ISIS   CSR1000v-02
 0    100  100    001e.e529.5fbc 50    ISIS   CSR1000v-02
 0    101  101    000c.2916.2320 50    ISIS   CSR1000v-05
 0    101  101    000c.29d4.1d6d 40    BD Eng Gi3:SI101
 0    101  101    001e.bd50.2abc 50    ISIS   CSR1000v-05
 0    101  101    001e.e62f.5dbc 40    BD Eng Gi3:SI101

6 unicast routes displayed in Overlay1

----------------------------------------------------------
6 Total Unicast Routes Displayed

CSR1000v-04#
CSR1000v-02#show otv
Overlay Interface Overlay1
 VPN name                 : Site-B
 VPN ID                   : 1
 State                    : UP
 Fwd-capable              : Yes
 Fwd-ready                : Yes
 AED-Server               : Yes
 Backup AED-Server        : No
 AED Capable              : Yes
 Join interface(s)        : GigabitEthernet2.12
 Join IPv4 address        : 192.168.12.1
 Tunnel interface(s)      : Tunnel0
 Encapsulation format     : GRE/IPv4
 Site Bridge-Domain       : 100
 Capability               : Unicast-only
 Is Adjacency Server      : Yes
 Adj Server Configured    : Yes
 Prim/Sec Adj Svr(s)      : 192.168.11.1

CSR1000v-02#
CSR1000v-02#
CSR1000v-02#
CSR1000v-02#show otv site
Site Adjacency Information (Site Bridge-Domain: 100)

Overlay1 Site-Local Adjacencies (Count: 2)

  Hostname       System ID      Last Change Ordinal    AED Enabled Status
* CSR1000v-02    001E.BD50.2A00 05:24:29    0          site       overlay
  CSR1000v-05    001E.E529.5F00 05:23:03    1          site       overlay


CSR1000v-02#
CSR1000v-02#
CSR1000v-02#
CSR1000v-02#show otv adjacency
Overlay Adjacency Database for overlay 1
Hostname                       System-ID      Dest Addr       Site-ID        Up Time   State
CSR1000v-04                    001e.e6ad.8500 192.168.14.1    0000.0000.0001 03:58:37  UP
CSR1000v-01                    001e.e62f.5d00 192.168.11.1    0000.0000.0001 00:09:23  UP
CSR1000v-05                    001e.e529.5f00 192.168.15.1    0000.0000.0002 03:58:37  UP

CSR1000v-02#
CSR1000v-02#
CSR1000v-02#
CSR1000v-02#show otv vlan
Key:  SI - Service Instance, NA - Non AED, NFC - Not Forward Capable.

Overlay 1 VLAN Configuration Information
 Inst VLAN BD   Auth ED              State                Site If(s)        
 0    100  100  *CSR1000v-02         active              Gi3:SI100
 0    101  101   CSR1000v-05         inactive(NA)        Gi3:SI101
 Total VLAN(s): 2

CSR1000v-02#
CSR1000v-02#
CSR1000v-02#
CSR1000v-02#show otv route

Codes: BD - Bridge-Domain, AD - Admin-Distance,
       SI - Service Instance, * - Backup Route

OTV Unicast MAC Routing Table for Overlay1

 Inst VLAN BD     MAC Address    AD    Owner  Next Hops(s)
----------------------------------------------------------
 0    100  100    000c.2916.2320 40    BD Eng Gi3:SI100
 0    100  100    000c.29d4.1d6d 50    ISIS   CSR1000v-01
 0    100  100    001e.e529.5fbc 40    BD Eng Gi3:SI100
 0    100  100    001e.e62f.5dbc 50    ISIS   CSR1000v-01
 0    100  100    001e.e6ad.85bc 50    ISIS   CSR1000v-01
 0    101  101    000c.29d4.1d6d 50    ISIS   CSR1000v-04
 0    101  101    001e.e62f.5dbc 50    ISIS   CSR1000v-04

7 unicast routes displayed in Overlay1

----------------------------------------------------------
7 Total Unicast Routes Displayed

CSR1000v-02#
CSR1000v-05#show otv
Overlay Interface Overlay1
 VPN name                 : Site-B
 VPN ID                   : 1
 State                    : UP
 Fwd-capable              : Yes
 Fwd-ready                : Yes
 AED-Server               : No
 Backup AED-Server        : Yes
 AED Capable              : Yes
 Join interface(s)        : GigabitEthernet2.15
 Join IPv4 address        : 192.168.15.1
 Tunnel interface(s)      : Tunnel0
 Encapsulation format     : GRE/IPv4
 Site Bridge-Domain       : 100
 Capability               : Unicast-only
 Is Adjacency Server      : No
 Adj Server Configured    : Yes
 Prim/Sec Adj Svr(s)      : 192.168.11.1/192.168.12.1

CSR1000v-05#
CSR1000v-05#
CSR1000v-05#
CSR1000v-05#show otv site
Site Adjacency Information (Site Bridge-Domain: 100)

Overlay1 Site-Local Adjacencies (Count: 2)

  Hostname       System ID      Last Change Ordinal    AED Enabled Status
  CSR1000v-02    001E.BD50.2A00 05:23:16    0          site       overlay
* CSR1000v-05    001E.E529.5F00 05:24:03    1          site       overlay


CSR1000v-05#
CSR1000v-05#
CSR1000v-05#
CSR1000v-05#show otv adjacency
Overlay Adjacency Database for overlay 1
Hostname                       System-ID      Dest Addr       Site-ID        Up Time   State
CSR1000v-04                    001e.e6ad.8500 192.168.14.1    0000.0000.0001 05:24:06  UP
CSR1000v-01                    001e.e62f.5d00 192.168.11.1    0000.0000.0001 00:09:22  UP
CSR1000v-02                    001e.bd50.2a00 192.168.12.1    0000.0000.0002 03:58:36  UP

CSR1000v-05#
CSR1000v-05#
CSR1000v-05#
CSR1000v-05#show otv vlan
Key:  SI - Service Instance, NA - Non AED, NFC - Not Forward Capable.

Overlay 1 VLAN Configuration Information
 Inst VLAN BD   Auth ED              State                Site If(s)
 0    100  100   CSR1000v-02         inactive(NA)        Gi3:SI100
 0    101  101  *CSR1000v-05         active              Gi3:SI101
 Total VLAN(s): 2

CSR1000v-05#
CSR1000v-05#
CSR1000v-05#
CSR1000v-05#show otv route

Codes: BD - Bridge-Domain, AD - Admin-Distance,
       SI - Service Instance, * - Backup Route

OTV Unicast MAC Routing Table for Overlay1

 Inst VLAN BD     MAC Address    AD    Owner  Next Hops(s)
----------------------------------------------------------
 0    100  100    000c.29d4.1d6d 50    ISIS   CSR1000v-01
 0    100  100    001e.e6ad.85bc 50    ISIS   CSR1000v-01
 0    101  101    000c.2916.2320 40    BD Eng Gi3:SI101
 0    101  101    000c.29d4.1d6d 50    ISIS   CSR1000v-04
 0    101  101    001e.bd50.2abc 40    BD Eng Gi3:SI101
 0    101  101    001e.e62f.5dbc 50    ISIS   CSR1000v-04

6 unicast routes displayed in Overlay1

----------------------------------------------------------
6 Total Unicast Routes Displayed

CSR1000v-05#

以上で障害試験、及び第二回目の検証を終えます。

OTV（Overlay Transport Virtualization）Cisco,仮想化