Re: OSPF NSSA N2/E2 translation

From: alsontra@hotmail.com
Date: Sat Jul 17 2004 - 18:16:37 GMT-3


And the answer is: If you have two ABR to an NSSA, the ABR with the highest
router-id will translate N2---to--->E2. If for some reason the ABR with
highest RID is not connected to area 0, no conversion will take place. Easies
solution is to change RIDs.

To paraphrase:

NSSA RFC 1587 states that before an NSSA ABR converts Type-7 to Type-5, all
NSSA ABR must examine all other NSSA ABR to determine the highest router-id.
The NSSA ABR with the highest router-id "must" the conversion from N2 to E2.
(Troubleshooting IP protocols, Cisco Press -Page 444)

Alsontra
  ----- Original Message -----
  From: alsontra@hotmail.com
  Cc: ccielab@groupstudy.com
  Sent: Tuesday, July 13, 2004 10:52 PM
  Subject: OSPF NSSA N2/E2 translation

  Group,

  Under what circumstances will an ABR to an NSSA "not" translate an N2?

  For instance, if R2 is an ABR to area 12 and R3 is redistributing its Lo0
interfaces as an N2, under what circumstances will R2 stop translating N2s
into E2s.

  R1-----------R3-----(area 12) NSSA-----SW2

  Or does an ABR to an NSSA always translate N2s? R3 shows SW2 lo0 interface
as being translated. However, all areas do not show the 150.1.8.0 link.
(translated loopback).

    Routing Bit Set on this LSA
    LS age: 307
    Options: (No TOS-capability, Type 7/5 translation, DC)
<---------------------
    LS Type: AS External Link
    Link State ID: 150.1.8.0 (External Network Number )
    Advertising Router: 150.1.8.8
    LS Seq Number: 80000003
    Checksum: 0x89C3
    Length: 36
    Network Mask: /24
          Metric Type: 2 (Larger than any link state path)
          TOS: 0
          Metric: 20
          Forward Address: 0.0.0.0
          External Route Tag: 0

  All routers in the OSPF domain have 150.1.8.0 in their databases, but not in
routing tables. Any ideas?

  Thanks,
  Alsontra



This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:11:57 GMT-3