Totally NSSA Filters type 3, 4 and type 5 LSA’s.

NSSA totally stubby area

An addition to the standard functionality of an NSSA, the totally stubby NSSA is an NSSA that takes on the attributes of a TSA, meaning that type 3 and 4 summary routes are not flooded into this type of area. It is also possible to declare an area both totally stubby and not-so-stubby, which means that the area will receive only the default route from area 0.0.0.0, but can also contain an autonomous system boundary router (ASBR) that accepts external routing information and injects it into the local area, and from the local area into area 0.0.0.0.

Redistribution into an NSSA area creates a special type of LSA known as TYPE 7, which can exist only in an NSSA area. An NSSA ASBR generates this LSA, and an NSSA ABR router translates it into type 5 LSA which gets propagated into the OSPF domain.

https://learningnetwork.cisco.com/message/111497

 

Adjacencies on Non-Broadcast Multi-Access (NBMA) Networks

http://www.cisco.com/en/US/tech/tk365/technologies_white_paper09186a0080094e9e.shtml#t24

Special care should be taken when configuring OSPF over multi-access non-broadcast medias such as Frame Relay, X.25, ATM. The protocol considers these media like any other broadcast media such as Ethernet. NBMA clouds are usually built in a hub and spoke topology. PVCs or SVCs are laid out in a partial mesh and the physical topology does not provide the multi access that OSPF believes is out there. The selection of the DR becomes an issue because the DR and BDR need to have full physical connectivity with all routers that exist on the cloud. Also, because of the lack of broadcast capabilities, the DR and BDR need to have a static list of all other routers attached to the cloud. This is achieved using the neighbor ip-address [priority number] [poll-interval seconds] command, where the "ip-address" and "priority" are the IP address and the OSPF priority given to the neighbor. A neighbor with priority 0 is considered ineligible for DR election. The "poll-interval" is the amount of time an NBMA interface waits before polling (sending a Hello) to a presumably dead neighbor. The neighbor command applies to routers with a potential of being DRs or BDRs (interface priority not equal to 0). The following diagram shows a network diagram where DR selection is very important:

Why Does the show ip ospf neighbor Command Reveal Neighbors in the Init

http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a00800949f7.shtml#trouble_init_state


the init state indicates that router-2 sees hello packets from the neighbor, but two-way communication has not been established. A Cisco router includes the Router IDs of all neighbors in the init (or a higher) state in the neighbor field of its hello packets. For two-way communication to be established with a neighbor, a router also must see its own Router ID in the neighbor field of the neighbor's hello packets. In other words, a router with a neighbor in the init state has received hello packets from the neighbor but has not seen its own Router ID in the neighbor's hellos. In this case, if the router does not receive four consecutive hellos, it tears down the session and the OSPF adjacency goes down.

mywebsearch how many times, this got into the pc

disable the plugin in the browser

local MS vendor ingramMicro training sbs2011 and hyper-v

local MS vendor ingramMicro training sbs2011 and hyper-v

do you have MS exam voucher's , nope .... dave shook his head ... shiiiitttt

Ingram Micro is holding free sessions on sbs 2011 and hyper-v

SBS 2011 standard -- the normal sbs
SBS 2011 eseentials -- the file/print + MS cloud

SBS 2011 licenses has changed , and upto 50 users ( not 75 anymore??)

there is no sbs 2011 premium, it is now called sbs 2011 addd-on, which is about more than 40% of the price.

in remote workplace, you can see public folders or file shares ... exchange 2010 sp1

now Hyper-V

they mention if you want to migrate ms virtual server 2005, you need un-install something, or you blow it up

yes, there is a hyper-V workgroup manager, it can manage 5 hosts

Live migration, you can do this way
on w2008 r2 host, enable hyper-v
enable quorum on one iscsi, and install windows on another windows lun,
add clusteriing feature, so there will be a cluster-ip address
add fail-over node,

then install vm in hyper-v

mount hyper-v in c:\clusterstorage\volume1
this is actually the mount points corresponding to the iscsi lun volume (not the cache I reckon)

I can test by un-pluggin the network cable, our test didn';t end-up well, the fail-over crashed to sorta of safe mode on the other machine. tutor said it was ok, vmware got a solution which fully sync memory

one gattacha i had is I have to add services/apps to the nodes, this time it is the virtual machine hyper-v vm,

that makes sense because that's the apps/services protected by the cluster

open mdi file

http://support.microsoft.com/kb/926198

Click Start, click Run, type appwiz.cpl in the Open box, and then click OK.


In the Currently installed programs list, click the 2007 Office version that you have installed.

Click Change.

Click Add or Remove features, and then click Continue.

Expand Office Tools.

Expand Microsoft Office Document Imaging.

Click Scanning, OCR, and Indexing Services Filter, and then click Run from My Computer.

Click Continue.

EIGRP #of maximum-paths

https://learningnetwork.cisco.com/thread/4104

EIGRP defaults to 4 paths for load balancing but the maximum that can be set
is 16. The maximum used to be 6 but this was increased.

EIGRP #of
maximum-paths

eigrp cir bandwidth

http://hujnet.com/network/cisco/ccnp/bsci/2/004.htm

Treats bandwidth as T1 by default

　　　– Should manually configure bandwidth as the CIR of the PVC

　　* Bandwidth utilization over multipoint Frame Relay, ATM, and ISDN PRI:

　　　– EIGRP uses the bandwidth on the physical interface divided by the number of neighbors on that interface to calculate the bandwidth attributed per neighbor.

　　Cisco IOS software assumes that point-to-point Frame Relay subinterfaces (like all serial interfaces) operate at full T1 link speed. In many implementations, however, only fractional T1 speeds are available. Therefore, when configuring these subinterfaces, set the bandwidth to match the contracted committed information rate (CIR) of the permanent virtual circuit (PVC).

　　When configuring multipoint interfaces, especially for Frame Relay (but also for ATM and ISDN PRI), it is important to understand that all neighbors share the bandwidth equally. That is, EIGRP uses the bandwidth command on the physical interface divided by the number of
Frame Relay neighbors connected on that physical interface to calculate the bandwidth attributed to each neighbor. EIGRP configuration should reflect the correct percentage of the actual available bandwidth on the line.

show ip eigrp traffic

show ip eigrp traffic

http://www.cisco.com/en/US/docs/ios/12_0/np1/command/reference/1reigrp.html#wp1018815

