Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Article Number: 000124926

PowerStore Alerts: MTU mismatch, MTU state, VLAN MTU state, DNS & NTP alerts

Summary: This article discusses MTU mismatch, MTU state, VLAN MTU state, DNS & NTP alerts.

This article may have been automatically translated. If you have any feedback regarding its quality, please let us know using the form at the bottom of this page.

Article Content

Symptoms

When Dell PowerStore encounters a problem, an error alert is generated to help identify the issue. This article explains the different possible causes and the relevant solutions for these error alerts. If your problem is not resolved despite the solution that is provided, check the technical support contact options.
SLN322737_en_US__1icon Note: Cannot find the information that you need? Let us know using the feedback form at the bottom of this article.

Cause

Cause is mentioned in Resolution section under respective alerts.

Resolution

Alert ID ONV_ICC_ICM_MTU_ISSUES_MISMATCH_DETECTED
ONV_ICC_ICD_MTU_ISSUES_MISMATCH_DETECTED
ONV_ICC_MGMT_MTU_ISSUES_MISMATCH_DETECTED
ONV_ICC_STORAGE_MTU_ISSUES_MISMATCH_DETECTED
ONV_ICC_VMOTION_MTU_ISSUES_MISMATCH_DETECTED
Alert Text MTU size issues detected while performing path MTU discovery of the following <network name> network addresses: (from <IP address> : <IP address>), … .
Error Code (0x01803003)
(0x01803203)
(0x01802C03)
(0x01802E03)
(0x01803403)
Resolution Cause
These alerts are shown when the Ongoing Network Validation mechanism of the PowerStore (ONV) has detected two facts at the same time:
  • The small ping packets (ICMP or ICMPv6 echo requests/responses) are going between certain IP addresses set on the PowerStore nodes
  • The ping packets of maximum size allowed by this network MTU settings do not go between these IP addresses
    It means that somewhere in the Ethernet infrastructure, the MTU size is set less than required by the PowerStore network named in the alert message. Usually some switch port is set to an insufficient MTU.
    Note that the path MTU check is performed only if the standard ping connectivity check has been successful. If for a certain address pair the system has shown this alert:
    The following <network name> network addresses are not reachable via ICMP from node network interfaces: (from <IP address> : <IP address>), … .
    then the MTU discovery would not be attempted for this pair.
     
Solution
Check port MTU configuration of the Ethernet switches which connect the PowerStore cluster together, starting with the ToR switches. Ensure that the path MTU for network named in the message is no less than the MTU set for this network at the PowerStore cluster.
 

 

Alert ID ONV_PORT_TOR_MTU_STATE_INVALID
ONV_PORT_CDP_MTU_STATE_INVALID
ONV_PORT_LLDP_MTU_STATE_INVALID
ONV_PORT_CROSS_PROTOCOL_MTU_STATE_INCONSISTENT
ONV_APPLIANCE_MGMT_PORTS_MTU_STATE_INVALID
ONV_APPLIANCE_DATA_PORTS_MTU_STATE_INVALID
ONV_CLUSTER_MGMT_PORTS_MTU_STATE_INVALID
ONV_CLUSTER_DATA_PORTS_MTU_STATE_INVALID
Alert Text
  • The %(local_port) is connected to port %(physical_switch_port_id) of switch %(physical_switch_id) with an MTU %(current_mtu) that is too small according to switch information received via SSH / SNMP. Minimally required MTU is %(required_mtu).
  • The %(local_port) is connected to port %(physical_switch_port_id) of switch %(physical_switch_id) with an MTU %(current_mtu) that is too small according to information received via Cisco Discovery Protocol (CDP). Minimally required MTU is %(required_mtu).
  • The %(local_port) is connected to port %(physical_switch_port_id) of switch %(physical_switch_id) with an MTU %(current_mtu) that is too small information received via Link Layer Discovery Protocol (LLDP). Minimally required MTU is %(required_mtu).
  • Cross-protocol MTU information is not consistent for %(local_port).
  • MTU mismatch detected between management switch ports: %(connection_scheme).
  • MTU mismatch detected between data switch ports: %(connection_scheme).
  • Cluster-wide MTU mismatch detected between management switch ports: %(connection_scheme).
  • Cluster-wide MTU mismatch detected between data switch ports: %(connection_scheme).
