No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

CX210 Switch Module V100R001 User Guide 14

This document describes the CX210 multi-plane switch module of the E9000 server in terms of its features, installation, removal, and configuration.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring Functions and Features of the MX210

Configuring Functions and Features of the MX210

NOTE:

The MX210 uses the universal FOS software platform provided by Brocade.

Cascading

An MX210 switch module can be cascaded with another MX210 switch module or with a Brocade FC switch. The Full Fabric license is required for cascading.

Context
  • Do not connect an MX210 switch module to the upper-layer Brocade FC switch before cascading the MX210 switch module with other MX210 switch modules.
  • Before cascading FC switches, back up their data.
Procedure
  1. Apply for the Full Fabric license required for cascading.

    To apply for a license, contact Huawei technical support.

  2. Log in to the FC switches to be cascaded.
  3. Import the license to the FC switches.

    For details, see Importing a License Using Commands.

  4. Set different domain IDs for the FC switches.

    For details, see Setting a Domain ID.

  5. Run the reboot command to restart the FC switches for the license to take effect.
  6. Run the fabricshow command to verify cascading.
  7. Configure zones on the FC switches based on site networking.

    For details, see Configuring Zones Using Commands.

Link Aggregation

Link aggregation allows you to create link aggregation groups between adjacent MX210 switch modules. Each link aggregation group contains a maximum of eight FC ports. The aggregated port rate can reach 64 Gbit/s (128 Gbit/s, duplex) to achieve optimal bandwidth usage and load balancing. The ISL Trunking license are required for link aggregation.

Context

After licenses are added, MX210 switch modules enable the ISL Trunking function to set link aggregation for bandwidth expansion.

Procedure
  1. Apply for the licenses required for link aggregation.

    NOTE:

    The ISL Trunking license are required for link aggregation.

    To apply for a license, contact Huawei technical support.

  2. Log in to the MX210.

    For details, see Logging In to the MX210 over a Serial Port and Logging In to the MX210 Using SSH.

  3. Run the licenseadd command to add the obtained ISL Trunking license.
  4. Run the reboot command to restart the MX210 switch module for the licenses to take effect.

Fabric OS Native and AG Modes

The MX210 supports the native and access gateway (AG) modes and can be dynamically switched between the two modes.

Context

The AG mode allows the MX210 to connect to the third-party fabric network. By default, the MX210 is in fabric OS native mode. Figure 4-39 shows the differences between the two modes.

Figure 4-39 Differences between the two modes

To enable the AG mode, perform the following steps:

Procedure
  1. Log in to the MX210.

    For details, see Logging In to the MX210 over a Serial Port and Logging In to the MX210 Using SSH.

  2. Run the switchdisable command to disable the MX210.
  3. Run the ag --modeenable command to enable the AG mode.

    After enabling the AG mode, you can use the default F_Port-to-N_Port mapping, or change the mapping on the CLI or using the web tools after changing the IP address. The AG mode simplifies the switch module deployment by using N_Port ID virtualization (NPIV). The AG mode facilitates connection of FC switch modules.

    NOTE:
    • The AG cannot be directly connected to the storage array. It must be connected to the FC switch.
    • If the following command output is displayed after you run ag --modeenable, run the authutil --policy -sw off command and then the ag --modeenable command to start the AG mode.

      Sometimes change Qilin to AG mode, it show "ERROR: AG mode not allowed while AUTHENTICATION policies are enabled. Please disable the AUTHENTICATION policies using the CLI authutil --policy -sw(switch)/-dev(device)"

    Table 4-6 lists the default AG settings.

    Table 4-6 Default AG settings

    Item

    Setting

    Automatic switchover

    Enabled on all N_Port ports.

    Automatic rollback

    Enabled on all N_Port ports.

    APC policy

    Disabled.

    Port group policy

    Enabled.

    ADS policy

    Disabled.

    The fabric OS features take effect only when the MX210 switch module is in fabric OS native mode. If the MX210 is in AG mode, the external port mode can be N_Port, and the internal port mode can be F_Port. Table 4-7 lists the AG mapping.

    Table 4-7 AG mapping

    Port Number (F_Port)

    Server Blade Slot

    Port Number (N_Port)

    9

    1

    1

    17

    9

    10

    2

    2

    18

    10

    11

    3

    3

    19

    11

    12

    4

    4

    20

    12

    13

    5

    5

    21

    13

    14

    6

    6

    22

    14

    15

    7

    7

    23

    15

    16

    8

    8

    0

    16

  4. Run the switchenable command to enable the MX210.

    NOTE:

    For the old MX210, the default port mapping is shown in Table 4-7. For the new MX210, ports 5 to 8 on the panel are controlled by a license and are unavailable during the initial configuration. Internal ports (F_Port) 13, 14, 15, 16, 21, 22, 23, and 0 automatically map to the online ports among ports 1 to 4 on the panel. If the port on demand (POD) license is added and ports 5 to 8 are activated, the default port mapping is shown in Table 4-7.

