H3C SecPath NSQM1ISPAXA1&NSQM1ISPAXB1
Intelligent Service Platform Modules Installation Guide

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Contents

Overview·· 1

Compatibility of the modules with firewalls· 1

Hardware information· 2

NSQM1ISPAXA1 intelligent service platform module· 2

NSQM1ISPAXB1 intelligent service platform module· 3

Mapping relations between ports on the modules and network cards· 3

Internal inline port interconnecting the module and device· 4

Technical specifications· 4

Installing the module· 5

Restrictions and guidelines· 5

Installing the NSQM1ISPAXA1 intelligent service platform module· 5

Installing the NSQM1ISPAXB1 intelligent service platform module· 6

Remove the module· 7

Restrictions and guidelines· 7

Removing an NSQM1ISPAXA1 intelligent service platform module· 7

Removing an NSQM1ISPAXB1 intelligent service platform module· 8

Verifying the installation· 8

Starting the module for the first time· 8

Setting up the configuration environment 8

Connecting the console cable· 9

Console cable· 9

Connecting the console cable· 9

Setting terminal parameters· 9

Configuration for the first access· 10

Configuring the IP address and gateway for the intelligent service platform·· 10

Configuring the SSH service· 12

Appendix A  Ports and LEDs· 1

Console port 1

GE copper port 1

GE fiber port 1

USB port 2

Port LEDs· 2

Appendix B  Basic Linux commands· 1

vi editor 1

Configuring a temporary IP address· 4

passwd command· 5

cd command· 6

cat command· 6

tar command· 6

cp command· 6

mkdir command· 7

Troubleshooting· 1

NIC failure· 1

Configuration terminal display problems· 1

 

Overview

H3C NSQM1ISPAXA1 and NSQM1ISPAXB1 intelligent service platform modules can be installed on the F1000 and F5000 firewall series. This document provides compatibility of the intelligent service platform modules with firewalls and information about how to install, remove, and configure the modules.

Compatibility of the modules with firewalls

The intelligent service platform modules are applicable to multiple firewalls. The following table describes the compatibility of the intelligent service platform modules with firewalls.

Table 1 Compatibility of the intelligent service platform modules with firewalls

Module model	Applicable firewall models	Applicable slots	Application software versions
NSQM1ISPAXA1	·     F1020, F1030, F1050, F1060, F1070, F1080 ·     F100-A-G2, F100-A-EI, F100-E-G2, F100-A-SI, F100-E-EI ·     F1020-GM, F1030-GM, F1070-GM, F1070-GM-L ·     F1000-AK130, F1000-AK135, F1000-AK140, F1000-AK145, F1000-AK150, F1000-AK155, F1000-AK160, F1000-AK165, F1000-AK170, F1000-AK175, F1000-AK1212, F1000-AK1222, F1000-AK1232, F1000-AK1312, F1000-AK1322, F1000-AK1332, F1000-AK180, F1000-AK185, F1000-AK711, F1000-GM-AK370, F1000-GM-AK370 ·     F1000-AI-20, F1000-AI-30, F1000-AI-50 ·     F1000-920-AI, F1000-930-AI, F1000-950-AI, F1000-960-AI, F1000-970-AI, F1000-980-AI, F1000-990-AI ·     F1000-E-VG, F1000-V70 ·     F1000-C-G2, F1000-C-EI, F1000-E-G2, F1000-S-G2, F1000-A-G2 ·     F100-A-G3, F100-E-G3, F100-A80-WiNet ·     F1000-C-HI, F1000-C-EI	Slot 1	R9360P19 or later
	·     F1090, F1000-AI-60, F1000-AI-90, F1000-AI-80, F1000-AI-70 ·     F1000-V90, F1000-V60, F1000-V50 ·     F1000-S-G3, F1000-A-G3, F1000-E-G3, F1000-C-G3 ·     F1000-E-G5, F1000-H-G5 ·     F1000-C8395 ·     F1000-AK1414, F1000-AK1424, F1000-AK1434, F1000-AK1514, F1000-AK1524, F1000-AK1534, F1000-AK1614 ·     F1000-AK1235, F1000-AK1242, F1000-AK1252, F1000-AK1262, F1000-AK1272, F1000-AK9160, F1000-AK9180 ·     F1000-AI-25, F1000-AI-35, F1000-AI-55, F1000-AI-75 ·     F100-E-G5, F1000-C-G5, F1000-C-G5-LI ·     F1000-9350-AI, F1000-9360-AI ·     F1000-740-HI, F1000-750-HI ·     F100-A91-WiNet ·     F1000-E-XI ·     F1000-T1000-E	Slot 1	R8660P18 or later
