Nortel Alteon Switch and Load Balancer driver

Title: Nortel Alteon Switch and Load Balancer driver for Tivoli Provisioning Manager, Version 2.1.0
Automation Package Version: 2.1.1
Technology Version:  Nortel Alteon OS
Navcode:
 

Contents

This file includes the following information:

  • 1.0 Introduction
  • 2.0 Components of this package
  • 3.0 Requirements
  • 4.0 Logical operations
  • 5.0 Planning
  • 6.0 Installation and configuration
  • 6.1 Customization
  • 7.0 Troubleshooting
  • 8.0 Uninstalling the driver
  • 9.0 Trademarks and Service Marks
     

1.0 Introduction

This file contains the latest information about installing Nortel Alteon switch and load balancer driver, as well as information about configuration and troubleshooting. This driver is for use with Tivoli Provisioning Manager, Version 2.1.0.

The  nortel_alteon.tcdriver driver supercedes existing driver: alteon-load-balancer.tcdriver”, instead use the new driver: nortel_alteon.tcdriver.  Also deprecated is existing device model “Alteon LoadBalancer, please use one of the newer device models. The new driver adds support for layer 2 functions, for example, add VLAN, move port to VLAN, etc. to existing layer 4-7 functionality.  Also, new in this driver is support for the Nortel Blade Center.  To use this driver you must uninstall the existing nortel_alteon.tcdriver, see section, 6.0 Installation and configuration, for instructions.

This driver has been tested with the following switches: Alteon 180E, and the Nortel Blade Center (see special configuration notes for the Nortel Blade Center). Software versions tested were:

·        Blade center: Software Version 20.0.1.2

·        Alteon 180E: Software Version 8.3.24.5-SSH

It is easy to add support for additional switches and load balancers from the Nortel Alteon family of switches and load balancers, see section, 6.2 Customization, below.

2.0 Components of this package

File

Description

 

 

doc/Nortel_Alteon.html

This document. Contains information on installing and configuring this orchestration package

 

 

bin/Nortel_Alteon_create_vip

Expect script to create a Virtual IP

bin/Nortel_Alteon_disable_rip

Expect Script to disable a Real IP

bin/Nortel_Alteon_enable_rip

Expect Script to enable a Real IP

bin/Nortel_Alteon_init

Expect Script to initialize a Nortel Alteon device

bin/Nortel_Alteon_remove_vip

Expect Script to remove a Real IP

 

 

workflow/Build_Nortel_Alteon_create_vip_Script_Params.wkf

Workflow used in the Create VIP workflow

workflow/Build_Nortel_Alteon_remove_vip_Script_Params.wkf

Workflow used in the Remove VIP workflow

workflow/Create_VIP_Nortel_Alteon.wkf

Workflow to create a Virtual IP

workflow/Nortel_Alteon_Add_RIP_to_VIP.wkf

Workflow to add a Real IP to a Virtual IP

workflow/Nortel_Alteon_Initialize.wkf

Workflow to initialize a Nortel Alteon device

workflow/Nortel_Alteon_Remove_RIP_from_VIP.wkf

Workflow to remove a Real IP to a Virtual IP

workflow/Remove_VIP_Nortel_Alteon.wkf

Workflow to remove a Virtual IP

 

 

workflow/Nortel_Alteon_Create_VLAN.wkf

Creates a VLAN using SNMP commands

workflow/Nortel_Alteon_Move_Port_to_VLAN.wkf

Moves a port into a VLAN

workflow/Nortel_Alteon_Turn_Port_ON.wkf

Turns on a port on the switch module

workflow/Nortel_Alteon_Remove_VLAN.wkf

Removes a VLAN from the switch module

workflow/Nortel_Alteon_Turn_Port_OFF.wkf

Turns off a port on the switch module

workflow/Nortel_Alteon_Save_To_NVRAM.wkf

Drives the script to add a port to a VLAN
This workflow is a helper workflow that is not inherited by the switch driver model.

 

 

java-plugin/com.thinkdynamics.kanaha.de.javaplugin.hardware.loadbalancers.Alteon.ActivateServer.xml

Java Plugin

java-plugin/com.thinkdynamics.kanaha.de.javaplugin.hardware.loadbalancers.Alteon.AddServerToGroup.xml

Java Plugin

java-plugin/com.thinkdynamics.kanaha.de.javaplugin.hardware.loadbalancers.Alteon.CreateRealServer.xml

Java Plugin

java-plugin/com.thinkdynamics.kanaha.de.javaplugin.hardware.loadbalancers.Alteon.DeactivateServer.xml

Java Plugin

java-plugin/com.thinkdynamics.kanaha.de.javaplugin.hardware.loadbalancers.Alteon.DeleteRealServer.xml

