You are right that 'OSPF area#' is included in the Hello messages : this is actually how ABR's are automatically found!
If you have 2 'area2' : it depends how they are connected : if they are connected then they are actually 1 area! If not, which I would think is your case, I think it should be fine because routing is not based on areaID but subnet addresses. The AreaID just helps define the raltionship of routers with each other either whether they are in the same area or not.
If you area2's are totally stubby, still no problem as the area0 between them still see their respective subnets...
The OSPF area-ID is NOT locally significant. All routers in an area must agree that they belong to the same area for them to actually belong to the same area. However, the only enforcement of this understanding is done on a link-link basis. Therefore, including the Area ID in the OSPF packet header allows routers to determine what area the neighboring router belongs to and whether or not to establish a neighbor relationship with this neighbor. So that should answer your first question.
I presume that when you say "type 3, type 5 packets" you are meaning type-3 and type-5 LSAs and not OSPF packet types 3 and 5, which are two different things. You need to understand that all OSPF packets only travel a single hop only (TTL=1). LSAs are carried in OSPF packets and during the process of flooding, they are carried within OSPF packets that change on every hop.
If you have two areas with the same number, the following possibilities may occur:
1. If the two areas are logically discontiguous, the backbone treats them as two separate areas. This is poor design but does work.
2. If the two(sic) areas are not logically discontigous, they are in effect the same area.
Apart from ABRs, the backbone does not have an understanding of area numbers. Every OSPF packet travelling within the backbone is associated with Area 0. The fact that LSAs carried within these packets originate from non-backbone areas is immaterial.
What I meant by that was: the two areas should not have any links between them which is configured with the same area-id as those two routers.. because this just makes it one big area instead of two separate areas.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...