NSQM1ISPAXB1	·     F5030, F5060, F5080, F5030-6GW ·     F5000-M, F5000-A ·     F5000-AI-20, F5000-AI-40 ·     F5000-V30	Slot 1 and Slot 2	F9660 or later
	F5030-D, F5060-D, F5080-D	Slot 2/1 and Slot 2/2	F9660 or later
	F5000-AK515, F5000-AK525	Slot 1 and Slot 2	R9660P28 or later

 

Hardware information

NSQM1ISPAXA1 intelligent service platform module

Figure 1 NSQM1ISPAXA1 intelligent service platform module

(1) 10/100/1000BASE-T Ethernet copper port	(2) 1000BASE-X Ethernet fiber port
(3) USB port	(4) Console port (CONSOLE)
(5) Handle	(6) Power button
(7) 1000BASE-X Ethernet fiber port	(8) 10/100/1000BASE-T Ethernet copper port (management Ethernet port)

 

NSQM1ISPAXB1 intelligent service platform module

Figure 2 NSQM1ISPAXB1 intelligent service platform module

(1) USB port	(2) Console port (CONSOLE)
(3) 10/100/1000BASE-T Ethernet copper port	(4) 1000BASE-X Ethernet fiber port
(5) 1000BASE-X Ethernet fiber port	(6) Ejector lever
(7) 10/100/1000BASE-T Ethernet copper port (management Ethernet port)	(8) Power button

 

Mapping relations between ports on the modules and network cards

The following table describes the mapping relations between ports on the intelligent service platform modules and network cards.

Table 2 Mapping relations between ports on the NSQM1ISPAXA1 intelligent service platform modules and network cards

Network card name	Interface
enp11s0f0	Port 0 on the faceplate (10/100/1000BASE-T Ethernet copper port)
enp11s0f1	Port 1 on the faceplate (10/100/1000BASE-T Ethernet copper port)
enp11s0f2	Port 2 on the faceplate (1000BASE-X Ethernet fiber port)
enp11s0f3	Port 3 on the faceplate (1000BASE-X Ethernet fiber port)
enp1s0f0
enp1s0f1
enp3s0f0	Internal inline port
enp3s0f1

 

Table 3 Mapping relations between ports on the NSQM1ISPAXB1 intelligent service platform modules and network cards

Network card name	Interface
enp11s0f0	Port 0 on the faceplate (10/100/1000BASE-T Ethernet copper port)
enp11s0f1	Port 1 on the faceplate (10/100/1000BASE-T Ethernet copper port)
enp11s0f2	Port 2 on the faceplate (1000BASE-X Ethernet fiber port)
enp11s0f3	Port 3 on the faceplate (1000BASE-X Ethernet fiber port)
enp1s0f0	Internal inline port
enp1s0f1
enp3s0f0
enp3s0f1

 

Internal inline port interconnecting the module and device

When an intelligent service platform module is installed on a device, it connects to the device through an internal inline port. The name of the inline port depends on the device model. For example, if you install an NSQM1ISPAXA1 module on an F1080 firewall, the inline port is named as enp3s0f0 on the module side and as GE1/1/0 on the device side, as shown in the following table.

Table 4 Internal inline port interconnecting the module and device

Module name	Internal inline port name on the module side	Internal inline port name on the device side
NSQM1ISPAXA1	enp3s0f0	GE1/1/0
NSQM1ISPAXB1	enp1s0f0	XGE1/1/0 or XGE1/2/0

 

Technical specifications

The following table describes the technical specifications for the intelligent service platform module. For the technical specifications of the ports, see "Appendix A  Ports and LEDs."

Table 5 Technical specifications

Item	Specification
Processor	Intel C3558, 2.2 GHz
DDR	8 GB DDR4
Storage	480 GB SSD
Operating system	Linux
Hot swapping	Not supported
External ports	·     2 × GE copper ports (including one management Ethernet port) ·     1 × Console port ·     2 × USB ports (USB 2.0) ·     2 × GE fiber ports
Dimensions (H × W × D)	·     NSQM1ISPAXA1: 40.1 × 150 × 243.6 mm (1.58 × 5.91 × 9.59 in) ·     NSQM1ISPAXB1: 40.1 × 189 × 212.4 mm (1.58 × 7.44 × 8.36 in)
Weight	1 kg (2.20 lb)
Power consumption (static)	18 W
Power consumption (fully loaded)	·     NSQM1ISPAXA1: 28 W ·     NSQM1ISPAXB1: 29 W
Operating temperature	0°C to 45°C (32°F to 113°F)
Operating relative humidity (noncondensing)	5% to 95%

 

The power button LED on the module indicates the operating status of the module. To start up or put the module in standby mode, press and hold the power button for 2 seconds.

Table 6 Description for the power button LED

LED status	Description
Steady green	Power is present on the module.
Steady red	The module is in a standby state.

 

Installing the module

Restrictions and guidelines

Follow these restrictions and guidelines when installing the module:

·     Wear an ESD wrist strap during the installation process. Make sure the strap makes good skin contact and is reliably grounded.

·     To prevent device damages, do not use excessive force during installation.

·     An intelligent service platform module uses two interface module slots on a device. After you install an intelligent service platform module on a device that has only two interface module slots, you cannot install other interface modules on the device.

Installing the NSQM1ISPAXA1 intelligent service platform module

1.     Face the rear panel of the device.

2.     The NSQM1ISPAXA1 intelligent service platform module uses two interface module slots on the device. Use a Phillips screwdriver to remove the screws on the filler panels and remove the filler panels. Keep the removed filler panels secure.

Figure 3 Removing filler panels

 

3.     Take out the module from its packaging materials and slowly push it along the guide rails into the interface module slots until it has a firm contact with the device.

4.     Use a Phillips screwdriver to fasten the captive screws on the module.

Figure 4 Installing an NSQM1ISPAXA1 intelligent service platform module

 

	NOTE: After installation, part of the module is left outside the device, increasing the overall depth of the device by 72 mm (2.83 in).

 

Installing the NSQM1ISPAXB1 intelligent service platform module

1.     Face the rear panel of the device.

2.     The NSQM1ISPAXB1 intelligent service platform module uses two interface module slots on the device. Use a Phillips screwdriver to remove the screws on the filler panels and remove the filler panels. Keep the removed filler panels secure.

Figure 5 Removing filler panels

 

3.     Open the two ejector levers of the module, and then push the module slowly into the slot along the guide rails.

4.     Push inward the two ejector levers to ensure that the interface module is firmly seated in the slot.

5.     Use a Phillips screwdriver to fasten the captive screws on the module.

Figure 6 Installing the NSQM1ISPAXB1 intelligent service platform module

 

Remove the module

Restrictions and guidelines

Follow these restrictions and guidelines when removing an intelligent service platform module:

·     To avoid cable damage, remove cables from the module before removing the module.

·     Wear an ESD wrist strap during the removal process. Make sure the strap makes good skin contact and is reliably grounded.

·     To avoid damage to the device and its components, do not use excessive force during the removal process.

·     If you are not to install a new module, install filler panels in the slots in time to ensure adequate heat dissipation and prevent dust from entering the device.

·     Replace the removed module on an antistatic mat.

Removing an NSQM1ISPAXA1 intelligent service platform module

1.     Use a Phillips screwdriver to loosen the screws on the module.

2.     Pull the handle to disengage the module from the device's connector terminal.

3.     Use both hands to remove the module from the device slowly and horizontally.

4.     Place the removed on an antistatic mat or in an antistatic bag with its PCB side facing up.

Figure 7 Removing an NSQM1ISPAXA1 intelligent service platform module

 

5.     If you are not to install a new module, install filler panels in the slots in time. To install a new module, see "Installing the NSQM1ISPAXA1 intelligent service platform module."

Removing an NSQM1ISPAXB1 intelligent service platform module

1.     Use a Phillips screwdriver to loosen the captive screws on the interface module.

2.     Hold and rotate outward the two ejector levers of the module. Pull the module a small part way out of the slot along the guide rails, and then support the module bottom with one hand and pull out the module completely out of the slot with the other slowly.

3.     Place the removed module on an antistatic mat or in an antistatic bag with its PCB side facing up.