Port Auto-Negotiation

The external FC ports of the MX210 support the rates of 2Gbit/s, 4Gbit/s, 8Gbit/s, and auto-negotiation. The actual port rates can be automatically adjusted based on the ports and peer device. The internal FC ports support only 8 Gbit/s.

The FC ports are internal ports or CUs used for querying command results. You can run the switchshow command to query FC port information.

Configuring the Port Mapping

This topic describes how to view and configure mapping between internal and external ports in AG mode.

Context

This task guides the software commissioning engineer to configure port mapping in AG mode for the MX210.

Procedure
  1. Log in to the MX210.

    For details, see Logging In to the MX210 over a Serial Port and Logging In to the MX210 Using SSH.

  2. Run the switchdisable command to disable the MX210.
  3. Run the ag --modeenable command to enable the AG mode.

    The MX210 restarts and then works in AG mode.

    If the message "ERROR: AG mode not allowed while AUTHENTICATION policies are enabled. Please disable the AUTHENTICATION policies using the CLI authutil --policy -sw(switch)/-dev(device)" is displayed, the authentication policy is enabled, so the AG mode cannot be enabled. Disable the authentication policy before enabling the AG mode.

    To disable the authentication policy, run the following command:

    FC_SW:admin> authutil –policy –sw off

    FC_SW:admin> authutil –policy –dev off

  4. Run the ag --mapshow command. The command output includes the homing port group (PG) and current active (registered and connected) ports on the MX210, as shown in Figure 4-40.

    NOTE:

    You can group a number of N_Ports (and its mapped F_Ports) together to connect to multiple independent fabrics or to create performance optimized ports. To group a number of ports, you must create a new port group and assign desired N_Ports to it. The N_Port grouping option is enabled by default, and all N_Ports are members of the default port group 0 (pg0).

    Figure 4-40 Homing PG and current active (registered and connected) ports information

  5. Modify the mapping between internal and external ports on the MX210.

    Each MX210 provides four FC ports to connect to external FC switches. To ensure load balancing between the four ports, manually set the mapping between internal and external ports. Four internal ports map to one external active port, and other ports server as standby ports. Figure 4-41 describes the port mapping.

    Figure 4-41 Mapping between internal and external ports on the MX210
    1. Delete the default port mapping.
      FC_SW: admin>ag --mapdel 1 "9;17"  
      FC_SW: admin>ag --mapdel 2 "10;18"  
      FC_SW: admin>ag --mapdel 3 "11;19"  
      FC_SW: admin>ag --mapdel 4 "12;20"  
      FC_SW: admin>ag --mapdel 5 "13;21"  
      FC_SW: admin>ag --mapdel 6 "14;22"  
      FC_SW: admin>ag --mapdel 7 "15;23"  
      FC_SW: admin>ag --mapdel 8 "16;0"     
    2. Set the new port mapping.
      FC_SW: admin>ag --mapadd 1 "9;10;17;18"  
      FC_SW: admin>ag --mapadd 2 "11;12;19;20"  
      FC_SW: admin>ag --mapadd 3 "13;14;21;22"  
      FC_SW: admin>ag --mapadd 4 "15;16;23;0"     

