PPG may reject MMSC connections

By default the PPG is configured with the tw_recycle setting enabled:

[root@ppg2 ~]# awk '/# Added by Gemini Mobile/,/recycle/' /etc/sysctl.conf# Added by Gemini Mobile 'factory' framework:##net.ipv4.tcp_tw_recycle = 1

This allows the fast reuse of connections in the TIME-WAIT queue. As an extra check it rejects the connection if a SYN packet arrives with timestamp (TSVal) smaller than the last known timestamp from this peer. This check is additional to the PAWS protection, but it only works if the TSVal values of the packets received from the same IP address are monotonically increasing.

This requirement is not met when the MMSC is behind NAT. The man page is also clear that this causes problems with NAT:

 tcp_tw_recycle (Boolean; default: disabled; since Linux 2.4) Enable fast recycling of TIME_WAIT sockets. Enabling this option is not recommended since this causes problems when working with NAT (Network Address Translation).

Because reuse of connections in the TIME-WAIT state may be needed for a high rate of requests, the tw_reuse option should be set:

 tcp_tw_reuse (Boolean; default: disabled; since Linux 2.4.19/2.6) Allow to reuse TIME_WAIT sockets for new connections when it is safe from protocol viewpoint. It should not be changed without advice/request of technical experts.

Related:

  • No Related Posts

Re: Unable to boot to utility partition on VNX5300, help!

System is out of warranty and a lab system, its working but i want to reload the image on it because some configuration won’t let me delete it.

I boot it up with serial cable attached, and hit ctrl-c and per “Backrev Array” solution it’s supposed to do a Minisetup and reboot a few times. It never reboots it just sits at the “int13 – EXTENDED READ (4000)” and never goes further.

I rebooted it manually myself and try to start the process again but I just get this… any ideas?

ABCDabcdEFabcd << Stopping after POST >> GabcdefHabcdefIabcdefJabcdeKLabMabNabOabcPQRSTUVWabXYabZAABBCCabDDabcEEabcFFabcGGabcHHabcIIabJJabKKLLMMNNOOPPQQRRSSTTUUVVWWXX

************************************************************

* Extended POST Messages

************************************************************

INFORMATION: POST Start

INFORMATION: MCU Operating mode changed from Linux to Clariion

INFORMATION: PSB not present

************************************************************

EndTime: 10/28/2018 15:29:59

…. Storage System Failure – Contact your Service Representative …

*******

Enclosure: 0x0008000B : Added to Table

Motherboard: 0x00130009 : Added to Table

Memory: 0x00000001

DIMM 0: 0x00000001

DIMM 1: 0x00000001

DIMM 2: 0x00000001

Mezzanine: 0x00100007

I/O Module 0: 0x00000001 : Added to Table

I/O Module 1: 0x00000001 : Added to Table

Power Supply A: 0x000B0014

Power Supply B: 0x00000001

0x00130009: MCU 0540

0x00130009: CMDAPP 0504

0x00130009: CMDTABLE 0096

0x00130009: CMDBOOT 0002

0x00130009: PLX 0305

0x000B0014: PS FW 0027

Checksum valid

Relocating Data Directory Boot Service (DDBS: Rev. 05.03)…

DDBS: K10_REBOOT_DATA: Count = 1

DDBS: K10_REBOOT_DATA: State = 0

DDBS: K10_REBOOT_DATA: ForceDegradedMode = 0

DDBS: **** WARNING: SP rebooted unexpectedly before completing MiniSetup on the Utility Partition.

DDBS: MDDE (Rev 600) on disk 1

DDBS: MDDE (Rev 600) on disk 3

DDBS: MDB read from both disks.

DDBS: Chassis and disk WWN seeds match.

DDBS: First disk is valid for boot.

DDBS: Second disk is valid for boot.

Utility Partition image (0x0040000F) located at sector LBA 0x1453D802

Disk Set: 1 3

Total Sectors: 0x013BA000

Relative Sectors: 0x00000800