Figure 8 Removing an NSQM1ISPAXB1 intelligent service platform module

 

4.     If you are not to install a new module, install filler panels in the slots in time. To install a new module, see "Installing the NSQM1ISPAXB1 intelligent service platform module."

Verifying the installation

Execute the display interface brief command on the device to verify that the physical connection state and data link layer protocol state of the internal inline port are up.

If the physical connection state and data link layer protocol state of the internal inline port are not up, perform the following steps:

1.     Follow the instructions in this document to reinstall the module.

2.     If the issue persists, contact H3C Support.

Starting the module for the first time

Setting up the configuration environment

The module provides a console port on the front panel from which you can log in to the device for the first time. Figure 9 shows a typical network diagram for intelligent service platform modules, using the NSQM1ISPAXB1 module as an example.

Figure 9 Typical network diagram of the module

 

To perform initial configuration for the module, use a console cable to connect a PC to the console port on the module.

The module communicates with the device via an internal inline port. The internal inline port is identified as enp1s0f0 on the module side and recognized as a 10GE port (such as XGE1/1/0) on the device side. To remotely manage and upgrade the module, you can use the management Ethernet port enp11s0f0.

Connecting the console cable

Console cable

A console cable is an 8-core shielded cable, with a crimped RJ-45 connector at one end for connection to the console port on the module, and a DB-9 female connector at the other end for connection to the serial port on a configuration terminal (for example, a PC). The console cable is as shown in the following figure.

Figure 10 Console cable

 

Connecting the console cable

	CAUTION: ·     Pay attention to the port labels and ensure that you connect the cable to the correct port. ·     When connecting the module and a PC, first connect the DB-9 connector of the cable to the PC, and then connect the RJ-45 connector at the other end of the cable to the module. To disconnect the cable, remove the RJ-45 connector before removing the DB-9 connector.

 

To connect a configuration terminal to the module:

1.     Plug the DB-9 female connector of the console cable to the serial port on the configuration terminal (for example, a PC).

2.     Connect the RJ-45 connector of the console cable to the console port on the module.

Setting terminal parameters

To configure and manage the module from the console port, you must run a terminal emulator program, such as TeraTermPro, on your configuration terminal. For more information about the terminal emulator programs, see the user guides for these programs.

Configure the terminal emulation program parameters as follows:

·     Baud rate—115200.

·     Data bit—8.

·     Stop bit—1.

·     Parity check—None.

·     Flow control—None.

Configuration for the first access

	WARNING! To ensure system security, use the passwd command to edit the login password if you access the intelligent service platform module for the first time as a root user. For more information about the command, see “passwd command.”

 

As shown in Figure 11, after the intelligent service platform module software starts up, the terminal emulator program displays the user login interface when you access the module through the console port.

Figure 11 User login interface

 

When you access the intelligent service platform module for the first time, you access as a super (root) user. The username and default password are root and 123456, respectively. Press Enter to access the CLI.

Figure 12 CLI for the root user

 

Configuring the IP address and gateway for the intelligent service platform

This section describes how to configure an IP address and the gateway for NIC enp11s0f0 of the intelligent service platform system.

For the Linux operating system, the IP address of a NIC can be dynamically obtained through DHCP or manually configured. To ensure service continuity, manually configure a fixed IP address for a NIC.

To configure a fixed IP address for a NIC, you must edit the configuration file for the NIC. The configuration file resides in the /etc/sysconfig/network-scripts directory and its name is in the ifcfg-+NIC_name format. For example, the name of the configuration file for NIC enp11s0f0 is ifcfg-enp11s0f0.

To configure an IP address and the gateway for NIC enp11s0f0:

1.     Open the configuration file of NIC enp11s0f0 by using the vi editor.

 

	NOTE: For information about how to use the vi editor, see "vi editor."

 

[root@H3LINUX100 ~]# vi /etc/sysconfig/network-scripts/ifcfg-enp11s0f0

The configuration file content is as follows:

TYPE=Ethernet

PROXY_METHOD=none

BROWSER_ONLY=no

BOOTPROTO=dhcp

DEFROUTE=yes

IPV4_FAILURE_FATAL=no

IPV6INIT=yes

IPV6_AUTOCONF=yes

IPV6_DEFROUTE=yes

IPV6_FAILURE_FATAL=no

IPV6_ADDR_GEN_MODE=stable-privacy

