Mubarak: The biggest thief in the History of
Mankind
Only $ 620 billion
Finally, the bitter truth is emerging
Notices of the largest banks of the biggest thief in history of mankind
$ 620 billion, nearly four trillion Egyptian pounds
And not only $ 70 billion
If the money was divided equably among the 84 million population, every one
would be living in luxury. Every one would have fun, no hunger, no cold and no
disease. No wonder why Israel and the United States love him to death.
فقط 620 مليار
دولار وأخيراً بانت الحقيقة المرّةإشعارات البنوك لأكبر لص في التاريخ على مد
العصور 620 مليار دولار أي ما يقرب من أربعة ترليون جنيه مصري وليس فقط 70 مليار
أموال المصريين المنهوبة هيّ 4000000000000 (أي أربعة، أمامها 12 صفر) قسمها على 80
مليون نسمة. الناتج يكفي لكي يعيش كل مصري منغنغ في العز والرفاهية ومفيش جوع ومفيش
برد ومفيش مرض

اكبر حرامي في التاريخ البشري
CCNP Notes: Basic IGP Redistribution
In the continuing series of CCNP notes, I am documenting my Cisco
Certified Networking Professional (CCNP) studies and sharing my notes along the
way. I am using the Official CCNP Route 642-902 exam guide from Cisco, available
for purchase
here.
This post covers notes from Chapter 9 regarding Basic IGP Redistribution.
- IGP Redistribution
- Requires:
- One router have working links in each routing domain
- A working routing configuration for each routing domain
- Configuration of the redistribute command to tell the
router where to take routes and add to other routing protocol
- For redistribution, a common table is used between protocols: the
routing table
- Redistribution into EIGRP
- redistribute protocol [process-id|as-number]
[metric bw delay reliability load mtu]
[match {internal|nssa-external|external 1|external 2}]
[tag tag-value] [route-map name]
- Protocol: The protocol to redistribute from
- Process-id|as-number: The source process ID or AS number to
redistribute from
- Metric: Manually set metric data (k-values) on imported routes
- Match: If redistributing from OSPF, allows importing of only specific
types of routes
- Tag: Allows routes to be tagged and distributed to be filtered on by
other routers
- Route-map: Allows logic from a route-map to filter routes, set metrics
and set route tags
- When redistributing into EIGRP, just enabling the redistribution command
will in fact not redistribute any routes.
- There must be a metric defined for the routes, and that can be done in
one of three ways:
- Set a default-metric bw delay reliability load
mtu
- Use the metric bw delay reliability load mtu
redistribute subcommand
- Use route-map to set metrics based on matched
routes
- When routes are sourced from another EIGRP process, a default metric
will be set automatically
- Note that EIGRP defaults to an administrative distance of 170 for
external routes (90 for internal)
- Verifying redistribution: show ip eigrp topology
- Redistributing into OSPF
- redistribute protocol [process-id|as-number]
[metric metric-value] [metric-type {1|2}]
[match {internal|nssa-external|external 1|external 2}]
[tag tag-value] [route-map name]
[subnets]
- Protocol: The protocol to redistribute from
- Process-id|as-number: The source process ID or AS number to
redistribute from
- Metric: Manually set metric of the imported routes
- Metric-type: Import routes as E1 or E2 routes
- Match: If redistributing from OSPF, allows importing of only specific
types of routes
- Tag: Allows routes to be tagged and distributed to be filtered on by
other routers
- Route-map: Allows logic from a route-map to filter routes, set metrics
and set route tags
- Subnets: Redistribute routes of classful networks
- Default metrics:
- From BGP, default to 1
- From OSPF, use source route’s metric
- All other sources, use metric of 20
- Create a Type 5 LSA for routes if not inside NSSA
- If inside NSSA, create a Type 7 LSA
- Use external metric type 2
- Redistribute only routes of classful networks, not routes for subnets
- If default-metric OSPF subcommand is set, use this
- If metric parameter on redistribute
command is set, use this
- If route-map parameter on redistribute
command is set, apply from route-map
- External Type 2 Routes
- OSPF ignores the internal metric of a External Type 2 (E2) route. Any
other router that has access to the same route will tie the metric by
default. There is a tie-breaking process that OSPF undertakes to determine
which route to insert into the routing table
- Intra-area: For intra-area, OSPF chooses the lowest
cost ASBR path to reach the router that advertised the lowest E2 metric.
Example:
- Find the advertising ASBRs as listed in the Type 5 LSAs
- Calculate lowest cost route to reach ASBRs using intra-area LSDB
- Use outgoing interface and next hop based on best route to ASBR
- The route’s metric is unchanged, still listed as advertised in the
Type 5 LSA
- Interarea: When ASBRs exists in other areas, a more
complex method of calculating the tie-breaking path must be used.
- Calculate the cost to each ABR
- Then, calculate the cost from the ABR to the ASBR (as listed in
Type 4 LSAs)
- Type 4 LSAs: Advertised into an area from a ABR and
include the cost from the ABR to a ASBR
- External Type 1 OSPF routes have their metric
calculated by taking the external metric and adding the internal, OSPF-calculated,
metric to reach the ASBR (whereas External Type 1 routes only use this
type of logic in tie-breaking situations).
- OSPF always prefers E1 over E2 routes
- Redistribution is allowed on any router in any area, except routers in
Stubby areas and Totally Stubby areas.
- Routers in TSSA areas do not support Type 5 LSAs, but use Type 7
LSAs to redistribute routes




Videos:
Watch ثروة اللص مبارك و عائلته patrimoine de hosni moubarak via YouTube Online
Watch تقرير عن
ثروة مبارك. via YouTube Online