×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
OK!
Making some progress again. I shut stuff down and carefully walked
through everything. My son had cabled up some of the modules before I
had gotten back from my trip, the CPM being one of them. I really
hadn't looked at the end of the cable where the 5 cat5 cables come
together, I had just securely run in the attachment screws. Looking at
the module end again, I noticed that there was a sticker on one side of
the connector housing that said "LED Side" and it was on the wrong side
(!). In defense of my son's cabling up the module, the positioning of
the cable is counter-intuitive. You would expect a bundle of cables to
point downward toward the large opening in the "acoustic cage".
Instead, with the cable properly attached, the cable bundle points
upward (take a look here:
http://www.petesworkshop.com/images/cpm_cabling.jpg ). The other thing
is that the connector allows you to connect the adapter the wrong way,
which is interesting because most cables prevent you from doing that
with a unique shape or a keylock notch or something. In any case, that
was my issue. The CPM cable was attached incorrectly.
With that physical connection issue taken care of, the IVM immediately
responded and I was able to log in. However, I am not sure how to
attach to the running partition (it is running, I checked the status).
Using the option to "Open terminal window" from the IVM starts a putty
SSH session that attempts to connect to 10.0.1.20. Yet another network
interface configuration issue. I tried the LAN console but I am not
sure what to set the IP address to for the system.(BTW the instructions
about the LAN console you had questions about came from page 44 of the
readme, just under the section entitled "Installation steps that must be
performed by the implementing party")
So the final step is now to connect to the i. I just need to figure
that out and I should be good to go. What should I set the IP address
of the LAN Console to ? Any idea why the "Open terminal Window" in IVM
is trying to attach to 10.0.1.20?
Thanks.
Pete
Lukas Beeler wrote:
On Mon, Oct 13, 2008 at 9:28 PM, Pete Helgren <Pete@xxxxxxxxxx> wrote:
All the documentation is from the Vess Natchev Readme document found here:
http://www-03.ibm.com/systems/resources/systems_power_hardware_blades_i_on_blade_readme.pdf
Yeah, i read through that countless times, but i don't get where you
got your 192.168 adresses from that may or may not be preconfigured...
The ip address there squares with the IP I assigned it: 10.0.10.240. It
doesn't show the subnet config but I am guessing that is OK (s/b
255.255.255.0)
It's there. Look at "netmask". 0xffffff00 is 255.255.255.0.
That could be something in the config or it could be a cable or seating
issue. So I am going to shut down and double check all the contacts and
see it I can get to the bottom of it.
As far i know from the Server Connectivity Module i've used in my BC S
deployments so far, the BC S Ethernet Port numbering is off - it's not
straight one-to-seven. I've spent a few minutes on looking for docs,
and i can't access any BC S right now, so i can't really help you
much.
Based on the screen shot I posted, I should be able to get to VIOS at IP
address 10.0.10.240, correct?
Yes.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