Enabling or Disabling a Port Using Commands

To enable or disable a port on the MX210 CLI, perform the following steps:

Procedure
  1. Log in to the MX210.

    For details, see Logging In to the MX210 over a Serial Port and Logging In to the MX210 Using SSH.

  2. Run the portenable command to enable a port or run the portdisable command to disable a port.

    FC_SW:admin>portenable 4 
    FC_SW:admin>portdisable 4     

  3. Run the switchshow command to check whether the port setting is successful.

    • If the value of Proto for a port is FC Disabled, the port is disabled.
    • If the value of Proto for a port is another value, the port is enabled.

Enabling or Disabling a Port Using Web Tools

To enable or disable a port using the web tools, perform the following steps:

Procedure
  1. Log in to the MX210.

    For details, see Logging In to the MX210 Using Web Tools.

  2. Click the Port Admin tab, as shown in Figure 4-42.

    Figure 4-42 Port Admin window

  3. In the navigation tree, choose the target port.
  4. Enable or disable the port.

    • If you need to enable the port, select Enable from the Port drop-down list in the right pane, and click Yes in the confirmation box that is displayed.
    • If you need to disable the port, select Disable from the Port drop-down list in the right pane, and click Yes in the confirmation box that is displayed.

Enabling the Access Gateway Mode Using Web Tools

Some fabric information, such as zone or security database information, will be deleted if you enable the access gateway (AG) mode. Back up these configurations before enabling the AG mode if you need to restore them.

Context

For details about how to back up configuration files, see Backing up the MX210 Configuration File by Using Web Tools.

NOTE:

The AG mode cannot be enabled if the manager server is enabled. You can run the MsplmgmtDeactivate command to disable Management Server.

Procedure
  1. Log in to the MX210.

    For details, see Logging In to the MX210 Using Web Tools.

  2. On the menu bar of the Web Tools, choose Configure > Switch Admin.

    The Switch Administration dialog box is displayed, as shown in Figure 4-43.

    Figure 4-43 Switch Administration dialog box

  3. Click the Switch tab. In Switch Status, select Disable.

    You must disable the MX210 before enabling the AG mode.

  4. In Access Gateway Mode, click Enable.
  5. Click Apply. In the displayed dialog box, click Yes to restart the MX210 for the AG mode to take effect.

Configuring Fabric Vision

Fabric Vision is used for advanced monitoring, management, and diagnosis of the CX210 to maximize infrastructure uptime. Fabric Vision includes two major functions: MAPS and Flow Vision.

Importing a Fabric Vision License
Context

Before the Fabric Vision function, import a Fabric Vision license to the switch module first. For details about how to apply for and import a license, see Applying for a License and Importing a License Using Commands respectively.

Configuring MAPS

MAPS (Monitoring and Alerting Policy Suite) is a set of components for monitoring and management. Pre-installed rules and automation enable simple policy-based monitoring and warning.

Using Predefined Policies

If a switch module fails and needs to be replaced with a new one, you can transfer all licenses on the failed switch module to the new one to reuse the licenses.

Context

The system predefines the following three default policies: dflt_aggressive_policy, dflt_moderate_policy, and dflt_conservation_policy. Each predefined policy contains over 190 rules.

Switches of version FOS7.4.0 and later versions provide the basic policy dflt_base_policy by default. This policy does not require the Fabric Vision license.

