Dell M1000E Software Supplementary Note for the Cisco M SFS7000E InfiniBand Switch

Table Of Contents

Dell M1000E Software Supplementary Note for the Cisco M SFS7000E InfiniBand Switch

Updating the Dell M1000E Module Firmware Using the In-Band Method

Installing and Building the ibspark Tool

Obtaining the Firmware Image File

Using the Mellanox ibspark Tool

Obtaining the Switch Port 0 LID Using the Cisco ib_sm_cli Tool for the Cisco High-Performance Subnet Manager

Obtaining the Switch Port 0 LID Using the OFED ibnetdiscover Tool

Using the ibspark Tool to Burn the Firmware Image

Burning a New Node GUID for the Cisco M SFS7000E InfiniBand Switch

Burning a New System Image GUID for the Cisco M SFS7000E InfiniBand Switch

Applying and Verifying New Firmware and GUID Values

Troubleshooting Error Messages

Using the OFED ibportstate In-Band IB Port Control Tool with the Dell M1000E

Port Control Using the Switch Port 0 LID

Port Control Using the Node GUID

Port Speed Control Using the Switch Port 0 LID

Monitoring Port Counters

Related Documentation

Obtaining Documentation and Submitting a Service Request

Dell M1000E Software Supplementary Note for the Cisco M SFS7000E InfiniBand Switch

---

Revised: April 21, 2008

This document is a Dell M1000E software supplementary note for the Cisco M SFS7000E InfiniBand (IB) Switch and includes the following sections:

•Updating the Dell M1000E Module Firmware Using the In-Band Method

•Using the OFED ibportstate In-Band IB Port Control Tool with the Dell M1000E

•Monitoring Port Counters

•Related Documentation

•Obtaining Documentation and Submitting a Service Request

Updating the Dell M1000E Module Firmware Using the In-Band Method

This section describes the in-band firmware update of the Dell M1000E module and includes the following topics:

•Installing and Building the ibspark Tool

•Obtaining the Firmware Image File

•Using the Mellanox ibspark Tool

Installing and Building the ibspark Tool

This section provides information about installing and building the ibspark tool.

The pre-built ibspark binary for this platform is available at the following URL:

http://www.cisco.com/kobayashi/sw-center/index.shtml

Obtaining the Firmware Image File

This section provides information about the firmware image file.

The image file for this platform is available at the following URL:

http://www.cisco.com/kobayashi/sw-center/index.shtml

Using the Mellanox ibspark Tool

This section describes how to use the Mellanox ibspark tool and includes the following topics:

•Obtaining the Switch Port 0 LID Using the Cisco ib_sm_cli Tool for the Cisco High-Performance Subnet Manager

•Obtaining the Switch Port 0 LID Using the OFED ibnetdiscover Tool

•Using the ibspark Tool to Burn the Firmware Image

•Burning a New Node GUID for the Cisco M SFS7000E InfiniBand Switch

•Burning a New System Image GUID for the Cisco M SFS7000E InfiniBand Switch

•Applying and Verifying New Firmware and GUID Values

•Troubleshooting Error Messages

The ibspark tool requires the local identifier (LID) of the Cisco M SFS7000E IB switch for which you are updating the firmware.

The LID is the switch port 0 LID of the switch chip. The LID value is provided to the tool with the -d option. The firmware filename is provided with the -i option.

Obtaining the Switch Port 0 LID Using the Cisco ib_sm_cli Tool for the Cisco High-Performance Subnet Manager

To obtain the switch port 0 LID using the Cisco ib_sm_cli tool for the Cisco High-Performance Subnet Manager (HPSM), perform the following steps:

---

Step 1 Run the ib_sm_cli command at the host terminal.

Step 2 Type the show port -s command at the ib_sm> prompt.

This command lists all the switch chip ports and host IB ports.

Step 3 Make a note of the number in the column labeled lid against port value 0.

This is the switch port 0 LID required by the firmware burning tool.

The following is sample output from the show port -s command that displays the location of switch port 0 LID:

ib_sm> show port -s

================================================================================                          
Subnet Manager Port Summary

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

node-guid                port  lid   state      link

--------------------------------------------------------------------------------

00:18:8b:90:97:fe:06:62  1     5     active     4x-ddr

00:18:8b:90:97:fe:06:6e  1     4     active     4x-ddr

00:18:8b:90:97:fe:06:96  1     2     active     4x-ddr

00:18:8b:90:97:fe:06:b2  1     3     active     4x-ddr

