Thursday, November 14, 2013

LAN Based Failover for Cisco PIX 515E

Revisited my blog after few years and below was an unpublished post and also I have tested this 3 years ago too.

This post will explain how you can couple a pair of Cisco PIX 515E in very basic level. (device version is 8.0(4) and this should be technically supported to any PIX /ASA version 6.2 and above)

There will be two identical failover scenarios;

Stateful Failover
With the stateful failover the active PIX will replicates the state table to the standby PIX. As such, if the active PIX fails, the standby PIX can take over transparently without any interruption to the current session already initiated to the PIX.

LAN-BASED Failover
With the Lan-Based failover the standby PIX waits idle and it will take over if the primary PIX fails at any point. (interface issue, power issue, etc) But the standby PIX has no information about any information about the existed session with the primary PIX was processing. So technically after a every failover all the session should be re initiated. This is not necessarily transparent to end users.

The Requirement
SOFTWARE:
1.) Must be in operating mode
     a.) Routed or Transparent.
     b.) Single or Multiple Context

HARDWARE:
1.) The two units in a failover configuration must have the same
      a.)hardware configuration:
      b.) same model
      c.) same number and types of interfaces
      d.) same amount of RAM

LICENSE:
1.) PIX 500:
     a.) One of the unit should be having UR (Unrestrcited License). The other unit can have FO (Failover) license or FO_AA (Failover Active/Active) License. Note: Boxes with FO or FO_AA, Restricted licenses can not be used for failover.

2.) ASA:
    User need to understand the requirement and can go for the the license according to his need. (Security Plus Bundle)





Thursday, November 19, 2009

VMware VSphere Client ERRORs on Windows 7 64bit

Error Messages:
1. Error parsing the server “hostname”“clients.xml” file.Login will continue, contact your system administrator
2. The type initializer for 'VirtualInfrastructure.Utils.HttpWebRequestProxy' threw an exception
Nothing will happen after you click "OK" on above errors.

Don't take a deep breath and panic. ;) follow these easy steps to resolve these errors withing 10 min.

1. You need to get a copy of following DLL file from computer which has installed .NET 3.5 SP1. The file name is System.dll and it's located in %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\

Please Note: Getting this DLL from 32 bit system is fine but not from Windows 7 or Win 2008 versions.
I have uploaded this file for you : http://www.easy-share.com/1908477347/System.dll

2. Create a folder and copy this DDL file to some where in "C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher" for this example I have created "bug" and copied the DLL inside it.

3. And please find the file named VpxClient.exe.config in the same folder which you have created the folder in action 2 (C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher) Open the particular file and include following lines before the end and without "" and save. (if you can't save the file get the ownership for the current user by using file properties >> Security >> Advanced... )

"


"

4. Now you need to make Environment Variable for the DDL file show in the screen shot below
Variable name: DEVPATH
Variable value: C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\bug\
That's all and now you are ready to go !