NEC ExpEther-2S, ExpEther-4S User Manual

Page 1

ExpEther IO Expansion Unit (40G)-2S ExpEther IO Expansion Unit (40G)-4S User’s Guide

Second edition, May 2017

The product, brand, or trade names used in this publication are the trademarks or registered

trademarks of their respective trademark owners. This manual may not be copied or altered without permission of NEC Corporation.

Page 2

[Memo]

Page 3

Keep this document as reference/with oneself while using the product. Keep this document in safe place. Read the precautions carefully before using the product

Precautions for Use (Must Read Before you Begin)

Note that "ExpEther IO Expansion Unit (40G)" described in this document indicates models for both,

N8141-80F: ExpEther IO Expansion Unit (40G)-2S and N8141-81F: ExpEther IO Expansion Unit (40G)4S.

The following provides information required to use the product with your server safely and properly. For

details of names in this section, refer to "Names and Functions of Parts" in this document.

Safety precautions

Follow the instructions in this document for the safe use of this product.

This User’s Guide describes hazardous parts of the product, possible hazards, and how to avoid them. Components with possible danger are indicated with a warning label placed on or around them

(or, in some cases, by printing the warnings on the product).

In User’s Guide or on warning labels, WARNING or CAUTION is used to indicate a degree of danger.

These terms are defined as follows:

Indicates there is a risk of death or serious personal injury.

Indicates there is a risk of burns, other personal injury, or property

damage.

Precautions and notices against hazards are presented with one of the following three symbols. The

individual symbols are defined as follows:

Attention

This symbol indicates the presence of a

hazard if the instruction is ignored.

An image in the symbol illustrates the hazard

type.

Example

Electric shock risk

Prohibited

action

This symbol indicates prohibited actions. An image in the symbol illustrates a particular

prohibited action.

Example

Do not disassemble

Mandatory

action

This symbol indicates mandatory actions. An image in the symbol illustrates a mandatory

action to avoid a particular hazard.

Example

Disconnect a plug

Page 4

Symbols used in this document and on warning labels

Attention

Indicates the presence of electric shock hazards.

Indicates the presence of mechanical

parts that can result in bodily injury.

Indicates the presence of a hot surface or component. Touching this

surface could result in bodily injury.

Indicates the presence of mechanical parts that can result in pinching or

other bodily injury.

Indicates there is a risk of explosion.

Indicates the presence of laser beam

that cause blindness.

Indicates there is a risk of fire or

fumes.

Indicates a general notice or warning

that cannot be pecifically identified.

Indicates there is a risk of electric shock for themultiple receiving.

Prohibited Actions

Do not disassemble, repair, or modify the product. Otherwise, an electric

shock or fire may be caused.

Do not touch the product with wet hand. Otherwise, an electric shock

may be caused.

Do not touch the component specified by this symbol. Otherwise, an electric

shock or burn may be caused.

Do not use the product in the place where water or liquid may pour. Otherwise, an electric shock or fire

may be caused.

Do not place the product near the fire.

Otherwise, a fire may be caused.

Indicates a general prohibited action

that cannot be specifically identified.

Mandatory Actions

Unplug the power cord of the product. Otherwise, it may cause an electric shock or fire.

Make sure equipment is properly grounded. Otherwise, it may cause an electric shock or fire.

Indicates a mandatory action that cannot be specifically identified. Make sure to follow the

instruction.

In addition to safety-related symbols for caution, the following notations are used in this document. These notations have the following meanings.

Important

Indicates critical items that must be followed when handling the hardware or operating

software.

Note

Indicates items that must be confirmed when handling the hardware or operating software.

Tip

Indicates information that is helpful to keep in mind when using this product.

Page 5

iii

Safety notes

This section shows notes on using the product safely. Read this section carefully to ensure proper and

safe use of the product. For symbols, refer to "Safety precautions" on page i.

General

Do not use the product for services where critical high availability may directly

affect human lives or high reliability is required.

This product is not intended to be used for control facilities or devices concerning human lives, including medical devices, nuclear facilities and devices, aeronautics and space devices, transportation facilities and devices; and facilities and devices requiring high reliability. We assumes no liability for any accident resulting in personal injury,

death, or property damage if the product has been used in the above conditions.

Do not directly look at the light.

An optical module mounted on this product uses laser beam for communication. Do not look at the optical connector terminal or insert a mirror when the power is turned on. If the laser beam gets into your eye, you may lose your sight (the laser beam is

invisible).

Do not use the product if any smoke, odor, or noise is present.

If smoke, odor, or noise is present, immediately turn off the product and disconnect the power plug from the outlet, then contact your sales representative. Using the product

in such conditions may cause a fire.

Do not insert needles or metal objects.

Do not insert needles or metal objects into ventilation holes in the product. Doing so

may cause an electric shock.

Use a rack that conforms to the designated standard.

This product can be mounted onto a 19-inch rack that conforms to EIA standards. Do

not mount the product onto any rack that does not conform to EIA standards. Doing so may cause a product malfunction, personal injury, or damage to peripheral devices. For more information about racks that can be used with the product, contact your

sales representative.

Use the product only under the specified environment.

Do not install the product rack in any environment that is not suitable for installation. Installation in an unsuitable environment is harmful for the product and other systems installed in the rack and may cause fire or personal injury due to the rack falling. For a detailed explanation on installation environments or seismic reinforcement, consult

with the instruction manual supplied with the rack or your sales representative.

Keep water or foreign matter away from the product.

Do not drop a pin, paper clip, water, alcohol and other foreign materials or liquid into this product. Failure to follow this warning may cause an electric shock, a fire, and other failures of the product. If such things accidentally enter the product, immediately turn off the power and disconnect the power plug from the outlet. Do

not disassemble the product, and contact your sales representative.

Page 6

Rack installation

Ambient temperature

The operating temperature of the rack ambient is greater than room ambient. Therefore, this product and other optional devices must be installed in an environment compatible with the maximum ambient temperature (Tma) specified by the

manufacturer.

Air Flow

Make air flow required for safe operation of this product and other units.

Loading of rack

Mount this product and other units onto the rack evenly. If the weight of units is shifted

to the right, the left, or the upper of the rack, the possibility of rack falling is increased.

Circuit overloading

Consideration should be given to the connection of the equipment to the supply circuit and the effect that overloading of the circuits might have on overcurrent protection and supply wiring. Appropriate consideration of equipment nameplate ratings should be

used when addressing this concern.

Reliable earthing

Maintain the reliable earthing of mounted units.

Do not attempt to carry or install the product alone.

At least two people are required to carry or install the rack. Otherwise, the rack may fall, resulting in personal injury or damage to peripheral devices. In particular, tall racks such as a 44U rack become unstable unless steadied with a stabilizer. Make sure that

two or more people hold the rack to carry or install the rack.

Do not install with the load weight distributed unevenly.

To avoid unevenly distributing the load of the rack and product, install a stabilizer or connect multiple racks to distribute the weight. Otherwise, the rack may fall, resulting

in personal injury.

Do not install components alone, and check the door hinge pins of the rack.

At least two people are required to install a rack door, rail, and other rack components. When installing the door, make sure that both upper and lower hinge pins are held in place. Incomplete attachment may cause components to fall off as well as personal

injury.

Do not pull out any unit from a rack that is not stable.

When pulling out a unit from the rack, make sure that the rack is stabilized (by using

stabilizers or quake-proof fixtures). Otherwise, the rack may fall, resulting in personal injury.

Do not pull out more than one unit from the rack.

Pulling out multiple units from the rack may cause the rack to fall, resulting in

personal injury. Pull out only one unit at one time.

Do not exceed the rated capacity of the power supply when connecting devices.

To prevent burn injuries, fire, and damage to the product, make sure the load on the

branch circuit that supplies power to the rack will not exceed the rated load.

Page 7

Power supply and power cord use

Do not hold the power plug with a wet hand.

Do not disconnect/connect the plug while your hands are wet. Failure to follow this

warning may cause an electric shock.

Do not connect the ground wire to a gas pipe.

Never connect the ground wire to a gas pipe. Failure to follow this warning may cause

a gas explosion.

Plug in to a proper power source.

Use a grounded outlet with the specified voltage. Use of an outlet with a voltage other than that specified causes fire and electrical leakage. Do not install the product in any environment that requires an extension cord. Connecting to a cord that does not conform to the power supply specs of the product causes overheating, resulting in fire.

Do not connect many power cords into a single outlet by using extension cords.

The electric current exceeding the rated flow overheats the outlet, which may cause a

fire.

Secure the power plug into the outlet.

Insert the plug of power cords into the outlet completely. Arc tracking may be

caused by inserting the plug halfway and the possibility of fire is increased.

Do not use any unauthorized power cord.

Use only the power cords authorized by NEC. Electric current that exceeds the amount allowed could cause fire. Also, observe the following precautions to prevent

electrical shock or fire caused by a damaged power cord.

•

Do not stretch the cord harness.

•

Do not bend the power cord.

•

Do not twist the power cord.

•

Do not step on the power cord.

•

Do not alter, modify, or repair the power cord.

•

Do not pinch the power cord.

•

Keep chemicals away from the power cord.

•

Do not place any object on the power cord.

•

Uncoil the power cord before use.

•

Do not secure the power cord with staples or equivalents.

•

Do not use a damaged power cord. Replace the damaged power cord with a power

cord of the same standard. Contact your sales representative for replacement.

Do not use the attached power cord for any other devices or usage.

The power cord that comes with your product is designed aiming to connect with this product and to use with the product, and its safety has been tested. Do not use the attached power cord for any other purpose. Doing so may cause a fire or an electric

shock.

Do not unplug the power cord by holding the cable part.

Pull the power cord straight out by holding the plug. Pulling the power cord by holding the cable part or applying extra pressure to the connector may damage the cable part,

which may cause a fire or electric shock.

Page 8

Installation, relocation, storage, and connection

Do not install the product in other than the specified place.

Do not install the product in the following places or any place other than specified in

User's Guide. Failure to follow this instruction may cause a fire.

•

A dusty place

•

A humid place such as near a boiler

•

A place where lamp black or steam is spread over

•

A place exposed to direct sunlight

•

A place near fire dump or thermal components

•

An unstable place

Do not use the product in an environment where corrosive gas is present.

Do not install the product in a place subject to corrosive gases including sulfur dioxide, hydrogen sulfide, nitrogen dioxide, chlorine, ammonia, or ozone. Do not install the product in an environment that contains dust, chemicals that accelerate corrosion such as NaCl or sulfur, or conductive materials. Failure to follow this warning may cause the

wiring on the printed wiring board to short-circuit, leading to fire. If you have any questions, contact your sales representative.

Do not install the product while the cover is removed.

Do not install the product to a rack while the cover or other relevant items removed. Not only will the cooling effect within the product decrease, causing the product to malfunction, but also may allow dust to enter the product, resulting in fire or electrical

shock.

Do not get your fingers caught in the rails.

When mounting/removing the product onto/from the rack, be careful to avoid getting

your fingers caught in the rails or cutting your fingers on the rails.

Do not install or remove optional devices while the power cord is plugged to a

power source.

Be sure to power off the product and unplug the power cord from a power outlet before

installing/removing any optional internal device to/from the product. If the product is off-

powered but its power cord is plugged to a power source, touching an internal component, cable, or connector may cause an electric shock or a fire resulted from a

short circuit.

Page 9

vii

Cleaning and working with internal devices

Do not disassemble, repair, or alter the product.

Never attempt to disassemble, repair, or alter the product on any occasion except as described in User's Guide. Failure to follow this warning may cause not only malfunction of the product but also an electric shock or fire.

Risk of explosion if a battery is removed or replaced.

Do not attempt to remove lithium, NiMH, or Li-ion batteries installed in this product by

yourself. If the product does not work normally due to the dead battery, contact your sales representative. Placing a battery close to a fire or in the water or replacing it with an incorrect type may cause an explosion. Dispose of used batteries according to

"Transfer, movement, and disposal."

Disconnect the power plug before cleaning the product.

Be sure to power off the product and disconnect the power plug from a power outlet before cleaning or installing/removing internal optional devices. Touching any internal device of the product with its power cord connected to a power source may cause an

electric shock even if the product is off-powered. Occasionally disconnect the power

plug from the outlet and clean the plug with a dry cloth. Heat will be generated if

condensation is formed on a dusty plug, which may cause a fire.

Pay attention to hot surface.

Components in the product are extremely hot just after the product is turned off.

Allow the surface to cool before installing/removing.

Secure cables or cards in place.

Be sure to secure the power cord, interface cables, and cards in place. Incomplete

installation causes a loose connection, resulting in smoke or fire.

Page 10

viii

During operation

Avoid contact with the product during thunderstorms.

Do not touch any part of the product including the cables when a thunderstorm is approaching. Also, do not connect or disconnect any devices. There may be a risk of

Keep animals away from the product.

Keep animals such as pets away from the product. Pet hair or other waste enters

the product, which may cause a fire or electric shock.

Do not place any object on top of products.

Separating the product from the rack may result in personal injury and damage to

nearby personal belongings.

Do not remove the product from the rack while it is running.

Do not pull out or remove the product from the rack while the product is running. In addition to causing equipment to not function properly, separating the product from the

rack may result in personal injury.

Do not get yourself caught in the fan.

Keep your hands and hair away from the cooling fan at the rear of the product during operation. Failure to observe this warning may cause your hands or hair

to catch in the fan, resulting in personal injury.

Page 11

Warning labels

Warning labels are attached on or near the components with potential hazards to draw attention of users to potential hazards involved in handling the server. These labels are either attached or printed on the components. Do not remove or black out these labels and keep them clean. If no labels are attached or

printed on the server, or if there is a label coming off or stained, contact your sales representative. (The followings are an example.)

Page 12

Transfer of this product

When transferring or selling this product to a third party, be sure to provide the documentation (including

this manual) to the third party.

Bundled software

Observe the following precautions when transferring the product to a third party.

 Transfer the bundled software together with the product.  All provided discs and documents must be transferred and no backup copies must be retained.  Transfer requirements listed in the "Software License Agreement" that comes with software must

be satisfied.

 Bundled software on client PC must be uninstalled before transferring.

Regarding the transportation of this product

This product and/or some of the associated optional devices uses lithium metal batteries or lithium ion batteries. Regulations for air/ocean transportation apply when transporting lithium batteries. Conform to the regulations if you want to transport this product or optional devices by air or ship.

Be sure to erase the data stored in HDD to prevent the leakage of sensitive data, such as customer data, to any third parties. NEC assumes no liability for data leakage. Data seems to be erased when you empty "Recycle Bin" of Windows or run the "format" command of the operating system. However, the actual data may still remain on the hard disk drive. Data not

erased completely might be restored by special software and used for unexpected purposes.

Page 13

Handling precautions (for proper operations)

Be sure to observe the following precautions for the proper functioning of the product. Ignoring the

precautions may cause malfunction or failure of the product.

 Connect the provided power cord to a 100 to 127/200 to 240 VAC outlet.  Install the product in an appropriate place. For details about the installation location, refer to “3.6

Installing ExpEther product” in User's Guide.

 If a peripheral device is not a hot-plug device, make sure that the server is off and unplug the

power cord before connecting/removing cables to/from peripheral devices.

 Wait for at least 30 seconds before connecting power cord to power outlet after disconnecting it.  Turn off the product and unplug the power cord before moving it.  Regularly clean the product to prevent various types of failure. For details about cleaning, refer to

“7 Daily Maintenance” in User's Guide.

 Wait for at least 30 seconds before turning on the product after turning off the product.  In the following cases, check and adjust the system clock before operation.

- After transportation

- After storage

- After the product is used following a period of disuse, in which storage conditions did not conform to those that guarantee product operations.

 Momentary voltage drop may occur due to lightning strike. To prevent this, use of UPS is

recommended.

 Check the system clock approximately once per month  When you have installed your PCI Express option card, install the driver according to the

instruction manual attached to the card.

 Demolished or remodeled products are not warranted.  We recommend that you store the product at a constant temperature to properly operate the

product and built-in devices in case of consecutive operations.

 Observe the following storage conditions to store the product.

- Temperature: −10°C to 55°C, Humidity: 20% to 80%, No condensation of moisture

 Do not use any cell phone or PHS and switch off them near the product. Electric waves from such

devices can cause product to malfunction.

 Make sure to use optional devices supported by this product. Even if third party's devices are

successfully installed or connected, installation of unsupported devices can cause the product to

malfunction or even failure.

 For optional devices, we recommend you use our NEC products. Some third-party products claim

that they support this product. You will be charged to repair failure or damage caused by use of

such products even within warranty period.

Page 14

xii

Anti-static measures

This product contains static-sensitive electronic components. Take the measures below to avoid a failure caused by static electricity when installing or uninstalling any optional device.

 Wearing anti-static wrist strap or anti-static gloves

Wear a wrist strap on your wrist and connect the wire to the chassis. If there is no wrist strap, touch an unpainted metal surface of the chassis connected to the ground to discharge static electricity from your body before touching the component. Touch the metal part occasionally to

discharge the static electricity while working on the component.

 Checking the workplace

- Work on an anti-static floor or concrete floor.

- If you work on a place where static electricity is likely to be generated (e.g. carpet), be sure to provide anti-static protection.

 Using the work table

- Place the server on a mat with electrostatic discharge (ESD) protection.

 Clothing

- Do not wear wool or synthetic clothes.

- Wear anti-static shoes.

- Remove any kind of metal accessories such as a ring, bracelet or wrist watch.

 Handling of components

- Keep the component in an anti-static bag until you install it to the product.

- Hold the component by the edges to avoid touching any terminals or mounting parts.

- Place the component in an anti-static bag when storing or moving it.

 Handling of cables

