If you have passed your CCIE Lab exam and used any of IPexpert’s training products including Self-study Material, Video on Demand, Audio on Demand, Rack Rental, or even one of our free vLecture’s and you don’t see your name on the list we want to hear from you! It doesn’t matter if you purchased the material from us or borrowed it from a friend just let us know what you thought about the material be visiting http://www.ipexpert.com/products/review or email CCIE@ipexpert.com with your Name and CCIE# and we will send you a free shirt seen below that will have your name and CCIE# in the list of Top Guns!

Print Friendly

Join IPexpert’s Live Online CCIE R&S 4.0 Written Exam and Lab Fundamental Bootcamp delivered by renowned Cisco Instructor and Cisco Press author, Anthony Sequeira. This one-of-a-kind bootcamp takes you beyond passing your CCIE Written Exam and into the Lab Fundamentals needed to be successful in passing the CCIE R&S Lab. Enjoy 2 months of interactive, live, online sessions with highly respected CCIE Instructors. All courses will be recorded and can be viewed on iPad/iPhone at later dates, as many times as needed.

With Special Guest Instructors:

• Marko Milivojevic  CCIE #18427 (R&S, SP)
• Vikram Malhi CCIE #13890 (Voice)
• Scott Morris CCIE #4713 (R&S, ISP-Dial, Security,SP)
• Narbik Kocharians CCSI, CCIE #12410 (R&S, Security, SP)
• And More…

Introducing the CCIE R&S Lab Fundamentals and Written Exam Bootcamp!

Materials Provided:

• Slide PDF workbook for note taking and review
• Full practice exam delivered during Final Exam Week
• 24 x 7 access to all recorded class sessions

Mentoring:

• 30 minute one-on-one call with instructor; scheduled during the two month event; additional one-on-one’s available as needed
• 24 x 7 one-on-one email access Private Facebook group
• Facebook and/or Skype chat access with class instructor

Schedule

NOTE: All sessions include Troubleshooting for the respective technology covered in that class.

• Tuesday, November 1, 2011: Topic: Implement Layer 2 Technologies
• Thursday, November 3, 2011: Topic: Implement Layer 2 Technologies
• Tuesday, November 8, 2011: Topic: Implement IPv4
• Thursday, November 10, 2011: Topic: Implement IPv4
• Tuesday, November 29, 2011: Topic: Implement IPv6
• Thursday, December 1, 2011: Topic: Implement MPLS Layer 3 VPNs
• Tuesday, December 6, 2011: Topic: Implement IP Multicast
• Thursday, December 8, 2011: Topic: Implement Network Security
• Tuesday, December 13, 2011: Topic: Implement Network Services
• Thursday, December 15, 2011: Topic: Implement Quality of Service
• Tuesday, December 20, 2011: Topic: Optimize the Network
• Tuesday, December 20, 2011: Topic: Final Exam Week

*All classes are scheduled for 8:00 – 10:00 PM EST.

Class Begins November 1st, 2011

Register Today at a Price You Can Afford $349

Print Friendly

• Initial set up of a Cisco Unified Communications Manager cluster
• CUCM redundancy designs
• Requirements for CUCM use of SHCP, TFTP, DNS, and NTP
• Determine necessary services to support CUCM deployment
• Describe and configure CUCM to support on-cluster calling
• Configure a CUCM group
• Configure CUCM profiles and device pools
• Configure CUCM templates
• Auto-Registered Phones Support functionality
• Describe and configure route plan for CUCM to support off-net calling
• Configure route patterns
• Configure Route lists and route groups
• Implement toll-fraud prevention
• Describe and configure CUCM media resources
• Configure music on hold
• Configure Cisco Unified Mobility

Matt Just – IPexpert, Inc.

Print Friendly

Matt Just – IPexpert, Inc.

Print Friendly

IPexpert’s Video On Demand training products will change the way clients study. These products are offered in a variety of convenient study methods and are complete with the most current and relevant information. IPexpert updates all material continually to ensure clients get the most up-to-date information possible.

CCNP Wireless Video on Demand Course (CUWSS, IUWVN, IUWMS, IAUWS) material contains detailed lecture topics on advanced networking technologies. These expert level Video on Demand courses assist network professionals in developing skills to plan, operate and troubleshoot complex network infrastructures. We currently offer the CCIE Lab Video on Demand in the CCIE R&S, Security, Wireless and Routing and Switching Track. With over 1,800 successful CCIE’s we are confident that you will be satisfied with our comprehensive video training solution.

Below, you will find the topics, technologies and protocols that are currently included in IPexpert’s CCNP Wireless Video on Demand series. We’re quite confident that you won’t find a more thorough, up-to-date product on the market!

