安装Exadata时,如果checkip有报错怎么办?

联系:QQ(5163721)

标题:安装Exadata时,如果checkip有报错怎么办?

作者:Lunar©版权所有[文章允许转载,但必须以链接方式注明源地址,否则追究法律责任.]

在安装老版本 Exadata (Image 11.2.3.2.0以前)时,我们通常会使用一个叫做 的excel来完成环境配置,并生成和这个 onecommand 配套的配置文件。
大概在2013年1月份后,新的版本 Exadata ( Image 11.2.3.2.0以后 )上,我们会使用一个基于java的onecommand工具,图形化的生成配置文件。

通常安装前,我们会跟客户有一个沟通,把Exadata上的各个网络配置等信息跟客户做一个充分沟通,然后根据客户的要求使用onecommand生成配置脚本,其中有一个checkip.zip
这个checkip.zip(使用里面的 checkip.sh )我们会交给客户,用来检查现有环境。

有时候,运行checkip后,发现错误,不是说环境就一定不ready,需要看具体的情况而定:
例如:先插现有环境,发现有2个地方放报错了:

[root@dm01db01 onecommand]# ./checkip.sh -m pre_deploy112

Exadata Database Machine Network Verification version 1.12


Network verification mode post_applyconfig starting ...

Saving output file from previous run as dbm.out_29002

Using name server 9.9.9.3 found in dbm.dat for all DNS lookups

Processing section DOMAIN  : SUCCESS
Processing section NAME    : ERROR - see dbm.out for details   -------这里发现错误
Processing section NTP     : SUCCESS
Processing section GATEWAY : SUCCESS
Processing section SCAN    : SUCCESS
Processing section COMPUTE : SUCCESS
Processing section CELL    : SUCCESS
Processing section FACTORY : SUCCESS
Processing section ILOM    : SUCCESS
Processing section SWITCH  : ERROR - see dbm.out for details   -------这里发现错误
Processing section VIP     : SUCCESS

One or more checks report ERROR. Review dbm.out for details
[root@dm01db01 onecommand]# 

这里,我们发现了两个错误,但是这两个错误是不是致命错误,以至于不能安装呢?
我们来检查一下 checkip.sh 的详细日志,分析下,到底什么问题:

[root@dm01db01 onecommand]# cat dbm.out

Running in mode post_applyconfig
Using name server 9.9.9.3 found in dbm.dat for all DNS lookups

Processing section DOMAIN
lunar.com

Processing section NAME
GOOD : 9.9.9.3 responds to resolve request for dm01db01.lunar.com
ERROR : 9.9.9.4 did not respond to resolve request for dm01db01.lunar.com in 3 seconds   ---这里报错,因为在onecommand中配置了两个DNS,但是安装的时候,我们的环境当时只配置了一个DNS Server

Processing section NTP
GOOD : 9.9.9.3 responds to time server query (/usr/sbin/ntpdate -q)

Processing section GATEWAY
GOOD : 9.9.9.4 pings successfully
GOOD : 192.168.11.254 pings successfully

Processing section SCAN
GOOD : dm01-scan.lunar.com resolves to 3 IP addresses
GOOD : dm01-scan.lunar.com forward resolves to 192.168.11.185
GOOD : 192.168.11.185 reverse resolves to dm01-scan.lunar.com.
GOOD : 192.168.11.185 does not ping
GOOD : dm01-scan.lunar.com forward resolves to 192.168.11.186
GOOD : 192.168.11.186 reverse resolves to dm01-scan.lunar.com.
GOOD : 192.168.11.186 does not ping
GOOD : dm01-scan.lunar.com forward resolves to 192.168.11.187
GOOD : 192.168.11.187 reverse resolves to dm01-scan.lunar.com.
GOOD : 192.168.11.187 does not ping

Processing section COMPUTE
GOOD : dm01db01.lunar.com forward resolves to 10.29.66.1
GOOD : 10.29.66.1 reverse resolves to dm01db01.lunar.com.
GOOD : 10.29.66.1 pings successfully
GOOD : dm01db02.lunar.com forward resolves to 10.29.66.2
GOOD : 10.29.66.2 reverse resolves to dm01db02.lunar.com.
GOOD : 10.29.66.2 pings successfully
GOOD : dm01client01.lunar.com forward resolves to 192.168.11.181
GOOD : 192.168.11.181 reverse resolves to dm01client01.lunar.com.
GOOD : 192.168.11.181 pings successfully
GOOD : dm01client02.lunar.com forward resolves to 192.168.11.182
GOOD : 192.168.11.182 reverse resolves to dm01client02.lunar.com.
GOOD : 192.168.11.182 pings successfully

