At 01:32 AM 1/5/01 +0100, Sascha E. Pollok wrote: >Dear folks, > >I posted a similar question some weeks ago but didn't >notice any answer so here ist is once again. > >Imagine the situation where there is a single Max >with 2xPRI (30 channels each). There is a primary >and backup radius-server for authentication >and accounting. In addition to authenticating callers >with Username/Password and/or Caller-ID, most of >the users get an IP assignment out of a pool. Some >callers are getting static ip assignments (Framed-Address/Netmask). >The Max is advertising it's dialup-routes via OSPF. >The pool gets summarized. > >Within Radius there are also some static routes with >dialup-profiles configured (customers with own mailserver >and thingies like that). > >All is working fine. Now imagine i'd like to add a 2nd >Max to the network due to lack of B-Channels. A 2nd >one is already mounted in the rack, the PRI's are almost >ready and will be reachable via the same number than >the current ones. > >Now problems arise. With only users dialing in and getting >pool or static IP assignments there would be no problem >because the Maxen advertise the IPs connected via OSPF. >The Maxen have different pools configured. >But what about dialout profiles? I could set the Max's name >in the static routes (on the radius-server), so that only >one of the Max's places calls but that wouldn't help >because if they dial in instead of getting called and they >connect to the non-dialing-Max, the "wanna-dial" Max >would still advertise the dialout-routes via OSPF and >we would have two identical routes within the OSPF domain. You can advertise a dialout route on one max, but have lower preference for that route than for the actively connected route, which is configured by radius. The route which will be preferred and propagated by ospf would be the "up" route. Greg ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com To get FAQ'd: <http://www.nealis.net/ascend/faq>