CCNP CUWSS Video on Demand (642-731) is an information-rich, concise video training containing detailed questions and solutions on topics seen on the Conducting Cisco Unified Wireless Site Survey exam. With hours of detailed lecture by IPexpert’s industry recognized Instructors, CCNP Wireless candidates will be confident in a CUWSS exam attempt. Enjoy this comprehensive video training solution from the comfort of your own home.

CCNP IUWVN Video on Demand (642-741) consists of detailed lecture on topics such as call setup and data flow, SCCP and SIP, cell separations and more. IPexpert’s CCNP IUWVN Video on Demand course offers CCNP Wireless candidates the “how to” in integrating VoWLAN services into the WLAN and is frequently reviewed to ensure that it is up to date and meets the latest topics tested on the CCNP exam.

CCNP IUWMS Video on Demand (642-746) allows CCNP Wireless candidates to study complex technologies found on the CCNP Wireless exam from the comfort of their home. This VOD contains detailed lecture on integrating mobility services into the WLAN. All CCNP Wireless Video on Demand courses are kept up to date to the current exam blueprints. CCNP Wireless candidates will develop the knowledge and skills to allow them to confidently take and pass the CCNP IUWMS exam.

CCNP IAUWS Video on Demand (642-736) contains detailed lecture on topics on securing wireless networks from security threats. VOD topics include configuring the CSSC, understanding the architectures, as well as configuring the WLC for NAC. We are confident that you won’t find a more thorough Video on Demand Course on the market. CCNP Wireless candidates will develop the knowledge and skills to allow them to confidently take and pass the CCNP IAUWS exam.

Matt Just – IPexpert, Inc.

Print Friendly

Below, you will find the topics, technologies and protocols that are currently included in IPexpert’s CCNP to CCIE Security Transition Kit. We’re quite confident that you won’t find a more thorough, up-to-date product on the market!

• Pre-product Design
• Choosing Cisco IOS technologies to implement HDL
• Integrate Cisco network security solutions with other features
• Configure and verify ASA VPN feature configurations
• Optimize Cisco IOS security infrastructure device performance
• Complex network security rules
• Configure and verify Classic IOS Firewall and NAT
• Maintain, update and tune IPS signatures
• Configure and verify IOS VPN features
• ASA Perimeter Security technologies and features
• Implement HLD based on given security requirements
• Create and test initial ASA appliance configurations using CLI
• Determine ASA licenses
• Perform initial setup on the AIP-SSM and CSC-SSM using CLI or ASDM
• Troubleshoot High Availability ASAs
• Verify static routing and dynamic routing protocols
• Integrate ASA VPN solutions with other security technologies
• Optimize ASA VPN performance, functions, and configurations
• Create complex ASA network security rules and More

The Transition Kit was developed to assist students in diving deeper into core concepts such as Pre-product Design, Choosing Cisco IOS technologies to implement HDL, Integrate Cisco network security solutions with other features, Configure and verify ASA VPN feature configurations, Optimize Cisco IOS security infrastructure device performance, Complex network security rules, Configure and verify Classic IOS Firewall and NAT, Maintain, update and tune IPS signatures, Configure and verify IOS VPN features, ASA Perimeter Security technologies and features, Implement HLD based on given security requirements, Create and test initial ASA appliance configurations using CLI, Determine ASA licenses, Perform initial setup on the AIP-SSM and CSC-SSM using CLI or ASDM, Troubleshoot High Availability ASAs, Verify static routing and dynamic routing protocols, Integrate ASA VPN solutions with other security technologies, Optimize ASA VPN performance, functions, and configurations, and Create complex ASA network security rules and others found on the CCNP Security Lab exam. Upon completion of the CCNP to CCIE Transition Kits students should be prepared enough to sit in a CCIE Security Bootcamp course. The detailed Transition Kit eBook is a thorough breakdown of all tasks and solutions with explanations and tips that guide clients through these challenging lab scenarios.

There is a reason why Cisco has the most popular IT Certifications in the industry. There is also a reason why IPexpert is the leader in Cisco training. So what will your certification be? When will you decide to take your career to the next level and become an IPexpert?

Matt Just – IPexpert, Inc.

Print Friendly

Bridging the Gap Between CCNP (R&S) to the CCIE (R&S) Lab

For over 10 years, IPexpert has been helping engineers pass the dreaded and coveted CCIE Lab exam. One of the common questions our students often ask is, “How do I begin my lab preparation if I’ve got text-book knowledge of various topics”. For over a decade we’ve given our clients a Structured Learning Approach, which introduces several products, in a specific sequential order, based on the student’s technical knowledge and experience.  We are now excited to announce a new product, which helps CCNP-level students bridge the gap between the traditional CCNP space to the hands-on CCIE lab arena – IPexpert’s CCNP (R&S) to CCIE (R&S) Transition Kit.

