BladeSystem - General
1752578 Members
4786 Online
108788 Solutions
New Discussion

Query on HP StorageWorks 3Gb SAS Blade Interconnect Switch

 
chuckk281
Trusted Contributor

Query on HP StorageWorks 3Gb SAS Blade Interconnect Switch

Kaleem had an interesting question about accessing the the SAS switch on a blade chassis.

 

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

Can someone tell me whether we can access HP StorageWorks 3Gb SAS Blade Interconnect Switch Via Telnet.

 

As per the user guide, its only mentioned about SSH connection. Customer is able to access via SSH & not able to access Via Telnet.

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01956986/c01956986.pdf?jumpid=reg_R1002_USEN

 

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

 

Brian had a solution to the question.

 

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

You could telnet into the OA and then connect to it via the virtual serial port....

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

 

Any other suggestions? Have you done this and been successful? Let us know please.

1 REPLY 1
chuckk281
Trusted Contributor

Re: Query on HP StorageWorks 3Gb SAS Blade Interconnect Switch

Monty also had some good stuff on this subject:

 

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

 

The 3Gb SAS Interconnect uses the OA for IP address, user authentication and roles.

This means that any GUI access is done after logging into the OA.  For telnet or SSH access you can use the 3Gb SAS interconnect a serial port to the OA from the OA CLI “connect interconnect” command.

 

See my example below – connecting to the 3GB SAS Interconnect in bay 4.

 

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

 

OA-0016355E9637> show interconnect list

 

Bay Interconnect Type     Manufacturer      Power   Health   UID  Management IP

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

  1 Ethernet          HP                   On      OK        Off 10.128.100.1

  2 Ethernet          HP                   On      OK        Off 10.128.100.2

  3 [Absent]

  4 SAS                 HP                   On      OK        Off 10.128.100.4

  5 Fibre Channel     HP                   On      OK        Off 10.128.101.5

  6 [Absent]

  7 Ethernet          Cisco Systems, Inc.  On      OK        Off 0.0.0.0

  8 Fibre Channel     Cisco                On      OK        Off 10.128.1.50

Totals: 6 interconnect modules installed, 6 powered on.

 

OA-0016355E9637> connect interconnect 4

 

NOTICE: This pass-thru connection to the integrated I/O console

is provided for convenience and does not supply additional access

control.  For security reasons, use the password features of the

integrated switch.

 

Connecting to integrated switch 4 at 115200,N81...

Escape character is '<Ctrl>_' (Control + Shift + Underscore)

 

Press [Enter] to display the switch console:

 

 

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

WARNING: This is a private system.  Do not attempt to login unless you are an

authorized user.  Any authorized or unauthorized access and use may be moni-

tored and can result in criminal or civil prosecution under applicable law.

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

 

VSM-0016358233B3 login: Administrator

Password:

 

HP Virtual SAS Manager CLI 2.0-20.0 (SEP FW 2.12)

 

 

=> help

 

CLI Syntax

   A typical  CLI command line consists of three parts: a target device,

   a command, and a parameter with values if necessary. Using angle brackets to

   denote a required variable and plain brackets to denote an optional

   variable, the structure of a typical CLI command line is as follows:

 

      <target> <command> [parameter=value]

 

   <target> is of format:

      [bladeenclosure all|chassisname="AAA"|serialnumber=#|

      [bladeenclosure serialnumber=# bladebay all|#]

      [bladeenclosure serialnumber=# switch all|[local|remote|wwid]

      [bladeenclosure serialnumber=# storageenclosure all|[#]

      [bladeenclosure serialnumber=# zonegroup all|#]

   Example targets:

      bladeenclosure all

      bladeenclosure serialnumber=USE7083CW8

      bladeenclosure chassisname=ABC

      bladeenclosure serialnumber=USE7083CW8 bladebay 1

      bladeenclosure serialnumber=USE7083CW8 switch Local

      bladeenclosure serialnumber=USE7083CW8 storageenclosure 123456

      bladeenclosure serialnumber=USE7083CW8 zonegroup 32

 

For detailed command information type any of the following:

   help add

   help create

   help delete

   help diags

   help flash

   help modify

   help network

   help rescan

   help reset

   help shorthand

   help show

   help shownetwork

   help showsyslog

   help target

 

All changes are made on a transaction basis. Therefore you must indicate when

you are starting, saving, or clearing your changes using the following commands

   startupdate, saveupdate, and clearupdate

 

For detailed command information type any of the following:

   help clearupdate

   help startupdate

   help saveupdate

 

Help also accepts commonly used CLI parameters and  keywords. Adding

additional keywords will further filter the help output. Examples:

   help <keyword> <keyword> ... <keyword>

 

 

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

 

And another point: 

Since you are using the OA to access the 3GB SAS module, if the OA telnet support is disabled – you will not be able to access the 3Gb SAS Interconnect nor the OA.

 

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

 

Good stuff from Monty. Does this help?? Let us know..