On Wed, Dec 31, 2008 at 15:17, Mark Walter <mwalter@xxxxxxxxxxxxxxx> wrote:
I've been through all of this documentation. I must say it's HORRIBLE! ! ! ! ! It doesn't specify which port.
IBM's documentation was written by students, for students. Not for
people who actually do any work ;)
In general, opscon today uses normal ethernet connections, and no
longer a serial connection that needed a special cable.
Your best bet is to do the following:
Install System i Access on a Laptop
Set a preliminary static IP address on the Laptops LAN Interface, e.G.
192.168.1.5/24
Start Operations Console, Add a new system, make sure to enter the
serial number correctly. If it asks for a partition number, enter "1".
If it asks for a system name and/or ip address, enter 192.168.1.10/24.
Connect your laptop to the lowest-numbered-non-HMC-Ethernet port on
your i. This is most probably T5, which is located on the back of the
chassis. You will not have link unless the machine is turned on. If
you have even a halfway modern laptop, it will have a gigabit
interface that can automatically switch for device-device connections,
if not, use a crossover cable.
Then, turn on the machine.
If it asks for u:pw, enter 11111111 as both user and password. It
should connect.
After connecting, you should configure a normal ethernet line and
enable external access using telnet. Make sure to install DCM and
secure telnet before exposing the machine to any production network.
Then, logon using telnet and reconfigure the console port for your
management VLAN.
If it doesn't, you'll have to do the 65+21 console change procedure.
It's easy to do, but very annoying.
midrange.com
