Solved NX OS, Vrf Lite, and OSPF processes

---

Hi ITPro!

Wondering if you can help confirm something for me in regard to the NX OS, VRF Lite, and ospf processes.

It seems I am able to use the same OSPF processes ID for multiple VRFs.. For example..

Router ospf 1
   vrf LAN1
   router-id 1.1.1.1
!
  vrf LAN2
  router-id 2.2.2.2
!
int vlan 1
   vrf member LAN1
   ip router ospf 1 area 0.0.0.0
!
int vlan 2
  vrf member LAN2
  ip router ospf 1 area 0.0.0.0

From what I can tell, these two “area 0” statements on each interface are completely isolated. Even though they are using the same ospf process number of 1? So it isn’t necessary to create a separate ospf process for each vrf?

-Adam

Ronnie, no worries. I don't follow your answer though. I realize that the OSPF process IDs are only locally significant with OSPF. In contrast to EIGRP for example where it isn't a process ID, its an AS number that has to match.

However my original question was regarding the use of the same OSPF process ID on the same router with multiple VRFs. In this case it was on the Nexus platform. After a lot more lab work since posting this question, the answer I believe is yes, the process IDs are in no way related when deployed to different VRFs in this manner. Area 0 for SVI LAN1 can be a completely different area 0 than for SVI LAN2. It appears to essentially run a different ospf process 1 for each VRF.

Router ospf 1
   vrf LAN1
   router-id 1.1.1.1
!
  vrf LAN2
  router-id 2.2.2.2
!
int vlan 1
   vrf member LAN1
   ip router ospf 1 area 0.0.0.0
!
int vlan 2
  vrf member LAN2
  ip router ospf 1 area 0.0.0.0

-Adam

@Adam-Tyler,

Sorry, your question fell through the cracks and this is my fault.

Regardless of the VRFs, the process-id numbers are only locally significant. So even if they were in the same VRF you could have all your routers with the same process-id!

Ronnie, no worries. I don't follow your answer though. I realize that the OSPF process IDs are only locally significant with OSPF. In contrast to EIGRP for example where it isn't a process ID, its an AS number that has to match.

However my original question was regarding the use of the same OSPF process ID on the same router with multiple VRFs. In this case it was on the Nexus platform. After a lot more lab work since posting this question, the answer I believe is yes, the process IDs are in no way related when deployed to different VRFs in this manner. Area 0 for SVI LAN1 can be a completely different area 0 than for SVI LAN2. It appears to essentially run a different ospf process 1 for each VRF.

Router ospf 1
   vrf LAN1
   router-id 1.1.1.1
!
  vrf LAN2
  router-id 2.2.2.2
!
int vlan 1
   vrf member LAN1
   ip router ospf 1 area 0.0.0.0
!
int vlan 2
  vrf member LAN2
  ip router ospf 1 area 0.0.0.0

-Adam

@Adam-Tyler said in NX OS, Vrf Lite, and OSPF processes:

After a lot more lab work since posting this question, the answer I believe is yes, the process IDs are in no way related when deployed to different VRFs in this manner. Area 0 for SVI LAN1 can be a completely different area 0 than for SVI LAN2. It appears to essentially run a different ospf process 1 for each VRF.

I think that's what I said. Regardless of the VRFs. Even if its in the same VRF or in different VRF the process-id numbers can be the same on different routers. Because they are only locally significant to that router. So you do not have to fun a different one...you can (I do because it helps me to keep track of the router I'm working on).