Posts Tagged ‘IBM’

Installazione di un server IBM periferiche non conosciute


2010
02.18
Installo uns erver IBM e appaiono
IBM Active PCI Device
ACPI\IBM37D4\2&DABA3FF&0
e:
ASF Table
ACPI\ASF0001\2&DABA3FF&0

un documento di IBM MIGR-43764 ci segnala un package di driver da installare aggiungete poi  anche questo pacchetto qui

Il documento Installing Microsoft Windows Server 2003 version 1.0 – Servers MIGR-51940,è chiarificatore

Credits: http://www.108.bz/

Vmware Acquisisce Zimbra


2010
01.13

Leggo da qui

che Vmware acquisisce Zimbra.

Prima Springsource e ora ZImbra il mondo Vmware diviene sempre più verticale e comincia mattone dopo mattone ad assomigliare ad altri 3 personaggi che già conosciamo.

Un immagine vale molto di più delle mie futili parole.

IBM DS 3400 / 3200 Default IP address


2009
09.07

The defaults are 192.168.128.101 and 102.

SNMP IBM RSA/RSA II


2009
08.26
Temperature RSA/RSA II

 .1.3.6.1.4.1.2.3.51.1.2.1.2.1.1  CPU1
 .1.3.6.1.4.1.2.3.51.1.2.1.2.2.1  CPU2
 .1.3.6.1.4.1.2.3.51.1.2.1.2.3.1  CPU3
 .1.3.6.1.4.1.2.3.51.1.2.1.2.4.1  CPU4
 .1.3.6.1.4.1.2.3.51.1.2.1.5.1.0  Ambiente

Ventole RSA/RSA II
(da 1 a 12)
.1.3.6.1.4.1.2.3.51.1.2.3.1.0
.1.3.6.1.4.1.2.3.51.1.2.3.2.0
.1.3.6.1.4.1.2.3.51.1.2.3.3.0
.1.3.6.1.4.1.2.3.51.1.2.3.4.0
.1.3.6.1.4.1.2.3.51.1.2.3.5.0
.1.3.6.1.4.1.2.3.51.1.2.3.6.0
.1.3.6.1.4.1.2.3.51.1.2.3.7.0
.1.3.6.1.4.1.2.3.51.1.2.3.8.0
.1.3.6.1.4.1.2.3.51.1.2.3.9.0
.1.3.6.1.4.1.2.3.51.1.2.3.10.0
.1.3.6.1.4.1.2.3.51.1.2.3.11.0
.1.3.6.1.4.1.2.3.51.1.2.3.12.0

SNMP IBM Iseries (AS400)


2009
08.26

Monitoraggio di un Iseries senza agent e senza fare neppure un logon ? SNMP !

Si ma quali sono gli OID da utilizzare?

.1.3.6.1.4.1.2.6.4.5.1.0  per sapere l’utilizzo di CPU

.1.3.6.1.2.1.25.2.2.0 utilizzo di ram

.1.3.6.1.2.1.25.1.6.0 running process

.1.3.6.1.2.1.25.1.5.0  numero di utenti che hanno effettuato un logon

1.3.6.1.2.1.1.1.0  Versione di OS

.1.3.6.1.2.1.1.3.0 System Uptime

.1.3.6.1.2.1.25.2.3.1.5.1 = Storage totale

.1.3.6.1.2.1.25.2.3.1.6.1 = Storage utilizato

.1.3.6.1.2.1.2.2.1.10.2  Traffico in sull’interfaccia di rete

.1.3.6.1.2.1.2.2.1.16.2 Traffico out sull’interfaccia di rete

A breve aggiungerò via via gli OID che troverò….


TCP/IP ports on the RSA II, BMC, and BladeCenter Management Module


2009
07.28

The Remote Supervisor Adapter II, BMC, and BladeCenter Management Module use a variety of TCP/IP ports for communication. On the Redbooks website a technote is published that lists them and indicates which ones the administrator can and cannot change.

You need to ensure that your network (firewalls and routers) allows communications through these ports for the adapter and Management Module to function properly.

For related information about this topic, refer to the following IBM Redbooks publication:
IBM eServer xSeries and BladeCenter Server Management, SG24-6495-00

Remote Supervisor Adapter II
The following ports are user configurable. The default port numbers used are indicated.

Port name Port number Description
http 80 (default) Web server HTTP connection – TCP
https 443 (default) SSL connection -TCP
telnet 23 (default) Telnet command-line interface connection -TCP
SSH 22 (default) Secure Shell (SSH) command-line interface – TCP
SNMP agent 161 (default) SNMP get/set commands – UDP
SNMP traps 162 (default) SNMP traps – UDP

The following TCP/IP ports are fixed and cannot be changed.

Port number Description
427 SLP connection – UDP
1044 Remote disk function – TCP
1045 Persistent remote disk (disk on card) – TCP
2000 Remote Console video redirect – TCP
6090 IBM Director commands – TCP
7070-7073 Scalable Partition management (x445) – TCP
7070-7077 Scalable Partition management (x460 and x3950) – TCP

BMC
The following TCP/IP ports are fixed and cannot be changed.


BladeCenter Advanced Management Module

The following ports are user configurable. The default port numbers used are indicated.

Port number Description
623 IPMI communications to SMBridge and IBM Director
664 IPMI communications (secondary)
161 SNMP get/set commands
162 SNMP traps and PET alerts to Director
Port name Port number Description
http 80 (default) Web server HTTP connection – TCP
https 443 (default) SSL connection -TCP
telnet 23 (default) Telnet command-line interface connection -TCP
SSH 22 (default) Secure Shell (SSH) command-line interface – TCP
SNMP agent 161 (default) SNMP get/set commands – UDP
SNMP traps 162 (default) SNMP traps – UDP
FTP 21 Listen port for the FTP server – TCP
FTP data 20 FTP data port – TCP
TFTP 69 TFTP server – TCP
Remote disk 1044 Remote disk function – TCP
Remote disk on-card 1045 Persistent remote disk (disk on card) – TCP
Remote KVM 3900 Remote Console – TCP

The following TCP/IP ports are fixed and cannot be changed.

BladeCenter Management Module
The following ports are user configurable. The default port numbers used are indicated.

Port number Description
25 E-mail alerts – TCP
53 DNS resolver – UDP
68 DHCP client connection – UDP
427 SLP connection – UDP
6090 IBM Director commands – TCP
13991 IBM Director alerts – UDP
Port name Port number Description
http 80 (default) Web server HTTP connection – TCP
https 443 (default) SSL connection -TCP
telnet 23 (default) Telnet command-line interface connection -TCP
SSH 22 (default) Secure Shell (SSH) command-line interface – TCP
SNMP agent 161 (default) SNMP get/set commands – UDP
SNMP traps 162 (default) SNMP traps – UDP

The following TCP/IP ports are fixed and cannot be changed.

Port number Description
25 E-mail alerts – TCP
53 DNS resolver – UDP
68 DHCP client connection – UDP
427 SLP connection – UDP
1044 Remote disk function – TCP
1045 Persistent remote disk (disk on card) – TCP
5900 Remote Console video redirect – TCP
6090 IBM Director commands – TCP
13991 IBM Director alerts – UDP

ThinkCentre A50 boot usb


2009
07.08

Simply remove any hard disk and ser removable device ad the first!

Aggiornarnamento firmware IBM DS 3400


2009
05.06

inspiegabilmente se si aggiorna il firmware a volte non va a buon fine carica tutto il file ma non aggiorna basta passargli uno script dallo Storage Manager

activate storageSubsystem firmware;

con il  alla fine effettuare verify and execute