00:18:8b:90:97:fe:06:fa  1     6     active     1x-ddr

00:1b:0d:55:55:00:00:00  0     8     active     4x-sdr

00:1b:0d:55:55:00:00:00  1     0     down       4x-sdr

00:1b:0d:55:55:00:00:00  2     0     active     4x-ddr

....truncated

---

Obtaining the Switch Port 0 LID Using the OFED ibnetdiscover Tool

To get the switch port 0 LID using the OpenFabrics Enterprise Distribution (OFED) ibnetdiscover tool for the Subnet Manager OpenSM, perform the following steps:

---

Step 1 At the host terminal run the ibnetdiscover command.

Step 2 Use the LID value as highlighted in the output.

It is the value displayed against the switch base port 0.

The following example highlights the location of switch port 0 LID:

host1# ibnetdiscover

# Topology file: generated on Tue Dec  4 15:36:50 2007

#

# Max of 2 hops discovered

# Initiated from node 00188b9097fe0696 port 00188b9097fe0697

vendid=0x5ad

devid=0xb924

switchguid=0x1b0d5555000000

Switch  24 "S-001b0d5555000000"        # "Cisco Switch" base port 0 lid 8 lmc 0

[14]    "H-00188b9097fe06fa"[1]         # "localhost HCA-1" lid 6

[13]    "H-00188b9097fe0662"[1]         # "localhost HCA-1" lid 5

[10]    "H-00188b9097fe06b2"[1]         # "localhost HCA-1" lid 2

[2]     "H-00188b9097fe066e"[1]         # "localhost HCA-1" lid 4

[16]    "H-00188b9097fe0696"[1]         # "svbu-dell10g-intel16 HCA-1" lid 1

vendid=0x2c9

devid=0x634a

sysimgguid=0x188b9097fe06fd

caguid=0x188b9097fe06fa

Ca      2 "H-00188b9097fe06fa"          # "localhost HCA-1"

[1]     "S-001b0d5555000000"[14]                # lid 6 lmc 0 "Cisco Switch"

lid 8

....truncated

---

Using the ibspark Tool to Burn the Firmware Image

To burn the firmware image, using the ibspark tool, perform the following steps:

---

Step 1 Obtain the switch port 0 LID.

Step 2 Obtain the new version of the dell10g.img firmware image file.

Step 3 Run the ibspark command on the host to burn the firmware image.

The ibspark command leaves the Node globally unique identifier (NodeGUID) and System ImageGUID unchanged by default. It only updates the firmware.

host1# ibspark -d 8 -i dell10g.img burn

- Checking primary image     -  OK

   Current FW Version:  1.0.0

   New FW Version:      1.0.0

- Burning secondary image    -  OK

- Verifying secondary image  -  OK

- Burning primary image      -  OK

- Verifying primary image    -  OK

The switch port 0 LID is 8 in the preceding example.

Step 4 Use the ibspark swreset option to soft reset the Cisco M SFS7000E IB switch.

Soft resetting the switch enables the new firmware to take effect.

The following example shows how to soft reset the switch.

host1# ibspark -d 8 swreset

Resetting device 8 ...

---

Burning a New Node GUID for the Cisco M SFS7000E InfiniBand Switch

This section describes how to burn a new Node GUID for the Cisco M SFS7000E IB switch.

To change the Node GUID, you must provide the current dell10g.img image as shown in the following example:

host1# ibspark -d 8 -guid 0x001b0d5555000000 -i dell10g.img burn 

- Checking primary image     -  OK

   Current FW Version:  1.0.0

   New FW Version:      1.0.0

    You are about to replace Node GUID in eeprom:

 Current value: 0x0005ad0000000002

 New value:     0x001b0d5555000000

    Is it OK ? (y/n) [n] : y

- Burning secondary image    -  OK

- Verifying secondary image  -  OK

- Burning primary image      -  OK

- Verifying primary image    -  OK

Burning a New System Image GUID for the Cisco M SFS7000E InfiniBand Switch

This section describes how to burn a new system image GUID for the Cisco M SFS7000E IB switch.

To burn a new system image GUID for the switch, use the ibspark -d command as shown in the following example:

host1# ibspark -d 8 -sysguid 0x001b0d5555000000 -I dell10g.img burn

- Checking primary image     -  OK

   Current FW Version:  1.0.0

   New FW Version:      1.0.0

    You are about to replace System Image GUID in eeprom:

 Current value: 0x0000000000000000

 New value:     0x001b0d5555000000

    Is it OK ? (y/n) [n] : y

