Pete's Packet

Limitless

Archive for January, 2010

CCIE® SP Operations Certification

Posted by Peter Kurdziel on January 25, 2010

The Cisco CCIE SP Operations certification
assesses and validates core IP NGN service provider operations
expertise.  Candidates who pass the CCIE SP Operations certification
exams demonstrate skills required of a expert-level (Tier III or Tier IV
support) operations engineer to troubleshoot and maintain complex
service provider IP NGN core (PE-PE and PE-CE) network infrastructures
in both IOS and IOS XR operating environments, plus validate broad
theoretical knowledge of operations management processes, frameworks,
and network management systems.

CCIE SP Operations Certification benefits:

  • Certification
    helps qualify personnel for customer’s Operations (NOC) Centers
  • Provides
    a credential (certification) that a person holds significant knowledge
    in SP Operations
  • Provides expert level certification to network
    operations (i.e. NOC) personnel to validate they are qualified to
    maintain and support Cisco service provider core IP (NGN) Next
    Generation Networks


CCIE SP Operations Written Exam Topics

 

The Cisco SP Operations Written
Exam (#350-060) has 100 multiple-choice questions and is two hours in
duration. The topic areas listed are general guidelines for the type of
content that is likely to appear on the exam. Please note, however, that
other relevant or related topic areas may also appear.

 

Exam Sections and Sub-task Objectives

√

1.0

Manage the network fault management
system

1.1

Develop a fault management
process for a managed network environment collaboratively with the tools
team

1.2

Determine the interaction
between the fault management system and the ticketing system in
collaboration with the tools team

1.3

Determine the method to gather appropriate metrics
for an established fault management process

2.0

Manage
performance and capacity

2.1

Identify spikes and potential trouble spots based
on syslog and/or Network Management System (NMS) output

2.2

Develop a plan to solve a particular performance
issue based on syslog and/or Network Management System (NMS) output

2.3

Identify the Network Management System (NMS)
metrics and SLA metrics that will be needed in order to further
troubleshoot a specific problem communicated orally, written, etc.

2.4

Develop a plan to establish a baseline and monitor
the network in conjunction with the tools and performance groups

2.5

Create baseline network performance in conjunction
with engineering and architecture teams

2.6

Monitor the network to look for variances against
the baseline

2.7

Edit existing scripts which
enable a network baseline management plan in conjunction with the tools
and performance groups

3.0

Manage
operations processes

3.1

Collaborate with the process
team and NOC management on process development to meet a desired
network operational objective

3.2

Develop a specific prototype
and test plan for a particular planned network change, working
collaboratively with the engineering and design groups

3.3

Develop, for a particular network, a list of needed
tools working collaboratively with the tools team

3.4

Develop a detailed operations plan  including
metrics and reporting functions for a particular network working
collaboratively with the process team

3.5

Develop a process change action plan based on the
results of a network audit

3.6

Develop and maintain a
spares plan for a particular network

4.0

Troubleshoot and
fix reachability and transport problems within the network

4.1

Identify predecessor steps that have not been
executed based on an escalation ticket dealing with reachability

4.2

Determine whether to fix or escalate a ticket
dealing with reachability

4.3

Identify the area(s) causing
a complex reachability problem of unknown origin

4.4

Troubleshoot a complex routing problem and,
considering the technical aspects, determine the risks and fix it

4.5

Troubleshoot a complex security problem and,
considering the technical aspects, determine the risks and fix it

5.0

Identify
problems in implementation plans

5.1

Find issues of a rollout plan received from
engineering before deployment

5.2

Identify hardware which is
not backwards compatible on a new service rollout plan

5.3

Find hardware that needs operating system upgrades
on a new service rollout plan

5.4

Review and provide
recommendations on areas in which NOC support plans will not be
sufficient on a new service rollout plan

6.0

Troubleshoot and
fix network performance problems

6.1

Identify predecessor steps that have not been
executed based on an escalation ticket dealing with network performance

6.2

Determine whether to fix or escalate a ticket
dealing with network performance

6.3

Determine whether to fix or where to escalate a
core network fault

6.4

Identify the source of a
complex network performance problem

6.5

Troubleshoot a complex network performance problem
and, considering the technical aspects, determine the risks and  fix it

6.6

Identify a complex
application performance problem and isolate it

6.7

Identify a complex computing device (server, call
manager, etc – not the network or application) performance problem and
isolate it

6.8

Troubleshoot a complex
traffic pattern problem and, considering the technical aspects,
determine the risks and fix it

6.9

Troubleshoot a complex,
chronic performance problem and, considering the technical aspects,
determine the risks and fix it

Posted in Real World | Leave a Comment »

Autonegotiation Valid Configuration

Posted by Peter Kurdziel on January 17, 2010

There is a lot of confusion about auto negotiation. Here is a chart that will help bring things into perspective.

Autonegotiation Valid Configuration



Configuration NIC (Speed/Duplex)

Configuration Switch (Speed/Duplex)

Resulting NIC Speed/Duplex

Resulting Catalyst Speed/Duplex

Comments

AUTO

AUTO

1000 Mbps, Full-duplex

1000 Mbps, Full-duplex

Assuming maximum capability of Catalyst switch, and NIC is 1000
Mbps, full-duplex.

1000 Mbps, Full-duplex

AUTO

1000 Mbps, Full-duplex

1000 Mbps, Full-duplex

Link is established, but the switch does not see any
autonegotiation information from NIC. Since Catalyst switches support only
full-duplex operation with 1000 Mbps, they default to full-duplex, and this
happens only when operating at 1000 Mbps.

AUTO

1000 Mbps, Full-duplex

1000 Mbps, Full-duplex

1000 Mbps, Full-duplex

Assuming maximum capability of NIC is 1000 Mbps,
full-duplex.

1000 Mbps, Full-duplex

1000 Mbps, Full-duplex

1000 Mbps, Full-duplex

1000 Mbps, Full-duplex

Correct Manual Configuration

100 Mbps, Full-duplex

1000 Mbps, Full-duplex

No Link

No Link

Neither side establishes link, due to speed
mismatch

100 Mbps, Full-duplex

AUTO

100 Mbps, Full-duplex

100 Mbps, Half-duplex

Duplex Mismatch
1

AUTO

100 Mbps, Full-duplex

100 Mbps, Half-duplex

100 Mbps, Full-duplex

Duplex Mismatch
1

100 Mbps, Full-duplex

100 Mbps, Full-duplex

100 Mbps, Full-duplex

100 Mbps, Full-duplex

Correct Manual
Configuration2

100 Mbps, Half-duplex

AUTO

100 Mbps, Half-duplex

100 Mbps, Half-duplex

Link is established, but switch does not see any
autonegotiation information from NIC and defaults to half-duplex when operating
at 10/100 Mbps.

10 Mbps, Half-duplex

AUTO

10 Mbps, Half-duplex

10 Mbps, Half-duplex

Link is established, but switch does not see Fast Link Pulse
(FLP) and defaults to 10 Mbps half-duplex.

10 Mbps, Half-duplex

100 Mbps, Half-duplex

No Link

No Link

Neither side establishes link, due to speed
mismatch.

AUTO

100 Mbps, Half-duplex

100 Mbps, Half-duplex

100 Mbps, Half-duplex

Link is established, but NIC does not see any autonegotiation
information and defaults to 100 Mbps, half-duplex.

AUTO

10 Mbps, Half-duplex

10 Mbps, Half-duplex

10 Mbps, Half-duplex

Link is established, but NIC does not see FLP and defaults to
10 Mbps, half-duplex.

Posted in Best practices, CATALYST, Real World, Troubleshooting | 1 Comment »

QoS Feature Support Table (netcraftsmen.net)

Posted by Peter Kurdziel on January 15, 2010

QoS Function LAN Ports OSM WAN Ports (includes GE-WAN ports, but not GigabitEthernet ports) Flex WAN/ MQC
Classification

Classify traffic based on CoS, or trusted values for IPP, DSCP or MPLS EXP, and by ACL.

Starting w/ 12.2(18)SXE, can support re-marked versions with the command “platform ip features sequential”

Classify IP traffic based on IPP, DSCP or MPLS EXP and by ACL. COS is not applicable.

Starting w/ 12.2(18)SXE, can support re-marked versions with the command “platform ip features sequential”

 Classify traffic based on:

  • ACL
  • ATM Cell Loss Priority bit
  • BGP index
  • CoS
  • DSCP
  • Frame Relay DLCI value
  • Frame-Relay DE bit
  • IPP
  • MAC-layer address
  • MPLS EXP
  • Packet length
  • Protocols supported by NBAR
  • VLAN ID
Marking

Can set DSCP, which includes IPP. Also EXP.

CoS is set indirectly on output.

Can also mark via policing:

police zzz conform-action set-prec-transmit

police zzz conform-action set-dscp-transmit

police zzz conform-action set-mpls-exp-imposition-transmit

Can set DSCP, which includes IPP. Also EXP.

CoS is not applicable.

Can also mark via policing:

police zzz conform-action set-prec-transmit

police zzz conform-action set-dscp-transmit

police zzz conform-action set-mpls-exp-imposition-transmit

Can set DSCP, which includes IPP. Also EXP.

CoS is not applicable.

Can also mark via policing:

police zzz conform-action set-prec-transmit

police zzz conform-action set-dscp-transmit

police zzz conform-action set-mpls-exp-imposition-transmit
Matching (or “Filtering”)

Supports single match command, either:

match access-group

match ip dscp

match ip precedence

match mpls experimental

With 12.2(18)SXE and later, also supports

match any

match dscp

match precedence

match protocol ip

match protocol ipv6

Also supports multiple match commands in SXE release.

Supports:

 

match access-group

match ip dscp

match ip precedence

match mpls experimental

With 12.2(18)SXE and later, also supports

match any

match vlan

Supports:

match access-group

match bgp-index

match class-map

match cos

match dscp

match destination-address

match dscp

match fr-dlci

match ip dscp

match ip precedence

match mpls experimental

match mpls

match precedence

match protocol

match source-address
Police

Configure with the police bps… command

Supported in inbound and outbound direction

Supports all LAN port match types

Configure with the police bps… command

Supported in inbound and outbound direction

Supports all OSM WAN port match types

Configure with the police bps… command

Supported in inbound and outbound direction

Supports all FlexWAN port match types
Trust Untrusted by default, CoS set to 0

Can define the port CoS with the mls qos cos port-cos command

 Trust DSCP by default

Can configure to trust CoS, DSCP, or IPP (ingress CoS always set to 0)

Can NOT define the port CoS with the mls qos cos port-cos command

 Trust DSCP by default

Can change DSCP by marking

 

Can NOT define the port CoS with the mls qos cos port-cos command
Shaping

Not supported.

Note: Can use “shape” command in an outbound policy, but this policy does not shape traffic!

Inbound and outbound shaping supported using “shape average bps” command.

Does NOT support ACL for matching in class map, but supports other OSM WAN match types

Note: Can NOT review data in “show mls qos ip” results.

Outbound shaping supported using the “shape average bps” and “shape peak bps” commands for outbound traffic.

Cannot use “shape” command inbound
Bandwidth or “CBWFQ”

Not supported

Note: can be applied to interface, no error message provided, but not shown in “show mls qos ip” listing.)

