Skip Navigation Links | |
Exit Print View | |
Sun Network QDR InfiniBand Gateway Switch HTML Document Collection for Firmware Version 2.1 |
USB Management Connector and Pins
Preparing to Install the Gateway
Suggested Tools for Installation
Antistatic Precautions for Installation
Verify Shipping Carton Contents
Assemble the Optical Fiber Data Cables
Install the Gateway in the Rack
Verifying the InfiniBand Fabric
Network Management Troubleshooting Guidelines
Understanding Routing Through the Gateway
Understanding Administrative Commands
Administering the I4 Switch Chip
Controlling the I4 Switch Chip
Administering the Subnet Manager
Controlling the Subnet Manager
Configuring Secure Fabric Management
Administering the InfiniBand Fabric
Monitoring the InfiniBand Fabric
Controlling the InfiniBand Fabric
Administering Gateway Resources
Installing Gateway Supportive Software (Linux)
Creating VNICs Under Gateway Manual Mode (Linux)
Creating VNICs Under Host Manual Mode (Linux)
Creating Virtual IO Adapters (Oracle Solaris)
Controlling Gateway Ports and Parameters
Understanding Oracle ILOM on the Gateway
Understanding Oracle ILOM Targets
Administering Oracle ILOM (CLI)
Accessing Oracle ILOM From the CLI
Switching Between the Oracle ILOM Shell and the Linux Shell
Monitoring Oracle ILOM Targets (CLI)
Controlling Oracle ILOM Targets (CLI)
Upgrading the Gateway Firmware Through Oracle ILOM (CLI)
Administering Oracle ILOM (Web)
Access Oracle ILOM From the Web Interface
Monitoring Oracle ILOM Targets (Web)
Controlling Oracle ILOM Targets (Web)
Upgrade the Gateway Firmware (Web)
Accessing the Rear Panel Diagram
Accessing Status Pane Information
Monitoring Parameters and Status
Administering Oracle ILOM (SNMP)
Monitoring Oracle ILOM Targets (SNMP)
Controlling Oracle ILOM Targets (SNMP)
Display the Sensor States (IPMI)
Display the Sensor Information (IPMI)
Display the System Event Log (IPMI)
Display FRU ID Information (IPMI)
Display Gateway Status LED States (IPMI)
Disable the Locator LED (IPMI)
Understanding Oracle ILOM Commands
Identify Faults in the Oracle ILOM Event Log
Determining the Alarm State of a Component or System
Understanding Service Procedures
Antistatic Precautions for Service
Determine If a Power Supply Is Faulty
Determine If the Battery Is Faulty
Remove the Gateway From the Rack
Understanding Hardware Commands
Linux Shells for Hardware Commands
Understanding InfiniBand Commands
Linux Shells for InfiniBand Commands
Understanding the SUN-DCS-IB-MIB MIB OIDs
Understanding the SUN-FABRIC-MIB MIB OIDs
Understanding the SUN-HW-TRAP-MIB MIB OIDs
Understanding the SUN-ILOM-CONTROL-MIB MIB OIDs
Understanding the SUN-PLATFORM-MIB MIB OIDs
Creates a LAG.
createlag lagname [-discoverpkey p_key][-datasl sl][-lacpmode active|passive|static][-distribution MAC-ONLY|IP-ONLY|TCP-IP|Default][-n][connector1 [connector2 [...connectorN]]][-vniclimit 1|4][-h]
where:
lagname is the identifier of the LAG.
p_key is the discovery partition key (1 to 7fff or default).
sl is the data service level.
Note - Use service level 1 (sl 1) only for low-latency, high-priority, small-message, low-bandwidth traffic. Use other service levels for regular, high-bandwidth traffic.
connector1 is the name of the first connector to be added to the LAG (0A-ETH-1 to 0A-ETH-4 and 1A-ETH-1 to 1A-ETH-4).
connectorN is the name of the last connector to be added to the LAG (0A-ETH-1 to 0A-ETH-4 and 1A-ETH-1 to 1A-ETH-4).
This hardware command creates a LAG for maximizing Ethernet bandwidth. You specify which connectors are to belong to the LAG.
Note - If a VNIC has been assigned to a connector, that connector cannot be added to a LAG until the respective VNIC has been deleted.
The createlag command supports the Link Aggregate Control Protocol (LACP) and permits network devices to auto-negotiate link bundling by sending LACP packets to peers which also implement LACP.
The LAG and associated VNICs are discovered by host drivers in the default or other partition that has been configured with the default discovery P_Key. By defining a LAG-specific discovery P_Key, the visibility is restricted to hosts configured with the same discovery P_Key. The gateway must be a full member of the discovery partition, and the hosts must be at least limited members. The discovery P_Key does not need to be the same as the partition used for data traffic, and different VLANs can still be associated with different partitions for data traffic.
You can create a Global Gateway by not specifying any connectors for the LAG.
Note - You can create a maximum of 16 Global Gateways per gateway.
The createlag command is available from the /SYS/Gateway_Mgmt and /SYS/Fabric_Mgmt Linux shell targets of the Oracle ILOM CLI interface.
This table describes the options to the createlag command and their purposes.
|
This example shows how to create a LAG with name test using the createlag command.
FabMan@gateway_name->createlag test 0A-ETH-1 0A-ETH-2 Lag created FabMan@gateway_name->