When connecting a cable (e.g., LAN cable), static electricity may also be charged due to friction against the floor. Connecting the charged cable with an I/O device may cause damage to the devices in the system. It is recommended to use a product such as electrostatic discharge kit to

eliminate the static charge before connecting the cable. Installing and uninstalling the optional device

- To avoid electric hazard and malfunction, be sure to turn off the power switch of the server

and unplug the power cord from the outlet before installing or uninstalling any optional

device.

- The device contains static-sensitive electronic components. When installing or uninstalling the optional device, wear an anti-static wrist strap on your wrist to avoid a failure caused by the static electricity. To use the strap, connect the wire to the chassis.

Page 15

xiii

For your health

As you are apt to keep the same posture for a long period in a desk work using a computer, you will easily

get the following medical conditions compared to other general office work.

 Getting eye strain  Heavy eyes  Getting blurred  Easily getting tired  You become numb on your neck, shoulder and fingers and feel pain entirely.

It is said that the way you feel these medical conditions differs substantially between individual due to

working hours and usage conditions. Keep the following in mind.

 Have 10 to 15 minutes break per one hour work.  Create a diversion by getting a light exercise during a break.

If you still feel tired on the next day, consult a doctor early.

Page 16

xiv

Accessories

The carton box contains this various accessories which are required for setup or maintenance. Make sure

you have them all for future use.

Make sure you have all accessories and inspect them. For details of the accessories, refer to attached

Getting started! If an accessory is missing or damaged, contact your sales representative.

Important

The chassis serial number plate and maintenance label is located on the product. If the serial number does not match the number on the warranty, you may not be guaranteed against failure even within the warranty

period. Contact your sales representative if they do not match.

Page 17

Abbreviations of Operating Systems

Windows Operating Systems are referred to as follows.

Notations in this manual

Official names of Windows

Windows Server 2012 R2 Windows Server 2012 R2 Standard

Windows Server 2012 R2 Datacenter

Disposal of this product and consumables

 Dispose of this product and optional products according to laws and regulations of the central

and/or local government. Dispose of the attached power cable together with the product to

prevent misuse to other products.

 For details about how to discard (and replace) the battery installed in this product, contact your

sales representative.

 Some parts of the product require replacement due to the life-span. We recommend that you

replace these parts periodically to operate it in a stable condition. Contact your sales

representative for the period of replacement and the life-span.

Page 18

xvi

Introduction

Thank you for purchasing this NEC ExpEther Series product.

ExpEther series products provide full expandability and flexible system configuration as an option product

of the NEC Express server.

Read this manual before using the product thoroughly to fully understand handling of ExpEther Series

product and appreciate its functions to the maximum extent.

Warnings and Additions to This Document

1. Unauthorized reproduction of the contents 1. of this manual, in part or in its entirety, is prohibited.

2. This manual is subject to change at any time without notice.

3. Do not make copies or alter the manual content without permission from NEC Corporation.

4. If you have any concerns, or discover errors or omissions in this manual, contact your sales representative.

5. Regardless of article 4, NEC Corporation assumes no responsibility for effects resulting due to your operations/mishandling.

6. The values used in the manual are sample values and not from actual use.

Latest editions

This manual was created based on the information available at the time of its creation. The screen images,

messages, and procedures are subject to change without notice. Substitute as appropriate when content

has been modified. Contact your sales representative for the latest version of documents including the user’s guide.

Keep this manual for future use.

Page 19

xvii

Contents

Precautions for Use (Must Read Before you Begin) .................................................. i

Safety precautions .................................................................................................................. i

Symbols used in this document and on warning labels ...................................................... ii

Safety notes........................................................................................................................... iii

Warning labels ...................................................................................................................... ix

Transfer of this product ......................................................................................................... x

Regarding the transportation of this product ...................................................................... x

Handling precautions (for proper operations) .................................................................... xi

Anti-static measures ............................................................................................................ xii

For your health .................................................................................................................... xiii

Accessories ......................................................................................................................... xiv

Abbreviations of Operating Systems ................................................................................. xv

Disposal of this product and consumables ....................................................................... xv

Introduction ......................................................................................................................... xvi

Warnings and Additions to This Document ...................................................................... xvi

Latest editions ..................................................................................................................... xvi

Chapter 1. Names and Functions of Parts .......................................................................... 1

1.1 N8141-80F ExpEther IO Expansion Unit (40G)-2S / N8141-81F ExpEther IO Expansion Unit

(40G)-4S ............................................................................................................................................ 1

1.1.1 ExpEther IO Expansion Unit (40G)-2S (Front) ..................................................................... 2

1.1.2 ExpEther IO Expansion Unit (40G)-4S (Front) ..................................................................... 4

1.1.3 ExpEther IO Expansion Unit (40G)-2S (Rear) ..................................................................... 6

1.1.4 ExpEther IO Expansion Unit (40G)-4S (Rear) ..................................................................... 7

1.2 N8143-121 ExpEther (40G) rack mount kit ................................................................................ 8

Chapter 2. To Operate This Unit Properly ........................................................................... 9

2.1 To operate this unit properly ....................................................................................................... 9

2.2 Transportation and storage ........................................................................................................ 9

Chapter 3. Setup ................................................................................................................. 10

3.1 Notes on installing built-in options ........................................................................................... 10

3.2 Safety notes ............................................................................................................................. 10

3.3 Anti-static measures ................................................................................................................. 10

3.4 Installing/Removing the cable .................................................................................................. 11

Page 20

xviii

3.5 Installing the ExpEther IO Expansion Unit (40G) and the option card .................................... 12

3.6 Installing ExpEther products .................................................................................................... 16

3.6.1 Environment to install the ExpEther IO Expansion Unit (40G) ........................................... 16

3.6.2 Mounting the ExpEther IO Expansion Unit (40G) on the rack ........................................... 18

3.7 Connecting ExpEther products ................................................................................................ 21

3.7.1 1:1 connection without using a network switch .................................................................. 22

3.7.2 Connection using an ethernet network switch (one ExpEther board (40G)) ..................... 23

3.7.3 Connection using an ethernet network switch (two or more ExpEther boards (40G)) ...... 25

Chapter 4. Procedure for Using the Product ..................................................................... 27

4.1 ExpEther Manager Software .................................................................................................... 27

4.1.1 Installing ExpEther manager .............................................................................................. 29

4.1.2 Uninstalling ExpEther manger ............................................................................................ 35

4.1.3 Procedure to start and stop ExpEther Manager ................................................................. 35

4.1.4 CLI (command line) ............................................................................................................ 36

4.2 ExpEtherConfig tool ................................................................................................................. 56

