VRRP Interface Track 동작 과정

2025. 3. 10. 22:17·Network/VRRP

1. VRRP Interface Track 동작 과정

1) 구성도 및 Configuration

더보기
< R1 : 설정 >
set bridge-domains VLAN10 vlan-id 10
set bridge-domains VLAN10 routing-interface irb.10
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-list 10
set interfaces irb unit 10 family inet address 10.0.0.2/24 vrrp-group 10 virtual-address 10.0.0.1
set interfaces irb unit 10 family inet address 10.0.0.2/24 vrrp-group 10 priority 120
set interfaces irb unit 10 family inet address 10.0.0.2/24 vrrp-group 10 accept-data
더보기
< R2 : 설정 >
set bridge-domains VLAN10 vlan-id 10
set bridge-domains VLAN10 routing-interface irb.10
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-list 10
set interfaces irb unit 10 family inet address 10.0.0.3/24 vrrp-group 10 virtual-address 10.0.0.1
set interfaces irb unit 10 family inet address 10.0.0.3/24 vrrp-group 10 accept-data
더보기
< SW : 설정 >
set bridge-domains VLAN10 vlan-id 10
set interfaces ge-0/0/0 unit 0 family bridge interface-mode trunk
set interfaces ge-0/0/0 unit 0 family bridge vlan-id-list 10
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-list 10
set interfaces ge-0/0/2 unit 0 family bridge interface-mode access
set interfaces ge-0/0/2 unit 0 family bridge vlan-id 10
  • Juniper Default Priority : 100 
  • Juniper Default Preempt : Enable
  • IGP는 OSPF로 구성하였으며 OSPF Interface-Type은 Broadcast로 설정

 

2) VRRP Interface Track 필요성

  • VRRP 동작 과정 및 VRRP Preempt 동작 과정은 이미 알고 있다는 가정하에 설명 시작

  • Master 장비는 Advertisement Interval마다 VRRP Advertisement를 전송하여 자신이 생존했음을 통보

 

  • R1 Uplink가 Down되어도 R1은 Master 상태를 유지
  • PC1은 외부로 데이터 전송 시, 게이트웨이인 V-MAC을 가지고 있는 Master인 R1까지 전송되지만 R1은 OSPF Neighbor가 끊어졌으므로 라우팅 테이블에 D-IP에 대한 정보가 없으므로 전송 불가

 

root@R1> show vrrp 
Interface     State       Group   VR state VR Mode   Timer    Type   Address
irb.10        up             10   master   Active      A  0.363 lcl    10.0.0.2       
                                                                vip    10.0.0.1
root@R1> show route table inet.0 1.1.1.1 

root@R1>
  • R1은 VRRP Master로 동작하면서 라우팅 테이블에 1.1.1.1/32 네트워크가 없는 상태

 

< PC1 Ping Test >
VPCS> ping 1.1.1.1

*10.0.0.2 icmp_seq=1 ttl=255 time=5.186 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=2 ttl=255 time=5.563 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=3 ttl=255 time=4.121 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=4 ttl=255 time=4.230 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=5 ttl=255 time=4.621 ms (ICMP type:3, code:0, Destination network unreachable)

 

3) VRRP Interface Track 동작 과정

(1) VRRP Interfae Track Configuration

< R1 : VRRP Interface Track 설정 >
set interfaces irb unit 10 family inet address 10.0.0.2/24 vrrp-group 10 track interface ge-0/0/0 priority-cost 70
	## ge-0/0/0 Down 시, Priority 70 감소
set interfaces irb unit 10 family inet address 10.0.0.2/24 vrrp-group 10 track priority-hold-time 45
	## 45초 동안 대기 후, Priority 변경

 

(2) R1 Uplink Failure

  • R1 ge-0/0/0이 Down되어도 위에서 설정한 'priority-hold-time' 시간 동안 R1은 VRRP Priority 값을 변경하지 않고 동작

 

root@R1> show vrrp 
Interface     State       Group   VR state VR Mode   Timer    Type   Address
irb.10        up             10   master   Active      A  0.049 lcl    10.0.0.2       
                                                                vip    10.0.0.1