Java Plugin

java-plugin/com.thinkdynamics.kanaha.de.javaplugin.hardware.loadbalancers.Alteon.GetNextAvailableGroupIndex.xml

Java Plugin

java-plugin/com.thinkdynamics.kanaha.de.javaplugin.hardware.loadbalancers.Alteon.GetNextAvailableVirtualIPIndex.xml

Java Plugin

java-plugin/com.thinkdynamics.kanaha.de.javaplugin.hardware.loadbalancers.Alteon.GetRealGroupIndex.xml

Java Plugin

java-plugin/com.thinkdynamics.kanaha.de.javaplugin.hardware.loadbalancers.Alteon.GetRealServerIndex.xml

Java Plugin

java-plugin/com.thinkdynamics.kanaha.de.javaplugin.hardware.loadbalancers.Alteon.GetVirtualIPIndex.xml

Java Plugin

java-plugin/com.thinkdynamics.kanaha.de.javaplugin.hardware.loadbalancers.Alteon.RemoveServerFromGroup.xml

Java Plugin

java-plugin/com.thinkdynamics.kanaha.de.javaplugin.hardware.loadbalancers.Alteon.SaveConfiguration.xml

Java Plugin

java-plugin/com.thinkdynamics.kanaha.de.javaplugin.hardware.loadbalancers.Alteon.SaveConfigurationOnUndo.xml

Java Plugin

java-plugin/com.thinkdynamics.kanaha.de.javaplugin.hardware.loadbalancers.Alteon.SetBalancingAlgorithm.xml

Java Plugin

 

 

XML/Nortel_Alteon-BC.xml

Sample XML file to define a Nortel Alteon Blade Center switch and load balancer

XML/Alteon180E.xml

Sample XML file to define a Nortel Alteon 180E switch and load balancer

3.0 Requirements

  • Tivoli Provisioning Manager, Version 2.1.0.
  • One or more switches from the Nortel Alteon switch family.

4.0 Logical operations

This driver uses the following logical operations associated with the device model:

Ethernet Switch device models

Logical operation

Description

Device.Initialize

Initializes a device.

Switch.Create VLAN

Creates a VLAN on a switch.

Switch.Remove VLAN

Removes a VLAN from a switch.

Switch.Turn Port ON

Turns on a switch port.

Switch.Turn Port OFF

Turns on a switch port.

Switch.Move Port to VLAN

Moves a switch port from one VLAN to another.

 

Load Balancer device models

Logical operation

Description

Device.Initialize

Device initialization for Nortel Alteon Load Balancer

LoadBalancer.Create Virtual IP

Creates a new Virtual IP on a device

LoadBalancer.Remove Virtual IP

Removes a Virtual IP from a device

LoadBalancer.Add Real IP to Virtual IP

Creates a new Real IP on a device

LoadBalancer.Remove Virtual IP

Removes a Real IP from a device

5.0 Planning

Within Tivoli Provisioning Manager, systems and their components are represented by Data Center Model (DCM) objects. DCM Objects are instances of DCM device types. For each DCM device type a set of attributes and a set of logical operations is defined. Logical operations are implemented by workflows. A workflow is a sequence of operations. Each operation can be a basic operation on a device, an invocation of another workflow or an invocation of another logical operation on the same or on another device.

For each type of system which is to be managed by Tivoli Provisioning Manager, the DCM model needs to adapt so that it can represent and operate on devices which are available within that type of system. The adaptation of the DCM model is done by adding variables to involved DCM types and by providing implementations for their logical operations in form of workflows. The basic operations of these workflows finally control devices associated with that type of system in a system type specific way.

Consequently in order to introduce a new type of system into Tivoli Provisioning Manager and use it to manage a particular instance of that new system type (which will be called the "target system" below) three things need to be done:

  1. Install the tcdrivers that provide the workflows to implement the logical operations associated with devices available in that system type. This may include installing some means of system type specific operational interface to realize system type specific basic steps of associated workflows.
  2. Prepare the target system. This might involve tasks like preconfiguring the target system for example,
       by providing preconfigured operating system images or by establishing proper authorization for basic operations.
  3. Define a set of DCM objects to represent the assets available in the target system.

6.0 Installation and configuration

This section provides instructions for installing nortel_alteon.tcdriver, a new tcdriver that provides L2 and L4 functionality for the Nortel Alteon line of switches and load balancers.  Before installing the new driver you must first uninstall existing driver: alteon-load-balancer.tcdriver.  If you do not have alteon-load-balancer.tcdriver installed you can skip to step 5.

Step 1

Check if the driver is used in the data center.

 

Start from the main page of TIO

