1. MC-LAG ICCP Down Test 구성도
1) MC-LAG ICCP Down Test 구성도
- 본 글은 IRB VRRP L3 Interface를 이용한 MC-LAG에서 ICCP 다운 발생 시, ARP 및 FDB Table이 Learning 되는 과정을 확인하는 것이 목표
- MC-LAG 개념 및 MC-LAG 기본 동작 과정을 먼저 학습하는 것을 권고
- ICCP Session이 다운되면 MC-LAG 피어에 설정한 Remote Static ARP에 대한 정보가 ARP Table에서 제거되며 해당 결과에 대한 이유는 Juniper Vendor에게 구두로 질문하였지만 답을 듣지 못하는 상황
- 아래 Wireshark 캡처를 확인할 때 참고하기 위한 MAC Address 정보
2) 테스트 장비
(1) 실장비
Hostname | Model | OS | Firmware(BIOS) |
vMX1 | QFX5120-48T | 23.4R2-S2.1 | CBDE_P_LIG1_00.29.01 |
vMX2 | QFX5120-48T | 23.4R2-S2.1 | CBDE_P_LIG1_00.29.01 |
vMX3 | EX4300-24T | 21.4R3-S3.4 | - |
- Emulator로 테스트 진행 시, MC-LAG Peer의 FDB Learning이 안 되는 문제가 있어 실장비와 동시에 테스트
(2) Emulator
- Emulator : EVE-NG
- OS : Juniper vMX 18.2R1.9
2. MC-LAG IRB VRRP L3 Interface Configuration
1) MC-LAG IRB VRRP L3 Interface Configuration
더보기
< vMX1 Configuration >
set system host-name vMX1
set chassis aggregated-devices ethernet device-count 1
set interfaces ge-0/0/0 unit 0 family inet address 1.1.2.1/24
set interfaces ge-0/0/1 unit 0 family bridge interface-mode trunk
set interfaces ge-0/0/1 unit 0 family bridge vlan-id 30
set interfaces ge-0/0/2 ether-options 802.3ad ae30
set interfaces ae30 aggregated-ether-options lacp active
set interfaces ae30 aggregated-ether-options lacp system-id 00:00:00:00:00:30
set interfaces ae30 aggregated-ether-options lacp admin-key 30
set interfaces ae30 aggregated-ether-options mc-ae mc-ae-id 30
set interfaces ae30 aggregated-ether-options mc-ae redundancy-group 12
set interfaces ae30 aggregated-ether-options mc-ae chassis-id 0
set interfaces ae30 aggregated-ether-options mc-ae mode active-active
set interfaces ae30 aggregated-ether-options mc-ae status-control active
set interfaces ae30 unit 0 family bridge interface-mode trunk
set interfaces ae30 unit 0 family bridge vlan-id 30
set interfaces irb unit 30 family inet address 30.0.0.2/24 arp 30.0.0.3 l2-interface ge-0/0/1.0
set interfaces irb unit 30 family inet address 30.0.0.2/24 arp 30.0.0.3 mac 2c:6b:f5:96:00:f0
set interfaces irb unit 30 family inet address 30.0.0.2/24 vrrp-group 10 virtual-address 30.0.0.1
set interfaces irb unit 30 family inet address 30.0.0.2/24 vrrp-group 10 priority 120
set interfaces irb unit 30 family inet address 30.0.0.2/24 vrrp-group 10 accept-data
set interfaces lo0 unit 0 family inet address 1.1.1.1/32
set multi-chassis multi-chassis-protection 1.1.2.2 interface ge-0/0/1
set protocols iccp local-ip-addr 1.1.2.1
set protocols iccp peer 1.1.2.2 redundancy-group-id-list 12
set protocols iccp peer 1.1.2.2 liveness-detection minimum-receive-interval 1000
set protocols iccp peer 1.1.2.2 liveness-detection multiplier 3
set protocols iccp peer 1.1.2.2 liveness-detection transmit-interval minimum-interval 1000
set bridge-domains VLAN30 description "ICL&CLIENT3"
set bridge-domains VLAN30 vlan-id 30
set bridge-domains VLAN30 routing-interface irb.30
set switch-options service-id 12
더보기
< vMX2 Configuration >
set system host-name vMX2
set chassis aggregated-devices ethernet device-count 1
set interfaces ge-0/0/0 unit 0 family inet address 1.1.2.2/24
set interfaces ge-0/0/1 unit 0 family bridge interface-mode trunk
set interfaces ge-0/0/1 unit 0 family bridge vlan-id 30
set interfaces ge-0/0/2 ether-options 802.3ad ae30
set interfaces ae30 aggregated-ether-options lacp active
set interfaces ae30 aggregated-ether-options lacp system-id 00:00:00:00:00:30
set interfaces ae30 aggregated-ether-options lacp admin-key 30
set interfaces ae30 aggregated-ether-options mc-ae mc-ae-id 30
set interfaces ae30 aggregated-ether-options mc-ae redundancy-group 12
set interfaces ae30 aggregated-ether-options mc-ae chassis-id 1
set interfaces ae30 aggregated-ether-options mc-ae mode active-active
set interfaces ae30 aggregated-ether-options mc-ae status-control standby
set interfaces ae30 unit 0 family bridge interface-mode trunk
set interfaces ae30 unit 0 family bridge vlan-id 30
set interfaces irb unit 30 family inet address 30.0.0.3/24 arp 30.0.0.2 l2-interface ge-0/0/1.0
set interfaces irb unit 30 family inet address 30.0.0.3/24 arp 30.0.0.2 mac 2c:6b:f5:46:59:f0
set interfaces irb unit 30 family inet address 30.0.0.3/24 vrrp-group 10 virtual-address 30.0.0.1
set interfaces irb unit 30 family inet address 30.0.0.3/24 vrrp-group 10 priority 100
set interfaces irb unit 30 family inet address 30.0.0.3/24 vrrp-group 10 accept-data
set interfaces lo0 unit 0 family inet address 2.2.2.2/32
set multi-chassis multi-chassis-protection 1.1.2.1 interface ge-0/0/1
set protocols iccp local-ip-addr 1.1.2.2
set protocols iccp peer 1.1.2.1 redundancy-group-id-list 12
set protocols iccp peer 1.1.2.1 liveness-detection minimum-receive-interval 1000
set protocols iccp peer 1.1.2.1 liveness-detection multiplier 3
set protocols iccp peer 1.1.2.1 liveness-detection transmit-interval minimum-interval 1000
set bridge-domains VLAN30 description "ICL&CLIENT3"
set bridge-domains VLAN30 vlan-id 30
set bridge-domains VLAN30 routing-interface irb.30
set switch-options service-id 12
더보기
< vMX3 Configuration >
set system host-name vMX3
set chassis aggregated-devices ethernet device-count 1
set interfaces ge-0/0/0 ether-options 802.3ad ae30
set interfaces ge-0/0/1 ether-options 802.3ad ae30
set interfaces ae30 aggregated-ether-options lacp active
set interfaces ae30 unit 0 family bridge interface-mode trunk
set interfaces ae30 unit 0 family bridge vlan-id 30
set interfaces irb unit 30 family inet address 30.0.0.10/24
set bridge-domains VLAN30 vlan-id 30
set bridge-domains VLAN30 routing-interface irb.30
2) ICCP Session Check
더보기
root@vMX1> show iccp
Redundancy Group Information for peer 1.1.2.2
TCP Connection : Established
Liveliness Detection : Up
Redundancy Group ID Status
12 Up
Client Application: l2ald_iccpd_client
Redundancy Group IDs Joined: 12
Client Application: lacpd
Redundancy Group IDs Joined: 12
root@vMX2> show iccp
Redundancy Group Information for peer 1.1.2.1
TCP Connection : Established
Liveliness Detection : Up
Redundancy Group ID Status
12 Up
Client Application: l2ald_iccpd_client
Redundancy Group IDs Joined: 12
Client Application: lacpd
Redundancy Group IDs Joined: 12
3) ICL and MC-AE State Check
더보기
root@vMX1> show interfaces mc-ae extensive
Member Link : ae30
Current State Machine's State: mcae active state
Local Status : active
Local State : up
Peer Status : active
Peer State : up
Logical Interface : ae30.0
Topology Type : bridge
Local State : up
Peer State : up
Peer Ip/MCP/State : 1.1.2.2 ge-0/0/1.0 up
MCAE Configuration
Redundancy Group : 12
MCAE ID : 30
MCAE Mode : active_active
Status Control : active
Chassis ID : 0
LACP Configuration
System ID : 00:00:00:00:00:30
Admin Key : 30
root@vMX2> show interfaces mc-ae extensive
Member Link : ae30
Current State Machine's State: mcae active state
Local Status : active
Local State : up
Peer Status : active
Peer State : up
Logical Interface : ae30.0
Topology Type : bridge
Local State : up
Peer State : up
Peer Ip/MCP/State : 1.1.2.1 ge-0/0/1.0 up
MCAE Configuration
Redundancy Group : 12
MCAE ID : 30
MCAE Mode : active_active
Status Control : standby
Chassis ID : 1
LACP Configuration
System ID : 00:00:00:00:00:30
Admin Key : 30
4) LACP State Check
더보기
root@vMX1> show lacp interfaces extensive
Aggregated interface: ae30
LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity
ge-0/0/2 Actor No No Yes Yes Yes Yes Fast Active
ge-0/0/2 Partner No No Yes Yes Yes Yes Fast Active
LACP protocol: Receive State Transmit State Mux State
ge-0/0/2 Current Fast periodic Collecting distributing
LACP info: Role System System Port Port Port
priority identifier priority number key
ge-0/0/2 Actor 127 00:00:00:00:00:30 127 1 30
ge-0/0/2 Partner 127 2c:6b:f5:8c:8c:c0 127 1 31
root@vMX2> show lacp interfaces extensive
Aggregated interface: ae30
LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity
ge-0/0/2 Actor No No Yes Yes Yes Yes Fast Active
ge-0/0/2 Partner No No Yes Yes Yes Yes Fast Active
LACP protocol: Receive State Transmit State Mux State
ge-0/0/2 Current Fast periodic Collecting distributing
LACP info: Role System System Port Port Port
priority identifier priority number key
ge-0/0/2 Actor 127 00:00:00:00:00:30 127 32769 30
ge-0/0/2 Partner 127 2c:6b:f5:8c:8c:c0 127 2 31
root@vMX3> show lacp interfaces extensive
Aggregated interface: ae30
LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity
ge-0/0/0 Actor No No Yes Yes Yes Yes Fast Active
ge-0/0/0 Partner No No Yes Yes Yes Yes Fast Active
ge-0/0/1 Actor No No Yes Yes Yes Yes Fast Active
ge-0/0/1 Partner No No Yes Yes Yes Yes Fast Active
LACP protocol: Receive State Transmit State Mux State
ge-0/0/0 Current Fast periodic Collecting distributing
ge-0/0/1 Current Fast periodic Collecting distributing
LACP info: Role System System Port Port Port
priority identifier priority number key
ge-0/0/0 Actor 127 2c:6b:f5:8c:8c:c0 127 1 31
ge-0/0/0 Partner 127 00:00:00:00:00:30 127 1 30
ge-0/0/1 Actor 127 2c:6b:f5:8c:8c:c0 127 2 31
ge-0/0/1 Partner 127 00:00:00:00:00:30 127 32769 30
5) VRRP State Check
더보기
root@vMX1> show vrrp
Interface State Group VR state VR Mode Timer Type Address
irb.30 up 10 master Active A 0.465 lcl 30.0.0.2
vip 30.0.0.1
root@vMX2> show vrrp
Interface State Group VR state VR Mode Timer Type Address
irb.30 up 10 backup Active D 3.587 lcl 30.0.0.3
vip 30.0.0.1
mas 30.0.0.2
3. ICCP Session Down
1) ICCP Session Down
< vMX1 & vMX2 ICCP Interface Down >
set interfaces ge-0/0/0 disable
2) ICCP Session Check
root@vMX1> show iccp
Redundancy Group Information for peer 1.1.2.2
TCP Connection : In progress
Liveliness Detection : Down
Redundancy Group ID Status
12 Down
Client Application: l2ald_iccpd_client
Redundancy Group IDs Joined: 12
Client Application: lacpd
Redundancy Group IDs Joined: 12
root@vMX2> show iccp
Redundancy Group Information for peer 1.1.2.1
TCP Connection : In progress
Liveliness Detection : Down
Redundancy Group ID Status
12 Down
Client Application: l2ald_iccpd_client
Redundancy Group IDs Joined: 12
Client Application: lacpd
Redundancy Group IDs Joined: 12
3) ICL and MC-AE State Check
root@vMX1> show interfaces mc-ae extensive
Member Link : ae30
Current State Machine's State: mcae active state
Local Status : active
Local State : down
Peer Status : Unknown
Peer State : Unknown
Logical Interface : ae30.0
Topology Type : bridge
Local State : up
Peer State : Unknown
Peer Ip/MCP/State : 1.1.2.2 ge-0/0/1.0 up
MCAE Configuration
Redundancy Group : 12
MCAE ID : 30
MCAE Mode : active_active
Status Control : active
Chassis ID : 0
LACP Configuration
System ID : 00:00:00:00:00:30
Admin Key : 30
root@vMX2> show interfaces mc-ae extensive
Member Link : ae30
Current State Machine's State: mcae active state
Local Status : active
Local State : up
Peer Status : Unknown
Peer State : Unknown
Logical Interface : ae30.0
Topology Type : bridge
Local State : up
Peer State : Unknown
Peer Ip/MCP/State : 1.1.2.1 ge-0/0/1.0 up
MCAE Configuration
Redundancy Group : 12
MCAE ID : 30
MCAE Mode : active_active
Status Control : standby
Chassis ID : 1
LACP Configuration
System ID : 00:00:00:00:00:30
Admin Key : 30
- ICCP 다운 시, LACP System-ID가 Default로 변경어 MC-LAG Client는 가장 먼저 LACP PDU를 수신하는 인터페이스를 사용하며 나중에 LACP PDU를 수신하는 인터페이스는 LACP System-ID가 다르므로 Mux State가 "Detached"으로 표시
- Local은 Active State이며 ICCP가 다운이므로 Remote State 파악 불가
4) LACP State Check
root@vMX1> show lacp interfaces extensive
Aggregated interface: ae30
LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity
ge-0/0/2 Actor No No No No Yes Yes Fast Active
ge-0/0/2 Partner No No No No No Yes Fast Active
LACP protocol: Receive State Transmit State Mux State
ge-0/0/2 Current Fast periodic Attached
LACP info: Role System System Port Port Port
priority identifier priority number key
ge-0/0/2 Actor 127 2c:6b:f5:46:59:c0 127 1 30
ge-0/0/2 Partner 127 2c:6b:f5:8c:8c:c0 127 1 31
root@vMX2> show lacp interfaces extensive
Aggregated interface: ae30
LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity
ge-0/0/2 Actor No No Yes Yes Yes Yes Fast Active
ge-0/0/2 Partner No No Yes Yes Yes Yes Fast Active
LACP protocol: Receive State Transmit State Mux State
ge-0/0/2 Current Fast periodic Collecting distributing
LACP info: Role System System Port Port Port
priority identifier priority number key
ge-0/0/2 Actor 127 2c:6b:f5:96:00:c0 127 32769 30
ge-0/0/2 Partner 127 2c:6b:f5:8c:8c:c0 127 2 31
root@vMX3> show lacp interfaces extensive
Aggregated interface: ae30
LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity
ge-0/0/0 Actor No No No No No Yes Fast Active
ge-0/0/0 Partner No No No No Yes Yes Fast Active
ge-0/0/1 Actor No No Yes Yes Yes Yes Fast Active
ge-0/0/1 Partner No No Yes Yes Yes Yes Fast Active
LACP protocol: Receive State Transmit State Mux State
ge-0/0/0 Current Fast periodic Detached
ge-0/0/1 Current Fast periodic Collecting distributing
LACP info: Role System System Port Port Port
priority identifier priority number key
ge-0/0/0 Actor 127 2c:6b:f5:8c:8c:c0 127 1 31
ge-0/0/0 Partner 127 2c:6b:f5:46:59:c0 127 1 30
ge-0/0/1 Actor 127 2c:6b:f5:8c:8c:c0 127 2 31
ge-0/0/1 Partner 127 2c:6b:f5:96:00:c0 127 32769 30
root@vMX3> show lacp interfaces extensive
Aggregated interface: ae30
LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity
ge-0/0/0 Actor No No No No No Yes Fast Active
ge-0/0/0 Partner No No No No Yes Yes Fast Active
ge-0/0/1 Actor No No Yes Yes Yes Yes Fast Active
ge-0/0/1 Partner No No Yes Yes Yes Yes Fast Active
LACP protocol: Receive State Transmit State Mux State
ge-0/0/0 Current Fast periodic Detached
ge-0/0/1 Current Fast periodic Collecting distributing
LACP info: Role System System Port Port Port
priority identifier priority number key
ge-0/0/0 Actor 127 2c:6b:f5:8c:8c:c0 127 1 31
ge-0/0/0 Partner 127 2c:6b:f5:46:59:c0 127 1 30
ge-0/0/1 Actor 127 2c:6b:f5:8c:8c:c0 127 2 31
ge-0/0/1 Partner 127 2c:6b:f5:96:00:c0 127 32769 30
5) VRRP State Check
root@vMX1> show vrrp
Interface State Group VR state VR Mode Timer Type Address
irb.30 up 10 master Active A 0.902 lcl 30.0.0.2
vip 30.0.0.1
root@vMX2> show vrrp
Interface State Group VR state VR Mode Timer Type Address
irb.30 up 10 backup Active D 3.340 lcl 30.0.0.3
vip 30.0.0.1
mas 30.0.0.2
6) vMX3 → VRRP Virtual-IP ICMP Request
- ping 테스트 전, ARP Table 및 FDB Table은 위 그림과 같은 상태
- vMX3은 VRRP Advertisement 패킷을 주기적으로 수신하므로 FDB에 Learning된 상태
- ICCP Session이 다운되었으므로 vMX1 및 vMX2는 Remote 장비에 대한 Static ARP 정보가 없는 상태
root@vMX3> ping 30.0.0.1 count 1
PING 30.0.0.1 (30.0.0.1): 56 data bytes
64 bytes from 30.0.0.1: icmp_seq=0 ttl=64 time=19.083 ms
--- 30.0.0.1 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 19.083/19.083/19.083/0.000 ms
- 테스트를 위해 vMX3에서 V-IP로 ICMP Request를 전송
- vMX3 ARP Table에 V-IP 정보가 없으므로 ARP Request 전송
- vMX2는 Broadcast를 수신하였으므로 Flooding
- vMX2는 S-MAC Learning을 하지만 ICCP Session이 다운되었으므로 vMX1과 동기화 불가
- vMX2는 ARP Request를 수신하고 D-MAC이 본인임을 확인하고 Target IP가 본인이므로 Sender MAC과 Sender IP 정보를 ARP Table에 Learning 하고 Opcode가 ARP Request이므로 이에 대응되는 ARP Reply를 전송
- Juniper MC-LAG에서 IRB를 이용한 VRRP 사용 시, Backup 장비가 데이터를 수신하여도 직접 처리
- vMX1은 ARP Request를 ICL로 수신했으므로 S-MAC Learning 및 ARP Resolution(Learning) 불가
- Juniper MC-LAG는 ICL 인터페이스를 통한 Dynamic Resolution은 지원하지 않으며 ARP Entry는 Remote MC-LAG Peer에서 ICCP를 이용하여 ICL 인터페이스에 학습 가능
- vMX2는 ARP Request를 수신하고 D-MAC이 본인임을 확인하고 Target IP가 본인임을 확인하고 Opcode가 ARP Request 임을 확인하여 이에 대응되는 ARP Reply를 전송
- vMX3은 ARP Reply를 수신하여 S-MAC을 Learning 하고 D-MAC이 본인임을 확인하고 Target IP가 본인이므로 Sender MAC과 Sender IP 정보를 ARP Table에 Learning
- vMX1은 ARP Request를 수신하고 D-MAC이 본인임을 확인하고 Target IP가 본인임을 확인하고 Opcode가 ARP Request 임을 확인하여 이에 대응되는 ARP Reply를 전송
- vMX3은 ARP Reply를 수신하여 S-MAC을 Learning 하고 D-MAC이 본인임을 확인하고 Target IP가 본인이므로 Sender MAC과 Sender IP 정보를 ARP Table에 Learning
- vMX3 ARP Table에 V-IP 정보가 있으므로 ICMP Request를 전송
- vMX2 ARP Table에 vMX3 IRB 정보가 있으므로 ICMP Reply를 전송
- vMX3는 ICMP Reply의 S-MAC인 vMX2 IRB MAC을 Learning
7) vMX3 → vMX1 Real-IP ICMP Request
- ping 테스트 전, ARP Table 및 FDB Table은 위 그림과 같은 상태
root@vMX3> ping 30.0.0.2 count 1
PING 30.0.0.2 (30.0.0.2): 56 data bytes
^C
--- 30.0.0.2 ping statistics ---
1 packets transmitted, 0 packets received, 100% packet loss
- 테스트를 위해 vMX3에서 vMX1 R-IP로 ICMP Request를 전송
- vMX3 ARP Table에 vMX1 IRB 정보가 없으므로 ARP Request 전송
- vMX2는 Broadcast를 수신하였으므로 Flooding
- vMX2는 S-MAC Learning을 하지만 ICCP Session 다운이므로 vMX1과 동기화 불가능
- vMX2는 ARP Request를 수신했지만 Target IP가 본인이 아니므로 ARP Learning 불가
- vMX1은 ARP Request를 ICL로 수신했으므로 S-MAC Learning 및 ARP Resolution(Learning) 불가
- vMX1은 ARP Request를 수신하고 D-MAC이 본인임을 확인하고 Target IP가 본인임을 확인하고 Opcode가 ARP Request 임을 확인하여 이에 대응되는 ARP Reply를 전송
- vMX2는 ARP Reply를 수신했지만 ICL로 수신하였으므로 S-MAC Learning 불가능
- vMX2 FDB Table에 D-MAC에 대한 정보가 있으므로 Forwarding
- vMX3은 ARP Reply를 수신하여 S-MAC을 Learning 하고 D-MAC이 본인임을 확인하고 Target IP가 본인이므로 Sender MAC과 Sender IP 정보를 ARP Table에 Learning
- vMX3 ARP Table에 vMX1 IRB 정보가 있으므로 ICMP Request 전송
- vMX2는 D-MAC이 FDB Table에 없으므로 Flooding
- 현재 vMX1 ARP Table에 vMX3 IRB에 대한 정보가 없으므로 ARP Request를 전송
- vMX2는 Broadcast를 수신하였으므로 Flooding
- vMX2는 ARP Request를 수신했지만 Target IP가 본인이 아니므로 ARP Learning 불가능
- vMX3는 ARP Request를 수신하여 S-MAC을 Learning 하고 D-MAC이 본인임을 확인하고 Target IP가 본인이므로 Sender MAC과 Sender IP 정보를 ARP Table에 Learning 하고 Opcode가 ARP Request이므로 이에 대응되는 ARP Reply를 전송
- vMX2는 ARP Reply를 수신하여 S-MAC을 Learning 하고 D-MAC이 본인임을 확인하고 Target IP가 본인이므로 Sender MAC과 Sender IP 정보를 ARP Table에 Learning
- vMX2는 ARP Reply를 수신했지만 ICCP Session이 다운이므로 Remote MC-LAG Peer와 ARP 동기화 불가
8) vMX3 → vMX2 Real-IP ICMP Request
- ping 테스트 전, ARP Table 및 FDB Table은 위 그림과 같은 상태
root@vMX3> ping 30.0.0.3 count 1
PING 30.0.0.3 (30.0.0.3): 56 data bytes
64 bytes from 30.0.0.3: icmp_seq=0 ttl=64 time=181.771 ms
--- 30.0.0.3 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 181.771/181.771/181.771/0.000 ms
- 테스트를 위해 vMX3에서 vMX2 R-IP로 ICMP Request를 전송
- vMX3 ARP Table에 vMX2 IRB 정보가 없으므로 ARP Request 전송
- vMX2는 Broadcast를 수신하였으므로 Flooding
- vMX2는 S-MAC Learning을 하지만 ICCP Session 다운이므로 vMX1과 동기화 불가능
- vMX2는 ARP Request를 수신하고 D-MAC이 본인임을 확인하고 Target IP가 본인이므로 Sender MAC과 Sender IP 정보를 ARP Table에 Learning 하고 Opcode가 ARP Request이므로 이에 대응되는 ARP Reply를 전송
- vMX1은 ARP Request를 수신했지만 Target IP가 본인이 아니므로 ARP Learning 불가능
- vMX1은 ARP Request를 수신하였지만 ICL로 수신하였으므로 ARP Resolution(Learning) 불가
- vMX2는 ARP Request를 수신하고 D-MAC이 본인임을 확인하고 Target IP가 본인임을 확인하고 Opcode가 ARP Request 임을 확인하여 이에 대응되는 ARP Reply를 전송
- vMX1은 ARP Reply를 수신했지만 ICL로 수신하였으므로 S-MAC Learning 불가능
- vMX1은 D-MAC이 본인이 아니므로 직접 처리 불가
- vMX3은 ARP Reply를 수신하여 S-MAC을 Learning 하고 D-MAC이 본인임을 확인하고 Target IP가 본인이므로 Sender MAC과 Sender IP 정보를 ARP Table에 Learning
- vMX3 ARP Table에 vMX2 IRB 정보가 있으므로 ICMP Request 전송
- vMX2 ARP Table에 vMX3 IRB 정보가 있으므로 ICMP Reply를 전송
- vMX3는 ICMP Reply의 S-MAC인 vMX2 IRB MAC을 Learning
'Network > MC-LAG' 카테고리의 다른 글
MC-LAG Option - "prefer-status-control-active" (0) | 2025.07.12 |
---|---|
MC-LAG Option - "backup-liveness-detection(BLD)" (1) | 2025.07.10 |
MC-LAG MC-AE Down with IRB VRRP L3 Interface (4) | 2025.07.06 |
MC-LAG ICL Down with IRB VRRP L3 Interface (1) | 2025.07.04 |
MC-LAG L3 Interface MAC Address Synchronization Configuration and ARP, FDB Table Synchronization(Juniper vMX) (1) | 2025.06.30 |
MC-LAG IRB VRRP L3 Interface Configuration and ARP, FDB Table Synchronization(Juniper vMX) (1) | 2025.06.28 |
MC-LAG Basic Configuration(Juniper vMX) (1) | 2025.06.26 |
MC-LAG MC-AE Mode(active-active or active-standby) (0) | 2025.06.24 |