Nimble Storage CS260G Parts

I recently had a failure of an HDD and Power Supply on an aged Nimble Storage CS260G Storage Array [12x 3TB HDD, 4x 600GB SSD], 10Gb SFP+. This system is outside of the warranty and now at the end of life by Nimble, now part of HPE. So that has me replacing parts on my own.

The SSD Used for caching is a: Intel® SSD 320 Series Drive – 300GB, 2.5in SATA 3Gb/s, 25nm, MLC – Currently discontinued.

https://ark.intel.com/content/www/us/en/ark/products/56567/intel-ssd-320-series-300gb-2-5in-sata-3gb-s-25nm-mlc.html

INTEL SSDSA2CW300G3 : 300.0 GB [1/1/0, sa1] – il

Retailers may have them for sales on Amazon – https://amzn.to/2DJkirX

Next was the Power Supply which turns out to be a Supermicro 1200W 1U Redundant Power Supply (PWS-1K21P-1R)
Link: https://store.supermicro.com/1200w-1u-pws-1k21p-1r.html

I also found some fences on Amazon for these – https://amzn.to/2OK7pUC

Office 365: Increase Mailbox Size

Like most things, there is a predefined default, and at some point in time, there will be a need to deviate from this. Office 365 Admins should have an understanding of those and setup procedures to increase the size for individuals or the organization when the need arises

To increase the Office 365 Mailbox size we must use Windows PowerShell as the Web UI lacks the ability to make such changes at this time.

Step 1: Connect to Office 365 – Exchange Online:
An Office 365 Exchange Online Admin Account is Required

$UserCredential = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
Import-PSSession $Session

Step 2: Get information about the mailbox you are looking to increase size on. I like to take note of the results before and then after I introduce changes

Get-Mailbox jermsmit | Out-GridView
Get-Mailbox jermsmit | Select *quota

Step 3: Issue the command to increase the storage:
Example: Set-Mailbox -ProhibitSendQuota -ProhibitSendReceiveQuota -IssueWarningQuota

Set-Mailbox jermsmit -ProhibitSendQuota 69.5GB -ProhibitSendReceiveQuota 70GB -IssueWarningQuota 69GB

Step 4: Review your changes, for this we goto step Step 2

For more information on Office 365 Mailbox Limits, please visit the following: https://docs.microsoft.com/en-us/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#mailbox-storage-limits

If your looking for a good Essentials for Administration of Exchange online please swing by Amazon for an excellent book: https://amzn.to/34LeVUN

International Men’s Day 2019

International Men’s Day is an opportunity to share positive contributions and raise awareness for issues related to men around the world. We don’t like to talk about it much, but suicide is one of the leading causes of death, disease, and injury among men globally – in fact (per the article) suicide is the top killer of men under the age of 45.

But the stigma around #mentalhealth and #suicideprevention persists – according to a recent survey, only 31% of males claimed to be willing to discuss their feelings with another person.

If you or someone you care about is in crisis, please seek help immediately:

Call 911(US), 999(UK), 112(EU), 119(JP)

Visit a nearby emergency department or your health care provider’s office.

In the US Call the toll-free, 24-hour hotline of the National Suicide Prevention Lifeline at 1-800-273-TALK (1-800-273-8255); TTY: 1-800-799-4TTY (4889) to talk to a trained counselor.

Please see the article link in the comment below:
https://www.independent.co.uk/life-style/international-mens-day-2019-when-is-it-date-celebrate-men-mental-health-movember-a9204376.html

Cross-Origin Resource Sharing (CORS)

Cross-origin resource sharing is a mechanism that allows restricted resources on a web page to be requested from another domain outside the domain from which the first resource was served. A web page may freely embed cross-origin images, stylesheets, scripts, iframes, and videos

Cross-Origin Resource Sharing (CORS) is a mechanism that uses additional HTTP headers to tell browsers to give a web application running at one origin, access to selected resources from a different origin. A web application executes a cross-origin HTTP request when it requests a resource that has a different origin (domain, protocol, or port) from its own.

An example of a cross-origin request: the front-end JavaScript code served from https://domain-a.com uses XMLHttpRequest to make a request for https://domain-b.com/data.json.

For security reasons, browsers restrict cross-origin HTTP requests initiated from scripts. For example, XMLHttpRequest and the Fetch API follow the same-origin policy. This means that a web application using those APIs can only request resources from the same origin the application was loaded from, unless the response from other origins includes the right CORS headers.

The CORS mechanism supports secure cross-origin requests and data transfers between browsers and servers. Modern browsers use CORS in a APIs such as XMLHttpRequest or Fetch to mitigate the risks of cross-origin HTTP requests.

source: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS

What is CoreXL & SecureXL

  • CoreXL: Technology that makes use of multiple processor cores
  • SecureXL: Connection acceleration technology (both throughput and connection establishment)

SecureXL is an acceleration solution that maximizes the performance of the Checkpoint Firewall. When SecureXL is enabled on a Security Gateway, some CPU intensive operations are processed by virtualized software instead of the Firewall kernel. This is said to allow the Firewall the ability to inspect and process connections more efficiently and accelerate throughput and connection rates.

Secure XL traffic flows: (from admin guide)

  • Slow path – Packets and connections that are inspected by the Firewall and are not processed by SecureXL.
  • Accelerated path – Packets and connections that are offloaded to SecureXL and are not processed by the Firewall.
  • Medium path – Packets that require deeper inspection cannot use the accelerated path. It is not necessary for the Firewall to inspect these packets, they can be offloaded and do not use the slow path. For example, packets that are inspected by IPS cannot use the accelerated path and can be offloaded to the IPS PSL (Passive Streaming Library). SecureXL processes these packets more quickly than packets on the slow path.

CoreXL is a performance-enhancing technology for Security Gateways on multi-core processing platforms. CoreXL enhances Security Gateway performance by enabling the processing cores to concurrently perform multiple tasks.

CoreXL joins ClusterXL Load Sharing and SecureXL as part of Check Point’s fully complementary family of traffic acceleration technologies.