Escolar Documentos
Profissional Documentos
Cultura Documentos
O Hot Standby Router Protocol (HSRP) é um protocolo da Cisco que, conforme detalhado no RFC 2281, permite que
vários gateways clientes sejam configurados como um roteador "virtual". Este roteador "virtual" é configurado com
um único endereço IP que é compartilhado entre o grupo junto com um endereço MAC virtual. A ideia por trás disso é,
claro, que o cliente veja seu único gateway, mesmo que esse gateway falhe. O HSRP elege um roteador ativo que
encaminha os pacotes IP do cliente. Um roteador de backup ou de espera pode ser configurado para assumir o
encaminhamento de pacotes caso o roteador ativo falhe. Para rastrear um ao outro, o HSRP usa multicast para enviar
suas atualizações e hellos do HSRP.
NOTA: O valor de prioridade pode ser de 1 a 255.o padrão é 100. Uma prioridade maior resultará nesse roteador
sendo eleito o roteador ativo. Se as prioridades
de todos os roteadores no grupo são iguais, o roteador com endereço IP mais alto se torna o roteador ativo
Active -ro u ter
HSRP_CISCO P rio rity 1 0 1
1 9 2 .1 6 8 .4 0 .5 / 2 4 1 9 2 .1 6 8 .4 0 .3 / 2 4
Ospf are a 0
eth0/0 fast0/0
eth0/3
fast0/1
R5 Vlan 40 R3 14
1 7 2 .4 0 .0 .1 2 / 3 0 Ospf 1 0 0
eth0/2 eth0/1 Lo 0 -1 7 2 .4 0 .0 .3 / 3 2
fast0/1 1 7 2 .4 0 .0 .8 / 3 0
13 9
10
Vlan 40 1 9 2 .1 6 8 .4 0 .0 / 2 4 R2
1 7 fast1/0 R1
Vi rtu a l-ga te w a y- fast0/0 fast0/0
1 9 2 .1 6 8 .4 0 .1 Lo 0 -1 7 2 .4 0 .0 .2 / 3 2
Lo 0 -1 7 2 .4 0 .0 .1 / 3 2
eth0/2 eth0/1 Lo 1 -1 9 2 .1 6 8 .5 0 .1 / 2 4
1 7 2 .4 0 .0 .1 6 / 3 0
18
eth0/0 fast0/0
eth0/3 fast0/1
R6 1 9 2 .1 6 8 .4 0 .4 / 2 4 R4
1 9 2 .1 6 8 .4 0 .6 / 2 4
Vlan 40
Lo 0 -1 7 2 .4 0 .0 .4 / 3 2
Sta ndby-ro u ter
P rio rity 1 0 0
Dada a topologia acima configurar HSRP de forma que os roteadores R5 e R6 tenham accesso a loopback 1 do
roteador R1 ainda que o roteador R3 e ou R4 cair. O roteador R3 devera estar no modo active e o roteador R4 no
modo standby. Os switches deveram fazer etherchannel nas suas interfaces e0/1-2 passando a vlan 40 como vlan de
interligação.
O roteadores R5-R6 serão usados para semular hosts finais e deverão apontar a routas default estatica ao IP virtual
do HSRP.
Para teste deveremos apos a configuração e teste desligar as interfaces do roteador R3 e analisar o comportamento
do trafego dentro da topologia.
R1_CONFIG
interface Loopback0
ip address 172.40.0.1 255.255.255.255
!
interface Loopback1
ip address 192.168.50.1 255.255.255.0
!
interface FastEthernet0/0
ip address 172.40.0.9 255.255.255.252
duplex auto
speed auto
!
!
router ospf 100
router-id 172.40.0.1
log-adjacency-changes
network 172.40.0.1 0.0.0.0 area 0
network 172.40.0.9 0.0.0.0 area 0
network 192.168.50.1 0.0.0.0 area 0
R2_CONF router ospf 100
router-id 172.40.0.2
interface Loopback0 log-adjacency-changes
ip address 172.40.0.2 255.255.255.255 network 172.40.0.2 0.0.0.0 area 0
! network 172.40.0.10 0.0.0.0 area 0
interface FastEthernet0/0 network 172.40.0.13 0.0.0.0 area 0
ip address 172.40.0.10 255.255.255.252 network 172.40.0.17 0.0.0.0 area 0
duplex auto
speed auto
!
interface FastEthernet0/1
ip address 172.40.0.13 255.255.255.252
duplex auto
speed auto
!
interface FastEthernet1/0
ip address 172.40.0.17 255.255.255.252
duplex auto
speed auto
R3_CONFIG router ospf 100
router-id 172.40.0.3
interface Loopback0 log-adjacency-changes
ip address 172.40.0.3 255.255.255.255 network 172.40.0.3 0.0.0.0 area 0
! network 172.40.0.14 0.0.0.0 area 0
interface FastEthernet0/0 network 192.168.40.1 0.0.0.0 area 0
ip address 192.168.40.3 255.255.255.0 network 192.168.40.3 0.0.0.0 area 0
duplex auto
speed auto
standby 1 ip 192.168.40.1
standby 1 priority 101
standby 1 preempt
!
interface FastEthernet0/1
ip address 172.40.0.14 255.255.255.252
duplex auto
speed auto
!
Configuração do HSRP no roteador R3
R3(config-if)#standby 1 ?
authentication Authentication
follow Name of HSRP group to follow
ip Enable HSRP IPv4 and set the virtual IP address
ipv6 Enable HSRP IPv6
mac-address Virtual MAC address
name Redundancy name string
preempt Overthrow lower priority Active routers
priority Priority level
timers Hello and hold timers
track Priority tracking
R3(config-if)#standby 1 ip 192.168.40.1
R3(config-if)#standby 1 priority 101
R3(config-if)#standby 1 preempt
R3(config-if)#
*Mar 1 01:12:58.443: %HSRP-5-STATECHANGE: FastEthernet0/0 Grp 1 state Standby -> Active
R3_CONFIG
interface Loopback0
ip address 172.40.0.4 255.255.255.255
!
interface FastEthernet0/0
ip address 192.168.40.4 255.255.255.0
duplex auto
speed auto
standby 1 ip 192.168.40.1
standby 1 preempt
!
interface FastEthernet0/1
ip address 172.40.0.18 255.255.255.252
speed 100
full-duplex
!
router ospf 100
router-id 172.40.0.4
log-adjacency-changes
network 172.40.0.4 0.0.0.0 area 0
network 172.40.0.18 0.0.0.0 area 0
network 192.168.40.1 0.0.0.0 area 0
network 192.168.40.4 0.0.0.0 area 0
Configuração do HSRP no roteador R4
interface FastEthernet0/0
ip address 192.168.40.5 255.255.255.0
duplex auto
speed auto
!
!
ip route 0.0.0.0 0.0.0.0 192.168.40.1
CONFIGURAÇÃO R6
interface FastEthernet0/0
ip address 192.168.40.6 255.255.255.0
duplex auto
speed auto
!
!
ip route 0.0.0.0 0.0.0.0 192.168.40.1
BATERIA DE TESTES R5#traceroute 192.168.50.1
R3(config-if)#shutdown
R1#ping 192.168.40.5
É provável que, se você tiver um ambiente de vários fornecedores e desejar os mesmos benefícios do HSRP, configure o
VRRP (Virtual Router Redundancy Protocol), protocolo de redundância de roteador virtual) para fazer isso. O VRRP,
detalhado no RFC 3768, opera da mesma maneira que o HSRP, elegendo um roteador Ativo chamado de Mestre entre
um grupo de roteadores e permitindo que ele seja o "detentor" de um IP e MAC virtual. Assim como no HSRP, uma
falha acionaria o roteador em espera (backup) para então se tornar o mestre e, subsequentemente, encaminhar o
tráfego do cliente. O VRRP também usa multicast para o seu mecanismo de hello e eleições, mas ao contrário do HSRP
* que usa 224.0.0.2 (esta sub-rede) o VRRP usa o 224.0.0.18.
Dada a topologia abaixo configurar o vrrp de forma que o roteador R3 torna-se o master de forma que
o trafego entre a rede 192.168.40.0/24 flua no sentido R3-R2-R1 e ou R1-R2-R3-R5-6
em caso o roteador R3 estar fora de serviço o trafego devera fluir no sentido inverso.
R4-R2-R1 e ou R1-R2-R4-R5-6
1 9 2 .1 6 8 .4 0 .5 / 2 4 1 9 2 .1 6 8 .4 0 .3 / 2 4
Ospf are a 0
eth0/0 fast0/0
eth0/3 R3 fast0/1
R5 Vlan 40 14
1 7 2 .4 0 .0 .1 2 / 3 0
eth0/2 eth0/1 Lo 0 -1 7 2 .4 0 .0 .3 / 3 2
fast0/1 1 7 2 .4 0 .0 .8 / 3 0
13 9
10
Vlan 40 1 9 2 .1 6 8 .4 0 .0 / 2 4 R2
1 7 fast1/0 R1
Vi rtu a l-ga te w a y- fast0/0 fast0/0
1 9 2 .1 6 8 .4 0 .1 Lo 0 -1 7 2 .4 0 .0 .2 / 3 2
Lo 0 -1 7 2 .4 0 .0 .1 / 3 2
eth0/2 eth0/1 Lo 1 -1 9 2 .1 6 8 .5 0 .1 / 2 4
1 7 2 .4 0 .0 .1 6 / 3 0
18
eth0/0 fast0/0
R4 fast0/1
R6 eth0/3 1 9 2 .1 6 8 .4 0 .4 / 2 4
1 9 2 .1 6 8 .4 0 .6 / 2 4
Vlan 40
Lo 0 -1 7 2 .4 0 .0 .4 / 3 2
Sta ndby-ro u ter
P rio rity 1 0 0
R3_CONFIG
set interfaces ge-0/0/0 unit 0 family inet address 192.168.40.3/24 vrrp-group 1 virtual-address 192.168.40.1
set interfaces ge-0/0/0 unit 0 family inet address 192.168.40.3/24 vrrp-group 1 priority 101
set interfaces ge-0/0/0 unit 0 family inet address 192.168.40.3/24 vrrp-group 1 preempt
set interfaces ge-0/0/1 unit 0 family inet address 172.40.0.14/30
set policy-options policy-statement VRRP_OSPF term accept_ospf from route-filter 172.40.0.3/32 exact
set policy-options policy-statement VRRP_OSPF term accept_ospf from route-filter 172.40.0.14/32 exact
set policy-options policy-statement VRRP_OSPF term accept_ospf from route-filter 192.168.40.3/32 exact
set policy-options policy-statement VRRP_OSPF term accept_ospf from route-filter 192.168.40.1/32 exact
set policy-options policy-statement VRRP_OSPF term accept_ospf then accept
}
root@R3# run show configuration }
}
interfaces { protocols {
ge-0/0/0 { ospf {
unit 0 { export VRRP_OSPF;
family inet { area 0.0.0.0 {
address 192.168.40.3/24 { interface ge-0/0/1.0;
vrrp-group 1 { interface ge-0/0/0.0;
virtual-address 192.168.40.1; }
priority 101; }
preempt; }
} policy-options {
} policy-statement VRRP_OSPF {
} term accept_ospf {
} from {
} route-filter 172.40.0.3/32 exact;
ge-0/0/1 { route-filter 172.40.0.14/32 exact;
unit 0 { route-filter 192.168.40.3/32 exact;
family inet { route-filter 192.168.40.1/32 exact;
address 172.40.0.14/30; }
} then accept;
R4_CONFIG
set interfaces ge-0/0/0 unit 0 family inet address 192.168.40.4/24 vrrp-group 1 virtual-address 192.168.40.1
set interfaces ge-0/0/0 unit 0 family inet address 192.168.40.4/24 vrrp-group 1 priority 100
set interfaces ge-0/0/0 unit 0 family inet address 192.168.40.4/24 vrrp-group 1 preempt
set interfaces ge-0/0/1 unit 0 family inet address 172.40.0.18/30
set policy-options policy-statement VRRP_OSPF term accept_ospf from route-filter 172.40.0.4/32 exact
set policy-options policy-statement VRRP_OSPF term accept_ospf from route-filter 172.40.0.18/32 exact
set policy-options policy-statement VRRP_OSPF term accept_ospf from route-filter 192.168.40.4/32 exact
set policy-options policy-statement VRRP_OSPF term accept_ospf from route-filter 192.168.40.1/32 exact
set policy-options policy-statement VRRP_OSPF term accept_ospf then accept
protocols {
ospf {
export VRRP_OSPF;
root@R4# run show configuration area 0.0.0.0 {
} interface ge-0/0/1.0;
} interface ge-0/0/0.0;
} }
interfaces { }
ge-0/0/0 { }
unit 0 { policy-options {
family inet { policy-statement VRRP_OSPF {
address 192.168.40.4/24 { term accept_ospf {
vrrp-group 1 { from {
virtual-address 192.168.40.1; route-filter 172.40.0.4/32 exact;
priority 100; route-filter 172.40.0.18/32 exact;
preempt; route-filter 192.168.40.4/32 exact;
} route-filter 192.168.40.1/32 exact;
} }
} then accept;
ge-0/0/1 { }
unit 0 { }
family inet {
address 172.40.0.18/30
Teste efectuado no equipamento R3
root@R3> show vrrp ?
Possible completions:
<[Enter]> Execute this command
brief Display brief output (default)
detail Display detailed output
extensive Display extensive output
interface Show VRRP interface
logical-system Name of logical system
nsr Display VRRP state of Master RE.
summary Display summary output
track Show VRRP track interfaces
| Pipe through a command
Nota: Podemos notar que apartir do comando acima que o roteador R4 e o backup do protocolo vrrp visto que o
mesmo foi configurado com uma prioridade inferior ao do roteador R3. partir de R6 poderemos ver que trafego
passara pelo R3 para chegar a loopback1 do roteador R1
Teste a apartir do roteador R5
R5#ping 192.168.50.1
R5#traceroute 192.168.50.1
R6#ping 192.168.40.1
R6#traceroute 192.168.50.1
Teste apartir de R5
R5#traceroute 192.168.50.1
1 9 2 .1 6 8 .4 0 .5 / 2 4 1 9 2 .1 6 8 .4 0 .3 / 2 4
gig0/0/0 Ospf are a 0
gig0/0/4 gig0/0/1 gig0/0/0
gig0/0/1
R5
R5 Vlan 40 R3 14
1 7 2 .4 0 .0 .1 2 / 3 0
gig0/0/2 Lo 0 -1 7 2 .4 0 .0 .3 / 3 2
gig0/0/3 gig0/0/1 1 7 2 .4 0 .0 .8 / 3 0
13 9
10
Vlan 40 1 9 2 .1 6 8 .4 0 .0 / 2 4
17 gig0/0/0 R1
Vi rtu a l-ga te w a y- Gig0/0/2 R2 gig0/0/0 R1
1 9 2 .1 6 8 .4 0 .1 Lo 0 -1 7 2 .4 0 .0 .2 / 3 2
gig0/0/2 Lo 0 -1 7 2 .4 0 .0 .1 / 3 2
gig0/0/3 1 7 2 .4 0 .0 .1 6 / 3 0 Lo 1 -1 9 2 .1 6 8 .5 0 .1 / 2 4
gig0/0/0 18
gig0/0/1 gig0/0/0
gig0/0/4
R6 R4 gig0/0/2
R6 1 9 2 .1 6 8 .4 0 .4 / 2 4
1 9 2 .1 6 8 .4 0 .6 / 2 4
Vlan 40
Lo 0 -1 7 2 .4 0 .0 .4 / 3 2
Sta ndby-ro u ter
P rio rity 1 0 0
Dada a topologia acima configurar o vrrp de forma que roteador R3 torna-se o master e o roteador R4 backup,
configurar eth-trunk entre o sw_fcoc1 e sw_fcoc2 nas interfaces ge-0/0/2-3, usar a vlan 40 para a comunicação
entre R3-R4 e os roteadores R5-R6.Usar a prioridade de 120, os testes deveram ser efetuado de forma que os
roteadores R5-R6 conseguem chegar na interface loopback1 do roteador R1, apois o roteador R3 torna-se o
master o trafego devera fluir no sentido R3------->R2---------->R1.
R1_CONFIG
interface GigabitEthernet0/0/0
ip address 172.40.0.9 255.255.255.252
#
interface LoopBack0
ip address 172.40.0.1 255.255.255.255
#
interface LoopBack1
ip address 192.168.50.1 255.255.255.0
[R2]interface LoopBack 0
[R2-LoopBack0]ip address 172.40.0.2 255.255.255.255
[R3]interface LoopBack 0
[R3-LoopBack0]ip address 172.40.0.3 255.255.255.255
[R4]interface LoopBack 0
[R4-LoopBack0]ip address 172.40.0.4 255.255.255.255
[R4-LoopBack0]
[SW_FCOC1]vlan 40
[SW_FCOC1-vlan40]
[SW_FCOC1]interface Eth-Trunk 40
[SW_FCOC1-Eth-Trunk40]port link-type trunk
[SW_FCOC1-Eth-Trunk40]port trunk allow-pass vlan 40
[SW_FCOC2]interface Eth-Trunk 40
[SW_FCOC2-Eth-Trunk40]port link-type trunk
[SW_FCOC2-Eth-Trunk40]port trunk allow-pass vlan 40
interface GigabitEthernet0/0/0
ip address 192.168.40.5 255.255.255.0
#
ip route-static 0.0.0.0 0.0.0.0 192.168.40.1
##################################################
R6_CONFIG
##################################################
1 192.168.40.3 60 ms 60 ms 80 ms
2 172.40.0.13 80 ms 60 ms 70 ms
3 172.40.0.9 90 ms 110 ms 90 ms
Teste efectuado apartir do roteador R4-R6
<R4>display vrrp
GigabitEthernet0/0/0 | Virtual Router 40
State : Backup
Virtual IP : 192.168.40.1
Master IP : 192.168.40.3
PriorityRun : 100
PriorityConfig : 100
MasterPriority : 120
Preempt : YES Delay Time : 0 s
TimerRun : 1 s
TimerConfig : 1 s
Auth type : NONE
Virtual MAC : 0000-5e00-0128
Check TTL : YES
Config type : normal-vrrp
Create time : 2019-03-02 22:48:53 UTC-08:00
Last change time : 2019-03-02 22:48:53 UTC-08:00
<R4>display vrrp
GigabitEthernet0/0/0 | Virtual Router 40
State : Master
Virtual IP : 192.168.40.1
Master IP : 192.168.40.4
PriorityRun : 100
PriorityConfig : 100
MasterPriority : 100
Preempt : YES Delay Time : 0 s
TimerRun : 1 s
TimerConfig : 1 s
Auth type : NONE
Virtual MAC : 0000-5e00-0128
Check TTL : YES
Config type : normal-vrrp
Create time : 2019-03-02 22:48:53 UTC-08:00
Last change time : 2019-03-03 09:40:38 UTC-08:00
Testes efectuados em R5 e R6 apois R4 tornar-se o Master
R5_TEST
<R5>ping 192.168.50.1
<R5>tracert 192.168.50.1
1 192.168.40.4 60 ms 90 ms 80 ms