Procedure
  1. Log in to the MX210.

    For details, see Logging In to the MX210 Using SSH.

  2. Run the following command to query the available policy types. See Figure 4-44.

    mapspolicy –show -summary

    Figure 4-44 Policy types

  3. Run the following command to activate the selected policy. See Figure 4-45.

    mapsPolicy --enable <policyName>

    Figure 4-45 Activating a Policy

  4. Change the global MAPS actions as needed. The Fence action is not recommended. See Figure 4-46.

    Figure 4-46 Modifying the global actions

    • It is recommended that you use one of the three default policies provided by Brocade. They are based on Brocade's years of experience.
    • Unless necessary, do not enable Fence.

Using Customized Policies
Context

If the default policies do not meet actual needs, you can create new policies.

Procedure
  1. Log in to the MX210.

    For details, see Logging In to the MX210 Using SSH.

  2. Run the following command to query the available groups. See Figure 4-47.

    logicalgroup --show

    Figure 4-47 Querying available groups

  3. Type mapsrule and press Enter. View the values of monitor in the command output, as shown in Figure 4-48.

    Figure 4-48 Viewing the values of monitor

  4. Type mapsrule and press Enter. View the values of timebase, op, and action in the command output, as shown in Figure 4-49.

    Figure 4-49 Viewing the values of timebase, op, and action

  5. Run the following command to create a rule:

    mapsrule --create

    Command format:

    mapsrule --create -group <group name> -monitor <ms name> -timebase <day:hour:min> -op <l:le:g:ge:eq> -value <value> > -action <action list>

    Table 4-8 describes the parameters.

    Table 4-8 Meaning

    Parameter

    Description

    group

    Specifies the group name. To query the groups that can be monitored, run the logicalgroup –show command.

    Monitor

    Specifies the elements to be monitored. The values include Port health, FRU health, FCIP health, and so on.

    timebase

    Specifies the monitoring frequency. The values are min, hour, day, and none.

    op

    Specifies the relational operation. The values are l (less), le (less or equal), g (greater), ge (greater or equal), and eq (equal).

    value

    Specifies the threshold. Values are as follows:

    • Number: 1 to 9999
    • Percentage: 1 to 100
    • FRU states: ON, OFF, IN, OUT, or FAULTY
    • Temperature monitoring: IN_RANGE, OUT_OF_RANGE

    action

    Specifies the action. Values include: raslog, snmp, and fence.

    • Example 1: Create a rule named check_crc. This rule monitors the number of CRC errors every hour on all ports and generates a RASlog if the number of CRC errors is greater than 10. The command for creating the rule is as follows:

      mapsrule --create check_crc -monitor crc -group ALL_PORTS -timebase hour -op g -value 10 -action raslog

    • Example 2: Create a rule named check_fan. This rule monitors the fan status and generates a RASlog and SNMP trap if the fan is faulty. The command for creating the rule is as follows:

      mapsrule --create check_fan -monitor FAN_STATE -group ALL_FAN -op eq -value FAULTY -action raslog,snmp

    • Example 3: Create a rule named check_memory. This rule monitors the memory usage and generates a RASlog if the memory usage is greater than 15%. The command for creating the rule is as follows:

      mapsrule --create check_memory -monitor MEMORY_USAGE -group CHASSIS -op g -value 15 -action raslog

Using the Dashboard

The dashboard shows the rules that affect the CX210 health status.

Context

The system predefines the following three default policies:

  • dflt_aggressive_policy
  • dflt_moderate_policy
  • dflt_conservation_policy

dflt_aggressive_policy contains strict thresholds. dflt_conservation_policy contains lenient thresholds. dflt_moderate_policy is between the aggressive and conservative policies and is recommended. Each predefined policy contains over 190 rules.

Switches of version FOS7.4.0 and later versions provide the basic policy dflt_base_policy by default. This policy does not require the Fabric Vision license.

Procedure
  1. Log in to the MX210.

    For details, see Logging In to the MX210 Using SSH.

  2. Run the following command to view the dashboard. As shown in Figure 4-50, the dashboard includes Active policy, Configured Notifications, Current Switch Policy Status, Summary Report, and so on.

    mapsdb --show

    Figure 4-50 Viewing the dashboard