Configure with either

bandwidth kbps

or the

bandwidth percent percentage

command in the outbound direction.

Does NOT support ACL for matching in class map, but supports other OSM WAN match types.

Note: Can NOT review data in “show mls qos ip” results

Configure with either

bandwidth kbps

or the

bandwidth percent percentage

command, in either the inbound or outbound direction.

Supports all FlexWAN port match types

Supported on physical interface interface if it is in default queueing mode.
Hierarchical Shaping Not supported

Supported for output policies only

Can only have class default in parent layer

Child policy does not support marking with set command

Does NOT support ACL for matching in class map, but supports other OSM WAN match types

Use bandwidth and priority in child policy

Supported for output policies only

Child policy does not support marking with set command

Use bandwidth and priority in child policy
WRED

Supported on main interface, configure with wrr-queue random-detect min-threshold queue_id

Supported on enhanced OSMs

Supported in output direction

Configure with random-detect under policy map class

Supported in output direction

Configure with random-detect under policy map class
Verification

Can use

show policy interface

show mls qos ip

Can use

show policy interface

show mls qos ip (for PFC QoS, not for shaping and CBWFQ)

Can use

show policy interface

Source: http://www.netcraftsmen.net/resources/archived-articles/425-qos-for-the-cisco-6500-revisited.html

