Hello,
In "OSPF: Frequently Asked Questions" there is a question relating to your problem:
Q. Can I control the P-bit when importing external routes into a not-so-stubby area (NSSA)?
A. When external routing information is imported into an NSSA in a type 7 link-state advertisement (LSA), the type 7 LSA has only area flooding scope. To further distribute the external information, type 7 LSAs are translated into type 5 LSAs at the NSSA border. The P-bit in the type 7 LSA Options field indicates whether the type 7 LSA should be translated. Only those LSAs with the P-bit set are translated. When you redistribute information into the NSSA, the P-bit is automatically set. A possible workaround applies when the Autonomous System Boundary Router (ASBR) is also an Area Border Router (ABR). The NSSA ASBR can then summarize with the not-advertise keyword, which results in not advertising the translated type 7 LSAs.
So you should see the route in the NSSA.
There is also a stement in "Filtering in NSSA"
http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094a88.shtml#filternssa
Another case of filtering is when you need to prevent the type 7 LSAs from being translated outside the NSSA. In other words, when you want to control which type 7 LSAs get translated into type 5. For example, we have a RIP learned route 141.108.10.0/24 that is being injected into the OSPF NSSA area 1. We do not want this route to be leaked into the rest of the OSPF areas. We achieve this using the following configuration on either the NSSA ASBR or the NSSA ABR.
router ospf 1
summary-address 141.108.10.0 255.255.255.0 not-advertise
So you could give it a try on the ABR and see whether this works.
Hope this helps! Please rate all posts.
Regards, Martin