root@R1> show vrrp detail 
Physical interface: irb, Unit: 10, Address: 10.0.0.2/24
  Index: 328, SNMP ifIndex: 537, VRRP-Traps: disabled, VRRP-Version: 2
  Interface state: up, Group: 10, State: master, VRRP Mode: Active
  Priority: 120, Advertisement interval: 1, Authentication type: none
  Advertisement threshold: 3, Computed send rate: 0
  Preempt: yes, Accept-data mode: yes, VIP count: 1, VIP: 10.0.0.1           
  Advertisement Timer: 0.661s, Master router: 10.0.0.2
  Virtual router uptime: 01:11:25, Master router uptime: 00:01:45
  Virtual Mac: 00:00:5e:00:01:0a
  Preferred: yes 
  Tracking: enabled 
    Current priority: 120, Configured priority: 120 
    Priority hold time: 45, Remaining: 23.512, Pending priority: 50
    Interface tracking: enabled, Interface count: 1  
      Interface     Int state   Int speed   Incurred priority cost
      ge-0/0/0.0    down                0                      70
    Route tracking: disabled
  • Interface Track이 Enable되었고 ge-0/0/0이 Down된 것을 인지하였지만 'priority-hold-time' 동안 Priority 값을 변경하지 않고 유지하여 Master로 계속 동작

 

root@R1> show route table inet.0 1.1.1.1 

root@R1>
더보기
< PC1 : Ping Test >
VPCS> ping 1.1.1.1 -c 1000 

84 bytes from 1.1.1.1 icmp_seq=1 ttl=63 time=5.419 ms
84 bytes from 1.1.1.1 icmp_seq=2 ttl=63 time=5.158 ms
1.1.1.1 icmp_seq=3 timeout
*10.0.0.2 icmp_seq=4 ttl=255 time=168.705 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=5 ttl=255 time=4.839 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=6 ttl=255 time=4.290 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=7 ttl=255 time=2.297 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=8 ttl=255 time=3.415 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=9 ttl=255 time=251.641 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=10 ttl=255 time=251.641 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=11 ttl=255 time=3.926 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=12 ttl=255 time=4.505 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=13 ttl=255 time=12.710 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=14 ttl=255 time=4.666 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=15 ttl=255 time=3.635 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=16 ttl=255 time=468.944 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=17 ttl=255 time=612.598 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=18 ttl=255 time=7.709 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=19 ttl=255 time=3.981 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=20 ttl=255 time=58.185 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=21 ttl=255 time=2.554 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=22 ttl=255 time=438.520 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=23 ttl=255 time=799.573 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=24 ttl=255 time=3.617 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=25 ttl=255 time=4.219 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=26 ttl=255 time=22.957 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=27 ttl=255 time=5.122 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=28 ttl=255 time=3.649 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=29 ttl=255 time=134.299 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=30 ttl=255 time=560.624 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=31 ttl=255 time=3.083 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=32 ttl=255 time=4.657 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=33 ttl=255 time=4.012 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=34 ttl=255 time=2.788 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=35 ttl=255 time=221.572 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=36 ttl=255 time=221.572 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=37 ttl=255 time=3.336 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=38 ttl=255 time=2.854 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=39 ttl=255 time=4.598 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=40 ttl=255 time=3.615 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=41 ttl=255 time=4.095 ms (ICMP type:3, code:0, Destination network unreachable)
*10.0.0.2 icmp_seq=42 ttl=255 time=4.095 ms (ICMP type:3, code:0, Destination network unreachable)
84 bytes from 1.1.1.1 icmp_seq=43 ttl=63 time=5.684 ms
84 bytes from 1.1.1.1 icmp_seq=44 ttl=63 time=5.643 ms
84 bytes from 1.1.1.1 icmp_seq=45 ttl=63 time=5.790 ms
84 bytes from 1.1.1.1 icmp_seq=46 ttl=63 time=5.787 ms
84 bytes from 1.1.1.1 icmp_seq=47 ttl=63 time=4.122 ms
84 bytes from 1.1.1.1 icmp_seq=48 ttl=63 time=4.997 ms
84 bytes from 1.1.1.1 icmp_seq=49 ttl=63 time=4.599 ms
84 bytes from 1.1.1.1 icmp_seq=50 ttl=63 time=4.627 ms
  • VRRP Priority 값을 변경하지 않으므로 PC1은 외부로 데이터 전송 시, 게이트웨이인 V-MAC을 가지고 있는 Master인 R1까지 전송되지만 R1은 OSPF Neighbor가 끊어져 라우팅 테이블에 D-IP에 대한 정보가 없으므로 PC1은 1.1.1.1과 통신 불가
  • 위 Ping Test는 R1 Uplink Down 시, Convergence될 때까지 진행한 결과로, R2가 Backup→Master로 변경될 때까지 통신 불가

 

  • R1은 'priority-hold-time' 후에 Priority를 감소하였지만 아직 Master로 동작

 

