Please enter search query.
Search <book_title>...
Veritas InfoScale™ Virtualization Guide - Linux on ESXi
Last Published:
2019-02-26
Product(s):
InfoScale & Storage Foundation (7.4)
Platform: VMware ESX
- Section I. Overview
- About Veritas InfoScale solutions in a VMware environment
- Section II. Deploying Veritas InfoScale products in a VMware environment
- Getting started
- Understanding Storage Configuration
- Section III. Use cases for Veritas InfoScale product components in a VMware environment
- Application availability using Cluster Server
- Multi-tier business service support
- Improving storage visibility, availability, and I/O performance using Dynamic Multi-Pathing
- How DMP works
- Improving data protection, storage optimization, data migration, and database performance
- Protecting data with Veritas InfoScale product components in the VMware guest
- Optimizing storage with Veritas InfoScale product components in the VMware guest
- Migrating data with Veritas InfoScale product components in the VMware guest
- Improving database performance with Veritas InfoScale product components in the VMware guest
- Setting up virtual machines for fast failover using Storage Foundation Cluster File System High Availability on VMware disks
- About setting up Storage Foundation Cluster File High System High Availability on VMware ESXi
- Configuring coordination point (CP) servers
- Section IV. Reference
Enabling TCP traffic to coordination point (CP) Server and management ports
For successful intra-cluster communication, make sure that cluster nodes and CP servers can be reached on port 14250 (or any other if you changed the default). If RedHat Firewall has been enabled, make sure there is a rule to allow the connection to ports 14250 and 14149.
To enable TCP traffic to CP server and management ports
- Stop iptables service:
[root@cps3 sysconfig]# service iptables stop iptables: Flushing firewall rules: [ OK ] iptables: Setting chains to policy ACCEPT: filter [ OK ] iptables: Unloading modules: [ OK ]
- Enter the following lines at the /etc/sysconfig/iptables file:
-A INPUT -p tcp -m tcp --dport 14250 -j ACCEPT -A INPUT -p tcp -m tcp --dport 14149 -j ACCEPT
- Start the service:
[root@cps2 ~]# service iptables restart iptables: Flushing firewall rules: [ OK ] iptables: Setting chains to policy ACCEPT: filter [ OK ] iptables: Unloading modules: [ OK ] iptables: Applying firewall rules: [ OK ] [root@cps2 ~]#
- Verify the new rule is in place:
[root@cps3 sysconfig]# iptables --list Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT tcp -- anywhere anywhere tcp dpt:cps ACCEPT tcp -- anywhere anywhere tcp dpt:vrts-tdd ACCEPT tcp -- anywhere anywhere tcp dpt:xprtld
For the SFCFSHA deployment example, these rules must be enabled on cfs01, cfs02, cfs03, cfs04, cps1, cps2 and cps3