archttp not seeing ARC-1260?

W

wkearney99

Limp Gawd
Joined
Sep 8, 2010
Messages
370
I've had a machine setup with two ARC-1210 cards for a while. I'm migrating from the two cards to a single ARC-1260. All boards have the latest 1.48 firmware on them. I upgraded the 1260 to that before installing it in this machine. I pulled one of the 1210's and replaced it with a 1260. Upon reboot the BIOS sees the two cards, that works fine.

But once booted into windows 2008 R2 (x64) the ARChttp utility only sees one controller (the 1210). The 1260 isn't shown. The controller is working as it does appear in the device manager and it's volumes are mounting in the OS (single 4-drive RAID5).

I realize the 1260 has it's own ethernet port. I don't have wire pulled to this machine for a second ethernet port. I wouldn't likely need to use it anyway. In-band control through archttp would be sufficient for my needs (and wouldn't waste an ethernet port either).

So can the archttp utility interface with a 1260? Do I need to set something via the BIOS firmware in order to use the localhost connection via archttp?
 
Oh, and I should add, the RAID set moved from the 1210 to the 1260 with absolutely no configuration changes on my part. I just moved the cabling to the new controller and it brought it up automatically. Nice!
 
You might need to install the driver again for the 1260 to be picked up. Different PCIe slot often require driver installation and reboot.

If Archttp still can't pick up the 1260 after you've done this. Try manually typing in port 82 on the address. The default 1210 should occupy default port 81 and any additional card is connected through incremental port (82, 83...etc)
 
The 1260 is being seen by the OS. I did install the driver for it, as it wasn't recognized right away by Windows 2008 R2. I reinstalled the archttp program just for kicks, that did not help.

It shows the 1210 on port 81 and the config assistant (the archttp program itself) on port 82. Connections to any other ports does not work.

I'm going to try dropping out to the BIOS again to see if there's anything else in the config that might affect this.
 
I went into the BIOS and set it's ethernet address to 127.0.0.1 using port 83, and disabled DHCP. Now archttp sees it. Don't know if that's why or not, because this also involved a reboot. I'll be migrating the other RAID set to this card and taking the other 1210 out. I'll see if that makes any difference in the port numbering that archttp uses. Right now the 1210 is on 81, the 1260 on port 83. Hmmm, I thought I told the BIOS to use port 83... I'll recheck during the next reboot.

So I have archttp access to both cards now. Can't specifically explain why, but at least it's working.
 
The 1260 BIOS has options for networking. What should it be set for if I'm not going to use the ethernet port on it?
 
Ok, migrated out the 2nd 1210 and now the whole thing's running on the 1260. Once again I had to do nothing to the RAID sets to make the transition. Came up clean on the new controller and booted fine. archttp sees the 1260, now on port 81 (the first one it allocates). Apparently archttp makes a connection independent of whatever the card's ethernet config might contain. Which, absent decent documentation, makes sense.

During the next reboot I'll reset the network configs in the BIOS to factory settings (dhcp, etc). No sense leaving it with something odd and have that bite me in the ass months/years from now...
 
You must log in or register to reply here.
Back
Top