Error Code (0x01800E02)
(0x01800F02)
(0x01801002)
(0x01801102)
(0x01801302)
(0x01801202‬)
(0x01801502)
(0x01801402)
Resolution Cause
PowerStore obtains the ToR switches ports MTU information by the number of ways. In the order of precedence, they are:
  • ToR management access, if the valid ToR switch access credentials are provided by the user
  • CDP protocol, if supported by ToR switch
  • LLDP protocol, if supported by ToR switch

    The MTU settings of all the PowerStore-facing ports of the ToR Ethernet switches should meet certain requirements.
  • The management ports of the PowerStore T models should be connected to a ToR Ethernet switch ports with MTU not less than 1500 or the PowerStore management port MTU setting value, whichever is bigger. The ToR switch in question is the "out-of-band" (OOB) management one.
  • All the management ports of an appliance should be connected to the ToR Ethernet switch ports with the same MTU value.
  • All the management ports of the appliances of the whole cluster should be connected to the ToR Ethernet switch ports with the same MTU value.
  • The data ports of the PowerStore T models and all the ports of the PowerStore X models should be connected to the ToR Ethernet switch ports with MTU not less than the cluster-wide "Fabric MTU" setting value.
  • All the data ports of an appliance should be connected to the ToR Ethernet switch ports with the same MTU value.
  • All the data ports of the appliances of the whole cluster should be connected to the ToR Ethernet switch ports with the same MTU value.
    Management port in this context is the 1 Gbit Ethernet port on the PowerStore main board of the PowerStore T models. On the PowerStore X models this port is reserved for the future use and the MTU validation checks are not performed for it. All ports of the PowerStore X model are considered data ports, and no management port related alerts are shown on the PowerStore X models.

    A.  When the MTU value of a PowerStore-facing port of the ToR switch (an uplink) is lower than the certain limits, the system shows an alert: 
    The %(local_port) is connected to port %(physical_switch_port_id) of switch %(physical_switch_id) with an MTU %(current_mtu) that is too small according to switch information received via SSH / SNMP. Minimally required MTU is %(required_mtu).
    For each port with an incorrect uplink MTU value, a separate alert is shown.

    B.  When the MTU values get for an uplink by different methods are not the same, the system shows an alert like this:
    Cross-protocol MTU information is not consistent for %(local_port).
    For each port with different methods returning different uplink MTU, a separate alert is shown.
    Due to the platform limitations, on the PowerStore X models the only available method to get the uplink MTU is the ToR switch management access. As the result, the following checks are not performed on PowerStore X models:
  • Check of MTU values got by CDP
  • Check of MTU values got by LLDP
  • Cross-protocol consistency check
C.  When the MTU values of the different uplinks is not the same for all the data ports or management ports, the system shows an alert like these:
MTU mismatch detected between management/data switch ports: %(connection_scheme).
Cluster-wide MTU mismatch detected between management/data switch ports: %(connection_scheme).
Data ports are being checked first and the management ones next. If the uplink MTU inconsistency is found for the data ports, the management port consistency check is not performed.
In the text messages of these alerts, all the uplinks of the corresponding type and scope are listed. The reason is that the PowerStore has no means to detect which of the different uplink MTU values should be considered the reference one. As the result, for example, if a single data uplink of the multi-appliance cluster gets the different MTU, the "Cluster-wide MTU mismatch detected on Ethernet switch ports…" alert message would list all the cluster data uplinks.

Solution
  • Change the port MTU settings of the ToR Ethernet switches to meet the PowerStore requirements.
  • Ensure that MTU information is consistent across the protocols.
  • Ensure that the MTU is configured consistently on the displayed management switch ports.
  • Ensure that the MTU is configured consistently on the displayed data switch ports.
 

 