IPexpert’s CCNP to CCIE R&S Transition Kit is designed for CCIE R&S candidates who wish to bridge the gap between CCNP and CCIE Routing & Switching. Learn about the protocols and technologies included in the exam blueprint at your own pace with IPexpert’s comprehensive Transition Kit eBook.

The Transition Kit was developed to assist students in diving deeper into core concepts such as Implementing EIGRP Routing, Implement a Multi-Area OSPF Routing, Implement eBGP Routing, Implement IPv6, Implement an IPv4 or IPv6 Redistribution Solution, Implement Layer 3 Path Control, Implement a VLAN Based Solution, Implement a Security Extension of a Layer 2 Solution, Implement Switch Based Layer 3 Services, Prepare Infrastructure to Support Advanced Services, Implement High Availability, Maintain and Monitor Network Performance, and Troubleshoot Multi Protocol System Networks, and Layer 3 Path Control and others found on the CCNP R&S Lab exam.  Upon completion of the CCNP to CCIE Transition Kit, students should be prepared enough to then jump into the proven methodology, known as IPexpert’s Structured Learning Approach. The Transition Kit is a thorough breakdown of all tasks and solutions with explanations and tips that guide clients through these challenging lab scenarios.

At IPexpert, we take great pride in being known as the industry’s most up-to-date and thorough Cisco training provider. We guarantee that all training materials we ship to our clients are current and up-to-date, reflecting all of the topics that are outlined on the most recent blueprint. If, at any time, you have questions pertaining to our content, we invite you to contact one of our Training Advisors who will be happy to assist you in creating a customized study plan that fits your learning preferences and your training budget.

Below, you will find the topics, technologies and protocols that are currently included in IPexpert’s CCNP to CCIE R&S Transition Kit.

• Implementing EIGRP Based Solutions
• Implement a Multi-Area OSPF Routing
• Implement eBGP Routing
• Implement IPv6
• Implement an IPv4 or IPv6 Redistribution Solution
• Implement Layer 3 Path Control
• Implement a VLAN Based Solution
• Implement a Security Extension of a Layer 2 Solution
• Implement Switch Based Layer 3 Services
• Prepare Infrastructure to Support Advanced Services
• Implement High Availability
• Maintain and Monitor Network Performance
• Troubleshoot Multi-Protocol System Networks

This week, August 8th, 2011 through August 12th, 2011 we are offering our blog readers a 50% discount off of this product’s list price. To receive your promotional discount, be sure to enter: PRODOFWEEK88 when making your online purchase here: http://www.ipexpert.com/Cisco/CCIE/Routing-and-Switching/Transition-Kit/CCNP-to-CCIE

Whether you’re just beginning your CCIE R&S Lab preparation and need some detailed guidance, if your CCIE studies have stalled, or if you need some additional work in one of the covered technologies included in this workbook, we feel confident that this unique product can get you back on track!

For more information, please visit the following links:

• CCNP to CCIE Routing and Switching Transition Kit Product Data Sheet
• Download a Sample of IPexpert’s CCNP to CCIE R&S Transition Kit
• View or purchase the Transition Kit with a 50% discount today

NOTICES for this special offer:

• Your purchase must be done online, and be made with the coupon code: PRODOFWEEK88 in order to be eligible for a 50% discount.
• Your purchase must be made before 5:00 PM EST Friday August 12th.
• Promotion not to be combined with other offers. Valid for new purchases only.

Print Friendly

To examine Network LSA, we will focus on area 0 and the connection between R1 and R2. As mentioned in the description of the network, this is a shared Ethernet segment, with R1 as the DR. Before we continue, let’s just quickly confirm the facts.

R1:

R1#show ipv6 ospf interface brief
Interface    PID   Area            Intf ID    Cost  State Nbrs F/C
Fa0/0        1     0               4          1     DR    1/1
Lo0          1     0               11         1     LOOP  0/0

R2:

R2#show ipv6 ospf neighbor

Neighbor ID     Pri   State           Dead Time   Interface ID    Interface
5.5.5.5           1   FULL/  -        00:00:31    10              Serial0/2/0
1.1.1.1         255   FULL/DR         00:00:33    4               GigabitEthernet0/0
6.6.6.6           1   FULL/  -        00:01:55    6               Serial0/1/0

Since R1 is the DR, it should also be the router to generate Type 2002 (Network) LSA and represent this shared network to the rest of the world. Let’s take a look. We will look into the database as seen by R5.

R5:

