BGP

Similar Questions

• A protocol that would provide the service for IPv4 and IPv6 traffic? (RIPv1, RIPv2, RIPng, BGP)

  A protocol that would provide the service for IPv4 and IPv6 traffic?

  • RIPv1
  • RIPv2
  • RIPng
  • BGP

  Hi SandeepTandel,

  ·         Your computer is on a domain network?

  ·         What exactly is the question do you face?

  Here the following protocols provide for IPv4 and IPv6 traffic or respectively:

  Ø Bng supports IPv4 and IPv6 protocols

  Ø RIPng supports IPv6

  Ø RIPv1 and RIPv2 supports IPv4

  Let us know if this information useful.

• Questions about N3024 switch by default - originate BGP

  Here is the configuration of the two switches.  I set up and rising BGP, passing of prefixes.  I want 1 switch to send a default gateway to switch 2 and have the default installation of command on the next statement are created.  I don't see the 0.0.0.0 route by default in the show ip bgp sum command, but which is detailed in the configuration guide.  However, I don't see a default route 0.0.0.0 in the routing table for switch 2 at all and an error message that there is no default route available.  Would I be missing here?

  Config is below:

  SWITCH 1

   

   

   

   

  Configure

  VLAN 50

  output

  VLAN 50

  name "switchtest".

  output

  hostname "Switch_1.

  location 1/0 1! Dell network N3024

  battery

  1 1 member! N3024

  output

  IP routing

  !

  loopback interface 1

  IP 10.0.0.1 address 255.255.255.255

  IP ospf area 0

  output

  interface vlan 1

  DHCP IP address

  output

  interface vlan 50

  172.16.0.1 IP address 255.255.255.252

  IP ospf area 0

  output

  router ospf

  router ID 10.0.0.1

  10.0.0.1 network 255.255.255.255 area 0

  network 172.16.0.0 255.255.255.252 area 0

  output

  !

  item in gi1/0/1 interface

  Description 'Switch '.

  switchport access vlan 50

  output

  Server SNMP engineid local 800002a203f8b1566f36c4

  router bgp 65001

  router BGP 10.0.0.1 ID

  172.168.0.0 netmask 255.255.255.252

  10.0.0.1 netmask 255.255.255.255

  172.16.0.2 neighbor remote - as 65002

  neighbor 172.16.0.2 are created by default

  output

  output

  Switch_1 #show ip bgp

  BGP table version is 7, local router ID is 10.0.0.1

  Status codes: s removed, * valid, > best, i - internal

  Source codes: i - IGP, e - EGP? -incomplete

  Network Next Hop metric LocPref path origin

  ------------------- ---------------- ---------- ---------- ------------- ------

  * > 172.16.0.0/30 172.16.0.2 1 100 65002 I

  * > 192.168.100.0/30 172.16.0.2 1 100 65002 I

  * > I have 10.0.0.1/32 0.0.0.0 1 100 I

  * > 10.0.0.2/32 172.16.0.2 1 100 65002 I

  Switch_1 #show ip bgp sum

  IPv4 routing... Enable

  BGP Admin Mode... Enable

  BGP router ID... 10.0.0.1

  Local AS number... 65001

  Traps ......................................... Disable

  Maximum paths... 1

  Maximum paths IBGP... 1

  Default Keep Alive Time... 30

  Default hold time... 90

  Number of entries of network... 4

  Number of PATHS... 1

  Default metric... Not configured

  Advertise default route... NO.

  Redistribution:

  Dist metric list of source route map

  --------- ---------- -------------------------------- --------------------------------

  Neighbor ASN MsgRcvd MsgSent State down time Pfx Rcvd

  ---------------- ----- -------- -------- ------------- -------------- ---------

  172.16.0.2 65002 78 82 ESTABLISHED 0:00:23:24 3

  Switch_1 #show ip route

  The traffic code: R - RIP derived, O - OSPF derived, C - connected, S - static

  B - Derived E - from outside, AI - BGP OSPF Inter zone

  E1 - OSPF external Type 1, E2 - OSPF external Type 2

  N1 - OSPF NSSA external Type 1, N2 - OSPF NSSA external Type 2

  S U - unnumbered Peer, L - flight road

  * Indicates the best route (the lowest metric) for the subnet.

  No default gateway is configured.

  *10.0.0.1/32 C [0/1] directly connected, Lo1

  B *10.0.0.2/32 [20/1] via 172.16.0.2, Vl50

  10.0.0.2/32 [110/11] via 172.16.0.2, Vl50

  *172.16.0.0/30 C [0/1] directly connected, Vl50

  B 172.16.0.0/30 [20/1] via 172.16.0.2, Vl50

  B *192.168.100.0/30 [20/1] via 172.16.0.2, Vl50

  192.168.100.0/30 [110/20] through 172.16.0.2, Vl50

  SWITCH 2

  Configure

  VLAN 50 100

  output

  VLAN 50

  name "SwitchTest".

  output

  VLAN 100

  name of the 'Switch '.

  output

  hostname "Switch_2".

  location 1/0 2. Dell network N3024F

  battery

  1 2 Member! N3024F

  output

  IP routing

  !

  loopback interface 0

  output

  !

  loopback interface 1

  10.0.0.2 IP address 255.255.255.255

  output

  interface vlan 1

  DHCP IP address

  output

  interface vlan 50

  IP 172.16.0.2 255.255.255.252

  IP ospf area 0

  output

  interface vlan 100

  IP 192.168.100.1 255.255.255.252

  output

  router ospf

  router ID 10.0.0.2

  10.0.0.2 network 255.255.255.255 area 0

  network 172.16.0.0 255.255.255.252 area 0

  network 192.168.100.0 255.255.255.252 area 0

  output

  !

  interface item in gi1/0/23

  switchport access vlan 100

  output

  !

  interface item in gi1/0/24

  Description 'Switch '.

  switchport access vlan 50

  output

  Server SNMP engineid local 800002a203f8b156530097

  router bgp 65002

  router BGP 10.0.0.2 ID

  172.16.0.0 netmask 255.255.255.252

  192.168.100.0 netmask 255.255.255.252

  10.0.0.2 netmask 255.255.255.255

  neighbor remote - as 65001 172.16.0.1

  output

  output

  Switch_2 #show ip bgp

  Version of BGP table is 9, local router ID is 10.0.0.2

  Status codes: s removed, * valid, > best, i - internal

  Source codes: i - IGP, e - EGP? -incomplete

  Network Next Hop metric LocPref path origin

  ------------------- ---------------- ---------- ---------- ------------- ------

  * > I have 172.16.0.0/30 0.0.0.0 1 100 I

  * > I have 192.168.100.0/30 0.0.0.0 1 100 I

  * > 10.0.0.1/32 172.16.0.1 1 100 65001 I

  * > I have 10.0.0.2/32 0.0.0.0 1 100 I

  Switch_2 #show ip bgp sum

  IPv4 routing... Enable

  BGP Admin Mode... Enable

  BGP router ID... 10.0.0.2

  Local AS number... 65002

  Traps ......................................... Disable

  Maximum paths... 1

  Maximum paths IBGP... 1

  Default Keep Alive Time... 30

  Default hold time... 90

  Number of entries of network... 4

  Number of PATHS... 1

  Default metric... Not configured

  Advertise default route... NO.

  Redistribution:

  Dist metric list of source route map

  --------- ---------- -------------------------------- --------------------------------

  Neighbor ASN MsgRcvd MsgSent State down time Pfx Rcvd

  ---------------- ----- -------- -------- ------------- -------------- ---------

  172.16.0.1 65001 83 82 ESTABLISHED 0:00:24:32 1

  Switch_2 #show ip route

  The traffic code: R - RIP derived, O - OSPF derived, C - connected, S - static

  B - Derived E - from outside, AI - BGP OSPF Inter zone

  E1 - OSPF external Type 1, E2 - OSPF external Type 2

  N1 - OSPF NSSA external Type 1, N2 - OSPF NSSA external Type 2

  S U - unnumbered Peer, L - flight road

  * Indicates the best route (the lowest metric) for the subnet.

  No default gateway is configured.

  B *10.0.0.1/32 [20/1] via 172.16.0.1, Vl50

  10.0.0.1/32 [110/11] via 172.16.0.1, Vl50

  *10.0.0.2/32 C [0/1] directly connected, Lo1

  *172.16.0.0/30 C [0/1] directly connected, Vl50

  *192.168.100.0/30 C [0/1] directly connected, Vl100

  Switch_2 #show ip route 0.0.0.0

  The traffic code: R - RIP derived, O - OSPF derived, C - connected, S - static

  B - Derived E - from outside, AI - BGP OSPF Inter zone

  E1 - OSPF external Type 1, E2 - OSPF external Type 2

  N1 - OSPF NSSA external Type 1, N2 - OSPF NSSA external Type 2

  S U - unnumbered Peer, L - flight road

   * Indicates the best route (the lowest metric) for the subnet.

  No default gateway is configured.

  No route found.

  Solution:

  Dell switches need to be turned on in the config.

  router bgp * AS number *.

  default-information originate always