4.2.1 Installation and uninstallation (Windows version） .............................................................. 56

4.2.2 Command reference ........................................................................................................... 61

Chapter 5. Cautions ............................................................................................................ 64

5.1 Note on the ExpEther IO Expansion Unit (40G) ...................................................................... 64

5.2 Other notes ............................................................................................................................... 64

Chapter 6. Specifications ................................................................................................... 65

6.1 Specifications ........................................................................................................................... 65

6.2 Environmental requirements .................................................................................................... 66

6.3 Cable ........................................................................................................................................ 66

Chapter 7. Daily Maintenance ............................................................................................ 67

7.1 Checking and Applying Updates .............................................................................................. 67

7.2 Checking LED .......................................................................................................................... 67

7.3 Cleaning ................................................................................................................................... 67

Chapter 8. User Support ..................................................................................................... 69

8.1 Maintenance Services .............................................................................................................. 69

8.2 Before Asking for Repair .......................................................................................................... 69

Chapter 9. Troubleshooting ............................................................................................... 70

9.1 Common problems of ExpEther series products ..................................................................... 70

9.2 Problems of ExpEther IO Expansion Unit (40G) ..................................................................... 71

9.3 Problems on ExpEther Manager Software .............................................................................. 71

Page 21

Chapter 1. Names and Functions of Parts

This chapter describes the names of the procuts parts.

1.1 N8141-80F ExpEther IO Expansion Unit (40G)-2S / N8141-81F ExpEther IO Expansion Unit (40G)-4S

Number

Name

Function

(1)

ExpEther IO

Expansion Unit (40G)

ExpEther IO Expansion Unit (40G)

Main unit (The figure shows the ExpEther IO Expansion Unit

(40G)-4S.)

(2)

Expansion power cable for PCI Express

board (accessory)

Extension power cable for PCI Express boards with two 6pin (2x3) connectors

(3)

Expansion power cable for GPU computing processor board (accessory)

Expansion powercable for GPU computing processor board; Contact your sales representative for corresponding products for which the operation has been checked.

(4)

Clamp for power cord

(accessory)

Clamp for power cord used to prevent the power cord from

falling off; Refer to the installation description for installation.

* Contact your sales representative for the power cord.

(1)

(2) (3)

(4)

Page 22

1.1.1 ExpEther IO Expansion Unit (40G)-2S (Front)

Number

Name

Function

(1)

Cooling FAN1

Cooling fan to cool the board in this unit and mounted option

boards

(2)

Cooling FAN2

Cooling fan to cool boards installed in the unit

(3)

Management LAN

Port

A port to connect the management LAN

(4)

Main Power Switch

Main power switch of the ExpEther IO Expansion Unit (40G) -2S; Press the main power switch to turn on/off the power.

(5)

System Status LED

This indicates the status of the ExpEther IO Expansion Unit

(40G).

On (amber): Status error (Critical) Blinking (amber): Status error (Warning) Off: Normal

(6)

POW LED

This indicates the power status of the ExpEther IO Expansion

Unit (40G).

On (green): DC-ON Blinking (green): DC-OFF Off: AC-OFF

(7)

ID LED

This indicates UID per slot.

On (blue): UID is on. Off：UID is off.

(8)

Slot Status LED

This indicates the status per slot.

On (amber): Status error Off: Normal

(9)

Host POW LED

This indicates the power status of the host connected to each

slot.

On (green): Host DC-ON Off: Host DC-OFF

(10)

UID Switch

ON/OFF status of the UID switch is output to the network per

slot. You can get the status via ExpEther Manager. (Install ExpEther Manager before using the function.)

(11)

Group ID Switch

The rotary switch to set the Group ID per slot; The factory default is “0”.You can set the Group ID from 1 to F (15) with this switch.If this switch is set to “0”, the Group ID can be set to 16 to 4000 by ExpEther Manager.You need to set the same Group ID to ExpEther boards (40G) connected to each slot of the ExpEther IO

Expansion Unit (40G) -2S.Change the setting of the Group ID switch when you turn off the power.

(2)

(7)

(8)

(10)

(9)

(11)

(4)

(5)

(3)

(6)

(1)

(12)

(13)

Page 23

Number

Name

Function

(12)

SPEED LED

This indicates the transfer speed of the management LAN port.

On (green): The port is operating with 100BASE-TX interface.

(13)

LINK/ACT LED

This indicates the access status of the management LAN port.

On (green): The port is connected with network normally. Blinking (green): The port is accessing network. Off: The port is disconnected from network.

Page 24

1.1.2 ExpEther IO Expansion Unit (40G)-4S (Front)

Number

Name

Function

(1)

Cooling FAN1

Cooling fan to cool the board in this unit and mounted option

boards

(2)

Cooling FAN2

Cooling fan to cool boards installed in the unit

(3)

Management LAN Port

A port to connect the management LAN

(4)

Main Power Switch

Main power switch of the ExpEther IO Expansion Unit (40G) -4S; Press the main power switch to turn on/off the power.

(5)

System Status LED

This indicates the status of the ExpEther IO Expansion Unit

(40G).

On (amber): Status error (Critical) Blinking (amber): Status error (Warning) Off: Normal

(6)

POW LED

This indicates the power status of the ExpEther IO Expansion

Unit (40G).

On (green): DC-ON Blinking (green): DC-OFF Off: AC-OFF

(7)

ID LED

This indicates UID per slot.

On (blue): UID is on. Off：UID is off.

(8)

Slot Status LED

This indicates the status per slot.

On (amber): Status error Off: Normal

(9)

Host POW LED

This indicates the power status of the host connected to each

slot.

On (green): Host DC-ON Off: Host DC-OFF

(10)

UID Switch

ON/OFF status of the UID switch is output to the network per

slot. You can get the status via ExpEther Manager. (Install ExpEther Manager before using the function.)

(11)

Group ID Switch

ExpEther IO Expansion Unit (40G) -4S.Change the setting of the Group ID switch when you turn off the power.

(2)

(3)

(5)

(4)

(6)

(7)

(8)

(9)

(1)

(11)

(10)

(12)

(13)

Page 25

Number

Name

Function

(12)

SPEED LED

This indicates the transfer speed of the management LAN port.

On (green): The port is operating with 100BASE-TX interface.

(13)

LINK/ACT LED

This indicates the access status of the management LAN port.

On (green): The port is connected with network normally. Blinking (green): The port is accessing network. Off: The port is disconnected from network.

Page 26

1.1.3 ExpEther IO Expansion Unit (40G)-2S (Rear)

Number

Name

Function

(1)

Fixing screw of the top

board

The screw fixes the top board of the ExpEther IO Expansion

Unit (40G).

(2)

PCIe Slot 1

The slot 1 is used to install the PCI Express card. A blank

panel is attached before shipment (two slot width).

(3)

(4)

PCIe Slot 2

The slot 2 is used to install the PCI Express card. A blank

panel is attached before shipment (two slot width).

(5)

(6)

QSFP + Port 1

Connectors to connect QSFP+ modules or DA cable

(7)

QSFP + Port 2

(8)

QSFP + Port 3

(9)

QSFP + Port 4

(10)

QSFP + Connector 1 Link LED

This indicates the network connection status of each QSFP+

port.

On (green): Normal connection status (link up status ) On (amber):Connection problem and communication

disabled

(11)

QSFP+ Connector 2 Link LED

(12)

QSFP+ Connector 3 Link LED

(13)

QSFP+ Connector 4 Link LED

(14)

Power Connector

Connectors to connect the attached power cord

(15)

Power LED

On (green): The power of the unit is turned on. Blinking (green): The power cord is connected and receiving

the AC power. On (amber): The power unit is out of order. Blinking (amber): The power unit is out of order. Off: The power is not supplied.

(1)

(2)

(3)

(4)

(5)

(15)

(14)

(8)

(6)

(10)

(11)

(7)

(9)

(12)

(13)

Page 27

1.1.4 ExpEther IO Expansion Unit (40G)-4S (Rear)

Number

Name

Function

(1)

Fixing screw of the top

board

The screw fixes the top board of the ExpEther IO Expansion

Unit (40G).

(2)

PCIe Slot 1

The slot 1 is used to install the PCI Express card. A blank

panel is attached before shipment (two slot width).

(3)

PCIe Slot 2

The slot 2 is used to install the PCI Express card. A blank

panel is attached before shipment (two slot width).

(4)

PCIe Slot 3

The slot 3 is used to install the PCI Express card. A blank

panel is attached before shipment (two slot width).

(5)

PCIe Slot 4

The slot 4 is used to install the PCI Express card. A blank

panel is attached before shipment (two slot width).

(6)

QSFP + Port 1

Connectors to connect QSFP+ modules or DA cable

(7)

QSFP + Port 2

(8)

QSFP + Port 3

(9)

QSFP + Port 4

(10)

QSFP + Connector 1 Link LED

This indicates the network connection status of each QSFP+

port.

On (green): Normal connection status (link up status ) On (amber):Connection problem and communication

disabled

(11)

QSFP+ Connector 2 Link LED

(12)

QSFP+ Connector 3 Link LED

(13)

QSFP+ Connector 4 Link LED

(14)

Power Connector

Connectors to connect the attached power cord

(15)

Power LED

On (green): The power of the unit is turned on. Blinking (green): The power cord is connected and receiving

the AC power. On (amber): The power unit is out of order. Blinking (amber): The power unit is out of order. Off: The power is not supplied.

(1)

(2)

(3)

(4)

(5)

(15)

(14)

(8)

(6)

(10)

(11)

(7)

(9)

(12)

(13)

Page 28

1.2 N8143-121 ExpEther (40G) rack mount kit

Number

Name

Function

(1)

Front bracket

Front side bracket to mount the ExpEther IO Expansion Unit

(40G) on the rack.

Quantity: 3

(2)

Rear bracket

Rear side bracket to mount the ExpEther IO Expansion Unit

(40G) on the rack

Quantity: 3

(3)

Rear Mount Frame

Rear side frame to mount the ExpEther IO Expansion Unit

(40G) on the rack

Quantity: 1

(4)

Front Mount Frame

Front side frame to mount the ExpEther IO Expansion Unit

(40G) on the rack

Quantity: 3

(5)

Screw

Following screws are attached. Screw (M410)  5 (including two spares) Screw (M512)  8 (including two spares) Screw (M38)  14 (including two spares)

Important

”N8140-820 general-purpose tray” is required to mount this unit on the rack using the rack mount kit. Check the following section for installation.

3.6.2 Mounting the ExpEther IO Expansion Unit (40G) on the rack

(1)

(2)

(3)

(4)

(5)

Page 29

Chapter 2. To Operate This Unit Properly

This section describes precautions to connect this unit and peripheral devices. Read this chapter to use the unit correctly

2.1 To operate this unit properly

Observe the following precautions to operate ExpEther products properly.

(1) Note on the environment for usage

Use ExpEther products in the environment where you properly operate them. Refer to “6.2

Environment specification” for the detail.

(2) Note during the operation

1. Check that the power cord of the server to connect the ExpEther board (40G) is not connected before installing/uninstalling the cable to connect peripheral devices (except USB). Installing/Uninstalling it without turning off the power may cause malfunction and a failure.

2. When you turn off and turn on the power of the ExpEther product again, take at least 30 seconds interval. Turning on the power immediately after turning off may cause malfunction and a failure.

(3) Note on cable connection

1. Use the cable conforming to the connector form and the signal array to connect ExpEther products and peripheral devices.

2. Do not give the cable a strong pull and put something on it. Install peripheral devices in a location where the cable may not be pulled. Avoid using the unit in a situation when the cable is stretched and when something is put on the cable.

3. Install the connector firmly. If you do not insert the connector firmly, you may not successfully operate the unit or cause malfunctioning. Install the connector firmly.

2.2 Transportation and storage

Follow the procedure described below to transport and store ExpEther products.

1. Turn off the power.

2. Pull out the power cord from the outlet.

Important

Pull the power cord straight out by holding the plug. Pulling the power cord by holding the cable part or applying extra pressure to the connector may damage

the cable part, which may cause a fire or electric shock.

3. Remove all cables connected to the unit.

4. Pack the unit securely so that it may not be damaged, shocked and shaken.

Page 30

Chapter 3. Setup

This chapter describes how to handle the unit correctly.

3.1 Notes on installing built-in options

This section describes installing options to the ExpEther IO Expansion Unit (40G) and precautions.

Important

 We recommend that a specialist, who is familiar with the unit and is an

engineer of a maintenance service company, install built-in options.

 Use parts specified by our company for built-in options and cables. If you

install other options than those specified, you should pay for a repair due

to malfunction, failure or damage even under the warranty period.

3.2 Safety notes

Important

Be sure to read “Precautions for use” described in the user’s guide or the startup guide attached to the unit. “Precautions for use” describes important

precautions to safely and correctly use this product.

3.3 Anti-static measures

This product contains static-sensitive electronic components. Take the measures below to avoid a failure caused by static electricity when installing or uninstalling any optional device.

● Wearing anti-static wrist strap or anti-static gloves Wear a wrist strap on your wrist and connect the wire to the chassis. If there is no wrist strap, touch an unpainted metal surface of the chassis connected to the ground to discharge static electricity from your body before touching the component. Touch the metal part occasionally to discharge the static electricity while working on the component.

● Checking the workplace

- Work on an anti-static floor or concrete floor.

- If you work on a place where static electricity is likely to be generated (e.g. carpet), be sure

to provide anti-static protection.

● Using the work table Place the server on a mat with electrostatic discharge (ESD) protection.

● Clothing

- Do not wear wool or synthetic clothes.

- Wear anti-static shoes.

- Remove any kind of metal accessories such as a ring, bracelet or wrist watch.

● Handling of components

- Keep the component in an anti-static bag until you install it to the product.

- Hold the component by the edges to avoid touching any terminals or mounting parts.

- Place the component in an anti-static bag when storing or moving it.

Page 31

3.4 Installing/Removing the cable

Installation

1. Insert the cable into the QSFP slot of the ExpEther IO Expansion Unit (40G).

Important

Insert the cable until it clicks.

Removal

1. Hold the handle of the cable from the QSFP slot of the ExpEther IO Expansion Unit (40G) and pull out the cable horizontally to the arrow direction.

Important

Be sure to pull the handle of the cable horizontally.

If you pull out the other part or pull out the cable to other directions, you may

damage the unit and the cable.

Handle

Page 32

3.5 Installing the ExpEther IO Expansion Unit (40G) and the option card

* The following illustration shows “ExpEther IO Expansion Unit (40G)-2S” as an example.

Important

Pull out the power plug from the outlet and remove the cable connecting

external devices before installing and removing the card.

1. Remove two screws on the back of the ExpEther IO Expansion Unit (40G) and slide the top cover to the back to remove it.

2. Remove the blank panel in the PCI Express slot to mount an option card. Remove blank panels for two slots to mount a two slot width option card.

PCI Express Slot Blank Panel

Page 33

3. Install a PCI Express option card mounted on the ExpEther IO Expansion Unit (40G) in the PCI Express slot of the unit and fix it with screws used for fixing the blank panel.

Important

Remove the retainer attached to the option card before mounting the card. You cannot mount it with a retainer on the ExpEther IO Expansion Unit.

PCI Express Option Card

Retainer

Remove the retainer.

Page 34

Important

Connect the attached extension power cable for the PCI Express board

to mount an option card that requires the extended power supply.

(You may need the extension power cable for the GPU computing

processor for the GPU computing processor board.) Either the 6-pin or 2-pin connector or both may not be connected depending on the PCI Express option card to be mounted. Form cables to avoid interfering with fans in the device. Form cables to avoid blocking the fan in the device. Use the attached cable tie as needed (only models with the cable).

4. Install the top cover in the reverse steps of removing it in step1.

Important

Take care not to have the cable of the fan pinched when you install the

top cover.

5. Set the group ID setting switch corresponding to the option card slot by using a flathead

screwdriver (2.3 to 2.5 mm in width). Set the group ID to 1 to F (15) according to the setting of the ExpEther board (40G) to be connected. If you set it to “0”, you can set the group ID to 16 to 4000 by using ExpEther Manager. You need to set the group ID in each slot for the

ExpEther IO Expansion Unit (40G).

Tips

You cannot connect the ExpEther board (40G) and the ExpEther IO Expansion Unit (40G) with different Group ID. Set the expansion unit to the

same Group ID as that of the ExpEther board (40G) to be connected.

Group ID Switch

Page 35

6. Connect the attached power cord to the power connector of the ExpEther IO Expansion Unit

(40G). Fix the power cord to the cable clamp to prevent it from falling off using the following

figure as a reference.

Important

If you use the power cord without attaching it to the clamp, you might

have the power cord pulled out during use.

Clamp for power cord

Page 36

3.6 Installing ExpEther products

This section describes installing the unit and connection.

Important

Be sure to read “Precautions for use” described in the user’s guide or the startup guide attached to the unit. “Precautions for use” describes important

precautions to safely and correctly use this product.

3.6.1 Environment to install the ExpEther IO Expansion Unit (40G)

The environment suitable for ExpEther IO Expansion Unit (40G) is as follows. Hold the product and carry it to the installation site, then place it slowly and gently.

Environment requirements <Operating Conditions>

Ambient temperature: 10

C to 40C

Humidity: 20 % to 80 %( and no

condensation) <Non-operating Conditions> Ambient temperature: -10

C to 55

Humidity: 20 % to 80 %( and no

condensation)

The outlet corresponding to the

AC cable used

Clean and orderly room

Floor, or flat and

sturdy desk

At least 150 mm clearance in front of/behind the unit, and 150 mm

clearance on both sides

Page 37

Do not install the product in an environment in which any of the following conditions apply:

Installing the product in any of the following conditions will cause the product to malfunction.

Important

Secure at least 150 mm for the back and front and 100 mm for the right

and left to install this unit.

The cooling capability of the unit may be reduced if enough space is not

secured.

Place of drastic temperature change, near a heater, air conditioner, or refrigerator.

Place where a carpet not subject to anti-static process is laid.

Place where the power cord of the product must be connected to an AC outlet that shares the ground wire with another outlet where another device with large power consumption is connected.

Place where intense vibration may be generated.

Place where some objects may be fallen.

Place near a device generating intense magnetic field such as TVs, radios, broadcast/communication antennas, power transmission wires, and electromagnetic cranes is placed.

Places where corrosive gas is present, such as environments where there is sulfur vapor i n the atmosphere, or places where chemicals are nearby or may be accidentally sprayed over.

Places where the power cords or interface cables may be stepped on or tripped over.

Do not install where there is power supply noise nearby such as contact sparks when turning power on or off during power relays. If you must install the server close to such equipment, separate power cables or install noise filter.

Page 38

3.6.2 Mounting the ExpEther IO Expansion Unit (40G) on the rack

You can mount the ExpEther IO Expansion Unit (40G) on a 19-inch rack by using the N8140-820 general-purpose tray and the N8143-121 ExpEther (40G) rack mount kit. You can mount up to 3 ExpEther IO Expansion Units (40G) per N8140-820 general-purpose tray and N8143-121 ExpEther (40G) rack mount kit.

The procedure to mount the ExpEther IO Expansion Unit (40G) is described below. (The illustration shows the ExpEther IO Expansion Unit (40G)-4S.)

Refer to the setup guide of the general-purpose tray for mounting the N8140-820 general-purpose tray on a 19-inch rack.

1. Installing a bracket on the unit

Install a front bracket on the front of the ExpEther IO Expansion Unit (40G) and install a rear

bracket on the back. Front

Rear

Screw: Fix it with 2 screws (M3x8).

Rear Bracket

Front Bracket

Page 39

2. Installing a bracket on the general-purpose kit

Install the rear mount frame in the general-purpose tray to be on the back of the unit. After fitting the part in the slit of the general-purpose tray, fix it with 3 screws (M4x10) from the bottom. Install it up to the third slit from the end.

Tips

Install the rear mount frame over two slits.

3. Installing the ExpEther IO Expansion Unit (40G)

Insert the bracket so that the rear bracket attached to the ExpEther IO Expansion Unit (40G)

fits in the raised part on the rear mount frame attached to the general-purpose tray.

Up to here

Rear

Fix it with 3 screws (M4x10).

Page 40

4. Installing a bracket

Hook the front mount frame on the slit of the general-purpose rack on the front of the

ExpEther IO Expansion Unit (40G) and hook it on the front bracket. Then, fix it with screws

(M5x12).

5. Installing a core nut on the rack Use this unit by installing it to a 19-inch rack compatible to the EIA standard. Install the unit after checking that the rack conforms to the following conditions.

Important

Install the unit after checking that the rack satisfies the following conditions.  There is 1 m or more space on the back and the front, 60 cm or more on the

right and the left and 40 cm or more from the top.

 The place can keep the room temperature between 10 ºC and 35 ºC and

the humidity between 20 % and 80 %.

Important

Pay attention to the following points when you install a rack mount kit.  Use a space for 4U to install the ExpEther IO Expansion Unit (40G).

Area occupied for installation

Screw: Fix it with 2 screws (M5x12).

Page 41

3.7 Connecting ExpEther products

Observe the following precautions when you connect ExpEther products.

 Use an ethernet network switch compliant with layer 2.  If Spanning Tree Protocol (STP) is enabled by the ethernet network switch setting, the

ExpEther board (40G) and the ExpEther IO Expansion Unit (40G) may take time to link

up and be ready for communication after the power-on and may not recognize the option board mounted on the IO Expansion unit (40G)-2S. Disable the Spanning Tree Protocol (STP) function before using. (Check the instruction manual of the ethernet network switch for the setting.)

 ExpEther products have multiple network connection ports. We recommend that you use

all network connection ports in multipath configuration. You can attain the following

performances in a multipath configuration.

・ Improvement of the transfer performance by distributing the network load ・ Redundancy mechanism to continue operation using other ports in case of a problem

on one port

 We recommend that you use a network switch whose delay time (latency) is short.  If you use a switch whose delay time (latency) is long, you may deteriorate the

performance and may not have it normally operated depending on the I/O device

connected.

 We recommend the following to avoid improper connection to network switches

constituting two network systems if you operate ExpEther products in the configuration of

two independent networks.

・ Change the color of cables used for each network system. ・ Attach tags near the connector of the cable to identify the connection source.

Important

When you connect ExpEther products, check if the server to mount the ExpEther board (40G), OS, devices to mount the ExpEther IO Expansion Unit (40G), and the driver are compatible with the hot plug feature of the PCI

Express slot.

If they are not compatible with the hot plug of the PCI Express slot, they could cause unexpected malfunctions by pulling and inserting the QSPF+ port during

operation.

Page 42

3.7.1 1:1 connection without using a network switch

Use one or two optical fiber cables or DA cables to directly connect the ExpEther board (40G) mounted on the server and the ExpEther IO Expansion Unit (40G).

Important

When you connect the cables directly, connect the QSFP+ port-1 of the ExpEther board (40G) directly to the QSFP+ port-1 of the ExpEther IO Expansion Unit (40G), and connect the QSFP+ port-2 of the ExpEther board (40G) directly to the QSFP+ port-2 of the ExpEther IO Expansion Unit (40G).

You cannot connect QSFP+ port of the ExpEther board (40G) to a different port

of the ExpEther IO Expansion Unit (40G).

Important

When you connect the ExpEther board (40G) directly to the ExpEther IO Expansion Unit (40G), set the Group Id to the same value from 1 to 15. If you set the Group Id to 0, you cannot connect the ExpEther board (40G) to the

ExpEther IO Expansion Unit (40G).

Refer to "3.5 Installing the ExpEther IO Expansion Unit (40G) and the option

card" for the detail.

Tips

When you connect two ExpEther boards (40G) directly to one ExpEther IO

Expansion Unit (40G), connect the QSFP+ port-1 of the second ExpEther board (40G) directly to the QSFP+ port-3 of the ExpEther IO Expansion Unit (40G) and connect the QSFP+ port-2 of the second ExpEther board (40G) directly to the QSFP+ port-4 of the ExpEther IO Expansion Unit (40G).

Important

When you connect two ExpEther boards (40G) directly to the ExpEther IO Expansion Unit (40G), set different Group IDs to two ExpEther boards (40G)

from 1 to 15. If you set same Group ID, the unit will not operate normally.

Important

When you connect two ExpEther boards (40G) directly to one ExpEther IO Expansion Unit (40G), you can only use PCIe slot 1/2 of the ExpEther board (40G) connected to the QSFP+ port 1/2 of the ExpEther IO Expansion Unit (40G). You cannot connect PCIe slot 3/4. On the contrary, you can only use PCIe slot 3/4 of the ExpEther board (40G) connected to the QSFP+ port 3/4 of

the ExpEther IO Expansion Unit (40G). You cannot connect PCIe slot 1/2.

Tips

At startup of the server, if the ExpEther board detects the ExpEther IO Expansion Unit that has the same Group ID as this board itself, it connects the I/O device to the server. The connected I/O device is recognized, by the OS, as

a PCI device.

If there are two or more ExpEther IO Expansion Units that have the same Group ID, the ExpEther board connects the devices based on the order in which it detected the Expansion Units. Therefore, the order of the PCI devices recognized by the OS may vary, depending on the order in which ExpEther

board detected the Expansion Units.

QSFP+ port-1

QSFP+ port-2

QSFP+ port-1

QSFP+ port-2

Page 43

3.7.2 Connection using an ethernet network switch (one ExpEther board (40G))

・ Connect the ExpEther board (40G) mounted on the sever and an ethernet network, the ExpEther

IO Unit (40G) and an ethernet network switch using the optical fiber cable or the DA cable.

・ Use an ethernet network switch compliant with QSFP+ to connect the ExpEther board (40G) and

the ExpEther IO Expansion Unit (40G).

・ You can connect up to 4 PCIe slots of the ExpEther IO Expansion Unit (40G) concurrently with

one ExpEther board (40G). You can connect more than 4 PCIe slots with the same Group ID in the same network environment. However, the fifth and subsequent PCIe slots will not be connected to the ExpEther board (40G).

・ When you configure two independent networks using multiple network switches or VLAN,

configure them so that the QSFP+ port-1 of the ExpEther board (40G) and the QSFP+ port-1 or port-3 of the ExpEther IO Expansion Unit (40G), and the QSFP+ port-2 of the ExpEther board (40G) and the QSFP+ port-2 or port-4 of the ExpEther IO Expansion Unit (40G) will belong to the same network. If you connect them to different networks, you cannot connect the ExpEther board (40G) and the ExpEther IO Expansion Unit (40G).

Tips

We recommend that you connect all QSFP+ ports of the ExpEther IO Expansion

Unit (40G) to the ethernet network switch.

Tips

Set the Group ID of the ExpEther board (40G) and the ExpEther IO Expansion Unit (40G) connected to the same value (1 to 15). Or, set the group ID setting switch to “0” and have ExpEther Manager connect the ExpEther board (40G)

and the ExpEther IO Expansion Unit (40G).

Ethernet Network Switch

Group ID = 1

Server for using

ExpEther Manager

Group ID = 1

Page 44

Tips

a PCI device.

board detected the Expansion Units.

If you have installed ExpEther Manager, it specifies for the ExpEther board, the order of detecting the ExpEther I/O Expansion Units; thus, the I/O device can be

connected to the server in the same order each time the server starts up.

Tips

The above order (specified by ExpEther Manager) of detecting the ExpEther IO Expansion Units (40G) is recorded in the nonvolatile memory of the ExpEther board (40G). Up to four I/O device slots can be connected to the ExpEther board (40G). Therefore, to connect a new I/O device to an ExpEther board (40G) to which four I/O device has been connected, use the following procedure

for connection:

1. Disconnect the I/O device to which the connection is to be suspended. Then

start up the server.

2. Execute CLI subcommand del_iomac to delete the target I/O device

information.

3. Connect the new I/O device to the ExpEther board (40G).

Page 45

3.7.3 Connection using an ethernet network switch (two or more ExpEther boards (40G))

・ When you connect multiple ExpEther boards (40G) in the same network environment, set a

unique Group ID for each ExpEther board (40G) and set the Group ID of the ExpEther IO Expansion Unit (40G) according to the destination ExpEther board (40G).

・ Connect the ExpEther board (40G) mounted on the sever and an ethernet network switch, the

ExpEther IO Unit (40G) and an ethernet network switch using the optical fiber cable or the DA cable.

・ Use an ethernet network switch compliant with QSFP+ to connect the ExpEther board (40G) and

the ExpEther IO Expansion Unit (40G).

・ You can connect up to 4 PCIe slots of the ExpEther IO Expansion Unit (40G) concurrently with

・ When you configure two independent networks using multiple network switches or VLAN,

Group ID = 1

Group ID = 2

Group ID = 5

Group ID = 2

Ethernet network switch

Server for using

ExpEther Manager

Page 46

Tips

We recommend that you connect all QSFP+ ports of the ExpEther IO Expansion

Unit (40G) to the ethernet network switch.

Tips

Set the Group ID of the ExpEther board (40G) and the ExpEther IO Expansion Unit (40G) connected to the same value (1 to 15) with the Group ID setting switch. Or, set the group ID setting switch to “0” and have ExpEther Manager

connect the ExpEther board (40G) and the ExpEther IO Expansion Unit (40G).

Tips

a PCI device.

board detected the Expansion Units.

If you have installed ExpEther Manager, it specifies for the ExpEther board, the order of detecting the ExpEther I/O Expansion Units; thus, the I/O device can be

connected to the server in the same order each time the server starts up.

Tips

for connection:

1. Disconnect the I/O device to which the connection is to be suspended. Then

start up the server.

2. Execute CLI subcommand del_iomac to delete the target I/O device

information.

3. Connect the new I/O device to the ExpEther board (40G).

Page 47

Chapter 4. Procedure for Using the Product

This chapter describes the basic usage of the ExpEther unit.

4.1 ExpEther Manager Software

You can use the ExpEther board (40G) and the ExpEther IO Expansion Unit (40G) as stand-alone units. However, you can also set connection of ExpEther products and check the operating status by using ExpEther Manager.

We provide ExpEther Manager (EEM) as the library (SDK) to operate ExpEther products. Using this library allows you to operate ExpEther products from the management software you have prepared.

(1) Library provided by ExpEther Manager

The library provided by ExpEther Manager is shown below.

ExpEther Manager supports three types of interfaces. Examples of using each interface are shown below.

● REST API

- CLI(command line interface)

- Via Web browser

- Cooperation with OpenStack

● Java API

- GUI (graphic user interface))