R5#show ipv6 ospf database network

            OSPFv3 Router with ID (5.5.5.5) (Process ID 1)

                Net Link States (Area 0)

  LS age: 1476
  Options: (V6-Bit, E-Bit, R-bit, DC-Bit)
  LS Type: Network Links
  Link State ID: 4 (Interface ID of Designated Router)
  Advertising Router: 1.1.1.1
  LS Seq Number: 80000007
  Checksum: 0x25C9
  Length: 32
        Attached Router: 1.1.1.1
        Attached Router: 2.2.2.2

From the output highlighted red We can indeed see that Type 2002 LSA with ID “4″ has been originated by R1. Highlighted green are the attached routers. We can see that no IPv6 prefixes are mentioned here. The reason for this is the same as it was with Type 2001. In order to optimize SPF calculations, prefixes are not carried in Type 2002, but instead in Type 2009 (Intra-Area-Prefix) LSA. Let’s take a look at that.

R5:

R5#show ipv6 ospf database prefix adv-router 1.1.1.1

            OSPFv3 Router with ID (5.5.5.5) (Process ID 1)

                Intra Area Prefix Link States (Area 0)

  Routing Bit Set on this LSA
  LS age: 1755
  LS Type: Intra-Area-Prefix-LSA
  Link State ID: 0
  Advertising Router: 1.1.1.1
  LS Seq Number: 80000009
  Checksum: 0x6420
  Length: 52
  Referenced LSA Type: 2001
  Referenced Link State ID: 0
  Referenced Advertising Router: 1.1.1.1
  Number of Prefixes: 1
  Prefix Address: 2001:DB8::1
  Prefix Length: 128, Options: LA, Metric: 0

  Routing Bit Set on this LSA
  LS age: 1755
  LS Type: Intra-Area-Prefix-LSA
  Link State ID: 4096
  Advertising Router: 1.1.1.1
  LS Seq Number: 80000007
  Checksum: 0x8129
  Length: 44
  Referenced LSA Type: 2002
  Referenced Link State ID: 4
  Referenced Advertising Router: 1.1.1.1
  Number of Prefixes: 1
  Prefix Address: 2001:DB8:12::
  Prefix Length: 64, Options: None, Metric: 0

In the above output, again from R5, red highlight shows LSA originated by R1 that references LSA Type 2002, originated by R1 with the ID “4″. Prefixes associated with this LSA are shown with cyan highlight.

There is one important thing to notice with Type 2002 LSA in OSPFv3. The prefix for the shared segment is advertised only by the designated router and not by any other attached routers. See output from R5 below.

R5:

R5#show ipv6 ospf database prefix adv-router 1.1.1.1

            OSPFv3 Router with ID (5.5.5.5) (Process ID 1)

                Intra Area Prefix Link States (Area 0)

  Routing Bit Set on this LSA
  LS age: 1034
  LS Type: Intra-Area-Prefix-LSA
  Link State ID: 0
  Advertising Router: 1.1.1.1
  LS Seq Number: 8000000A
  Checksum: 0x6221
  Length: 52
  Referenced LSA Type: 2001
  Referenced Link State ID: 0
  Referenced Advertising Router: 1.1.1.1
  Number of Prefixes: 1
  Prefix Address: 2001:DB8::1
  Prefix Length: 128, Options: LA, Metric: 0

  Routing Bit Set on this LSA
  LS age: 1034
  LS Type: Intra-Area-Prefix-LSA
  Link State ID: 4096
  Advertising Router: 1.1.1.1
  LS Seq Number: 80000008
  Checksum: 0x7F2A
  Length: 44
  Referenced LSA Type: 2002
  Referenced Link State ID: 4
  Referenced Advertising Router: 1.1.1.1
  Number of Prefixes: 1
  Prefix Address: 2001:DB8:12::
  Prefix Length: 64, Options: None, Metric: 0

R5#show ipv6 ospf database prefix adv-router 2.2.2.2

            OSPFv3 Router with ID (5.5.5.5) (Process ID 1)

                Intra Area Prefix Link States (Area 0)

  Routing Bit Set on this LSA
  LS age: 1125
  LS Type: Intra-Area-Prefix-LSA
  Link State ID: 0
  Advertising Router: 2.2.2.2
  LS Seq Number: 80000013
  Checksum: 0xC90E
  Length: 64
  Referenced LSA Type: 2001
  Referenced Link State ID: 0
  Referenced Advertising Router: 2.2.2.2
  Number of Prefixes: 2
  Prefix Address: 2001:DB8::2
  Prefix Length: 128, Options: LA, Metric: 0
  Prefix Address: 2001:DB8:25::
  Prefix Length: 64, Options: None, Metric: 64

