Hi Guys - a customer has pointed out some confusing information regarding FA, ESXi ISCSI and port binding
According to https://core.vmware.com/resource/best-practices-running-vmware-vsphere-iscsi#sec7262-sub12 port binding is unsupported if the FA has iscsi-interfaces in 2 subnets. On https://support.purestorage.com/Solutions/VMware_Platform_Guide/User_Guides_for_VMware_Solutions/FlashArray_VMware_Best_Practices_User_Guide/VMware_and_iSCSI_FAQs#NIC_Teaming_vs_Port_Binding.2C_which_should_I_use.3F|https://support.purestorage.com/Solutions/VMware_Platform_Guide/User_Guides_for_VMware_S[…]ay_VMware_Best_Practices_User_Guide/VMware_and_iSCSI_FAQs it is stated "So which should you use? The answer here is clear, port binding whenever possible. This is not only recommended as a best practice with Pure Storage but by VMware as well."Solved901Views0likes12CommentsIs there a way, on the flasharray (either GUI or CLI) to check connections hitting a specific port on one of the controllers?
I've got a support case open on this as well, but it appears that we have no hosts hitting one particular port on our array despite all configs looking correct452Views0likes10CommentsRelease notes for purity
When I look at the release notes for purity https://support.purestorage.com/FlashArray/FlashArray_Release/01_Purity_FA_Release_Notes/9929_Purity%2F%2F%2F%2FFA_6.1.x_Release_Notes#6.1.22_Release_Notes Notes it says "Addresses several CVEs. (PURE-267648, PURE-261137)" - I cannot find anything regarding PURE-267648 and PURE-261137. I have tried searching the CVE db, but there is nothing about 6.1.22 and fixed CVEs. Where do i find this information?Solved412Views0likes3CommentsHi I've been trying to get the sql vvol script to refresh
Hi I've been trying to get the sql vvol script to refresh a secondary sql vm working and I think I'm close except for this line 109 Its not passing the arrary name. Any thoughts? Feel like I'm missing something?? Thanks!Solved401Views0likes5CommentsAnnouncing the General Availability of Purity//FA 6.9.2
We are happy to announce the general availability of 6.9.2, the third release of the 6.9 Long-Life Release (LLR) line and the thirteenth release based on the code line from 6.8! This LLR line provides long-term maintenance of the complete feature set introduced in the 6.8 Feature Release Line, including Fusion, with consistency in capabilities, user experience, and interoperability. This release includes support for R5 Controllers for FlashArray //X and //C, bringing performance, density, and data protection improvements to the 6.9 LLR line. For more detailed information about bug fixes and security updates included in each release, see the release notes. UPGRADE RECOMMENDATIONS AND EOL SCHEDULE Customers who are looking for long-term maintenance of the complete 6.8 feature set are encouraged to upgrade to the 6.9 LLR. Customers who are looking for continued delivery of all the newest capabilities as soon as they are available should upgrade to the 6.10 Feature Release line. When possible, customers should make use of Self-Service Upgrades (SSU) to ease the process of planning and executing non-disruptive Purity upgrades for their fleet. The 6.9 LLR line is planned for development through June 2028. HARDWARE SUPPORT This release is supported on the following FlashArray Platforms: FA//X (R3, R4, R5), FA//C (R3, R4, R5), FA//XL (R1, R5), FA//E, FA//RC20, and Pure Storage Cloud Dedicated (PSCD) for Azure and AWS. The PSCD release may take up to a week to be available on the AWS Marketplace and Azure Marketplace. Note, DFS software version 2.2.5 is recommended with this release. LINKS AND REFERENCES Purity//FA 6.9 Release Notes Self-Service Upgrades Purity//FA Release and End-of-Life Schedule FlashArray Hardware and End-of-Support DirectFlash Shelf Software Compatibility Matrix FlashArray Capacity and Feature Limits FlashArray Feature Interoperability Matrix400Views0likes0Comments