OpenVZ Forum: Support » Migrating physical Trixbox 2.0/Asterisk => VE: no network

Home » General » Support » Migrating physical Trixbox 2.0/Asterisk => VE: no network

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Migrating physical Trixbox 2.0/Asterisk => VE: no network [message #9790]

Mon, 22 January 2007 17:08

mperkel
Messages: 253
Registered: December 2006

Senior Member

Trying to migrate physical server Trixbox 2.0/Asterisk to VE. What I did was create a Cantos VE and from inside there I rsync'ed a physical Trixbox server. I then copied the /etc/sysconfig/network-scripts directory from a working VE. But the networking isn't working and from inside the VE I get this when restarting the network.

service network restart
Shutting down interface venet0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: error: unknown error 1 setting key 'kernel.sysrq'
net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
error: unknown error 1 setting key 'kernel.core_uses_pid'
error: unknown error 1 setting key 'net.ipv4.tcp_syncookies'
[FAILED]
Bringing up loopback interface: [ OK ]
Bringing up interface venet0: [ OK ]

What am I missing? Thanks in advance.

Junk Email Filter
http://www.junkemailfilter.com

[Updated on: Tue, 23 January 2007 13:19] by Moderator

Report message to a moderator

Re: Migrating physical Trixbox 2.0/Asterisk => VE: no network [message #9798 is a reply to message #9790]

Tue, 23 January 2007 08:51

dim
Messages: 344
Registered: August 2005

Senior Member

Please, we need the output of the following commands:
1) `ip a l` in VE
2) `ip r l` in VE
3) `iptables-save` in VE
4)-6) above commands on the host itself
7) `sysctl net.ipv4.ip_forward` on the host

And please, specify kernel version you use.

http://static.openvz.org/openvz_userbar_en.gif

[Updated on: Tue, 23 January 2007 13:19] by Moderator

Report message to a moderator