Configuring the Flow Vision Function

Flow Vision includes the Flow Monitor function and can perform statistics and analysis of specific flows and frame types.

Using Customized Policies
Context

The Flow Monitor function shows the storage network status. It monitors the network traffic without disturbing the network and obtains statistics of specific flows or frame types.

Procedure
  1. Log in to the MX210.

    For details, see Logging In to the MX210 Using SSH.

  2. Run the following command to create a new flow:

    Flow --create

    Command format:

    flow --create <flowname> -feature <list> <Port options> <Frame options> <Config options>

    Table 4-9 describes the parameters.

    Table 4-9 Command parameters

    Parameter

    Description

    Flowname

    Name of the customized flow

    List

    The value is usually monitor.

    Port options. Format: D,I (Domain,Index) or [slot/]port

    • -ingrport: ingress port
    • -egrport: egress port
    • -mirrorport: mirror port

    Frame options

    • -srcdev <devID>: source address (in PID or PWWN format)
    • -dstdev <devID>: target address (in PID or PWWN format)
    • -frametype <ftyp>: SCSI, SCSIRead, SCSIWrite, and so on
    • –lun: LUN ID

    Config options

    • -bidir: monitors bidirectional traffic
    • -noactivate: creates a flow but does not activate it
    • -noconfig: creates a flow, which will be lost after a restart
    • Example 1: Create a flow to monitor the traffic from the source device (0x020300 to the destination device (0x010200) as follows:

      flow –create myflow1 –feature monitor –ingrport 1/2 –srcdev 0x020300 –dstdev 0x010200

    • Example 2: Create a flow to monitor the traffic of port 5 as follows:

      flow --create flowLearn -feature monitor -ingrport 3/5 -srcdev "*" -dstdev "*"

    • Example 3: Create a flow to monitor the bidirectional traffic from the source address to the destination address as follows:

      flow --create endtoendflow -feature monitor -ingrport 2/5 -srcdev 010500 -dstdev 040900 -bidir

  3. Run the following command to view traffic statistics:

    flow –show

  4. (Optional) Run the following command to import a flow to MAPS, so that the mapsrule command is used to monitor the flow as a group:

    mapsConfig --import <flowName> [-force]

    Example 1: Import the flow named myflow1 to MAPS as follows:

    mapsconfig –import myflow1

Configuring Extended Fabric

Certain functions of the MX210 can be used only when specific licenses are available. For example, device cascading requires a Full Fabric license, and port aggregation requires a Full Fabric license and ISL Trunking license.

If an interswitch link (ISL) of over 10 km is deployed and uses E-Ports of switches, you must configure the switch ports so that they support long links. In a long-distance fabric, buffer credit management is important to the fabric transmission performance.

Configuring an ISL
Context

Before deploying a long-distance fabric, import an Extended Fabric license and configure switch ports so that they support links of over 10 km.

Long-distance links increase the latency and affect the bandwidth, so the port buffer credits need to be modified to minimize the effect. The number of buffer credits represent the ability to receive additional frames. If the receiving device does not send credits to the sending device, the sending device does not send frames.

The total available buffer credits of each port group are limited. Therefore, configuring buffer credits of an ISL may affect the performance of the other ports in the port group.

The Extended Fabric license cannot be used in AG mode.

Procedure
  1. Log in to the MX210.

    For details, see Logging In to the MX210 Using SSH.

  2. Run the following command to disable the switch.

    switchdisable

  3. Run the following command to configure ports so that they support long-distance links.

    portcfglongdistance

    For example, run the following command to configure port 2 to support a 15 km link.

    portcfglongdistance 2 LS 1 -distance 15

  4. Run the following command to enable the switch.

    switchenable

Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000053379

Views: 24634

Downloads: 625

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next