lcsjason Absent Member.
Absent Member.
1319 views

Mail Flow through DR Groupwise server

Hoping someone might be able to assist. We have a Novell/Groupwise server and 3 Post Office Servers. We had to fail over to our DR Novell/Groupwise server after a hardware failure. Failover allowed for authentication services and mail is flowing between the post office servers. However, we are unable to send/receive to external domains. Have repointed our NAT to the DR server and I suspect it is an issue with the MTA or POA but my familiarity with the system is very limited but in Groupwise and with how it was setup. Any ideas would be appreciated, thanks!
Labels (2)
0 Likes
2 Replies
Micro Focus Expert
Micro Focus Expert

Re: Mail Flow through DR Groupwise server

Hi,

Welcome to the forums and thank you for your question, though the circumstances are not the greatest.

Ok, if there was a problem with the MTA mail would not be flowing between post offices. So let's turn our attention to GWIA. I'd check to see if the GWIA is indeed bound to the correct IP address and is servicing calls. Use telnet to connect to the GWIA IP on port 25 and see if you get the correct SMTP response.

Let's do that first and please let us know how it goes.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Knowledge Partner
Knowledge Partner

Re: Mail Flow through DR Groupwise server

In article <lcsjason.7sqieo@no-mx.forums.microfocus.com>, Lcsjason
wrote:
> we are unable to send/receive to external domains.
> Have repointed our NAT to the DR server and I suspect it is an issue
> with the MTA or POA but my familiarity with the system is very limited
> but in Groupwise and with how it was setup.


Given that your DR server has a different IP, we either need to tell
GroupWise about it or if possible add the old IP as a secondary address.

Adding the old IP as a secondary would be the fastest if the DR server
is in the same subnet as the primary. Then making any other switches
can be done at a more leasurely pace.

We need to confirm some things before we dive much more in.
Since Novell is a Company name, that doesn't help us know what operating
system your GroupWise system is running on. Options are SLES, OES based
on SLES, or Windows. Knowing which helps on a bunch of levels of how we
can guide you. Do you have other eDirectory servers? If so eDirectory
may need looking at as well.
Your main GroupWise server (CoreGW for short), sounds like this is the
one with an MTA(Domain), a GWIA (Internet Agent), likely WebAccess, and
possibly a little used POA(Post Office)
The Post office servers will at least have a POA, but they might have
their own MTAs which would be one way the PostOffices get to talk to
each other when the main GroupWise serve is not accessible.

Make sure you have all the IP addresses of both the servers and that
GroupWise uses (they can be different)

To change the IP addresses you will need to get onto ConsoleOne on the
server. I'll assume you've been using it for basic maintenance Likely
each of your GroupWise servers have ConsoleOne installed, and we may
need to touch each of them, but for now start with the CoreGW server.
Under GroupWise system, do you see just one Domain (globe icon) or more
(4?). For each Domain, right click and select GroupWise Utilities, Link
Configuration, and note how each is linked. If multiple Domains, you
may well need to touch each of the others directly to tell them where
CoreGW is now.
With the GroupWise System selected, I expect to see one GWIA (select
Gateways in the pull down in the top middle of ConsoleOne). On that GWIA
object, double click or right click and select properties. On the tabs,
Find the GroupWise Identification, click on the little arrow on it to
select the Network Address sub tab. The TCP/IP address will either be
the dead hardware's IP or a secondary address that was on the server.
Change this to match appropriately to your DR server, OK to close that
properties window. Change that top pulldown to Message Transfer Agents
(MTAs), and go into properties of your CoreGW's MTA, GroupWise tab with
the sub tab of Network Address and adjust like you did for GWIA.

Hopefully that will get your system behaving.

Let us know how it goes, and if there are still problems, include the
answers to the questions I posed (without any IP addresses)


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.