Posted in QOS | Leave a Comment »

Here is a great enhancement to your voicemail.

Posted by Peter Kurdziel on January 15, 2010

I thought I would pass this on since I am having a lot of fun with it. I use this service and I can not imagine being without it. You have hundreds of great prerecorded greetings to choose from. Some are pretty funny.

You can check your voice mail on the phone or on the pc. I don’t even check it on my phone anymore. I always use my laptop.

More info here: http://www.youmail.com?src=ccie

Posted in Routing & Switching Lab | Leave a Comment »

Advanced MPLS Traffic Engineering

Posted by Peter Kurdziel on January 14, 2010

MPLS TE explicit paths are usually used in combination with an offline network analysis and simulation tool to optimize the backbone utilization based on observed flows across the backbone.

In this part of the exercise, you’ll use the MPLS TE explicit paths to force the traffic between PE routers to take the longer path through the P router. You will use dynamic path computation as a fallback option.

Task 1 Determine the Explicit Path

Explicit MPLS TE path must specify hop-by-hop path across an MPLS backbone, listing ingress IP addresses of all LSRs between the tunnel headend and tunnel tailend (including the tailend IP address). The simplest way to get these addresses is to perform a trace command from the tunnel headend toward the tunnel tailend using loose source routing.

The following steps have to be performed on all PE routers:

Step 1 Do a trace toward the tunnel tailend with loose source routing through the P-router. You will get a printout similar to the one below:
Step 2 Create an explicit MPLS TE route, listing the IP addresses displayed by the trace command as the next-hop addresses in the explicit route. Add the tailend router’s loopback address as the last hop in the explicit route.
Step 3 Configure the explicit route defined above as the preferred path option for the tunnel interface configured in the previous section, with the dynamically computed route being a fallback option.

PE1#trace

Protocol [ip]:

Target IP address: 192.168.1.3

Source address:

Numeric display [n]:

Timeout in seconds [3]:

Probe count [3]:

Minimum Time to Live [1]:

Maximum Time to Live [30]: 10

Port Number [33434]:

Loose, Strict, Record, Timestamp, Verbose[none]: l

Source route: 192.168.1.5

Loose, Strict, Record, Timestamp, Verbose[LV]: v

Loose, Strict, Record, Timestamp, Verbose[L]:

Type escape sequence to abort.

Tracing the route to PE3 (192.168.1.3)

1 192.168.1.21 20 msec 16 msec 20 msec

2 192.168.1.17 32 msec 32 msec 36 msec

3 192.168.1.13 48 msec *  48 msec

ip explicit-path name PE3 enable

next-address 192.168.1.21

next-address 192.168.1.17

next-address 192.168.1.13

next-address 192.168.1.3

interface Tunnel0

tunnel mpls traffic-eng path-option 1 explicit name PE3

tunnel mpls traffic-eng path-option 99 dynamic

PE3#trace

Protocol [ip]:

Target IP address: 192.168.1.1

Source address:

Numeric display [n]:

Timeout in seconds [3]:

Probe count [3]:

Minimum Time to Live [1]:

Maximum Time to Live [30]:

Port Number [33434]:

Loose, Strict, Record, Timestamp, Verbose[none]: l

Source route: 192.168.1.5

Loose, Strict, Record, Timestamp, Verbose[LV]: v

Loose, Strict, Record, Timestamp, Verbose[L]:

Type escape sequence to abort.

Tracing the route to PE1 (192.168.1.1)

1 192.168.1.14 32 msec 32 msec 32 msec

2 192.168.1.18 64 msec 68 msec 64 msec

3 192.168.1.22 96 msec *  96 msec

ip explicit-path name PE1 enable

next-address 192.168.1.14

next-address 192.168.1.18

next-address 192.168.1.22

next-address 192.168.1.1

interface Tunnel0

tunnel mpls traffic-eng path-option 1 explicit name PE1

tunnel mpls traffic-eng path-option 99 dynamic

PE2#trace

Protocol [ip]:

Target IP address: 192.168.1.4

Source address:

Numeric display [n]:

Timeout in seconds [3]:

Probe count [3]:

Minimum Time to Live [1]:

Maximum Time to Live [30]:

Port Number [33434]:

Loose, Strict, Record, Timestamp, Verbose[none]: l

Source route: 192.168.1.5

Loose, Strict, Record, Timestamp, Verbose[LV]: v

Loose, Strict, Record, Timestamp, Verbose[L]:

Type escape sequence to abort.

Tracing the route to PE4 (192.168.1.4)

1 192.168.1.17 40 msec 32 msec 32 msec

2 192.168.1.13 120 msec 468 msec 576 msec