Calculated mirror drive geometry:

Sectors: 63

Heads: 255

Cylinders: 1287

Capacity: 20686848 sectors

Total Sectors: 0x013BA000

Relative Sectors: 0x00000800

Calculated mirror drive geometry:

Sectors: 63

Heads: 255

Cylinders: 1287

Capacity: 20686848 sectors

Stopping USB UHCI Controller…

Stopping USB UHCI Controller…

EndTime: 10/28/2018 15:33:37

int13 – RESET (1)

int13 – CHECK EXTENSIONS PRESENT (3)

int13 – CHECK EXTENSIONS PRESENT (5)

int13 – GET DRIVE PARAMETERS (Extended) (6)

int13 – EXTENDED READ (200)

int13 – EXTENDED READ (400)

int13 – EXTENDED READ (600)

int13 – READ PARAMETERS (800)

int13 – READ PARAMETERS (802)

int13 – DRIVE TYPE (803)

int13 – CHECK EXTENSIONS PRESENT (804)

int13 – GET DRIVE PARAMETERS (Extended) (805)

int13 – READ PARAMETERS (806)

int13 – EXTENDED WRITE (846)

int13 – EXTENDED WRITE (847)

int13 – EXTENDED WRITE (848)

int13 – READ PARAMETERS (964)

int13 – DRIVE TYPE (965)

int13 – CHECK EXTENSIONS PRESENT (966)

int13 – GET DRIVE PARAMETERS (Extended) (967)

int13 – READ PARAMETERS (968)

int13 – EXTENDED WRITE (997)

int13 – EXTENDED WRITE (998)

int13 – EXTENDED WRITE (999)

int13 – EXTENDED READ (1000)

int13 – EXTENDED WRITE (1012)

int13 – EXTENDED WRITE (1013)

int13 – EXTENDED WRITE (1014)

int13 – EXTENDED READ (1200)

int13 – EXTENDED READ (1400)

int13 – EXTENDED READ (1600)

int13 – EXTENDED READ (1800)

int13 – EXTENDED READ (2000)

int13 – EXTENDED READ (2200)

int13 – EXTENDED READ (2400)

int13 – EXTENDED READ (2600)

int13 – EXTENDED READ (2800)

int13 – EXTENDED READ (3000)

int13 – EXTENDED READ (3200)

int13 – EXTENDED READ (3400)

int13 – EXTENDED READ (3600)

int13 – EXTENDED READ (3800)

int13 – EXTENDED READ (4000)

It doesn’t seem to ever go past this… so I cannot move on to the next steps in the solution.

any help or experience with this would be much appreciated!

-M

Related:

  • No Related Posts

BSOD after deploying sysprepped image

I need a solution

I’ve been having periodic issues deploying sysprepped images with GSS 3 (we’re currently on 3.2 RU6) but managed to get it working on Windows 10 1709 and 1803 – until today. The problem has surfaced again and I think I can trace it to GSS writing files to the wrong partition. I have a deployment task for a sysprepped image with a custom unattend file that fails randomly; sometimes on certain models, and other times on models that work 99% of the time. The result is after laying down the image, it reboots to a blue screen claiming that the registry is corrupt. When I boot the machine with a recovery USB, I open the command line and run notepad. I can see that the System Reserved drive is labelled C, and in that drive is a “windows” directory, with a “panther” subdirectory (note that they aren’t capitalized) that contains our unattend file named unattend.xml. I assume this is GSS copying our custom unnattend file to C:windowspanther – except it appears that GSS (or WinPE) thinks the reserved partition is the system drive and writes the unattend file to it, causing corruption and ultimately the blue screen on boot. Another example of this is that I have a script that will write to the WindowsSetupScriptssetupcomplete.cmd file in order to install the DAgent on first boot (for portability, since we have multiple GSS servers in our environment), except I have to specify that drive as D: for WinPE to write to the correct partition.

