rocketmq叢集安裝部署過程(4.0.0版本)、安裝中的常見問題舉例
準備工作:
環境:hadoop11,hadoop12,hadoop13 (Centos6.7)
軟體:rocketmq安裝包(v4.0.0) rocketmq-all-4.0.0-incubating-bin-release.zip
工具:XShell,XFTP
hadoop11: 192.168.106.101
hadoop12: 192.168.106.102
hadoop13: 192.168.106.103
3個虛擬節點的構成如下:
安裝步驟
操作過程
1、安裝包已經上傳至其中3個節點:
hadoop11,hadoop12,hadoop13都執行以下命令:
unzip rocketmq-all-4.0.0-incubating-bin-release.zip
[root@hadoop11 software]# pwd
/home/tuzq/software
修改資料夾名稱:
[root@hadoop11 software]# mv apache-rocketmq-all/ rocketmq
檢視最終的效果:
2、修改配置檔案
我這裡已經將配置檔案提前準備好了,只呈現以下配置檔案的結果。
節點1(192.168.106.101)配置檔案:
配置檔案放在:/home/tuzq/software/rocketmq/conf中
檔名稱是:broker-a-m.properties
cd /home/tuzq/software/rocketmq/conf
vim broker-a-m.properties
檔案中的內容如下:
brokerClusterName=post
brokerName=broker-a
namesrvAddr=192.168.106.101:9876;192.168.106.102:9876
brokerId=0
listenPort=10911
brokerIP1=192.168.106.101
deleteWhen=04
fileReservedTime=72
brokerRole=ASYNC_MASTER
storePathRootDir=/home/tuzq/software/rocketmq/rootdir
storePathCommitLog=/home/tuzq/software/rocketmq/commitlog
defaultTopicQueueNums=4
autoCreateTopicEnable=true
autoCreateSubscriptionGroup=true
flushDiskType=ASYNC_FLUSH
vim broker-c-s.properties
檔案的內容是:
brokerClusterName=post
brokerName=broker-c
namesrvAddr=192.168.106.101:9876;192.168.106.102:9876
brokerId=1
listenPort=10920
brokerIP1=192.168.106.101
deleteWhen=04
fileReservedTime=72
brokerRole=SLAVE
storePathRootDir=/home/tuzq/software/rocketmq/rootdir
storePathCommitLog=/home/tuzq/software/rocketmq/commitlog
defaultTopicQueueNums=4
autoCreateTopicEnable=true
autoCreateSubscriptionGroup=true
flushDiskType=ASYNC_FLUSH
節點2(192.168.106.102)配置檔案:
cd /home/tuzq/software/rocketmq/conf
vim broker-a-s.properties
brokerClusterName=post
brokerName=broker-a
namesrvAddr=192.168.106.101:9876;192.168.106.102:9876
brokerId=1
listenPort=10920
deleteWhen=04
brokerIP1=192.168.106.102
fileReservedTime=72
brokerRole=SLAVE
storePathRootDir=/home/tuzq/software/rocketmq/rootdir
storePathCommitLog=/home/tuzq/software/rocketmq/commitlog
defaultTopicQueueNums=4
autoCreateTopicEnable=true
autoCreateSubscriptionGroup=true
flushDiskType=ASYNC_FLUSH
vim broker-b-m.properties
檔案內容是:
brokerClusterName=post
brokerName=broker-b
namesrvAddr=192.168.106.101:9876;192.168.106.102:9876
brokerId=0
listenPort=10911
brokerIP1=192.168.106.102
deleteWhen=04
fileReservedTime=72
brokerRole=ASYNC_MASTER
storePathRootDir=/home/tuzq/software/rocketmq/rootdir
storePathCommitLog=/home/tuzq/software/rocketmq/commitlog
defaultTopicQueueNums=4
autoCreateTopicEnable=true
autoCreateSubscriptionGroup=true
flushDiskType=ASYNC_FLUSH
節點3(192.168.106.103)配置檔案:
cd /home/tuzq/software/rocketmq/conf
vim broker-b-s.properties
檔案內容是:
brokerClusterName=post
brokerName=broker-b
namesrvAddr=192.168.106.101:9876;192.168.106.102:9876
brokerId=1
listenPort=10920
brokerIP1=192.168.106.103
deleteWhen=04
fileReservedTime=72
brokerRole=SLAVE
storePathRootDir=/home/tuzq/software/rocketmq/rootdir
storePathCommitLog=/home/tuzq/software/rocketmq/commitlog
defaultTopicQueueNums=4
autoCreateTopicEnable=true
autoCreateSubscriptionGroup=true
flushDiskType=ASYNC_FLUSH
vim broker-c-m.properties
檔案內容是:
brokerClusterName=post
brokerName=broker-c
namesrvAddr=192.168.106.101:9876;192.168.106.102:9876
brokerId=0
listenPort=10911
brokerIP1=192.168.106.103
deleteWhen=04
fileReservedTime=72
brokerRole=ASYNC_MASTER
storePathRootDir=/home/tuzq/software/rocketmq/rootdir
storePathCommitLog=/home/tuzq/software/rocketmq/commitlog
defaultTopicQueueNums=4
autoCreateTopicEnable=true
autoCreateSubscriptionGroup=true
flushDiskType=ASYNC_FLUSH
3、啟動nameserver
三臺機器上都建立logs資料夾(rocketmq中沒有這個logs資料夾):
建立資料夾命令:
mkdir -p /home/tuzq/software/rocketmq/logs
節點1和節點2的啟動命令:
nohup sh /home/tuzq/software/rocketmq/bin/mqnamesrv >/home/tuzq/software/rocketmq/logs/mqnamesrv.log 2>&1 &
注意:我這裡將啟動日誌重定義到了logs路徑下,需要提前手動建立logs資料夾,以便於統一管理日誌,方便檢視。
下圖中展示了啟動命令,日誌中可以看到NameServer成功啟動的日誌。
NameServer - 節點1
請注意hostname,下面是hadoop11
[[email protected] conf]# nohup sh /home/tuzq/software/rocketmq/bin/mqnamesrv >/home/tuzq/software/rocketmq/logs/mqnamesrv.log 2>&1 &
[1] 9676
[[email protected] conf]# cat /home/tuzq/software/rocketmq/logs/mqnamesrv.log
nohup: 忽略輸入
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=320m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: Using the DefNew young collector with the CMS collector is deprecated and will likely be removed in a future release
Java HotSpot(TM) 64-Bit Server VM warning: UseCMSCompactAtFullCollection is deprecated and will likely be removed in a future release.
The Name Server boot success. serializeType=JSON
[[email protected] conf]#
截圖如下:
在下面的演示過程中將不再進行截圖,所有的過程都把程式碼粘貼出來,在進行檢視的時候注意機器的hostname
NameServer = 節點2
[[email protected] rocketmq]# nohup sh /home/tuzq/software/rocketmq/bin/mqnamesrv >/home/tuzq/software/rocketmq/logs/mqnamesrv.log 2>&1 &
[1] 9558
[[email protected] rocketmq]# cat /home/tuzq/software/rocketmq/logs/mqnamesrv.log
nohup: 忽略輸入
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=320m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: Using the DefNew young collector with the CMS collector is deprecated and will likely be removed in a future release
Java HotSpot(TM) 64-Bit Server VM warning: UseCMSCompactAtFullCollection is deprecated and will likely be removed in a future release.
The Name Server boot success. serializeType=JSON
[[email protected] rocketmq]#
在節點1和節點2上分別執行jps命令,可以看到類似如下的結果:
[root@hadoop11 conf]# jps
9682 NamesrvStartup
9774 Jps
4、啟動Broker-a(Master位於節點1、Slave位於節點2)
broker-a分為Master和slave,分別位於節點1和節點2上,需要分別啟動。
注意:需要根據啟動角色,為broker指定一個配置檔案
在執行下面的命令前,先修改檔案路徑:{ROCKET_HOME}/bin/runbroker.sh中的JVM引數配置,如若不改,將會因為記憶體不夠啟動不了broker.
修改前:JAVA_OPT="${JAVA_OPT} -server -Xms8g -Xmx8g -Xmn4g"
修改後:JAVA_OPT="${JAVA_OPT} -server -Xms256m -Xmx512m -Xmn512m -XX:PermSize=256m -XX:MaxPermSize=640m"
如圖所示:
broker-a的master - 節點1
命令:
[root@hadoop11 bin]# nohup sh /home/tuzq/software/rocketmq/bin/mqbroker -c /home/tuzq/software/rocketmq/conf/broker-a-m.properties >/home/tuzq/software/rocketmq/logs/broker-a-m.log 2>&1 &
[2] 10081
[root@hadoop11 bin]# jps
9682 NamesrvStartup
10088 BrokerStartup
10154 Jps
[root@hadoop11 bin]# cat /home/tuzq/software/rocketmq/logs/broker-a-m.log
nohup: 忽略輸入
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=256m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=640m; support was removed in 8.0
[root@hadoop11 bin]#
broker-a的slave - 節點2:
命令如下:
[root@hadoop12 bin]# nohup sh /home/tuzq/software/rocketmq/bin/mqbroker -c /home/tuzq/software/rocketmq/conf/broker-a-s.properties >/home/tuzq/software/rocketmq/logs/broker-a-s.log 2>&1 &
[2] 9926
[root@hadoop12 bin]# jps
9989 Jps
9564 NamesrvStartup
9933 BrokerStartup
[root@hadoop12 bin]# cat /home/tuzq/software/rocketmq/logs/broker-a-s.log
nohup: 忽略輸入
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=256m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=640m; support was removed in 8.0
[root@hadoop12 bin]#
驗證broker-a:
broker-a啟動結束,這時候可以使用命令檢視一下rocketmq叢集狀態:
命令:
[[email protected] bin]# sh /home/tuzq/software/rocketmq/bin/mqadmin clusterList -n 192.168.106.101:9876
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
#Cluster Name #Broker Name #BID #Addr #Version #InTPS(LOAD) #OutTPS(LOAD) #PCWait(ms) #Hour #SPACE
post broker-a 0 192.168.106.101:10911 V4_0_0_SNAPSHOT 0.00(0,0ms) 0.00(0,0ms) 0 419078.85 -1.0000
post broker-a 1 192.168.106.102:10920 V4_0_0_SNAPSHOT 0.00(0,0ms) 0.00(0,0ms) 0 419078.85 0.1532
[[email protected] bin]#
5、啟動broker-b(Master位於節點2、slave位於節點3)
broker-b的Master - 節點2
[root@hadoop12 bin]# nohup sh /home/tuzq/software/rocketmq/bin/mqbroker -c /home/tuzq/software/rocketmq/conf/broker-b-m.properties >/home/tuzq/software/rocketmq/logs/broker-b-m.log 2>&1 &
[3] 10175
[root@hadoop12 bin]# jps
10182 BrokerStartup
9564 NamesrvStartup
9933 BrokerStartup
10238 Jps
[root@hadoop12 bin]# cat /home/tuzq/software/rocketmq/logs/broker-b-m.log
nohup: 忽略輸入
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=256m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=640m; support was removed in 8.0
[root@hadoop12 bin]#
broker-b的slave - 節點3:
[root@hadoop13 bin]# nohup sh /home/tuzq/software/rocketmq/bin/mqbroker -c /home/tuzq/software/rocketmq/conf/broker-b-s.properties >/home/tuzq/software/rocketmq/logs/broker-b-s.log 2>&1 &
[1] 9953
[root@hadoop13 bin]# jps
9969 Jps
9960 BrokerStartup
[root@hadoop13 bin]# cat /home/tuzq/software/rocketmq/logs/broker-b-s.log
nohup: 忽略輸入
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=256m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=640m; support was removed in 8.0
[root@hadoop13 bin]#
驗證broker-b
[[email protected] bin]# sh /home/tuzq/software/rocketmq/bin/mqadmin clusterList -n 192.168.106.101:9876
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
#Cluster Name #Broker Name #BID #Addr #Version #InTPS(LOAD) #OutTPS(LOAD) #PCWait(ms) #Hour #SPACE
post broker-a 0 192.168.106.101:10911 V4_0_0_SNAPSHOT 0.00(0,0ms) 0.00(0,0ms) 0 419078.98 -1.0000
post broker-a 1 192.168.106.102:10920 V4_0_0_SNAPSHOT 0.00(0,0ms) 0.00(0,0ms) 0 419078.98 0.1532
post broker-b 0 192.168.106.102:10911 V4_0_0_SNAPSHOT 0.00(0,0ms) 0.00(0,0ms) 0 419078.98 0.1532
post broker-b 1 192.168.106.103:10920 V4_0_0_SNAPSHOT 0.00(0,0ms) 0.00(0,0ms) 0 419078.98 0.0190
[[email protected] bin]#
6、啟動broker-b(Master位於節點3,Slave位於節點1)
broker-c的Master - 節點3
[root@hadoop13 bin]# nohup sh /home/tuzq/software/rocketmq/bin/mqbroker -c /home/tuzq/software/rocketmq/conf/broker-c-m.properties >/home/tuzq/software/rocketmq/logs/broker-b-s.log 2>&1 &
[2] 10201
[root@hadoop13 bin]# cat /home/tuzq/software/rocketmq/logs/broker-b-s.log
nohup: 忽略輸入
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=256m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=640m; support was removed in 8.0
[root@hadoop13 bin]#
broker-c的Slave - 節點1
[root@hadoop11 bin]# nohup sh /home/tuzq/software/rocketmq/bin/mqbroker -c /home/tuzq/software/rocketmq/conf/broker-c-s.properties >/home/tuzq/software/rocketmq/logs/broker-a-m.log 2>&1 &
[3] 10458
[root@hadoop11 bin]# jps
10465 BrokerStartup
9682 NamesrvStartup
10519 Jps
10088 BrokerStartup
[root@hadoop11 bin]# cat /home/tuzq/software/rocketmq/logs/broker-a-m.log
nohup: 忽略輸入
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=256m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=640m; support was removed in 8.0
[root@hadoop11 bin]#
驗證broker-c
[[email protected] bin]# sh /home/tuzq/software/rocketmq/bin/mqadmin clusterList -n 192.168.106.101:9876
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
#Cluster Name #Broker Name #BID #Addr #Version #InTPS(LOAD) #OutTPS(LOAD) #PCWait(ms) #Hour #SPACE
post broker-a 0 192.168.106.101:10911 V4_0_0_SNAPSHOT 0.00(0,0ms) 0.00(0,0ms) 0 419079.12 0.0203
post broker-a 1 192.168.106.102:10920 V4_0_0_SNAPSHOT 0.00(0,0ms) 0.00(0,0ms) 0 419079.12 0.1532
post broker-b 0 192.168.106.102:10911 V4_0_0_SNAPSHOT 0.00(0,0ms) 0.00(0,0ms) 0 419079.12 0.1532
post broker-b 1 192.168.106.103:10920 V4_0_0_SNAPSHOT 0.00(0,0ms) 0.00(0,0ms) 0 419079.12 0.0190
post broker-c 0 192.168.106.103:10911 V4_0_0_SNAPSHOT 0.00(0,0ms) 0.00(0,0ms) 0 419079.12 0.0190
post broker-c 1 192.168.106.101:10920 V4_0_0_SNAPSHOT 0.00(0,0ms) 0.00(0,0ms) 0 419079.12 0.0203
[[email protected] bin]#
7、常見問題
問題1
啟動broker的時候提示記憶體不夠的錯誤
解決方法:由於個人電腦配置不夠,無法為虛擬機器申請更大的記憶體。所以,採用修改broker啟動記憶體的方式解決了。
修改檔案路徑:{ROCKET_HOME}/bin/runbroker.sh
修改前:JAVA_OPT=”
如圖所示:
重新啟動broker,日誌中沒有錯誤,jps程序中也可以看到broker正常啟動。
問題2
在同一臺機器上啟動多個broker的時候提示如下錯誤:
問題原因:
按照本文最開始的圖所示,同一臺機器上會存在兩個Broker,如果不進行特殊指定,broker的預設埠是10911
所以一臺機器上啟動兩個broker時,第二個broker就會出現埠被佔用的錯誤。
解決辦法:
修改rocketmq的配置檔案,增加listenPort配置。配置之後如下所示:
同一臺機器的配置檔案:
–>broker-a-m.properties
–>broker-c-s.properties
使用JPS檢視一下程序是否有問題
在檢視一下啟動日誌是否有問題
最後使用clusterList命令來驗證一下叢集健康狀態
命令:sh bin/mqadmin clusterList -n 192.168.106.101:9876
成功實現了,如本文最開始圖片所示的安裝部署
相關推薦
rocketmq叢集安裝部署過程(4.0.0版本)、安裝中的常見問題舉例
準備工作: 環境:hadoop11,hadoop12,hadoop13 (Centos6.7) 軟體:rocketmq安裝包(v4.0.0) rocketmq-all-4.0.0-incubating-bin-release.zip 工具:X
Kubernetes(K8s)安裝部署過程(一)--證書安裝
更改 目錄 hand /etc 主題 nbsp kubecon 安裝部署 post 一、安裝前主題環境準備 1、docker安裝 建議使用官網yum源安裝,添加yum源之後,直接yum install docker即可 2、關閉所有節點的selinux
Kubernetes(K8s)安裝部署過程(三)--創建高可用etcd集群
方式安裝 10.9 修改配置 取消 roo initial code clas list 這裏的etcd集群復用我們測試的3個節點,3個node都要安裝並啟動,註意修改配置文件 1、TLS認證文件分發:etcd集群認證用,除了本機有,分發到其他node節
Kubernetes(K8s)安裝部署過程(四)--Master節點安裝
emc 不用 ces 成功 sts var 獲取 art health 再次明確下架構: 三臺虛擬機 centos 7.4系統,docker為17版本,ip為10.10.90.105到107,其中105位master,接下來的master相關組件安裝到此機器上。 etc
Kubernetes(K8s)安裝部署過程(六)--node節點部署
sch wan tool pods systemd tps stat mis type hi,everybody,我回來了,之前安裝到flannel之後,文章一直沒有更新,甚至不少小夥伴都來加qq詢問是否繼續更新了, 這裏說明下原因,我在部署1.91node的時候的確出現
Kubernetes1.91(K8s)安裝部署過程(八)-- kubernetes-dashboard安裝
addons quest 集群 heapster 管理 min sele author aps kubernets-dashboard顧名思義是操作面板安裝,也就是可視化管理機器,同意我們用鏡像結合配置文件部署。 1、下載鏡像: docker pull reg
centos7.4安裝rabbitmq服務(3.7.10版本)
一、需要安裝erlang版本依賴,可以使用二進位制安裝方式,也可以通過rpm安裝,但是安裝的時候會提示需要erlang版本>=19.3,而且直接預設yum倉庫中的版本較低。,為了節省時間,文章中直接通過新增yum源安裝。 1.下載rabbitmq的rpm包(http://www.rabbitmq.co
Linux(最簡單的版本)下安裝MySQL -筆者遇到一系列坑
首先先上傳安裝包:筆者使用的是rpm按章包: https://pan.baidu.com/s/171UVMHmPBQX6ObcoXeb2BA 我之前到處這這個安裝包,在官網上,我都沒找到這個rpm的安裝包。 MySQL的官網下載: https://dev.mysql.com/downlo
hadoop-3.0.0-alpha4安裝部署過程
auth specific daemon ive bsp admin ram 8.14 產生 關閉防火墻 #systemctl stop firewalld.service #停止firewall #systemctl disable firewalld.service #
centos6.8下安裝部署LNMP(備註:nginx1.8.0+php5.6.10+mysql5.6.12)
debug pcr chkconfig c++ sam libjpeg php 執行 btool 在平時運維工作中,經常需要用到LNMP應用框架。以下對LNMP環境部署記錄下: 1)前期準備:為了安裝順利,建議先使用yum安裝依賴庫[root@opd ~]#yum ins
自制Hadoop偽分佈、叢集安裝詳細過程(vmware)
Hadoop單機版、偽分佈、叢集安裝教程推薦連結: http://dblab.xmu.edu.cn/blog/page/2/?s=Hadoop 注:vmware6.5及以上,執行命令基本相同,除了編輯檔案時“vi”指令替換為“vim”指令 一、下載安裝所需檔案  
linux環境下(centos 7)安裝redis(4.0.11版本)
以下是我安裝redis的筆記: 首先進入到linux環境需要安裝redis的目錄,我的是/etc/local/hxq 然後 wget http://download.redis.io/releases/redis-4.0.11.tar.gz 解壓到當前目錄:tar -z
4.Kali 1.0 / 2.0 安裝中文輸入法(谷歌pinyin + 其他)
1.kali預設是沒有中午輸入法的,需要自己安裝一下 2.首先我們先獲取root許可權 [email protected]:~$ su密碼: 3.安裝中文輸入法(apt-get 指令不會的同學可以學習一下基礎指令哦) [email protected]:/home/dnt#
linux centos7 tomcat下安裝部署solr-5.4.0
想安裝個solr看看啥效果,網上搜了半天也沒搞出來,雜七雜八的,現在總算出來了,整理了一下,僅供參考,有什麼不對的歡迎指出,共同進步。 1.把官網下載的solr-5.4.0.tgz上傳到linux伺服器上,我的上傳位置為/home/gaolei。將s
最新Win7 +Python3.6.0(Anaconda3-4.3.21)+Tensorflow的安裝與配置(不用切換python3.5)
一、首先進入Anaconda官網下載 https://www.anaconda.com/download/各位根據自己電腦配置下載對應的版本,我這裡下載的是Python3.6version 64bit的版本 下載並安裝完成後,開啟 CMD, 輸入 'conda --v
ArcGIS Enterprise 10.5.1 靜默安裝部署記錄(Centos 7.2 minimal版)- 2、安裝Portal for ArcGIS
-a 切換 https stop user 安裝 執行 limits 方式 安裝Portal for ArcGIS 解壓portal安裝包,tar -xzvf Portal_for_ArcGIS_Linux_1051_156440.tar.gz 切換到arcgis賬戶靜
ArcGIS Enterprise 10.5.1 靜默安裝部署記錄(Centos 7.2 minimal版)- 3、安裝 ArcGIS for Server
切換 驗證 裝包 start dap sof 訪問權限 tar 服務 安裝ArcGIS for Server 解壓server安裝包,tar -xzvf ArcGIS_Server_Linux_1051_156429.tar.gz 切換到arcgis賬戶靜默安裝serv
ArcGIS Enterprise 10.5.1 靜默安裝部署記錄(Centos 7.2 minimal版)- 1、安裝前準備
計算機 boot thread connect conf 1.8 div 導入 top 安裝前準備 上傳文件到服務器,x-ftp xshell登陸Centos 檢查機器名 修改機器名為:portal.cloud.local 方法一:零時設置,重啟後失效,
Cisco模擬器GNS3(2.0.0b4版本)安裝和配置
設備 適用於 實驗 交換機 運行時 裏的 https sco style GNS3(2.0.0b4版本)(適用於CCNA和CCNP) 下載地址:https://www.gns3.com/software 包含GNS3.exe和GSN3 VM 註意下載
Virtual Box 安裝過程(卸載Vmware後)
all 所有 有用 box window mac work col virtual VirtualBox安裝前的操作:(或許某些操作不一定有用,但是我是這麽做下來的,最後也安裝成功了) 步驟一:停止之前安裝的vmware的所有服務(如果之前沒有安裝過虛擬機軟件,無需做此操