NAME=quy

UUID=db19dc60-6676-43d8-aa8d-ba6df2cfe6da

DEVICE=enp11s0f0

ONBOOT=no

2.     Edit the configuration file.

¡     Change BOOTPROTO=dhcp to BOOTPROTO=static to manually configure an IP address for the NIC.

¡     Change ONBOOT=no to ONBOOT=yes to enable automatic startup of the NIC when the system starts up.

¡     Add the IPADDR, NETMASK, and GATEWAY items to configure the IP address, mask, and gateway address for the NIC, respectively. As shown in the example, configure the IP address as 1.1.1.1, mask as 255.255.255.0, and gateway address as 1.1.1.3. Enable automatic startup of the NIC when the system starts up.

The edited configuration file content is as follows:

TYPE=Ethernet

PROXY_METHOD=none

BROWSER_ONLY=no

BOOTPROTO=static

DEFROUTE=yes

IPV4_FAILURE_FATAL=no

IPV6INIT=yes

IPV6_AUTOCONF=yes

IPV6_DEFROUTE=yes

IPV6_FAILURE_FATAL=no

IPV6_ADDR_GEN_MODE=stable-privacy

NAME=quy

UUID=db19dc60-6676-43d8-aa8d-ba6df2cfe6da

DEVICE=enp11s0f0

ONBOOT=yes

IPADDR=1.1.1.1

NETMASK=255.255.255.0

GATEWAY=1.1.1.3

3.     Restart the network.service service.

[root@H3LINUX100 ~]# systemctl restart network.service

4.     Verify that NIC enp11s0f0 has obtained an IP address.

[root@H3LINUX100 ~]# ifconfig enp11s0f0

The following output shows that the NIC is configured with IP address 1.1.1.1.