·        In the left pane click on

o       System Configuration and workflow management tab

·        In the left pane

o       Expand the entry for Device Drivers

o       Expand the entry for Network Appliances

o       Chose Alteon LoadBalancer

·        In the right pane choose the following Tab

o       References

·        Look in the Device Names section,

o       If you see a device name listed, note the name of the device listed and continue on to step 2.

o       If you do not see a device name listed continue on to step 3.

Step 2

Remove references to the old driver.

 

Start from the main page of TIO

o       In the left pane click on

o       Click the Data center assets and resources tab

o       In the left pane

o       Expand the Inventory tab

o       Expand the Load Balancers tab

o       Then choose the device name you noted in step 1.

o       In the right pane, choose the Workflows tab

o       Scroll down to the section that has heading Device Driver

o       In the roll-down menu change the assignment to read “not assigned” and click on the tab that has label “Change Device Driver”.

o       Verify that your changes have been accepted.  This is done by repeating step 1, at the end of step 1 you should not see any devices listed in the References tab.

Step 3

Close all TIO browser windows and stop TIO

Step 4

Uninstall the current driver. 

o       Open a Shell or DOS window depending on your environment

o       Change to one of the following directories depending on your environment:

o       $TIO_HOME/tools

o       %TIO_HOME%\tools

o       Run one of the following commands depending on your environment:

o       ./tc-driver-manager.cmd listallstr

o       ./tc-driver-manager.sh

o       You should see:

alteon-load-balancer                    2.1.0   installed

o       Run one of the following commands depending on your environment:

o       ./tc-driver-manager.cmd uninstalldriver alteon-load-balancer

o       ./tc-driver-manager.sh uninstalldriver alteon-load-balancer

o       You should see:

Un-installation successful. (Driver name:alteon-load-balancer)

Step 5

Install new driver

  • Copy new driver (Nortel_Alteon.tcdriver) to one of these 2 directories depending on your environment:
    • $TIO_HOME/drivers
    • %TIO_HOME%\drivers
  • Rename the old tcdriver, for example: alteon-load-balancer.tcdriver_ORG
  • Rename the following file in the $TIO_HOME/drivers/lib/alteon-load-balancer.jar_OLD
  • Run the following command
    • ./tc-driver-manager.cmd installdriver ../drivers/Nortel_Alteon.tcdriver

Verify, you should see the following

    • Installation successful. (Driver name:../drivers/Nortel_Alteon.tcdriver)

Step 6

Restart TIO.  If no device names from step #1 were found, you are done, otherwise continue with step 7.

Step 7

Use the new device driver

o       In the left pane click on

o       Click the Data center assets and resources tab

o       In the left pane

o       Expand the Inventory tab

o       Expand the Load Balancers tab

o       Then choose the device name you noted in step 1.

o       In the right pane, choose the Workflows tab

o       Scroll down to the section that has heading Device Driver

o       In the roll-down menu change the assignment to read “Alteon LoadBalancer 180E” and click on the tab that has label “Change Device Driver”.

o       Verify that your changes have been accepted.  This is done by repeating step 1, at the end of step 1 you should see your device listed in the References tab.

Step 8

Verify that your changes have been accepted. 

In the left pane of the welcome screen, click on

·        System Configuration and workflow management tab

In the left pane choose

·        Device Drivers,

·        Then choose Network Appliances

·        Then chose Alteon LoadBalancer 180E

In the right pane choose the following Tab

·        References

Look under the Device Names section, you should see your device listed. 

 

 

You are done with the installation part.

6.1.1 Adding Nortel devices to TIO

Two sample files are provided and can be used as templates for adding the Nortel Alteon switch/load balancers to your datacenter.

·        XML/Nortel_Alteon-BC.xml

·        XML/Alteon180E.xml

These are available in the $TIO_HOME or %TIO_HOME% directories depending on your environment.

 

6.1.1 Configuration of the Nortel Alteon Blade Center

The following presumes that you have used the IBM and Nortel documentations to configure the Blade Center for IP and SNMP and that connectivity exists between TIO and the Blade Center.

 

For each Switch Module installed in a single Blade Center chassis, represent the switch as separate switch device in IBM Tivoli Intelligent ThinkDynamic Orchestrator (ITTIO).

Each switch module has 18 ports in total; these are divided into three categories of ports:

  • Ports 1-14 are assigned to the internal bays for each of the blades and show up as INT1-INT14 when using the CLI
  • Ports 15-16 are represented as Management ports and show up as MGT1-MGT2 when using the CLI
  • Ports 17-20 are represented as External ports and show up as EXT1-EXT2 when using the CLI

 