● C/C++ API ― User’s own management software

Page 48

(2) Functions provided by ExpEther Manager

ExpEther Manager provides the following functions.

● Operating in the configuration of 16 or more ExpEther devices on the same network

● Monitoring the operating status of ExpEther devices

● Controlling the power supply of ExpEther devices (remote power ON/OFF)

● Exchanging the ExpEther board (40G) and ExpEther IO Expansion Unit (40G)

● Restarting ExpEther devices (remote resetting)

(3) Operating environment of ExpEther Manager

ExpEther Manager (EEM) operates on the management devices connected on the same network to which ExpEther devices are connected as shown below.

The operating environment of ExpEther Manager is shown below.

● Windows environment

- Windows 7 Professional 64-bit(x64) Edition

- Windows 7 Professional 32-bit(x32) Edition

- Windows Server 2012 R2

● Linux environment

- Red Hat Enterprise Linux 6.5 (64bit) or later

Page 49

4.1.1 Installing ExpEther manager (1) Files used for installation

eem /

Windows /

eem-win-x86.zip

Archive for Windows (32-bit) EEM associated files

eem-win-x64.zip

Archive for Windows (64-bit) EEM associated files

eem_setup.bat

Registry file to set event logs used to install Windows (32bit/64-bit) EEM

eem_unsetup.bat

Used to uninstall Windows (32-bit/64-bit) EEM and clear the registry file

Linux /

eem-linux-x64.tar.gz

Archive for Linux (64-bit) EEM associated files

Contact your sales representative for the installation media of ExpEther Manager.

(2) For Windows

1. Installing JDK Get the latest JDK from the following site and install it.

http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html

Hereinafter, the installation destination of JDK 7 is described as “<JDK path>”. For example, if you install JDK7-update75 to the default folder, “C:¥Program Files¥Java¥jdk1.7.0_75” is described as “<JDK path>”.

Important

 Be sure to install 64-bit JDK on 64-bit version Windows.  Even if you specify 32-bit version JDK, you cannot start EEM.

2. Installing WinPcap Get the installer of WinPcap from the following site and install it.

https://www.winpcap.org/install/

3. Installing a Visual C++ redistributable package of Visual Studio 2013

Get a Visual C++ redistributable package of Visual Studio 2013 from the following site and

install it.

https://www.microsoft.com/en-us/download/details.aspx?id=40784

4. Installing Python This step is not required if “CLI commands” are not used.

Get the latest version of Python 2.7x from the following site and install it.

https://www.python.org/downloads/windows/

Hereinafter, the installation path of Python is described as “<Python path>”.

Page 50

5. Placing ExpEther Manager files

Unpack zip files corresponding to the OS architecture of the target server in an arbitrary

folder. For 32-bit OS： eem-win-x86.zip

For 64-bit OS： eem-win-x64.zip Hereinafter, the path to extract files in this step is described as “<EEM path>”.

For example, if you extract files to “C:¥Program Files¥NEC”, “C:¥Program Files¥NEC¥eem” is

described as “<EEM path>”.

6. Editing the config file First, execute the following command on a command prompt.

> route print Pay attention to a part of “Interface list” among the output result. A part of output example：

=======================================================================

==== Interface list

16...a0 36 9f 32 91 5e ......Intel(R) Ethernet Server Adapter I350-T2 #2

15...a0 36 9f 32 91 5f ......Intel(R) Ethernet Server Adapter I350-T2

13...00 25 5c e2 af f9 ......Intel(R) 82574L Gigabit Network Connection #2

11...00 25 5c e2 af f8 ......Intel(R) 82574L Gigabit Network Connection

1...........................Software Loopback Interface 1

12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter

14...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2

17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3

18...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #4

=======================================================================

==== The leftmost number of the output is “Interface number”.

*16, 15, 13, 11, 1, 12, 14, 17 and 18 in this output example

Identify the NIC interface number connected to the ExpEther board from the MAC address

and the NIC name outputted on each line and describe it in the following file. <EEM path>¥conf¥eem.conf Example of setting：

ether_port_ifindex=15, 16

7. Setting the event log of ExpEther Manager

Execute the following file by [Execute as an administrator] and set the registry key to output

the event log of EEM. eem_setup.bat * Describe “<EEM path>”in EEM_INSTALL_PATH described in eem_setup.bat.

Example) When <EEM path> is “C:¥Program Files¥NEC¥EEM” set EEM_INSTALL_PATH=C:¥Program Files¥NEC¥EEM

* The event log of EEM is displayed as follows; [Event viewer (local)] - [Windows log] Application of the event viewer

Page 51

8. Setting environment variables

Add paths to the following system environment variables.

Environment variable

name

Path to be added

JAVA_HOME

CATALINA_HOME

<EEM path>¥tomcat

PATH

%JAVA_HOME%¥bin <Python path>*1

*1 This step is not required if

“CLI commands” are not used.

* If you do not find environment variables, add them.

Tips

You can set system environment variables in the window displayed in the

following steps for Windows Server 2012 R2.

· Start the control panel.

· Select “System and security” from items of the control panel.

· Select “System” from items of the system and security.

· Select “Detail setting of the system” from the left side menu of the system.

· Select “Environment variables” shown in the “Detail setting” of the system property.

(3) For Linux

1. Installing OpenJDK7 Install OpenJDK 7 on the Linux server.

Example of installation on yum： yum install java-1.7.0-openjdk-devel

2. Installing Python This step is not required if “CLI commands” are not used.

Install the latest version of Python on the Linux server. Example of installation on yum：

yum install python

3. Placing ExpEther Manager files Unpack the following compressed file in an arbitrary directory.

eem-linux-x64.tar.gz Hereinafter, the path to extract files in this step is described as “<EEM path>”.

For example, if you extract files to “/opt/nec”, “/opt/nec/eem” is described as “<EEM path>.

4. Editing the config file Edit the following file and specify the NIC device name used by EEM.

<EEM path>/conf/eem.conf Example of setting：

ether_port=eth2,eth3

Page 52

5. Setting environment variables

Add paths to the following environment variables using the login shell.

Environment variable

name

Path to be added

CATALINA_HOME

<EEM path>/tomcat

LD_LIBRARY_PATH

<EEM path>/lib

Example of setting： export CATALINA_HOME=/opt/nec/eem/tomcat

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/nec/eem/lib * You need to execute the login shell by logging in again before starting EEM.

(4) procedure to change the configuration

1. Ports used by ExpEther Manager EEM uses the following ports in default setting.

Port No.

Use

30500

Used as a receiving point of REST API of EEM (for

HTTP communication)

30501

Used as a receiving point of REST API of EEM (for

HTTPS communication)

* Only when you enable HTTPS in the procedure

described later

30502

For shutdown of Tomcat

2. Changing HTTP ports Fix the following file to change HTTP ports. This step is not required if you do not change the port.

<EEM path>/tomcat/conf/server.xml Example of setting：

* Fix the underlined part to a new port number. You need to fix the following file to use CLI commands described later. <EEM path>/eemcli/eemcli.conf Example of setting：

## Port number of EEM REST service. ## (default: 30500) server_port=30500

* Fix the underlined part to a new port number.

Page 53

3. Enabling HTTPS

This step is not required if you do not use HTTPS. HTTPS is disabled in the initial status.

This step allows you to enable HTTPS. First, execute the following command to create a key store.

# keytool -genkeypair -dname "cn=<Host name or IP address>" -alias tomcat -keyalg RSA keystore <EEM path>/tomcat/.keystore

* Enter any password when you are required.

Next, fix the following file. <EEM path>/tomcat/conf/server.xml

Before change： <!—

-->

After change： <Connector port="30501" protocol="org.apache.coyote.http11.Http11Protocol"

maxThreads="150" SSLEnabled="true" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" keystoreFile="<EEM path>/tomcat/.keystore" keystorePass="tomcat" />

* Change the port number of HTTPS as required. Comment out the <Connector> tag shown in “Changing HTTP ports” by enclosing with “<!--”

and “-->” to enable HTTPS and disable HTTP at the same time. Example of setting：

<!- <Connector port="30500" protocol="HTTP/1.1" maxThreads="10" connectionTimeout="5000" redirectPort="30501" />

-->

4. Setting a firewall Set a firewall to get through HTTP and HTTPS ports as required.

5. Setting Basic authentication This step is not required if Basic authentyication is disabled.

Basic authentication of REST API service is disabled in the default seting. This step allows you to enable Basic authentication.

Modify the following file to enable Basic authentication. <EEM path>/tomcat/webapp/eem/WEB-INF/web.xml

Page 54

Before change：