If we check the routing table for 2001:db8:12::/64 on R5, we get the correct metric of 65:

R5:

R5#show ipv6 route 2001:db8:12::/64
Routing entry for 2001:DB8:12::/64
  Known via "ospf 1", distance 110, metric 65, type intra area
  Route count is 1/1, share count 0
  Routing paths:
    FE80::218:19FF:FEF3:42B0, Serial0/2/0
      Last updated 05:18:41 ago

The reason for the correct metric calculation is information contained in Router LSA, which includes a reference to the shared link, with the correct metric, advertised by R2. Take a look:

R5:

R5#show ipv6 ospf database router adv-router 2.2.2.2

            OSPFv3 Router with ID (5.5.5.5) (Process ID 1)

                Router Link States (Area 0)

  Routing Bit Set on this LSA
  LS age: 1293
  Options: (V6-Bit, E-Bit, R-bit, DC-Bit)
  LS Type: Router Links
  Link State ID: 0
  Advertising Router: 2.2.2.2
  LS Seq Number: 8000001E
  Checksum: 0xABA9
  Length: 56
  Area Border Router
  AS Boundary Router
  Number of Links: 2

    Link connected to: another Router (point-to-point)
      Link Metric: 64
      Local Interface ID: 8
      Neighbor Interface ID: 10
      Neighbor Router ID: 5.5.5.5

    Link connected to: a Transit Network
      Link Metric: 1
      Local Interface ID: 2
      Neighbor (DR) Interface ID: 4
      Neighbor (DR) Router ID: 1.1.1.1

This concludes the intra-area related posts in this series. Next time, we’ll explore how routers exchange the information between areas. In other words, we’ll take a look at Inter-Area-Prefix LSA>

Happy studies!

–
Marko Milivojevic – CCIE #18427
Senior Technical Instructor – IPexpert
Join our Online Study List

Print Friendly

Matt Just – IPexpert, Inc.

Print Friendly

The Test Network

The test network we’ll work on is shown on the diagram below. We will be using this same network throughout this series.

We can see on the diagram that routers R1, R2 and R5 are backbone (area 0) routers, with R2 and R5 being ABRs, too. R2 is connected to R6 over Frame Relay interface in NSSA area 26 and R5 is connected to R4 in area 45 over a point-to-point serial interface. Routers R4 and R6 are also ASBRs. All routers are statically configured with OSPF Router-ID in the R.R.R.R format, where R is the router number (R1′s Router ID will be 1.1.1.1).

Here are the relevant configurations for all the routers.

R1:

interface Loopback0
 ipv6 address 2001:DB8::1/128
 ipv6 ospf 1 area 0
!
interface FastEthernet0/0
 ipv6 address 2001:DB8:12::1/64
 ipv6 ospf priority 255
 ipv6 ospf 1 area 0
!
ipv6 router ospf 1
 router-id 1.1.1.1
!

R2:

interface Loopback0
 ipv6 address 2001:DB8::2/128
 ipv6 ospf 1 area 0
!
interface GigabitEthernet0/0
 ipv6 address 2001:DB8:12::2/64
 ipv6 ospf priority 0
 ipv6 ospf 1 area 0
!
interface Serial0/1/0
 encapsulation frame-relay
 ipv6 address FE80::2 link-local
 ipv6 address 2001:DB8:26::2/64
 ipv6 ospf network point-to-multipoint
 ipv6 ospf 1 area 26
 frame-relay map ipv6 2001:DB8:26::6 206
 frame-relay map ipv6 2001:DB8:26::2 206
 frame-relay map ipv6 FE80::6 206 broadcast
 no frame-relay inverse-arp
!
interface Serial0/2/0
 ipv6 address 2001:DB8:25::2/64
 ipv6 ospf 1 area 0
!
ipv6 router ospf 1
 router-id 2.2.2.2
 area 26 nssa default-information-originate
!

R4:

interface Loopback0
 ipv6 address 2001:DB8::4/128
 ipv6 ospf 1 area 45
!
interface Loopback4
 ipv6 address 2001:DB8:4::4/64
!
interface Serial0/1/0
 ipv6 address 2001:DB8:45::4/64
 ipv6 ospf 1 area 45
!
ipv6 router ospf 1
 router-id 4.4.4.4
 redistribute connected route-map CON-to-OSPF
!
route-map CON-to-OSPF permit 10
 match interface Loopback4
!

R5:

interface Loopback0
 ipv6 address 2001:DB8::5/128
 ipv6 ospf 1 area 0
!
interface Serial0/0/0
 ipv6 address 2001:DB8:45::5/64
 ipv6 ospf 1 area 45