Re: Migrating physical Trixbox 2.0/Asterisk => VE: no network [message #9805 is a reply to message #9790]

Tue, 23 January 2007 14:50

mperkel
Messages: 253
Registered: December 2006

Senior Member

In VE

[root@asterisk1 /]# ip a l
1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
3: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,10000> mtu 1500 qdisc noqueue
link/void
inet 127.0.0.1/32 scope host venet0
inet 69.50.231.3/32 brd 69.50.231.3 scope global venet0:0

[root@asterisk1 /]# ip r l
192.0.2.0/24 dev venet0 scope host
169.254.0.0/16 dev venet0 scope link
default via 192.0.2.1 dev venet0

[root@asterisk1 /]# iptables-save
# Generated by iptables-save v1.2.11 on Tue Jan 23 09:44:51 2007
*mangle
:PREROUTING ACCEPT [266338:13726413]
:INPUT ACCEPT [266336:13726317]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [265331:11430576]
:POSTROUTING ACCEPT [265331:11430576]
COMMIT
# Completed on Tue Jan 23 09:44:51 2007
# Generated by iptables-save v1.2.11 on Tue Jan 23 09:44:51 2007
*filter
:INPUT ACCEPT [266336:13726317]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [265331:11430576]
COMMIT
# Completed on Tue Jan 23 09:44:51 2007

In host:

[root@darwin acllists]# ip a l
2: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
4: sit0: <NOARP> mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0
6: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:17:31:4d:c6:59 brd ff:ff:ff:ff:ff:ff
inet 69.50.231.8/28 brd 69.50.231.15 scope global eth0
inet 69.50.231.9/28 brd 69.50.231.15 scope global secondary eth0:9
inet6 fe80::217:31ff:fe4d:c659/64 scope link
valid_lft forever preferred_lft forever
1: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue
link/void

[root@darwin acllists]# ip r l
69.50.231.7 dev venet0 scope link
69.50.231.3 dev venet0 scope link
69.50.231.0/28 dev eth0 proto kernel scope link src 69.50.231.8
169.254.0.0/16 dev eth0 scope link
default via 69.50.231.1 dev eth0

[root@darwin acllists]# iptables-save
# Generated by iptables-save v1.3.5 on Tue Jan 23 06:48:00 2007
*mangle
:PREROUTING ACCEPT [154799105:18881939255]
:INPUT ACCEPT [151532345:18610681828]
:FORWARD ACCEPT [3262635:270618423]
:OUTPUT ACCEPT [157765457:35789181814]
:POSTROUTING ACCEPT [161030087:36060175350]
COMMIT
# Completed on Tue Jan 23 06:48:00 2007
# Generated by iptables-save v1.3.5 on Tue Jan 23 06:48:00 2007
*filter
:INPUT ACCEPT [151532454:18610690095]
:FORWARD ACCEPT [3262637:270618531]
:OUTPUT ACCEPT [157765459:35789181973]
COMMIT
# Completed on Tue Jan 23 06:48:00 2007

[root@darwin acllists]# sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 1

Kernel 2.6.18-028test010 #2 SMP

Thanks in advance

Junk Email Filter
http://www.junkemailfilter.com

[Updated on: Tue, 23 January 2007 14:53]

Report message to a moderator

Re: Migrating physical Trixbox 2.0/Asterisk => VE: no network [message #9829 is a reply to message #9805]

Wed, 24 January 2007 09:11

dim
Messages: 344
Registered: August 2005

Senior Member

Looks like correct configuration. Could it be DNS issue?

Report message to a moderator

Re: Migrating physical Trixbox 2.0/Asterisk => VE: no network [message #9835 is a reply to message #9829]

Wed, 24 January 2007 14:54

mperkel
Messages: 253
Registered: December 2006

Senior Member

Definitely not a DNS issue. I can't see why DNS would make this error.

error: unknown error 1 setting key 'kernel.core_uses_pid'
error: unknown error 1 setting key 'net.ipv4.tcp_syncookies'
[FAILED]

Junk Email Filter
http://www.junkemailfilter.com

Report message to a moderator

Re: Migrating physical Trixbox 2.0/Asterisk => VE: no network [message #9836 is a reply to message #9835]

Wed, 24 January 2007 14:57

dim
Messages: 344
Registered: August 2005

Senior Member

Above messages are because in VE context change of this sysctls is prohibited. Could you ping host node by its IP from VE? Could you ping external IPs from VE? Could you ping VE from host node?

[Updated on: Wed, 24 January 2007 14:57]

Report message to a moderator

Re: Migrating physical Trixbox 2.0/Asterisk => VE: no network [message #9838 is a reply to message #9790]

Wed, 24 January 2007 15:18

mperkel
Messages: 253
Registered: December 2006

Senior Member

Thanks for your help.

Remember I started this by copying a physical machine into a VE. So I suspect that the problem is related to network scripts. What I need to do, which I thought I did was to merge the networking from a VE and physical copy.

I copied the /etc/sysconfig/network-scripts directory. Are there other directories and files I need to copy?

Junk Email Filter
http://www.junkemailfilter.com

Report message to a moderator

Re: Migrating physical Trixbox 2.0/Asterisk => VE: no network [message #9845 is a reply to message #9790]

Thu, 25 January 2007 15:52

mperkel
Messages: 253
Registered: December 2006

Senior Member

New details.

Migght not be VE related. On the HE I can't seem to add additional IP addresses there either. The main IP works but only the main IP.

ifconfig
eth0 Link encap:Ethernet HWaddr 00:17:31:4D:C6:59
inet addr:69.50.231.8 Bcast:69.50.231.15 Mask:255.255.255.240
inet6 addr: fe80::217:31ff:fe4d:c659/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:39133654 errors:0 dropped:0 overruns:0 frame:0
TX packets:39979143 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:127239880 (121.3 MiB) TX bytes:3929486685 (3.6 GiB)
Interrupt:16 Base address:0x2000

eth0:0 Link encap:Ethernet HWaddr 00:17:31:4D:C6:59
inet addr:69.50.231.9 Bcast:69.50.231.15 Mask:255.255.255.240
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:16 Base address:0x2000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:494627 errors:0 dropped:0 overruns:0 frame:0
TX packets:494627 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:199769732 (190.5 MiB) TX bytes:199769732 (190.5 MiB)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Looks normal to me but the IP address 69.50.231.9 is dead. I'm not sure what's wrong but sure could use some help. How do you troubleshoot this?

ifcfg-eth0

DEVICE=eth0
IPADDR=69.50.231.8
NETMASK=255.255.255.240
GATEWAY=69.50.231.1
ONBOOT=yes
TYPE=Ethernet
BOOTPROTO=none
USERCTL=no
PEERDNS=yes
IPV6INIT=no

ifcfg-eth0:0

IPADDR="69.50.231.9"
GATEWAY="69.50.231.1"
NETMASK=255.255.255.240
IPV6INIT=no
ONBOOT=yes
USERCTL=no
PEERDNS=yes
TYPE=Ethernet
DEVICE=eth0:0
BOOTPROTO=none

Junk Email Filter
http://www.junkemailfilter.com

Report message to a moderator

Previous Topic:	network card does not work properly with openvz kernel
Next Topic:	SOLVED Ubuntu 6.06 - will it work

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Nov 16 13:06:19 GMT 2024

Total time taken to generate the page: 0.03097 seconds