- Burning secondary image    -  OK

- Verifying secondary image  -  OK

- Burning primary image      -  OK

- Verifying primary image    -  OK

Applying and Verifying New Firmware and GUID Values

This section describes how to add new firmware and GUID values to the Cisco M SFS7000E IB switch and how to verify the changed values.

To apply new firmware and GUID values, perform the following steps:

---

Step 1 Perform a soft reset.

The following example shows how to perform a soft reset:

host1# ibspark -d 8 swreset

Resetting device 8 ...

Step 2 Verify the firmware version and GUID values burned.

The following example shows how to verify the firmware version and GUID values:

host1# ibspark -d 8 query

Query:

  FW Version:            1.0.0

  Node GUID:             0x001b0d5555000000

  System Image GUID:     0x001b0d5555000000

  Node Description:      Cisco Switch

  Board Serial Number:   NONE

  PSID:                  0

---

Troubleshooting Error Messages

This section describes some typical error messages.

1. The following types of error messages are displayed if an incorrect LID is provided:

host1# ibspark -d 9 query

ibvsmad: iberror: failed: cr access read to Lid 9 failed

host1# ibspark -d 0 query

ibvsmad: iberror: failed: can't resolve destination port 0

2. The following error message is displayed if the file extension of the firmware image file is in upper case.

host1# ibspark -d 8 -i dell10g.IMG burn

-E- Failed to open image file dell10g.IMG: Unsupported file format (.IMG).

Supported formats: .img

Rename the files with the incorrect file extensions, and repeat the command.

Using the OFED ibportstate In-Band IB Port Control Tool with the Dell M1000E

This section describes how to use the OFED ibportstate in-band IB port control tool with the Dell M1000E and includes the following topics:

•Port Control Using the Switch Port 0 LID

•Port Control Using the Node GUID

•Port Speed Control Using the Switch Port 0 LID

This section provides examples of how to control IB ports on the Dell  M1000E chassis using the OFED ibportstate tool. On switch ports the ibportstate tool supports enable, disable, and reset operations. On switch and host-channel adapter (HCA) ports it supports the speed operation. The default operation is query.

Port Control Using the Switch Port 0 LID

The following example shows how to query, disable, and then enable port 16 on the Cisco M SFS7000E IB switch.

Use the ib_sm_cli tool and the show port -s command to display the summary of ports on the IB network. The first four entries displayed in Step 2 are the HCAs on the four blade servers present in the chassis. The remaining entries displayed are the switch ports.

To query and control the port state by specifying the port LID, perform the following steps:

---

Step 1 Type the command ib_sm_cli at the host terminal.

Step 2 List all the switch chip ports and host IB ports at the ib_sm> prompt.

Make a note of the number in the column labeled lid against port value 0. This is the switch port 0 LID. In the following output, it is 8.

The following example shows how to list the switch chip ports and host IB ports:

ib_sm> show port -s

================================================================================                          
Subnet Manager Port Summary

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

node-guid                port  lid   state      link

--------------------------------------------------------------------------------

00:18:8b:90:97:fe:06:6e  1     2     active     4x-ddr

00:18:8b:90:97:fe:06:96  1     5     active     4x-ddr

00:18:8b:90:97:fe:06:b2  1     3     active     4x-ddr

00:18:8b:90:97:fe:06:fa  1     4     active     1x-ddr

00:1b:0d:55:55:00:00:00  0     8     active     4x-sdr

.

00:1b:0d:55:55:00:00:00  15    0     down       4x-sdr

00:1b:0d:55:55:00:00:00  16    0     active     4x-ddr

.

00:1b:0d:55:55:00:00:00  24    0     down       4x-sdr

ib_sm>

Step 3 Query the state of the IB port.

To query the state of IB port 16 on the switch, the LID of the switch port 0 is required.

The following example shows how to query the state of the IB port:

host1# ibportstate 8 16 query

PortInfo:

# Port info: Lid 8 port 16

LinkState:.......................Active

PhysLinkState:...................LinkUp

LinkWidthSupported:..............1X or 4X

LinkWidthEnabled:................1X or 4X

LinkWidthActive:.................4X

LinkSpeedSupported:..............2.5 Gbps or 5.0 Gbps

LinkSpeedEnabled:................2.5 Gbps or 5.0 Gbps

LinkSpeedActive:.................5.0 Gbps

Peer PortInfo:

