01-09-2008
Able to ping server's private network
Hi guys,
I'm in the progress of setting up a private network in our Sun solaris platform.
Existing ip: 172.16.102.101
New private ip: 192.168.2.3
Netmask is the same for both private & public 255.255.255.0
After setting up the ip, I'm able to ping this private ip address from our workstation, with the ip 172.16.101.120. Why is this so? Supposingly we are unable to ping from outside.
Appreciate any helps here...I'm quite new in network field.
Thanks in bunch!
Last edited by *Jess*; 01-09-2008 at 01:14 AM..
7 More Discussions You Might Find Interesting
1. IP Networking
i have one private network with one ip address, and i have a seperate network on a seperate ip address.
now, each network is behind a firewall/router. now what i want to do is be able to access one server on the second network from a computer on the first., but with the private ip address, (this... (2 Replies)
Discussion started by: norsk hedensk
2 Replies
2. IP Networking
Hi all,
Currently we are in the progress of setting up a private network on all of our Sun Solaris servers. Purpose is to move all backup tasks to the private, hence reduce load on public network.
Some of our servers only consists of 1 network card but with several ports. Shall we purchase... (10 Replies)
Discussion started by: *Jess*
10 Replies
3. UNIX for Dummies Questions & Answers
Hi all,
I just purchased 2 Ultra 10 servers and I want to practice with home networking. I want to create a private network where I can connect both boxes to the internet via broadband using my four port adsl modem/router. My ISP assigns me 192.168 addresses via DHCP and I use the ISP's DNS but... (1 Reply)
Discussion started by: Kongowea
1 Replies
4. IP Networking
Hi all,
please help solving my small issue
below is the configuration
I have 3 systems
sytem1 -------- system 2 ----------system 3
system 1 : 10.255.1.4 & default gw 10.255.1.55
system2 : ip 1 : 10.255.1.55 , ip 2: 10.255.2.1
system 3 : ip : 10.255.2.3
on system 2 : ... (4 Replies)
Discussion started by: Gopi Krishna P
4 Replies
5. IP Networking
how does a router directs the internet traffic to a specific host in the private network?
Example:
My PC has ip 192.168.134.100
Router has ip 192.168.134.200
My company's ip 202.52.150.33
When i try to access internet, say google, it traverses from... (1 Reply)
Discussion started by: Arun_Linux
1 Replies
6. Windows & DOS: Issues & Discussions
Hello,
I have a desktop which has two network cards installed on it and I connected these two card through a hub.
On the desktop in have installed a Windows Vista Home Edition SO and a Windowx XP SO in a virtual way. I also had intalled a Virtual BOX software and Windows XP run through it.
By... (1 Reply)
Discussion started by: zendcool
1 Replies
7. AIX
Able to ping the server but not able to login through putty it says network timeout
Please assist (3 Replies)
Discussion started by: Vishal_dba
3 Replies
LEARN ABOUT DEBIAN
vzmigrate
vzmigrate(8) Containers vzmigrate(8)
NAME
vzmigrate - migrate a container between two OpenVZ servers
SYNOPSIS
vzmigrate [-r|--remove-area yes|no] [--ssh=ssh_options] [--rsync=rsync_options] [--keep-dst] [--online] [-v] destination_address CTID
DESCRIPTION
This utility is used to migrate a container from one (source) Hardware Node (HN) to another (destination) HN. The utility can migrate
either stopped or running container. For a stopped container, simple CT private area transfer is performed (rsync(1) is used for file
transfer). For running containers, migration may be offline (default) or online.
This program uses ssh as a transport layer. You will need to put ssh public key to destination node and be able to connect to node without
entering password.
OPTIONS
-r, --remove-area yes | no
Whether to remove a container area on source HN for the successfully migrated container. Default is yes.
--ssh=options
Additional options that will be passed to ssh while establishing connection to destination HN.
--rsync=options
Additional options that will be passed to rsync(8). You may add options like -z to enable data compression if you are migrating
over a slow link.
--keep-dst
Do not clean synced destination container private area in case of some error. It makes sense to use this option on big container
migration to avoid syncing container private area again in case some error (on container stop for example) occurs during first
migration attempt.
--online
Perform online (zero-downtime) migration: during the migration the container hangs for a while and after the migration it continues
working as though nothing has happened.
-v Verbose mode. Causes vzmigrate to print debugging messages about its progress. Multiple -v options increase the verbosity. The
maximum is 3.
EXAMPLES
Migration of CT 101 to 192.168.1.130 with downtime:
vzmigrate 192.168.1.130 101
Online migration of CT 102 to 192.168.1.130:
vzmigrate --online 192.168.1.130 102
EXIT STATUS
0 EXIT_OK
Command completed successfully.
1 EXIT_USAGE
Bad command line options.
2 EXIT_VE_STOPPED
Container is stopped.
4 EXIT_CONNECT
Can't connect to destination (source) HN.
6 EXIT_COPY
Container private area copying/moving failed.
7 EXIT_VE_START
Can't start or restore destination CT.
8 EXIT_VE_STOP
Can't stop or checkpoint source CT.
9 EXIT_EXISTS
Container already exists on destination HN.
10 EXIT_NOTEXIST
Container does not exists on source HN.
12 EXIT_IP_INUSE
You attempt to migrate CT which IP address(es) are already in use on the destination node.
13 EXIT_QUOTA
Operation with CT quota failed.
SEE ALSO
rsync(1).
COPYRIGHT
Copyright (C) 2001-2010, Parallels, Inc. Licensed under GNU GPL.
OpenVZ 28 Jun 2011 vzmigrate(8)