Router# show ip eigrp traffic

IP-EIGRP Traffic Statistics for process 77

Hellos sent/received: 218/205

Updates sent/received: 7/23

Queries sent/received: 2/0

Replies sent/received: 0/2

Acks sent/received: 21/14

Table 34 describes the fields that might be shown in the display.

Table 34 show ip eigrp traffic Field Descriptions 

Field	Description
process 77	Autonomous system number specified in the ip router command.
Hellos sent/received	Number of hello packets that were sent and received.
Updates sent/received	Number of update packets that were sent and received.
Queries sent/received	Number of query packets that were sent and received.
Replies sent/received	Number of reply packets that were sent and received.
Acks sent/received	Number of acknowledgment packets that were sent and received.

Cisco Single BGP with Origin value

weight (cisco only , local as significant), higher better
local_preference, higher better
origin type lower better

as-Path, shorter better

med (metric), lower better

http://showipbgp.com/bgp-configurations/40-cisco/128-1-3-1-cisco-single-bgp-with-origin-value.html

Lowest Origin Type is one
of important criteria for BGP best path selection.

- Prefer the path with the lowest origin type: IGP is
lower than EGP, and EGP is lower than INCOMPLETE. (IGP < EGP <
Incomplete)
- IGP origin is created when there is a network statement
-
EGP origin is created via ‘redistribute
- Incomplete origin
is created via redistribute

What Is Administrative Distance?

http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094195.shtml

Default Distance Value Table

This table lists the administrative distance default values of the protocols that Cisco supports:

Route Source	Default Distance Values
Connected interface	0
Static route	1
Enhanced Interior Gateway Routing Protocol (EIGRP) summary route	5
External Border Gateway Protocol (BGP)	20
Internal EIGRP	90
IGRP	100
OSPF	110
Intermediate System-to-Intermediate System (IS-IS)	115
Routing Information Protocol (RIP)	120
Exterior Gateway Protocol (EGP)	140
On Demand Routing (ODR)	160
External EIGRP	170
Internal BGP	200
Unknown*	255

bgp-aggregate-address-command

http://www.ipbalance.com/routing/bgp/281-bgp-aggregate-address-command.html

When the aggregate-address command is used within BGP routing, the aggregated address is advertised, along with the more specific routes. The exception to this rule is through the use of the summary-only command. The “summary-only” keyword suppresses the more specific routes and announces only the summarized route.

BGP – Split Horizon

http://www.ccie-wiki.com/BGP_Split_Horizon.htm

“A route learned from one IBGP neighbor will not be advertised to another IBGP neighbor.”

default BGP MED value is 0

https://learningnetwork.cisco.com/docs/DOC-2480

An AS is a collection of networks under a single technical administration An IGP is run inside an AS, an EGP is run between AS.
Desing Goals for Interdomain Routing	Scalability Secure routing information exchange Support for routing policies
BGP Characteristics	Reliable updates Triggered updates only Rich metrics
BGP performing areas	Interdomain routing applications Huge internetworks Environments that require complex routing policies
BGP uses	Customers connected to more than one service provider Service provider networks Service providers exchanging traffic Network core
Lesson 2: Understanding BGP Path Attributes
Well-Know	Mandatory Origin AS-path Next-hop Discretional Local preference (default value = 100) Atomic aggregate
Optional	Transitive Aggregator Community (default value = nonexistent) Nontransitive MED (default value = 0 )
Cisco-defined	Weight (default value = 32768)
Lesson 3: Establishing BGP Sessions
BGP States	Idle Active OpenSent OpenConfirm Established
BGP Open message parameters	Version number AS number Holdtime BGP identifier Optional parameters(Type,TLV, authentication)
BGP Keepalive	Default value 60 seconds
BGP Holdtime	Default value 180 seconds
Lesson 4: Processing BGP Routes
BGP Route Selection Criteria	Router check next-hop attribute, excludes routes with inaccessible next-hop Prefer the route with the higher weight. (Value considered local to router) Prefer the route with the higher local preference (within AS) Prefer the route that router originated (redistribution) Prefer shortest AS path Prefer lowest origin code Prefer lowest MED Prefer external EBGP paths IBGP paths closest IGP neighbor EBGP paths oldest path Paths from router with the lowest BGP router-ID
Lesson 5: Configuring Basic BGP
Configuring MD5 Authentication	The first character cannot be a number. The string can contain any alphanumeric characters, including spaces. You cannot specify a password in the format "number-space-anything"
Announcing Networks in BGP	Manually configure networks Use redistribution Use aggregation to announce summary prefixes
Configuring Classless BGP	BGP4 supports CIDR Any BGP router can advertise individual networks or supernets Prefix notation is used with BGP
BGP support for TTL security check	Lightweight security Protects the EBGP peering sessions Supportsdirectly connected peering and multihop peering sessions
Lesson 6: Monitoring and troubleshooting BGP
Common BGP session startup symptoms	BGP neighbor do not become active BGP neighbor is active, session never established BGP neighbor oscillates between idle and active
Common BGP session startup problems	BGP Neighbor not reachable BGP Neighbor not configured BGP AS number mismatch

show ip bgp neighbors [address] [received-routes | routes | advertised-routes | {pathsregular-expression} | dampened-routes]

http://www.cisco.com/en/US/docs/ios/12_0/np1/command/reference/1rbgp.html#wp1022538

Examples

The following is sample output from the show ip bgp neighbors command:

Router# show ip bgp neighbors 172.16.232.178

BGP neighbor is 172.16.232.178,  remote AS 10, external link

Index 1, Offset 0, Mask 0x2

Inbound soft reconfiguration allowed

BGP version 4, remote router ID 172.16.232.178

BGP state = Established, table version = 27, up for 00:06:12

Last read 00:00:12, hold time is 180, keepalive interval is 60 seconds

Minimum time between advertisement runs is 30 seconds

Received 19 messages, 0 notifications, 0 in queue

Sent 17 messages, 0 notifications, 0 in queue

Inbound path policy configured

Route map for incoming advertisements is testing

Connections established 2; dropped 1

Connection state is ESTAB, I/O status: 1, unread input bytes: 0

Local host: 172.16.232.181, Local port: 11002

Foreign host: 172.16.232.178, Foreign port: 179

Enqueued packets for retransmit: 0, input: 0, saved: 0

Event Timers (current time is 0x530C294):

Timer          Starts    Wakeups            Next

Retrans            12          0             0x0

TimeWait            0          0             0x0

AckHold            12         10             0x0

SendWnd             0          0             0x0

KeepAlive           0          0             0x0

GiveUp              0          0             0x0

PmtuAger            0          0             0x0

iss:  133981889  snduna:  133982166  sndnxt:  133982166     sndwnd:  16108

irs: 3317025518  rcvnxt: 3317025810  rcvwnd:      16093  delrcvwnd:    291

SRTT: 441 ms, RTTO: 2784 ms, RTV: 951 ms, KRTT: 0 ms

minRTT: 0 ms, maxRTT: 300 ms, ACK hold: 300 ms

Flags: higher precedence, nagle

Datagrams (max data segment is 1460 bytes):

Rcvd: 15 (out of order: 0), with data: 12, total data bytes: 291

Sent: 23 (retransmit: 0), with data: 11, total data bytes: 276

Table 46 describes the fields shown in the display.

Table 46 show ip bgp neighbors Field Descriptions 

Field	Description
BGP neighbor	IP address of the BGP neighbor and its autonomous system number. If the neighbor is in the same autonomous system as the router, then the link between them is internal; otherwise, it is considered external.
BGP version	BGP version being used to communicate with the remote router; the neighbor's router ID (an IP address) is also specified.
BGP state	Internal state of this BGP connection.
table version	Indicates that the neighbor has been updated with this version of the primary BGP routing table.
up for	Amount of time that the underlying TCP connection has been in existence.
Last read	Time that BGP last read a message from this neighbor.
hold time	Maximum amount of time that can elapse between messages from the peer.
keepalive interval	Time period between sending keepalive packets, which help ensure that the TCP connection is up.
Received	Number of total BGP messages received from this peer, including keepalives.
notifications	Number of error messages received from the peer.
Sent	Total number of BGP messages that have been sent to this peer, including keepalives.
notifications	Number of error messages the router has sent to this peer.
Connections established	Number of times the router has established a TCP connection and the two peers have agreed speak BGP with each other.
dropped	Number of times that a good connection has failed or been taken down.
Connection state	State of BGP peer.
unread input bytes	Number of bytes of packets still to be processed.
Local host, Local port	Peering address of local router, plus port.
Foreign host, Foreign port	Neighbor's peering address.
Event Timers	Table displays the number of starts and wakeups for each timer.
iss	Initial send sequence number.
snduna	Last send sequence number the local host sent but has not received an acknowledgment for.
sndnxt	Sequence number the local host will send next.
sndwnd	TCP window size of the remote host.
irs	Initial receive sequence number.
rcvnxt	Last receive sequence number the local host has acknowledged.
rcvwnd	Local host's TCP window size.
delrecvwnd	Delayed receive window—data the local host has read from the connection, but has not yet subtracted from the receive window the host has advertised to the remote host. The value in this field gradually increases until it is larger than a full-sized packet, at which point it is applied to the rcvwnd field.
SRTT	A calculated smoothed round-trip timeout.
RTTO	Round-trip timeout.
RTV	Variance of the round-trip time.
KRTT	New round-trip timeout (using the Karn algorithm). This field separately tracks the round-trip time of packets that have been retransmitted.
minRTT	Smallest recorded round-trip timeout (hard wire value used for calculation).
maxRTT	Largest recorded round-trip timeout.
ACK hold	Time the local host will delay an acknowledgment in order to piggyback data on it.
Flags	IP precedence of the BGP packets.
Datagrams: Rcvd	Number of update packets received from neighbor.
with data	Number of update packets received with data.
total data bytes	Total bytes of data.
Sent	Number of update packets sent.
with data	Number of update packets with data sent.
total data bytes	Total number of data bytes.

route-map match statement

route-map match statement

http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a008047915d.shtml

Route-Map Basics

This is a typical Open Shortest Path First to Enhanced Interior Gateway Routing Protocol (OSPF-to-EIGRP) route-map, applied in a redistribute command:

!
router eigrp 1
 redistribute ospf 1 route-map ospf-to-eigrp
 default-metric 20000 2000 255 1 1500

!--- Output suppressed.

!
route-map ospf-to-eigrp deny 10
 match tag 6
 match route-type external type-2
!
route-map ospf-to-eigrp permit 20
 match ip address prefix-list pfx
 set metric 40000 1000 255 1 1500
!
route-map ospf-to-eigrp permit 30
 set tag 8
!

There are several points to note from this example:

• Route-map clauses are numbered. In this example, clauses have sequence numbers 10, 20, and 30. Sequence numbers allow you to do these actions:
  
  • Easily delete one specific clause but not affect other parts of the route-map.
  • Insert a new clause between two existing clauses.
  Cisco recommends that you number clauses in intervals of 10, to reserve numbering space in case you need to insert clauses in the future.
• Route-maps can have permit and deny clauses. In route-map ospf-to-eigrp, there is one deny clause (with sequence number 10) and two permit clauses. The deny clause rejects route matches from redistribution. Therefore, these rules apply:
  
  • If you use an ACL in a route-map permit clause, routes that are permitted by the ACL are redistributed.
  • If you use an ACL in a route-map deny clause, routes that are permitted by the ACL are not redistributed.
  • If you use an ACL in a route-map permit or deny clause, and the ACL denies a route, then the route-map clause match is not found and the next route-map clause is evaluated.
• Each route-map clause has two types of commands:
  
  • match—Selects routes to which this clause should be applied.

bgp attributes order

http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094431.shtml

How the Best Path Algorithm Works

BGP assigns the first valid path as the current best path. BGP then compares the best path with the next path in the list, until BGP reaches the end of the list of valid paths. This list provides the rules that are used to determine the best path:

1. Prefer the path with the highest WEIGHT.
   Note:  WEIGHT is a Cisco-specific parameter. It is local to the router on which it is configured.
   
2. Prefer the path with the highest LOCAL_PREF.
   Note: A path without LOCAL_PREF is considered to have had the value set with the bgp default local-preference command, or to have a value of 100 by default.
   
3. Prefer the path that was locally originated via a network or aggregate BGP subcommand or through redistribution from an IGP.
   Local paths that are sourced by the network or redistribute commands are preferred over local aggregates that are sourced by the aggregate-address command.
   