• Stateful HA with BGP

  Hi all

  I'm new here on this forum. Please bare with me for my post :)

  I use SonicWall 3600 HA Stateful configuration. We plan to enable BGP support the requirement of our endpoint connection.

  My questions are:

  (1) when the stateful HA is activate, is sync configuration backup device BGP?

  (2) should I buy license BGP for both devices (Active/Backup)?

  (3) it is ideal to use HA Stateful configuration with BGP turned on?

  Hope someone can help me :)

  Thanks in advance,

  Joven D.

  (1) when the stateful HA is activate, is sync configuration backup device BGP?

  Yes, all Configurations that are Sync'd.

  (2) should I buy license BGP for both devices (Active/Backup)?

  # All licenses are sync'd between 2 devices, after have been related to MySonicWALL.com

  (3) it is ideal to use HA Stateful configuration with BGP turned on?

  With discussion with other technicians, BGP has no effect on your HA or Stateful setting. BGP as a protocol cannot be sync would be between 2 devices, as when the first goes down there will be a re-synchronization with remote anyway because it works ontop of a TCP connection. There are SIDES, but when Eve is activated it will always ask for the full table.

  So in short, I don't see a downside to running Stateful HA with BGP have set up on this device.

  If I find more documentation or someone else tells me otherwise I will update this thread.

  Thank you
  Ben D
  #Iwork4Dell

