How to change the SecurePlatform WebUI default access port

The SecurePlatform WebUI default access port is HTTPS 443.

To change it, log in to the SecurePlatform CLI in Standard mode, and run this command:

webui enable <port_number>

The machine then presents this output:

Shutting down cp_http_server_wd [OK]
Shutting down cpwmd_wd [OK]
Running cp_http_server_wd [OK]
Running cpwmd_wd [OK]

To disable access to the WebUI, run the command:

webui disable

https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk27242

Forcing NICs on SecurePlatform full/half duplex or 10/100/1000 Mbps using ethtool

Network interfaces cards (NICs) on SecurePlatform are configured to auto-negotiate link speed and duplex settings with the device to which they are physically connected to. If a NIC interface is unable to auto-negotiate with the device, it is necessary to hard code the settings.

Solution:

In expert mode, use the 'ethtool' to hard code link speed and duplex settings of network interfacesNICs.
Note: Per the IEEE specification, gigabit speed cannot be forced. It can only be auto-negotiated.
Quick command syntax:

ethtool -s DEVNAME speed 10|100|1000 duplex full|half autoneg off|on

Example:

• ethtool -s eth0 speed 100 duplex full autoneg off
  (Will force eth0 interface to 100 MB link speed, full duplex).



• ethtool -s eth0 speed 100 duplex half
  (Will force eth0 interface to 100 MB link speed, half duplex).



• ethtool -s eth0 autoneg on
  (Will force eth0 interface to auto-negotiate).



• ethtool -s eth0 autoneg off
  (Will force eth0 interface auto-negotiate off).

Commands can be put at the end of the /etc/rc.local startup script, to survive reboot.

m Wake on multicast messages.
b Wake on broadcast messages.
a Wake on ARP.
g Wake on MagicPacket(tm).
s Enable SecureOn(tm) password for MagicPacket(tm).
d Disable (wake on nothing). This option clears all previous options.