The XML file used to represent the Blade Center defines the three categories as separate modules:

  • Internal module is used to refer to ports INT1-INT14
  • Management module is used to refer to ports MGT1-MGT2; no operations are supported on these ports.
  • External module is used to refer to ports EXT1-EXT4

 

When using the workflows, it is important to refer to the ports exactly as they are defined in TIO, otherwise due to case-sensitivity some of the operations may not work as expected.

6.2 Customization

To customize this driver you will need to find the appropriate OIDs for your device model.

 

Use Alteon 180E as a reference point and populate the following tables for your particular device model:

Switch OIDs

Variable

OID for Alteon 180E

OID for your device model

agApplyConfiguration  

1.3.6.1.4.1.1872.2.1.2.1.2.0

 

agPortNewCfgState    

1.3.6.1.4.1.1872.2.1.2.3.3.1.4

 

agSaveConfiguration    

1.3.6.1.4.1.1872.2.1.2.1.1.0

 

vlanNewCfgAddPort   

1.3.6.1.4.1.1872.2.1.4.3.1.6

 

vlanNewCfgDelete      

1.3.6.1.4.1.1872.2.1.4.3.1.8

 

vlanNewCfgRemovePort         

1.3.6.1.4.1.1872.2.1.4.3.1.7

 

vlanNewCfgVlanName

1.3.6.1.4.1.1872.2.1.4.3.1.2

 

 

Load Balancer OIDs

Variabl

OID for Alteon 180E

OID for your device model

agApplyConfiguration

1.3.6.1.4.1.1872.2.1.2.1.2.0

 

agReset

1.3.6.1.4.1.1872.2.1.2.1.4

 

agSaveConfiguration

1.3.6.1.4.1.1872.2.1.2.1.1.0

 

slbCurCfgGroupIndex

1.3.6.1.4.1.1872.2.1.5.10.1.1

 

slbCurCfgVirtServIndex

1.3.6.1.4.1.1872.2.1.5.7.1.1

 

slbCurCfgVirtServerIndex

1.3.6.1.4.1.1872.2.1.5.5.1.1

 

slbCurCfgVirtServerIpAddress

1.3.6.1.4.1.1872.2.1.5.5.1.2

 

slbCurCfgVirtServiceRealGroup

1.3.6.1.4.1.1872.2.1.5.7.1.4

 

slbNewCfgGroupAddServer

1.3.6.1.4.1.1872.2.1.5.11.1.3

 

slbNewCfgGroupMetric

1.3.6.1.4.1.1872.2.1.5.11.1.5

 

slbNewCfgGroupRemoveServer

1.3.6.1.4.1.1872.2.1.5.11.1.4

 

slbNewCfgRealServerDelete

1.3.6.1.4.1.1872.2.1.5.3.1.11

 

slbNewCfgRealServerIpAddr

1.3.6.1.4.1.1872.2.1.5.3.1.2

 

slbNewCfgRealServerState

1.3.6.1.4.1.1872.2.1.5.3.1.10

 

slbRealServerMaxSize

1.3.6.1.4.1.1872.2.1.5.1.0

 

 

 

Once you have the values for the above variable you will need to follow the following steps:

·        Create a new device model using GUI (system configuration and workflow management ->Device Drivers ->Network Appliances, do not use the subcategory tab)

·        Add workflows to the device model

·        Add a property for each OID above under the variables tab

7.0 Troubleshooting

For all errors during the install of nortel_alteon tcdriver, Refer to the following log files in %TIO_HOME%/logs/tcdrivermanager

  • console.log, error.log for general error messages
  • objectDump.xml for finding the objects that failed to get to the database

By default, debug messages are not copied to the log files. To get more log file information, change the setting on %TIO_HOME%/config/log4j.prop to:

  • log4j.appender.errorfile.threshold=debug
  • log4j.appender.consolefile.threshold=debug

If the SNMP Set Request transition fails with an Exception error, the SNMP configuration isn't set correctly. Double check the settings in TIO with the actual settings of the switch.

 8.0 Uninstalling the driver

To uninstall the driver:

  1. Change the directory to %TIO_HOME%/tools
  2. Run tc-driver-manager.cmd uninstallDriver nortel_alteon. On non-Windows systems, run the tc-driver-manager.sh command.

 9.0 Trademarks and Service Marks

The following are trademarks or registered trademarks of IBM Corporation in the United States and other countries:

IBM   Tivoli     

Other company, product, or service names may be trademarks or service marks of others. **************************************************************************

** COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 2004

** ALL RIGHTS RESERVED.

**************************************************************************

Note to US Government Users -- Documentation related to restricted rights --
Use, duplication, or disclosure is subject to restriction set forth in GSA ADP Schedule Contract with IBM Corp.