root@R1> show vrrp detail    
Physical interface: irb, Unit: 10, Address: 10.0.0.2/24
  Index: 328, SNMP ifIndex: 537, VRRP-Traps: disabled, VRRP-Version: 2
  Interface state: up, Group: 10, State: master, VRRP Mode: Active
  Priority: 50, Advertisement interval: 1, Authentication type: none
  Advertisement threshold: 3, Computed send rate: 0
  Preempt: yes, Accept-data mode: yes, VIP count: 1, VIP: 10.0.0.1           
  Advertisement Timer: 0.335s, Master router: 10.0.0.2
  Virtual router uptime: 01:51:43, Master router uptime: 00:00:49
  Virtual Mac: 00:00:5e:00:01:0a
  Preferred: yes 
  Tracking: enabled 
    Current priority: 50, Configured priority: 120 
    Priority hold time: 45, Not running 
    Interface tracking: enabled, Interface count: 1  
      Interface     Int state   Int speed   Incurred priority cost
      ge-0/0/0.0    down                0                      70
    Route tracking: disabled

 

(3) Master Device Change

  • R2는 본인보다 Priority가 낮은 VRRP Advertisement를 수신하고 Preempt 옵션이 동작하여 Master로 변경
  • PC1은 외부로 데이터 전송 시, 게이트웨이인 V-MAC을 가지고 있는 Master 장비인 R2로 전송되고 R2는 라우팅 테이블에 D-IP에 대한 정보가 있으므로 통신 가능

 

root@R1> show vrrp 
Interface     State       Group   VR state VR Mode   Timer    Type   Address
irb.10        up             10   backup   Active      D  2.857 lcl    10.0.0.2       
                                                                vip    10.0.0.1       
                                                                mas    10.0.0.3
root@R2> show vrrp 
Interface     State       Group   VR state VR Mode   Timer    Type   Address
irb.10        up             10   master   Active      A  0.044 lcl    10.0.0.3       
                                                                vip    10.0.0.1
root@R1> show vrrp detail 
Physical interface: irb, Unit: 10, Address: 10.0.0.2/24
  Index: 328, SNMP ifIndex: 537, VRRP-Traps: disabled, VRRP-Version: 2
  Interface state: up, Group: 10, State: backup, VRRP Mode: Active
  Priority: 50, Advertisement interval: 1, Authentication type: none
  Advertisement threshold: 3, Computed send rate: 0
  Preempt: yes, Accept-data mode: yes, VIP count: 1, VIP: 10.0.0.1           
  Dead timer: 2.451s, Master priority: 100, Master router: 10.0.0.3 
  Virtual router uptime: 01:13:20
  Preferred: yes 
  Tracking: enabled 
    Current priority: 50, Configured priority: 120 
    Priority hold time: 45, Not running 
    Interface tracking: enabled, Interface count: 1  
      Interface     Int state   Int speed   Incurred priority cost
      ge-0/0/0.0    down                0                      70
    Route tracking: disabled
  • Interface Track이 동작하여 Priority를 50으로 감소하였으며 Backup으로 동작 중이었던 R2는 Master로 동작

 

Oct  4 08:54:31  R1 mib2d[5931]: SNMP_TRAP_LINK_DOWN: ifIndex 526, ifAdminStatus down(2), ifOperStatus down(2), ifName ge-0/0/0
Oct  4 08:55:16  R1 vrrpd[16092]: VRRPD_NEW_BACKUP: Interface irb.10 (local address 10.0.0.2) became VRRP backup for group 10
  • R1은 로그 확인 결과 설정한 'priority-hold-time'과 비슷한 45s 후에 Master→Backup으로 변경

 

(4) R1 Uplink Recovery

  • R1 ge-0/0/0이 Up되어도 위에서 설정한 'Priority-hold-time' 시간 동안 R1은 VRRP Priority 값을 변경하지 않고 동작

 

root@R1> show vrrp 
Interface     State       Group   VR state VR Mode   Timer    Type   Address
irb.10        up             10   backup   Active      D  3.353 lcl    10.0.0.2       
                                                                vip    10.0.0.1       
                                                                mas    10.0.0.3
