Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Portable Remote Addr on Pipelines
We have many pipelines that call into us on a rotary of 12 PRI coming into
4 maxen, seperate from our small pockets of strictly dedicated user MAXen.
With this setup, most of the pipelines have a remote address of the first
max in the rollover, though they connect to all of them. We've had very
few problems with this setup(other than stacking induced reboots), and
when you go into the pipeline and do a show ip route, it shows the max
that it's currently connected to as it's gateway, regardless of what it
has in the remote ip address of the config.
Regards,
Joe Shaw - jshaw@insync.net
NetAdmin - Insync Internet Services
Fortune for today: "Life may have no meaning -- or worse, it may have a meaning
of which you disapprove." Unknown.
On Mon, 12 Jan 1998, David Nochlin wrote:
> In an environment with many remote P75's calling in to a small
> number of Max's (currently one, but soon to be more) - I am
> trying to have as little hardcoded into the remote configurations
> as possible. Currently I'm battling with the remote address
> parameter. I would like to be able to a) change the IP addresses
> of our Max without changing the Remote Address parameter on
> the remote Pipelines b) callin to multiple Max's (again without
> the need to change the Pipelines Remote Address parameter).
>
> With 4.6C it was possible to use the remote address 127.0.0.2 on a
> P75 to accomplish what I want. I'm not quite sure why this works
> but it appears to. This doesn't work with 5.X however.
>
> Can anyone suggest the correct magic to do what I want? Any and
> all suggestions would be appreciated.
>
> Thanks,
>
> David
>
>
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
References: