Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Not Answered
  • Replies replies
    7
  • Subscribers subscribers
    6
  • Views views
    414
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to configure 2 SMG to know each other

kseb

Currenlty we are configured Two SMG. How to make SMG know each other

Parents
  • 0  

    It is impossible to answer that question without knowing what you are trying to do.

    • Why do you have two appliances?
    • How are they being used?
    • Why do you need to make SMG know each other?

    __________
    Kevin Boyle, SuperUser
    Calgary, Alberta, Canada

Reply
  • 0  

    It is impossible to answer that question without knowing what you are trying to do.

    • Why do you have two appliances?
    • How are they being used?
    • Why do you need to make SMG know each other?

    __________
    Kevin Boyle, SuperUser
    Calgary, Alberta, Canada

Children
  • 0   in reply to   

    As Kevin already replied. Usually you will create a SMG network. So all appliances work together and store configuration, data and values in common databases. 

    If you have started to install two separate appliances they will use two separate databases which do not communicate ...

    Use "Verified Answers" if your problem/issue has been solved!

  • 0 in reply to   

    I am new to SMG and GW.

    We are planning to use two SMG for load-balancing ie. We are having LB in front of  SMG so with LB will manage traffic to both node.

    Why do you need to make SMG know each other?

    any cluster type (heartbeat)

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.