De tudo mais um pouco

This was done on the Pfsense 2.4.5. Check disk size: [2.4.5-RELEASE][root@server1]/root: gpart show =>       63  104857537  da0  MBR  (50G)          63          1       - free -  (512B)          64  104857535    1  freebsd  [active]  (50G)   104857599          1       - free -  (512B) =>        0  104857535  da0s1  BSD  (50G)           0   98566144      1  freebsd-ufs  (47G)    98566144    5242880      2  freebsd-swap  (2.5G)   103809024    1048511         - free -  (512M) On vmware increase the disk size of the Virtual Machine. I did this with the VM powered down. Power on the Pfsense machine. Check disk size again: [2.4.5-RELEASE][root@server1]/root: gpart show =>       63  629145537  da0  MBR  (300G)          63          1       - free -  (512B)          64  104857535    1  freebsd  [active]  (50G)   104857599  524288001       - free -  (250G) =>        0  104857535  da0s1  BSD  (50G)           0   98566144      1  freebsd-ufs  (47G)    98566144    5242880      2  freebs

I have a situation where: Frames attached on HMC using the dhcp range 192.128 But due network requirements it was necessary change the range. To avoid any problem, I opened a ticket with IBM Support and they give me the following solution: Is not need power off hte lpars on the frame. Is not need power off the frames. Not need to ask a onsite support to remove frames from power and power on again. Just access the network configuration on HMC and change the DHCP range on the interface. After that reboot the HMC. With that the DHCP lease on frame side will expire and get the new IP address. Can last 20 minutes to the frame get the new IP after the HMC rebooted. On the HMC interface you will see the frame lost connection but will be back soon, give it time. If the solution above do not work you or a onsite support will need unplug the cable on the frame side FSP port. Leave unplugged for 3  minutes and plug back. Only unplug on the frame side, not the HMC. Fortunatelly it was not necessar