Sangfor Community»Categories General Activity & Notice [Ended] Round 13 | Technical Document Scavenger Hunt

[Ended] Round 13 | Technical Document Scavenger Hunt

views: 676 | comments: 15 | added to Favorites 0
Lights on | 提示:支持键盘翻页<-左 右->
    组图打开中,请稍候......
Created: 2024-Dec-03 09:02

Summary:

Reply

Apriyanto Posted 2024-Dec-09 22:06
Q1: What should you do before upgrading the HCI cluster?     
Confirm the Upgrade path
Go to Sangfor community download the aDeploy tool
Launch the aDeploy clik Pre-change Check > Pre-upgrade Check.
The Platorm select X86 use the drop-down arrow select the HCI cluster current version and target version click search, then in the below will shows the recommended upgrade path.
You can go Sangfor community download the version you need to upgrade the cluster.
Pre-upgrade Check
Select the target version fill in the cluster ip and password, then click Start Check. It will take some time.
Notice: make sure that the SSH port has been enabled of the HCI. You can login HCI cluster go to System > Port Management have a check.
Click Cose then click Install.

Q2: Will rolling back an HCI patch impact the business and why?
Yes, it will because patch rollback need reboot all the nodes in the cluster.

Q3: How to get the HCI cluster upgrade license?
After get the SCP or HCI device information you can get ask the local region sales to help get the license file.

Q4: After the license expires, you must complete the license update within a specific timeframe to avoid affecting ongoing business operations. What is the specific timeframe in days?
HCI and SCP will continue to function normally for 30 days.

Q5: What is the difference between SCP license and HCI license?
SCP can manage multiple HCI clusters and distribute its license to these managed HCI clusters, whereas HCI license can only be used for itself.

Q6: What is the minimum host CPU license required if the SCP manages two HCI clusters—one cluster with 16 CPUs in centralized mode and the other with 8 CPUs in standalone mode?

2 host because SCP centralized mode cannot be switched to standalone mode, and vice versa.
Noviyanto Posted 2024-Dec-09 10:37
Q1 1) Use adeploy to perform a pre-upgrade check on the cluster.
   2) After resolving any issues detected by adeploy, apply the pre-check package to the cluster.
   3) Upload the upgrade package in the HCI interface and follow the prompts to proceed with the upgrade.
Q2 Yes it will because patching rollback need reboot all the nodes in the cluster.
Q3 We can get ask the local region sales to help get the license file.
Q4 30 days
Q5 SCP can manage multiple HCI clusters and distribute its license to these managed HCI clusters, whereas HCI license can only be used for itself.
Q6 2 licenses
pbeugenio Posted 2024-Dec-08 12:39
Q1: 1) Use adeploy to perform a pre-upgrade check on the cluster.

    2) After resolving any issues detected by adeploy, apply the pre-check     package to the cluster.

Q2: patch rollback need reboot all the nodes in the cluster.

Q3:System > Licensing Management

Q4: 30 days

Q5: SCP can manage multiple HCI clusters and distribute its license to these managed HCI clusters, whereas HCI license can only be used for itself.

Q6: 24 CPU


ND Posted 2024-Dec-04 17:42
Q1: 1) Use adeploy to perform a pre-upgrade check on the cluster.
       2) After resolving any issues detected by adeploy, apply the pre-check package to the cluster.
       3) Upload the upgrade package in the HCI interface and follow the prompts to proceed with the upgrade.

Q2: Yes, rollback needs to reboot all nodes in the cluster.

Q3: After get the SCP or HCI device information you can get ask the local region sales to help get the license file.

Q4: 30 days

Q5: SCP can manage multiple HCI clusters and distribute its license to these managed HCI clusters, whereas HCI license can only be used for itself.

Q6: 24
JJ Teoh Posted 2024-Dec-04 11:53
Q1: Use adeploy to perform a pre-upgrade check on the cluster.
Q2: Yes, as patch rollback need reboot all the nodes in the cluster.
Q3: System > Licensing Management, export the device info file, then can get ask the local region sales to help get the license file.
Q4: 30 days
Q5: SCP can manage multiple HCI clusters and distribute its license to these managed HCI clusters, whereas HCI license can only be used for itself.
Q6: 16
Rotring Posted 2024-Dec-03 22:18
Q1:
1. Backup Critical Data
2. Check Compatibility
3. Review Release Notes
4. Test in a Staging Environment
5. Check System Health
6. Plan for Downtime
7. Verify Resource Availability
8. Update Firmware and Drivers
9. Document Current Configuration
10. Prepare a Rollback Plan
11. Download Upgrade Packages
Q2:
Yes, rolling back an HCI patch can impact the business, depending on the situation.
Reasons and Implications:
1.VM Downtime
2.Configuration Changes
3.Data Integrity Risks
4.Cluster Stability
5.Business Continuity
6.Resource Availability
Mitigation Strategies:
Plan Rollbacks Carefully
Backup Data
Test Rollback Procedures
Communicate with Stakeholders
Q3:
1. Contact the Vendor or Reseller
2. Provide Licensing Information
3. Verify Upgrade Eligibility
4. Access the Customer Portal
5. Request Through Support
6. Receive and Apply License
7. Confirm License Activation
Q4 : 90 days
Q5 : SCP license is geared towards managing storage resources in a traditional environment, whereas an HCI license covers the management of a unified infrastructure, including storage, compute, and networking resources.
Q6 : The minimum host CPU license required for the SCP to manage the two HCI clusters would be 24 CPUs.
Enrico Vanzetto Posted 2024-Dec-03 22:14
Q1:1) Use adeploy to perform a pre-upgrade check on the cluster. 2) After resolving any issues detected by adeploy, apply the pre-check package to the cluster. 3) Upload the upgrade package in the HCI interface and follow the prompts to proceed with the upgrade.
Q2:Yes, because patch rollback need reboot all the nodes in the cluster.
Q3:Collect and share this information with the local sales team, and then proceed to update or expand the license.
Q4:30
Q5:SCP can manage multiple HCI clusters and distribute its license to these managed HCI clusters, whereas HCI license can only be used for itself.
Q6:24 CPU
pmateus Posted 2024-Dec-03 17:33
Q1. Do a  Pre-upgrade Check.
Q2. yes, need reboot all the nodes
Q3. System > Licensing Management
Q4. 30 days
Q5. HCI all the modules will be licensed automatically. SPC we need to do it manually
Q6. 24
CLELUQMAN Posted 2024-Dec-03 16:37
Q1 : Before get the HCI device information should create the HCI cluster first.

Q2 : Yes, the original license will be lost

Q3 : ask the local region sales to help get the license file.

Q4 : 30 days

Q5 : SCP can manage multiple HCI clusters and distribute its license to these managed HCI clusters, whereas HCI license can only be used for itself.

Q6 :  24 CPUs
Humayun Ahmed Posted 2024-Dec-03 15:56
Q1: Check the current version, active/standby SCP, disaster recovery scenarios, ongoing task and the number and capacity of disks of SCP VMs.

Q2: Yes, Service Downtime, Inconsistent State, Data Integrity Risks, Dependency Conflicts, Performance Issues and Business Disruption.

Q3: After get the SCP or HCI device information you can get ask the local region sales to help get the license file.

Q4: 30 days.

Q5: SCP can manage multiple HCI clusters and distribute its license to these managed HCI clusters, whereas HCI license can only be used for itself.

Q6: 24 CPU licenses.