4. Prefer the path with the shortest AS_PATH.
   Note: Be aware of these items:
   
   • This step is skipped if you have configured the bgp bestpath as-path ignore command.
     
   • An AS_SET counts as 1, no matter how many ASs are in the set.
     
   • The AS_CONFED_SEQUENCE and AS_CONFED_SET are not included in the AS_PATH length.
     
5. Prefer the path with the lowest origin type.
   Note: IGP is lower than Exterior Gateway Protocol (EGP), and EGP is lower than INCOMPLETE.
   
6. Prefer the path with the lowest multi-exit discriminator (MED).
   Note: Be aware of these items:
   
   • This comparison only occurs if the first (the neighboring) AS is the same in the two paths. Any confederation sub-ASs are ignored.
     In other words, MEDs are compared only if the first AS in the AS_SEQUENCE is the same for multiple paths. Any preceding AS_CONFED_SEQUENCE is ignored.
     
   • If bgp always-compare-med is enabled, MEDs are compared for all paths.
     You must disable this option over the entire AS. Otherwise, routing loops can occur.
     
   • If bgp bestpath med-confed is enabled, MEDs are compared for all paths that consist only of AS_CONFED_SEQUENCE.
     These paths originated within the local confederation.
     
   • THE MED of paths that are received from a neighbor with a MED of 4,294,967,295 is changed before insertion into the BGP table. The MED changes to to 4,294,967,294.
     
   • Paths received with no MED are assigned a MED of 0, unless you have enabled bgp bestpath med missing-as-worst .
     If you have enabled bgp bestpath med missing-as-worst, the paths are assigned a MED of 4,294,967,294.
     
   • The bgp deterministic med command can also influence this step.
     Refer to How BGP Routers Use the Multi-Exit Discriminator for Best Path Selection for a demonstration.
     
7. Prefer eBGP over iBGP paths.
   If bestpath is selected, go to Step 9 (multipath).
   Note: Paths that contain AS_CONFED_SEQUENCE and AS_CONFED_SET are local to the confederation. Therefore, these paths are treated as internal paths. There is no distinction between Confederation External and Confederation Internal.
   
8. Prefer the path with the lowest IGP metric to the BGP next hop.
   Continue, even if bestpath is already selected.
   
9. Determine if multiple paths require installation in the routing table for BGP Multipath.
   Continue, if bestpath is not yet selected.
   
10. When both paths are external, prefer the path that was received first (the oldest one).
    This step minimizes route-flap because a newer path does not displace an older one, even if the newer path would be the preferred route based on the next decision criteria (Steps 11, 12, and 13).
    Skip this step if any of these items is true:
    
    • You have enabled the bgp best path compare-routerid command.
      Note: Cisco IOS Software Releases 12.0.11S, 12.0.11SC, 12.0.11S3, 12.1.3, 12.1.3AA, 12.1.3.T, and 12.1.3.E introduced this command.
      
    • The router ID is the same for multiple paths because the routes were received from the same router.
      
    • There is no current best path.
      The current best path can be lost when, for example, the neighbor that offers the path goes down.
      
11. Prefer the route that comes from the BGP router with the lowest router ID.
    The router ID is the highest IP address on the router, with preference given to loopback addresses. Also, you can use the bgp router-id command to manually set the router ID.
    Note: If a path contains route reflector (RR) attributes, the originator ID is substituted for the router ID in the path selection process.
    
12. If the originator or router ID is the same for multiple paths, prefer the path with the minimum cluster list length.
    This is only present in BGP RR environments. It allows clients to peer with RRs or clients in other clusters. In this scenario, the client must be aware of the RR-specific BGP attribute.
    
13. Prefer the path that comes from the lowest neighbor address.
    This address is the IP address that is used in the BGP neighbor configuration. The address corresponds to the remote peer that is used in the TCP connection with the local router.
    

eigrp passive interface

eigrp passive interface

http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080093f0a.shtml

With EIGRP running on a network, the passive-interface command stops both outgoing and incoming routing updates, since the effect of the command causes the router to stop sending and receiving hello packets over an interface.

OSPFv3 authentication

http://packetlife.net/blog/2008/sep/3/ospfv3-authentication/


Most IPv4 routing protocols support some form of neighbor authentication, provided by either a plaintext password or MD5 HMAC. However, OSPFv3 (OSPF for IPv6) doesn't include any authentication capabilities of its own; instead, it relies entirely on IPsec to secure communications between neighbors. This is beneficial in simplifying the OSPFv3 protocol and standardizing its authentication mechanism.

BGP Peer Groups

http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080093fb7.shtml

BGP Peer Groups

You can group BGP neighbors who share the same outbound policies together in what is called a BGP peer group. Instead of configuring each neighbor with the same policy individually, a peer group allows you to group the policies which can be applied to individual peers thus making efficient update calculation along with simplified configuration

Enabling OSPF for IPv6 on an Interface

http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-ospf.html#wp1075426

http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-ospf.html

Enabling OSPF for IPv6 on an Interface

Perform this task to enable OSPF for IPv6 routing and configure OSPF for IPv6 on each interface. By default, OSPF for IPv6 routing is disabled and OSPF for IPv6 is not configured on an interface.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. ipv6 ospf process-id area area-id [instance instance-id]

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	interface type number Example: Router(config)# interface ethernet 0/0	Specifies an interface type and number, and places the router in interface configuration mode.
Step 4	ipv6 ospf process-id area area-id [instanceinstance-id] Example: Router(config-if)# ipv6 ospf 1 area 0	Enables OSPF for IPv6 on an interface.

Address Import into OSPF for IPv6

http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-ospf.html#wp1069833

Address Import into OSPF for IPv6

When importing the set of addresses specified on an interface on which OSPF for IPv6 is running into OSPF for IPv6, users cannot select specific addresses to be imported. Either all addresses are imported, or no addresses are imported.

ospf stub area rules

http://www.cisco.com/en/US/tech/tk365/technologies_white_paper09186a0080094e9e.shtml

Stub Areas

OSPF allows certain areas to be configured as stub areas. External networks, such as those redistributed from other protocols into OSPF, are not allowed to be flooded into a stub area. Routing from these areas to the outside world is based on a default route. Configuring a stub area reduces the topological database size inside an area and reduces the memory requirements of routers inside that area.
An area could be qualified a stub when there is a single exit point from that area or if routing to outside of the area does not have to take an optimal path. The latter description is just an indication that a stub area that has multiple exit points, will have one or more area border routers injecting a default into that area. Routing to the outside world could take a sub-optimal path in reaching the destination by going out of the area via an exit point which is farther to the destination than other exit points.
Other stub area restrictions are that a stub area cannot be used as a transit area for virtual links. Also, an ASBR cannot be internal to a stub area. These restrictions are made because a stub area is mainly configured not to carry external routes and any of the above situations cause external links to be injected in that area. The backbone, of course, cannot be configured as stub.
All OSPF routers inside a stub area have to be configured as stub routers. This is because whenever an area is configured as stub, all interfaces that belong to that area will start exchanging Hello packets with a flag that indicates that the interface is stub. Actually this is just a bit in the Hello packet (E bit) that gets set to 0. All routers that have a common segment have to agree on that flag. If they don't, then they will not become neighbors and routing will not take effect.
An extension to stub areas is what is called "totally stubby areas". Cisco indicates this by adding a "no-summary" keyword to the stub area configuration. A totally stubby area is one that blocks external routes and summary routes (inter-area routes) from going into the area. This way, intra-area routes and the default of 0.0.0.0 are the only routes injected into that area

IPv6 Neighbor Discovery Protocol (NDP)

http://netcerts.net/wp-content/uploads/2010/10/IPV6_netcerts-ndp.jpg
http://fengnet.com/book/CCIE%20Professional%20Development%20Routing%20TCPIP%20Volume%20I/ch02lev1sec5.html

show ip ospf

http://www.cisco.com/en/US/docs/ios/12_3/iproute/command/reference/ip2_s3g.html#wp1036469

The following is sample output from the show ip ospf command when entered without a specific OSPF process ID:

Router# show ip ospf 

Routing Process "ospf 201" with ID 10.0.0.1 and Domain ID 10.20.0.1 

Supports only single TOS(TOS0) routes 

Supports opaque LSA 

SPF schedule delay 5 secs, Hold time between two SPFs 10 secs 

Minimum LSA interval 5 secs. Minimum LSA arrival 1 secs 

LSA group pacing timer 100 secs 

Interface flood pacing timer 55 msecs 

Retransmission pacing timer 100 msecs 

Number of external LSA 0. Checksum Sum 0x0      

Number of opaque AS LSA 0. Checksum Sum 0x0      

Number of DCbitless external and opaque AS LSA 0 

Number of DoNotAge external and opaque AS LSA 0 

Number of areas in this router is 2. 2 normal 0 stub 0 nssa 

External flood list length 0 

Area BACKBONE(0) 

Number of interfaces in this area is 2 

Area has message digest authentication 

SPF algorithm executed 4 times 

Area ranges are 

Number of LSA 4. Checksum Sum 0x29BEB  

Number of opaque link LSA 0. Checksum Sum 0x0      

Number of DCbitless LSA 3 

Number of indication LSA 0 

Number of DoNotAge LSA 0 

Flood list length 0 

Area 172.16.26.0 

Number of interfaces in this area is 0 

Area has no authentication 

SPF algorithm executed 1 times 

Area ranges are 

192.168.0.0/16 Passive Advertise  

Number of LSA 1. Checksum Sum 0x44FD   

Number of opaque link LSA 0. Checksum Sum 0x0      

Number of DCbitless LSA 1 

Number of indication LSA 1 

Number of DoNotAge LSA 0 

Flood list length 0

BGP NETWORK COMMAND

BGP NETWORK COMMAND
http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-ospf.html

The network command controls the networks that originate from this box. This concept is different than the familiar configuration with Interior Gateway Routing Protocol (IGRP) and RIP. With this command, you do not try to run BGP on a certain interface. Instead, you try to indicate to BGP what networks BGP should originate from this box. The command uses a mask portion because BGP version 4 (BGP4) can handle subnetting and supernetting. A maximum of 200 entries of the network command are acceptable.
The network command works if the router knows the network that you attempt to advertise, whether connected, static, or learned dynamically.
An example of the network command is:

RTA#
router bgp 1
network 192.213.0.0 mask 255.255.0.0
ip route 192.213.0.0 255.255.0.0 null 0

This example indicates that router A generates a network entry for 192.213.0.0/16. The /16 indicates that you use a supernet of the class C address and you advertise the first two octets, or first 16 bits.
Note: You need the static route to get the router to generate 192.213.0.0 because the static route puts a matching entry in the routing table.

Force SPF in OSPF for IPv6

Force SPF in OSPF for IPv6

When the process keyword is used with the clear ipv6 ospf command, the OSPF database is cleared and repopulated, and then the SPF algorithm is performed. When the force-spf keyword is used with the clear ipv6 ospf command, the OSPF database is not cleared before the SPF algorithm is performed. 

 http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-ospf.html

EIGRP Feasible distance , feasible successor

http://www.cisco.com/en/US/docs/ios/12_0/np1/command/reference/1reigrp.html#wp1021269

feasible distance is for the successor

feasible successor 's reported disance /advertised must be less than the feasible distance

show ip eigrp topology

( first number is the metric / second number is the metric advertise by its number)

http://www.techexams.net/forums/ccna-ccent/42562-successor-feasible-successor-eigrp.html

ipv6 NSAP ... is there still such address

ipv6 address is rapidly changing as well ....

aha..

unicast
link local
anycast


anyway, scarlett moved in with sum1 else , her link is gone...

clean up another fake alert virus

same strain again, disappoint about panda. there is a panda online activescan , no luck either.

uploaded some samples to n-able

malwarebyte's anti-malware still rocks

high cpu usage on an Acer aspire travelmate notebook

taskmgr shows about 50~60 cpu usage ...

use process explorer to check ... interrupts uses about that amount.

tried this and tried that,,,'

eventually caught glimpse of another user forum complaining a similar thing related to battery

pull the batt out, cpu usage dropped right away

interesting thing is the onbaord  kb/ mouse are not so responsive when cpu usage high, but external USB k/m are fine...

ddisable activedesktop in windows xp

http://www.pcauthorities.com/windows-xp/turn-off-windows-active-desktop/comment-page-1#comments


corrypted activedesktop may causing windows xp login freezing

1.From the Windows Start menu, select Run. In the Run box, type regedit and click OK.


2.In the Registry Editor, locate the following key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\

CurrentVersion\Policies\Explorer

3.Create a new DWORD Value with the name ClassicShell, and assign a value of 1 to it.

4.Close the Registry Editor. Select Exit from the File menu.

ip summary-address eigrp

ip summary-address eigrp

