IVM installation through blade center

By -

system> env -T system:blade[5] ok>console DESTINATION BLADE IS IN POWER OFF STATE SOL session is temporarily not available. Attempting to re-establish your session ... SOL connection is re-established. SOL session is now active. SOL session is temporarily not available. Attempting to re-establish your session ... SOL connection is re-established. SOL session is now active. system:blade[5]> sol -status enabled SOL Session: Active SOL retry interval: 250 ms SOL retry count: 7 SOL bytes sent: 0 SOL bytes received: 105 SOL destination IP address: 192.199.199.85 SOL destination MAC: 00:1A:64:47:40:DA SOL I/O module slot number: 1 SOL console user ID: USERID SOL console login from: 9.126.97.184 (SSH) SOL console session started: 03/14/12 -- 11:30:47 SOL console session stopped: N/A Blade power state: On system:blade[5]> ping 192.199.199.85 Invalid syntax. Type 'ping -h' for help. system:blade[5]> config -name P6 blade2 system:blade[5]> list system:blade[5] P6 blade2 system:blade[5]> monalerts Command cannot be issued to this target. Type env -h for help on changing targets. system:blade[5]> info Name: P6 blade2 UUID: 7885 E8AA 4C10 11D9 8B56 001A 6447 40DA Manufacturer: IBM (LW) Manufacturer ID: 20301 Product ID: 137 Mach type/model: JS22 (Type 7998)/799861X Mach serial number: 10034CA Manuf date: 2309 Hardware rev: 0 Part no.: 46K7912 FRU no.: 46K7900 FRU serial no.: YL10W9152043 CLEI: Not Available Unique ID 1: Not Available Unique ID 2: Not Available Unique ID 3: Not Available Unique ID 4: Not Available Unique ID 5: Not Available Unique ID 6: Not Available Unique ID 7: Not Available Unique ID 8: Not Available MAC Address 1: 00:1A:64:47:40:DC -> 00:1A:64:47:40:EB MAC Address 2: Not Available MAC Address 3: Not Available MAC Address 4: Not Available MAC Address 5: Not Available MAC Address 6: Not Available MAC Address 7: Not Available MAC Address 8: Not Available FW/BIOS Build ID: EA340_039 Rel date: 11/12/2008 Rev: 0842 Level Status: Unique Local Control KVM: Yes Media Tray: Yes Power On Time: 0 days 0 hours 18 min 32 secs Number of Boots: 0 Product Name: JS12/JS22 Express Blade Server, 1-2 dual-core IBM POWER6 CPU(s)

Comments

Post a Comment

Popular posts from this blog

How to delete SEA in VIOS

By -
Remove the network en0 #ifconfig en0 down #ifconfig en0 detach Delete SEA $ lsdev -type sea name             status      description ent27            Defined     Shared Ethernet Adapter $ chdev -dev en26 -attr state=detach en27 changed $ rmdev -dev ent26;rmdev -dev en26;rmdev -dev et26 ent27 deleted $ rmdev -dev en26 en27 deleted $ rmdev -dev et26 et27 deleted system information #prtconf|more rmdev -dev ent3;rmdev -dev en3;rmdev -dev et3
Read more

More VIOS commands

By -
RAID controller USB UHC Spec --> local disk Location code website need to find? SCSI Adapter create LVM on VIOS if we hv single physical disk lsdev -virtul ent1 -- virtual adapter lsdev ent0 ---physical adapter lsmap -all -net netstat -state chdev -dev ent0 -attr state=detach mkdev VIOS Adapter 2 Port VLAN 1 port 3 vlan 99 bridge NO $ oem_setup_env 32 LPM_VIOS juno 37 c05076050e790000 c05076050e790001 show WWPN no lscfg -vpl fcs0 http://9.126.134.190/na_admin/ show hardisks lspv mkvdev -sea ent0 -vadapter ent1 -default ent1 -defaultid 1 5) Scan for new disks from your server Log into your server and scan for new hardware. SCAN SAN disks LUNS In AIX: AIX# cfgmgr AIX# fget_config -Avada $ vfcmap -vadapter vfchost2 -fcp fcs1 $ lsmap -all -npiv Name          Physloc                            ClntID ClntName       ClntOS ------------- ---------------------------------- ------ -------------- ------- vfchost0      U8205
Read more

Webmin configuration for LDAP

By -
We cannot add or delete users by default so we have to do below changes in LDAP module in GUI mode only. Configuring the module The most complex part of using this module is configuring it to talk to your LDAP server. By default, it will attempt to auto-detect the settings by looking at the LDAP client settings on your system, documented on the LDAPClient page. However, if this fails (perhaps because the LDAP server is not one of its own clients), you will need to configure the module manually as follows : On the module's main page, click on the Module Config link. In the LDAP server host field, enter the hostname of your LDAP server. If it is running on the same machine, enter localhost. If the LDAP server is using encryption, change the LDAP server uses TLS? option to Yes. In the Bind to LDAP server as field, enter the full DN of the administrative user for your LDAP server. This might be something like cn=Manager,dc=my-domain,dc=com. In the Credentials for bind name above field,
Read more