After following the instructions given by resident moderator Bakunin over here
#1 Connect to ASMI #2 Configure the deconfigured memory #3 Start the machine
OK, everything is fine, however now cannot connect to ASMI through browser,
using both HMC Ports
Default IP 1 = 192.168.2.147
Default IP 2 = 192.168.3.147
able to ping both IPs, did a reset of service processor from the control panel 9113-550 , pulled the power plug and started, still same problem
1- able to ping both service IPs
2- but unable to use any browser to connect it
I couldn't find this on the board
Figure 6. Top view of the system (including service processor reset switch)
$ lssysconn -r all
resource_type=0,type_model_serial_num=9113-550*107780E,sp=unavailable,side=unavailable,ipaddr=192.168.2.147,alt_ipaddr=192.168.3.147,state=No Connection,eth_loc_code=U787B.001.DNW3313-P1-T5,alt_eth_loc_code=U787B.001.DNW3313-P1-T6
$
# lscfg | grep ibmvmc0
* ibmvmc0 U9113.550.107780E-V1-C2 Virtual Management Channel
#
# lsrsrc -a IBM.MCP
2610-431 Cannot enumerate resources for this command on node 10.1.1.124. The node is not currently in the cluster.
2610-431 Cannot enumerate resources for this command on node 10.1.1.129. The node is not currently in the cluster.
2610-429 The specified resource class is not installed on node 10.1.1.120.
Resource Persistent Attributes for IBM.MCP
resource 1:
MNName = "10.1.1.125"
NodeID = 1439001851767854463
KeyToken = "10.1.1.110"
IPAddresses = {"10.1.1.110"}
ActivePeerDomain = ""
NodeNameList = {"10.1.1.125"}
# lsrsrc -a IBM.DRM
Resource Persistent Attributes for IBM.DRM
Can I reset ASMI from control panel codes or any other procedure ?
I haven't used an IBM p-Series without a HMC for such a long time that i am not sure i can help you off the top of my head here. However, there might be all sorts of problems putting obstacles into the IP-communication between your browser and the Serviceprocessor.
First off, it might be that the IP addresses have once been changed and i am not sure if a simple SP-reset really changes that back to the defaults. (That i am not sure means just that: i don't know. If you have information in the affirmative, then perhaps it is so.)
Second, there is a sure-fire way to connect to the SP, whatever its IP might be: go to the data centre, connect a crossed-out cable to the SP connector 1 or 2 and connect your system directly to it. I have a small netbook for these purposes with a Wireshark/Ethereal software installed, so i can identify even unknown or fogotten IP-adresses. Once you identified the IP-address you still need the ASMI password, which is, btw., completely separate!
Yes, the IPs are active. Who tells you for sure that they are the service processors? They could be all sorts of systems, yes?
OK, you have highlighted something, let me highlight something for you in return
$ lssysconn -r all
resource_type=0,type_model_serial_num=9113-550*107780E,sp=unavailable,side=unavailable,ipaddr=192.168.2.147,alt_ipaddr=192.168.3.14],state=No Connection,eth_loc_code=U787B.001.DNW3313-P1-T5,alt_eth_loc_code=U787B.001.DNW3313-P1-T6
$
I'd say the IVM awaits the interface to be where you are trying to find them. But it is not any more successful in that venture than you are. Therefore, eliminate all possible problems and connect directly to the system with a cross-over cable as suggested. That is a sure-fire method and if this fails the box is a case for the technician.
Thanks, I have to try two things:
1- Reset Toggle which is on the board (not tried yet)
2- Cross Cable : May be that will work (just informing you, it was working with straight cable, then i reconfigured the deconfigured memory and then stopped connecting to ASMI via browser)
I should have paid more attention to the model number: older models needed a crossover cable, newer ones don't (or, more correctly: don't care - they work with both). As it worked with a normal cable the first time your hardware is obviously new enough to ve able to use both, so the cable is not the problem.