Unsolved
This post is more than 5 years old
1 Rookie
•
12 Posts
0
1318
July 12th, 2014 00:00
RPA temporary IP issues
While installing a new 2-node SE cluster, I found that neither node would hold the temp ip config, and I had to go into setup and configure the nodes manually to get them to accept their ip's.
It feels like I need to save the temp ip config, but clearly there's no option to do this.
Am I missing something?
Current Version 4.0 SP2 (upgrading to 4.1)
0 events found
No Events found!
forshr
2 Intern
•
1.1K Posts
1
July 12th, 2014 06:00
Hi Dave,
There have been a couple of historical reasons for RPA's losing there temporary IP addresses. I assume you have logged onto each RPA as boxmgmt and set the temporary IP addressing and then run DM RP/SE Installer Wizard.
Can you confirm the RPA mode, Gen4 or Gen5? Also, have the RPAs been used in a previous RP system?
Note that 4.0 target code is 4.0 SP2 P1.
Regards,
Richard
Storage_Dave
1 Rookie
•
12 Posts
0
July 12th, 2014 09:00
These are brand new gen 5's. I've logged in as boxmgmt and then tried to discover them through the GUI tool, but can't see them.
I got around it for node1 by going through setup in cli and configuring the ip's manually, but it leaves me with a problem for node 2 still..
I've done all the usual network checks to confirm the LAN and wan ports are communicating as expected, and can find no fault with the network switch ports or config..
forshr
2 Intern
•
1.1K Posts
1
July 12th, 2014 11:00
Just repeat the same process for node 2. In fact after setting the temp IP address for node 2 you should be able to import the settings from node 1.
There may be several reasons for what you're experiencing. Incorrect cabling and network patching are the most common. Duplicate IP addressing is another. I've also seen this happen when the WAN port is not cabled/connected.
Storage_Dave
1 Rookie
•
12 Posts
0
July 12th, 2014 16:00
I was on the wan port using a x-over cable on the .77 address (like the proc gen tells you to).
When I tried to connect to node 1 to import the settings, it said it couldn't connect.
I'll double check network settings on Monday. Thanks for the advice :)
Storage_Dave
1 Rookie
•
12 Posts
0
July 15th, 2014 12:00
Problem identified as switch port config issue, wan and LAN ports in incorrect vsan's (wrong way around). No wonder I couldn't see the LAN addresses!
Thanks for your help!