State Less The Band Technology Site

Posts Tagged ‘ccnp’

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 »

Passing the BSCI exam and earning your CCNP is all about knowing the details, and when it comes to EIGRP SIA routes, there are plenty of details to know. A quick check in a search engine for “troubleshoot SIA” will bring up quite a few matches. Troubleshooting SIA routes is very challengin in that there’s no one reason they occur.

View the EIGRP topology table with the show ip eigrp topology command, and you’ll see a code next to every successor and feasible successor. A popular misconception is that we want these routes to have an “A” next to them – so they’re active. That’s what we want, right? Active routes sound good, right?

Well, they sound good, but they’re not. If a route shows as Active in the EIGRP topology table, that means that DUAL is currently calculating that route, and it’s currently unusable. When a route is Passive (“P), that means it’s not being recalculated and it’s a usable route.

Generally, a route shown as Active is going to be there for a very short period of time by the time you repeat the command, hopefully that Active route has gone Passive. Sometimes that doesn’t happen, though, and the route becomes SIA – Stuck In Active.
Read the rest of this entry »

When you’re working on your BCMSN exam on your way to CCNP certification, you’ll read at length about how Cisco routers and multilayer switches can work to provide router redundancy – but there’s another helpful service, Server Load Balancing, that does the same for servers. While HSRP, VRRP, and CLBP all represent multiple physical routers to hosts as a single virtual router, SLB represents multiple physical servers to hosts as a single virtual server.

In the following example, three physical servers have been placed into the SRB group ServFarm. They’re represented to the hosts as the virtual server 210.1.1.14.

The hosts will seek to communicate with the server at 210.1.1.14, not knowing that they’re actually communicating with the routers in ServFarm. This allows quick cutover if one of the physical servers goes down, and also serves to hide the actual IP addresses of the servers in ServFarm.

The basic operations of SLB involves creating the server farm, followed by creating the virtual server. We’ll first add 210.1.1.11 to the server farm:

MLS(config)# ip slb serverfarm ServFarm

MLS(config-slb-sfarm)# real 210.1.1.11

MLS(config-slb-real)# inservice
Read the rest of this entry »

To pass the CCNP exams, you’ve got to master Quality of Service, and the first step in doing so is knowing the differences between the different QoS types.

Now this being Cisco, we can’t just have one kind of QoS! We’ve got best-effort delivery, Integrated Services, and Differentiated Services. Let’s take a quick look at all three.

Best-effort is just what it sounds like – routers and switches making their “best effort” to deliver data. This is considered QoS, but it’s kind of a “default QoS”. Best effort is strictly “first in, first out” (FIFO).

An entire path from Point A to Point B will be defined in advance when Integrated Services are in effect. Integrated Services is much like the High-Occupancy Vehicle lanes found in many larger cities. If your car has three or more people in it, you’re considered a “priority vehicle” and you can drive in a special lane with much less congestion than regular lanes. Integrated Services will create this lane in advance for “priority traffic”, and when that traffic comes along, the path already exists. Integrated Services uses the Resource Reservation Protocol (RSVP) to create these paths. RSVP guarantees a quality rate of service, since this “priority path” is created in advance. Read the rest of this entry »