No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

OceanStor 9000 V300R006C00 Object Storage Service (Compatible with OpenStack Swift APIs) Administrator Guide 07

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
(Optional) Configuring NAT IP Address Mapping

(Optional) Configuring NAT IP Address Mapping

When you use the DNS function provided by the OceanStor 9000 object storage service, you need to configure network address translation (NAT) IP address mapping to enable a public network to access the object storage service.

Prerequisites

  • You have used the DNS service provided by the OceanStor 9000 object storage service.
  • The OceanStor 9000 has been deployed in an enterprise intranet, and the management IP address is the intranet IP address.
  • The OceanStor 9000 object storage service needs to be provided for the external users.
  • The customer must provide a proxy device for network address translation (NAT), for example, a firewall.

Procedure

  1. Use PuTTY to remotely log in to a management node. For details about how to log in, see "Appendix A Common Operations > Remotely Logging In to a Storage Node Using PuTTY."
  2. Run the sh /opt/obs/scripts/dns/updateOSCNatIps.sh ip1,ip2,ip3... command to configure NAT IP address mapping on a management node.

    ip1,ip2,ip3... indicates the IP addresses mapped from the external, which correspond to service plane IP addresses respectively and are equal to the number of front-end service IP addresses. The values are separated by commas (,). 192.168.171.22 and 192.168.171.23 are used as examples.

    sh updateOSCNatIps.sh 192.168.171.22,192.168.171.23
    Update OSC Nat Ips Success.
    

  3. Repeat 1 to 2 to configure NAT IP address mapping on the other management node.

    NOTE:
    The NAT IP address mapping configuration of the two management nodes is the same.

  4. Run cat /etc/nsd/obs.conf | grep "backward.monitor.osc.addresses" on either of the management node to view the information about the service plane IP address on the intranet.

    cat /etc/nsd/obs.conf | grep "backward.monitor.osc.addresses"
    backward.monitor.osc.addresses=192.168.171.11,192.168.171.12
    

  5. Run cat /etc/nsd/obs.conf | grep "front.monitor.osc.addresses" to view externally mapped IP addresses.

    cat /etc/nsd/obs.conf | grep "front.monitor.osc.addresses"
    front.monitor.osc.addresses=192.168.171.22,192.168.171.23

  6. Record the mapping between service plane IP addresses on the intranet and externally mapped IP addresses.

    In this example, service plane IP addresses 192.168.171.11 and 192.168.171.12 correspond to externally mapped IP addresses 192.168.171.22 and 192.168.171.23 respectively. If multiple service plane IP addresses exist, they respectively correspond to externally mapped IP addresses in sequence.

  7. Configure the proxy device which provides NAT based on the mapping between service plane IP addresses and externally mapped IP addresses.

    For details, see product documents of the NAT proxy device.

Translation
Download
Updated: 2019-04-28

Document ID: EDOC1000122524

Views: 11159

Downloads: 86

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next