Management Node Not available

Discussion in 'Networking Questions' started by Tsi-Shawn, Jan 18, 2015.

  1. Tsi-Shawn

    Tsi-Shawn Kilo Poster

    Messages:
    89
    Today I was adding a public IP to the management node via the gui inside the node. I changed the IP and then was not able to log back into the management node, it still tries to connect to the original 10. which times out. I have made sure that it was changed back in
    /var/opt/pva/agent/etc/vzagent.conf and the agent restarted but it still times out. Where whould I go to make this change in the cli?

    Network was vent0 with the 10. IP. I clicked configure under the network tab and changed it, then it timed out.

    [root@cloudserver ~]# prlctl list
    UUID STATUS IP_ADDR T NAME
    {68b6e7b7-e042-4e85-ab16-9faa6c95d6ee} running 192.168.80.46 CT 1
    {472de2b7-9e6f-47cc-8608-53ab20ef29eb} running 206.248.169.131 CT 50


    If you go to http://206.248.169.130/ you will see what I mean. I am trying to get the pva link to go to http://206.248.169.131/
     
    Last edited: Jan 18, 2015
  2. Tsi-Shawn

    Tsi-Shawn Kilo Poster

    Messages:
    89
    Here is the fix for now to get the new IP deleted and the old one back to get the node up and running.

    vzctl set 50 --ipdel 206.248.169.131 --ipadd 10.23.5.29 --save
     
  3. Tsi-Shawn

    Tsi-Shawn Kilo Poster

    Messages:
    89
    I am still looking to get a public IP on the management node and have had no luck looking for a solution online. Does anyone have any ideas?
     
  4. IP^__^

    IP^__^ Odin Team

    Messages:
    80
  5. Tsi-Shawn

    Tsi-Shawn Kilo Poster

    Messages:
    89
    I already look through that article but could not complete his steps.

    [root@cloudserver ~]# pvamn restart
    -bash: pvamn: command not found

    If you could outline how to add both IP's I would be thankful
     
  6. IP^__^

    IP^__^ Odin Team

    Messages:
    80
    This command should be executed from the container with PVA MN inside. Please try to execute it from there. If there will be no such command then it points that somehow your MN installation is corrupted
    and it is good idea to verify PVA packages using "rpm -V".

    Simply use the vzctl set command like:
    vzctl set 50 --ipadd $IP_1 --ipadd $IP_2 --save
     
  7. Tsi-Shawn

    Tsi-Shawn Kilo Poster

    Messages:
    89
    [root@cloudserver ~]# vzlist -o ip 50
    IP_ADDR
    10.23.5.29 206.248.169.131


    Although when I go to the public IP it times out, and the internal does not work. it works to open the management node but all containers/vm's go offline and stay offline.

    This is my first time using this product. When you say "should be ran from the container" can you explain how to do that? I am missing steps I know and would like to get this up and running so I can demo, sign this off and purchase the partnership license.
     
    Last edited: Jan 19, 2015
  8. Tsi-Shawn

    Tsi-Shawn Kilo Poster

    Messages:
    89
    upload_2015-1-19_11-30-56.png

    I can change everything so that top left cloudserver.teksavvy.com is changed to the 206.218.169.131 IP but the VM and container below it go offline.
     

Share This Page