3 192.168.1.9 76 msec *  80 msec

interface Tunnel0

tunnel mpls traffic-eng path-option 1 explicit name PE4

tunnel mpls traffic-eng path-option 99 dynamic

ip explicit-path name PE4 enable

next-address 192.168.1.17

next-address 192.168.1.13

next-address 192.168.1.9

next-address 192.168.1.4

PE4#trace

Protocol [ip]:

Target IP address: 192.168.1.2

Source address:

Numeric display [n]:

Timeout in seconds [3]:

Probe count [3]:

Minimum Time to Live [1]:

Maximum Time to Live [30]:

Port Number [33434]:

Loose, Strict, Record, Timestamp, Verbose[none]: l

Source route: 192.168.1.5

Loose, Strict, Record, Timestamp, Verbose[LV]: v

Loose, Strict, Record, Timestamp, Verbose[L]:

Type escape sequence to abort.

Tracing the route to PE2 (192.168.1.2)

1 192.168.1.10 32 msec 32 msec 32 msec

2 192.168.1.14 64 msec 64 msec 72 msec

3 192.168.1.18 112 msec *  96 msec

interface Tunnel0

tunnel mpls traffic-eng path-option 1 explicit name PE4

tunnel mpls traffic-eng path-option 99 dynamic

ip explicit-path name PE2 enable

next-address 192.168.1.10

next-address 192.168.1.14

next-address 192.168.1.18

next-address 192.168.1.2

Explicit Path Verification

Step 4 Perform the steps outlined in the section Simple MPLS TE verification to verify proper operation of the MPLS TE tunnels.
Step 5 Perform trace from A1 ® A2 and from B1 ® B2. The traffic should flow over the P router.

A1#trace a2

Type escape sequence to abort.

Tracing the route to A2 (201.1.0.2)

1 150.1.11.1 28 msec 28 msec 28 msec

2 192.168.1.14 [MPLS: Labels 24/25 Exp 0] 408 msec 400 msec 400 msec

3 192.168.1.18 [MPLS: Labels 27/25 Exp 0] 360 msec 660 msec 440 msec

4 150.1.11.9 [MPLS: Label 25 Exp 0] 232 msec 268 msec 356 msec

5 150.1.11.10 144 msec *  144 msec

A1#

B1#trace b2

Type escape sequence to abort.

Tracing the route to B2 (201.2.0.2)

1 150.1.12.1 28 msec 28 msec 28 msec

2 192.168.1.17 [MPLS: Labels 25/26 Exp 0] 396 msec 400 msec 396 msec

3 192.168.1.13 [MPLS: Labels 26/26 Exp 0] 364 msec 364 msec 1056 msec

4 150.1.12.9 [MPLS: Label 26 Exp 0] 228 msec 232 msec 232 msec

5 150.1.12.10 164 msec *  548 msec

B1#



Posted in Routing & Switching Lab | Leave a Comment »

How to install Call Manager 6.x in VMWare

Posted by Peter Kurdziel on January 12, 2010

http://www.blindhog.net/how-to-install-call-manager-6x-in-vmware/


Posted in Routing & Switching Lab | Leave a Comment »

Vegas baby!!!!!

Posted by Peter Kurdziel on January 12, 2010

Cisco Live 2010 – Pre-Registration Now Open

Cisco Live is Cisco’s annual IT and communications conference. The
conference features Networkers, our premier education and training
program, and other special programs designed to meet the diverse needs
of today’s IT and communications professional from increasing technical
proficiency to understanding the impact of technology on business.

Las Vegas, Nevada
June 27 – July 1, 2010

Posted in Other, Real World | Leave a Comment »

Narbik is adding CCIE Security and Service Provider bootcamps this year!

Posted by Peter Kurdziel on January 12, 2010

Here is a list of bootcamps and dates.
http://www.micronicstraining.com/classes/index.php?dispatch=categories.view&category_id=190

Posted in Other, Real World, Routing & Switching Lab | Leave a Comment »

Troubleshooting the Catalyst 6500

Posted by Peter Kurdziel on January 12, 2010

Troubleshooting Hardware and Common Issues on Catalyst 6500/6000 Series Switches Running Cisco IOS System Software


Troubleshoot Error Messages in the Syslog or Console



The show diagnostic sanity Command



