portal.nutanix.com
Open in
urlscan Pro
84.53.164.187
Public Scan
Submitted URL: https://portal.nutanix.com/kb/9845
Effective URL: https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000br0aCAA
Submission: On June 28 via api from IN — Scanned from DE
Effective URL: https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000br0aCAA
Submission: On June 28 via api from IN — Scanned from DE
Form analysis
0 forms found in the DOMText Content
info alert Currently viewing public documentation. Please login to access the full list of documentation. SUPPORT & INSIGHTS 0 Guest * Home * * Documentation * Software Documentation * EOL Information * Hardware Replacement Documentation * Hardware Compatibility Lists * Knowledge Base * Solutions Documentation * Nutanix Validated Design New * Compatibility and Interoperability Matrix * Support Resources * Downloads * Security * Security Contact and Procedures * Product Signing (GPG) Keys Home Knowledge Base NCC Print to PDF Try Now ALERT - A160104 - FILE_SERVER_CVM_CONFIG_CHECK KB ARTICLE PAGE ALERT - A160104 - FILE_SERVER_CVM_CONFIG_CHECK Article #000009845 Last modified onApr 17th 2024 SUMMARY: The NCC health check "file_server_cvm_config_check" verifies whether AOS & Files Cluster Internal Network are on different subnets. VERSIONS AFFECTED: NCC 4.x, All Nutanix Files Versions, ALL AOS Version NCC Nutanix Files DESCRIPTION: Alert Overview The NCC health check file_server_cvm_config_check verifies if AOS & Files Cluster Internal (storage) networks are on different subnets. Sample Alert Block Serial Number: 23SMXXXXXXXX alert_time: Tue Apr 2024 15:05:10 GMT-0800 (PST) alert_type: File Server alert_msg: File Server {file_server_name} internal network {nvm_subnet} is not on the same subnet as Controller VM {cvm_ip} subnet {cvm_subnet} cluster_id: xxxxx alert_body: No Alert Body Available Output messaging Check ID160104Description"File Server internal network and Controller VM are in different Subnet"Causes File Server internal network and the Controller VM are in different subnets. This may cause performance issues.ResolutionsRe-IP the file server's internal network is on the same subnet as the Controller VM. Contact Nutanix support if the issue still persists or assistance needed.ImpactFile Server performance might have degraded.Alert TitleFile Server internal network is not on the same subnet as Controller VM.Alert MessageFile Server {file_server_name} internal network {nvm_subnet} is not on the same subnet as Controller VM {cvm_ip} subnet {cvm_subnet} SOLUTION: Troubleshooting Confirm the subnet which the Files internal interface has been selected to use and also check the subnet in use by the CVMs. For Files, if you navigate to the File Server page in Prism Element, you can select the affected Files cluster and click view IPs under "Storage Network" to the bottom left of the page. You can find the IPs of the CVMs by browsing to settings, network configuration, then selecting the Management LAN under Internal Interfaces. Resolving the Issue When the File Server internal network and the Controller VM's are in different subnets, it may cause performance issues due to slow IO (iSCSI traffic) which is dependent on communication between File Server VM internal/Storage network and CVM. The core reasoning is explained in the Nutanix Files Solution Guide: Nutanix recommends placing the FSVM storage interface on the same network VLAN as the Nutanix CVM management interface (eth0 of the CVM). Using the same VLAN helps ensure maximum performance for ISCSI sessions. The Procedure to update a File Server Network is documented in the Nutanix Files Guide. For your reference, the Nutanix Files Guide section to update your network is available here. If you need more help, consider engaging Nutanix Support. Running the NCC Check You can run the following checks as part of the full NCC Health Checks: nutanix@CVM$ ncc health_checks run_all Or you can run the check separately: nutanix@CVM$ ncc health_checks fileserver_checks fileserver_cvm_checks file_server_cvm_config_check You can also run the checks from the Prism web console Health page: select Actions > Run Checks. Select All checks and click Run. * This check is scheduled to run every 24 hours, by default. * This check will generate a WARN alert.