RE: ASMI and changing IP address

Hi Larry,

Day 1 - I was able to open ASMI via http://192.168.2.147 after relaxing
security in IE to make that a trusted site.
Day 1 - I changed the eth0 to be dynamic
Today - I changed the ASMI eth0 back to factory 192.168.2.147 (option 3 in
network services)
Today - I can not open ASMI via http://192.168.2.147 using IE, Firefox, or
Chrome.

It does act as if it is a routing issue - I am able to open the connection
on port 80, but nothing every comes back from the ASMI. The serial ASMI
works fine.

On Day 1, I changed the eth0 configuration using the web-based ASMI. I think
that was problematic.

We bought this box from an IBM reseller through their refurb channel. It was
configured by them, but I don't think they setup the LAN console for us. It
has a twinax card in it and it came with a twinax hub.

-- Jake


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DrFranken
Sent: Monday, February 08, 2010 11:44 AM
To: Midrange Systems Technical Discussion
Subject: Re: ASMI and changing IP address

Jacob,

T6 and T7 are the ports assigned to IBM i, AIX, or Linux partitions.
They are not available to ASM.
In ASMI networks Eth0 and Eth1 refer to HMC1 and HMC2 ports
respectively on the back of the FSP itself.

What browser are you using to attempt your connections? It has been
my experience that Firefox works best but recent versions of Chrome may
also work well. Internet Exploder may not work as well. Generally the
connection should be started with http:\\ rather than https:\\

- Larry


On 2/8/2010 2:20 PM, Jacob Anderson wrote:

Hi Chris,

I do not have an IBM HMC.

I have a Windows 2008 Server connected:
192.168.2.20/24 -> directly to HMC1 Port configured as

192.168.2.147/24

192.168.5.12/24 -> switch, no longer connected to the iSeries
Serial -> Serial on iSeries
No software firewall enabled

ASMI over Serial works.
ASMI over http does not work
ASMI over https does not work

From the serial interface, I reset the HMC ports back to factory.

I am able to ping 192.168.2.147 from the host windows box, so the cables

are

labeled correctly.

In the ASMI, I do not see any way for me to configure the other LAN ports
(T6 and T7 I think), not sure why that is? Maybe I have to set that up in
the operations console?

As a note, when I try to open the ops-con against 192.168.2.147 it never
loads, it just says that it is trying to connect. Is it supposed to be

able

to work on the HMC ports addresses??

Thanks

-- Jake


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Bipes
Sent: Monday, February 08, 2010 10:50 AM
To: Midrange Systems Technical Discussion
Subject: RE: ASMI and changing IP address

Jake,

Do you have a Hardware Management Console from IBM? If so, is that the
windows pc you referred to in an earlier post?

What I think you have is:
On the iSeries, HMC1 and HMC2 plugged into a switch and have the IP
address:
HMC1 = 192.168.5.250
HMC2 = 192.168.16.30

You refer to a Windows PC, would that we the IBM HMC PC?
You mention that LAN1 is into a switch and has an IP of 192.168.5.12
And that LAN2 is directly plugged into HMC2 with an IP of 192.168.16.20.

What are your subnet masks?

Again what your windows PC shows as LAN1 and LAN2 may be different that
what is labeled on the hardware.

Did you ever try reversing the cables?




Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jacob Anderson
Sent: Monday, February 08, 2010 10:17 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: ASMI and changing IP address

Hi Chris,

I am confused as well. This should have been a routine IP change and the
web-based ASMI should continue to respond.

So I can connect using S1 and will reset the IP back to factory. Maybe
that will get me back to the start.

We are in San Diego, CA, pretty far south from you.

You were very helpful, thank you for that!