root@R2> show vrrp 
Interface     State       Group   VR state VR Mode   Timer    Type   Address
irb.10        up             10   master   Active      A  0.062 lcl    10.0.0.3       
                                                                vip    10.0.0.1
root@R1> show vrrp detail 
Physical interface: irb, Unit: 10, Address: 10.0.0.2/24
  Index: 328, SNMP ifIndex: 537, VRRP-Traps: disabled, VRRP-Version: 2
  Interface state: up, Group: 10, State: backup, VRRP Mode: Active
  Priority: 50, Advertisement interval: 1, Authentication type: none
  Advertisement threshold: 3, Computed send rate: 0
  Preempt: yes, Accept-data mode: yes, VIP count: 1, VIP: 10.0.0.1           
  Dead timer: 2.513s, Master priority: 100, Master router: 10.0.0.3 
  Virtual router uptime: 01:17:53
  Preferred: yes 
  Tracking: enabled 
    Current priority: 50, Configured priority: 120 
    Priority hold time: 45, Remaining: 34.048, Pending priority: 120
    Interface tracking: enabled, Interface count: 1  
      Interface     Int state   Int speed   Incurred priority cost
      ge-0/0/0.0    up                 1g                       0
    Route tracking: disabled
  • Interface Track이 Enable되었고 ge-0/0/0이 Up된 것을 인지하였지만 'priority-hole-time'동안 Priority 값을 변경하지 않고 유지하여 Backup으로 계속 동작

 

root@R2> show route table inet.0 1.1.1.1 

inet.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

1.1.1.1/32         *[OSPF/10] 14:02:51, metric 100
                    > to 1.1.3.1 via ge-0/0/0.0
더보기
< PC1 : Ping Test >
VPCS> ping 1.1.1.1 -c 1000

