Hüseyin Göksin Blog

Bilgi paylaştıkça çoğalır….

Error Code: 502 Proxy Error. The specified Secure Sockets Layer (SSL) port is not allowed. ISA Server is not configured to allow SSL requests from this

set isa=CreateObject("FPC.Root")
set tprange=isa.GetContainingArray.ArrayPolicy.WebProxy.TunnelPortRanges
set tmp=tprange.AddRange("SSL 9443", 9443, 9443)
tprange.Save

“A restart of the Microsoft Firewall Service is required after you run the script”

To add a tunnel port range with Microsoft Internet Security and Acceleration (ISA) Server 2004, this VBScript script will add port 10000:

Dim root 
Dim tpRanges 
Dim newRange 
Set root = CreateObject("FPC.Root")
Set tpRanges = root.GetContainingArray.ArrayPolicy.WebProxy.TunnelPortRanges
set newRange = tpRanges.AddRange("SSL 10000", 10000, 10000)
tpRanges.Save
Reklamlar

Filed under: Uncategorized

No vmcore disk partition is available and no network coredump server has been configured. Host core dumps cannot be saved

One of the nice features of ESXi 5.x is the possibility to run  a diskless system by using Auto Deploy.

When first booting the created image you’ll notice some errors which can be easily resolved.

‘No vmcore disk partition is available and no network coredump server has been configured. Host core dumps cannot be saved.’  &
‘System logs on host xxxx are stored on non-persistant storage.’

Quite a mouthful and even though we wouldn’t want to see an actual coredump we do need to fix this warning.
vCenter 5.1 now comes with a coredump & syslog server which integrates with vCenter (optional) and makes this a breeze.

On your vCenter server open the installer and install both options. Using the default options will work fine, for convenience I used the integrate into vCenter option on both.

Install

 

 

 

 

 

 

 

 

Once installed you have to activate them on your ESXi host. Make sure you do these steps before creating your Host Profile (or update it) so all host deployed later will get these settings on boot.
Open the configuration tab and select Security Profile. Click on Firewall Properties and check the syslog check box.

syslog

 

 

 

 

 

 

This will open ESXi firewall for outgoing traffic to the syslog server. Click OK and open Configuration – Software – Advanced Settings and scroll down to Syslog. Find Syslog.global.logHost and enter your syslogserver like: udp://your.syslogserver:514
Click OK and if all went fine, you’ll see you have one less warning in your host summary.

Fixing the second warning can be done in the actual Host Profile but I prefer to fix this before. We do need SSH access so click Configuration – Security Profile and select the Properties of the Security Profile. Select SSH and start it. If you want SSH access to remain after reboots select Start and stop with host.
This will add a new warning to the Summary which we’ll solve later on.

SSH

 

 

 

 

 

 

 

Now open up PuTTY connect your host, login as root and run the commands:
# esxcli system coredump network set --interface-name vmk0 --server-ipv4 10xx.xx.xx.xx --server-port 6500
replacing 10xx.xx.xx.xx with your core dump server.
Enable the new setting:
# esxcli system coredump network set --enable true

That’s it, no more warning on your host and when creating a Host Profile for deployment of more hosts these settings will be inherited.

To get rid of the SSH warning you could either stop the service or if you want to be able to connect to your host(s) with SSH simply open Configuration – Software – Advanced Settings and open UserVars. Scroll down to the bottom and at UserVars.SuppressShellWarning enter 1.

UserVars

Filed under: Esx Ailesi