Hi Iamnothere
I am starting up a new HiPath 4000 Version 6 latest software on DSCXL2 (not the DSCXL2+ newer type)
I have the 'A' side installed but now I cannot log on to the Assistant/Portal
What do I need to do for that to startup?
If your XML file was properly configured, you should not need to access the Portal. But if you absolutely need to access the Portal at this point with V6 R2, there is a new procedure to access the Portal. You will need to use a CLIENT PC. You will need to use the "ifconfig" command from the Linux console to verify the current eth0 IP Address. THIS ADDRESS will provide temporary access to the Portal during the installation. Assign to the Client PC's NIC a unique IP Address from the same network as you used to assign the eth0 IP Address. Using a Layer 2 switch, connect your Client PC to the Primary server's eth0 port (or whichever port you assigned as the Customer LAN). From your client PC, launch your browser to the PHYSICAL IP ADDRESS of the eth0 port.
This temporary Portal IP Address vanishes after the DRBD Synchronization starts. Then the only Portal addresses will be 192.0.2.7 on the ATL LAN, and the customized address that you assigned via the XML file or via the Portal -> System -> LAN Config.
Thanks,
What I am really missing is the step by step of config.
I have 2 installed already but this one is not playing nice.
My XML looks OK as I have copied it from a system I installed recently but changed the IP addresses obviously.
How long do you wait after the install/reboot for the assistant to be live?
How do you check on progress?
It just sits there...
I am concerned that because I am using the older type of processor that it wont work.
How do I know that the DRBD Synchronization has started?
I assume I have the 'b' processor installed at that stage?
Sorry for all the questions, under pressure as usual
I am going to type something here that I despise when others use this technique when responding to me: Why do you need to access Assistant after only the Primary server has installed? It is not necessary.
The installation process calls for the Secondary server to be installed next, then connect the cables, then the DRBD synchronization. You should not try to alter that process.
I have not tried to access Assistant at this specific point, as this step would be like sitting down to eat a meal before it has been cooked.
The XML installation technique masks all of the manually-performed individual steps that were necessary in V6R0 & V6R1. Now when the Primary server reboots after the installation, and you have removed the USB flash drive, Assistant has been installed, but it may not be ready for access until the server-to-server sync happens.
The installation process:
(1) use USB with XML file to install Primary server
(2) use USB with XML to install Secondary server
(3) Connect cables
(4) Allow servers to sync
(5) After all four VMs have sync'ed, the ADP should have "-.", active SWU indicates "empty database", and Assistant is ready, then generate the SWU database.
(6) Then apply licensing, do backups, etc.
(7) Start RAID as final step
I can send you the official USA V6R2 Installation document if you'd like.
Provide me a FTP IP Address and access info.
There is no cause for concern regarding the use of the original DSCXL2. It is exactly the same as the DSCXL2+ except for the cosmetic changes: new slot/bay for hard drive, and new eSata connection for the new HDTR2.
The same processor and RAM is used for both versions of the board.
The DRBD sync happens only after both servers are installed and cables connected.
From the Linux console port of either server, type:
service drbd status
Repeat this command, as it does not dynamically update.
Look for the word "CONNECTED", which means that the sync for that specific VM has completed. If you see a percentage, then that amount of progress has been made on syncing the "source" VM, which means that the overall sync has not yet completed. If you see four instances of the word "CONNECTED", then the DRBD sync is finished.
Thanks, much appreciated. I did the early early course. They did not even work out how to do duplex at that stage so I am missing out a bit, and my class mate was from Brazil with little English should go on an update course really.
I don't need to access the assistant after the setup and your comments make sense, my notes on the previous setups are hazy.
Thanks for the step by step, it makes sense to me as I always seem to be in a hurry when I have to create these.
I would appreciate the copy of the V6R2 doc, I might have something similar but the logical steps above are what I needed.
Thanks also for the post on the DRBD status as that will come in handy.
One other thing !
It looks like during the install that a process called udevd is changing eth0 to eth6 does that make any sense or should it be all ok after the install.
Try FTP to 87.192.192.66 user: conversation Password: conversation
I have not noticed the eth0 -> eth6 activity. Did you implement bonding via the XML file?
If not, I hope and trust that it is simply some internal task that will normalize later.
The document that I can send you is actually available via eDoku: It's the V6R2 Installation and Migration document.
I do not actually have it here right now, as I am on holiday this week.
But if you need it badly, I can get to it within an hour or so. Let me know.
Was your instructor named Lee @ Nottingham? He and I work together - different countries, though.
Hi,
Yes hopefully its just an internal thing with the eth0
At the moment if things go well then I will be fine, just starting again on the 'b' side
I went to Munich for the course but I have been to Nottingham on a few occasions as well.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.