LevelBlue Knowledge Base » Knowledgebase » Legacy Products » Secure Web Gateway » Hardware » NG-8000

End of Life Notice: SWG7000 models based on IBM HS22 series

ofer Kalef — Sun, 10 Feb 2013 02:46:28 GMT

This article applies to:

Secure Web Gateway (SWG)

Information:

According to IBM announcement on the discontinuation of the HS22 7870, Trustwave releases this EOL notice for the following models:

SWG 7100 (NG8100-S1)
SWG 7080 (NG8080-S1)
SWG 7610 (SE 8610-S1)

This Product End of Life Notice is effective as of November 26, 2015.

Notes:

The HS22 models will be replaced by IBM HS23 models.

Building the IBM Bootable Media Creator

ofer Kalef — Mon, 24 Dec 2012 00:11:12 GMT

Question:
How can I build the Bootable Media Creator, which is used to update the IBM firmware and run hardware diagnostics on Secure Web Gateway (SWG) appliances?

Answer:
Sometimes it is necessary to upgrade firmware versions or to collect specific logs from IBM-based SWG appliances (including blades). The instructions below describe the process of creating the Bootable Media Creator that is used in Firmware upgrades and DSA log retrieval from IBM appliances.

Before beginning the procedure, please use the link below to download the Bootable Media Creator tool.

http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=MIGR-5079823

Once the download is complete, double click the utility in order to launch it. The steps below are a screen-by-screen walkthrough of the utility.

Welcome - There is no required text for the descriptive name on the Welcome screen; you may choose any name you like or leave the default. Click Next.
Media Purpose - select Upgrades and Diagnostics. The rest should be unchecked. Click Next.
Acquire Location - use the Check the IBM web site with the UpdateXpress System Packs (UXSP’s) option. Click Next.
Targeted Systems – Select the exact IBM machine type of the appliance. For example, the first generation NG-6000 is a System X3650 – 7979. Note that more than one type of system can be selected. It is recommended to only select the systems that require Firmware updates or DSA log retrieval in order to ensure that all of the content can fit on a single disc.
HTTP Proxy - Select any Proxy information the software might need to use to download the proper updates. Proxy options are based on your current network settings; you may not need to use them. In that case, just select “Do not use proxy”. Click Next.
Target Directory - This the location the downloaded files will be saved on the PC. Click Next.
Media Format – Select Device Type: CD/DVD and Write directly to Device. Select the Disk drive your recordable CD/DVD is in. (You may use the Write to Image File if your CD/DVD is not ready and wish to save the ISO file to the computer to burn at a later time.) Click Next.
Confirm Choices – Verify that the systems, directories, update type are correct and any additional settings needed to access the internet. (There is also an option at the bottom to save the current configuration. This can be used if you chose to stop and come back later or if you require using these settings again to create additional boot disks at a later time.) Click Next.
Creation Process – The tool will now download and burn the CD/DVD (or create a Bootable .ISO image if Write to Image File was selected). Download times will vary based on how many systems were selected. Approximate time for one system is 20 minutes. Click Next.
Burn the ISO image onto a CD or DVD if you did not chose to burn the disk in Step 7. Once the image has been burned onto a CD or DVD the disk should be ready to use for the IBM system.

Software Versions:
all

How to reset a SWG7000 Advanced Management Module

Rudolf Kessler — Fri, 22 Jun 2012 06:39:27 GMT

This article applies to:

SWG 7000
AMM (Advanced Management Module)

Question:

How can I reset the settings of an AMM?

Procedure:

The management module reset button is shown in the following figure.

Use a straightened paper clip or similar item to access it. The reset button has two uses:

Reset the network configuration: Press and hold the reset button for 3 seconds or less.
Reset the entire management module (including user IDs and passwords) to the factory defaults. This requires a sequence of presses and releases:
- Press and hold the reset button for 5 seconds.
- Release the button and wait 5 seconds.
- Press and hold the button for another 10 seconds.
Note that this sequence should be as precise as possible to ensure success: 5 in, 5 out, 10 in. After you do a full factory defaults reset in this way, the default user ID and password will be in effect: USERID (all caps) and PASSW0RD (a zero, not the letter O).

After the network configuration has been reset, you can access the Web interface to reconfigure it. To do this, you will need to know the management module's IP address. This can be done as follows:

The management module defaults to using DHCP. The host name will be MMxxxxxxx, where xxxxxxx is the MAC address of the management module. This number is printed below the reset button.
If no DHCP server is found, the management module uses a default IP address of 192.168.70.125 with subnet mask 255.255.255.0. The host name will be MMxxxxxxx.

Notes:

Because it is possible to reset the passwords using the reset button, you should ensure that your BladeCenter chassis is physically secure so that only authorized personnel can physically access the reset button.

Source: IBM @ http://www.redbooks.ibm.com/abstracts/tips0519.html

BladeCenter Power Consumption Chart

Yossi Porat — Tue, 13 Oct 2009 00:00:00 GMT