sopass xx:yy:zz:aa:bb:cc
(Set SecureOn(tm) password. Argument to this option must be 6 bytes in ethernet MAC hex format (xx:yy:zz:aa:bb:cc).

msglvl N
(Set driver message level. Meanings differ per driver).


Full options of command:
Example:

ethtool -s ethX [speed 10|100|1000] [duplex half|full] [port tp|aui|bnc|mii] [autoneg on|off] [phyad N] [xcvr internal|external]
[wol p|u|m|b|a|g|s|d...] [sopass xx:yy:zz:aa:bb:cc] [msglvl N]

OPTIONS

-s
Allows changing some or all settings of the specified Ethernet device; options only apply if -s is specified.

ethX
Device Name

speed 10|100|1000
Sets speed in Mbps; ethtool with a single argument will show supported device speeds.

duplex half|full
Sets full- or half-duplex mode.

port tp|aui|bnc|mii
Selects device port.

autoneg on|off
Specifies whether or not autonegotiation is enabled.

phyad N
Physical address

xcvr internal|external
Selects transceiver type; currently only internal and external can be specified.

wol p|u|m|b|a|g|s|d...
Sets Wake-on-LAN options; not all devices support this. The Argument to this option is a string of characters specifying the options to enable.

Thanks to:

http://firewalltipss.blogspot.co.il/2010/09/forcing-nics-on-secureplatform-fullhalf.html

Error 1920 - Service VMWare View Composer (svid) failed to start

"Error 1920 - Service VMWare View Composer (svid) failed to start. Verify that you have sufficient privileges to start system services."

Here is how I fixed the issue: Installed the SQL Native client for 2008R2. 

Thanks to:

http://itadminexchange.blogspot.co.il/2011/10/view-composer-5-error-1920.html

Exchange 2010 Setup: Unable to read data from the Metabase. Ensure that Microsoft Internet Information Services is installed

Open Power Shell in elevated mode (run as administrator)

1. Type the following (or copy paste)
   • Import-Module ServerManager
   • Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart
2. The second command will install the required components and reboot the server
3. After reboot, open the Power Shell again in elevated mode.
4. Type this to set NetTcpPortSharing service to automatic.
   • Set-Service NetTcpPortSharing -StartupType Automatic
5. Close the Powershell. Try running Exchange 2010 setup again.



Remove HP Proliant Support Pack from Virtualized Servers

כלי חינמי שמעיף את כל השאריות העקשניות שלHP  שלא מוסרות בדרכים הקונבנציונליות לאחר ביצוע  P2V:

This FREE tool remove the HP Proliant Support Pack from Virtualized Servers

http://ctxadmtools.musumeci.com.ar/HPPSPCleaner/HPPSPCleaner11.html

Processors and guest operating systems that support VMware Fault Tolerance

Processors and guest operating systems that support VMware Fault Tolerance

Details

VMware Fault Tolerance (FT) requires specific processors (CPUs) and guest operating systems.

Solution

Processors 

VMware collaborated with AMD and Intel in providing an efficient VMware FT capability on modern x86 processors. The collaboration required changes in both the performance counter architecture and virtualization hardware assists of both Intel and AMD and these have been included in all processors launched since early 2008.

Download the VMware SiteSurvey (http://www.vmware.com/download/shared_utilities.html ) utility to check if your configuration can run VMware FT.  

For VMware FT to be supported, the servers that host the virtual machines must use compatible processors selected from the categories as documented below. Processors within the same category are always compatible with each other. Intel Xeon Nehalem and Westmere processor types are also compatible with one another. Note that AMD Opteron Barcelona processors are not compatible with Intel processors.

Intel Xeon Penryn Category:

• 31xx Series
• 33xx Series
• 52xx Series 
• 54xx Series
• 74xx Series

Intel Xeon Nehalem Category:

• 34xx Series (Lynnfield)
• 35xx Series
• 55xx Series
• 65xx Series
• 75xx Series
• i3/i5 (Clarkdale)

The i3/i5 (Clarkdale) processor series is listed in the Nehalem category because its instruction set is most similar to that generation.

 Intel Xeon Sandy Bridge Category 1:

• E3-12xx Series

 Intel Xeon Sandy Bridge Category 2:

• i3-21xx Series

AMD Opteron Barcelona Category:

• 13xx Series
• 23xx and 24xx Series (DP)
• 41xx Series
• 61xx Series
• 83xx and 84xx Series (MP)

For a processor to be supported by vSphere Fault Tolerance, the Primary VM and Secondary VM must both be running on a version of ESX/ESXi that supports the processor. See http://www.vmware.com/resources/compatibility for more information.

Guest Operating Systems

The following table displays guest operating system support for VMware FT. For specific guest operating system version information, see the Guest Operating System Installation Guide at http://www.vmware.com/pdf/GuestOS_guide.pdf.

Note: A virtual machine can be FT-enabled while powered on only if marked with "ON" in the following table. The processor types that support this are also listed. Otherwise, the virtual machine must be powered off before FT is enabled.

Guest Operating System	Notes or Limitations
Windows 7	ON-Penryn Requires VMware vSphere 4.0 Update 1 or greater.
Windows Server 2008	ON-Penryn
Windows Vista	ON-Penryn
Windows Server 2003 (64 bit)	ON-Penryn
Windows Server 2003 (32 bit)	ON-Penryn Requires Service Pack 2 or greater when AMD Opteron Barcelona processor type is used.
Windows XP (64 bit)	ON-Penryn
Windows XP (32 bit)	ON-Penryn AMD Opteron Barcelona processor type is not supported.
Windows 2000	AMD Opteron Barcelona processor type is not supported.
Windows NT 4.0	AMD Opteron Barcelona processor type is not supported.
Linux (all ESX-supported distributions)	ON-Penryn
Netware Server	n/a
Solaris 10 (64-bit)	ON-Penryn Requires Solaris U1 when AMD Barcelona processor type is used.
Solaris 10 (32-bit)	ON-Penryn AMD Opteron Barcelona processor type is not supported.
FreeBSD (all ESX-supported distributions)	ON-Penryn

Note: System vendors are certifying that their systems work with FT. You can find details on the FT-certified systems at http://www.vmware.com/resources/compatibility. More systems are being certified all the time, so check back if your platform is not currently listed.

You can also check processor, operating system, and virtual machine configuration compliance with FT by downloading and running the VMware SiteSurvey utility from http://www.vmware.com/download/shared_utilities.html. It highlights compliance issues and describes how to correct them.

For more information about VMware Fault Tolerance, refer to the article: VMware Fault Tolerance FAQ (1013428)

Intel Xeon Westmere Category:

• 34xx Series (Clarkdale)
• 36xx Series 
• 56xx Series
• E7-28xx Series
• E7-48xx Series
• E7-88xx Series

 

1. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1008027


2. http://www.vmware.com/pdf/vsphere4/r41/vsp_41_availability.pdf

3. http://www.vmware.com/files/pdf/resources/ft_virtualization_wp.pdf

4. http://ntpro.nl/blog/archives/1090-Fault-Tolerance-Checklist.html

5. http://www.vmware.com/download/shared_utilities.html

 

V-79-57344-34004 - End of data set was unexpectedly encountered

Problem

We are using "Backup Exec 10D" with service pack4 from BUE. Currently trying to backup four physical servers, and one server always fails to to backup. Errors generated from the Backup Exec's job log:

Job log
Verify- \\Server\D: Unexpected end of backup set encountered on CERTANCE 1.
V-79-57344-34004 - End of data set was unexpectedly encountered.

Solution

Talked to other techs that use Backup Exec software and they were able to give me some tips for this error.

Fix1:
Force the NIC to the same speed of the switch it's connected to.
1. Go to Device manager by -> right clicking My Computer -> Manage
2. Select Device manager -> select NIC card -> right click NIC card
3. Advance TAB -> in the Property window select Speed & Duplex -> Change value drop down to forced speed, instead of "Auto"


Fix2:
1. Ensure the drivers you're using for the tape drives are compatible. This means if you have a tape library ensure the tape library drivers are manufactuers drivers. This is listed in your device manager as "Medium Changers."
2. Ensure the drivers for your "tape drives" are from Symantec Backup Exec. This is listed under your device manager as "Tape Drives."


The first fix1 solved my supposivly network issue.