| You shouldn't need another MTA. On the X.25=>X.400 node you need to
install only the base component of the MTA (so that the server node
knows where its MTA is), and the existing Alpha needs to be configured
to recognize the new server as an Agent. Then the info needs to be set
up right in the MTS.
If you want to manage the MTA remotely, you need the Mgt component as
well (installed on the new server), but you should be able to get by
with just the Base component.
The only possible fly in the ointment is X.25; I know next to nothing
about that. GJ, cd you comment with the voice of experience?
b
|
| Hi,
a number of options.
1) why does the customer want a second system, a x25 interface could be
configured on the first server.
2) The first MB400 server can use the second server just for X25 access
to the public x25 network. The protocol between server 1 and 2 will be
LLC2 and server 2 will act as a relay client to relay the x25 traffic.
If this is the only purpose of server2, you could better use a DECnis.
3) server 2 has also MB400 installed, server1 and 2 communicate on
X400-P1 level, either automatically configured or manually. server 2
has the direct x25 link to the public network.
4) As in .1, move MB400 from server 1 to server2. In this scenario
server2 must have the mta-basekit installed to access server2
All is possible, pick your choice, 1 is the cheapest
GJ
|