PowerFlex 3.X: The old IP is showing up as still in use in PxFM
Summary: PowerFlex 3.X The old IP is showing up as still in use in PxFM.
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.
Symptoms
The IPs are changed manually on the resource itself outside the PxFM.
When ever we change the IP of any resource manually outside the PxFM, then the old IP does not free up from the network.
Tab of PxFM. The changed or new IP will be updated successfully on the respective resource but the issue is the old IP will still be
Shown as in use by same resource or service. The PxFM database does not flush out the old IP details.
Example: If the user change the virtual IPs manually on MDM and if the user run inventory or update the service,
Then the new IP will be reflected on the respective resource(PowerFlex GW). However the main issue would be.
The old IP will not free up from the PxFM database and still shows as it is in use by the resource or service
And cannot use the same IP for the new deployment.
These old IPs cannot be further used for new deployment inside the PxFM and we might run in short of IPs.
When ever we change the IP of any resource manually outside the PxFM, then the old IP does not free up from the network.
Tab of PxFM. The changed or new IP will be updated successfully on the respective resource but the issue is the old IP will still be
Shown as in use by same resource or service. The PxFM database does not flush out the old IP details.
Example: If the user change the virtual IPs manually on MDM and if the user run inventory or update the service,
Then the new IP will be reflected on the respective resource(PowerFlex GW). However the main issue would be.
The old IP will not free up from the PxFM database and still shows as it is in use by the resource or service
And cannot use the same IP for the new deployment.
These old IPs cannot be further used for new deployment inside the PxFM and we might run in short of IPs.
Cause
The PxFM database sometime does not get updated when the changes are done manually outside the PxFM.
Resolution
Step 1: Select the respective resource and run the inventory for that. Then go to the respective resource.
And see if the IP details are updated. Then go to the network section of PxFM and see if the new IP details
Are updated and the old IP is freed up. Only if the old IP is still showing as in use by the resource or service then go to step 2
Step 2: Go to the respective service and click update service. If still the old IP is showing as in use then.
Go to step 3
Step 3: Make the note of all the resources of the affected service. Go ahead and remove the respective service with the manage mode option.
Then re-add the service as existing service and this might not take more than 45 mins. Doing this would flush the respective service data from PxFM database and update it with the correct IP's.This should finally free up the old IP and can be used for further deployments.
This option is safe as it does not change the existing components or Resources and add the service back to the PxFM.
And see if the IP details are updated. Then go to the network section of PxFM and see if the new IP details
Are updated and the old IP is freed up. Only if the old IP is still showing as in use by the resource or service then go to step 2
Step 2: Go to the respective service and click update service. If still the old IP is showing as in use then.
Go to step 3
Step 3: Make the note of all the resources of the affected service. Go ahead and remove the respective service with the manage mode option.
Then re-add the service as existing service and this might not take more than 45 mins. Doing this would flush the respective service data from PxFM database and update it with the correct IP's.This should finally free up the old IP and can be used for further deployments.
This option is safe as it does not change the existing components or Resources and add the service back to the PxFM.
Additional Information
Do not delete the service.Only use remove service with Manage mode option.
Affected Products
PowerFlex appliance Intelligent Catalog SoftwareProducts
PowerFlex rack, VxFlex Ready Nodes, PowerFlex Appliance, PowerFlex custom node, PowerFlex appliance R650, PowerFlex appliance R6525, PowerFlex appliance R660, PowerFlex appliance R6625, Powerflex appliance R750, PowerFlex appliance R760
, PowerFlex appliance R7625, PowerFlex custom node, PowerFlex custom node R650, PowerFlex custom node R6525, PowerFlex custom node R660, PowerFlex custom node R6625, PowerFlex custom node R750, PowerFlex custom node R760, PowerFlex custom node R7625, PowerFlex rack connectivity, PowerFlex Software, VxFlex Product Family, VxFlex Ready Node, VxFlex Ready Node R640, VxFlex Ready Node R740xd, PowerFlex appliance R640, PowerFlex appliance R740XD, PowerFlex appliance R7525, PowerFlex appliance R840, VxFlex Ready Node R840
...
Article Properties
Article Number: 000173720
Article Type: Solution
Last Modified: 19 Nov 2025
Version: 4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.