Alert ID ONV_ICM_NETWORK_VLAN_INTERFACE_MTU_STATE_INVALID
ONV_ICD_NETWORK_VLAN_INTERFACE_MTU_STATE_INVALID
ONV_MGMT_NETWORK_VLAN_INTERFACE_MTU_STATE_INVALID
ONV_STORAGE_NETWORK_VLAN_INTERFACE_MTU_STATE_INVALID
ONV_VMOTION_NETWORK_VLAN_INTERFACE_MTU_STATE_INVALID
Alert Text
  • VLAN interface on the data switch %(physical_switch_id) for the intra-cluster management (ICM) with VLAN ID %(vlan_id) has an MTU %(current_mtu) that is too small.
  • VLAN interface on the data switch %(physical_switch_id) for the intra-cluster data (ICD) with VLAN ID %(vlan_id) has an MTU %(current_mtu) that is too small.
  • VLAN interface on the management switch %(physical_switch_id) for the management network with VLAN ID %(vlan_id) has an MTU %(current_mtu) that is too small.
  • VLAN interface on the data switch %(physical_switch_id) for the storage network with VLAN ID %(vlan_id) has an MTU %(current_mtu) that is too small.
  • VLAN interface on the data switch %(physical_switch_id) for the vMotion network with VLAN ID %(vlan_id) has an MTU %(current_mtu) that is too small.
Error Code (0x01801702)
(0x01801802)
(0x01801602)
(0x01801902)
(0x01801a02)
System Impact Inconsistent MTU settings on intra-cluster management VLAN interfaces can lead to loss of internal connectivity between nodes.
Inconsistent MTU settings on intra-cluster data network VLAN interfaces can affect internal volume migrations.
Inconsistent MTU settings across the network can lead to connectivity issues.
Inconsistent MTU settings on storage network VLAN interfaces can affect host connectivity.
Inconsistent MTU settings on vMotion network VLAN interfaces can affect virtual volume balancing.
Resolution Cause
These alerts are shown when the PowerStore detects that the VLAN interface configured on the ToR Ethernet switch for one of the PowerStore network VLANs has the insufficient MTU value.
Usually to enable a VLAN on the Ethernet switch you need to create a pseudo-interface for it. This interface can have its own MTU settings different from the physical port ones. If the PowerStore has the ToR switch administrative access credentials configured, it reads the VLAN interfaces configuration from the switch, matches it by the VLAN ID with the PowerStore networks and compares the MTU size of the VLAN pseudo-interface with the requested network MTU size.

Solution
Check the ToR Ethernet switch configuration and increase the MTU size on the corresponding VLAN interface.
The repair flow messages for these alerts gives user the useful hints where to look and what should be the minimal MTU value.
Increase the MTU on VLAN interface <physical_switch_vlan_iface_id> to at least <required_mtu>.
For example: Increase the MTU on VLAN interface <PowerStoreMgmt100> to at least 1500.
 

 

Alert ID ONV_DNS_STATUS_FULLY_UNAVAILABLE
ONV_NTP_STATUS_FULLY_UNAVAILABLE
Alert Text
  • All configured DNS servers are unavailable.
  • All configured NTP servers are unavailable.
Error Code (0x01800103)
(0x01800203)
System Impact Depending on the configuration, any services that use host names could be affected.
Replication sessions may be affected.
Resolution Cause
It could be a network connectivity problem, a configuration error or an actual multiple servers’ failure. If the PowerStore appliance loses its management network connection, it would lose the DNS and NTP connectivity too.
Note that if the NTP servers are set up using their domain names, the DNS failure would result in NTP connectivity failure.
PowerStore does periodically check that the configured DNS and NTP servers are accessible and do correctly respond to DNS and NTP protocol requests.
When all the configured DNS or NTP servers stop responding, the system shows the corresponding alert: 
  • All configured DNS servers are unavailable.
  • All configured NTP servers are unavailable.
    The name resolving would stop immediately as the system loses the connectivity to all the DNS servers. At the same time, the NTP service would maintain the correct system time long after the connectivity to the NTP servers is lost.
     
Solution
  • Ensure that the DNS server IP addresses are correct and reachable via the management network.
  • Ensure that the NTP server IP addresses are correct and reachable via the management network.

Article Properties

Affected Product

PowerStore

Last Published Date

07 Apr 2021

Version

3

Article Type

Solution

Back to Top