Supervisor Engine or Module Problems


     
Supervisor Engine LED in Red/Amber or Status Indicates faulty

     
Switch Is in Continuous Booting Loop, in ROMmon mode, or Missing the System Image

     
Standby Supervisor Engine Module Is Not On Line or Status Indicates unknown

     
Show Module Output Gives “not applicable” for SPA Module

     
Standby Supervisor Engine Reloads Unexpectedly

     
Even After You Remove the Modules, the show run Command Still Shows Information About the Removed Module Interfaces

     
Switch Has Reset/Rebooted on Its Own

     
DFC-Equipped Module Has Reset on Its Own

     
Troubleshoot a Module That Does Not Come On Line or Indicates faulty or other Status

     
Inband Communication Failure

     
Error “System returned to ROM by power-on (SP by abort)”

     
Error: NVRAM: nv->magic != NVMAGIC, invalid nvram

     
Error: Switching Bus FIFO counter stuck

     
SYSTEM INIT: INSUFFICIENT MEMORY TO BOOT THE IMAGE!


Troubleshoot CatOS to Cisco IOS Software or Cisco IOS Software to CatOS Conversion


     
Problem when User Attempts to Access the NVRAM After Cisco IOS to CatOS Conversion

     
Unable to Boot with Cisco IOS Software when User Converts from CatOS to Cisco IOS


Interface/Module Connectivity Problems


     
Connectivity Problem or Packet Loss with WS-X6548-GE-TX and WS-X6148-GE-TX Modules used in a Server Farm

     
Workstation Is Unable to Log In to Network During Startup/Unable to Obtain DHCP Address

     
Troubleshoot NIC Compatibility Issues

     
Interface Is in errdisable Status

     
Troubleshoot Interface Errors

     
You Receive %PM_SCP-SP-3-GBIC_BAD: GBIC integrity check on port x failed: bad key Error Messages

     
You Get COIL Error Messages on WS-X6x48 Module Interfaces

     
Troubleshoot WS-X6x48 Module Connectivity Problems

     
Troubleshoot STP Issues

     
Unable to Use Telnet Command to Connect to Switch

     
Giant Packet Counters on VSL Interfaces


Power Supply and Fan Problems


     
Power Supply INPUT OK LED Does Not Light Up

     
Troubleshoot
C6KPWR-4-POWRDENIED: insufficient power, module in slot [dec] power
denied or %C6KPWR-SP-4-POWRDENIED: insufficient power, module in slot
[dec] power denied Error Messages

     
FAN LED Is Red or Shows failed in the show environment status Command Output

     
“Diagnostic level complete” causes a crash on 6500


Cisco Support Community – Featured Conversations



Related Information

Catalyst 6500/6000 Switches ARP or CAM Table Issues Troubleshooting


Troubleshoot ARP or CAM Related Issues


     
Loss of Dynamic MAC Addresses with Distributed Switching

     
CEF Drops Packets at Regular Intervals

     
Switch Filter All-Zero MAC Addresses from the CAM Table

     
Unicast Flooding in the Network Every 5 Minutes

     
ARP Issues in Hybrid CatOS

     
Error EARL-2-EARL4LOOKUPRAMERROR During the CAM Table Lookup

     
Static CAM Entries Lost After Supervisor Switchover

     
%ACL-5-TCAMFULL: acl engine TCAM table is full

     
Ping Issues Occur when the MSFC Does Not Respond to the ARP Request in Catalyst 6500 Series Switches

     
Multiple Entries in MAC Address Table

     
Virtual IP Address Used by Microsoft Load Balancing is Not Reachable


Troubleshooting Input Queue Drops and Output Queue Drops


Processing and Switching



Input Queue Drops


     
Troubleshoot Input Queue Drops


Output Queue Drops


     
Troubleshoot Output Queue Drops


Commands to Obtain More Information


     
show interfaces switching

     
show interfaces stats

     
ip accounting mac-address

     
show interfaces mac-accounting

More info here: http://www.cisco.com/en/US/products/hw/switches/ps708/prod_tech_notes_list.html

Posted in CATALYST, Real World, Troubleshooting | Leave a Comment »

Awesome flow chart- BPG path selection -

Posted by Peter Kurdziel on January 4, 2010

http://rbcciequest.wordpress.com/2008/02/27/bgp-path-selection/

Posted in BGP | Leave a Comment »

 
Follow

Get every new post delivered to your Inbox.