Please see the Excel workbook

This article applies to:: NG 8000

This article was previously published as:: Finjan KB 1926

IBM BladeCenter HS22 Technical Introduction

Yossi Porat — Tue, 13 Oct 2009 00:00:00 GMT

This article applies to:
NG 8000
This article was previously published as:
Finjan KB 12607

No connection available after connecting BladeCenter Copper Pass-thru Module

support finjan — Fri, 27 Mar 2009 00:00:00 GMT

Description
After installing the Pass-thru Module as instructed by the installation guide, each blade's eth0 interface begins to go up and down in a loop.

Symptoms
The following error messages apear in the blade's console output:
"eth0 NIC link is up, 1000 Mbps full duplex
eth0 NIC link is down"
No connection could be made to and from the blades.
The power LED of the Pass-thru Module is on and the error LED is not lit.
After connecting the copper pass-thru module cable to the network "no Link OK LED" is lit!
The management event log does not show any error related to the Pass-thru Module and its status seems to be OK.

Cause
The BladeCenter Copper Pass-thru Module can only work with 1GB switch.

Solution
Make sure you are using the BladeCenter Copper Pass-thru Module with 1GB switch.

This article applies to:
NG 8000
This article was previously published as:
Finjan KB 1091

Blade Server Firmware Upgrade Process

support finjan — Fri, 27 Mar 2009 00:00:00 GMT

This article applies to:
NG 8000
This article was previously published as:
Finjan KB 1110

How to Change Port Settings on an NG-8000

support finjan — Fri, 27 Mar 2009 00:00:00 GMT

This article applies to:
NG 8000
This article was previously published as:
Finjan KB 1113

Blade does not boot completely due to Media Tray

support finjan — Fri, 27 Mar 2009 00:00:00 GMT

Question
Why might a blade not boot completely when it is connected to the NG-8000's media tray?

Answer
The NG-8000's media tray may lose focus with a particular blade. This can sometimes occur after a power outage. It could also indicate that the media tray is not properly seated.

If the media tray's connection is incomplete, it may be impossible for the blade to properly identify the media tray during boot-up, and this can result in an incomplete boot cycle. This will only happen on a blade that is currently connected to the media tray. The simplest solution is to connect the media tray to a different blade and reboot the affected blade. However, if the media tray is not seated well, this behavior could return.

The media tray is hot-swappable, so it can be reseated while the system in online. First, the NG-8000's front bezel should be removed by simultaneously pressing in on the blue plastic tabs on its bottom left and right sides and then pulling the bezel forward. Next, the media tray itself can be removed by simultaneously pressing in on the metal tabs behind the orange labels on either side of the media tray and pulling. It is recommended that any dust that has accumulated on the media tray be clean while it is removed. Reconnecting the media tray is simply a matter of snapping it back into place, followed by replacing the front bezel of the chassis.

After reinsertion, it is recommended that the media tray be switched to a different blade using the media tray button on the front of each blade. If necessary, the media tray can be returned to the original blade. Switching the media tray to a different blade will help it reinitialize its connection to the blades.

This article applies to:
NG 8000
This article was previously published as:
Finjan KB 1264

Load Balancing Configuration with NG-8040

support finjan — Fri, 27 Mar 2009 00:00:00 GMT

This article applies to:
NG 8000
This article was previously published as:
Finjan KB 1418

What kind of cable do I need for the 8040 Serial Console?

support finjan — Fri, 27 Mar 2009 00:00:00 GMT

Question
What kind of cable do I need for the 8040 serial console (loadbalancer switch)?

Answer
The original IBM cable has the part number (P/N) 32R1803.
It has a SubD9 jack (female) on PC side, and a SGI miniDIN jack (male, non-center-pin) on switch side:

SubD9 jack (female)

SGI miniDIN jack (male, non-center-pin)

The wire assignment is as follows:

Software Version
N/A

This article was previously published as:
Finjan KB 1472

How to Access the NG-8040 L2-7 Switch

support finjan — Fri, 27 Mar 2009 00:00:00 GMT

Description
External management access to the NG-8040 layer 2-7 switch has to be enabled through the Chassis Management Console.

Symptoms
Web GUI, telnet or secure shell connections cannot be established.

Cause
External access is disabled by default and has to be enabled explicitly.

Solution
In the Blade center management console select I/O module tasks -> Configuration
Navigate to the relevant bay (the slot where the L2-7 switch is installed) and select "Advanced Configuration"
Enable "External management over all ports" in the section "Advanced Setup" and save this setting.

Now it is possible to access the switch through web GUI, telnet or SSH, if configured.

Software Version
N/A

This article applies to:
NG 8000
This article was previously published as:
Finjan KB 1551

Configuring Nortel Gigabit Ethernet Switch in Cisco Environment

Amir Foox — Fri, 27 Mar 2009 00:00:00 GMT

This article applies to:
NG 8000
This article was previously published as:
Finjan KB 1791