enp11s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 1.1.1.1  netmask 255.255.255.0  broadcast 1.1.1.255

        inet6 fe80::2a0:c9ff:fe00:0  prefixlen 64  scopeid 0x20<link>

        ether 00:a0:c9:00:00:00  txqueuelen 1000  (Ethernet)

        RX packets 1248  bytes 95322 (93.0 KiB)

        RX errors 0  dropped 196  overruns 0  frame 0

        TX packets 67  bytes 9122 (8.9 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

        device memory 0x81760000-8177ffff

5.     Verify that NIC enp11s0f0 is configured with a gateway address.

[root@H3LINUX100 ~]# ip route

The following output shows that the NIC is configured with gateway address 1.1.1.2.

default via 1.1.1.2 dev enp11s0f0 proto static metric 100

1.1.1.0/24 dev enp11s0f0 proto kernel scope link src 1.1.1.1 metric 100

Configuring the SSH service

By default, the intelligent service platform is enabled with the SSH service. You can configure or upgrade the intelligent service platform through SSH remote access.

Viewing the SSH service status

To view the SSH service status, execute the following command:

[root@H3LINUX100 ~]# systemctl status sshd.service

Figure 13 shows that the SSH service is enabled.

Figure 13 Viewing the SSH service status

 

SSH remote access

	IMPORTANT: ·     When you access the intelligent service platform through SSH, make sure NIC enp11s0f0 has been configured with the IP address, mask, and gateway address. ·     Make sure your PC and NIC enp11s0f0 can reach each other. ·     Before accessing the intelligent service platform, make sure your PC is enabled with the SSH client feature.

 

You can remotely access the intelligent service platform through SSH as a root user or a non-root user.

·     Root user—Installs or upgrades the intelligent service platform.

·     Non-root user—Manages the intelligent service platform, such as configuring routes and uploading software versions of the intelligent service platform.

The methods of accessing the intelligent service platform are different for a root user and a non-root user.

·     Access the intelligent service platform as a root user.

You can access the intelligent service platform as a root user by using either of the following methods:

¡     Execute the [root@H3LINUX100 ~]# ssh [email protected] command.

Figure 14 Accessing the intelligent service platform as a root user through SSH (1)

 

¡     Execute the [root@H3LINUX100 ~]# ssh 1.1.1.1 command.

Figure 15 Accessing the intelligent service platform as a root user through SSH (2)

 

As shown in Figure 14, when you access the intelligent service platform as a root user for the first time, the system asks if you want to save the public key fingerprint of the target host. Please enter yes.

As shown in Figure 15, when you access the intelligent service platform as a root user again, the system does not ask again.

·     Access the intelligent service platform as a non-root user.

a.     If no non-root users are created, access the intelligent service platform as a root user first. Execute the useradd and passwd commands to create a non-root user and configure the login password, respectively.

For example, execute the following commands to create non-root user user and configure the login password as 123456.

[root@H3LINUX100 ~]# useradd user

[root@H3LINUX100 ~]# passwd 123456

Figure 16 shows that non-root user user is created and authenticated.

Figure 16 Creating a non-root user

 

b.     Execute the following command to access the intelligent service platform through SSH as a non-root user:

[root@H3LINUX100 ~]# ssh [email protected]

Figure 17 Accessing the intelligent service platform as a non-root user through SSH (1)

 

Figure 18 Accessing the intelligent service platform as a non-root user through SSH (2)

 

As shown in Figure 17, when you access the intelligent service platform as a non-root user for the first time, the system asks if you want to save the public key fingerprint of the target host. Please enter yes.

As shown in Figure 18, when you access the intelligent service platform as a non-root user again, the system does not ask again.

Appendix A  Ports and LEDs

Console port

Table 7 Console port specifications

Item	Specification
Connector	RJ-45
Standard compliant	EIA/TIA-232
Baud rate	115200 bps
Transmission medium and max transmission distance	≤ 15 m (49.21 ft) over asynchronous serial cables
Services	·     Provides connection to an ASCII terminal ·     Provides connection to a serial port of a local terminal (for example a PC) running a terminal emulator program

 

GE copper port

Table 8 GE copper port specifications

Item	Specification
Connector	RJ-45
Interface speed and duplex mode	1000 Mbps, full duplex
Cable type	Category 5 or above twisted pair cable
Max transmission distance	100 m (328.08 ft)
Standard compliant	IEEE 802.3i, 802.3u, 802.3ab
Functions and services	Connects to a computer or remote network management work station for upgrading and managing applications

 

GE fiber port

Table 9 GE fiber port specifications

Item	Specification
Connector	LC
Transceiver module type	SFP
Standard compliance	1000BASE-X
Interface speed	1000 Mbps
Duplex mode	Full duplex

 

USB port

Table 10 USB port specifications

Item	Specification
Interface type	USB2.0
Standard compliant	xHCI
Functions and services	Accesses the file system on the flash of the intelligent service platform module, for example, to upload or download application and configuration files

 

Port LEDs

Table 11 Port LED description

Status	Description
Steady green	A 1000 Mbps link is present on the port.
Flashing green	The port is sending or receiving data at 1000 Mbps.
Off	No link is present on the port.

 

Appendix B  Basic Linux commands

vi editor

The vi editor supports the following working modes:

·     Command mode—To enter this mode, execute the vi filename command to open a file. In this mode, you can perform the following tasks:

¡     Use the arrow keys to move the cursor.

¡     Delete characters or lines in the file.

¡     Copy and paste file data.

·     Insert mode—To enter this mode, press i, I, o, O, a, A, r, or R. In this mode, you can edit the content. To return to the command mode, press Esc.

·     Last-line mode—To enter this mode, press :, /, or ?. Then, the cursor moves to the bottom line. In this mode, you can search for keywords, read files, save files, replace characters in bulk, exit files, or view line numbers. To return to the command mode, press Esc.

The following example edits the configuration file of NIC enp11s0f0 to describe how to use the vi editor.

1.     Open the ifcfg-enp11s0f0 file.

[root@H3LINUX100 ~]# vi /etc/sysconfig/network-scripts/ifcfg-enp11s0f0

Figure 19 shows the configuration file content. The vi editor enters the command mode.

Figure 19 Configuration file content of NIC enp11s0f0

 

2.     Edit the configuration file.

Move the cursor to the end of the fourth line, and then press a. The vi editor enters the insert mode and the cursor moves to the position after the last p in the line. You can edit the ifcfg-enp11s0f0 configuration file as required.

After editing the configuration file, press Esc to return to the command mode. However, the configuration file content is not actually edited.

Figure 20 Editing the configuration file

 

3.     Save the configuration file.

In the current mode, press : to enter the last-line mode. In this mode, you can execute the following commands:

¡     w—Write the file.

¡     q—Exit the file.

¡     wq—Write and save the file.

¡     wq!—Write and forcibly save the file.

¡     q! —Forcibly exit the file without saving it.

As shown in Figure 21, execute the wq command in the last line to save the configuration file. Press Enter to return to the CLI.

Figure 21 Saving the configuration file

 

Configuring a temporary IP address

The temporary IP address of a NIC loses effect after the module restarts up. Configure temporary IP addresses for NICs as required.

To configure a temporary IP address for NIC enp11s0f0:

1.     Configure the IP address as 1.1.1.1 and mask as 24 for NIC enp11s0f0.

[root@H3LINUX100 ~]# ifconfig enp11s0f0 1.1.1.1/24

2.     View the IP address of NIC enp11s0f0.

[root@H3LINUX100 ~]# ifconfig enp11s0f0

Figure 22 Configuring a temporary IP address

 

The output shows that a temporary IP address has been configured for NIC enp11s0f0.

passwd command

Use the passwd or passwd username command to edit or configure the login password for a Linux user. When you access the intelligent service platform module for the first time or create a non-root user, you must edit or configure the login password.

·     To edit the login password for a root user who accesses the module for the first time, execute the passwd command at the CLI.

[root@H3LINUX100 ~]# passwd

As shown in Figure 23, after you execute the passwd command, the system prompts you to enter the new password twice. Make sure you enter the same new password.

Figure 23 Editing the login password for a root user

 

·     To configure a login password for a non-root user, first access the CLI as a root user. Execute the useradd command to create a non-root user, and then execute the passwd username command to configure a login password for the non-root user.

[root@H3LINUX100 ~]# useradd user

[root@H3LINUX100 ~]# passwd user

As shown in Figure 24, configure a password for non-root user user as prompted.

Figure 24 Creating a non-root user and configuring the login password

 

cd command

Use the cd [absolute path/relative path/special character] command to change the working directory for a login user.

The following shows examples about how to change the working directory for a login user.

·     Switch the working directory from the root directory to the /opt/EScan directory.

[root@H3LINUX100 ~]# cd /opt/EScan

[root@H3LINUX100 EScan]#

·     Switch the working directory from the /opt/EScan directory to the /opt/Adaptec directory.

[root@H3LINUX100 EScan]# cd ../Adaptec

·     Switch the working directory from the /opt/EScan directory to the root directory.

[root@H3LINUX100 EScan]# cd ~

·     Switch the working directory from the /opt/EScan directory to the /opt directory.

[root@H3LINUX100 EScan]# cd ..

cat command

Use the cat filename command to view the file content.

For example, execute the following command to view the scanner version:

[root@H3LINUX100 ~]# cat /opt/EScan/conf/configsVersion

tar command

Use the tar options filename command to compress folders to a file or decompress files.

For example, execute the following command to compress the EScan folder to the EScan.tar.gz file:

[root@H3LINUX100 EScan]# tar -czvf EScan EScan.tar.gz

Execute the following command to decompress the EScan.tar.gz file:

[root@H3LINUX100 EScan]# tar -xzvf EScan.tar.gz

cp command

Use the cp source destination command to copy files.

For example, execute the following command to copy the EScan.tar.gz file in the /opt directory to the /h3Linux directory:

[root@H3LINUX100 ~]# cp /opt/EScan.tar.gz /h3Linux

mkdir command

Use the mdkir directory command to create directories.

For example, execute the following command to create the /USB directory:

[root@H3LINUX100 /]# mkdir USB

Troubleshooting

NIC failure

Symptom

The ifconfig command does not display information about NIC enp3s0f1.

Solution

To resolve the issue:

1.     Execute the reboot command to restart the intelligent service platform module.

2.     Execute the following commands to reload the NIC driver.

modprobe –r igb

modprobe –r ixgbe

modprobe igb

modprobe ixgbe

Configuration terminal display problems

Symptom

The configuration terminal displays nothing or garbled text when the module is powered on.

Solution

To resolve the issue:

·     Verify that the power supply system is operating correctly.

·     Verify that the console cable is connected correctly to the serial port specified on the configuration terminal.

·     Verify that the configuration terminal parameters are configured correctly.

¡     Baud rate—115200.

¡     Data bits—8.

¡     Parity—None.

¡     Stop bits—1.

¡     Flow control—None.

¡     Terminal emulation—VT100.

·     Verify that the console cable is in good condition.