# Port info: Lid 8 DR path 0,16 port 1

LinkState:.......................Active

PhysLinkState:...................LinkUp

LinkWidthSupported:..............1X or 4X

LinkWidthEnabled:................1X or 4X

LinkWidthActive:.................4X

LinkSpeedSupported:..............2.5 Gbps or 5.0 Gbps

LinkSpeedEnabled:................2.5 Gbps or 5.0 Gbps

LinkSpeedActive:.................5.0 Gbps

Step 4 Disable the port.

The following example shows how to disable the port:

host1# ibportstate 8 16 disable

Initial PortInfo:

# Port info: Lid 8 port 16

LinkState:.......................Active

PhysLinkState:...................LinkUp

LinkWidthSupported:..............1X or 4X

LinkWidthEnabled:................1X or 4X

LinkWidthActive:.................4X

LinkSpeedSupported:..............2.5 Gbps or 5.0 Gbps

LinkSpeedEnabled:................2.5 Gbps or 5.0 Gbps

LinkSpeedActive:.................2.5 Gbps

After PortInfo set:

# Port info: Lid 8 port 16

LinkState:.......................Down

PhysLinkState:...................Disabled

Step 5 Verify the port state once again by querying one more time.

The following example shows how to verify the port state:

host1# ibportstate 8 16 query

PortInfo:

# Port info: Lid 8 port 16

LinkState:.......................Down

PhysLinkState:...................Disabled

LinkWidthSupported:..............1X or 4X

LinkWidthEnabled:................1X or 4X

LinkWidthActive:.................4X

LinkSpeedSupported:..............2.5 Gbps or 5.0 Gbps

LinkSpeedEnabled:................2.5 Gbps or 5.0 Gbps

LinkSpeedActive:.................2.5 Gbps

Step 6 Verify whether the port state is disabled.

The following example shows how to verify whether the port state is disabled:

ib_sm> show port -s

================================================================================                          
Subnet Manager Port Summary

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

node-guid                port  lid   state      link

--------------------------------------------------------------------------------

00:18:8b:90:97:fe:06:6e  1     2     active     4x-ddr

00:18:8b:90:97:fe:06:b2  1     3     active     4x-ddr

00:18:8b:90:97:fe:06:fa  1     4     active     1x-ddr

00:1b:0d:55:55:00:00:00  0     8     active     4x-sdr

00:1b:0d:55:55:00:00:00  1     0     down       4x-sdr

.

.

.

00:1b:0d:55:55:00:00:00  16    0     down       4x-sdr

.

.

.

00:1b:0d:55:55:00:00:00  24    0     down       4x-sdr

ib_sm>

Step 7 Issue the port enable command.

The following example shows how to issue the port enable command:

host1# ibportstate 8 16 enable

Initial PortInfo:

# Port info: Lid 8 port 16

LinkState:.......................Down

PhysLinkState:...................Disabled

LinkWidthSupported:..............1X or 4X

LinkWidthEnabled:................1X or 4X

LinkWidthActive:.................4X

LinkSpeedSupported:..............2.5 Gbps or 5.0 Gbps

LinkSpeedEnabled:................2.5 Gbps or 5.0 Gbps

LinkSpeedActive:.................2.5 Gbps

After PortInfo set:

# Port info: Lid 8 port 16

LinkState:.......................Down

PhysLinkState:...................Polling

Step 8 Verify that the port is enabled.

The following example shows how to verify that the port is enabled:

host1# ibportstate 8 16 query

PortInfo:

# Port info: Lid 8 port 16

LinkState:.......................Active

PhysLinkState:...................LinkUp

LinkWidthSupported:..............1X or 4X

LinkWidthEnabled:................1X or 4X

LinkWidthActive:.................4X

LinkSpeedSupported:..............2.5 Gbps or 5.0 Gbps

LinkSpeedEnabled:................2.5 Gbps or 5.0 Gbps

LinkSpeedActive:.................2.5 Gbps

Peer PortInfo:

# Port info: Lid 8 DR path 0,16 port 1

LinkState:.......................Active

PhysLinkState:...................LinkUp

Step 9 Verify the port state.

The following example shows how to verify the port state:

ib_sm> show port -s

================================================================================                          
Subnet Manager Port Summary

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

node-guid                port  lid   state      link

--------------------------------------------------------------------------------

00:18:8b:90:97:fe:06:6e  1     2     active     4x-ddr

.

.

.

00:1b:0d:55:55:00:00:00  16    0     active     4x-ddr

.

.

.

00:1b:0d:55:55:00:00:00  24    0     down       4x-sdr

ib_sm>

---

Port Control Using the Node GUID

This section describes port control using Node GUID.

To control the port using Node GUID, perform the following steps:

---

Step 1 Run the ib_sm_cli command at the host terminal.

Step 2 Type the show port -s command at the ib_sm> prompt.

Step 3 Obtain the Node GUID of the switch.

The following example shows how to obtain the Node GUID of the switch:

ib_sm> show port -s

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

                          Subnet Manager Port Summary

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

node-guid                port  lid   state      link

--------------------------------------------------------------------------------

00:05:ad:00:97:fe:06:e6  1     8     active     4x-ddr

.

.

.

00:1b:0d:00:00:00:ca:a6  23    0     active     4x-ddr

00:1b:0d:00:00:00:ca:a6  24    0     active     4x-ddr

00:1b:0d:55:00:00:ca:aa  0     18    active     4x-sdr

00:1b:0d:55:00:00:ca:aa  1     0     down       4x-sdr

00:1b:0d:55:00:00:ca:aa  2     0     active     4x-ddr

00:1b:0d:55:00:00:ca:aa  3     0     down       4x-sdr

.

.

.

00:1b:0d:55:00:00:ca:aa  24    0     active     4x-ddr

ib_sm> exit

It is 00:1b:0d:55:00:00:ca:aa in this example. It is the node-guid value against the switch port 0.

Step 4 Disable switch port 2.

The following example shows how to disable switch port 2:

host1# ibportstate -G 0x1b0d550000caaa 2 disable

Initial PortInfo:

# Port info: Lid 18 port 2

LinkState:.......................Active

PhysLinkState:...................LinkUp

LinkWidthSupported:..............1X or 4X

LinkWidthEnabled:................1X or 4X

LinkWidthActive:.................4X

LinkSpeedSupported:..............2.5 Gbps or 5.0 Gbps

LinkSpeedEnabled:................2.5 Gbps or 5.0 Gbps

LinkSpeedActive:.................5.0 Gbps

After PortInfo set:

# Port info: Lid 18 port 2

LinkState:.......................Down

PhysLinkState:...................Disabled

Step 5 Verify that switch port 2 is disabled.

The following example shows how to verify that the switch port is disabled:

host1# ibportstate -G 0x1b0d550000caaa 2

PortInfo:

# Port info: Lid 18 port 2

LinkState:.......................Down

PhysLinkState:...................Disabled

LinkWidthSupported:..............1X or 4X

LinkWidthEnabled:................1X or 4X

LinkWidthActive:.................4X

LinkSpeedSupported:..............2.5 Gbps or 5.0 Gbps

LinkSpeedEnabled:................2.5 Gbps or 5.0 Gbps

LinkSpeedActive:.................2.5 Gbps

---

Port Speed Control Using the Switch Port 0 LID

This section describes how to control the port speed by specifying the switch port LID.

To control port speed by specifying its LID, perform the following steps:

---

Step 1 Run the ib_sm_cli command on the host terminal.

Step 2 Type the show port -s command at the ib_sm> prompt.

This command displays all the switch chip ports and host IB ports. Make a note of the number in the column labeled lid against port value 0. It is the switch port 0 LID.

ib_sm> show port -s

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

Subnet Manager Port Summary

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

node-guid                port  lid   state      link

--------------------------------------------------------------------------------

00:18:8b:90:97:fe:06:62  1     5     active     4x-ddr

00:18:8b:90:97:fe:06:6e  1     2     active     4x-ddr

.

.

.

00:1b:0d:55:55:00:00:00  22    0     down       4x-sdr

00:1b:0d:55:55:00:00:00  23    0     active     4x-ddr

00:1b:0d:55:55:00:00:00  24    0     active     4x-ddr

ib_sm>

Step 3 Set the speed for port 23 to single data rate (SDR).

The option speed followed by number 1 sets the speed to SDR and number 2 sets the speed to double data rate (DDR).

The following example shows how to set the speed for port 23 to SDR:

host1# ibportstate 8 23 speed 1

Initial PortInfo:

# Port info: Lid 8 port 23

LinkSpeedEnabled:................5.0 Gbps

After PortInfo set:

# Port info: Lid 8 port 23

LinkSpeedEnabled:................2.5 Gbps

Step 4 Verify the set speed.

The following example shows how to verify the set speed:

host1# ibportstate 8 23 speed query

Initial PortInfo:

# Port info: Lid 8 port 23

LinkSpeedEnabled:................2.5 Gbps

After PortInfo set:

# Port info: Lid 8 port 23

LinkSpeedEnabled:................2.5 Gbps

Step 5 Set the speed for port 24 to SDR.

The option speed followed by number 1 sets the speed to SDR and number 2 sets the speed to DDR.

The following example shows how to set the port 24 speed to SDR:

host1# ibportstate 8 24 speed 1

Initial PortInfo:

# Port info: Lid 8 port 24

LinkSpeedEnabled:................5.0 Gbps

After PortInfo set:

# Port info: Lid 8 port 24

LinkSpeedEnabled:................2.5 Gbps

Step 6 Verify the set speed.

The following example shows how to verify the set speed:

host1# ibportstate 8 24 speed query

Initial PortInfo:

# Port info: Lid 8 port 24

LinkSpeedEnabled:................2.5 Gbps

After PortInfo set:

# Port info: Lid 8 port 24

LinkSpeedEnabled:................2.5 Gbps

ib_sm> show port -s

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

Subnet Manager Port Summary

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

node-guid                port  lid   state      link

--------------------------------------------------------------------------------

00:18:8b:90:97:fe:06:62  1     5     active     4x-ddr

.

.

.

00:1b:0d:55:55:00:00:00  0     8     active     4x-sdr

00:1b:0d:55:55:00:00:00  1     0     down       4x-sdr

00:1b:0d:55:55:00:00:00  2     0     active     4x-ddr

.

.

.

00:1b:0d:55:55:00:00:00  23    0     active     4x-ddr

00:1b:0d:55:55:00:00:00  24    0     active     4x-ddr

ib_sm>

---

Note Speed changes are not affected until ports undergo link renegotiation.

---

Step 7 Recycle port 23 to renegotiate the link.

Use the reset operation to renegotiate the link.

host1# ibportstate 8 23 reset

Initial PortInfo:

# Port info: Lid 8 port 23

LinkState:.......................Active

PhysLinkState:...................LinkUp

After PortInfo set:

# Port info: Lid 8 port 23

LinkState:.......................Down

PhysLinkState:...................Disabled

ib_sm> show port -s

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

Subnet Manager Port Summary

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

node-guid                port  lid   state      link

--------------------------------------------------------------------------------

00:18:8b:90:97:fe:06:62  1     5     active     4x-ddr

.

.

.

00:1b:0d:55:55:00:00:00  0     8     active     4x-sdr

.

.

.

00:1b:0d:55:55:00:00:00  23    0     active     4x-sdr

00:1b:0d:55:55:00:00:00  24    0     active     4x-sdr

ib_sm>

---

Monitoring Port Counters

If port counters are monitored when there is no Subnet Manager running on the network, the port_rcv_error counter keeps incrementing on the port where the Subnet Manager is running. This is not an operational issue. The reason these errors are registered is as follows:

Devices such as switches in an IB network generate traps on port state changes. The Subnet Manager requests the notification of port state change traps by programming the MasterSM LID in the PortInfo of the switch port 0. On detecting any port state change, the switch sends traps to the MasterSM LID, if set. The traps egress the switch on a port, if the linear forwarding table of the switch has an egress port for that LID. The traps are received by the Subnet Manager and are repressed by it.

If a Subnet Manager is terminated inadvertently, the switch still sends traps about any port state change to the MasterSM LID that was programmed by the Subnet Manager. Because there is no Subnet Manager running on the port, the traps are not repressed, and as a result, the switch continues to send traps. As the trap packets are not consumed, the buffers fill up, after which the trap packets are credited as port receive errors. When the Subnet Manager is restarted, it reads the buffers and sends a trap repress to stop the generation of traps. This stops further increment of the error counter.

---

Note The counters must be cleared after the Subnet Manager is restarted.

---

Related Documentation

For additional information about the Cisco M SFS7000E and related products and interfaces, see the following publications:

•Cisco M SFS7000E Installation Note: InfiniBand Blade Switch for the Dell Modular Server Chassis

•Regulatory Compliance and Safety Information for the Cisco M SFS7000E InfiniBand Blade Switch for the Dell Modular Server Chassis

•Dell M1000E Host Driver Software Entitlement for the Cisco M SFS7000E InfiniBand Primary Switch

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn is a service mark; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0804R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2008 Cisco Systems, Inc. All rights reserved.