<!— <security-constraint> <web-resource-collection> <web-resource-name>ExpEtherManagerRestResources</web-resource-name> <url-pattern>/*</url-pattern> </web-resource-collection> <auth-constraint> <role-name>eem-rest</role-name> </auth-constraint> </security-constraint>

<login-config> <auth-method>BASIC</auth-method> <realm-name>ExpEtherManagerRestService</realm-name> </login-config>

<security-role> <role-name>eem-rest</role-name> </security-role>

-->

After change：

<login-config> <auth-method>BASIC</auth-method> <realm-name>ExpEtherManagerRestService</realm-name> </login-config>

<security-role> <role-name>eem-rest</role-name> </security-role>

-->

Next, modify the following file to change the user name and the password used for Basi

authentication.

Note that the user name and the password are set to “admin” and “eemeem” in the default setting.。

<EEM path>/tomcat/conf/tomcat-users.xml Example of setting：

<role rolename="eem-rest"/> <user username="admin" password="eemeem" roles="eem-rest"/>

Page 55

4.1.2 Uninstalling ExpEther manger (1) For Windows

1. Stopping ExpEther Manage

Stop EEM before uninstalling EEM. Refer to "4.1.3 Procedure to start and stop ExpEther

Manager” for stopping EEM.

2. Deleting ExpEther Manager Delete the eem directory (<EEM path>) extracted by “4.1.1 Installing ExpEther manager”. Uninstall the package installed by “4.1.1 Installing ExpEther manager” as required.

3. Clearing the event log setting of ExpEther Manager

Execute the following file as an administrator ([Execute as an administrator]) to clear the

registry key set by “4.1.1 Installing ExpEther manager”. eem_unsetup.bat

4. Changing the configuration Set environment variables and a firewall as required.

(2) For Linux

1. Stopping ExpEther Manager

Stop EEM before uninstalling EEM. Refer to "4.1.3 Procedure to start and stop ExpEther

Manager” for stopping EEM.

3. Changing the configuration Set environment variables and a firewall as required.

4.1.3 Procedure to start and stop ExpEther Manager (1) For Windows

[Starting procedure]

1. Starting a command prompt in an administrator mode

Select [All programs] - [Accessory] - [Command prompt] of the [Start] menu and right-click it to start the command prompt in the administrator mode.

2. Executing a start script

Execute the following script. ExpEther Manager is started and the Tomcat window is

displayed. <EEM path>¥tomcat¥bin¥startup.bat

[Stopping procedure]

1. You can stop the manager by closing the Tomcat window displayed by “4.1.3 (1) For Windows”.

Page 56

(2) For Linux

[Starting procedure]

1. Executing a start script

Execute the following script. <EEM path>/tomcat/bin/startup.sh

[Stopping procedure]

1. Executing a stop script Execute the following script. <EEM path>/tomcat/bin/shutdown.sh

4.1.4 CLI (command line)

CLI Commands to call Rest API of ExpEther Manager are supplied. You can check the status of ExpEther products on the ExpEther network by executing the CLI.

[Procedure to execute the CLI] <EEM path>/eemcli/eemcli.py

(1) Installation

1. The CLI is extracted concurrently when ExpEther Manager is placed on your server.

2. Set the IP address of the server on which you have installed ExpEther Manager to

“server_ip” of the configuration file of the CLI. server_ip=<IP Address>

The default of server_ip is “127.0.0.1”. You do not need to specify server_ip if you use CLI on

the same server as that on which you have installed ExpEther Manager.

3. Operation check a) Start ExpEther Manager.

b) Execute the following command and check that you can get the API version.

$ python eemcli.py get_apiver version_number: v1.0

[Reference] The CLI operates in the environment of Python 2.x (Python 3.x is not supported). However, it will be operable by executing the following command to install the package in the environment such as PHEL6.5 where Python 2.6.x has been installed.

yum install -y python-argparse

Page 57

(2) Configuration file

Shown below is the description of items of the configuration file referred to by the CLI.

Attribute name

Default

Description

server_ip

127.0.0.1

Specify the IP address of the server on which you have installed EEM.

server_port

8080

Specify the port number of the REST service.

timeout

Specify timeout time (in seconds) of the HTTP session.

auth

Specify the type of authentication. 0: No use 1: Use Basic authentication to specify your user name and password in the character string encoded by Base64. 2: Use Basic authentication to specify your user name and password in plain text.

encoded_id

None

Specify a character string of your user name and password concatenated by “:” and encoded by Base64 for auth=1.

user

None

Specify a user name in plain text for auth=2.

password

None

Specify a password in plain text for auth=2.

ssl

false

When this is true, HTTPS communication is enabled.

cert

None

Specify the path of the server certificate for ssl=true. Refer to “Notes” for the server certificate.

print_json

false

The result of execution is displayed in JSON format if this is true.

validation

true

The command line argument is checked if this is true.

[Notes] You can read the configuration file stored in any folder by specifying an option “-c CONFIG, --

config CONFIG” when you execute a command.  An error is generated when the configuration file is not found in the path specified by the

option.

 The configuration file stored in the same folder as that of eemcli.py is read when the option is

omitted.

 When no configuration file is found, all set items are defaulted.

(3) Log output

 The result of executing the CLI is output to the standard output and the standard error output.  You can output the debug log by specifying “-v, --verbose” option when you execute a

command.

(4) End status

 “0” is returned for a normal end. A positive integer is returned for an abnormal end.

(5) Format

eemcli.py [-h] [-v] [-c CONFIG] subcommand ...

 -h, --help: Output the help message and terminate.  -v, --verbose: Output the debug log.  -c CONFIG, --config CONFIG: Read the config file specified in CONFIG.

Page 58

(6) Subcommand list

 The list of subcommands provided by the CLI is shown in the table below.

Subcommand

description

dumpreg

Dump registers of the ExpEther engine.

readreg

Read the data of registers of the ExpEther engine.

writereg

Write the data in registers of the ExpEther engine.

dumpeeprom

Dump EEPROM mounted on the ExpEther unit.

readrom

Read the data of EEPROM mounted on the ExpEther unit.

writerom

Write the data to EEPROM mounted on the ExpEther unit.

get

Get the device information managed by ExpEther Manager.

delete

Delete the device information managed by ExpEther Manager.

audit

Update the device information managed by ExpEther Manager.

init

Initialize the hardware setting in the ExpEther board.

replace

Replace the ExpEther unit.

perst

Reset the ExpEther unit.

sysrst

Reset the ExpEther I./O Expansion unit (10G v2.0). Note：This command is intended for a specific unit.

send_rst

Reset the EE unit. Also reset the ExpEther Client, the ExpEther I/O Expansion unit connected to the specified EE board and the board

itself.

set_powstat

Change the power status of the ExpEther unit. Power status change: ON/OFF

get_led

Get the lighting status of UID LED of the ExpEther unit.

set_led

Change the lighting status of UID LED of the ExpEther unit.

get_rotary

Get the rotary switch status by which the group ID of the ExpEther

unit is set.

set_manage

Update the management information (management status/ monitoring status) of ExpEther Manager.

set_gid

Update the group ID set in the ExpEther unit.

del_gid

Delete the group ID set in the ExpEther unit. Note：The group ID of the unit is defaulted after it is deleted.

set_vlantagging

Update the VLAN tag conversion mode of the ExpEther unit (1G and

40G). Note： This command is intended for ExpEther units (1G and 40G).

set_multmac

Update multiple MAC address modes of the ExpEther unit (40G). Note：This command is intended for ExpEther units (40G).

set_encrypt

Update the encrypting mode of the ExpEther unit (40G). Note：This command is intended for ExpEther units (40G).

set_compati

Update the compatible mode between 1G and 10G version units of

the ExpEther unit (40G). Note：This command is intended for ExpEther units (40G).

del_compati

Delete the compatible mode between 1G and 10G version units of

the ExpEther unit (40G). Note：This command is intended for ExpEther units (40G).

set_powinh

Update the power OFF inhibition status of ExpEther boards (1G and

10G). Note：This command is intended for ExpEther units (1G and 40G).

Page 59

Subcommand

description

set_hosinfo

Update the host information set in the ExpEther board.

set_maxio

Update the maximum IO number connectable to the ExpEther

board(10G).

Note：This command is intended for ExpEther units (10G).

set_pcieinfo

Update the PCle device information mounted on the ExpEther IO

Expansion Unit (1G and 10G). Note：This command is intended for ExpEther units (1G and 10G).

set_powlink

Update the power interlocking status of ExpEther clients and IO

Expansion units (1G and 10G).

Note：This command is intended for ExpEther client and IO

Expansion unit units (1G and 10G).

del_iomac

Delete the MAC address information of ExpEther clients and IO Expansion units allocated to the downstream port of the ExpEther

board.

get_groups

Get the list of the group ID information.

get_apiver

Get the version information of API provided by ExpEther Manager.

dump_stats

Output the statistic information kept by ExpEther Manager to the log

file.

unlock_eeprom

Unlock EEPROM access forcibly.

(7) Command reference

dumpreg

Dump the data of registers of the ExpEther engine.

eemcli.py dumpreg --id ID [--address ADDRESS] [--length LENGTH]

 --id ID, -i ID: Specify the EE card ID.  --address ADDRESS, -a ADDRESS: Specify the start address (0x0-0xfffc, multiple of 4).

(Default: 0x0)

 --length LENGTH, -l LENGTH: Specify the data length (1-24576) to be gotten. (Default: 4)

o The specified value is rounded to the multiple of 4. o If the value of “ADDRESS + LENGTH” exceeds 0xfffc, the data up to 0xfffc is returned.

readreg

Read the data of registers of the ExpEther engine.

eemcli.py readreg --id ID --address ADDRESS

 --id ID, -i ID: Specify the EE card ID.  --address ADDRESS, -a ADDRESS: Specify the address of the register (0x0-0xfffc, multiple

of 4).

writereg

Write the data of registers of the ExpEther engine.

eemcli.py writereg --id ID --address ADDRESS --data DATA [--verify VERIFY]

 --id ID, -i ID: Specify the EE card ID.  --address ADDRESS, -a ADDRESS: Specify the address of the register (0x0-0xfffc, multiple

of 4).

 --data DATA, -d DATA: Specify the data of the register (0x0-0xffffffff).  --verify VERIFY, -V VERIFY: Specify “enabled” or “disabled”. (Default: enabled)

o If you specify “enabled”, you have the data read and verified after writing.

Page 60

dumprom

Dump EEPROM mounted on the ExpEther unit.

eemcli.py dumprom --id ID [--address ADDRESS] [--length LENGTH]

 --id ID, -i ID: Specify the EE card ID.  --address ADDRESS, -a ADDRESS: Specify the start address. (0x0-0x7fc, multiple of 4)

(Default: 0x0)

 --length LENGTH, -l LENGTH: Specify the data length (1-2048) to be taken. (Default: 4)

o The specified value is rounded out to a multiple of 4. o If the value of ADDRESS plus LENGTH exceeds “0x7fc”, the data up to “0x7fc” will be

returned.

readrom

Read the data of EEPROM mounted on the ExpEther unit.

eemcli.py readrom --id ID --address ADDRESS

 --id ID, -i ID: Specify the EE card ID.  --address ADDRESS, -a ADDRESS: Specify the EEPROM address (0x0-0x7fc, multiple of

4).

writerom

Write the data to EEPROM mounted on the ExpEther unit.

eemcli.py writerom --id ID --address ADDRESS --data DATA [--verify VERIFY]

 --id ID, -i ID: Specify the EE card ID.  --address ADDRESS, -a ADDRESS: Specify the EEPROM address (0x0-0x7fc, multiple of

4).

 --data DATA, -d DATA: Specify the data of EEPROM (0x0-0xffffffff).  --verify VERIFY, -V VERIFY: Specify “enabled” or “disabled”. (Default: enabled)

o If you specify “enabled”, you have the data read and verified after writing.

get

Get the device information managed by ExpEther Manager.

* Refer to the tail end in this section for examples of output and display of the get command.

eemcli.py get {--id ID | --list | --all} [--status STATUS] [--time TIME] [--gid GID]

 Specify either “--id/-I” or “--list/-l” or “--all/-a”.

o If you specify “--id/-I”, you have the single device information displayed. o If you specify “--list/-I”, you have the list of all EE card IDs. o If you specify “--all/-a”, you have the all devices information displayed.

 --id ID, -i ID: Specify the EE card ID.  Specify “--status STATUS” or “-s STATUS: eesv or eeio”.

o You have only the device information with the specified EE card status. o This is enabled only when you specify “--list/-l” or ”--all/-a”. If you specify “--id/-I”, this is

ignored.

 --time TIME, -t TIME: Specify the update time of the device information (elapsed time from

1970/1/1 00:00:00 000 UTC in milliseconds)

o Only the device information with the update time larger than the specified value will be

displayed.

o This is enabled only when you specify “--list/-l” or ”--all/-a”. If you specify “--id/-I”, this is

ignored.

 --gid GID, -g GID: Specify the group ID (1-4094).

o Only the device information with the specified group ID will be displayed. o This is enabled only when you specify “--list/-l” or ”--all/-a”. If you specify “--id/-I”, this is

ignored.

Page 61

delete

Delete the device information managed by ExpEther Manager.

eemcli.py delete --id ID

 --id ID, -i ID: Specify the EE card ID.  --force STATE, -f STATE: Specify “enabled” or “disabled”. (default: disabled)

o If you specify “disabled”, the command generates an error if the target ExpEther unit is

connected.

o If you specify “enabled”, the device information is deleted even if the target ExpEther unit

is connected.

audit

Update the device information managed by ExpEther Manager.

eemcli.py audit --id ID

 --id ID, -i ID: Specify the EE card ID.

init

Initialize the hardware setting in the ExpEther unit.

eemcli.py init --id ID

 --id ID, -i ID: Specify the EE card ID.

The following information is initialized.

 VLAN ID setting  IO MAC address setting  VLAN tag conversion disabled  Multiple MAC address mode setting (Only ExpEther unit (40G))  Encrypting mode setting (Only ExpEther unit (40G))  Encryption key (Only 40G)  1/10G compatible mode setting (Only ExpEther board (40G))  Power OFF inhibition setting (Only ExpEther unit (1G/10G))  Host information (serial number, model name) (Only ExpEther board)

Important

If you attempt to initialize an ExpEther device while the OS is running, this may affect operation of the OS because the connected I/O device becomes unable to be recognized. Shut down the OS and start up the BIOS Setup screen before

performing this.

Important

Check the hardware setting in the ExpEther unit and set the value if necessary

by using the CLI subcommand and the ExpEtherConfig tool.

 VLAN tag conversion disabling setting (using the set_vlantagging

command)

 Multiple MAC address mode setting (using the set_multimac

command)

 Encrypting mode setting (using the set_encrypt command)  1/10G compatible mode setting (using the set_compati command)  Power OFF inhibition setting (using the set_powinh command)  Host information (using the ExEtherConfig tool)

replace

Replace the ExpEther unit.

eemcli.py replace --id ID --oldid OLDID

 --id ID, -i ID: Specify theEE card ID after replacement.  --oldid OLDID, -o OLDID: Specify the EE card ID before replacement.

Page 62

Tips

This command updates the hardware setting of the EE card specified by “id” with the EE card setting specified by “oldid”. The following information will be

updated.

Tips

The command generates an error if the status, the type and the version of the EE card specified by “oldid” are different from that specified by “id” or if the

management state of the EE card specified by “oldid” is enabled.

You can check the status, the type, the version and the management state of the

EE card by executing the subcommand “get”.

You can change the management state of the EE card by executing the

subcommand “set_manage”.

perst

reset the ExpEther unit.

eemcli.py perst --id ID

 --id ID, -i ID: Specify the EE card ID.

Important

If you attempt to reset an ExpEther device while the OS is running, this may affect operation of the OS. Thus, when resetting the device, pay attention to the

OS operating state.

sysrst

Reset the ExpEther I./O Expansion unit (10G v2.0).

eemcli.py sysrst --id ID

 --id ID, -i ID: Specify the EE card ID.

Important

If you attempt to reset an ExpEther device while the OS is running, this may affect operation of the OS. Thus, when resetting the device, pay attention to the

OS operating state.

send_rst

Reset the EE unit. Also reset the ExpEther Client, the ExpEther I/O Expansion unit connected to the specified EE board and the board itself.

eemcli.py send_rst --id ID

 --id ID, -i ID: Specify the EE card ID.

Important

If you attempt to reset an ExpEther device while the OS is running, this may affect operation of the OS. Thus, when resetting the device, pay attention to the

OS operating state.

set_powstat

Change over the power status of the ExpEther unit.

eemcli.py set_powstat --id ID

Page 63

 --id ID, -i ID: Specify the EE card ID.

Tips

This command is valid only for 1G and 10G EE cards.

Important

If you attempt to change the power state while the OS is running, this may affect operation of the OS. Thus, when resetting the device, pay attention to the OS

operating state.

get_led

Get the lighting status of UID LED of the ExpEther unit.

eemcli.py get_led --id ID

 --id ID, -i ID: Specify the EE card ID.

set_led

Update the lighting status of UID LED of the ExpEther unit.

eemcli.py set_led --id ID --state STATE

 --id ID, -i ID: Specify the EE card ID.  --state STATE, -s STATE: Specify “on” or “off”.

get_rotary

Get the status of the rotary switch to set the group ID of the ExpEther unit.

eemcli.py get_rotary --id ID

 --id ID, -i ID: Specify the EE card ID.

set_manage

Update the management information (management status/monitoring status) of ExpEther Manager.

eemcli.py set_manage --id ID [--admin ADMIN] [--monitor MONITOR] [--time TIME]

 --id ID, -i ID: Specify the EE card ID.  --admin ADMIN, -a ADMIN: Specify “enabled” or “disabled”.  --monitor MONITOR, -m MONITOR: Specify “enabled” or “disabled”.  --time TIME, -t TIME: Specify the update time of the device information (elapsed time from

1970/1/1 00:00:00 000 UTC in milliseconds).

o Specify “--time/--t” to verify whether the specified update time is equal to that of the

device information.

set_gid

Update the group ID set for the ExpEther unit.

eemcli.py set_gid --id ID [--gid GID] [--time TIME]

 --id ID, -i ID: Specify the EE card ID.  --gid GID, -g GID: Specify the group ID (16-4092). If omitted, EEM generates a group ID.  --time TIME, -t TIME: Specify the update time of the device information (elapsed time from

1970/1/1 00:00:00 000 UTC in milliseconds).

o Specify “--time/--t” to verify whether the specified update time is equal to that of the

device information.

Page 64

Tip

To change the group ID of the IO expansion unit to another group ID, initialize

the group ID and update it. You can initialize the group ID by executing the subcommand “del_gid”.

If there is no ExpEther board that has the specified group ID to be set for the IO

expansion unit, the command generates an error.

Important

If you instruct the ExpEther board to change the Group ID, the board will reset itself because it reflects the new ID. This may affect operation of the OS. Thus,

when performing this, pay attention to the OS operating state. After changing the Group ID, need to restart the server.

Important

If you instruct the ExpEther I/O Expansion Unit to change the Group ID, the I/O device will be disconnected from the currently connected ExpEther board. This may affect operation of the OS. Thus, when performing this, pay attention to the

OS operating state.

del_gid

Delete the group ID set for the ExpEther unit.

eemcli.py del_gid --id ID [--time TIME]

 --id ID, -i ID: Specify the EE card ID.  --time TIME, -t TIME: Specify the update time of the device information (elapsed time from

1970/1/1 00:00:00 000 UTC in milliseconds).

o Specify “--time/--t” to verify whether the specified update time is equal to that of the

device information.

Tip

The group ID of the ExpEther board is initialized to 4094 and that of the IO

expansion unit is initialized to 4093 by executing this command.

Important

If you instruct the ExpEther board to change the Group ID, the board will reset itself because it reflects the new ID. This may affect operation of the OS. Thus,

when performing this, pay attention to the OS operating state. After changing the Group ID, need to restart the server.

Important

OS operating state.

set_vlantagging

Update the VLAN tag conversion mode of the ExpEther unit (1G and 40G).

eemcli.py set_vlantagging --id ID --state STATE [--time TIME]

 --id ID, -i ID: Specify the EE card ID.  --state STATE, -s STATE: Specify “enabled” or “disabled”.  --time TIME, -t TIME: Specify the update time of the device information (elapsed time from

1970/1/1 00:00:00 000 UTC in milliseconds).

o Specify “--time/--t” to verify whether the specified update time is equal to that of the

device information.

Important

The setting is reflected after the server restarts. Whenever you change the

setting, restart the server.

set_multimac

Update multiple MAC address modes of the ExpEther unit (40G).

eemcli.py set_multimac --id ID --state STATE [--time TIME]

 --id ID, -i ID: Specify the EE card ID.  --state STATE, -s STATE: Specify “enabled” or “disabled”.

Page 65

 --time TIME, -t TIME: Specify the update time of the device information (elapsed time from

1970/1/1 00:00:00 000 UTC in milliseconds).

o Specify “--time/--t” to verify whether the specified update time is equal to that of the

device information.

Important

If you have changed the multiple MAC address mode from enabled to disabled, connect each QSFP+ port pair(*) to the different networks on the ExpEther

device (40G). (*) Port 1 and port 2, and port 3 and port 4 are paired respectively.

Important

The setting is reflected after the server restarts. If you changed the setting, shut down the server and change the network configuration before starting up the

server.

set_encrypt

Update the encrypting mode of the ExpEther unit (40G).

eemcli.py set_encrypt --id ID --encrypt ENCRYPT [ENCRYPT ...] [--time TIME]

 --id ID, -i ID: Specify the EE card ID.  --encrypt ENCRYPT [ENCRYPT ...], -e ENCRYPT [ENCRYPT ...]: Specify “enabled” or

“disabled”.

o Specify the encrypting mode for downstream port 0-15 if the EE card status is EESV. o Specify the encrypting mode for upstream ports if the EE card status is EEIO. o If the encrypting mode is not specifid, “disabled” value is set.

 --time TIME, -t TIME: Specify the update time of the device information (elapsed time from

1970/1/1 00:00:00 000 UTC in milliseconds).

o Specify “--time/--t” to verify whether the specified update time is equal to that of the

device information.

Important

The setting is reflected after the server restarts. If you changed the setting, shut down the server and change the network configuration before starting up the

server.

set_compati

Update the compatible mode between 1G and 10G version units of the ExpEther unit (40G).

eemcli.py set_compati --id ID --compati COMPATI [COMPATI ...] [--time TIME]

 --id ID, -i ID: Specify the EE card ID.  --compati COMPATI [COMPATI ...], -c COMPATI [COMPATI ...]: Specify “10g” or “40g”.

o Specify the EE card type of EEIO connectable to 40G EESV downstream port 0-7. o If the compatible mode is not specified, “40g” value is set.

 --time TIME, -t TIME: Specify the update time of the device information (elapsed time from

1970/1/1 00:00:00 000 UTC in milliseconds).

o Specify “--time/--t” to verify whether the specified update time is equal to that of the

device information.

Important

The setting is reflected after the server restarts. If you changed the setting, shut down the server and change the network configuration before starting up the

server.

del_compati

Delete the compatible mode between 1G and 10G version units of the ExpEther board (40G).

eemcli.py del_compati --id ID [--time TIME]

 --id ID, -i ID: Specify the EE card ID.  --time TIME, -t TIME: Specify the update time of the device information (elapsed time from

1970/1/1 00:00:00 000 UTC in milliseconds).

o Specify “--time/--t” to verify whether the specified update time is equal to that of the

device information.

Page 66

Important

The setting is reflected after the server restarts. If you changed the setting, shut down the server and change the network configuration before starting up the

server.

set_powinh

Update the power OFF inhibition status of ExpEther boards (1G and 10G).

eemcli.py set_powinh --id ID --state STATE [--time TIME]

1970/1/1 00:00:00 000 UTC in milliseconds).

o Specify “--time/--t” to verify whether the specified update time is equal to that of the

device information.

Important

The setting is reflected after the server restarts. If you changed the setting, shut down the server and change the network configuration before starting up the

server.

set_hostinfo

Update the host information set in the ExpEther board.

eemcli.py set_hostinfo --id ID --serial SERIAL --model MODEL [--time TIME]

 --id ID, -i ID: Specify the EE card ID.  --serial , -s SERIAL: Specify the serial number (up to 32-byte character string).  --model MODEL, -m MODEL: Specify the model (up to 32-byte character string).  --time TIME, -t TIME: Specify the update time of the device information (elapsed time from

1970/1/1 00:00:00 000 UTC in milliseconds).

o Specify “--time/--t” to verify whether the specified update time is equal to that of the

device information.

set_maxio

Update the maximum IO number connectable to the ExpEther board.

eemcli.py set_maxio --id ID --count COUNT [--time TIME]

 --id ID, -i ID: Specify the EE card ID.  --count COUNT, -c COUNT: Specify the maximum number of EEIO (0 to 8 (1G and 10G) ,

or 0 to16 (4G) ).

 --time TIME, -t TIME: Specify the update time of the device information (elapsed time from

1970/1/1 00:00:00 000 UTC in milliseconds).

o Specify “--time/--t” to verify whether the specified update time is equal to that of the

device information.

set_pcieinfo

Update the PCle device information mounted on the ExpEther IO Expansion Unit (1G and 10G).

eemcli.py set_pcieinfo --id ID --vendor VENDOR --device DEVICE --class CLASS [--time TIME]

 --id ID, -i ID: Specify the EE card ID.  --vendor VENDOR, -v VENDOR: Specify the vendor ID (0x0 to 0xffff).  --device DEVICE, -d DEVICE: Specify the device ID (0x0 to 0xffff).  --classcode CLASSCODE, -c CLASSCODE: Specify the class code (0x0 to 0xffffff).  --time TIME, -t TIME: Specify the update time of the device information (elapsed time from

1970/1/1 00:00:00 000 UTC in milliseconds).

o Specify “--time/--t” to verify whether the specified update time is equal to that of the

device information.

Page 67

set_powlink

Update the power interlocking status of ExpEther clients and IO Expansion units (1G and 10G).

eemcli.py set_powlink --id ID --state STATE [--time TIME]

1970/1/1 00:00:00 000 UTC in milliseconds).

o Specify “--time/--t” to verify whether the specified update time is equal to that of the

device information.

Important

The setting is reflected after the server restarts. If you changed the setting, shut down the server and change the network configuration before starting up the

server.

del_iomac

Delete the MAC address information of ExpEther clients and IO Expansion units allocated to the downstream port of the ExpEther board.

eemcli.py del_iomac --id ID --port PORT

 --id ID, -i ID: Specify the EE card ID.  --port PORT, -p PORT: Specify downstream port ID (0 to 7 (1G and 10G), or 0 to 15 (40G))

to unfix EEIO.

Important

Before deleting the target I/O device, disconnect the I/O device from the server.

get_groups

Get the list of the group ID information.

eemcli.py get_groups

get_apiver

Get the API version information provided by ExpEther Manager.

eemcli.py get_apiver

dump_stats

Output the statistic information kept by ExpEther Manager to the log file.

eemcli.py dump_stats [--level LEVEL]

 --level LEVEL, -L LEVEL: Specify the verbose level (Default: 0).

o 0: Dump the statistic information. o 1 or more: Dump the detail statistic information.

unlock_eeprom

Unlock EEPROM access forcibly.

eemcli.py unlock_eeprom --id ID

 --id ID, -i ID: Specify the EE card ID.

Page 68

Description of examples of output and display of the get command

An output example of the ExpEther board (40G) is shown below.

id : 0x8cdf9d81dc1a status : eesv update_time : 1469656583191 admin_status : enabled monitoring_status : enabled notification_status0 : [u'up', u'down'] notification_status1 : [u'up', u'down'] mac_address : 8c:df:9d:81:dc:1a group_id : 50 vlan_tagging : disabled multi_mac_addresses : enabled encryption : [u'disabled', u'disabled', u'disabled', u'disabled',

u'disabled', u'disabled', u'disabled', u'disabled', u'disabled', u'disabled', u'disabled', u'disabled', u'disabled', u'disabled',

u'disabled', u'disabled'] type : 40g uid_switch_status : off power_status : on pcie_link_width : x8 interrupt_vector : 0x0 ee_version : v1.0 device_id : 0x1d revision : 0x0 fpga_version : 0x1400 eeprom_data_version : 0x0 serial_number : model : link_status0 : up link_status1 : up max_eeio_count : 16 eesv_type : nbc compatibility : [u'default'] host_serial_number : host_model : downstream_ports : downstream_port_id : 0 eeio_connection_status: down eeio_mac_address : 8c:df:9d:98:a0:62 downstream_port_id : 1 eeio_connection_status: down eeio_mac_address : 8c:df:9d:98:a0:66 downstream_port_id : 2 eeio_connection_status: down eeio_mac_address : 8c:df:9d:98:a0:64 downstream_port_id : 3 eeio_connection_status: down eeio_mac_address : 8c:df:9d:98:a0:60 downstream_port_id : 4 eeio_connection_status: down eeio_mac_address : 00:00:00:00:00:00 downstream_port_id : 5 eeio_connection_status: down eeio_mac_address : 00:00:00:00:00:00 downstream_port_id : 6 eeio_connection_status: down eeio_mac_address : 00:00:00:00:00:00 downstream_port_id : 7 eeio_connection_status: down eeio_mac_address : 00:00:00:00:00:00 downstream_port_id : 8 eeio_connection_status: down eeio_mac_address : 00:00:00:00:00:00 downstream_port_id : 9 eeio_connection_status: down eeio_mac_address : 00:00:00:00:00:00

Page 69

downstream_port_id : 10 eeio_connection_status: down eeio_mac_address : 00:00:00:00:00:00 downstream_port_id : 11 eeio_connection_status: down eeio_mac_address : 00:00:00:00:00:00 downstream_port_id : 12 eeio_connection_status: down eeio_mac_address : 00:00:00:00:00:00 downstream_port_id : 13 eeio_connection_status: down eeio_mac_address : 00:00:00:00:00:00 downstream_port_id : 14 eeio_connection_status: down eeio_mac_address : 00:00:00:00:00:00 downstream_port_id : 15 eeio_connection_status: down eeio_mac_address : 00:00:00:00:00:00

An output example of the ExpEther IO Expansion Unit (40G) is shown below.

id : 0x8cdf9d98a06c status : eeio update_time : 1469656564830 admin_status : enabled monitoring_status : enabled notification_status0 : [u'up', u'down'] notification_status1 : [u'up', u'down'] mac_address : 8c:df:9d:98:a0:6c group_id : 151 vlan_tagging : disabled multi_mac_addresses : enabled encryption : [u'disabled'] type : 40g uid_switch_status : off power_status : on pcie_link_width : x4 interrupt_vector : 0x0 ee_version : v1.0 device_id : 0x1e revision : 0x0 fpga_version : 0x400 eeprom_data_version : 0x0 serial_number : model : link_status0 : up link_status1 : up path_status0 : down path_status1 : down eesv_connection_status: down eesv_mac_address : 8c:df:9d:81:db:80 pcie_connection_status: up pcie_vendor_id : 0x1c58 pcie_device_id : 0x3 pcie_class_code : 0x10802

Output display by the get command is described below. Type

・Common: Indicates output by both the ExpEther board and the ExpEther IO Expansion Unit.

・EESV: Indicates output for the ExpEther board. ・EEIO: Indicates output for the ExpEther IO Expansion Unit or ExpEther clients.

Parameter name

Parameter

Type

Description

0x000000000000 to

0xffffffffffff

Common

EE card ID Fixed 12 digits hexadecimal

Page 70

Parameter name

Parameter

Type

Description

status

{eesv | eeio}

Common

Type of ExpEther unit

 eesv:

Indicates the ExpEther board.

 eeio:

Indicates the ExpEther I/O Expansion Unit or an ExpEther client.

update_time

0 to 9223372036854775

807

Common

Update time of the device

information

Indicates the elapsed milliseconds from 1970/1/1 00:00:00 000 UTC.

admin_status

{enabled | disabled}

Common

Administration status of the ExpEther

unit

 enabled:

Administration status enabled

 disabled:

Administration status disabled

The default is “enabled”.

You can set the ExpEther unit only when the administration status is enabled.

monitoring_status

{enabled | disabled}

Common

Monitoring status of the ExpEther

unit

 enabled:

Monitoring status enabled

 disabled:

Monitoring status disabled

The default is “enabled”.

notification_status0

{up | down}

Common

Continuity status from the LAN port-0 of the ExpEther unit to the LAN port0 and 1 of the ExpEther Manager

 up:

Periodical notification received

 down:

Notification not received for a certain period

notification_status1

{up | down}

Common

Continuity status from the LAN port-1 of the ExpEther unit to the LAN port0 and 1 of the ExpEther Manager

 up:

Periodical notification received

 down:

Notification not received for a certain period

mac_address

00:00:00:00:00:00 to

FF:FF:FF:FF:FF:FF

Common

MAC address of the ExpEther unit

The MAC address whose least

significant bit is “0” is set for a 40G

version ExpEther unit.

group_id

1 to 4094

Common

Group ID

vlan_tagging

{enabled | disabled}

Common

VLAN tag mode

 enabled:

VLAN tag mode enabled

 disabled:

VLAN tag mode disabled

This parameter is not displayed when the type of the ExpEther unit is 10G.

Page 71

Parameter name

Parameter

Type

Description

multi_mac_address

{enabled | disabled}

Common

Multiple MAC address mode

 enabled:

Set enabled

 disabled:

Set disabled

This parameter is not displayed when the type of the ExpEther unit is

1G/10G.

encryption

{enabled | disabled}

Common

Encryption mode

The encryption mode set to downstream ports 0 to 15 is displayed for an ExpEther board (for

16 ports).

The encryption mode for upstream ports is displayed for the ExpEther

I/O Expansion Unit or ExpEther

clients.  enabled:

Encryption mode enabled

 disabled:

Encryption mode disabled

The encryption mode should be same for communication between the ExpEther board and the ExpEther I/O Expansion Unit or

ExpEther clients.

This parameter is not displayed when the type of the ExpEther unit is

1G/10G.

type

{1g | 10g | 40g}

Common

Type of the ExpEther unit

uid_switch_status

{on | off}

Common

Status of the UID switch of the

ExpEther unit

 on:

UID switch pressed

 off:

UID switch not pressed

power_status

{on | off}

Common

Power status of the ExpEther unit

 on:

Power ON

 off:

Power OFF

pcie_link_width

{x1 | x2 | x4 | x8 |

x16 | x32}

Common

Link width of PCIe For ExpEther boards:

PCle link width between the ExpEther board and the main unit

mounting the board For ExpEther I/O Expansion Units:

Link width of the PCle device

mounted on the PCle slot

interrupt_vector

0x0 to 0xff

Common

Interrupt vector value (Internal administration information of

ExpEther Manager)

ee_version

{v1.0 | v2.0}

Common

EE version。

 v1.0:

ExpEther

 v2.0:

MR-ExpEther

device_id

0x0 to 0xffff

Common

Device Id of the ExpEther unit

revision

0x0 to 0xff

Common

Revision of the ExpEther unit

fpga_version

0x0 to 0xffff

Common

FPGA version of the ExpEther unit

eeprom_data_versi

0x0 to 0xffffff

Common

EEPROM data version of the

ExpEther unit

Page 72

Parameter name

Parameter

Type

Description

serial_number

Up to 32 bytes

character string US-ASCII character (0x20 to 0x7E)

Common

Serial number of the ExpEther unit

model

Up to 32 bytes

character string US-ASCII character (0x20 to 0x7E)

Common

Model name of the ExpEther unit

link_status0

{up | down}

Common

Link status of the LAN port-0 of the ExpEther unit

 up:

Link-up

 down:

Link-down

Always down for 1G/10G version

link_status1

{up | down}

Common

Link status of the LAN port-1 of the ExpEther unit

 up:

Link-up

 down:

Link-down

Always down for 1G/10G version

max_eeio_count

For 1G/10G: 0 to 8 For 40G: 0 to16

EESV

Maximum EEIO

The maximum value of PCle slots on the ExpEther I/O Expansion Unit to

be connected to the ExpEther board

eesv_type

{na | sa | nbc | sbc}

EESV

Type of the ExpEther board

compatibility

{10g | 40g | default}

EESV

1/10GEE compatibility mode

Specify the type of the ExpEther I/O Expansion Unit connectible to Downstream ports 0 to 7 of 40G

version EESV.

 10g:

1G/10G version

 40g:

40G version

 default:

Only 40G EEIO can be connected

to Downstream ports 0 to 7. Only 40G version ExpEther I/O Expansion Unit can be connected to Downstream ports 8 to 15.

This parameter is not displayed if the

type of the ExpEther unit is 1G/10G version.

power_off_inhibition

_status

{enabled | disabled}

EESV

Power OFF inhibition status

 enabled:

Power OFF inhibition enabled  disabled:

Power OFF inhibition disabled

When the power off inhibition of the ExpEther board is enabled, the power status cannot be updated from the ExpEther I/O Expansion Unit or

ExpEther clients. 40G version ExpEther units do not

support power off inhibition. Therefore, this parameter is not displayed if the type of the ExpEther

unit is 40G version.

Page 73

Parameter name

Parameter

Type

Description

host_serial_number

Up to 32 bytes

character string US-ASCII character (0x20 to 0x7E)

EESV

The serial number of the host device on which the ExpEther board is

mounted

host_model

Up to 32 bytes

character string US-ASCII character (0x20 to 0x7E)

EESV

The model name of the host device on which the ExpEther board is

mounted

downstre

am_ports

downstr eam_po

rt_id

0 to 7(1G/10G), 0 to 15(40G)

EESV

Downstream Port ID。 The number of entries of the

Downstream Port information 8 for 1G/10G version and 16 for 40G

version.

eeio_co nnectio n_statu

{up | down}

EESV

Connection status of the ExpEther

I/O Expansion Unit or ExpEther clients

 up:

Connected  down:

Not connected

eeio_m ac_addr

ess

00:00:00:00:00:00 to

FF:FF:FF:FF:FF:FF

EESV

MAC address of the destination ExpEther I/O Expansion Unit or

ExpEther clients

path_status0

{up | down}

EEIO

Path status of the LAN port-0 of the

ExpEther I/O Expansion Unit and

LAN ports of the ExpEther boards

 up:

Path status enabled  down:

Path status disabled

path_status1

{up | down}

EEIO

Path status of the LAN port-1 of the

ExpEther I/O Expansion Unit and

LAN ports of the ExpEther boards

 up:

Path status enabled  down:

Path status disabled

eesv_connection_st

atus

{up | down}

EEIO

Connection status with the ExpEther

board

 up:

Connected with the ExpEther

board  down:

Not connected with the ExpEther

board

eesv_mac_address

00:00:00:00:00:00 to

FF:FF:FF:FF:FF:FF

EEIO

MAC address of the ExpEther board

pcie_connection_st

atus

{up | down}

EEIO

Connection status with PCle devices mounted on the ExpEther I/O Expansion Unit  enabled:

Connected with PCIe devices  disabled:

Not connected with PCIe devices

pcie_vendor_id

0x0 to 0xffff

EEIO

PCle device information mounted on the ExpEther I/O Expansion Unit (vendor ID)

Vendor ID of PCle devices mounted

on the ExpEther I/O Expansion Unit

Page 74

Parameter name

Parameter

Type

Description

pcie_device_id

0x0 to 0xffff

EEIO

PCle device information mounted on the ExpEther I/O Expansion Unit (device ID) Device ID of PCle devices mounted on the ExpEther I/O Expansion Unit

pcie_class_code

0x0 to 0xffffff

EEIO

PCle device information mounted on the ExpEther I/O Expansion Unit (Class code) Class code of PCle devices mounted on the ExpEther I/O Expansion Unit

resource_id

0x0 to 0xffff

EEIO

Resource ID (Internal administration information of ExpEther Manager) This parameter is not displayed if the EE version is v1.0.

power_interlock_sta

tus

{enabled | disabled}

EEIO

Power interlock status with the

ExpEther board

 enabled:

Power interlock status enabled  disabled:

Power interlock status disabled

When the power interlock status of the ExpEther I/O Expansion Unit or

ExpEther clients is enabled, the power of the ExpEther I/O Expansion Unit is turned off when the power of the ExpEther board is turned off. 40G EE card does not support power interlock. Therefore, this parameter is not displayed if the type of the

ExpEther device is 40G version.

timestamp

0 to 9223372036854775 807 (java.lang.Long.MA

X_VALUE)

Common

Time stamp of the device information

Elapsed milliseconds from 1970/1/1

00:00:00 000 UTC

(8) EE card ID

 Specify the ExpEther unit to execute CLI subcommands by the argument "EE card ID". This

section describes how to check the EE card ID.

 A specific EE card ID is allocated to each ExpEther unit before shipment

One EE card ID is allocated to each ExpEther board (40G).

One EE card ID is allocated to each PCI Express Expansion slot that is mounted on the

ExpEther IO Expansion Unit (40G).

 The EE card ID corresponds to the MAC address of the ExpEther unit.

The MAC address of the ExpEther unit is printed on the label attached to the predetermined

location on the ExpEther unit.

Check the explanation of the MAC address of the ExpEther unit described in Getting started!

of the ExpEther board (40G) and the ExpEther IO Expansion Unit (40G).

Example of correspondence between MAC address and EE card ID

MAC address

EE card ID

00255CA6DCED

Tip

Check the EE card ID according to the following steps if you didn't take a

copy of the MAC address of the ExpEther unit.

Page 75

 You can check the EE card ID of the ExpEther board (40G) by using the ExpEtherConfig tool.

Refer to "4.2 ExpEtherConfig tool”.

 You can check the EE card ID of the ExpEther IO Expansion Unit (40G) in the following steps.

1. Press the UID switch located on the target PCI Express slot.

2. Execute the CLI subcommand "get" with the argument "--all".

eemcli.py get --all

3. The information of the ExpEther unit is displayed. Search lines whose "uid_switch_status"

is displayed as "on". "id" of the ExpEther unit whose "uid_switch_status" is "on" indicates

the EE card ID of the target PCI slot.

An output example is shown below.

id : 0x8cdf9d98a062 card ID status : eeio :ExpEther IO Expansion Unit update_time : 1469649457638 admin_status : enabled monitoring_status : enabled notification_status0 : [u'down', u'down'] notification_status1 : [u'down', u'down']

mac_address : 8c:df:9d:98:a0:62 ← MAC address group_id : 151 vlan_tagging : disabled multi_mac_addresses : enabled encryption : [u'disabled'] type : 40g

uid_switch_status : on ← Status of ID LED. ”on”：Light on

Page 76

4.2 ExpEtherConfig tool

The ExpEtherConfig tool includes the following functions for the ExpEther board (40G) mounted on the server.

 Output the information of the ExpEther board (40G)  Set the information (host information) to identify the server to the ExpEther board

NEC ESMPRO Manager uses the host information set on the ExpEther board to link the ExpEther board to the server that mounts it. You need to set the model name and the serial number of the server to the ExpEther board (40G) mounted on trhe server by using the ExpEtherConfig tool to manage the ExpEther board by NEC ESMPRO Manager.

OS's supporting the tool is shown below.

Windows Server 2012 R2 (x64 UEFI)

Red Hat Enterprise Linux 6 (x64 UEFI)

Red Hat Enterprise Linux 7 (x64 UEFI)

4.2.1 Installation and uninstallation (Windows version）

(1) Installation

Tip

Installation of ExpEtherConfig also installs the PlxSvc driver. If the PlxSvc driver has been installed, it is not installed. Stop the PlxSvc service and

uninstall the PlxSvc driver in advance.

Contact your sales representative for the installation media of ExpEtherConfig Tool.

i Sign in (Log on) with the built-in Administrator (or an account with the administrative right). ii Start the setup program "setup.exe" of the ExpEtherConfig tool.

The "setup.exe" is stored in the installer directory extracted from

ExpEtherConfigTool_Win_x64.zip.

iii "Choose Setup Language" screen is displayed. Select English and click "OK". Click "Cancel"

to finish installation.

Page 77

iv The setup program installs ExpEtherConfig tool if it is not found on the computer

When the installation starts, the InstallShield Wizard of the ExpEtherConfig tool is started.

Click "Next"

v Read the displayed license agreement carefully.

If you agree to it, select "I accept the terms in the license agreement" and click "Next".

Page 78

vi Installation destination is displayed.

The default destination folder is shown below.

“C:¥Program Files (x86)¥NEC Corporation¥ExpEtherConfig” Click "Next" if you do not change the destination folder. Click "Change" to change the destination folder. Enter a destination folder and click "Next".

vii The installation confirmation screen is displayed.

Click "Install" to start installing the ExpEtherConfig tool.

Page 79

viii When the tool has been installed, InstallShield Wizard is displayed as shown below.

Click "Finish" to exit the wizard.

(2) Uninstallation

Tip

This procedure does not uninstall the PlxSvc driver and stop the service.

Uninstall the tool after the following steps to uninstall the PlxSvc driver. ・ Execute the command prompt by an account with an administrative

right.

・ Execute PlxSvcCtrl.bat stored in the installed directory with “remove”

option in the command prompt.

# PlxSvcCtrl.bat remove

i Sign in (Log on) with the built-in Administrator (or an account with the administrator

authorization).

ii Start the setup program "setup.exe" of the ExpEtherConfig tool.

The "setup.exe" is stored in the installer directory extracted from

ExpEtherConfigTool_Win_x64.zip.

iii "Choose Setup Language" screen is displayed. Select English and click "OK". Click

"Cancel" to finish installation.

Page 80

iv The InstallShield Wizard of the ExpEtherConfig tool is started. Click "Next".

v The confirmation screen to delete the program is displayed.

Click "Remove" to start uninstalling the ExpEtherConfig tool.

vi When the tool has been uninstalled, InstallShield Wizard is displayed as shown below.

Click "Finish" to exit the wizard.

Page 81

4.2.2 Command reference

[Brief summary]

The ExpEtherConfig tool includes the following functions for the ExpEther board (40G) mounted on the

server.

 Output the information of the ExpEther board (40G).  Set the information (host information) to identify the server to the ExpEther board.

When you mounted a new ExpEther board (40G) or replaced the ExpEther board (40G), be sure to

execute the ExpEtherConfig tool and set the host information.

[Format]

ExpEtherConfigTool <command> [option]

Command

Description

show_details

Output the information of the ExpEther board (40G).

set_hostinfo

Set the host information to the ExpEther board.

* Be sure to specify one of commands described above.

Option

Description

-l<Level>

Specify the log level to execute it. Use the default value if you omit it. Level: 1: TRACE Output all logs.

2: DEBUG Output logs higher than the debug level. 3: INFO Output logs higher than the information level. <Default> 4: WARN Output logs higher than the warning level. 5: ERROR Output only error logs.

* Execute the tool by specifying the path of the destination folder or changing the current folder.

[Result]

The command specified with “show_details” outputs the following information as the standard output.

The command specified with “set_hostinfo” outputs the following information as the standard output after

executing the host information.

Output message

Description

ExpEther ID

ID to uniquely identify the ExpEther board and to be used by ExpEther

Manager

MAC Address

MAC address of the ExpEther board

VLAN ID

VLAN ID set on the ExpEther board

Host model name

Model name of the host set on the ExpEther board

Host serial number

Serial number of the host set on the ExpEther board

Following messages are output when an eror is generated by the tool.

Output message

Description

Invalid arguments.

Indicates that the argument specified in the command

line is invalid.

Failed to get the host data.

Indicates failure to get the host data.

Failed to set host data.

Indicates failure to set the host data.

Failed to search ExpEther device.

Indicates failure to search ExpEther device.

Failed to lock for EEPROM

access.

Indicates failure to lock for EEPROM access.

Failed to unlock for EEPROM

access.

Indicates failure to unlock for EEPROM access.

Failed to verify the lock for

EEPROM access.

Indicates failure to verify the lock for EEPROM access. Failed to write EEPROM.

Indicates failure to write EEPROM.

Failed to read EEROM.

Indicates failure to read EEPROM.

Page 82

Output logs to the following directory.

● Log format <Date/time> <Log level> <Function name> - <Message>

● Level and log message list

Level

Log message

description

TRACE

Start.

Indicates the beginning of the function.

TRACE

End.

Indicates the end of the function. This is output only when the command is

successfully terminated.

DEBUG

Model name : XXXXX

Model name obtained from the host

DEBUG

Serial number : XXXX

Serial number obtained from the host

DEBUG

Success to search ExpEther (found : X

devices).

Indicates that ExpEther has been

searched.

DEBUG

Success to scan PCI devices (count :

X).

Indicates that PCI devices have been

scanned.

DEBUG

The driver is not activated yet.

Indicates that the driver has not been

initialized.

DEBUG

The driver and devices are ready.

Indicates that the driver and devices

have been initialized.

DEBUG

The driver is ready.

Indicates that the driver has been

initialized.

DEBUG

ExpEther device is found.

Indicates that ExpEther has been

detected.

DEBUG

Success to read EEPROM data (offset:

xx, value xx).

Indicates that EEPROM has been

successfully read.

DEBUG

Success to write EEPROM data (offset:

xx, value xx).

Indicates that EEPROM has been

successfully written.

DEBUG

Success to read register (offset: xx,

value xx).

Indicates that registers have been

successfully read.

DEBUG

Success to write register (offset: xx,

value xx).

Indicates that registers have been

successfully written.

DEBUG

Retry to clear the lock for EEPROM

Access.

Indicates retrial to clear the lock for

EEPROM access.

DEBUG

Retry to verify the lock for EEPROM

Access.

Indicates retrial to verify the lock for

EEPROM access.

DEBUG

Retry to lock for EEPROM Access.

Indicates retrial to lock for EEPROM

access.

INFO

xx ExpEther devicdes are found.

Indicates the number of detected

ExpEther devices.

INFO

Model name : XXXXX

Model name obtained from the host

INFO

Serial number : XXXX

Serial number obtained from the host

INFO

Finished to set the host data normally.

Indicates successful end.

INFO

Success to unlock EEPROM access.

Indicates success to unlock EEPROM

access.

INFO

Success to lock EEPROM access.

Indicates success to lock EEPROM

access.

INFO

Success to verify the lock for EEPROM

access.

Indicates success to verify the lock for

EEPROM access.

ERROR

Invalid arguments.

Indicates that the argument specified

in the command line is invalid.

ERROR

Failed to set host data.

Indicates failure to set host

information.

ERROR

The driver is not active.

Indicates failure to search ExpEther devices as the PlxSvc driver has not

been initialized.

ERROR

Failed to search ExpEther device.

Indicates failure to search ExpEther

devices.

Output directory

File name

Tool execution directory

ExpEtherConfigTool.log

Page 83

Level

Log message

description

ERROR

The active driver is not found.

Indicates failure to search ExpEther devices as the PlxSvc driver has not

been installed or is invalid.

ERROR

Failed to scan devices.

Indicates failure to scan PCI devices.

ERROR

Failed to write model name (offset : xx,

value :xx).

Indicates failure to write the model

name.

ERROR

Failed to write serial number (offset : xx,

value :xx).

Indicates failure to write the serial

number.

ERROR

Failed to open device

Indicates failure to open devices.

ERROR

Failed to read model name (offset : xx).

Indicates failure to read the model

name.

ERROR

Failed to read serial number (offset : xx).

Indicates failure to read the serial

number.

ERROR

Device is busy.

Indicates failure to access EEPROM.

ERROR

Compare error (write data: xx, read

data: xx)

Indicates the data to write to EEPROM

did not correspond to the read data.

ERROR

Failed to write register (offset: xx, value:

xx, err: xx)

Indicates failure to write registers.

ERROR

Failed to write register (offset: xx, err:

xx)

Indicates failure to read registers.

ERROR

Failed to get the host data.

Indicates failure to get the host

information.

ERROR

Failed to read MAC address from

eeprom (offset: xx).

Indicates failure to read the MAC

address.

ERROR

Failed to read VLAN ID from eeprom

(offset: xx).

Indicates failure to read VLAN ID.

ERROR

Exceeded the retry count to lock

EEPROM access.

Indicates failure to lock EEPROM

access.

ERROR

Exceeded the retry count to verify the

lock for EEPROM access.

Indicates failure to verify the lock for

EEPROM access.

ERROR

Exceeded the retry count to unlock

EEPROM access.

Indicates failure to unlock EEPROM

access.

ERROR

Exceeded the retry count to read

Indicates failure to read registers with

indirect access.

ERROR

Exceeded the retry count to write

Indicates failure to write registers with

indirect access.

Important

After executing the command “set_hostinfo” and setting the host information, be sure to execute the CLI subcommand “audit” of

ExpEther Manager. eemcli.py audit --id ID

Important

Do not execute this tool several times at a time.

Tip

If you find an error caused by the tool due to a failure in locking, wait for several seconds or several ten seconds and execute it again. If the error persists, execute the CLI subcommand “unlock_eeprom” of ExpEther

Manager.

eemcli.py unlock_eeprom --id ID

Tip

An old version of the PlxSvc driver may have the ExpEtherConfig tool cause an error. In that case, delete the PlxSvc driver in advance and

install the ExpEtherConfig tool again.

Page 84

Chapter 5. Cautions

This chapter describes notes for caution on the ExpEther IO Expansion Unit (40G).

5.1 Note on the ExpEther IO Expansion Unit (40G)

 The ExpEther IO Expansion Unit (40G) does not support sleeping. Set OS sleeping of the server on

which the ExpEther board (40) to be connected to the ExpEther IO Unit (40G) is mounted to [Off] or [Disable] before using it. If you enable the sleeping setting and use it, you may fail to return from sleeping and lose the important data. Setting sleeping to [Off] or [Disable] may vary depending on OS. Check the instruction manual of the OS you use.

 • You can connect up to four PCIe slots of the ExpEther IO Expansion Unit (40G) concurrently

connected to one ExpEther board (40G). You can connect four or more PCIe slots with the same Group ID in the same network environment. However, the fifth or subsequent PCIe slots are not

connected to the ExpEther board (40G).

 If you mount a PCI Express board on the ExpEther IO Expansion Unit (40G), be sure to connect it

to ther ExpEther board (40G) and then turn on the power of the server.

5.2 Other notes

 When you connect an existing IP terminal to a network switch to connect the ExpEther product, the

traffic of ExpEther does not disturb the existing IP traffic. Therefore, if the existing IP traffic is busy, you may not get the performance of ExpEther. To work ExpEther and existing terminals together, put it into operation to secure a network band for ExpEther using the QoS function of the network switch.

 If Spanning Tree Protocol (STP) is enabled by the network switch setting, the ExpEther board

(40G) and the ExpEther IO Expansion Unit (40G) may take time to link up and be ready for communication after the power-on and may not recognize the option board mounted on the IO Expansion unit (40G). Disable the Spanning Tree Protocol (STP) function before using. (Check the instruction manual of the network switch for the setting.)

Page 85

Chapter 6. Specifications

6.1 Specifications

Item

ExpEther IO

Expansion Unit

(40G)-2S

ExpEther IO

Expansion Unit

(40G)-4S

Remarks

LAN I/F

QSFP+ x4 RJ45 x1

ExpEther connection for

QSFP+

Only management for

RJ45

PCI Express expansion

slot

PCI Express Gen3 x8Lane connection x 2

slots

PCI Express Gen3 x8Lane connection x 4

slots

The physical slot

supports x16 long size.

Expansion slot mounted Option card

Contact your sales representative for the

product whose operation has been checked.

LED

POW LED

DC-ON: On (green), DC-OFF: Blinking (green), AC-OFF: Off

One per chassis

System Status

LED

Status error (Critical): On (amber), Status error

(Warning): Blinking (amber)

One per chassis ID LED

UID (Software control): On (blue)

One per slot

Slot Status

LED

Status error: On (amber), Normal: Off

One per slot

Host POW

LED

Host DC-ON: On (green), Host DC-OFF: Off

One per slot

Switch

Power

switch

Power ON/OFF control

One per chassis UID

Control from the network

One per slot

Group ID setting

Group ID setting rotary switch (set to 1 to F)

One per slot

If it is set to 0, ExpEther Manager sets the Group

ID from16 to 4000.

AC power rating

100 to 127 V/200 to 240 V

12.47 A/ 7.08 A

100 to 127 V/200 to 240 V

9.5 A/ 4.6 A

External dimensions

(width × depth × height)

142 mm x 400 mm x132 mm (protrusions excluded)

Weight

About 5 kg

Not including PCI

Express board

Power consumption

Max:1200 W

Max: 800 W

Installing PCI Express board, and connecting the expansion power

cable

Accessories

Power cord (3m, 100V/ bipolar grounded outlet), clamp for power cord, expansion power cable for PCI Express board, expansion power cable for GPU computing processor board, Getting Started !, warranty

card

Power cord (3m, 100V/ bipolar grounded outlet), clamp for power cord, Getting Started !,

warranty card

Page 86

6.2 Environmental requirements

Item

Content

Remarks

Temperature Operating

10 to 40°C

Storage

–10 to 55°C

Humidity Operating

20 to 80%(no condensation)

Storage

20 to 80%(no condensation)

Voltage / frequency variation

100 to 127 V/200 to 240 V 50 Hz/60 Hz

6.3 Cable

Contact your sales representative for the product whose operation has been checked.

Page 87

Chapter 7. Daily Maintenance

To use this product under good conditions at all times, periodically check and maintain as follows. If failures are found, ask your sales representative, and it will avoid further malfunctioning of the product.

7.1 Checking and Applying Updates

For the update information of this product, contact your salses representative.

Tips

NEC recommends that you back up data before applying the latest update.

7.2 Checking LED

After powering on the server or before shutting down the system and powering off the product, check the LED on the product. For the functions and descriptions of the LED, see Chapter 1 in this guide. If the indicator shows the server abnormality, contact your salses representative.

7.3 Cleaning

Regularly clean the server to keep it in good condition.

WARNING

Be sure to observe the following precautions to use the server safety. Failure to observe the precautions may cause death or serious injury. For details, see Precautions for Use in this guide.

 Do not disassemble, repair, or alter the server.  Disconnect the power plug before cleaning the server.

Important

Be sure to read "Precautions for Use" attached to this product, or Precautions for Use in this guide. This describes points of caution to

ensure the safe use of this product.

Wipe the external surfaces of the server with a dry soft cloth. Follow the procedure below if stains

remain on the surfaces.

Important

 Do not use thinner, benzene, and other volatile solvents.

Those solvents could damage or tarnish the material.

 The power outlet, cables, connectors on the rear panel of the

product, and the inside of the server must be kept dry.

1. Confirm that the power of this product is OFF (POWER LED is OFF).

2. Unplug the power cord of ExpEther IO Expansion Unit (40G) from a power outlet, and wipe off dust from the power cord plug with a dry cloth.

3. Soak a soft cloth in neutral detergent that is diluted with cold or lukewarm water, and squeeze it firmly.

Page 88

4. Rub off stains on ExpEther IO Expansion Unit (40G) with the cloth prepared in step 3.

5. Soak a soft cloth in water, squeeze it firmly, and wipe the server with it once again.

6. Wipe off with dry cloth to absorb excess liquid.

7. Wipe off dusts attached to the vent with dry cloth.

Page 89

Chapter 8. User Support

Before getting after-sales service, check the contents of the warranty and service.

8.1 Maintenance Services

Service representatives from NEC subsidiary companies or companies authorized by NEC provide maintenance services. For the services, contact your sales representative.

8.2 Before Asking for Repair

If you think that a failure occurred, follow the steps below:

1. Check if the power cord and cables to other products are properly connected.

2. See Chapter 9.Troubleshooting. If you find a symptom similar to your problem, take the action as instructed.

3. Confirm that the required software has been properly installed.

4. Scan for viruses using a commercial Antivirus Software.

If the problem persists after taking the measures above, contact your sales representative. Take notes on LED indications and the display on the screen at the failure, which will be useful information for the repair. For repair within the warranty period, be sure to apply with your warranty.

Page 90

Chapter 9. Troubleshooting

If this product does not work correctly, check it according to the contents of the following checklist before sending it for repair. If an item in the checklist corresponds with a problem you are experiencing, follow the subsequent check and processing instructions.

9.1 Common problems of ExpEther series products

 The power does not turn on.

□Is the power properly supplied to the unit?

→ Check that you have connected the power cord of the server to the outlet (or UPS

(uninterruptible power system)) that conforms to the power standard.

→ Check that the power cord is properly connected to the ExpEther IO Expansion Unit (40G). → Check that the power cord of the ExpEther IO Expansion Unit (40G) is properly connected to

the outlet.

→ Use the power cord attached to the unit. Check that the coating of the power cord or the plug

is broken.

→ Check that the breaker of the connected outlet is turned on. → Check that the main power switch of the ExpEther IO Expansion Unit (40G) is turned on. → If you connect it to a UPS, check that the power of the UPS is turned on and the UPS outputs

the power. Refer to the instruction manual attached to the UPS.

 LINK unsuccessful

□Is the network cable correctly connected?

→ Check if the cable is firmly attached to the LAN port or the QSFP+ port of the ExpEther

product and the link partner (such as switches).

→ Check if the power of the link partner (such as switches) is turned on. → If you use the non-standard cable, damaged interface cable, excessively bent cable and that

crushed under the heavy object, you may not get into communication. In that case, try to use

other cables.

 The ExpEther board and the ExpEther IO device do not get connected.

□ Is the Group ID correctly set?

→ To get the ExpEther board (40G) and the ExpEther IO Expansion Unit (40G) connected, you

need to set the Group ID of the ExpEther board (40G) and the ExpEther IO Expansion Unit

(40G) to the same value. Check the Group ID setting.

→ If you have multiple ExpEther boards (40G) connected on the same network, check if the

Group IDs of the ExpEther boards (40G) is redundant. If you find redundant Group IDs of the

ExpEther boards (40G), set them again to avoid redundancy.

 The performance of the connected ExpEther IO device is low.

→ If you use only one connection port, use two ports to change to multi-path connection and

check how it works.

→ Check the delay time of the network environment including network switches. The

performance may reduce in the network environment where you find a significant delay time. To improve the performance, it is effective to improve the delay time of the network. Therefore, reduce the number of steps of the connected network switch and change the

network switch to that whose delay time is less.

 The product does not correctly operate if you pull out and insert the QSFP+ cable during

operation.

→ Check if the server is compatible with the PCI Express hot plug feature. → To pull out and insert the QSFP+ cable during operation, the server mounting the ExpEther

board (40G), OS, devices mounted on the ExpEther IO Expansion Unit (40G), and the driver

need to be compatible with the PCI Express hot plug feature.

Page 91

9.2 Problems of ExpEther IO Expansion Unit (40G)

 The PCI Express card mounted on the ExpEther IO Expansion Unit (40G) cannot be

recognized.

→ Check if the PCVI Express card is properly inserted into the PCI Express slot of the ExpEther

IO Expansion Unit (40G).

→ Check if the power of the ExpEther IO Expansion Unit (40G) is turned on. → Check if the extension power cable is properly connected for the PCI Express card that

needs to be connected to the extension power cable.

 The power turned off during the operation and wouldn’t turn on.

→ The ExpEther IO Expansion Unit (40G) may have detected a temperature anomaly or the

power has turned off. Remove the power cord from the ExpEther IO Expansion Unit (40G) and check if there is any problem in the operating environment. Check if there is any problem of the operation of the cooling fan of the ExpEther IO Expansion Unit (40G) after turning on

the power.

→ Check if the power cord has been pulled out or if the main power switch has been turned off.

 The performance of the mounted device is low.

→ Products other than those whose operation has been checked mounted on the ExpEther IO

Expansion Unit (40G) may not be cooled. Contact your sales representative for the product

whose operation has been checked.

→ Check that four connection ports of the ExpEther IO Expansion Unit (40G) are all connected.

 ID LED does not light up by pressing the UID switch.

→ Check if the ExpEther board and the ExpEther IO Expansion Unit (40G) are connected. → To light up ID LED by pressing the UID switch, you need to install ExpEther Manager on the

control unit that is on the same network.

→ Check if you can identify the target ExpEther IO Expansion Unit (40G) from ExpEther

Manager.

9.3 Problems on ExpEther Manager Software

 ExpEther Manager does not start.

→ Check again if the configured environment variables are correct. → Check again if eem.conf is correctly configured. → If you have changed environment variables and eem.conf, restart EEM.

 The CLI (command line) times out.

→ Check if the control unit is correctly connected on the ExpEther network by the network cable

and the status of the external L2 switch.

→ Check again if eem.conf is correctly configured. → If you specify a long data length to the option parameter “-length” of the CLI subcommand

“dumpreg” and “dumprom”, specify a shorter data length and adjust it.

 The host information of the ExpEther board (40G) is set by using the ExpEtherConfig tool.

However, the information is not reflected on the management software.

→ After setting the host information, execute the CLI subcommand “audit”

 Collecting the information in case of a problem

→ Collect the information from the following directories in case of a problem.

<EEM path>/logs/ <EEM path>/conf/ <EEM path>/tomcat/logs/

Page 92

All product, brand, or trade names used in this guide are the trademarks or registered trademarks of their respective trademark owners

Trademarks

Microsoft, Windows, Windows Server and Visual Studio are registered trademarks or trademarks of

Microsoft Corporation in the United States and other countries. Intel, Pentium, and Xeon are registered trademarks of Intel Corporation of the United States.

Adobe, the Adobe logo, and Acrobat are trademarks of Adobe Systems Incorporated. DLT and DLTtape

are trademarks of Quantum Corporation of the United States. PCI Express is a trademark of Peripheral Component Interconnect Special Interest Group. Linux is a trademark or registered trademark of Linus Torvalds in Japan and other countries.

Red Hat® and Red Hat Enterprise Linux are trademarks or registered trademarks of Red Hat, Inc. in the

United States and other countries. The OpenStack® Word Mark and the OpenStack® logos are trademarks of the OpenStack Foundation. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates. Apache and Tomcat are trademarks of the Apache Software Foundation.

All other product, brand, or trade names used in this publication are the trademarks or registered

trademarks of their respective trademark owners.

Cautions

(1) Unauthorized reproduction of the contents of this document, in part or in its entirety, is prohibited. (2) The contents of this document may change without prior notice. (3) Every effort has been made to ensure the completeness of this document. However, if you have any

concerns, or discover errors or omissions, please contact your retailer.

(4) NEC assumes no liability for any loss, including loss of earnings, arising from the use of this product,

irrespective of (3) above.

(5) This product is not intended for use in medical, nuclear, aerospace, mass transit or other applications

where human life may be at stake or high reliability is required, nor is it intended for use in controlling such applications. We disclaim liability for any personal injury and property damages caused by such

use of this product.

(6) The data saved in a microSD card and a USB memory will not be warranted even if the unit gets out of

order. Take measures such as backing up the data for yourself.

Page 93

License Agreement Notice

Open source software of following license is included in the part of this product (ExpEther Manager).

 asm-debug-all-5.0.2.jar  Javaassis  Java Native Access  Apache log4  org.osgi.core-4.2.0.jar  SQLite JDBC  validation-api-1.1.0.Final.jar  Apache Tomcat 7.0.57  Apache log4cxx 0.10.0  aopalliance-repackaged-2.3.0-b10.jar  HK2  Javax  Jersey  osgi-resource-locator-1.0.1.jar  Java Persistece API  Eclipse  WinPcap

License This product uses the following open source software according to the terms of the ASM License.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that

the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. Neither the name of the copyright holders nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,

EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

--------------------------------------------------------------------------------

This product uses the following open source software according to the terms of the Apache License

Version 2.0. * javassist-3.18.1-GA.jar

* jna-4.1.0.jar * log4j-1.2.17.jar

Page 94

* org.osgi.core-4.2.0.jar * sqlite-jdbc-3.8.7.jar * validation-api-1.1.0.Final.jar * Apache Tomcat 7.0.57 * Apache log4cxx 0.10.0.

Apache License

Version 2.0, January 2004

http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by

Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting

the License.

"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial

ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this

License.

"Source" form shall mean the preferred form for making modifications, including but not limited to

software source code, documentation source, and configuration files.

"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to

other media types.

"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is

provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the

interfaces of, the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise

designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution

has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable

sublicense, and distribute the Work and such Derivative Works in Source or Object form.

Page 95

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as

stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent

litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work

or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date

such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any

medium, with or without modifications, and in Source or Object form, provided that You meet the

following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent,

trademark, and attribution notices from the Source form of the Work, excluding those notices that do

not pertain to any part of the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that

You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display

generated by the Derivative Works, if and wherever such third-party notices normally appear. The

contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices

cannot be construed as modifying the License.

You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work

otherwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally

submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of

this License, without any additional terms or conditions.

Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license

agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service

marks, or product names of the Licensor, except as required for reasonable and customary use in

describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the

Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties

or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR

PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the

Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence),

contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if

such Contributor has been advised of the possibility of such damages.

Page 96

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof,

You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such

warranty or additional liability.

END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the

you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either

express or implied. See the License for the specific language governing permissions and limitations under the License.

--------------------------------------------------------------------------------

Page 97

This product uses the following open source software according to the terms of the the Common Development and Distribution License (CDDL-1.0).

* aopalliance-repackaged-2.3.0-b10.jar * hk2-api-2.3.0-b10.jar * hk2-locator-2.3.0-b10.jar * hk2-utils-2.3.0-b10.jar * javax.annotation-api-1.2.jar * javax.inject-2.3.0-b10.jar * javax.ws.rs-api-2.0.1.jar * jaxb-api-2.2.7.jar * jersey-client.jar * jersey-common.jar * jersey-container-servlet.jar * jersey-container-servlet-core.jar * jersey-entity-filtering-2.13.jar * jersey-guava-2.13.jar * jersey-media-moxy-2.13.jar * jersey-server.jar * osgi-resource-locator-1.0.1.jar * persistence-api-1.0.jar

COMMON DEVELOPMENT AND DISTRIBUTION LICENSE Version 1.0 (CDDL-1.0)

1. Definitions.

1.1. Contributor means each individual or entity that creates or contributes to the creation of

Modifications.

1.2. Contributor Version means the combination of the Original Software, prior Modifications used by a

Contributor (if any), and the Modifications made by that particular Contributor.

1.3. Covered Software means (a) the Original Software, or (b) Modifications, or (c) the combination of

files containing Original Software with files containing Modifications, in each case including

portions thereof.

1.4. Executable means the Covered Software in any form other than Source Code.

1.5. Initial Developer means the individual or entity that first makes Original Software available under

this License.

1.6. Larger Work means a work which combines Covered Software or portions thereof with code not

governed by the terms of this License.

1.7. License means this document.

1.8. Licensable means having the right to grant, to the maximum extent possible, whether at the time of

the initial grant or subsequently acquired, any and all of the rights conveyed herein.

1.9. Modifications means the Source Code and Executable form of any of the following:

A. Any file that results from an addition to, deletion from or modification of the contents of a file

containing Original Software or previous Modifications; B. Any new file that contains any part of the Original Software or previous Modification; or C. Any new file that is contributed or otherwise made available under the terms of this License.

1.10. Original Software means the Source Code and Executable form of computer software code that is originally released under this License.

1.11. Patent Claims means any patent claim(s), now owned or hereafter acquired, including without limitation, method, process, and apparatus claims, in any patent Licensable by grantor.

Page 98

1.12. Source Code means (a) the common form of computer software code in which modifications are made and (b) associated documentation included in or with such code.

1.13. You (or Your) means an individual or a legal entity exercising rights under, and complying with all of the terms of, this License.

For legal entities, You includes any entity which controls, is controlled by, or is under common control with You. For purposes of this definition, control means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial ownership of

such entity.

2. License Grants.

2.1. The Initial Developer Grant.

Conditioned upon Your compliance with Section 3.1 below and subject to third party intellectual

property claims, the Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive license:

(a) under intellectual property rights (other than patent or trademark) Licensable by Initial

Developer, to use, reproduce, modify, display, perform, sublicense and distribute the Original Software (or portions thereof), with or without Modifications, and/or as part of a Larger Work;

and

(b) under Patent Claims infringed by the making, using or selling of Original Software, to make,

have made, use, practice, sell, and offer for sale, and/or otherwise dispose of the Original

Software (or portions thereof).

distributes or otherwise makes the Original Software available to a third party under the terms

of this License.

(d) Notwithstanding Section 2.1(b) above, no patent license is granted: (1) for code that You delete

from the Original Software, or (2) for infringements caused by: (i) the modification of the Original Software, or (ii) the combination of the Original Software with other software or

devices.

2.2. Contributor Grant.

Conditioned upon Your compliance with Section 3.1 below and subject to third party intellectual

property claims, each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license:

(a) under intellectual property rights (other than patent or trademark) Licensable by Contributor to

use, reproduce, modify, display, perform, sublicense and distribute the Modifications created by such Contributor (or portions thereof), either on an unmodified basis, with other Modifications,

as Covered Software and/or as part of a Larger Work; and

(b) under Patent Claims infringed by the making, using, or selling of Modifications made by that

Contributor either alone and/or in combination with its Contributor Version (or portions of such combination), to make, use, sell, offer for sale, have made, and/or otherwise dispose of: (1) Modifications made by that Contributor (or portions thereof); and (2) the combination of Modifications made by that Contributor with its Contributor Version (or portions of such

combination).

distributes or otherwise makes the Modifications available to a third party.

(d) Notwithstanding Section 2.2(b) above, no patent license is granted: (1) for any code that

Contributor has deleted from the Contributor Version; (2) for infringements caused by: (i) third party modifications of Contributor Version, or (ii) the combination of Modifications made by that Contributor with other software (except as part of the Contributor Version) or other devices; or (3) under Patent Claims infringed by Covered Software in the absence of Modifications made

by that Contributor.

Page 99

3. Distribution Obligations.

3.1. Availability of Source Code.

Any Covered Software that You distribute or otherwise make available in Executable form must also be made available in Source Code form and that Source Code form must be distributed only

under the terms of this License.

You must include a copy of this License with every copy of the Source Code form of the Covered

Software You distribute or otherwise make available.

You must inform recipients of any such Covered Software in Executable form as to how they can obtain such Covered Software in Source Code form in a reasonable manner on or through a

medium customarily used for software exchange.

3.2. Modifications.

The Modifications that You create or to which You contribute are governed by the terms of this License. You represent that You believe Your Modifications are Your original creation(s) and/or You

have sufficient rights to grant the rights conveyed by this License.

3.3. Required Notices.

You must include a notice in each of Your Modifications that identifies You as the Contributor of the Modification. You may not remove or alter any copyright, patent or trademark notices contained within the Covered Software, or any notices of licensing or any descriptive text giving attribution to

any Contributor or the Initial Developer.

3.4. Application of Additional Terms.

You may not offer or impose any terms on any Covered Software in Source Code form that alters or restricts the applicable version of this License or the recipients rights hereunder. You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one

or more recipients of Covered Software.

However, you may do so only on Your own behalf, and not on behalf of the Initial Developer or any Contributor. You must make it absolutely clear that any such warranty, support, indemnity or liability obligation is offered by You alone, and You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of

warranty, support, indemnity or liability terms You offer.

3.5. Distribution of Executable Versions.

You may distribute the Executable form of the Covered Software under the terms of this License or under the terms of a license of Your choice, which may contain terms different from this License, provided that You are in compliance with the terms of this License and that the license for the Executable form does not attempt to limit or alter the recipients rights in the Source Code form

from the rights set forth in this License.

If You distribute the Covered Software in Executable form under a different license, You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Developer or Contributor. You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of any

such terms You offer.

3.6. Larger Works.

You may create a Larger Work by combining Covered Software with other code not governed by the terms of this License and distribute the Larger Work as a single product. In such a case, You

must make sure the requirements of this License are fulfilled for the Covered Software.

4. Versions of the License.

4.1. New Versions.

Sun Microsystems, Inc. is the initial license steward and may publish revised and/or new versions

of this License from time to time.

Each version will be given a distinguishing version number. Except as provided in Section 4.3, no

Page 100

one other than the license steward has the right to modify this License.

4.2. Effect of New Versions.

You may always continue to use, distribute or otherwise make the Covered Software available under the terms of the version of the License under which You originally received the Covered Software. If the Initial Developer includes a notice in the Original Software prohibiting it from being distributed or otherwise made available under any subsequent version of the License, You must distribute and make the Covered Software available under the terms of the version of the License under which You originally received the Covered Software. Otherwise, You may also choose to use, distribute or otherwise make the Covered Software available under the terms of any

subsequent version of the License published by the license steward.

4.3. Modified Versions.

When You are an Initial Developer and You want to create a new license for Your Original Software, You may create and use a modified version of this License if You: (a) rename the license and remove any references to the name of the license steward (except to note that the license differs from this License); and (b) otherwise make it clear that the license contains terms which

differ from this License.

5. DISCLAIMER OF WARRANTY. COVERED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN AS IS BASIS,

WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED SOFTWARE IS WITH YOU. SHOULD ANY COVERED SOFTWARE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED SOFTWARE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.

6. TERMINATION.

6.1. This License and the rights granted hereunder will terminate automatically if You fail to comply with

terms herein and fail to cure such breach within 30 days of becoming aware of the breach.

Provisions which, by their nature, must remain in effect beyond the termination of this License shall

survive.

6.2. If You assert a patent infringement claim (excluding declaratory judgment actions) against Initial

Developer or a Contributor (the Initial Developer or Contributor against whom You assert such claim is referred to as Participant) alleging that the Participant Software (meaning the Contributor Version where the Participant is a Contributor or the Original Software where the Participant is the Initial Developer) directly or indirectly infringes any patent, then any and all rights granted directly or indirectly to You by such Participant, the Initial Developer (if the Initial Developer is not the Participant) and all Contributors under Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice from Participant terminate prospectively and automatically at the expiration of such 60 day notice period, unless if within such 60 day period You withdraw Your claim with respect to the Participant Software against such Participant either unilaterally or pursuant to a written agreement

with Participant.

6.3. In the event of termination under Sections 6.1 or 6.2 above, all end user licenses that have been

validly granted by You or any distributor hereunder prior to termination (excluding licenses granted

to You by any distributor) shall survive termination.

7. LIMITATION OF LIABILITY. UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT

(INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED SOFTWARE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOST PROFITS, LOSS OF GOODWILL,