05-03-2012 04:20 PM
it's running 11.4P1.3. I found the following doc but doesn't seem to apply to 11.x. i'm sure it's not as easy at changing it at the Linux level and reboot. do i need to re-install? thx
05-17-2013 06:07 AM
Is it possible?
JNCIA-JUNOS, JNCIS-ENT/SEC, JNCIP-ENT
(CCNA, ACMP, ACFE, CISE)
CONNECT EVERYTHING. EMPOWER EVERYONE.
Share & Learn. Knowledge is Power.
"If there's a will, there's a way!"
08-08-2013 01:18 PM
I had a will and found the way ;-)
This was on Space 12.3P2.8. Yours may be different:
- SSH to the Space appliance with user "admin". Select option "6> (Debug) run shell" and enter the admin password again. You are now at the root shell.
- After GREP'ing through the files /usr/sbin/sh_jmp_setup_engine.sh and /usr/libexec/jmp-cli-menu/* I found that you need to use system-config-network-cmd. ( http://web.mit.edu/rhel-doc/5/RHEL-5-manual/Deployment_Guide-en-US/s1-network-save-config.html)
- Export the network config and make a copy
- Edit the file /tmp/networkconfig.changes and remove all the lines except the ones you want to change. Make your changes and save the file. You can also change the IP address here.
- Re-import your changes. Then export the new settings and compare to make sure they took effect:
system-config-network-cmd -i -f /tmp/networkconfigsystem-config-network-cmd -e > /tmp/networkconfig.newdiff /tmp/networkconfig.orig /tmp/networkconfig.new21c21< DeviceList.Ethernet.eth0.Gateway=192.168.0.254---> DeviceList.Ethernet.eth0.Gateway=192.168.0.1
- You can see the changes are there. Restart networking for the changes to take effect. Check the route table to see your changes in there!
service network restart
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
- At this point I am able to hit the Space appliance, but not its cluster IP. After some digging in /etc/hosts, /usr/sbin/sh_jmp_setup_engine.sh /usr/libexec/jmp-cli-menu/*, and /usr/libexec/jmp-vip-tools/setVIP.sh I found that Space uses the Linux-HA Heartbeat system. I restarted this and a few minutes later I was able to connect to the cluster IP:
- That's it! Note that each time you do service network restart you also need to restart heartbeat with /etc/init.d/heartbeat restart.
- Now that I have connectivity, I need to change the gateway in Space itself so that it does not overwrite it upon reboot. This is done via the web interface under Administration>Fabric>Space Node Settings.