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

Image
The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this
Read more

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s
Read more

AD LDS – Syncronizing AD LDS with Active Directory

Image
First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N
Read more