Trending Topics

VMware on AWS - How to restore NSX DFW firewall rules to previous state

Image
Customers who uses NSX day-in, day-out would like to have a point-in time restore functionality of DFW firewall rules. Many customer have a large footprints in VMC and make changes to DFW quite often. This feature was missing for long time and we could see its included in recent versions . Let's see how DFW configuration roll back works  NSX DFW configuration has versioning, and it is stored in the NSX Manager.  Every time when someone update DFW configuration, NSX creates one more version but keep storing the previous ones. You can rollback for previous config but reapplying it once again.  You can find the options under Networking & Security tab , > Security > Distributed Firewall . In the right side we see an Actions drop down. Choose View to get to the below screen.  Let’s go through the use case:  1. Original state- default config with no custom rules:  a. There are no saved configurations during last 30 days: In my existing test setup, with the current setting

Clariion CX, CX3, CX4 – How to add Storage Capacity to Attached Host






Microsoft Windows



1. If needed, add new drives to the storage system.


2. If needed, create a hot spare using Navisphere Manager.


3. If needed, create an additional RAID group on the drives using Navisphere Manager.


4. Create (bind) additional LUNs on the RAID group using Navisphere Manager.


5. Assign the new LUNs to the server using Navisphere Manager.


6. Verify that the new LUNs were assigned to the server using Navisphere Manager.


7. On the server, verify that the server has access to the LUNs:


a. On the Windows desktop, right-click My Computer and click Manage.


b. In the left pane of the Computer Management dialog box, double-click on the storage icon.


c. Click Disk Management.


d. Verify that the LUNs that you added are listed in the right pane.


8. Start or restart the Navisphere Host Agent to push the server’s LUN mapping and operating system information to the storage system.


9. On the server, start PowerPath and verify that PowerPath sees all of the paths to the LUN.



Linux


1. If needed, add new drives to the storage system.


2. If needed, create a hot spare using Navisphere Manager.


3. If needed, create an additional RAID group on the drives using Navisphere Manager.


4. Create (bind) additional LUNs on the RAID group using Navisphere Manager.





5. Assign the new LUNs to the server using Navisphere Manager.


6. Verify that the LUNs were assigned to the server using Navisphere Manager.


7. On the server, verify that all LUNS have entries in the /proc/scsi/scsi/ directory.


8. On the server, verify that each LUN has an entry in the appropriate HBA file:


· For QLogic HBAs, the entry is in proc/scsi/qlaxxx/hba_number


· For Emulex HBAs, the entry is in /proc/scsi/lpfc/hba_number


9. On the server, verify that the failover software recognizes all of the paths to the LUNs.


For example, for PowerPath, verify that PowerPath recognizes all of the paths to the LUNs using the powermt command: powermt display dev=all class=clariion


10. Partition the LUN and then create and mount a file system to make the LUN available to the operating system.


11. Run the Navisphere Host Agent to push the server’s LUN mapping and operating system information to the storage system.


12. Save the failover configuration.


For example, for PowerPath, save the PowerPath configuration using the powermt savecommand.





13. On the server, verify that the server and failover software sees all of the paths to the LUN.V


For example, for PowerPath, verify the configuration using the powermt display command.

Popular posts from this blog

HOW TO EDIT THE BCD REGISTRY FILE

DNS Scavenging.

AD LDS – Syncronizing AD LDS with Active Directory