State Less The Band Technology Site

Posts Tagged ‘chris’

Like TCP, BGP is connection-oriented. An underlying connection between two BGP speakers is established before any routing information is exchanged. This connection takes place on TCP port 179. As with EIGRP and OSPF, keepalive messages are sent out by the BGP speakers in order to keep this relationship alive.

Once the connection is established, the BGP speakers exchange routes and synchronize their tables. After this initial exchange, a BGP speaker will only send further updates upon a change in the network topology.

The IGP protocols that use Autonomous Systems, IGRP and EIGRP, require prospective neighbors to be in the same AS. This is not true with BGP. Routers can be in different Autonomous Systems and still exchange routes. The BGP neighbors do not have to be directly connected, and often are not, but do need to be able to reach the IP addresses they use in their neighbor statements.

A BGP peer that is in the same AS is referred to as an Internal BGP (iBGP) Peer, where a BGP peer in another AS is an External BGP (eBGP) Peer.

A sample iBGP configuration:

Router bgp 100

Neighbor 10.1.1.2 remote-as 100

A sample eBGP configuration:

Router bgp 100

Neighbor 10.1.1.2 remote-as 200

Cisco recommends that eBGP peers be directly connected, where iBGP peers generally will not be.

Before we get too much farther into BGP theory, let’s get a configuration started. You’ll use the router bgp command to configure a router as a BGP speaker. Right after that, the neighbor command will be used to identify this BGP speaker’s potential neighbors. (The terms “peer” and “neighbor” are interchangeable in BGP, but it’s the neighbor statement that is used to statically define neighbors. BGP is not capable of discovering neighbors dynamically.)

R1(config-router)#neighbor 172.12.123.3 remote-as 200

While almost all of the neighbor options are just that — optional — you do have to specify the BGP AS of the remote router. BGP has no mechanism to dynamically discover neighbors. Remember, BGP speakers do not have to be in the same AS to become peers. To verify that the remote BGP speaker has become a peer, run show ip bgp neighbor.
Read the rest of this entry »

Whether you’re on the road to the CCNA, CCNP, MCSE, or you’re on any other computer certification track, the odds are that sooner or later, you’re going to fail an exam. It’s happened to almost all of us, yours truly included. What you have to keep in mind in these times is that success is not a straight line. You’ve probably seen charts showing the growth of an industry or a business — you know, the ones that go from left to right, and look kind of jagged. The line goes up for a while, then down a bit, then up some more, then down a little.

The key? While every business has its setbacks, the net result is that the line goes up and progress is made. That’s how you want your certification pursuit and your career to go as well – upward!

I’m not asking you to be happy about failing an exam. You’re allowed to get mad for a few minutes, vow to never take another exam again, and be disappointed. What you’re not allowed to do is stay that way.
Read the rest of this entry »

CCNA and CCNP candidates who have their own Cisco home labs often email me about an odd situation that occurs when they erase a switch’s configuration. Their startup configuration is gone, as they expect, but the VLAN and VTP information is still there!

Sounds strange, doesn’t it? Let’s look at an example. On SW1, we run show vlan brief and see in this abbreviated output that there are three additional vlans in use:

SW1#show vlan br

10 VLAN0010 active

20 VLAN0020 active

30 VLAN0030 active

We want to totally erase the router’s startup configuration, so we use the write erase command, confirm it, and reload without saving the running config:

SW1#write erase

Erasing the nvram filesystem will remove all configuration files! Continue?

[confirm]

[OK]

Erase of nvram: complete

00:06:00: %SYS-7-NV_BLOCK_INIT: Initalized the geometry of nvram

SW1#reload

System configuration has been modified. Save? [yes/no]: n

Proceed with reload? [confirm]

The router reloads, and after exiting setup mode, we run show vlan brief again. And even though the startup configuration was erased, the vlans are still there!

Switch#show vlan br

10 VLAN0010 active

20 VLAN0020 active

30 VLAN0030 active
Read the rest of this entry »