rac的clusterware安裝完成之後vip無法ping通
今天同事遇到這樣一個事情,安裝完成clusterware之後,最後執行完root.sh之後,需要在rac2上執行vipca再次配置,在這一步驟卻過不去。一起看了一下這個問題,送報錯的log中有比較明顯的提示:沒有配置閘道器。
有了這個提示之後,就比較好處理,在linux上配置192.168.79.1為閘道器,其中192.168.79.1為vmware VMnet1(hostonly)的網絡卡地址。service network restart之後,再次執行執行vipca,也能執行成功,檢視crs_stat看到vip也確實online了,但是就是ping不通vip,為什麼?
[[email protected]Name Type R/RA F/FT Target State Host
----------------------------------------------------------------------
ora.devdb.db application 0/1 0/1 ONLINE OFFLINE
ora....b1.inst application 0/5 0/0 ONLINE OFFLINE
ora....b2.inst application 0/5 0/0 ONLINE OFFLINE
ora....SM1.asm application 0/5 0/0 ONLINE UNKNOWN rac1
ora....C1.lsnr application 0/5 0/0 ONLINE UNKNOWN rac1
ora.rac1.gsd application 0/5 0/0 ONLINE ONLINE rac1
ora.rac1.ons application 0/3 0/0 ONLINE ONLINE rac1
ora.rac1.vip application 0/0 0/0 ONLINE ONLINE rac1
ora....SM2.asm application 0/5 0/0 ONLINE UNKNOWN rac2
ora....C2.lsnr application 0/5 0/0 ONLINE UNKNOWN rac2
ora.rac2.gsd application 0/5 0/0 ONLINE ONLINE rac2
ora.rac2.ons application 0/3 0/0 ONLINE ONLINE rac2
ora.rac2.vip application 0/0 0/0 ONLINE ONLINE rac2
[
[[email protected] bin]# ping rac2-vip
PING rac2-vip.oracle.com (192.168.79.26) 56(84) bytes of data.
From rac1.oracle.com (192.168.79.15) icmp_seq=1 Destination Host Unreachable
From rac1.oracle.com (192.168.79.15) icmp_seq=2 Destination Host Unreachable
From rac1.oracle.com (192.168.79.15) icmp_seq=3 Destination Host Unreachable
--- rac2-vip.oracle.com ping statistics ---
5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4001ms
, pipe 4
[
[[email protected] bin]#
[[email protected] bin]#
檢查了一下vip相關的設定,發現確實有點問題,vip網路是配置成192.168.1.的網段,注意看eth0:1的網段:
[[email protected] bin]# ifconfig -aeth0 Link encap:Ethernet HWaddr 00:0C:29:9C:EE:4F
inet addr:192.168.79.15 Bcast:192.168.79.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe9c:ee4f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3677 errors:0 dropped:0 overruns:0 frame:0
TX packets:3688 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:317108 (309.6 KiB) TX bytes:350214 (342.0 KiB)
Interrupt:10 Base address:0x20a4
eth0:1 Link encap:Ethernet HWaddr 00:0C:29:9C:EE:4F
inet addr:192.168.1.105 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:10 Base address:0x20a4
eth1 Link encap:Ethernet HWaddr 00:0C:29:9C:EE:59
inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe9c:ee59/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29480 errors:0 dropped:0 overruns:0 frame:0
TX packets:35281 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:20628586 (19.6 MiB) TX bytes:31021035 (29.5 MiB)
Interrupt:5 Base address:0x2424
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:20969 errors:0 dropped:0 overruns:0 frame:0
TX packets:20969 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3709389 (3.5 MiB) TX bytes:3709389 (3.5 MiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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)
[[email protected] bin]#
並且我們通過oifcfg看到配置了2個網段的public,在正常情況下,我們只需要一個public和一個cluster_interconnect:
[[email protected] bin]# ./oifcfg getifeth0 192.168.1.0 global public
eth0 192.168.79.0 global public
eth1 10.0.0.0 global cluster_interconnect
[[email protected] bin]#
[[email protected] bin]#
問了一下之前的情況,原來同事在家裡是用橋接(bridged)的網路設定虛擬機器的網絡卡地址,地址設定的IP地址為192.168.1網段,並且當時沒設定閘道器。
查到這裡,問題就比較好辦了。
1.取消oifcfg中的關於192.168.1網段:
[[email protected] bin]# ./oifcfg delif -global eth0/192.168.1.0檢查一下結果:
[[email protected] bin]# ./oifcfg getifeth0 192.168.79.0 global public
eth1 10.0.0.0 global cluster_interconnect
[[email protected] bin]#
2.這裡介紹2中修改vip地址的方法,rac1我用方法a修改,rac2我用方法b修改:
a)用srvctl修改vip地址
[[email protected] bin]#
[[email protected] bin]# ./crs_stat -p ora.rac1.vip
NAME=ora.rac1.vip
TYPE=application
ACTION_SCRIPT=/u01/app/oracle/product/10.2.0/crs_1/bin/racgwrap
ACTIVE_PLACEMENT=1
AUTO_START=1
CHECK_INTERVAL=60
DESCRIPTION=CRS application for VIP on a node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=rac1
OPTIONAL_RESOURCES=
PLACEMENT=favored
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=0
SCRIPT_TIMEOUT=60
START_TIMEOUT=0
STOP_TIMEOUT=0
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=eth0
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=255.255.255.0
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=192.168.79.25
[[email protected] bin]#
b)用匯出crs,編輯crs,再update crs資源的方式:
## 先匯出crs資源中關係rac2的vip資訊,注意匯出的路徑為$ORA_CRS_HOME/crs_1/profile下,名稱為<資源名>.cap:[[email protected] bin]# ./crs_stat -p ora.rac2.vip > /u01/app/oracle/product/10.2.0/crs_1/crs/profile/ora.rac2.vip.cap
##修改該檔案,將vip的地址改掉
[[email protected] tmp]# cat /u01/app/oracle/product/10.2.0/crs_1/crs/profile/ora.rac2.vip.cap
NAME=ora.rac2.vip
TYPE=application
ACTION_SCRIPT=/u01/app/oracle/product/10.2.0/crs_1/bin/racgwrap
ACTIVE_PLACEMENT=1
AUTO_START=1
CHECK_INTERVAL=60
DESCRIPTION=CRS application for VIP on a node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=rac2
OPTIONAL_RESOURCES=
PLACEMENT=favored
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=0
SCRIPT_TIMEOUT=60
START_TIMEOUT=0
STOP_TIMEOUT=0
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=eth0
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=255.255.255.0
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=192.168.79.26
[[email protected] bin]# ./crs_register -u ora.rac2.vip
[[email protected] bin]#
[[email protected] bin]#
[[email protected] bin]#
[[email protected] bin]# ./crs_stat -p ora.rac2.vip
NAME=ora.rac2.vip
TYPE=application
ACTION_SCRIPT=/u01/app/oracle/product/10.2.0/crs_1/bin/racgwrap
ACTIVE_PLACEMENT=1
AUTO_START=1
CHECK_INTERVAL=60
DESCRIPTION=CRS application for VIP on a node
FAILOVER_DELAY=0
FAILURE_INTERVAL=0
FAILURE_THRESHOLD=0
HOSTING_MEMBERS=rac2
OPTIONAL_RESOURCES=
PLACEMENT=favored
REQUIRED_RESOURCES=
RESTART_ATTEMPTS=0
SCRIPT_TIMEOUT=60
START_TIMEOUT=0
STOP_TIMEOUT=0
UPTIME_THRESHOLD=7d
USR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0
USR_ORA_CONNECT_STR=/ as sysdba
USR_ORA_DEBUG=0
USR_ORA_DISCONNECT=false
USR_ORA_FLAGS=
USR_ORA_IF=eth0
USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=255.255.255.0
USR_ORA_OPEN_MODE=
USR_ORA_OPI=false
USR_ORA_PFILE=
USR_ORA_PRECONNECT=none
USR_ORA_SRV=
USR_ORA_START_TIMEOUT=0
USR_ORA_STOP_MODE=immediate
USR_ORA_STOP_TIMEOUT=0
USR_ORA_VIP=192.168.1.106 ## <--修改此處為192.168.79.26
[root@rac2bin]#
##修改完成之後,更新crs:
[root@rac2bin]# ./crs_register-uora.rac2.vip
[root@rac2bin]#
[root@rac2bin]#
[root@rac2bin]#
## 檢查vip的是否修改完成:
[root@rac2bin]# ./crs_stat-pora.rac2.vipNAME=ora.rac2.vipTYPE=applicationACTION_SCRIPT=/u01/app/oracle/product/10.2.0/crs_1/bin/racgwrapACTIVE_PLACEMENT=1AUTO_START=1CHECK_INTERVAL=60DESCRIPTION=CRSapplication forVIPonanodeFAILOVER_DELAY=0FAILURE_INTERVAL=0FAILURE_THRESHOLD=0HOSTING_MEMBERS=rac2OPTIONAL_RESOURCES=
PLACEMENT=favoredREQUIRED_RESOURCES=
RESTART_ATTEMPTS=0SCRIPT_TIMEOUT=60START_TIMEOUT=0STOP_TIMEOUT=0UPTIME_THRESHOLD=7dUSR_ORA_ALERT_NAME=
USR_ORA_CHECK_TIMEOUT=0USR_ORA_CONNECT_STR=/ assysdbaUSR_ORA_DEBUG=0USR_ORA_DISCONNECT=falseUSR_ORA_FLAGS=
USR_ORA_IF=eth0USR_ORA_INST_NOT_SHUTDOWN=
USR_ORA_LANG=
USR_ORA_NETMASK=255.255.255.0USR_ORA_OPEN_MODE=
USR_ORA_OPI=falseUSR_ORA_PFILE=
USR_ORA_PRECONNECT=noneUSR_ORA_SRV=
USR_ORA_START_TIMEOUT=0USR_ORA_STOP_MODE=immediateUSR_ORA_STOP_TIMEOUT=0USR_ORA_VIP=192.168.79.26
[root@rac2bin]#
[root@rac2bin]#
3.重啟crs服務:
[[email protected] bin]# /etc/init.d/init.crs stopShutting down Oracle Cluster Ready Services (CRS):
Stopping resources.
Successfully stopped CRS resources
Stopping CSSD.
Shutting down CSS daemon.
Shutdown request successfully issued.
Shutdown has begun. The daemons should exit soon.
[[email protected] bin]#
[[email protected] bin]#
[[email protected] bin]#
[[email protected] bin]# /etc/init.d/init.crs start
Startup will be queued to init within 90 seconds.
[[email protected] bin]#
[[email protected] bin]#
4.檢查網路:
[[email protected] bin]# ifconfig -aeth0 Link encap:Ethernet HWaddr 00:0C:29:9C:EE:4F
inet addr:192.168.79.15 Bcast:192.168.79.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe9c:ee4f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4926 errors:0 dropped:0 overruns:0 frame:0
TX packets:4894 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:423166 (413.2 KiB) TX bytes:458330 (447.5 KiB)
Interrupt:10 Base address:0x20a4
eth0:1 Link encap:Ethernet HWaddr 00:0C:29:9C:EE:4F
inet addr:192.168.1.105 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:10 Base address:0x20a4
eth0:2 Link encap:Ethernet HWaddr 00:0C:29:9C:EE:4F
inet addr:192.168.79.25 Bcast:192.168.190.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:10 Base address:0x20a4
eth1 Link encap:Ethernet HWaddr 00:0C:29:9C:EE:59
inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe9c:ee59/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:39931 errors:0 dropped:0 overruns:0 frame:0
TX packets:42423 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:31121904 (29.6 MiB) TX bytes:37055997 (35.3 MiB)
Interrupt:5 Base address:0x2424
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:25976 errors:0 dropped:0 overruns:0 frame:0
TX packets:25976 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3862680 (3.6 MiB) TX bytes:3862680 (3.6 MiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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)
[[email protected] bin]#
此時已經可以ping vip了:
[[email protected] bin]# ping rac2-vipPING rac2-vip.oracle.com (192.168.79.26) 56(84) bytes of data.
64 bytes from rac2-vip.oracle.com (192.168.79.26): icmp_seq=0 ttl=64 time=0.921 ms
64 bytes from rac2-vip.oracle.com (192.168.79.26): icmp_seq=1 ttl=64 time=1.19 ms
64 bytes from rac2-vip.oracle.com (192.168.79.26): icmp_seq=2 ttl=64 time=0.000 ms
--- rac2-vip.oracle.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 0.000/0.706/1.198/0.512 ms, pipe 2
[[email protected] bin]#
另外,由於eth0上出現了2個繫結的IP,如果你如果和我一樣有潔癖,可以用ifconfig再改一下:
[[email protected] ~]# ifconfig eth0:1 down[[email protected] ~]# ifconfig eth0:2 down
[[email protected] ~]# ifconfig eth0:1 192.168.79.25 netmask 255.255.255.0 up
[[email protected] ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0C:29:9C:EE:4F
inet addr:192.168.79.15 Bcast:192.168.79.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe9c:ee4f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1709 errors:0 dropped:0 overruns:0 frame:0
TX packets:1800 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:144931 (141.5 KiB) TX bytes:154502 (150.8 KiB)
Interrupt:10 Base address:0x20a4
eth0:1 Link encap:Ethernet HWaddr 00:0C:29:9C:EE:4F
inet addr:192.168.79.25 Bcast:192.168.79.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:10 Base address:0x20a4
eth1 Link encap:Ethernet HWaddr 00:0C:29:9C:EE:59
inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe9c:ee59/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:58831 errors:0 dropped:0 overruns:0 frame:0
TX packets:46188 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:58311355 (55.6 MiB) TX bytes:40821202 (38.9 MiB)
Interrupt:5 Base address:0x2424
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:25831 errors:0 dropped:0 overruns:0 frame:0
TX packets:25831 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4026775 (3.8 MiB) TX bytes:4026775 (3.8 MiB)
[[email protected] ~]# [[email protected] bin]# ifconfig eth0:1 down
[[email protected] bin]# ifconfig eth0:2 down
[[email protected] bin]# ifconfig eth0:1 192.168.79.26 netmask 255.255.255.0 up
[[email protected] bin]#
[[email protected] bin]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0C:29:C4:93:DA
inet addr:192.168.79.16 Bcast:192.168.79.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fec4:93da/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4573 errors:0 dropped:0 overruns:0 frame:0
TX packets:4471 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:382261 (373.3 KiB) TX bytes:414120 (404.4 KiB)
Interrupt:10 Base address:0x20a4
eth0:1 Link encap:Ethernet HWaddr 00:0C:29:C4:93:DA
inet addr:192.168.79.26 Bcast:192.168.79.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:10 Base address:0x20a4
eth1 Link encap:Ethernet HWaddr 00:0C:29:C4:93:E4
inet addr:10.0.0.2 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fec4:93e4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:46132 errors:0 dropped:0 overruns:0 frame:0
TX packets:58460 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:40803518 (38.9 MiB) TX bytes:58269953 (55.5 MiB)
Interrupt:5 Base address:0x2424
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:26665 errors:0 dropped:0 overruns:0 frame:0
TX packets:26665 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4014814 (3.8 MiB) TX bytes:4014814 (3.8 MiB)
[[email protected] bin]#
最後,再次重申一下,安裝clusterware的之前,一定要配置好閘道器。
相關推薦
rac的clusterware安裝完成之後vip無法ping通
今天同事遇到這樣一個事情,安裝完成clusterware之後,最後執行完root.sh之後,需要在rac2上執行vipca再次配置,在這一步驟卻過不去。一起看了一下這個問題,送報錯的log中有比較明顯的提示:沒有配置閘道器。 有了這個提示之後,就比較好處理,在linux上配
centos中安裝配置nginx完成之後主機無法訪問
CP 方法 true VM 配置 pre PE all 開啟 原因 VMware中安裝centos7,安裝配置完成nginx後,主機無法訪問。虛擬機沒有放行Nginx默認端口80。 解決方法 解決方法 首先:開啟 web 端口 firewall-cmd --p
Vmware 下安裝虛擬無法ping通主機地址
VMware預設的橋接模式中橋接方式為“自動”,沒有指定很可能將網路橋接到其他網絡卡上,無法聯網。 點選電腦右下角的網路,點選“開啟網路和共享中心”(win10自己搜尋路徑),選擇“更改介面卡設定”。在連線網路的介面卡下面有網絡卡的名稱,“本地連線”下的“Realtek PCIe
Microsoft Virtual PC虛擬機器安裝Centos區域網無法ping通問題
Microsoft Virtual PC虛擬機器安裝centos作業系統,完成後發現能ping通外網,區域網無法ping通,設定了靜態IP還是沒用 後來發現是虛擬機器聯網模式的問題 解決辦法: 將虛擬
解決VirtualBox安裝的Centos7.6虛擬機器無法ping通的問題
使用 VirtualBox 6.0 在 windows 10 系統下最小化安裝 Linux Centos_7
解決win下無法ping通VM虛擬機CentOS系統的方法
可能 ifconfig linu 說我 退出 時也 win 原因 network 事情描述:公司遷新址,電腦帶過去之後,用xshell連接vm的centos系統老是連接失敗,然後考慮到公司遷新址這個情況,我首先懷疑是ip的問題,然後在vm中執行ifconfig找到cento
解決在Vmare workstation中,Linux虛擬機無法ping通網關的問題
vmare workstation 無法 前言: 我之前用的是橋接模式配置,ip地址可以ping通,網關怎麽都ping不通。我們不妨轉換一個思路,把橋接模式改成NAT模式。 (1) 修改Linux虛擬機網絡適配器模式為NAT模式 (2) 修改虛擬網絡編輯器 查看DHCP
安裝JDK9之後eclipse無法啟動問題解決辦法
簡單 mac os 環境配置 user 配置 環境 err ada 信息 操作系統:MAC OS JDK:1.8.0_131 eclipse:官網最新版 安裝jdk的過程很簡單,從官網下載之後依次點擊就可以了,在終端輸入:java -version 可以看到安裝後的版本信息
phpstudy安裝好之後mysql無法啟動(親測可行)
系統服務 spa 安裝 可能 style 刪除 span sql 無法 安裝好phpstudy後,Apache可以啟動,Mysql無法啟動。 嘗試解決辦法:可能是之前已經裝過Mysql,要把系統服務裏面的MySQL刪除,留下MySQLa服務。 在cmd命令行下輸入:sc
虛擬機器 與 host主機,無法ping通的問題
這個寫的比較簡單,先做以下記錄 centos虛擬機器安裝到別的電腦上,因為linux中的程式需要向外有網路互通,所以需要重新設定ip 通過 ifconfig eth4 192.168.0.20 broadcast 192.168.0.1
虛擬機器與主機無法ping通解決方式彙總
一,ip地址問題 1,純粹的ip地址寫錯 這種情況要先檢查自己主機和虛擬機器的ip地址 &nb
CentOS 7 minimal安裝完成之後安裝圖形介面
實驗環境:CentOS 7 minimal ,hostname:linuxprobe.org IP:10.1.1.53【1】GNOME桌面環境1、先把最小化安裝完成的CentOS7做下快照(本文安裝的CentOS在workstation裡)2、通過遠端連線上安裝
VMware14 安裝CentOS7 實現宿主機ping通虛擬機器、虛擬機器ping通宿主機、虛擬機器能上網且能ping通百度
本文旨在通過通過虛擬機器VMware14來安裝CentOS7 系統,並配置固定IP來實現在Windows系統中使用Linux環境。 本文目錄: 0、本機環境 1、VMware14 初始化 1.1、安裝VMware14
Lwip協議中網路介面(netif)無法ping通解決方法
提出問題: 在除錯單板網路通訊的時候,發現: 1、開啟上位機軟體,並連續傳送讀取資料指令。 2、接上網路線,給單板供電,上位機軟體能正確接收到資料;斷開單板電源,重新給單板供電,上位機能正確接收到資料;頻繁幾次開關機測試,上位機依然能正確接收到資料。 3、在單板供電的情況下,帶電插拔
CENTOS7和Ubuntu16.04配置靜態IP後無法ping通閘道器和外部網路的問題
centos7配置靜態IPcentos7安裝成功後,為了保證多個虛擬機器的通訊,需配置靜態ip和統一閘道器,只需要修改網絡卡(用ifconfig檢視使用的網絡卡,我的是ens33)的配置檔案就行了,其他檔案不用動(/etc/sysconfig/network 這個檔案不用動
ECS例項安全組預設的公網規則被刪除導致無法ping通
問題描述: ECS 伺服器無法ping通,排查防火牆、網絡卡IP配置無誤,回滾系統後仍然無法ping通。 分析解決: 排查後發現,由於該ECS例項安全組預設的公網規則被刪除導致,重配公網入口安全組規則即可。 1. 登入阿里雲ECS控制檯,單擊【安全組】>【配置規則
openstack 主機無法ping通instance,無法ssh到instance
https://docs.openstack.org/zh_CN/user-guide/cli-nova-configure-access-security-for-instances.html 好不容易安裝好了OpenStack,發現無法ping通instance,無法ssh到instance
解決vmbox配置設定好自定義網橋後無法ping通問題
啟動一個docker容器後,在虛擬機器和宿主機上pingdocker容器的ip地址發現無法ping通 原因:通過ping發出的資料包由於沒有找到對應的應用而被丟棄,也沒被轉發 解決方法: 關閉虛擬機器 在vmbox點選設定--網路--網路1--高階--混雜模式設定穩全部
Android Studio安裝完成之後,不能執行的解決辦法
Android小白,想搭建一套Android開發環境,win10 64位系統。但是Android Studio安裝完成之後,雙擊不能執行, 並且沒有任何提示雙擊不能執行, 並且沒有任何提示。同時,java和javac都可以正常工作,也就是說JDK的環境配
關於VMWare虛擬機器下搭建hadoop叢集練習各虛擬機器間無法ping通主機名的問題
最近看了點hadoop的視訊教程,看起來好流弊的樣子,於是忍不住動手在VMWare上嘗試著搭下hadoop的叢集環境,然而對於初學者的我,上來就遇到了一個問題。。。 在跟著嘗試做ssh免密碼登入的時候,在虛擬機器間直接ping ip地址可以ping通,但是ping主機名的