!
interface Serial0/2/0
 ipv6 address 2001:DB8:25::5/64
 ipv6 ospf 1 area 0
!

R6:

interface Loopback0
 ipv6 address 2001:DB8::6/128
 ipv6 ospf 1 area 26
!
interface Loopback6
 ipv6 address 2001:DB8:6::6/64
!
interface Serial0/1/0
 encapsulation frame-relay
 ipv6 address FE80::6 link-local
 ipv6 address 2001:DB8:26::6/64
 ipv6 ospf network point-to-multipoint
 ipv6 ospf 1 area 26
 frame-relay map ipv6 2001:DB8:26::2 602
 frame-relay map ipv6 2001:DB8:26::6 602
 frame-relay map ipv6 FE80::2 602 broadcast
 no frame-relay inverse-arp
!
ipv6 router ospf 1
 router-id 6.6.6.6
 area 26 nssa
 redistribute connected route-map CON-to-OSPF
!
route-map CON-to-OSPF permit 10
 match interface Loopback6
!

We’ll quickly run the verification script to ensure that everything in our network is reachable. This should work from any device in the network, but I will run the test from R6.

R6:

R6#tclsh
R6(tcl)#foreach ip {
+>(tcl)#2001:db8::1
+>(tcl)#2001:db8::2
+>(tcl)#2001:db8::4
+>(tcl)#2001:db8::5
+>(tcl)#2001:db8::6
+>(tcl)#2001:db8:12::1
+>(tcl)#2001:db8:12::2
+>(tcl)#2001:db8:25::2
+>(tcl)#2001:db8:25::5
+>(tcl)#2001:db8:45::4
+>(tcl)#2001:db8:45::5
+>(tcl)#2001:db8:26::2
+>(tcl)#2001:db8:26::6
+>(tcl)#2001:db8:4::4
+>(tcl)#2001:db8:6::6
+>(tcl)#} { ping $ip so lo0 repe 3 time 1 }

Type escape sequence to abort.
Sending 3, 100-byte ICMP Echos to 2001:DB8::1, timeout is 1 seconds:
Packet sent with a source address of 2001:DB8::6
!!!
Success rate is 100 percent (3/3), round-trip min/avg/max = 20/20/20 ms
Type escape sequence to abort.
Sending 3, 100-byte ICMP Echos to 2001:DB8::2, timeout is 1 seconds:
Packet sent with a source address of 2001:DB8::6
!!!
Success rate is 100 percent (3/3), round-trip min/avg/max = 20/20/20 ms
Type escape sequence to abort.
Sending 3, 100-byte ICMP Echos to 2001:DB8::4, timeout is 1 seconds:
Packet sent with a source address of 2001:DB8::6
!!!
Success rate is 100 percent (3/3), round-trip min/avg/max = 20/21/24 ms
Type escape sequence to abort.
Sending 3, 100-byte ICMP Echos to 2001:DB8::5, timeout is 1 seconds:
Packet sent with a source address of 2001:DB8::6
!!!
Success rate is 100 percent (3/3), round-trip min/avg/max = 20/21/24 ms
Type escape sequence to abort.
Sending 3, 100-byte ICMP Echos to 2001:DB8::6, timeout is 1 seconds:
Packet sent with a source address of 2001:DB8::6
!!!
Success rate is 100 percent (3/3), round-trip min/avg/max = 0/1/4 ms
Type escape sequence to abort.
Sending 3, 100-byte ICMP Echos to 2001:DB8:12::1, timeout is 1 seconds:
Packet sent with a source address of 2001:DB8::6
!!!
Success rate is 100 percent (3/3), round-trip min/avg/max = 20/20/20 ms
Type escape sequence to abort.
Sending 3, 100-byte ICMP Echos to 2001:DB8:12::2, timeout is 1 seconds:
Packet sent with a source address of 2001:DB8::6
!!!
Success rate is 100 percent (3/3), round-trip min/avg/max = 16/18/20 ms
Type escape sequence to abort.
Sending 3, 100-byte ICMP Echos to 2001:DB8:25::2, timeout is 1 seconds:
Packet sent with a source address of 2001:DB8::6
!!!
Success rate is 100 percent (3/3), round-trip min/avg/max = 16/18/20 ms
Type escape sequence to abort.
Sending 3, 100-byte ICMP Echos to 2001:DB8:25::5, timeout is 1 seconds:
Packet sent with a source address of 2001:DB8::6
!!!
Success rate is 100 percent (3/3), round-trip min/avg/max = 20/21/24 ms
Type escape sequence to abort.
Sending 3, 100-byte ICMP Echos to 2001:DB8:45::4, timeout is 1 seconds:
Packet sent with a source address of 2001:DB8::6
!!!
Success rate is 100 percent (3/3), round-trip min/avg/max = 20/21/24 ms
Type escape sequence to abort.
Sending 3, 100-byte ICMP Echos to 2001:DB8:45::5, timeout is 1 seconds:
Packet sent with a source address of 2001:DB8::6
!!!
Success rate is 100 percent (3/3), round-trip min/avg/max = 20/20/20 ms
Type escape sequence to abort.
Sending 3, 100-byte ICMP Echos to 2001:DB8:26::2, timeout is 1 seconds:
Packet sent with a source address of 2001:DB8::6
!!!
Success rate is 100 percent (3/3), round-trip min/avg/max = 20/20/20 ms
Type escape sequence to abort.
Sending 3, 100-byte ICMP Echos to 2001:DB8:26::6, timeout is 1 seconds:
Packet sent with a source address of 2001:DB8::6
!!!
Success rate is 100 percent (3/3), round-trip min/avg/max = 0/1/4 ms
Type escape sequence to abort.
Sending 3, 100-byte ICMP Echos to 2001:DB8:4::4, timeout is 1 seconds:
Packet sent with a source address of 2001:DB8::6
!!!
Success rate is 100 percent (3/3), round-trip min/avg/max = 20/21/24 ms
Type escape sequence to abort.
Sending 3, 100-byte ICMP Echos to 2001:DB8:6::6, timeout is 1 seconds:
Packet sent with a source address of 2001:DB8::6
!!!
Success rate is 100 percent (3/3), round-trip min/avg/max = 0/0/0 ms