Processing section CELL
GOOD : dm01cel01.lunar.com forward resolves to 10.29.66.3
GOOD : 10.29.66.3 reverse resolves to dm01cel01.lunar.com.
GOOD : 10.29.66.3 pings successfully
GOOD : dm01cel02.lunar.com forward resolves to 10.29.66.4
GOOD : 10.29.66.4 reverse resolves to dm01cel02.lunar.com.
GOOD : 10.29.66.4 pings successfully
GOOD : dm01cel03.lunar.com forward resolves to 10.29.66.5
GOOD : 10.29.66.5 reverse resolves to dm01cel03.lunar.com.
GOOD : 10.29.66.5 pings successfully

Processing section FACTORY

Processing section ILOM
GOOD : dm01db01-ilom.lunar.com forward resolves to 10.29.66.6
GOOD : 10.29.66.6 reverse resolves to dm01db01-ilom.lunar.com.
GOOD : 10.29.66.6 pings successfully
GOOD : dm01db02-ilom.lunar.com forward resolves to 10.29.66.7
GOOD : 10.29.66.7 reverse resolves to dm01db02-ilom.lunar.com.
GOOD : 10.29.66.7 pings successfully
GOOD : dm01cel01-ilom.lunar.com forward resolves to 10.29.66.8
GOOD : 10.29.66.8 reverse resolves to dm01cel01-ilom.lunar.com.
GOOD : 10.29.66.8 pings successfully
GOOD : dm01cel02-ilom.lunar.com forward resolves to 10.29.66.9
GOOD : 10.29.66.9 reverse resolves to dm01cel02-ilom.lunar.com.
GOOD : 10.29.66.9 pings successfully
GOOD : dm01cel03-ilom.lunar.com forward resolves to 10.29.66.10
GOOD : 10.29.66.10 reverse resolves to dm01cel03-ilom.lunar.com.
GOOD : 10.29.66.10 pings successfully

Processing section SWITCH
GOOD : dm01sw-iba0.lunar.com forward resolves to 10.29.66.12
GOOD : 10.29.66.12 reverse resolves to dm01sw-iba0.lunar.com.
GOOD : 10.29.66.12 pings successfully
GOOD : dm01sw-adm0.lunar.com forward resolves to 10.29.66.11
GOOD : 10.29.66.11 reverse resolves to dm01sw-adm0.lunar.com.
GOOD : 10.29.66.11 pings successfully
GOOD : dm01sw-ibb0.lunar.com forward resolves to 10.29.66.13
GOOD : 10.29.66.13 reverse resolves to dm01sw-ibb0.lunar.com.
GOOD : 10.29.66.13 pings successfully
GOOD : dm01sw-pdua0.lunar.com forward resolves to 10.29.66.14
GOOD : 10.29.66.14 reverse resolves to dm01sw-pdua0.lunar.com.
ERROR : 10.29.66.14 does not ping                              --这里报错,因为我们的系统工程师没有在2个PDU上连接网线到Exadata内置的Cisco交换机,O(∩_∩)O哈哈~
GOOD : dm01sw-pdub0.lunar.com forward resolves to 10.29.66.15
GOOD : 10.29.66.15 reverse resolves to dm01sw-pdub0.lunar.com.
ERROR : 10.29.66.15 does not ping                             --这里报错,原因同上

Processing section VIP
GOOD : dm01client01-vip.lunar.com forward resolves to 192.168.11.183
GOOD : 192.168.11.183 reverse resolves to dm01client01-vip.lunar.com.
GOOD : 192.168.11.183 does not ping
GOOD : dm01client02-vip.lunar.com forward resolves to 192.168.11.184
GOOD : 192.168.11.184 reverse resolves to dm01client02-vip.lunar.com.
GOOD : 192.168.11.184 does not ping
[root@dm01db01 onecommand]# 

从上面的分析,我们可以看到,主要是2个错误:
1,在onecommand中生成配置文件时填写了两个DNS,但是安装的时候,我们的环境当时只配置了一个DNS Server
2,在2个PDU上连接网线到Exadata内置的Cisco交换机

这些都是非致命的问题,解决方法:
1,重新生成配置文件,只填写一个DNS
2,给PDU加上连线,连接到Cisco

再或者,其实这2个错误,可以忽略,O(∩_∩)O哈哈~

此条目发表在 日常运维 分类目录,贴了 , 标签。将固定链接加入收藏夹。

安装Exadata时,如果checkip有报错怎么办?》有 1 条评论

  1. missyou 说:

    Lunar最近明显加快了Exadata的更新频率啊,nice!

发表评论

电子邮件地址不会被公开。 必填项已用 * 标注

您可以使用这些 HTML 标签和属性: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>