84 bytes from 1.1.1.1 icmp_seq=1 ttl=63 time=5.757 ms
84 bytes from 1.1.1.1 icmp_seq=2 ttl=63 time=5.199 ms
84 bytes from 1.1.1.1 icmp_seq=3 ttl=63 time=6.005 ms
84 bytes from 1.1.1.1 icmp_seq=4 ttl=63 time=5.261 ms
84 bytes from 1.1.1.1 icmp_seq=5 ttl=63 time=5.689 ms
84 bytes from 1.1.1.1 icmp_seq=6 ttl=63 time=5.340 ms
84 bytes from 1.1.1.1 icmp_seq=7 ttl=63 time=5.055 ms
84 bytes from 1.1.1.1 icmp_seq=8 ttl=63 time=4.720 ms
84 bytes from 1.1.1.1 icmp_seq=9 ttl=63 time=5.657 ms
84 bytes from 1.1.1.1 icmp_seq=10 ttl=63 time=5.892 ms
84 bytes from 1.1.1.1 icmp_seq=11 ttl=63 time=4.176 ms
84 bytes from 1.1.1.1 icmp_seq=12 ttl=63 time=4.653 ms
84 bytes from 1.1.1.1 icmp_seq=13 ttl=63 time=5.483 ms
84 bytes from 1.1.1.1 icmp_seq=14 ttl=63 time=5.320 ms
84 bytes from 1.1.1.1 icmp_seq=15 ttl=63 time=4.310 ms
84 bytes from 1.1.1.1 icmp_seq=16 ttl=63 time=4.382 ms
84 bytes from 1.1.1.1 icmp_seq=17 ttl=63 time=4.674 ms
84 bytes from 1.1.1.1 icmp_seq=18 ttl=63 time=5.813 ms
84 bytes from 1.1.1.1 icmp_seq=19 ttl=63 time=6.623 ms
84 bytes from 1.1.1.1 icmp_seq=20 ttl=63 time=4.602 ms
84 bytes from 1.1.1.1 icmp_seq=21 ttl=63 time=5.067 ms
84 bytes from 1.1.1.1 icmp_seq=22 ttl=63 time=5.184 ms
84 bytes from 1.1.1.1 icmp_seq=23 ttl=63 time=4.456 ms
84 bytes from 1.1.1.1 icmp_seq=24 ttl=63 time=4.737 ms
84 bytes from 1.1.1.1 icmp_seq=25 ttl=63 time=5.797 ms
84 bytes from 1.1.1.1 icmp_seq=26 ttl=63 time=6.725 ms
84 bytes from 1.1.1.1 icmp_seq=27 ttl=63 time=5.130 ms
84 bytes from 1.1.1.1 icmp_seq=28 ttl=63 time=5.843 ms
84 bytes from 1.1.1.1 icmp_seq=29 ttl=63 time=3.634 ms
84 bytes from 1.1.1.1 icmp_seq=30 ttl=63 time=5.463 ms
84 bytes from 1.1.1.1 icmp_seq=31 ttl=63 time=3.953 ms
84 bytes from 1.1.1.1 icmp_seq=32 ttl=63 time=4.682 ms
84 bytes from 1.1.1.1 icmp_seq=33 ttl=63 time=5.733 ms
84 bytes from 1.1.1.1 icmp_seq=34 ttl=63 time=6.185 ms
84 bytes from 1.1.1.1 icmp_seq=35 ttl=63 time=4.959 ms
84 bytes from 1.1.1.1 icmp_seq=36 ttl=63 time=5.640 ms
84 bytes from 1.1.1.1 icmp_seq=37 ttl=63 time=4.677 ms
84 bytes from 1.1.1.1 icmp_seq=38 ttl=63 time=4.680 ms
84 bytes from 1.1.1.1 icmp_seq=39 ttl=63 time=5.099 ms
84 bytes from 1.1.1.1 icmp_seq=40 ttl=63 time=5.145 ms
84 bytes from 1.1.1.1 icmp_seq=41 ttl=63 time=6.402 ms
84 bytes from 1.1.1.1 icmp_seq=42 ttl=63 time=6.663 ms
84 bytes from 1.1.1.1 icmp_seq=43 ttl=63 time=5.076 ms
84 bytes from 1.1.1.1 icmp_seq=44 ttl=63 time=4.362 ms
84 bytes from 1.1.1.1 icmp_seq=45 ttl=63 time=4.639 ms
84 bytes from 1.1.1.1 icmp_seq=46 ttl=63 time=4.590 ms
84 bytes from 1.1.1.1 icmp_seq=47 ttl=63 time=6.674 ms
84 bytes from 1.1.1.1 icmp_seq=48 ttl=63 time=5.184 ms
84 bytes from 1.1.1.1 icmp_seq=49 ttl=63 time=6.193 ms
84 bytes from 1.1.1.1 icmp_seq=50 ttl=63 time=5.629 ms
  • R2 라우팅 테이블에 D-IP인 1.1.1.1/32에 대한 네트워크 정보가 있으므로 PC1은 1.1.1.1과 통신 가능
  • 위 Ping Test는 R1 Uplink Recovery 시, Convergence될 때까지 진행한 결과로, 'priority-hold-time' 동안 R2가 Master로 동작하므로 R1이 Backup→Master로 변경되어도 문제없이 통신 가능

 

  • R1은 'priority-hold-time' 후에 Priority를 120으로 원복하였지만 아직 Backup으로 동작

 

root@R1> show vrrp detail    
Physical interface: irb, Unit: 10, Address: 10.0.0.2/24
  Index: 328, SNMP ifIndex: 537, VRRP-Traps: disabled, VRRP-Version: 2
  Interface state: up, Group: 10, State: backup, VRRP Mode: Active
  Priority: 120, Advertisement interval: 1, Authentication type: none
  Advertisement threshold: 3, Computed send rate: 0
  Preempt: yes, Accept-data mode: yes, VIP count: 1, VIP: 10.0.0.1           
  Dead timer: 0.000s, Master priority: 100, Master router: 10.0.0.3 
  Virtual router uptime: 12:02:39
  Preferred: yes 
  Tracking: enabled 
    Current priority: 120, Configured priority: 120 
    Priority hold time: 45, Not running 
    Interface tracking: enabled, Interface count: 1  
      Interface     Int state   Int speed   Incurred priority cost
      ge-0/0/0.0    up                 1g                       0
    Route tracking: disabled

 

(5) Master Device Change

  • R1은 본인보다 Priority가 낮은 VRRP Advertisement를 수신하고 Preempt 옵션이 동작하여 Master로 변경
  • PC1은 외부로 데이터 전송 시, 게이트웨이인 V-MAC을 가지고 있는 Master 장비인 R1로 전송되고 R1은 라우팅 테이블에 D-IP에 대한 정보가 있으므로 통신 가능

 

root@R1> show vrrp 
Interface     State       Group   VR state VR Mode   Timer    Type   Address
irb.10        up             10   master   Active      A  0.201 lcl    10.0.0.2       
                                                                vip    10.0.0.1