The network is fully functional! Let’s dive and explore the LSAs…

Router (Type 2001) LSA

Similarly to OSPFv2 used for IPv4 routing, OSPFv3 uses Router LSA to inform routers in the area about its presence and available links. However, as we’ll see, contents of this LSA are somewhat different than those in OSPFv2. For this exercise, we’ll focus on area 45 and router R4. The only reason for this is the size of the database we’ll need to look into, nothing else. So, what do we have there then? Let’s take a look.

R4:

R4#show ipv6 ospf database ?
  adv-router        Advertising Router link states
  database-summary  Summary of database
  external          External link states
  inter-area        Inter-area LSA
  internal          Internal LSA information
  link              Link link states
  network           Network link states
  nssa-external     NSSA External link states
  prefix            Prefix link states
  router            Router link states
  self-originate    Self-originated link states
  unknown           Unknown link states
  |                 Output modifiers

From the available options, we can see that command-line syntax for exploring the database is very similar, if not identical to the one in OSPFv2. Let’s see what Router LSAs we have in our R4′s database.

R4:

R4#show ipv6 ospf database router

            OSPFv3 Router with ID (4.4.4.4) (Process ID 1)

                Router Link States (Area 45)

  LS age: 1095
  Options: (V6-Bit, E-Bit, R-bit, DC-Bit)
  LS Type: Router Links
  Link State ID: 0
  Advertising Router: 4.4.4.4
  LS Seq Number: 80000008
  Checksum: 0x90F4
  Length: 40
  AS Boundary Router
  Number of Links: 1

    Link connected to: another Router (point-to-point)
      Link Metric: 64
      Local Interface ID: 8
      Neighbor Interface ID: 6
      Neighbor Router ID: 5.5.5.5

  Routing Bit Set on this LSA
  LS age: 1163
  Options: (V6-Bit, E-Bit, R-bit, DC-Bit)
  LS Type: Router Links
  Link State ID: 0
  Advertising Router: 5.5.5.5
  LS Seq Number: 80000005
  Checksum: 0x2B5E
  Length: 40
  Area Border Router
  Number of Links: 1

    Link connected to: another Router (point-to-point)
      Link Metric: 64
      Local Interface ID: 6
      Neighbor Interface ID: 8
      Neighbor Router ID: 4.4.4.4

Highlighted red in the output, we can see originating routers of two LSAs. One is originated by ourselves (4.4.4.4) and the other one by R5 (5.5.5.5). Please note that even though they look like IPv4 addresses, Router-IDs are not IPv4 addresses. Just as in OSPFv2, they are 32bit numbers displayed in dotted-decimal format to make them look like IPv4s. We can also observe that there are no IPv6 addresses listed anywhere in the contents of the LSA. If you recall IPv4 Type 1 format, this is a major difference. In OSPFv3, Router LSA carries only a reference to links. These references are highlighted green. The reference consists of the local interface identifier, remote interface identifier and the remote neighbor. This is where Type 0008 (Link) and Type 2009 (Intra-Area-Prefix) LSAs come into play.

Link (Type 0008) LSA