http://petespacket.com/2008/12/22/ip-summary-address-eigrp-as-number-ip-address-mask-admin-distance-leak-map-name/

Defaults

•An administrative distance of 5 is applied to Enhanced Interior Gateway Routing Protocol (EIGRP) summary routes.

•EIGRP automatically summarizes to the network level, even for a single host route.

•No summary addresses are predefined.

•The default administrative distance metric for EIGRP is 90.

 the summary path will point to null0

show ip bgp

http://www.powerfast.net/bgp/BGP_Nd50.html
router#show ip bgp 66.66.66.66

BGP routing table entry for 66.66.66.66/32

Paths: (2 available, best #1)

66.66.66.66/32

3 i comm 65535:65281

172.16.23.3 from 172.16.23.3 (peer 3.3.3.3)

Origin IGP, local pref 100, weight 0, valid, best

BGP Path Selection Criterion: Lowest BGP Neighbor Router-ID

IGP Metric: 0 IGP Pref: 0 IGP Protocol: DIRECT

IGP Next Hop: 0.0.0.0 Route Age: 0:03:22

66.66.66.66/32 (Second best)

77 i comm 65535:65281

172.16.12.1 from 172.16.12.1 (peer 172.16.12.1)

Origin IGP, local pref 100, weight 0, valid

IGP Metric: 0 IGP Pref: 0 IGP Protocol: DIRECT

IGP Next Hop: 0.0.0.0 Route Age: 0:02:21

router#

sh ip bgp summary

http://www.powerfast.net/bgp/BGP_Nd60.html

State	The current state of the session: Idle - ignore everything Connect - trying to connect Active - waiting for a connection OpenSent - open packet has been sent OpenConfirm - waiting for keepalive or notify Estab - connection has been established
PF Rcvd	Number of routes received from the specified neighbor

ccnp notes BGP ospf redistribution , ospf point-multipoint

when bgp is redistributed to ospf the default metric is 1, if its IGP it will be 20, type e2

ospf point-multi-point broadcast or non-broadcast , there is no dr/bdr, like a collection of point-2-point

mobile me got a problem? Brendon said so

mobile me got a problem? Brendon said so

Brendon used to have mobile me , now he said there were problems. funny that's the reason he didn't want sbs 2008.

now he is looking at hosted exchange

Docx extension on windows 2003 server ,

Office 2003 basic installed, some users tried to open as PDF , hence stuck there, have to add to local admin to change , then change back

dat file as attachment in email , this is wierdo

use notepad to open it, it is showing gibbersish, but showed something like pdf

so use pdf reader open it, it is fine

pdf complete ...

how do I copy the database over to another server , sql server 2008 R2 express

if you just copy raw databases like ldf mdf, then you need detach first then copy that thing over
then you can just re-attach it

Esther cannot access / display city council's exchange 2003 email owa properly

there is a problem with owa on the page, ...

use ccleaner to clean the page

then disable almot all ie add-ins

thing all good except i lost 5 bucks for not entering the u/p properly

642-902 lab BGP part 2 topology and configs

based on yesterdays topology upload , some modifications being made as Jeremy didn't advertise the external route link to internal

for some reason I can't attach files so I just pasted those here

R1 config
!
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R1
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
ip cef
!
!
!
!
no ip domain lookup
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback1
 ip address 1.1.1.1 255.255.255.255
!
interface FastEthernet0/0
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/0
 ip address 10.1.12.1 255.255.255.0
 clock rate 2000000
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/1
 ip address 10.1.13.1 255.255.255.0
 clock rate 2000000
!
interface Serial0/2
 no ip address
 shutdown
 clock rate 2000000
!
interface Serial0/3
 no ip address
 shutdown
 clock rate 2000000
!
router ospf 1
 log-adjacency-changes
 network 1.1.1.1 0.0.0.0 area 0
 network 10.1.0.0 0.0.255.255 area 0
!
router bgp 5500
 no synchronization
 bgp log-neighbor-changes
 neighbor 4.4.4.4 remote-as 5500
 neighbor 4.4.4.4 update-source Loopback1
 no auto-summary
!
!
!
no ip http server
no ip http secure-server
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
line con 0
 exec-timeout 0 0
 logging synchronous
line aux 0
line vty 0 4
 login
!
!
end

R4 configs
!
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R4
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
ip cef
!
!
!
!
no ip domain lookup
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback4
 ip address 4.4.4.4 255.255.255.255
!
interface FastEthernet0/0
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/0
 ip address 10.1.24.2 255.255.255.0
 clock rate 2000000
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/1
 ip address 10.1.34.2 255.255.255.0
 clock rate 2000000
!
interface Serial0/2
 ip address 10.1.45.1 255.255.255.0
 clock rate 2000000
!
interface Serial0/3
 no ip address
 shutdown
 clock rate 2000000
!
router ospf 1
 log-adjacency-changes
 network 4.4.4.4 0.0.0.0 area 0
 network 10.1.23.0 0.0.0.255 area 0
 network 10.1.24.0 0.0.0.255 area 0
 network 10.1.34.0 0.0.0.255 area 0
!
router bgp 5500
 no synchronization
 bgp log-neighbor-changes
 neighbor 1.1.1.1 remote-as 5500
 neighbor 1.1.1.1 update-source Loopback4
 neighbor 1.1.1.1 next-hop-self
 neighbor 5.5.5.5 remote-as 6500
 neighbor 5.5.5.5 ebgp-multihop 5
 neighbor 10.1.45.2 remote-as 6500
 no auto-summary
!
!
!
no ip http server
no ip http secure-server
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
line con 0
 exec-timeout 0 0
 logging synchronous
line aux 0
line vty 0 4
 login
!
!
end

R5 configs
!
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R4
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
ip cef
!
!
!
!
no ip domain lookup
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback4
 ip address 4.4.4.4 255.255.255.255
!
interface FastEthernet0/0
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/0
 ip address 10.1.24.2 255.255.255.0
 clock rate 2000000
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/1
 ip address 10.1.34.2 255.255.255.0
 clock rate 2000000
!
interface Serial0/2
 ip address 10.1.45.1 255.255.255.0
 clock rate 2000000
!
interface Serial0/3
 no ip address
 shutdown
 clock rate 2000000
!
router ospf 1
 log-adjacency-changes
 network 4.4.4.4 0.0.0.0 area 0
 network 10.1.23.0 0.0.0.255 area 0
 network 10.1.24.0 0.0.0.255 area 0
 network 10.1.34.0 0.0.0.255 area 0
!
router bgp 5500
 no synchronization
 bgp log-neighbor-changes
 neighbor 1.1.1.1 remote-as 5500
 neighbor 1.1.1.1 update-source Loopback4
 neighbor 1.1.1.1 next-hop-self
 neighbor 5.5.5.5 remote-as 6500
 neighbor 5.5.5.5 ebgp-multihop 5
 neighbor 10.1.45.2 remote-as 6500
 no auto-summary
!
!
!
no ip http server
no ip http secure-server
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
line con 0
 exec-timeout 0 0
 logging synchronous
line aux 0
line vty 0 4
 login
!
!
end


topology file same as previous
autostart = False
[127.0.0.1:7200]
    workingdir = working
    udp = 10000
    [[2691]]
        image = D:\IOS\c2691-entservicesk9-mz.124-13b.bin
        idlepc = 0x62283bc8
        ghostios = True
    [[ROUTER R4]]
        model = 2691
        console = 2003
        aux = 2100
        cnfg = configs\R4.cfg
        wic0/0 = WIC-2T
        wic0/1 = WIC-2T
        s0/0 = R2 s0/1
        s0/1 = R3 s0/1
        s0/2 = R5 s0/0
        x = -52.0
        y = -14.0
    [[ROUTER R1]]
        model = 2691
        console = 2000
        aux = 2101
        cnfg = configs\R1.cfg
        wic0/0 = WIC-2T
        wic0/1 = WIC-2T
        s0/0 = R2 s0/0
        s0/1 = R3 s0/0
        x = -172.0
        y = -149.0
    [[ROUTER R2]]
        model = 2691
        console = 2001
        aux = 2102
        cnfg = configs\R2.cfg
        wic0/0 = WIC-2T
        s0/0 = R1 s0/0
        s0/1 = R4 s0/0
        x = -186.0
        y = -14.0
    [[ROUTER R3]]
        model = 2691
        console = 2002
        aux = 2103
        cnfg = configs\R3.cfg
        wic0/0 = WIC-2T
        s0/0 = R1 s0/1
        s0/1 = R4 s0/1
        x = -42.0
        y = -152.0
[127.0.0.1:7201]
    workingdir = working
    udp = 10100
    [[2691]]
        image = D:\IOS\c2691-entservicesk9-mz.124-13b.bin
        idlepc = 0x62283bc8
        ghostios = True
    [[ROUTER R5]]
        model = 2691
        console = 2004
        aux = 2104
        cnfg = configs\R5.cfg
        wic0/0 = WIC-2T
        s0/0 = R4 s0/2
        x = 163.0
        y = -162.0
[GNS3-DATA]
    configs = configs
    workdir = working
    [[NOTE 1]]
        text = AS6500
        x = 181.0
        y = -67.0
    [[NOTE 2]]
        text = AS 5500
        x = -163.0
        y = 127.0
    [[NOTE 3]]
        text = s0/0
        x = -6.47356356195
        y = 28.4682130238
        interface = R3 s0/0
    [[NOTE 4]]
        text = s0/1
        x = 35.3915084294
        y = 61.9284445907
        interface = R3 s0/1
    [[NOTE 5]]
        text = s0/0
        x = 31.7593438286
        y = -17.9807550237
        interface = R2 s0/0
    [[NOTE 6]]
        text = s0/1
        x = 72.6315721092
        y = 16.5834981624
        interface = R2 s0/1
    [[NOTE 7]]
        text = s0/1
        x = 72.473563562
        y = 15.5317869762
        interface = R1 s0/1
    [[NOTE 8]]
        text = s0/0
        x = 34.2406561714
        y = 61.9807550237
        interface = R1 s0/0
    [[NOTE 9]]
        text = s0/0
        x = 1.84437745212
        y = 47.0863943933
        interface = R5 s0/0
    [[NOTE 10]]
        text = s0/2
        x = 64.1556225479
        y = -3.08639439326
        interface = R4 s0/2
    [[NOTE 11]]
        text = s0/1
        x = 30.6084915706
        y = -17.9284445907
        interface = R4 s0/1
    [[NOTE 12]]
        text = s0/0
        x = -6.63157210916
        y = 27.4165018376
        interface = R4 s0/0
    [[SHAPE 1]]
        type = ellipse
        x = -208.0
        y = -192.0
        width = 263.0
        height = 296.0
        border_style = 2
        z = -2.0

change office 2007 product key to re-activation after activated for std license

change office 2007 product key to re-activation after activated for std license

delete two reg keys

per link

http://support.microsoft.com/kb/895456

basic BGP lab files per cbt nugget Jeremy 642-902

BGP topo anyone?

well... I simulated Jeremy's basic bgp

here is the conf s

topology file
autostart = False
[127.0.0.1:7200]
    workingdir = working
    udp = 10000
    [[2691]]
        image = D:\IOS\c2691-entservicesk9-mz.124-13b.bin
        idlepc = 0x60d94004
        ghostios = True
    [[ROUTER R4]]
        model = 2691
        console = 2003
        cnfg = configs\R4.cfg
        wic0/0 = WIC-2T
        wic0/1 = WIC-2T
        s0/0 = R2 s0/1
        s0/1 = R3 s0/1
        s0/2 = R5 s0/0
        x = -52.0
        y = -14.0
    [[ROUTER R1]]
        model = 2691
        console = 2000
        cnfg = configs\R1.cfg
        wic0/0 = WIC-2T
        wic0/1 = WIC-2T
        s0/0 = R2 s0/0
        s0/1 = R3 s0/0
        x = -172.0
        y = -149.0
    [[ROUTER R2]]
        model = 2691
        console = 2001
        cnfg = configs\R2.cfg
        wic0/0 = WIC-2T
        s0/0 = R1 s0/0
        s0/1 = R4 s0/0
        x = -186.0
        y = -14.0
    [[ROUTER R3]]
        model = 2691
        console = 2002
        cnfg = configs\R3.cfg
        wic0/0 = WIC-2T
        s0/0 = R1 s0/1
        s0/1 = R4 s0/1
        x = -42.0
        y = -152.0
[127.0.0.1:7201]
    workingdir = working
    udp = 10100
    [[2691]]
        image = D:\IOS\c2691-entservicesk9-mz.124-13b.bin
        idlepc = 0x60d94004
        ghostios = True
    [[ROUTER R5]]
        model = 2691
        console = 2004
        cnfg = configs\R5.cfg
        wic0/0 = WIC-2T
        s0/0 = R4 s0/2
        x = 163.0
        y = -162.0
[GNS3-DATA]
    configs = configs
    workdir = working
    [[NOTE 1]]
        text = AS6500
        x = 181.0
        y = -67.0
    [[NOTE 2]]
        text = AS 5500
        x = -163.0
        y = 127.0
    [[NOTE 3]]
        text = s0/0
        x = 1.84437745212
        y = 47.0863943933
        interface = R5 s0/0
    [[NOTE 4]]
        text = s0/2
        x = 64.1556225479
        y = -3.08639439326
        interface = R4 s0/2
    [[NOTE 5]]
        text = s0/1
        x = 30.6084915706
        y = -17.9284445907
        interface = R4 s0/1
    [[NOTE 6]]
        text = s0/0
        x = -6.63157210916
        y = 27.4165018376
        interface = R4 s0/0
    [[NOTE 7]]
        text = s0/1
        x = 35.3915084294
        y = 61.9284445907
        interface = R3 s0/1
    [[NOTE 8]]
        text = s0/0
        x = -6.47356356195
        y = 28.4682130238
        interface = R3 s0/0
    [[NOTE 9]]
        text = s0/1
        x = 72.6315721092
        y = 16.5834981624
        interface = R2 s0/1
    [[NOTE 10]]
        text = s0/0
        x = 31.7593438286
        y = -17.9807550237
        interface = R2 s0/0
    [[NOTE 11]]
        text = s0/1
        x = 72.473563562
        y = 15.5317869762
        interface = R1 s0/1
    [[NOTE 12]]
        text = s0/0
        x = 34.2406561714
        y = 61.9807550237
        interface = R1 s0/0
    [[SHAPE 1]]
        type = ellipse
        x = -208.0
        y = -192.0
        width = 263.0
        height = 296.0
        border_style = 2
        z = -2.0

R1 config
!
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R1
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
ip cef
!
!
!
!
no ip domain lookup
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback1
 ip address 1.1.1.1 255.255.255.255
!
interface FastEthernet0/0
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/0
 ip address 10.1.12.1 255.255.255.0
 clock rate 2000000
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/1
 ip address 10.1.13.1 255.255.255.0
 clock rate 2000000
!
interface Serial0/2
 no ip address
 shutdown
 clock rate 2000000
!
interface Serial0/3
 no ip address
 shutdown
 clock rate 2000000
!
router ospf 1
 log-adjacency-changes
 network 1.1.1.1 0.0.0.0 area 0
 network 10.1.0.0 0.0.255.255 area 0
!
router bgp 5500
 no synchronization
 bgp log-neighbor-changes
 neighbor 4.4.4.4 remote-as 5500
 neighbor 4.4.4.4 update-source Loopback1
 no auto-summary
!
!
!
no ip http server
no ip http secure-server
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
line con 0
 exec-timeout 0 0
 logging synchronous
line aux 0
line vty 0 4
!
!
end

R2 config
!
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R2
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
ip cef
!
!
!
!
no ip domain lookup
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface FastEthernet0/0
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/0
 ip address 10.1.12.2 255.255.255.0
 clock rate 2000000
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/1
 ip address 10.1.24.1 255.255.255.0
 clock rate 2000000
!
router ospf 1
 log-adjacency-changes
 network 10.1.0.0 0.0.255.255 area 0
!
!
!
no ip http server
no ip http secure-server
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
line con 0
 exec-timeout 0 0
 logging synchronous
line aux 0
line vty 0 4
!
!
end

R3 config
!
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R3
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
ip cef
!
!
!
!
no ip domain lookup
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface FastEthernet0/0
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/0
 ip address 10.1.13.2 255.255.255.0
 clock rate 2000000
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/1
 ip address 10.1.34.1 255.255.255.0
 clock rate 2000000
!
router ospf 1
 log-adjacency-changes
 network 10.1.0.0 0.0.255.255 area 0
!
!
!
no ip http server
no ip http secure-server
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
line con 0
 exec-timeout 0 0
 logging synchronous
line aux 0
line vty 0 4
!
!
end

R4 config
!
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R4
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
ip cef
!
!
!
!
no ip domain lookup
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback4
 ip address 4.4.4.4 255.255.255.255
!
interface FastEthernet0/0
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/0
 ip address 10.1.24.2 255.255.255.0
 clock rate 2000000
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/1
 ip address 10.1.34.2 255.255.255.0
 clock rate 2000000
!
interface Serial0/2
 ip address 10.1.45.1 255.255.255.0
 clock rate 2000000
!
interface Serial0/3
 no ip address
 shutdown
 clock rate 2000000
!
router ospf 1
 log-adjacency-changes
 network 4.4.4.4 0.0.0.0 area 0
 network 10.1.0.0 0.0.255.255 area 0
!
router bgp 5500
 no synchronization
 bgp log-neighbor-changes
 neighbor 1.1.1.1 remote-as 5500
 neighbor 1.1.1.1 update-source Loopback4
 neighbor 5.5.5.5 remote-as 6500
 neighbor 5.5.5.5 ebgp-multihop 5
 neighbor 10.1.45.2 remote-as 6500
 no auto-summary
!
!
!
no ip http server
no ip http secure-server
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
line con 0
 exec-timeout 0 0
 logging synchronous
line aux 0
line vty 0 4
!
!
end

R5 config

!
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R5
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
memory-size iomem 5
ip cef
!
!
!
!
no ip domain lookup
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface Loopback5
 ip address 5.5.5.5 255.255.255.255
!
interface FastEthernet0/0
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/0
 ip address 10.1.45.2 255.255.255.0
 clock rate 2000000
!
interface FastEthernet0/1
 no ip address
 shutdown
 duplex auto
 speed auto
!
interface Serial0/1
 no ip address
 shutdown
 clock rate 2000000
!
router bgp 6500
 no synchronization
 bgp log-neighbor-changes
 neighbor 10.1.45.1 remote-as 5500
 no auto-summary
!
ip route 4.4.4.4 255.255.255.255 10.1.45.1
!
!
no ip http server
no ip http secure-server
!
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
line con 0
 exec-timeout 0 0
 logging synchronous
line aux 0
line vty 0 4
!
!
end