Hi,

this list appears to be almost dead, but I'll try anyway:

I'm lab-testing OSPF deployment on a network of Max1800/2k/4k boxes that
is uplinked by a Cisco. To not flood the Ascends with all external LSAs
I'm using a NSSA. The problem is that the Cisco involved receives all
the Type-7 LSAs from the NSSA as expected, but doesn't translate them to
Type-5s.

According to

cisco>show ip ospf database nssa-external 192.168.234.0

            OSPF Router with ID (aaa.aaa.aaa.aaa) (Process ID 15372)

                Type-7 AS External Link States (Area 1)

  LS age: 566
  Options: (No TOS-capability, Type 7/5 translation, No DC)
  LS Type: AS External Link
  Link State ID: 192.168.234.0 (External Network Number )
  Advertising Router: bbb.bbb.bbb.bbb
  LS Seq Number: 8000002A
  Checksum: 0x60B4
  Length: 36
  Network Mask: /24
        Metric Type: 2 (Larger than any link state path)
        TOS: 0 
        Metric: 10 
        Forward Address: 0.0.0.0
        External Route Tag: 0

the Type-7 LSA is received and has the P(ropagate)-Bit set. The reason
for the LSA not to be translated is (I found that out after reading the
NSSA RFC) that the Ascend box originates the LSA with

        Forward Address: 0.0.0.0

while RFC 1587 *requires* that

   When an NSSA internal AS boundary router originates a type-7 LSA that
   it wants to be translated into a type-5 LSA by the NSSA area border
   router (and subsequently flooded into the backbone), it must set the
   P-bit in the LS header's option field and add a valid forwarding
                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^
   address in the type-7 LSA.
   ^^^^^^^^^^^^^^^^^^^^^^^^^

which isn't happening. So the Cisco is correct in refusing the translation,
while the Ascend is issuing the LSA the wrong way.

Now this is a Max2k running TAOS 7.0.26. I tested to upgrade it to 7.2.4
and surprise - the forward address is in the LSAs then and the Cisco will
translate them.

Well you say, where is the problem? The problem is that 7.0.26 is the latest
available TAOS that runs on a Max4k. There is no later version available,
so the bug was never fixed for that platform.

So what to do *now*?

TIA,
Andre.
-- 
-> Andre Beck    +++ ABP-RIPE +++    IBH Prof. Dr. Horn GmbH, Dresden <-
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request at bungi.com
Archives: http://www.nexial.com/mailinglists/