REM Point DAgent to correct ghost server
md D:WINDOWSSETUPSCRIPTS
ECHO msiexec /i C:DAgentdagent_x64.msi /qn server_tcp_addr=%DSSERVER% server_tcp_port=402 >> D:WINDOWSSETUPSCRIPTSsetupcomplete.cmd

Is there an easy way to mitigate this? I don’t know of a way to either force WinPE to see the correct drive letters, or to specify where to copy the unattend file since WinPE sees the System Reserve partition as the C drive.

0

Related:

  • No Related Posts

Ghost not deploying image but no logs

I need a solution

I have a decent number of machiens that ghost seems to fail at but it is not creating the ghost error logs in PE.

This is the error shown in the console

ErrorMessage: Exception has occured in File Tcube_ClientImageDeploy.cpp at Line No 978. Type of exception is ClientImageDeployException. Error Description is Child Process returned an error. The exit code from process is 3. Value of Windows error code = 183 and message is Cannot create a file when that file already exists.

I have tried gdisk64 to delete partitions in case its somethign with that and that gives me the error regardless of what gdisk64 parameter I try

gdisk64 (W) fixed disk has partitions) that extend past the end of the disk

I have also tried diskpart and get errors there too.  I know we can’t all of a sudden have 100 drive failures, so any help is appreciated as they do pass the internal computer drive tests.

0

Related:

  • No Related Posts

Unable to boot to utility partition on VNX5300, help!

System is out of warranty and a lab system, its working but i want to reload the image on it because some configuration won’t let me delete it.

I boot it up with serial cable attached, and hit ctrl-c and per “Backrev Array” solution it’s supposed to do a Minisetup and reboot a few times. It never reboots it just sits at the “int13 – EXTENDED READ (4000)” and never goes further.

I rebooted it manually myself and try to start the process again but I just get this… any ideas?

ABCDabcdEFabcd << Stopping after POST >> GabcdefHabcdefIabcdefJabcdeKLabMabNabOabcPQRSTUVWabXYabZAABBCCabDDabcEEabcFFabcGGabcHHabcIIabJJabKKLLMMNNOOPPQQRRSSTTUUVVWWXX

************************************************************

* Extended POST Messages

************************************************************

INFORMATION: POST Start

INFORMATION: MCU Operating mode changed from Linux to Clariion

INFORMATION: PSB not present

************************************************************

EndTime: 10/28/2018 15:29:59

…. Storage System Failure – Contact your Service Representative …

*******

Enclosure: 0x0008000B : Added to Table

Motherboard: 0x00130009 : Added to Table

Memory: 0x00000001

DIMM 0: 0x00000001

DIMM 1: 0x00000001

DIMM 2: 0x00000001

Mezzanine: 0x00100007

I/O Module 0: 0x00000001 : Added to Table

I/O Module 1: 0x00000001 : Added to Table

Power Supply A: 0x000B0014

Power Supply B: 0x00000001

0x00130009: MCU 0540

0x00130009: CMDAPP 0504

0x00130009: CMDTABLE 0096

0x00130009: CMDBOOT 0002

0x00130009: PLX 0305

0x000B0014: PS FW 0027

Checksum valid

Relocating Data Directory Boot Service (DDBS: Rev. 05.03)…

DDBS: K10_REBOOT_DATA: Count = 1

DDBS: K10_REBOOT_DATA: State = 0

DDBS: K10_REBOOT_DATA: ForceDegradedMode = 0

DDBS: **** WARNING: SP rebooted unexpectedly before completing MiniSetup on the Utility Partition.

DDBS: MDDE (Rev 600) on disk 1

DDBS: MDDE (Rev 600) on disk 3

DDBS: MDB read from both disks.

DDBS: Chassis and disk WWN seeds match.

DDBS: First disk is valid for boot.

DDBS: Second disk is valid for boot.

Utility Partition image (0x0040000F) located at sector LBA 0x1453D802

Disk Set: 1 3

Total Sectors: 0x013BA000

Relative Sectors: 0x00000800

Calculated mirror drive geometry:

Sectors: 63

Heads: 255

