“CCIE”的版本间的差异

来自qingwei personal wiki
跳转至: 导航搜索
(创建页面,内容为“== eigrp 认证 == authentication mode hmac-sha-256 ccie key chain不同? eigrp 认证 authentication mode hmac-sha-256 ccie key chain不同? 命名基…”)
 
 
第23行: 第23行:
  
 
copy running-config startup-config
 
copy running-config startup-config
 +
== BGP ==
 +
R11#sh ip bgp 10.2.0.0/16
 +
BGP routing table entry for 10.2.0.0/16, version 67
 +
Paths: (2 available, best #1, table default)
 +
Flag: 0x820
 +
  Advertised to update-groups: (Pending Update Generation)
 +
    2
 +
  Refresh Epoch 1
 +
  65001 65001, (aggregated by 65002 10.255.1.15)
 +
    10.254.0.53 from 10.254.0.53 (10.255.1.7)
 +
      Origin IGP, localpref 100, valid, external, atomic-aggregate, best
 +
      rx pathid: 0, tx pathid: 0x0
 +
  Refresh Epoch 1
 +
  65001 65001, (aggregated by 65002 10.255.1.15)
 +
    10.255.1.12 (metric 11) from 10.255.1.12 (10.255.1.12)
 +
      Origin IGP, metric 0, localpref 100, valid, internal, atomic-aggregate
 +
      rx pathid: 0, tx pathid: 0
 +
R11#sh ip bgp 10.2.0.0/16
 +
BGP routing table entry for 10.2.0.0/16, version 67
 +
Paths: (2 available, best #1, table default)
 +
Flag: 0x820
 +
  Advertised to update-groups: (Pending Update Generation)
 +
    2
 +
  Refresh Epoch 1
 +
  65001 65001, (aggregated by 65002 10.255.1.15)
 +
    10.254.0.53 from 10.254.0.53 (10.255.1.7)
 +
      Origin IGP, localpref 100, valid, external, atomic-aggregate, best
 +
      rx pathid: 0, tx pathid: 0x0
 +
  Refresh Epoch 1
 +
  65001 65001, (aggregated by 65002 10.255.1.15)
 +
    10.255.1.12 (metric 11) from 10.255.1.12 (10.255.1.12)
 +
      Origin IGP, metric 0, localpref 100, valid, internal, atomic-aggregate
 +
      rx pathid: 0, tx pathid: 0
 +
 +
 +
Origin IGP----------通过network宣告的
 +
Origin Incomplete---------重分发进BGP得到的路由

2018年1月15日 (一) 07:38的最新版本

eigrp 认证

authentication mode hmac-sha-256 ccie key chain不同?

eigrp 认证 authentication mode hmac-sha-256 ccie key chain不同? 命名基本配置address-family 什么情况用

DMVPN R18 D 10.2.19.0/24 [90/3097600] via 123.20.1.25, 00:00:26, Tunnel0 123.20.1.25 为什么不是123.20.1.27

水平分割的原理是 从这个端口学到的 路由条目 不再出这个端口发送出去-----防止环路 路由反射----------IBGP不许full mesh

路由策略实施后为什么R3没有123.0.0.0/8 le32的路由

没理解下面的要求 all ip add used for ebgp peering must pass the bgp's directly connected check l no bgp speaker is AS 12345 may use the network or redistribute startement under any address-family of the bgp router config

ip pim sparse-mode作用是什么


copy running-config startup-config

BGP

R11#sh ip bgp 10.2.0.0/16 BGP routing table entry for 10.2.0.0/16, version 67 Paths: (2 available, best #1, table default) Flag: 0x820

 Advertised to update-groups: (Pending Update Generation)
    2
 Refresh Epoch 1
 65001 65001, (aggregated by 65002 10.255.1.15)
   10.254.0.53 from 10.254.0.53 (10.255.1.7)
     Origin IGP, localpref 100, valid, external, atomic-aggregate, best
     rx pathid: 0, tx pathid: 0x0
 Refresh Epoch 1
 65001 65001, (aggregated by 65002 10.255.1.15)
   10.255.1.12 (metric 11) from 10.255.1.12 (10.255.1.12)
     Origin IGP, metric 0, localpref 100, valid, internal, atomic-aggregate
     rx pathid: 0, tx pathid: 0

R11#sh ip bgp 10.2.0.0/16 BGP routing table entry for 10.2.0.0/16, version 67 Paths: (2 available, best #1, table default) Flag: 0x820

 Advertised to update-groups: (Pending Update Generation)
    2
 Refresh Epoch 1
 65001 65001, (aggregated by 65002 10.255.1.15)
   10.254.0.53 from 10.254.0.53 (10.255.1.7)
     Origin IGP, localpref 100, valid, external, atomic-aggregate, best
     rx pathid: 0, tx pathid: 0x0
 Refresh Epoch 1
 65001 65001, (aggregated by 65002 10.255.1.15)
   10.255.1.12 (metric 11) from 10.255.1.12 (10.255.1.12)
     Origin IGP, metric 0, localpref 100, valid, internal, atomic-aggregate
     rx pathid: 0, tx pathid: 0


Origin IGP----------通过network宣告的 Origin Incomplete---------重分发进BGP得到的路由