root@R1> show vrrp detail 
Physical interface: irb, Unit: 10, Address: 10.0.0.2/24
  Index: 328, SNMP ifIndex: 537, VRRP-Traps: disabled, VRRP-Version: 2
  Interface state: up, Group: 10, State: master, VRRP Mode: Active
  Priority: 120, Advertisement interval: 1, Authentication type: none
  Advertisement threshold: 3, Computed send rate: 0
  Preempt: yes, Accept-data mode: yes, VIP count: 1, VIP: 10.0.0.1           
  Advertisement Timer: 0.502s, Master router: 10.0.0.2
  Virtual router uptime: 01:19:55, Master router uptime: 00:01:27
  Virtual Mac: 00:00:5e:00:01:0a
  Preferred: yes 
  Tracking: enabled 
    Current priority: 120, Configured priority: 120 
    Priority hold time: 45, Not running 
    Interface tracking: enabled, Interface count: 1  
      Interface     Int state   Int speed   Incurred priority cost
      ge-0/0/0.0    up                 1g                       0
    Route tracking: disabled
  • Interface Track이 동작하여 Priority를 120으로 원복하였으며 Backup으로 동작 중이었던 R1은 Master로 동작

 

Oct  4 09:01:09  R1 mib2d[5931]: SNMP_TRAP_LINK_UP: ifIndex 526, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/0/0
Oct  4 09:01:55  R1 vrrpd[16092]: VRRPD_NEW_MASTER: Interface irb.10 (local address 10.0.0.2) became VRRP master for group 10 with master reason priority
  • R1은 로그 확인 결과 설정한 'priority-hold-time'과 비슷한 45s 후에 Backup→Master로 변경

 

저작자표시 비영리 변경금지 (새창열림)

'Network > VRRP' 카테고리의 다른 글

VRRP with RPM and Event-option Configuration(Juniper vMX)  (0) 2025.03.18
VRRP Load Balancing Configuration(Juniper vMX)  (0) 2025.03.16
VRRP Basic Configuration(Juniper vMX)  (0) 2025.03.14
VRRP Route Track 동작 과정  (0) 2025.03.12
VRRP Preempt Hold-Time(Delay) 동작 과정  (0) 2025.03.06
VRRP Preempt 동작 과정  (0) 2025.03.04
VRRP 동작 과정  (0) 2025.03.02
VRRP Header  (0) 2025.02.28
'Network/VRRP' 카테고리의 다른 글
  • VRRP Basic Configuration(Juniper vMX)
  • VRRP Route Track 동작 과정
  • VRRP Preempt Hold-Time(Delay) 동작 과정
  • VRRP Preempt 동작 과정
ant-choi의 네트워크
ant-choi의 네트워크
안녕하세요. 네트워크 엔지니어로 근무하고 있는 직장인 입니다. 2024.08.26부터 새로운 버전으로 블로그를 개설하였습니다. 제가 스터디한 내용이나 회사에서 업무 진행 시, 필요한 내용들을 정리하여 업로드 하는 것을 목표로 하고 있습니다. 오류가 있거나 피드백이 있으신 분들은 댓글 남겨주시면 감사하겟습니다.
  • ant-choi의 네트워크
    ant-choi의 네트워크
    ant-choi의 네트워크
  • 전체
    오늘
    어제
    • 분류 전체보기 (158) N
      • Network (141) N
        • Juniper Software (0)
        • Juniper Basic (7)
        • Emulator (24)
        • Network Basic (11)
        • ARP, ICMP (15)
        • VLAN (22)
        • STP (0)
        • VRRP (11)
        • Link Aggregation (10)
        • MC-LAG (11) N
        • Switching, Routing Basic (15)
        • DHCP (15)
        • OSPF (0)
        • BGP (0)
        • Routing Instance (0)
        • VXLAN (0)
        • EVPN-VXLAN (0)
        • Issue (0)
      • Office (5)
        • Office 공통 (1)
        • Excel (1)
        • Power Point (1)
        • Word (2)
        • Outlook (0)
      • 기타 (12)
        • Windows (1)
        • Browser (4)
        • Tistory (7)
        • Notion (0)
        • Application (0)
  • 블로그 메뉴

    • hELLO· Designed By정상우.v4.10.3
    ant-choi의 네트워크
    VRRP Interface Track 동작 과정
    상단으로

    티스토리툴바