PowerFlex :Network Connectivity - Testing Port 7072

Summary: How to verify/investigate connectivity to port 7072 on a given set of SDSes, from Linux and ESXi. The intended use of this KB is to confirm SDC-SDS connectivity or SDS-SDS connectivity. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Instructions

1.Gather a list of all IPs involved

  • Group them by subnet and SDC/SDS, vmknic/SVM, etc.
  • Check list for duplicates and inconsistencies.

2.Test connectivity to the SDS process' port 7072

On Linux, the following one-liner can be modified to suit the customer's environment. 

  • As we expect that there will be a range of IPs on two data subnets, replace the variables in the following with the two networks to check, and the range of IPs in the last octet:
for j in {BEGINNING_IP..ENDING_IP}; do for i in NETWORK_1 NETWORK_2;do echo "$i.$j:";echo ""| $(which nc 2> /dev/null || which netcat 2> /dev/null) -nvw 2 ${i}.${j} 7072;done;done

       for example example, with data networks of 38.38.38.x and 39.39.39.x, and a range of IPs from .244 through .248, this looks like:
             
for j in {244..248}; do for i in 38.38.38 39.39.39;do echo "$i.$j:";echo ""| $(which nc 2> /dev/null || which netcat 2> /dev/null) -nvw 2 ${i}.${j} 7072;done;done
  • On SLES 11 SVMs, you'll see the following output when successful:
38.38.38.244:
(UNKNOWN) [38.38.38.244] 7072 (?) open
39.39.39.244:
(UNKNOWN) [39.39.39.244] 7072 (?) open
38.38.38.245:
(UNKNOWN) [38.38.38.245] 7072 (?) open
39.39.39.245:
(UNKNOWN) [39.39.39.245] 7072 (?) open

 

   
This when the port is closed:



   
38.38.38.246:
(UNKNOWN) [38.38.38.246] 7073 (?) : Connection refused
39.39.39.246:
(UNKNOWN) [39.39.39.246] 7073 (?) : Connection refused
38.38.38.247:
(UNKNOWN) [38.38.38.247] 7073 (?) : Connection refused
39.39.39.247:
(UNKNOWN) [39.39.39.247] 7073 (?) : Connection refused

   

  

  

   And this when it can't reach the host:
   

    
   
 38.38.38.248:
(UNKNOWN) [38.38.38.248] 7072 (?) : Connection timed out
39.39.39.248:
(UNKNOWN) [39.39.39.248] 7072 (?) : Connection timed out

 

   

   
    
    
  • On newer releases (RHEL 7 here) you'll see this when it succeeds:
    • 
   

   
38.38.38.244:
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: Connected to 38.38.38.244:7072.
Ncat: Connection reset by peer.
39.39.39.244:
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: Connected to 39.39.39.244:7072.
Ncat: Connection reset by peer.
38.38.38.245:
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: Connected to 38.38.38.245:7072.
Ncat: Connection reset by peer.
39.39.39.245:
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: Connected to 39.39.39.245:7072.
Ncat: Connection reset by peer.

   
This when the port is closed:



   
38.38.38.247:
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: Connection refused.
39.39.39.247:
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: Connection refused.
 

   

   
And this when it fails to reach the host:

   
38.38.38.248:
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: Connection timed out.
39.39.39.248:
Ncat: Version 6.40 ( http://nmap.org/ncat )
Ncat: Connection timed out.
 

   

   
 

   
 



   
 On ESXi, the following one-liner can be modified to suit the customer's environment and test VMKNIC   SDS data IP connectivity:

   
    
    
  • As we expect that there will be a range of IPs on two data subnets, replace the variables in the following with the two networks to check, and the range of IPs in the last octet:
    • 
   

   

    
    
for j in `seq BEGINNING_IP ENDING_IP`; do for i in NETWORK_1 NETWORK_2;do nc -vz -w 2 ${i}.${j} 7072;done;done

    

     
   

   for example,with data networks of 38.38.38.x and 39.39.39.x and a range of IPs from .244 through .248, this looks like:
   

    

    
    
for j in `seq 244 248`; do for i in 38.38.38 39.39.39;do nc -vz -w 2 ${i}.${j} 7072;done;done

    

     
   

   

    This will output the following for successful connections:
    

     
    
Connection to 38.38.38.244 7072 port [tcp/*] succeeded!
Connection to 39.39.39.244 7072 port [tcp/*] succeeded!
Connection to 38.38.38.245 7072 port [tcp/*] succeeded!
Connection to 39.39.39.245 7072 port [tcp/*] succeeded!
Connection to 38.38.38.246 7072 port [tcp/*] succeeded!
Connection to 39.39.39.246 7072 port [tcp/*] succeeded!
Connection to 38.38.38.247 7072 port [tcp/*] succeeded!
Connection to 39.39.39.247 7072 port [tcp/*] succeeded!

    

and for failures to connect, the following output:



    
 

    

     
nc: connect to 38.38.38.248 port 7072 (tcp) timed out: Operation now in progress nc: connect to 39.39.39.248 port 7072 (tcp) timed out: Operation now in progress

 

    

   

  

        


        

        
        
Affected Products

        VxFlex Product Family
    
Products

        PowerFlex Software, VxFlex Product Family, VxFlex Ready Node, PowerFlex appliance R740XD, PowerFlex appliance R840







                        

                            

    

        

            

                
                    
 Article Properties

                
            

            

                

                        
Article Number: 000022737

                

                
                

                        
Article Type: How To

                

                

                        
Last Modified: 17 نيسان 2026


                

                    

                            
Version:  6

                    


            


        

    

    

        

            

                
                    
Find answers to your questions from other Dell users

                
            

            

                

                    
                



            


        

    

    

        

            

                
                    
Support Services

                
            

            

                

                    Check if your device is covered by Support Services.