Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Intervening Network Region Help

Status
Not open for further replies.

lopes1211

Technical User
Jan 11, 2002
2,835
US
I need some help with trying to clean up everything from being direct connected currently and start utilizing NR250 as an intervening region with PROCR. I also believe I need 2 ghost regions to separate the 2 MPLS networks used in the WAN. I'm getting a little stuck on how this design should lay out

If I have a CORE in NR1 connected to 2 MPLS networks:

NR 1,2,3 are connected to MPLS A. (call it ghost NR248)
NR 1,4,5 are connected to MPLS B. (call it ghost NR249)


1. Do all NR's direct connect to NR250 or just NR 248&249?
2. Does NR 1,2,3 direct connect to 248 and also have an intervening NR250 between each other or is the intervening regions between them 248:250?
3. Does NR 1,4,5 direct connect to 249 and also have an intervening NR250 between each other or is the intervening regions between them 249:250?

When connecting NR2,3 to NR 4,5 is the intervening region just 248:249 or is it 248:250:249?
When connecting NR4,5 to NR 3,4 is the intervening region just 249:248 or is it 249:250:248?


-CL
 
I don't see why it should be that complicated if you only have 1 core. Are we saying NR1 is a data center and NRs 2 and 3 are west coast offices and 4 and 5 east coast offices?

Is the IP routing such that MPLS A and B can't talk to each other and you need to peg on a DSP in NR 1 for 2 or 3 to talk to 4 or 5?

I think you overthunk it, but that tends to happen with network regions!
 
Yes, your assumptions are accurate. East ant west talk to each other through the core data center. So is it best to abandon those ideas but still setup nr250 and intervene everything through that?

-CL
 
It's really all about where you want to pull DSPs from.

Do 1-5 each have their own DSPs?
If none were available in a particular region, do you want 2 to pull from 1 first and then 3 and then 4 or 5?

Based on DSP sizing being adequate, it's probably not worth spelling out that 2 pulls from 2, then 1, then 3 then 4/5. You could probably just say "2 pulls from 2, then 1, then 3/4/5"

That would make 2,3,4,5 each direct to 1 with their bandwidth limits defined and each connect to 250 intervening via 1, and 1 direct to 250 with no limits.

I'm a little rusty, but that's where my train of thought is going.

 
I never use NR-250 for the intervening region. There is some history which I won't get into here but I suggest you stay away from it. Avaya will probably break it again sooner or later. I usually set 241 as the PROCR and 240 as the WAN. How you intervene depends on what you are trying to accomplish in your design. Since you seem to have 2 disparate WAN networks I would suggest having 2 WAN regions for intervening. Both would attach directly to your core (assuming NR-1) and then out to your remote sites. You may want additional intervening regions to the remote sites to make the core the shortest path between sites. Really depends on your available bandwidth and DSP resources at each site.
 
Jimbo...so assuming I used 2 WAN regions 239 and 240, 241 for procr, and the core is NR1.....I'm confused where procr connects in that scenario. It sounds like you're saying:

West coast NR's - direct to WEST NR239
East coast NR's - direct to EAST NR240
Core NR1 direct to both NR 239 & 240

Where is procr 241 in this design?

-CL
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top