×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

System Platform 6.3 and bad default gateway

System Platform 6.3 and bad default gateway

System Platform 6.3 and bad default gateway

(OP)
I had to change the addressing of System Platform 6.3, unfortunately I made a mistake by typing the wrong (from other subnet) default gateway address. I can log in to DOM-0 using the putty console, but C-DOM and LSP and US are unreachable. I tried to use the service port S8300 address but to no avail - in any case, there is no web interface c-dom and other virtual hosts :(
Do you have an idea how to change the default gateway using CLI?

BR
T.

RE: System Platform 6.3 and bad default gateway

from dom0, as root, you could xm list to see all vms and xm console to plug right on to the console of any VM

Say you did xm console udom - that would put you on the CLI console of CDOM and you could root in, basic linux CLI to change default gateway, service network restart, then you might be able to get to the HTTP page again to set it in there properly. CDOM triggers scripts in dom0 when you do management stuff and dom0 then triggers scripts in the VMs - like when you change a default gateway in that webpage, then CDOM tells dom0 to tell all VMs to reconfigure themselves accordingly.

You could try that.
Also, there's a backend private network as well. 172.20.10.x if I recall correctly. If you ifconfig in dom0 you'll see virtual interfaces - at least 2 per vm - one on the private backend management network and one on the corp lan. So, cdom should have an IP on that. If dom0 is 172.20.10.1, try ssh'ing to 172.20.10.2 - and if you can ping/ssh from dom0 to cdom on the private interface, then you could build an SSH tunnel

To build and SSH tunnel, ssh on over with putty to dom0. Right click, settings, down at the bottom, ssh and tunnels. Leave the radio boxes "local" and "auto" selected. Put sourceport 443. put dest port 172.20.10.2:443 and click add underneath and then click apply - if you don't click add before apply, it doesn't take. Once you do that, https://127.0.0.1 goes on the ssh tunnel and dom0 forwards it to the destination. Might find your way into the webpage that way.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close