Cylinders: 1287

Capacity: 20686848 sectors

Total Sectors: 0x013BA000

Relative Sectors: 0x00000800

Calculated mirror drive geometry:

Sectors: 63

Heads: 255

Cylinders: 1287

Capacity: 20686848 sectors

Stopping USB UHCI Controller…

Stopping USB UHCI Controller…

EndTime: 10/28/2018 15:33:37

int13 – RESET (1)

int13 – CHECK EXTENSIONS PRESENT (3)

int13 – CHECK EXTENSIONS PRESENT (5)

int13 – GET DRIVE PARAMETERS (Extended) (6)

int13 – EXTENDED READ (200)

int13 – EXTENDED READ (400)

int13 – EXTENDED READ (600)

int13 – READ PARAMETERS (800)

int13 – READ PARAMETERS (802)

int13 – DRIVE TYPE (803)

int13 – CHECK EXTENSIONS PRESENT (804)

int13 – GET DRIVE PARAMETERS (Extended) (805)

int13 – READ PARAMETERS (806)

int13 – EXTENDED WRITE (846)

int13 – EXTENDED WRITE (847)

int13 – EXTENDED WRITE (848)

int13 – READ PARAMETERS (964)

int13 – DRIVE TYPE (965)

int13 – CHECK EXTENSIONS PRESENT (966)

int13 – GET DRIVE PARAMETERS (Extended) (967)

int13 – READ PARAMETERS (968)

int13 – EXTENDED WRITE (997)

int13 – EXTENDED WRITE (998)

int13 – EXTENDED WRITE (999)

int13 – EXTENDED READ (1000)

int13 – EXTENDED WRITE (1012)

int13 – EXTENDED WRITE (1013)

int13 – EXTENDED WRITE (1014)

int13 – EXTENDED READ (1200)

int13 – EXTENDED READ (1400)

int13 – EXTENDED READ (1600)

int13 – EXTENDED READ (1800)

int13 – EXTENDED READ (2000)

int13 – EXTENDED READ (2200)

int13 – EXTENDED READ (2400)

int13 – EXTENDED READ (2600)

int13 – EXTENDED READ (2800)

int13 – EXTENDED READ (3000)

int13 – EXTENDED READ (3200)

int13 – EXTENDED READ (3400)

int13 – EXTENDED READ (3600)

int13 – EXTENDED READ (3800)

int13 – EXTENDED READ (4000)

It doesn’t seem to ever go past this… so I cannot move on to the next steps in the solution.

any help or experience with this would be much appreciated!

-M

Related:

  • No Related Posts

ScaleIO: Cannot install Windows 2012 on VxRack Node hardware

Article Number: 493737 Article Version: 3 Article Type: Break Fix



ScaleIO 1.32.1,ScaleIO 1.32.2,ScaleIO 1.32.3,ScaleIO 1.32.4,ScaleIO 1.32.5,ScaleIO 1.32.6,ScaleIO 2.0,ScaleIO 2.0.0,ScaleIO 2.0.0.1,ScaleIO 2.0.0.2,ScaleIO 2.0.0.3,ScaleIO 2.0.1,ScaleIO 2.0.1.1

Issue Description

Unable to install Windows 2012 R2 on VxRack Node hardware

Scenario

Customer is following the SolVe Desktop procedures to install Windows 2012 R2 on VxRack Node hardware and is failing at the “Windows Setup” screen.

Symptoms

Upon choosing which partition to install Windows to in the “Windows Setup” screen and hitting the “Next” button, an error will pop up:

“Windows cannot be installed to this disk. This computer’s hardware may not

support booting to this disk . Ensure that the disk’s controller is enabled in the

computer’s BIOS menu.”

User-added image

Impact

Cannot install Windows OS to the VxRack Node hardware, upon which ScaleIO will be installed.

Windows will not recognize the UEFI disk as bootable.

Workaround

If the SolVe Desktop procedures have been followed precisely, the workaround is to make the boot disk use legacy mode.

In the BIOS of the VxRack node, change the following settings:

  1. Advanced -> CSM Configuration -> Storage -> Legacy
  2. Boot -> Boot Mode -> Legacy
  3. Boot -> Boot Option #1 -> Hard Disk:(Bus 03 Dev 00)PCI Raid Adapter

    This can be manipulated under “Boot -> Hard Disk Drive BBS Priorities

If step #3 shows the satadom, make sure that the virtual drive has already been created. If it has, reboot the host one more time to show the hard drive correctly in step #3.

This will allow Windows to see the disk as bootable and then successfully install Windows 2012 on the hard drive.

Impacted versions

v1.32.x

v 2.0.x

Fixed in version

N/A

Related:

Converting Linux VMDK to GHO file, Error 652

I need a solution

Hi. I’m following the instructions found here to create a ghost file from a Linux virtual machine. Unfortunately I’m encountering some issues. In the command prompt, I get the message “ABORT: 62, Attempted to access an inconsistent Linux partition. Operation aborted at user request”

It’s Ubuntu 18.04, file system is ext4

Any help appreciated. Thanks.

0

Related:

Need Help in replacing Boot drive

Hi,

We have just got our support contract expired and we will renewing the contract in some days, but we got 1 boot drive replacement alert and our third party hardware support is replacing the boot drive

We need to replace the boot drive on NL400 node, I have got the document regarding it. Can some one brief me out the list of commands that need to be on cluster

I’m just aware the FRU package needs to be installed and drive firmware update needs to be done, where the firmware packages needs to be placed, it just says drag and drop on the cluster

Related:

Guard Boot stopped showing up on dual boot encrypted windows with unencrypted linux

I need a solution

Hi,

It uses to work great for both windows and linux, and suddently the boot guard dissapeared and not showing up on power on / restart

Now the Guard Boot not showing up, it goes straith to grub bootloader, from there i can successfully boot unencrypted linux.

But can’t boot encrypted windows. 

I tried restoring the guard boot, by downloading recovery image.

If i boot from recovery image, the drive is recognized, i enter my passphrase and successfully boot to windows.

From there i tried running:

pgpwde –recover –disk 0
 

But i get:
Error: This drive is already managed.

0

Related:

NetScaler SDX Single Bundle Upgrade Failure When Upgrading from 12.0.57.24 to 12.0.58.15 or 12.1.48.13

For the NetScaler SDX single bundle upgrade to succeed, disk space used as reported by XenServer/Dom0 filesystem should be equal to or lower than 72%.

Before upgrading the SDX appliance, check the available space on XenServer and Dom0 partition. Run the df / command to check the amount of disk space used (Use%). If the disk space does not meet the requirement, don’t proceed with the upgrade until you’ve cleared the disk space.

Example 1: Failure scenario where disk use is greater than 72%

In the example below, disk space used by XenServer filesystem is reported as 75%. Amount of space used by logs in /var/log directory is reported over 400 Mb. This will cause the single bundle upgrade to fail.

[root@netscaler-sdx ~]# df /Filesystem 1K-blocks Used Available Use% Mounted on/dev/sda2 4128448 2927040 991696 75% /[root@netscaler-sdx ~]#[root@netscaler-sdx ~]#[root@netscaler-sdx ~]# cd /var/log/[root@netscaler-sdx log]# du . -sh483M .

For SDX appliances in which RAID is deployed, disk reported disk partition is /dev/md_d0p2 instead of /dev/sda2.

Example 2: Working scenario where disk use is less than or equal to 72%

 [root@netscaler-sdx]# df /Filesystem 1K-blocks Used Available Use% Mounted on/dev/md_d0p2 4128448 2821304 1097432 72% / cd /var/log [root@netscaler-sdx log]# df /Filesystem 1K-blocks Used Available Use% Mounted on/dev/md_d0p2 4128448 2821304 1097432 72% / [root@netscaler-sdx ~]# cd /var/log/[root@netscaler-sdx log]# du . -sh215M

Related: