Oracle Exalogic Elastic Cloud X2-2 Hardware
 
Oracle Exalogic Elastic Cloud Software
 
Oracle Exalogic Elastic Cloud X2-2 Full Rack
 
Oracle Exalogic Elastic Cloud X2-2 Qtr Rack
 
Oracle Exalogic Elastic Cloud X2-2 Half Rack
 

PLA-Support>Database Technology>Engineered Systems>Oracle Exalogic>MW: Exalogic Core
 

Exalogic Gateway Instance Check REQUIRED in Multirack scenarios.

In this Document

Purpose

Troubleshooting Steps

Oracle Confidential (PARTNER). Do not distribute to customers.
Reason: For FE's /PARTNER consumption ONLY.

Applies to:

Purpose

The purpose of this document is to outline an Gateway Switch issue that has been discovered with multiracking the Exalogic X-2 rack.

Troubleshooting Steps

This issue is isolated to the following Switch:

Sun Network QDR InfiniBand Gateway Switch (Sun NM2-GW )

Documentation:

http://download.oracle.com/docs/cd/E19671-01/index.html

This switch consists of following ports:

(32x) QDR InfiniBand ports (BASE-T)
(8x) 10GbE ports
(1x) GbE management port (BASE-T)

The gateway is a full, 32-port QDR InfiniBand switch which is redundantly deployed in each Exalogic rack. It consists of 8, 10GbE ports bridged (not switched) to the IB fabric.

This serves two roles in Exalogic:
1) Core InfiniBand switching function on all IB-connected components are switched through these.
2) Connectivity to datacenter 10GbE client network

Issue:

When installing an Exalogic system, the installer must check all the gateway switch
instance numbers (NM2-GW) in the fabric to make sure the automatic setup
assigned different instance numbers for each switch. The instance numbers must be
different. If two switches in the fabric share the same instance number, the system
can't tell which one in the network it is monitoring and will run the fans at full speed
to prevent over temp situations. This situation is most important when connecting
two or more Exalogic systems.

The switches must not use consecutive numbers. The recommendation is to use
even numbers. From the factory – the rack will use the numbers 10, 20, 30, 40 for
the switches in a full rack and 10, 20 for the smaller configurations. Use this
schema if you have to make changes.

On Rack 1, GW1 display which number is in use.

Example:

[root@elx2cn01-gw ~]# setgwinstance --list
No BXM system name set, using 6 last bits of the ip-address, value: 25

If Rack 1, GW1 is not 10, then set it to 10 following the factory scheme:

Example:

[root@elx2cn01-gw ~]# setgwinstance 10
Stopping Bridge Manager..-. [ OK ]
Starting Bridge Manager. [ OK ]
[root@elx2cn01-gw ~]# setgwinstance --list
BXM system name set to 10

If Rack 1, GW2 is not 20, then login to Rack1 GW2 and set it to 20:

Example:
[root@elx2cn02-gw ~]# setgwinstance --list
No BXM system name set, using 6 last bits of the ip-address, value: 26
[root@elx2cn02-gw ~]# setgwinstance 20
Stopping Bridge Manager..-. [ OK ]
Starting Bridge Manager. [ OK ]
[root@elx2cn02-gw ~]# setgwinstance --list
BXM system name set to 20

If Rack 1, GW3 is not 30, then login to Rack 1, GW3 and set it to 30.

If Rack 1, GW4 is not 40, then login to Rack 1, GW4 and set it to 40.

If Rack 2, GW1 is not 10+2, then set it to 12.

If Rack 2, GW2 is not 20+2, then set it to 22.

If Rack 2, GW3 is not 30+2, then set it to 32.

If Rack 2, GW4 is not 40+2, then set it to 42.

This solution has no attachment