Re: OSPF Process ID

[Richard Holland]

The process id in OSPF is basically so you can run more than a single OSPF instance on a given router(s).  At first it would seem unclear as to why you would want to even run more than one OSPF instance, but think about this:  You work for company A, you have a large multiple area OSPF network, your healthy routers slap the hello packets out, flood LSA's, all is good.  Then Johnny Q. Corporate, your CEO, decides to buy Company B to narrow competition down, Company B also has a large multi area OSPF network, but their timers are different, your routers can't deal with these "invalid" Hello packets coming in, so to merge the two networks together, you could make the router(s) hooking Company A with B together run one OSPF instance for Company A, and one for B.  This saves you a hell amount of time on reconfiguring routers, provided you can redistribute effectively.   Isn't this what an AS does?  Not by nature, althought it does end up being one use of an AS, and especially in this situation.  AS's also discuss route policy, it's the 90's.   Or maybe you have two networks that don't connect together, but they share one router.  Again, it's best to use seperate OSPF id's for each, than try to filter and the like.   Richard Holland CCNA,CCNP,MCSE,MCP+I OpenBSD,Telephones,Cars,Money   ----- Original Message ----- From: Henrique Issamu Terada To: [EMAIL PROTECTED] Sent: Saturday, June 17, 2000 3:02 PM Subject: OSPF Process ID Hi people   I apologize if my question is a little bit stupid , but I cannot understand the ospf process id. Should it not be the AS ? Why ?   Henrique Issamu Terada CPM Comunica��es - Brazil CCNA Certified