Link LSA is exchanged only between the neighbors sharing the same link (it has a link flooding scope). Here’s a quick look into this LSA, again on R4.

R4:

R4#show ipv6 ospf database link

            OSPFv3 Router with ID (4.4.4.4) (Process ID 1)

                Link (Type-8) Link States (Area 45)

  LS age: 98
  Options: (V6-Bit, E-Bit, R-bit, DC-Bit)
  LS Type: Link-LSA (Interface: Serial0/1/0)
  Link State ID: 8 (Interface ID)
  Advertising Router: 4.4.4.4
  LS Seq Number: 80000008
  Checksum: 0xB1A4
  Length: 56
  Router Priority: 1
  Link Local Address: FE80::20A:B8FF:FE1A:5178
  Number of Prefixes: 1
  Prefix Address: 2001:DB8:45::
  Prefix Length: 64, Options: None

  LS age: 423
  Options: (V6-Bit, E-Bit, R-bit, DC-Bit)
  LS Type: Link-LSA (Interface: Serial0/1/0)
  Link State ID: 6 (Interface ID)
  Advertising Router: 5.5.5.5
  LS Seq Number: 80000008
  Checksum: 0xBAAA
  Length: 56
  Router Priority: 1
  Link Local Address: FE80::20A:B8FF:FE19:C8F0
  Number of Prefixes: 1
  Prefix Address: 2001:DB8:45::
  Prefix Length: 64, Options: None

We can see in this output that R4′s database contains only two Type 0008 LSAs. One is originated by R4 itself and the other one by R5. Contents are very simple. The link-local address of the originating router and all IPv6 prefixes associated with this interface. Note the Link State ID, highlighted green – these are the exact same values used in the Router LSA as link references. We can now tie the two together and learn about the prefixes used on the remote router. There is a problem, however. The flooding scope of the Link LSA means that only directly connected neighbors will know about this.

What about the situation like the one we have in area 0? R1 and R5 are not directly connected, yet they can clearly communicate. This is where Intra-Area-Prefix (Type 2009) LSA comes into play.

Intra-Area-Prefix (Type 2009) LSA

Let’s examine Intra-Area-Prefix database on R4.

R4:

R4#show ipv6 ospf database prefix

            OSPFv3 Router with ID (4.4.4.4) (Process ID 1)

                Intra Area Prefix Link States (Area 45)

  Routing Bit Set on this LSA
  LS age: 8
  LS Type: Intra-Area-Prefix-LSA
  Link State ID: 0
  Advertising Router: 4.4.4.4
  LS Seq Number: 8000000A
  Checksum: 0xCDE0
  Length: 64
  Referenced LSA Type: 2001
  Referenced Link State ID: 0
  Referenced Advertising Router: 4.4.4.4
  Number of Prefixes: 2
  Prefix Address: 2001:DB8::4
  Prefix Length: 128, Options: LA, Metric: 0
  Prefix Address: 2001:DB8:45::
  Prefix Length: 64, Options: None, Metric: 64

  LS age: 392
  LS Type: Intra-Area-Prefix-LSA
  Link State ID: 0
  Advertising Router: 5.5.5.5
  LS Seq Number: 80000009
  Checksum: 0xA188
  Length: 44
  Referenced LSA Type: 2001
  Referenced Link State ID: 0
  Referenced Advertising Router: 5.5.5.5
  Number of Prefixes: 1
  Prefix Address: 2001:DB8:45::
  Prefix Length: 64, Options: None, Metric: 64

Highlighted red we can see referenced LSA. Referenced LSA can be either Type 2001, as in this case or Type 2002, which we’ll observe next time. Since Type 2001 LSA doesn’t carry any prefixes, in this LSA we’re providing the missing information. The missing information is one or more prefixes. In the case of LSA originated by R4, we have two prefixes advertised. One prefix is for the link to R5 and the other one for the Loopback0.

Conclusions

We’ve demonstrated some important differences between OSPFv2 and OSPFv3 when it comes to LSAs used to carry intra-area information. The logical question to ask at this point would be – what’s the reason for the additional LSAs? Answer may not be immediately obvious, but once exposed becomes very logical.

When a new prefix is added or removed in OSPFv2, new Router LSA needs to be sent. This in turn triggers area-wide SPF run. In OSPFv3, addition and removal of the prefix, does not trigger SPF recalculation, since this information is not carried in Type 2001, but instead in Type 2009 LSA. This is more scalable and efficient approach, than the aging OSPFv2.

Next time, we’ll look into another intra-area LSA – Network (Type 2002).

Happy studies!

–
Marko Milivojevic – CCIE #18427
Senior Technical Instructor – IPexpert
Join our Online Study List

Print Friendly