[GTER] O que pode estar ocasionando isso? (BGP4)

Antonio Carlos Pina apina at infolink.com.br
Thu Jun 2 14:41:21 -03 2005


De uma máquina Windows debaixo do Velox (RJ) está bastante acessível:

C:\Documents and Settings\pina>tracert 200.163.207.253

Tracing route to BrT-L1-ctameborder.brasiltelecom.net.br [200.163.207.253]
over a maximum of 30 hops:

  1    40 ms    30 ms    30 ms  200217050254.user.veloxzone.com.br
[200.217.50.2
54]
  2    30 ms    40 ms    30 ms  200.195.51.133
  3    30 ms    30 ms    30 ms  PO6-0.ARC-RJ-ROTN-01.telemar.net.br
[200.223.131
.137]
  4    30 ms    30 ms    40 ms  200.223.131.210
  5    30 ms    40 ms    40 ms  200.223.254.141
  6    50 ms    50 ms    50 ms  BrT-L1-ctameborder.brasiltelecom.net.br
[200.163
.207.253]

Trace complete.

C:\Documents and Settings\pina>


Já vi isso ocorrer em casos de interface DOWN ou processo BGP derrubado. Ou
ainda quando os keepalives não estão seguindo normalmente.

Grato,
Pina

----- Original Message ----- 
From: "Marcus Grando" <marcus at sbh.eng.br>
To: "Grupo de Trabalho de Engenharia e Operacao de Redes"
<gter at eng.registro.br>
Sent: Thursday, June 02, 2005 2:31 PM
Subject: [GTER] O que pode estar ocasionando isso? (BGP4)


> Pessoal,
>
> O que pode estar ocasionando isso: "200.163.207.253 (inaccessible)"? Sem
> anuncio? filtro? erro de conf? alguem tem uma luz?
>
> Abraços
>
> route-server>sh ip bgp 200.203.128.0/17
> BGP routing table entry for 200.203.128.0/17, version 2766045299
> Paths: (7 available, no best path)
> Flag: 0x208
>    Not advertised to any peer
>    8167, (received & used)
>      200.163.207.253 (inaccessible) from 64.200.103.9 (64.200.103.9)
>        Origin IGP, metric 0, localpref 120, valid, internal
>        Community: 7911:777 7911:7707
>        Originator: 64.200.87.2, Cluster list: 64.200.103.9,
> 64.200.103.242, 64.200.87.3
>    8167
>      200.163.207.253 (inaccessible) from 64.200.135.4 (64.200.135.4)
>        Origin IGP, localpref 100, valid, internal
>        Community: 7911:777 7911:7707
>        Originator: 64.200.87.2, Cluster list: 64.200.135.4,
> 64.200.135.8, 64.200.87.3
>    8167
>      200.163.207.253 (inaccessible) from 64.200.127.10 (64.200.127.10)
>        Origin IGP, localpref 100, valid, internal
>        Community: 7911:777 7911:7707
>        Originator: 64.200.87.2, Cluster list: 64.200.127.10,
> 64.200.127.3, 64.200.87.3
>    8167
>      200.163.207.253 (inaccessible) from 64.200.110.5 (64.200.110.5)
>        Origin IGP, localpref 100, valid, internal
>        Community: 7911:777 7911:7707
>        Originator: 64.200.87.2, Cluster list: 64.200.110.5,
> 64.200.110.3, 64.200.87.3
>    8167
>      200.163.207.253 (inaccessible) from 64.200.141.6 (64.200.141.6)
>        Origin IGP, localpref 100, valid, internal
>        Community: 7911:777 7911:7707
>        Originator: 64.200.87.2, Cluster list: 64.200.141.6,
> 64.200.143.3, 64.200.87.3
>    8167
>      200.163.207.253 (inaccessible) from 64.200.151.7 (64.200.151.7)
>        Origin IGP, localpref 100, valid, internal
>        Community: 7911:777 7911:7707
>        Originator: 64.200.87.2, Cluster list: 64.200.151.7,
> 64.200.151.1, 64.200.87.3
>    8167
>      200.163.207.253 (inaccessible) from 64.200.103.8 (64.200.103.8)
>        Origin IGP, localpref 100, valid, internal
>        Community: 7911:777 7911:7707
>        Originator: 64.200.87.2, Cluster list: 64.200.103.8,
> 64.200.103.242, 64.200.87.3
>
> -- 
> Marcus Grando
> marcus(at)sbh.eng.br
> --
> gter list    https://eng.registro.br/mailman/listinfo/gter
>




More information about the gter mailing list