want to segregate corp and prod networks. initially have planned multiple domains, two area 0s under different processes.
prod networks don't need knowledge of corp net as all corp traffic is natted incoming against prod interfaces. does it make sense to define the prod area as a stub network? totally stubby?
also, have a pt - pt between two sites each. both sites have prod and corp segments and would like to keep prod and corp in distinct processes across the sites. is this possible? can i place an interface in more than one process?
you can do this - but they will share the same routing table, so it doesnt actually give you much separation.
if you have images with the right features, try using multiple VRFs - this means you get 2 different routing tables, in 2 logical routers - then you can run 2 separate copies of OSPF and actually keep them apart.
Note that IOS switches can do this as well as the routers.
usually this kind of separation is about isolating potentially unstable "stuff" from a critical network.
however - the best separation can be an airgap and 2 separate sets of boxes.
not sure about your split - but ours is for testing, and is forever being rebooted, having new images loaded on it, connecitons repatched and so on.
using the same boxes for production and test is like that old cartoon of sawing off a branch of a tree you are sitting on.....
you can split the interface if you can use sub-interfaces - if it is serial, then try frame relay encap with 2 PVCs (you can set up frame relay switching at 1 end - you dont need any actual switches), or VLANs with Ethernet.
If that isnt suitable, try using GRE to tunnel 1 network thru the other - ideally the base would be the stable one.