• Redistribution of BGP with EIGRP

  Hi all

  I'm trying to redistribute BGP, EIGRP, and vice versa. I'm succussfully EIGRP to BGP redistribution, but cannot get the EIGRP routes into BGP.

  Here is my config. Any guidance or help would be very appreciated.

  router eigrp 100
  network 10.18.72.0 0.0.0.255
  redistribute static route-map DEFAULT_ROUTE
  redistribute bgp 65535
  passive-interface default
  no passive-interface FastEthernet0/0
  !
  router bgp 65535
  bgp router-id 172.18.2.1
  bgp log-neighbor-changes
  redistribute eigrp 100 route-map EIGRP_REDISTRIBUTE
  neighbor 172.18.2.2 remote-as 65535
  neighbor 172.18.2.2 password ciscobgp
  no auto-summary
  ip access-list extended EIGRP_ROUTES_TO_BGP
  permit ip any any
  !
  !
  ip prefix-list DEFAULT seq 5 permit 0.0.0.0/0
  !
  route-map EIGRP_REDISTRIBUTE permit 20
  match ip address EIGRP_ROUTES_TO_BGP
  !
  route-map DEFAULT_ROUTE permit 10
  match ip address prefix-list DEFAULT
  

  Thanks in advance.

  Neil

  Add "internal to redistribute bgp' in your bgp process. By default, iBGP redistributed in a PGI. The reason for this is simply the amount of roads that can receive a bgp router can overload an igp very easily, if you want to filter routes during this operation.

  After adding this, disable your bgp neighbors and you should start to see roads.

  HTH,
  John

  Please note all useful messages *.

• BGP configuration

  Hi all

  Please can someone help me understand this concept...

  Let me show you the scenario

  a single MPLS of ISP connection come to my router and my router in the DMZ servers

  I have to connect to the remote server to my server DMZ

  The ISP gave me the details of BGP configure

  now what do I Route my private network for remote servers...

  I run NAT on my router to go through the ISP connection... now I can ping to the gateway of the ISP and can see all the router in table bgp #sh

  is this correct or I need to directly transfer traffic from the internal network of ISP through BGP... or

  Do I have to create Tunnels... If the Tunnels are necessary then I need to know the remote desktop

  

  Thank you very much in advance

  You have 1 site that has a circuit of mpls and the other doesn't, or go in the same provider and SPLM on both sides? If you have mpls on both sides by the same provider, it should be as easy as peering with the supplier with bgp on both sides and advertising then your internal subnets. If you have the public internet between you, you will need tunnels of lan-to-lan creat between two routers. Here is a guide to help you to do:

  http://www.Cisco.com/en/us/Tech/tk583/TK372/technologies_configuration_example09186a0080094634.shtml

  HTH,
  John

  Please note all useful messages *.

