PR ID/CR ID:	LSIP200149140
Headline:	TB FW Re-activate the user option to enable Patrol Read on SSD.
Description:	Internal notes: Most SSDs do their own patrol read and it isn't a good idea to do additional patrol reads. If we do this, do we do this for all customers? Please scope: 1) Read mode page first to see if SSD is already doing the background scan 2) if not, have NVDATA control for patrol read on SSD. 1) One line description of the customer issue (customer pain point). -> In current TB firmware (11M05), Patrol Read to SSD cannot be enabled. However, OEM requires Patrol Read in TB because their server supports SSD Patrol Read in Ruchbah and Castor. Also, SSD vendor shows the same error rate of unrecoverable error comparing to HDD, OEM thinks Parol Read is necessary. 2) List of affected components. Indicate pertinent HW, pre-boot apps, CLI, UX, etc. ->Firmware, MegaCLI(?) 3) Describe the current customer use cases. How is the product used today by this customer? What problems are encountered? Attach any pertinent logs and supporting information. -> OEM is enabling Patrol Read for both HDD and SSD. Once per week. 4) Describe the desired customer use cases. What behavior does the customer wish to see? How, specifically, does it differ from current behavior? What components does the customer request to be changed? Will any desired customization be under customer control, or remain under LSI control? ->They understand the risk of HDD/SSD Patrol Read if it's done too frequently. However, at least they need an option command to enable SSD Patrol Read from CLI to activate SSD PR in their factory. 6) Urgency. Describe the relative severity of the problem, in the customer‚s view. Are there time-critical considerations to be aware of? ->11M06 patch
State:		Implementation

IMP ID/CO ID:	LSIP200184338
Headline:	(auto4comp UNIV_VIVA_Cli) TB FW Re-activate the user option to enable Patrol Read on SSD.
Description:	Auto Create from PR LSIP200149140. Internal notes: Most SSDs do their own patrol read and it isn't a good idea to do additional patrol reads. If we do this, do we do this for all customers? Please scope: 1) Read mode page first to see if SSD is already doing the background scan 2) if not, have NVDATA control for patrol read on SSD. 1) One line description of the customer issue (customer pain point). -> In current TB firmware (11M05), Patrol Read to SSD cannot be enabled. However, OEM requires Patrol Read in TB because their server supports SSD Patrol Read in Ruchbah and Castor. Also, SSD vendor shows the same error rate of unrecoverable error comparing to HDD, OEM thinks Parol Read is necessary. 2) List of affected components. Indicate pertinent HW, pre-boot apps, CLI, UX, etc. ->Firmware, MegaCLI(?) 3) Describe the current customer use cases. How is the product used today by this customer? What problems are encountered? Attach any pertinent logs and supporting information. -> OEM is enabling Patrol Read for both HDD and SSD. Once per week. 4) Describe the desired customer use cases. What behavior does the customer wish to see? How, specifically, does it differ from current behavior? What components does the customer request to be changed? Will any desired customization be under customer control, or remain under LSI control? ->They understand the risk of HDD/SSD Patrol Read if it's done too frequently. However, at least they need an option command to enable SSD Patrol Read from CLI to activate SSD PR in their factory. 6) Urgency. Describe the relative severity of the problem, in the customer‚s view. Are there time-critical considerations to be aware of? ->11M06 patch
State:	Delivered
Associated Task:	LSIP200189612
Task References:	LSIP200149140

DFCT ID:	LSIP200147485
Headline:	Macon: In EFI environment CC cannot be started on a VD after performing Fast Init
Description:	Connect Few PDs and boot to EFI shell. Create raid1 thru EFI CLI. Using "megacli.efi ldinit start lN aN" start fast Initailization on raid 1. Now start CC on the raid1. "CC cannot be started on this VD at this time" error message is displayed. NOte: CC can be started on r1 if slow init is done . Details ------------ system: Canoe pass EFI Driver name: LSI EFI SAS DRIVER Driver Version: 02010000 EFI CLI version: 2.00.00 Drives: SATA
Steps to Reproduce:	1) Conncet few PDs and boot to EFI shell 2) Create 2 drive raid1 3) Using "megacli.efi ldinit start lN aN" start Initailization on raid 1 (Fast init) 4)Now start CC on raid 1. 5) CC cannot be started on VD after fast init is performed. Details ------------ system: Canoe pass EFI Driver name: LSI EFI SAS DRIVER Driver Version: 02010000 EFI CLI version: 2.00.00 Drives: SATA
Resolution:	updated Help
Fix Impact:	Medium
External Behavior Change:	No
Suggested Testing:	use "-force" with the command.
Child Tasks:	LSIP200189209

DFCT ID:	LSIP200184682
Headline:	Dos MegaCli doesn't show AdpFWFlash command syntax in the help menu.
Description:	Execute the command "MegaCli.exe -h " in Dos mode & check for AdpFwFlash command syntax.
Steps to Reproduce:	Execute the command "MegaCli.exe -h " in Dos mode & check for AdpFwFlash command syntax.
Resolution:	Dos help for megacli needs to be entered in a file other than general OS help. This has been done accordingly
Fix Impact:	Cosmetic
External Behavior Change:	No
Suggested Testing:	execute the command "MegaCli.exe -h" in DOS mode. You can find the AdpFwFlash command syntax, which was missing in earlier releases
Child Tasks:	LSIP200189626

DFCT ID:	LSIP200151201
Headline:	WB:Data not getting generated while trying to capture information through Megacli with IO running in background.
Description:	With the latest released build components we dont see data being getting generated inside logs while trying to capture information through Megacli with IO running in background. we expect data to be incremented as IO is running.we also tested the same feature in linux(SUSE 32 Bit) where we could see signifacant amount of data being incremented with continuation of test. LSIP200150311:will closethis defect and will be logging new one incontinuation of the issue observed. Configuration details: ---------------------- Driver version:megasas2.sys 5.1.112.32 FW version:2.130.03-1299 Controller:9262-8i OS:Win2k8 32 Bit CLI: 8.02.14 MSM: 8.31-06
Steps to Reproduce:	1.Create VDs with WB/WT, CIO policies, over R5, R6, R50, R60, DGs. 2.Create anyone Cachecade VD(R1,R0 or PRL11). 3.Full init all the VDs, and create file systems on the respective partiotions. 4.Start IO, (Use Chaos or winsmash) on all the VDs. 5.Enable the information captuing feature using MegaCli {MegaCLI –Perf -Start [-interval ] -aN} 6.With the IO running, after every interval of 5 minutes get the captured information in CSV format, {MegaCLI –Perf -Getresults [–format ] –f -aN} 7.Compare or see inside the logs with zero values.
Resolution:	Fixed by calculating the buffer size based on current configuration (current VD and SSCD count).
Fix Impact:	Medium
External Behavior Change:	No
Suggested Testing:
Child Tasks:	LSIP200189543

Task ID:	LSIP200130846
Headline:	130846 Release Task
Description:	Release Task
State:	Active
Change Set Files:
References:

Task ID:	LSIP200189543
Headline:	189543 CLI crashes on fetching performance metrics
Description:	CLI crashes on fetching performance metrics
State:	Delivered
Change Set Files:
References:	LSIP200151201(DFCT)

Task ID:	LSIP200189209
Headline:	189209 Macon: In EFI environment CC cannot be started on a VD after performing Fast Init
Description:	Macon: In EFI environment CC cannot be started on a VD after performing Fast Init
State:	Delivered
Change Set Files:
References:	LSIP200147485(DFCT)

Task ID:	LSIP200189626
Headline:	189626 Defect: Dos MegaCli doesn't show AdpFWFlash command syntax in the help menu.
Description:	Dos MegaCli doesn't show AdpFWFlash command syntax in the help menu.
State:	Delivered
Change Set Files:
References:	LSIP200184682(DFCT)

Task ID:	LSIP200094154
Headline:	94154 Release Task
Description:	Release Task
State:	Active
Change Set Files:
References:

Task ID:	LSIP200189291
Headline:	189291 VMware MegaSCU porting
Description:	VMware MegaSCU porting
State:	Delivered
Change Set Files:
References:

Task ID:	LSIP200189612
Headline:	189612 PR: (auto4comp UNIV_VIVA_Cli) TB FW Re-activate the user option to enable Patrol Read on SSD.
Description:	(auto4comp UNIV_VIVA_Cli) TB FW Re-activate the user option to enable Patrol Read on SSD.
State:	Delivered
Change Set Files:
References:	LSIP200184338(CO)

Task ID:	LSIP200093459
Headline:	93459 Release Task
Description:	Release Task
State:	Active
Change Set Files:
References: