To have a better experience, please upgrade your IE browser.upgrade
Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
Smart Modular Data Centers
Prefabricated Modular Data Centers
Precision Air Conditioners
Data Center Management
Handsets and Terminals
Rapid Deployment System
Enterprise Communications Terminals
Platform or Infrastructure
Enterprise Communications Gateways
Core Network Devices
Radio Access Network Devices
Firewall and Application Security Gateway
DDoS Protection Systems
Anti-APT Based on Big Data Analysis
ME Series Multi-Service Control Gateways
Multi-Service Packet Transport Platforms
AR Series IoT Gateways
AR Series Access Routers
Hybrid Flash Storage
Integrated Video Site Solution
Enterprise Telecom Energy
Smart Site Management System
Multi-Service Transmission Platforms
HD Network Cameras
Video Cloud Nodes
Video Content Management
Indoor Access Points
Outdoor Access Points
Scenario-specific product series
IT Infrastructure Storage Solutions
Data Center Network
Data Center Energy
Enterprise Communications Solution
Contact Center Solution
Advisory and Implementation
Support and Optimization
Training and Certification
Explore Technology Services
National Research and Education Network
Education Cloud Data Center
Multi-Channel HD Telemedicine Solution
Over The Top/Multi-Tenant Data Center (OTT/MTDC)
Internet Exchange Point (IXP)
Internet Access Provider (IAP)
Design & Simulation
Planning & Analytics
Oil & Gas IoT
HPC & Operations Management
Digital Urban Rail
Retail Cloud Platform
Enterprise Data Center
Enterprise Cloud Communications
Network Management System
Buy from Huawei
If you need to get information about your project, please submit your information and we will contact you within one working day.
Consult online customer service regarding products/solutions you are interested in.
If your company has signed an eDeal contract with Huawei, please buy your required product/solution via the link below.
Buy from resellers
Search for a nearby reseller and get direct contact information.
Find a Partner
Become a Partner
Alliance and solution Partner
Huawei Authorized Learning Partner
Huawei Authorized Information and Network Academy
Product and version information:
The host and the storage array were properly connected through a direct connection or SAN network. Log in to the storage array management system and map two LUNs, for example 10 GB LUN0 and 20 GB LUN1, to the host. Log in to the host, scan for the mapped LUNs, and check the LUN status, quantity, and capacities. On the storage array management system, delete the two LUNs mapped to the host, and map another two LUNs to the host, which have different capacities from the forementioned LUNs, for example 30 GB LUN2 and 40 GB LUN3. On the host, scan for the newly mapped LUNs. There is a possibility that the capacities of the mapped LUNs appear to be different from their actual capacities, even after the host is restarted.
To update the capacity information, perform the following steps:
1. Run the reboot command to restart the Solaris10U9ForX86 host.
2. Run the cfgadm -al command to scan for LUNs.
3. Use the format tool to delete the disk partition information of former LUNs. The disk partition information is retained on the location of the host LUN IDs of the mapped LUNs.The following uses host LUN ID 2 as an example. Perform the following steps:
a. Run the format command, and enter 2 at the cursor. The output is shown in Figure1.
Figure 1 Selecting disk 2
b. Enter fdisk at the cursor. The output is shown in Figure2.
Figure 2 fdisk command
c. Enter 3 at the cursor to delete the fdisk partition. In the same way as previously described, delete all fdisk partitions. The output is shown in Figure3.
Figure 3 Deleting fdisk partitions
d. Enter 5 at the cursor to exit fdisk and update disk settings. The output is shown in Figure4.
Figure 4 Exiting fdisk
4. Use the format tool to create disk partition information about the newly mapped LUNs.
Use the host LUN IDs of the newly mapped LUNs in this step. Perform the following steps:
a. Run the format command, and enter 2 at the cursor. The output is shown in Figure5.
Figure 5 Selecting disks
b. Enter fdisk at the cursor. The output is shown in Figure6.
Figure 6 fdisk command
c. Enter 1 at the cursor to create the fdisk partition. It is recommended that only one fdisk partition be created though more can be created. The output is shown in Figure7.
Figure 7 Creating a fdisk partition
d. Enter 5 at the cursor to exit fdisk and update disk settings. The output is shown in Figure8.
Figure 8 Exiting fdisk
e. Enter verify at the cursor to view partition information and verify that the capacities are the same as the actual values. The output is shown in Figure9.
Figure 9 Viewing partition information
The capacities appeared to be different from actual values as long as the following conditions were met:
The root cause is that the Solaris10U9ForX86 operating system has a defect.
Solaris10U9ForX86 considers disk information such as capacities to be permanent once the disk is created. If the capacity appear to be different from the actual value, Solaris10U9ForX86 may fail to read/write disk data properly. Therefore, do not unnecessarily change LUN mappings. Meanwhile, use host LUN IDs that have never been used when mapping new LUNs.
When mapping a new LUN, consider the following three situations:
1. If the newly mapped LUN is a LUN on which no FDISK partition is created, and its host LUN ID has been used by other mapped LUNs, its capacity appears to be different from the actual value.
2. If the host LUN ID of the newly mapped LUN has not been used by other mapped LUNs, even if no FDISK partition is created on the LUN, there is no capacity inconsistency issue.
3. If any FDISK partitions are created on the LUN, there is no capacity inconsistency issue.
When creating FDISK partitions on a disk, Solaris10U9ForX86 stores its capacity information in its disk tag, and then writes the capacity information to the first sector. Solaris10U9ForX86 considers the disk capacity to be permanent once the disk is created. The following explains how Solaris10U9ForX86 identifies a LUN:
1. Solaris10U9ForX86 cannot properly obtain the capacity information from the first sector if no FDISK partition is created on the newly mapped LUN.
2. If the newly mapped LUN has FDISK partitions, Solaris10U9ForX86 read the capacity information from the first sector of the disk and update the disk information in system cache. In this case, the capacity appeared is the same as the actual value.