• Original Site BGP attribute

  Dear friends,

  I tried to get a good understanding of the Site of origin of BGP attribute (not so EIGRP). I understand his idea and its impact, but there is a problem that I couldn't wrap my head around yet.

  Quoting RFC 4364, Section 8:

                       We add one more restriction on the distribution of    routes from PE to CE: if a route's Site of Origin attribute    identifies a particular site, that route must never be redistributed    to any CE at that site. 

  My understanding of this statement is that a site must be identifiable by a given value of the attribute of so, or in other words, there should be a way to assign a specific value of the attribute so to the entire site. Then, knowing the value of the so for the entire site, a route once appeared on this site should never be announced to him.

  This is where my problems start. We know that there is not a strict mapping one to one between a site and a VRF. A site can consist of one or several VRF and is not actually represented by a single object in the IOS - it's rather a simple collection of VRF who share routing information in such a way that for mutual communication, the use of the vertebral column is not required. There is no representation of the site as a single object in the IOS and there is therefore no way to assign a particular site so as a whole. In addition, the attribute so is not yet configured on a basis of by-VRF, instead, it is pushed on the individual courses from USING a road map or a per neighbor configuration. What is so attribute on a given prefix from, then? I simply do not see how a whole VRF or an entire site is assigned its own value of so unique for comparison purposes, in a manner similar to the assignment of identifiers of road or road of targets based on per VRF.

  So my question is: If the attribute so is pushed on routes from one THIS and these routes are announced to an another EP on the same site, how is the EP another knows the correct value of the site of the so so that it can compare to the so on prefixed receipt and not advertise routes to the site they came from? The VRF simply "inherits" the individual itineraries so as they are received and processed by a road-map set- ting so?

  Any help and clarification is appreciated!

  Best regards

  Peter

  Hi Peter,.

  So for BGP is "related" to THAT neighbor. Thus, when a prefix must be announced to a neighbor, we check the so of the prefix with the so of the BGP neighbor. For anything else, he is bound to the interface.

  The configuration can be done in four different ways (the setting of the so and the verification of the so is related to that):

  (1) ' road-map in ' on what neighboring BGP command

  (2) directly on the order of CE BGP neighbor

  (3) plan of the site on the interface of the VRF and redistribution of the (static) IGP into BGP routes and (static), IGP point to this interface

  (4) plan of the site on the command interface and network VRF

  General principle (but you know it):

  http://www.Cisco.com/en/us/partner/docs/iOS/ios_xe/iproute_bgp/configuration/guide/irg_neighbor_soo_xe.html

  With the help of a roadmap and setting different for different prefixes from the same neighbor BGP SoO doesn't make much sense, so I guess that we were never bothered by possible nonuniqueness in the configuration when you look at what a 'site' is.

  Thank you

  Luke

• DMVPN BGP and EIGRP

  I am in the initial phase of research DMVPN.  We currently have an MPLS network running BGP.  Each site has Internet at home as well as a VPN site-to-site is built on the router and talks to an ASA when the SPLM fails.

  I want to implement DMVPN to do away with the site to site VPN and ASA.  I'm going to run EIGRP on routers to connect DMVPN.  Are there any good whitepapers on BGP as the main path and by EIGRP on the DMVPN as a backup?  Or no focus on a general config?

  Thank you

  It's really the main issue.

  With your configuration DMVPN roads will be internal EIGRP of an advertisement of 90, so your default DC prefer DMVPN on MPLS, which is exactly what you don't want.

  There are several ways around this as summarizing through DMPVN, redistribution connected on the sites of the branch in EIGRP so roads DMVPN are external as well and then changing measures etc.

  The other alternative I have ever done so it's for your information is really Cisco have what is called a solution IWAN where DMVPN is performed everywhere that is, even through the MPLS network.

  That would solve your problem of external routes internal EIGRP but IWAN vs is much more than just that, even if you do not need necessarily to implement the entire solution at a time.

  I just thought that it should be mentioned, and if you want more information on this I can direct you to the design guide.

  Jon

• IOS XR MPLS VPN L3 + BGP error message

  I use the file "iosxrv-k9-demo - 5.1.2" image on GNS3 for free practice.

  When my IOS XR with MPLS L3 VPN router and assigning an interface of IOS XR to a VRF, it gives an error:

  RP/0/0 / CPU0:Feb 19 20:16:50.182: bgp [1048]: ROUTING-BGP-3-RPC_SET_ERROR %: [22]: read all RPC operation: Table. Error: ' Subsystem (3373) "detected the status of 'fatal', 'Code (37)': pkg/bin/PMO: (PID = 663826):-traceback = b395988 b229e9c 8226a4b 8224bdc afb2e7c b22d857 8267050.

  looking for a solution.

  Hi umesh, there is a table operation handler problem that has been fixed in xr 513. When the list is empty, it returns "error", but which is not necessary to return the error, an empty list can be ok, so the sw fix that went in is to check that and return errors more detailed codes inside the s in this case table operations and PMO communition XR (which is made via RPC or remote call procedure).

  few options who may be here to try:

  -1 ignore it and continue the configuration

  -2 set all definitions of vrf first under router bgp and everywhere where necessary before you assign it to an interface

  -3 clear config, reboot, apply the new configuration step by step with the first definitions of vrf and last to apply to the interface.

  -4 Download xr513 XRv.

  see you soon

  Xander

• Numbers of BGP AFI/SAFI

  Hi guys,.

  I am currently studying for my exam 642-611 MPLS and I was wandering if someone could point me to a repository for numbers of BGP AFI/SAFI.

  Specifically, what are the numbers of the AFI for VPNv4 and VPNv6 addresses?

  Thank you

  Concerning

  Scott

  Scott,

  Here is the link to the list maintained by the Internet Assigned Numbers Authority IANA)

  Address family identifier (AFI)

  http://www.IANA.org/assignments/address-family-numbers/address-family-numbers.XHTML

  Identifier (SAFI) subsequent address family

  http://www.IANA.org/assignments/Safi-namespace

  Concerning

• Use BGP to Loopback interfaces

  Hello

  have seen it several times this loopback interfaces are used to iBGP routers to connect nearby instead of direct physical interface.

  Is this done bacuase Loopback interfaces are still rising (but then I wonder if the physical/link interface breaks down is not the same result!) it also means that a PGI like OSPF or EIGRP must be running to provide communication between the loopback interfaces which is necessary to establish an iBGP connectivity?

  Thank you

  Hello

  If you use a loop or a physical interface will always require you an IGP with IBGP because is not a routing protocol is a transport L4 so the IGP Protocol it informs how stands as the BGP has no idea who he IGP is necessary

  Interns are selected for IBGP because it there once so the IGP has always a looping path the IBGP session will stay up, don't not necessary in EBGP as usually only 1 way between 2 points

• When to use BGP-address family?

  I often see BGP configured on a router of the provider (P/PE) like this (he is a true router just anonymizated extract);

  router bgp 12345

  Remote 1.1.1.1 neighbor - as 12345. iBGP peer

  ipv4 address family

  Remote 1.1.1.1 neighbor - as 12345. iBGP peer

  vpnv4 address family

  Remote 1.1.1.1 neighbor - as 12345. iBGP peer

  address ipv4 vrf Customer1 family

  neighbor 10.0.0.1 remote - as 67890! eBGP peer

  • I understand the CE peering defined under the 'family of addresses ipv4 vrf Customer1' because we put their journey in this VRF
  • I understand that "address-family vpnv4" is used to define peers from iBGP provider to be attached, carrying this customer VRF to another CE
  • Finally, I understand that a provider's router is an iBGP peer so that it is set directly under "router bgp 12345".

  What is the need for a 'family of ipv4 addresses' (without the vrf) here or never?

  What it does the output as 'normal' neighbor definitions (those who are directly under "router bgp 12345") and nearby definitions vpnv4, do not provide?

  Hello

  The BGP, as you know, has a capacity of Multiprotocol - in one sitting, it is capable of carrying information about the various routed protocols (IPv4 Unicast, Multicast IPv4, IPv6 Unicast, Multicast IPv6, VPNv4, CLNP), in the jargon of BGP called "address families. With being a true multiprotocol routing protocol BGP, however, you all way to say BGP address what families should be exchanged with a neighbor especially. We are accustomed to the fact that, if we define a neighboring IPv4, we intend to Exchange IPv4 routes with this neighbour - but why is making a rule? Why do assumptions early on the address simply family because the address of the neighbor is from a family special itself?

  That's the point behind the controls of the address family . Definition of a neighbor in a particular address family means we want to Exchange routes of specific address with this neighbour family. No no not a neighbor listed under a particular address family means that we do not expect to exchange information of this family of addresses with this neighbour.

  Now, ipv4 address family says neighbors with whom we want to Exchange normal IPv4 unicast routes. It's perhaps surprising because to Exchange IPv4 routes with a neighbor, just simply set this neighbour by its address. The fact is that for backward compatibility with older BGP versions that were not Multiprotocol-capable, the BGP attributes implicitly defined all the neighbors to a section of the invisible -ipv4 address family . In other words, as soon as you set a neighbor, it is automatically added to a section of the invisible -ipv4 address family so that you don't have to do it manually.

  You can change, however. First of all, if you enter the BGP configuration command bgp upgrade-cli , you will find that the BGP configuration has been converted entirely to the family style address configuration. Outside any family address stanzas, only the nearby base settings are configured as their addresses, as numbers, updated sources. However, all orders by family of remaining addresses will be automatically moved into the stanzas of the address family. The behavior or BGP operations do not change with this new style of configuration, only the format of configuration is changed.

  In addition, if you enter the No bgp ipv4 unicast default command configuring BGP, BGP will prevent you from automatically assigning each neighbour newly defined in the section of the ipv4 address family . You then must add each neighbor set to each scheduled automatically - address family it does automatically for you more.

  So to wrap - ipv4 address family is in fact a pervasive section in the BGP configuration but for reasons of backward compatibility, it is not visible by default. However, the configuration can be converted into a configuration by address-family-strict, and in fact, I would recommend that for all new deployments.

  Please feel welcome to ask for more!

  Best regards

  Peter

• BGP: remove-private-like vs remove-private-as all

  I use the BGP 'remove-private-under' option to remove our private as numbers of routes sent over the Wan.  This works well.  However, some paths are Amazon VPC end with their ASN (usually 7224 or 9059).  In this case the announced route always ends look like this:

  *>  172.31.0.0/16    169.254.254.2          100    100      0 1234 65441 65442 65443 1234 7224 i

  I was hoping the command "delete-private-like everything" would change this path to "1234 1234 7224", but reading through the document , is not clear to me exactly what is.

  Hello

  before IOS 15.1 (2) T, remove-private-like functionality has the following restriction:

  If the path of the two all understood AS public and private as numbers, with the order of removal-private-under neighbor would not remove private as numbers.

  That's why the keyword 'all' optional has been added, which should eliminate private as numbers even when there is public as numbers in the path.

• BGP MPLS ATT

  I'm having a problem with a circuit ATT MPLS Ethernet with BGP.  I have a 140 circuit with ATT MPLS network and this is the only site where I will have this type of problem.

  RECS to the CPE BGP to Rabat and the circuit goes up and down.  Finally the circuit will remain difficult.  I see at the bottom of my router.  ATT tests the circuit and say they are testing their equipment clean.  If I go in my equipment and close the physical interface that connects to the ATT equipment the port constantly monte to the TOP and BGP is restored without any problem.

  * 26 sep 23:37:36.319: % LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state down
  * 26 sep 23:37:37.319: % LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed State to down
  * 26 sep 23:37:51.319: % LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed State to
  * 26 sep 23:37:52.319: % LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed State to
  * 26 sep 23:37:53.195: % ADJCHANGE-5-BGP: neighbor 172.X.X.X Up
  * 26 sep 23:40:07.319: % LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state down
  * 26 sep 23:40:08.319: % LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed State to down
  * 26 sep 23:40:08.319: % NBR_RESET-5-BGP: neighbor 172.X.X.X reset (flap Interface)
  * 26 sep 23:40:08.339: % ADJCHANGE-5-BGP: neighbor 172.X.X.X down the flap of the Interface
  * 26 sep 23:40:08.339: % BGP_SESSION-5-ADJCHANGE: 172.X.X.X a unicast IPv4 topology neighbor base removed from Rabat Interface session
  * 26 sep 23:45:20.319: % LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed State to
  * 26 sep 23:45:21.319: % LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed State to
  * 26 sep 23:45:22.527: % ADJCHANGE-5-BGP: neighbor 172.X.X.X Up
  * 26 sep 23:46:53.319: % LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state down
  * 26 sep 23:46:54.319: % LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed State to down
  * 26 sep 23:46:54.319: % NBR_RESET-5-BGP: neighbor 172.X.X.X reset (flap Interface)
  * 26 sep 23:46:54.339: % ADJCHANGE-5-BGP: neighbor 172.X.X.X down the flap of the Interface
  * 26 sep 23:46:54.339: % BGP_SESSION-5-ADJCHANGE: 172.X.X.X a unicast IPv4 topology neighbor base removed from Rabat Interface session
  * 26 sep 23:46:56.319: % LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed State to
  * 26 sep 23:46:59.319: % LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed State to down
  * 27 sep 00:01:16.319: % LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed State to
  * 27 sep 00:01:17.319: % LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed State to
  * 27 sep 00:01:24.171: % ADJCHANGE-5-BGP: neighbor 172.X.X.X Up
  * 27 sep 00:02:18.319: % LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed state down
  * 27 sep 00:02:19.319: % LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed State to down
  * 27 sep 00:02:19.319: % NBR_RESET-5-BGP: neighbor 172.X.X.X reset (flap Interface)
  * 27 sep 00:02:19.339: % ADJCHANGE-5-BGP: neighbor 172.X.X.X down the flap of the Interface
  * 27 sep 00:02:19.339: % BGP_SESSION-5-ADJCHANGE: 172.X.X.X a unicast IPv4 topology neighbor base removed from Rabat Interface session
  * 27 sep 00:10:11.971: % LINK-5-CHANGED: Interface GigabitEthernet0/1, changed state down administratively
  * 27 sep 00:10:16.963: % LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed State to down
  * 27 sep 00:10:20.319: % LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed State to
  * 27 sep 00:10:21.319: % LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/1, changed State to
  * 27 sep 00:10:23.911: % ADJCHANGE-5-BGP: neighbor 172.X.X.X Up

  Hello

  Looking at this exit there is certainly a problem of layer 1 over there if its wiring or connection mux fault t, 9/10 its side ISP but you will likely replace the local wiring to keep out them

  carrier lost 13, 0 no carrier, 0 break out

  carrier and no carrier has lost the carrier is an electrical signal that use Ethernet devices to detect if the wire is being used by an another transmitting station.

  The carrier lost counter increases whenever there is a loss of sense of the carrier. This occurs when the material emits a frame on the wire and does not see its own carrier wave on the Ethernet. The absence of the carrier signal increments the counter by any carrier.

  carrier lost

  Description: Cisco IOS sh interface meter. The number of times that the carrier was lost in the transmission. Common causes: find a bad cable. Check the physical connection on both sides.

• BGP announcement: How do I remove the attributes "next hop" and "metrics" inherited from OSPF?

  Hello

  I use a router THAT WAN Cisco ASR1001 connected via BGP AS65075 with our ISP.

  This router is connected through OSPF with our Cisco 7206VXR/NPE-G2 firewall.

  Topology:

  ISP <- bgp="" -="">RT 1001 <- ospf="" -="">FW 7206 <->LAN

  On the WAN router, static routes are set to null0 to always announce our class C networks.

  Route IP 192.168.10.0 255.255.255.0 Null0 250

  ...

  Network guidelines are placed in our BGP configuration:

  router bgp 65075

  The log-neighbor BGP-changes

  neighbor EBGP-PEER-IPv4-peer group

  EBGP-PEER-IPv4 neighbor fall-over bfd

  neighbour 192.168.88.138 distance - as 65200

  192.168.88.138 a neighbor EBGP peers PEERS-IPv4

  192.168.88.138 ISP IPv4 neighbor description

  next password 192.168.88.138 7 unknown

  !

  ipv4 address family

  ...

  network 192.168.10.0

  ...

  a neighbor EBGP-PEER-IPv4 soft-reconfiguration inbound

  EBGP-PEER-IPv4 neighbor distribute-list prefix-v4 on

  an EBGP-PEER-IPv4 neighbor prefix-maximum 100

  neighbor EBGP-PEER-IPv4-1 filter list out

  neighbor 192.168.88.138 activate

  neighbor 192.168.88.138 filter-list 2

  output-address-family

  A part of these networs are also learned through OSPF. If these routes are present in the routing table:

  RT-01 #sh ro ip 192.168.10.0

  Routing for 192.168.10.0/24 entry

  Known via "ospf 1", distance 110, metric 20, type extern 2, metric 1 forward

  Published by bgp 65075

  Last update to 192.168.0.79 on Port - channel1.28, 7w0d there is

  Routing descriptor blocks:

  * 192.168.0.79, from 192.168.0.71, 7w0d there is, through Port - channel1.28

  See metric: 20, number of share of traffic is 1

  Because these roads are active in the rounting table. Announcing BGP based on his and attributes "next hop" and "metric" are inherited from OSPF:

  RT-01 #sh ip bgp neighbors 192.168.88.138 announced-routes

  ...

  Network Next Hop path metrics LocPrf weight

  ...

  * > 192.168.10.0 192.168.0.79 20 32768 I

  ...

  Is it possible to remove the legacy of OSPF into BGP attributes?

  How to set the "next hop" to the value 0.0.0.0 and "metric" to 0?

  Thank you

  Best regards

  Jérôme

  Hello Berthier,

  NEXT_HOP is a hill & attribute mandatory path including the eBGP value is the IP address of the BGP peer (specified in the neighbor's remote control) where the router learns the prefix. Thus, your peers (eBGP) will still see the IP 192.168.88.138 in your BGP Next Hop as updates. I agree you the output of the command ' sh ip bgp neighbors 192.168.88.138 roads announced "can be confusing, but not worried about it.

  Metric 20 is cause of path must be acquired by OSPF. Copy in default atributte MED BGP metric. So I see that you have only a peer is very important change this value because MED is not transitive, if this value is not propagated by other ACE access your provider. Anyway, if you want to change, you must:

  1. create a list of prefixes with one or more prefixes that you want to "reset" the MED value:

  list of prefixes prefix-to-reset-MED seq 5 permit 192.168.10.0/24

  list of prefixes prefix-to-reset-MED seq 10 permit X.X.X

  2. create a roadmap

  allowed to reset - MED card route 5

  match of prefix-to-reset-MED IP prefix-list

  the metric value 0

  road map provided to zero-MED allowed 10

  !

  The last road map is necessary to ensure that the rest of the prefixes are sent.

  3. apply the road map

  a neighbor EBGP-PEER-IPv4-roadmap given to zero-MED on

  Concerning

• Duplicate BGP AS path

  Hello guys,.

  Today at awkward work something caught my attention.

  The situation returns to BGP, when I run the command sh ip bgp, the output gives me this:

  RT52162 #sh ip bgp
  Version of BGP table is 56, local router ID is 10.10.0.16
  Status codes: deleted, cushioning d s, history of h, * valid, > best, i - internal.
  r SIDE-failure, stale S
  Source codes: i - IGP, e - EGP,? -incomplete

  Network Next Hop path metrics LocPrf weight
  * 0.0.0.0 172. **. 161 50 0 15 * 15 * 5 5 65010?
  *>                                 172.**.***.169                              0          15**5 65010 ?
  *> 10.**.0.16/32        0.0.0.0                                            0            32768 ?
  *> 10.**.0.0/16          0.0.0.0                                            0            32768 ?

  The part "BOLD" of the output is exactly the same thing, and this connection works on ATM.

  I can't understand this question, so if someone could explain to me why this is happening or how can we solve it, I have other sites configured the with the same configuration and it gives me the same exact result.

  Hello

  The nearby 172.xxx.xxx.161 done AS_PATH adding by adding at the beginning of his time number one DID when advertising the default route so it is considered to be a neighbor of backup.

  Concerning

  Alain