hp openviewread.pudn.com/downloads12/doc/50545/hp11_nnm完全实施... · web viewhp openview...

NNM UNIX使用手册

中国惠普公司软件事业部

NNM UNIX 使用手册

1


目录第一章准备工作......................................................................................................................................4

1.检查硬件配置....................................................................................................................................42.检查软件配置....................................................................................................................................4

第二章安装 NNM....................................................................................................................................8

1. 在本地系统上安装 ORACLE-FOR-OPENVIEW..................................................................................82. 在本地系统上安装NNM.................................................................................................................93.安装相关的 PATCH............................................................................................................................134.查看NNM及相关 PATCH安装情况................................................................................................135.配置 NNM 的数据库.......................................................................................................................136. NNM 验证过程...............................................................................................................................177. NNM 注册.......................................................................................................................................18

第三章配置 NNM..................................................................................................................................20

1.NNM 运行于 WEB............................................................................................................................202.NNM 轮询间隔的配置....................................................................................................................203.NNM 的故障管理配置....................................................................................................................214.NNM 的性能管理配置....................................................................................................................235.NNM 种子文件的配置....................................................................................................................296.NNM 被管节点图标的增加与修改................................................................................................307.NNM 分布式管理的配置................................................................................................................318.NNM 操作员用户的配置................................................................................................................339.分布式结构设计..............................................................................................................................349.1 配置过滤器...................................................................................................................................349.2 配置收集站...................................................................................................................................359.3配置管理站...................................................................................................................................369.4 DETERMINING ALL OBJECTS MONITORED BY A COLLECTION STATION........................................369.5 PERFORMING A FULL TOPOLOGY SYNCHRONIZATION...................................................................379.6 配置事件上传...............................................................................................................................37

第四章 NNM 的备份与恢复..................................................................................................................39

1. 单用户模式做系统全备份.............................................................................................................392. NNM 数据备份与恢复...................................................................................................................39

附录一文件清单....................................................................................................................................41

1. /ETC/PASSWD....................................................................................................................................412. /ETC/GROUP......................................................................................................................................423. /ETC/HOSTS.......................................................................................................................................434. /ETC/NSSWITCH.CONF.......................................................................................................................445. /ETC/RC.CONFIG.D/NETCONF.............................................................................................................456. /.PROFILE..........................................................................................................................................48

2


7. /HOME/ORACLE/.PROFILE..................................................................................................................508. CRONTAB -L......................................................................................................................................519. /ETC/RESOLV.CONF...........................................................................................................................531. BDF...................................................................................................................................................542. VGDISPLAY -V...................................................................................................................................553. IOSCAN -FN.......................................................................................................................................584. SWLIST..............................................................................................................................................605. UNAME -A.........................................................................................................................................646. SWAPINFO.........................................................................................................................................657. LANSCAN..........................................................................................................................................668. dmesg...............................................................................................................................................67

3


第一章准备工作HP OpenView Network Node Manager V6.1（以下简称 NNM） for HP-UX

11.0 在安装之前需要对设备的硬件与软件的配置状况进行检测，查看其是否满足 NNM运行的需求，所以本章主要叙述NNM安装之前的准备工作。

1.检查硬件配置运行NNM v6.1时要求的机器硬件配置如下：

HP 9000 workstation, series 700或 800

CD drive 96MB RAM 250MB Free disk space 192 MB swap

实际检测步骤如下：

1. 以 root身份登录，运行 ioscan，检测 CD-ROM drive;

见附录

2. 运行 bdf检查磁盘空间：见附录

3．运行 swapinfo检查 swap分区：见附录

2.检查软件配置NNM v6.1对软件的环境要求如下：

4


HP-UX (Version 10.20,11.X) which includes: The Common Desktop Environment (CDE) X Windows and OSF/Motif (or HP VUE) Netscape Navigator web browser (version 4.06 or higher) Common Desktop Environment (CDE) Help files:

/usr/dt/lib/libDtHelp.1/usr/dt/lib/libDtSvc.1

实际检测步骤如下：

1．以 root身份登录，swlist

见附录

2．运行 uname -a 检查操作系统的版本见附录

3．检查网络操作

没有正确的网络连接和网络配置，网管工作站(NMS)不能正常工作。使用ifconfig命令和/etc/rc.config.d/netconf中的配置数据验证 NMS的 IP地址和缺省的网关与技术需求工作表中收集的信息是一致的。

lanscan

见附录

使用 Ping验证下面设备的可达性： NMS自身缺省网关

使用 nslookup命令检查工作站怎样做名字解析。这个命令将指出它是使用/

etc/hosts还是域名服务器。

5


/etc/resolv.conf

见附录/etc/nsswitch.conf

见附录

看看是否 DNS有/etc/hosts文件作后备，确保不论以 root还是非 root用户登录，/etc/hosts和 DNS为管理 server和所有被管节点返回同样的值。可以临时改变/etc/nsswitch.conf的搜索层次来完成这一任务。

4．改变目录，检查/usr/dt/lib/libDtHelp.1与/usr/dt/lib/libDtSvc.1是否存在.

# ls /usr/dt/lib/libD*/usr/dt/lib/libDtHelp.1 /usr/dt/lib/libDtSvc.2/usr/dt/lib/libDtHelp.2 /usr/dt/lib/libDtSvc.3/usr/dt/lib/libDtHelp.3 /usr/dt/lib/libDtTerm.1/usr/dt/lib/libDtMrm.3 /usr/dt/lib/libDtTerm.2/usr/dt/lib/libDtPrint.1 /usr/dt/lib/libDtTerm.3/usr/dt/lib/libDtPrint.2 /usr/dt/lib/libDtWidget.1/usr/dt/lib/libDtPrint.3 /usr/dt/lib/libDtWidget.2/usr/dt/lib/libDtSvc.1 /usr/dt/lib/libDtWidget.3

#

5．检查/较正内核参数使用 SAM检查所有相关的内核参数的最小值符合要求。如果必要，做任何

需要的调整，然后创建一个新的内核并重新启动。

6


7


a. If your installation includes more than 35 managed nodes that use DCE/TCP communication, increase the maxfiles setting to: 3*Number_of_DCE/TCP_nodes + 15b. If more than 10 GUIs (Java and/or Motif) are started, add (6 * NumberOfGUIs).c. Use the formula: (16*(NPROC+16+MAXUSERS)/10+384+2*(npty+nstrpty)) or (75 * (NumberOfGUIs) + 1000), whichever is greater.d. Use the maximum of 200 or the formula: (35 + 5 * NumberOfGUIs)e. Use the formula: (20+15*MAXUSERS) or (200 +6 *NumberOfGUIs), whichever is greater.

Maxusers=192, nfiles=3214

8


第二章安装 NNM

1. 在本地系统上安装NNM

1. 使用”root”用户登录到系统2. 安装一个流行的 HPUX11.0 的 WEB 浏览器 Netscape

/opt/netscape

3. 将NNM的安装盘插入光驱4. 将光驱挂到文件系统上，在提示符下输入：

/etc/mount /dev/dsk/c0t0d0 /cdrom

5. 安装NNM，在提示符下输入：cd /cdrom./install

根据屏幕提示逐步完成安装过程，具体步骤如下面各图所示：

9


NNM安装图示（一）

10


NNM安装图示（二）

11


NNM安装图示（三）

12


2.安装相关的 patch

安装完NNM后，需要安装相关的 patch使之正常使用，步骤如图1．解包

sh /opt/patches/PHSS_22424

2．在提示符下输入:

swinstall -x autoreboot=true -x patch_match_target=true \ -s /opt/patches/PHSS_22424.depot

3.查看NNM及相关 patch安装情况运行 swlist：#… …PHSS_22424 1.0 OV NNM6.1 Consolidated Patch 10/08/2000 #

4. NNM 验证过程1. 启动NNM：/opt/OV/bin/ovstart –c

2. 确认NNM进程运行状态：/opt/OV/bin/ovstatus –c

执行 ovstatus –c命令。下面的样本输出示例了执行 ovstatus命令的结果。/opt/OV/bin # ./ovstatus -c Name PID State Last Message(s) OVsPMD 1060 RUNNING - ovsessionmgr 1066 RUNNING Initialization complete. ovwdb 1067 RUNNING Initialization complete. ovuispmd 1141 RUNNING Initialized. 2 ovw clients registered. ovtrapd 1123 RUNNING Initialization complete. ovactiond 1124 RUNNING Initialization complete. ovalarmsrv 1125 RUNNING Initialization complete.

13


pmd 1068 RUNNING Initialization complete. ovdbcheck 1069 RUNNING Connected to embedded database. ovrequestd 1070 RUNNING Initialization complete. httpd - unknown (Does not communicate with ovspmd.) ovtopmd 1122 RUNNING Connected to native database "openview". netmon 1142 RUNNING Initialization complete. snmpCollect 1143 RUNNING Initialization complete.

浏览 ovstatus的输出确保所有的进程在运行态。记录所有没有运行的进程，使用ovstart <procname>启动它们。

3. 启动NNM界面：/opt/OV/bin/ovw

3.1 检验 ovw

ovw是NNM的用户接口。当 ovw启动后，查看 IP Internet图标是否监色蓝色指示一种未知的状态并且网管工作站没有发现任何结点，如果存在这种情况，应考虑下面方法：- 使用 ifconfig命令确定硬件接口状态(通常是 lan0)。如果它处于停止

(down)状态，使用 ifconfig重新启动它。(看 ifconfig手册页了解更多信息以及它的语法），如果 ifconfig不能启动接口，NMS需要重启，在某些硬件配置中当启动NMS后网络接口处于失效状态就需要这样做。

- 重新检查网管机 IP和 SNMP配置。- Ping(/etc/ping)网管机，为了至少发现一个结点，产生到 NMS自身的信息量。

- Ping所有已知结点，但这个策略只能在至少发现一个结点后使用- 对于所有其它的情况，使用 Help下拉菜单访问 NNM 联机帮助以获得进一步排除故障的帮助。

3.2 验证正确的映射14


确保 ipmap(OV后台进程)以正确方式生成map。正确的NNM运行应具备以下几点：- 在 IP internet map上至少出现一个网络，并且它是NMS所在的子网。- NMS的缺省的网关路由器存在，并且是 SNMP可存取的。- 在NMS所在的子网上至少有一个网段(segment)

如果在发现所有结点时有问题，像 traceroute命令行实用程序可用于鉴别 netman

进程没有发现的路由器。这可以帮助发现那些配置以不正确的 community名或不能处理 SNMP 请求的路由器。

5. NNM 注册第一步：收集 License 信息在你的认证书（Entitlement Certificate）上，找到并记录下下面的两个数字：HP order Number: ______________HP product number: ______________1. If NNM

Is already running and displaying a dialog box which ask, Request your password now?, select OK.

Is already running, but no dialog box is showing, you can do one of two things:

- In the Options pull-down menu, select License Password.- Open an hpterm window. Type: /opt/OV/bin/ovnnmPassword

Is not currently running, open an hpterm window, type: /opt/OV/bin/ovnnmPassword

2. The license Password dialog appears. This box has three options:- Current Password lists any password already assigned to the NNM

product you are currently running.- Request Password takes you to the next step in requesting a permanent

password.

15


- An empty field box lets you enter a password into your NNM product’s files.

3. Select the Request Password button.4. The Request Password dialog appears. This box will display your IP

address. Write it below:IP address __________________________

第二步：完成并发送 License 申请表有四种方式发送 License 申请表：

- by using the online HP PDC web site(http://www.webware.hp.com )

- by sending electronic mail to the HP PDC(For Asia/Pacific: [email protected])

- by faxing a form to the HP PDC(For Asia/Pacific: +81(3)3227-5238

- by telephoning the HP PDC(For Asia/Pacific: +81(3)3227-5264

第三步：安装永久 License

有两种方法： 1.If your “Instant-On” temporary password is still valid, use the following method:- Start the NNM. The License Password dialog will appear. - If you received your permanent password from the web site, move the

window containing the password certificate to one side of your screen so you can see it as well as the License Password dialog.

- From the dialog, cut and paste, or type, the permanent password (and any string enclosed in double quotation marks appearing after the password) in the blank field.

- Select Apply. A dialog appears, confirming your password’s installation.

2.If your “Instant-On” temporary password has expired and you cannot start up NNM, use the method below instead:

- Run the ovnnmPassword utility at a command prompt. Type: /opt/OV/bin/ovnnmPassword

- The License Password dialog appears. Type the permanent password (and any string enclosed in double quotation marks appearing after the password) in the blank field.

- Select Apply. A dialog appears, confirming your password’s installation.

16

mailto:[email protected]

http://www.webware.hp.com/


第三章配置 NNM

1.NNM 运行于 web

1. 如需要，可安装 web browser 产品。（NNM 安装过程中会自动安装 web

server )

2. As root, 启动NNM进程, type: /opt/OV/bin/ovstart –c

3. 启动NNM界面, type: /opt/OV/bin/ovw

4. 启动web browser 产品5. 在web环境下运行NNM：

- If NNM is running on your system, select the Tools: HP OpenView Launcher item from the NNM menu bar. The Launcher’s window will appear.

- If NNM is running on a system other than yours, open up a web browser on your system. In the browser’s Location field, specify one of the following URLs: (For HP-UX/Solaris: http://hostname:8880/OVCgi/ovlaunch.exe )

(注： hostname 是 web server 的域名全称，如 mymachine.myco.com)

2.NNM 轮询间隔的配置设备节点或网段轮询间隔 Community

骨干网络路由器 10.0.7.1-910.0.3.1-2

10s Bjidc-nms

系统主机网段 10.0.3.0/26 1m public

网络设备 210.51.18.2-5 1m Bjidc-nms

其他网段 210.51.16.0/27210.51.16.33/27210.51.0.0/21210.51.8.0/21

2m public

17

http://hostname:8880/OVCgi/ovlaunch.exe


3.NNM 的故障管理配置故障类型报警触发条件节点或网段报警方式MAC 地址改变

设备 MAC 地址发生改变

10.0.7.0/26

10.0.3.0/26

以蓝色显示在事件监控台上，并声音报警

18


宕机、主机不通

Node Down 210.51.0.0/21

210.51.8.0/21

10.0.3.0/26

立即以红色显示在事件监控台上，声音报警并以呼机方式呼叫管理员

主机网卡、路由设备端口失效

Interface

Down

210.51.0.0/21

210.51.8.0/21

10.0.3.0/26

立即以红色显示在事件监控台上，声音报警并以呼机方式呼叫管理员

主机网卡失效及路由设备端口失效

Email 报警的配置1. /etc/nsswitch.conf:

hosts: files

protocols: files

19


services: files

networks: files

netgroup: files

rpc: files

aliases: files

2. sendmail.cf:

将 #Dj$w.Foo.COM 变为 Dj$w.china.hp.com

3. /etc/hosts 中加入 mail server

203.93.288.252 xcn01.china.hp.com xcn01.china.hp.com.

4. mailservs:

export SENDMAIL_SERVER=1

MAILSERVER=xcn01.china.hp.com

5. /sbin/init.d/sendmail stop

/sbin/init.d/sendmail start

6. echo 'Subject:Node down!\n$2 node down!\n' | /usr/lib/sendmail

'[email protected]'

声音报警的配置/opt/audio/bin/send_sound -wav /opt/OV/contrib/NNM/Audio/nodedown.wav

chmod 777 /opt/OV/contrib/NNM/Audio/nodedown.wav

20


4.NNM 的性能管理配置

性能参数阀值节点或网段是否记录备注端口流量 bjrtccia751 10.0.7.3

bjrtccia752 10.0.7.41/2/4ap1000-1 10.0.7.5ap1000-2 10.0.7.6nms-manager 10.0.3.44

是 5min

端口利用率 75% bjrtccia751 10.0.7.3bjrtccia752 10.0.7.41/2/4ap1000-1 10.0.7.5ap1000-2 10.0.7.6nms-manager 10.0.3.44

是以黄色显示在事件监控台上

Cpu 利用率 75% bjrtccia751 10.0.7.3bjrtccia752 10.0.7.4ap1000-1 10.0.7.5ap1000-2 10.0.7.6nms-manager 10.0.3.44


内存利用率 75% bjrtccia751 10.0.7.3bjrtccia752 10.0.7.4ap1000-1 10.0.7.5ap1000-2 10.0.7.6nms-manager 10.0.3.44


数据缓冲区利用率

75% bjrtccia751 10.0.7.3bjrtccia752 10.0.7.4ap1000-1 10.0.7.5ap1000-2 10.0.7.6nms-manager 10.0.3.44


Queue 10 bjrtccia751 10.0.7.3bjrtccia752 10.0.7.4

否以黄色显示在事件监控台上

CRC 40 bjrtccia751 10.0.7.3bjrtccia752 10.0.7.4

否以黄色显示在事件监控台上

硬盘空间 90% 支持 SNMP 硬盘空间 MIB 的主机是以黄色显示在事件

监控台上

21


加载新厂家的MIB 库的步骤：

1. 检查是否需要加载新的相应厂家的MIB

Cisco Systembjrtccia751 10.0.7.3bjrtccia752 10.0.7.4bjswccsa651 10.0.7.7bjswccsa652 10.0.7.8

Solaris

Linux 注意: /etc/snmp/snmpd.conf 的配置FreeBSDMicrosoft Windows NT

nms-manager 10.0.3.44

2. 从相应网站下载 MIB

3. Load MIB 到网管站4. 通过 MIB Browser 查找相应的 MIB Object

22


在 Data Collection & Thresholds / MIB Object Selection 窗口中选择 MIB

Object，增加以下MIB 项：

1. Cpu 利用率Cisco

.1.3.6.1.4.1.9.2.1.56

.iso.org.dod.internet.private.enterprises.cisco.local.lsystem.busyPer

23


CPU busy percentage in the last 5 second period. Not the last 5 realtime seconds but the

last 5 second period in the scheduler.

Windows

.1.3.6.1.2.1.25.3.3.1.2

.iso.org.dod.internet.mgmt.mib-2.host.hrDevice.hrProcessorTable.

hrProcessorEntry.hrProcessorLoad

The average, over the last minute, of the percentage of time that this processor was not

idle.

2. 端口流量.1.3.6.1.2.1.2.2.1.10.

.iso.org.dod.internet.mgmt.mib-2.interfaces.ifTable.ifEntry. ifInOctets

.1.3.6.1.2.1.2.2.1.16.

.iso.org.dod.internet.mgmt.mib-2.interfaces.ifTable.ifEntry. ifOutOctets

选择 Instance，如“1,2,13”

3. 端口利用率If%util \

"Percent of available bandwidth utilized on an interface\n\

Computed by:\n\

(Received byte rate + transmitted byte rate) * 8\n\

------------------------------------------------\n\

interface link speed\n\

then converted to a percentage."\

选择 Instance，如“1,2,13”

24


4. 端口误码率 CRC

.1.3.6.1.4.1.9.2.2.1.1.12

.iso.org.dod.internet.private.enterprises.cisco.local.linterfaces.lifTable.lifEntry.locIfInCRC

Number of input packets which had cyclic redundancy checksum errors.

5. 设备等待队列 < 40

.1.3.6.1.4.1.9.9.37.1.2.1.2

.iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoQueueMIB.ciscoQueueObje

cts.cQStatsTable.cQStatsEntry.cQStatsDepth

The number of messages in the sub-queue.

port 1/2/3/4

cQStatsMaxDepth = 40

修改$OV_CONF/mibExpr.conf 文件，创建数据收集表达式：

###########################################################

CiscoMem%Util \"Cisco device busy percentage\n\( ciscoMemoryPoolUsed / ciscoMemoryPoolUsed + ciscoMemoryPoolFree ) * 100 "\.1.3.6.1.4.1.9.9.48.1.1.1.5. \.1.3.6.1.4.1.9.9.48.1.1.1.6. \.1.3.6.1.4.1.9.9.48.1.1.1.5. \+ \/ \100 \*

CiscoBuff%Util \"Cisco device busy percentage\n\( ( bufferElMax - bufferElFree ) / bufferElMax ) * 100 "\.1.3.6.1.4.1.9.2.1.10. \

25


.1.3.6.1.4.1.9.2.1.9. \- \.1.3.6.1.4.1.9.2.1.10. \/ \100 \*

DiskCD%Util \"Disk C:(2) D:(3) Utility percentage\n\( hrStorageUsed / hrStorageSize ) * 100 "\.1.3.6.1.2.1.25.2.3.1.6. \.1.3.6.1.2.1.25.2.3.1.5. \/ \100 \*

$OV_CONF/mibExpr.conf 文件内容见附录。

5.NNM 种子文件的配置1. Create a text seed file with a text editor of your choice (e.g. notepad). Locationdoesn’t matter. In this example, we’ll call the file \tmp\seed. The syntax of the line isvery simple: single-line entries of IP addresses or nodenames. Put lines into the filefor any machines that most likely will have visited the most machines on the externalsubnet. If nodes on the other side of the firewall exchange little information, you willneed to make additional seedfile entries. An example seedfile is:1.2.6.11.2.3.211.2.7.12. Stop netmon by issuing an ovstop netmon command.3. Change to the $OV_LRF directory (by default, \OpenView\lrf on Windows NT,/etc/opt/OV/share/lrf on HPUX 10.x) and edit netmon.lrf. You need to addparameters to the last line. The entry for netmon should look something like this:netmon:netmon:

OVs_YES_START:ovtopmd,pmd,ovwdb:-P:OVs_WELL_BEHAVED:15:

Modify the parameter section to add the seed file created above:netmon:netmon:

OVs_YES_START:ovtopmd,pmd,ovwdb:-P –s \tmp\seed:OVs_WELL_BEHAVED:15:

4. Execute ovaddobj netmon.lrf to register the changes just made.

26


5. Restart netmon with ovstart netmon.

Cat netmon.lrf## @(#)netmon.lrf# @(#)HP OpenView NNM Release B.06.10 Oct 28 1999# @(#)Copyright (c) 1990-1999 Hewlett-Packard Company# $Revision: /main/PULSAR/PULSAR_REP/1 $ $Date: 1999/02/02 20:27 UTC $## Local Registration File for Network Node Manager network monitor daemon## Arguments can be placed between the second and third colons# of the second line. See lrf(4) and netmon(1m)## Run ovaddobj(1m), ovstop(1m) and ovstart(1m) after modifying this file:# ovaddobj $OV_LRF/netmon.lrf# ovstop netmon# ovstart netmon#netmon:netmon:OVs_YES_START:ovtopmd,pmd,ovwdb:-P -s /tmp/cnc/seed -k segRedux=true:OVs_WELL_BEHAVED:15:PAUSE

Cat /tmp/cnc/seed10.0.7.3210.52.212.124

6.NNM 被管节点图标的增加与修改1. Locate the following file:

$OV_CONF/oid_to_sym2. Make a backup copy of the oid_to_sym file, if you have not already done so.3. Edit the oid_to_sym file to modify the line referring to HP 9000 Series 700 workstations. Your changes map this device to the new HP700 subclass instead of the existing HP-UX workstation subclass.

Add line:1.3.6.1.4.1.2.3.1.2.1.1.3:Computer:AIX #IBM AIX Workstation1.3.6.1.4.1.2021.250.10:Computer:Mini # RedHat Linux

4. $OV_CONF/oid_to_type Add sysObjectId:1.3.6.1.4.1.2.3.1.2.1.1.3:IBM:IBM RS/6000

27


1.3.6.1.4.1.2021.250.10:RedHat Linux:UCDavis5. /etc/opt/OV/share/fields/C/snmp_fields

Field "SNMPAgent" {…"UCDavis",…}

6. /etc/opt/OV/share/fields/C/ovw_fieldsField "vendor" {

…"RedHat Linux",…}

1. Make sure that your PATH environment variable includes:$OV_BIN2. Log in as root3. Close all NNM sessions4. With all the NNM processes running, shut down just the netmon service. From the command prompt, type:ovstop -c -v netmon5. Update the database by using the ovtopofix command. The -o option to ovtopofix requires the SNMP sysObjectID, as returned by the agent of the object you are updating. This is the same sysObjectID you used in the oid_to_sym file. From the command prompt, type:ovtopofix -u -o ’1.3.6.1.4.1.11.2.3.2.5’ 2>&1|tee /tmp/ovtopofixOut

6. Restart the netmon service. From the command prompt, type:ovstart -v7. Check that all services are RUNNING. From the command prompt, type:ovstatus -c

7.NNM 分布式管理的配置一级管理中心设置为：1. 管理站2. 事件收集3. 对下一级收集站拓扑图的同步4. 设置 Discovery Filter 或边缘路由设备 SNMP 设置，限制自动发现范围5. 不设 map filter

二级管理中心设置为：28


1. 收集站2. 事件上传3. 设置 Discovery Filter 或边缘路由设备 SNMP 设置，限制自动发现范围4. 不设 map filter 及 topology filter

控制收集站（Collection Station）管理范围（控制节点发现）的方法包括：1. 边缘路由设备 SNMP 的设置（SNMP及其 Community Name），同时限制种子文件的设置

2. 发现过滤器（Discovery Filter）的设置1. Create a filter in the file $OV_CONF/$LANG/filters

…// CNC Beijing IDC Discovery FilterCNCBJIDC "IP Addresses 10.0.*.* 210.51.*.*"

{ ( "IP Address" ~ 10.0.*.* ) || ( "IP Address" ~ 210.51.*.* ) || ( "IP Address" ~ 210.52.212.124 ) || isSegment }

2. Select Options:Network Polling Configuration:IP from the menu bar. 3. Make sure the Discover New Nodes option button is on in the IP tabs, as needed. 4. Click the Use Discovery Filter option button to the on position. The corresponding text box will ungray.5. Enter the filter name as defined in the filters file into this text box.6. Click [OK] to save the changes and close the dialog box. The discovery filter will be applied to all newly discovered objects. Polling is still done on all previously discovered objects whether or not they would have passed the filter. To apply the filter to previously discovered objects you need to stop netmon by typing:ovstop netmonOnce netmon is stopped, execute the following command:ovtopofix -f filternameThen start netmon by typing:ovstart netmon

1. ovstop2. /usr/sbin/snmpd -k3. Edit the set community name line in the /etc/SnmpAgent.d/snmpd.conf file to read as follows:set-community-name: name #enter community name4. /usr/sbin/snmpd5. ovstart -v

1. Make sure the NNM background processes are running:ovstatus2. Determine what collection stations already exist by executing the following commandxnmtopoconf -print

29


This will give you a list of current collection stations and tell you if they are managed or unmanaged. If the collection station does not appear, continue to the next step. If the collection station does appear, continue with step 4.3. Add the collection station to the topology by executing the following command:xnmtopoconf -add -unmanage collectionstationThis same command is used for the floating host name of a Service Guard cluster on UNIX systems. As part of your Service Guard configuration process, you updated the ov.conf configuration file HOSTNAME= parameter. 4. Configure the set community name to be used when communicating with the collection station by selecting Options:SNMP Configuration from the menu bar. This displays the SNMP Configuration dialog box.5. In the SNMP Parameters pane of the dialog box, specify in the Set Community text field the same set community name that you configured on the collection station.6. Click [OK] to close the SNMP Configuration dialog box.7. To make sure the collection station is configured correctly, execute the following command xnmtopoconf -test collectionstation8. Manage the collection station by executing the following command:xnmtopoconf -manage collectionstationThis causes the management station to start monitoring and synchronizing with the remote collection station. As part of this, the management station will be added to the collection station’s internal list of interested managers. This internal list is referred to as %REMOTE_MANAGERS_LIST% in various places in the interface, such as the event configuration system, when forwarding is being configured.nmdemandpoll -s collectionstation

8.NNM 操作员用户的配置1. 修改 /opt/OV/bin/ovw 的权限：

# ll ovw-r-xr-xr-x 1 bin bin 2483999 Oct 10 05:39 ovw# chmod 554 ovw# ll ovw-r-xr-xr-- 1 bin bin 2483999 Oct 10 05:39 ovw

2. 增加操作员用户 operator，口令 operator；用户组为 bin

3. 修改 $HOME/.profile，增加：export $PATH=PATH:/opt/OV/bin

4. 修改 /.profile，增加：xhost +

30


5. 修改 /etc/dt/config/Xconfigdelete the # at the start of the line:

Dtlogin*authorize: False

Note: If the file is not in /etc, then copy /usr/dt/config/Xconfig to /etc/dt/config/Xconfig

6. /sbin/init.d/dtlogin.rc stop/sbin/init.d/dtlogin.rc start

9.分布式结构设计

一级管理中心设置为：管理站事件收集对下一级收集站拓扑图的同步设置 Discovery Filter 或边缘路由设备 SNMP 设置，限制自动发现范围不设 map filter

二级管理中心设置为：收集站事件上传设置 Discovery Filter 或边缘路由设备 SNMP 设置，限制自动发现范围不设 map filter 及 topology filter

控制收集站（Collection Station）管理范围（控制节点发现）的方法包括：边缘路由设备 SNMP 的设置（SNMP及其 Community Name），同时限制种子文件的设置

发现过滤器（Discovery Filter）的设置

9.1 配置过滤器Map Filter

A map filter allows the operator to display only the objects of interest to that operator. Objects that

31


are rejected by a map filter remain in the management station’s topology database and are still subject to status polling. 1. Create a filter in the file $OV_CONF/$LANG/filters2. Select Map:Properties from the menu bar. The Map Description dialog box appears.3. Select IP Map from the Configurable Applications list and click [Configure For This Map]. 4. You must have read/write rights to the current map. Enter the filter name that you created in the text box under Map Filter.5. Click [Verify] to make sure the filter name or expression you specified is a valid filter.6. Click [OK] to save the changes and close the dialog box.

Discovery Filter

A discovery filter reduces the number of devices a management station orcollection station is actively discovering and monitoring. A discovery filter can be configured on a management station or a collection station. 1. Create a filter in the file $OV_CONF/$LANG/filters2. Select Options:Network Polling Configuration:IP from the menu bar. 3. Make sure the Discover New Nodes option button is on in the IP tabs, as needed. 4. Click the Use Discovery Filter option button to the on position. The corresponding text box will ungray.5. Enter the filter name as defined in the filters file into this text box.6. Click [OK] to save the changes and close the dialog box. The discovery filter will be applied to all newly discovered objects. Polling is still done on all previously discovered objects whether or not they would have passed the filter. To apply the filter to previously discovered objects you need to stop netmon by typing:ovstop netmonOnce netmon is stopped, execute the following command:ovtopofix -f filternameThen start netmon by typing:ovstart netmon

Managing and Unmanaging Locally Monitored Objects

xnmtopoconf [-manageobj | -unmanageobj] station object

32


9.2 配置收集站Configuring Security for a Collection Station

1. ovstop2. /usr/sbin/snmpd -k3. Edit the set community name line in the /etc/SnmpAgent.d/snmpd.conf file to read as follows:set-community-name: name #enter community name4. /usr/sbin/snmpd5. ovstart -v

Topology Filter

A topology filter at a collection station defines the subset of topology data that management stations can access.1. Create a filter in the file $OV_CONF/$LANG/filters2. ovstop3. Edit the ovtopmd.lrf file to include the -f option followed by the desired filter name or filter expression name. For example,ovtopmd:ovtopmd:

OVs_YES_START:pmd,ovwdb:O -f Routers: OVs_WELL_BEHAVED:15:

where, Routers is a predefined filter contained in the standard filter definition file.4. Reconfigure ovtopmd by executing the following command:ovaddobj ovtopmd.lrf5. ovstart -v

9.3配置管理站Determining if a Node is a Collection Station

xnmtopoconf -print

33


9.4 Determining All Objects Monitored by a

Collection Stationovtopodump -rRISC stn2ovtopodump -RISC | grep stn2

Configuring for a Specific Collection Station

1. Make sure the NNM background processes are running:ovstatus2. Determine what collection stations already exist by executing the following commandxnmtopoconf -printThis will give you a list of current collection stations and tell you if they are managed or unmanaged. If the collection station does not appear, continue to the next step. If the collection station does appear, continue with step 4.3. Add the collection station to the topology by executing the following command:xnmtopoconf -add -unmanage collectionstationThis same command is used for the floating host name of a Service Guard cluster on UNIX systems. As part of your Service Guard configuration process, you updated the ov.conf configuration file HOSTNAME= parameter. 4. Configure the set community name to be used when communicating with the collection station by selecting Options:SNMP Configuration from the menu bar. This displays the SNMP Configuration dialog box.5. In the SNMP Parameters pane of the dialog box, specify in the Set Community text field the same set community name that you configured on the collection station.6. Click [OK] to close the SNMP Configuration dialog box.7. To make sure the collection station is configured correctly, execute the following command xnmtopoconf -test collectionstation8. Manage the collection station by executing the following command:xnmtopoconf -manage collectionstationThis causes the management station to start monitoring and synchronizing with the remote collection station. As part of this, the management station will be added to the collection station’s internal list of interested managers. This internal list is referred to as %REMOTE_MANAGERS_LIST% in various places in the interface, such as the event configuration system, when forwarding is being configured.

34


9.5 Performing a Full Topology Synchronizationnmdemandpoll -s collectionstation

9.6 配置事件上传1. Select Options:Event Configuration from the menu bar; the Event Configuration window appears. From the command line, you may run xnmtrap.2. Select an enterprise from the Enterprise Identification pane. 3. Select an event that you want to forward from the Event Identification pane.4. Select Edit:Modify Event from the menu bar in the Event Configuration window; the Event Configurator/Modify Event dialog box appears. 5. Click on the Forward Event check box to expand the dialog box to display the Forwarded Event Destinations pane.6. Complete the [Forwarding] tab by specifying the destinations to forward the events to.You can add destinations in the following ways:• Clicking [Remote Mgrs] to add all remote management stations to the Forwarded Event Destinations list. The remote management stations are specified in a list indicated by the special string %REMOTE_MANAGERS_LIST%. This list is created automatically as systems are defined to be collection stations.• Clicking [Add From Map] to add the destinations that are selected on the map.• Typing the destination in the Destination text box and clicking [Add]. The destination you specify can be a file containing a list of destinations, a hostname, or an Internet address.7. Click [OK] from the Modify Events dialog box.8. Click File:Save from the Event Configuration window to save the changes.

35


第四章 NNM 的备份与恢复

1. 单用户模式做系统全备份

1.1 进入单用户模式

1. 系统重启：shutdown -r -y 0

2. 在启动开始，当屏幕提示时按任意键中断自动启动过程 <Interupt>

3. 当出现提示菜单时，输入 BO，进入 ISL 模式

4. 当出现提示符号时，输入：hpux -is

进入单用户模式。

1.2 全备份

1. 进入单用户模式后，输入：mount -a

mount 所有硬盘

2. 进入系统管理工具 sam 进行系统全备份。

36


2. NNM 数据备份与恢复

2.1 NNM 数据备份

1. 执行命令：ovbackup.ovpl

可以将所有当前 NNM 的配置情况及所有数据备份到生成的备份目录 $OV_TMP/ovbackup 中

2. 使用 tar 命令将备份目录 $OV_TMP/ovbackup 中的文件拷贝到磁带机的磁带中：tar cvf /dev/rmt/0m $OV_TMP/ovbackup

2.2 NNM 数据恢复

1. 使用 tar 命令将磁带中的数据及文件恢复到备份目录 $OV_TMP/ovbackup 中tar xvf /dev/rmt/0m $OV_TMP/ovbackup

2. 执行命令：ovrestore.ovpl

37


可以将所有 NNM 的配置情况及所有数据从备份目录 $OV_TMP/ovbackup 中恢复到当前使用的 NNM。

38


附录一文件清单1. /etc/passwd

# cat /etc/passwdroot:CgcNnXFB/C57U:0:3::/:/sbin/shdaemon:*:1:5::/:/sbin/shbin:*:2:2::/usr/bin:/sbin/shsys:*:3:3::/:adm:*:4:4::/var/adm:/sbin/shuucp:*:5:3::/var/spool/uucppublic:/usr/lbin/uucp/uucicolp:*:9:7::/var/spool/lp:/sbin/shnuucp:*:11:11::/var/spool/uucppublic:/usr/lbin/uucp/uucicohpdb:*:27:1:ALLBASE:/:/sbin/shnobody:*:-2:-2::/:www:*:30:1::/:oracle:h9Umrzj0kJ2V6:101:101:,,,:/home/oracle:/usr/bin/shhong:I/7a2XSVYnK1w:102:4::/home/hong:/sbin/shnone:NtecfE83kRfRk:103:0::/home/none:/sbin/shoperator:fQpr1FFyIlsUg:104:2:,,,:/home/operator:/usr/bin/sh#

39


2. /etc/group

# cat /etc/passwdroot:CgcNnXFB/C57U:0:3::/:/sbin/shdaemon:*:1:5::/:/sbin/shbin:*:2:2::/usr/bin:/sbin/shsys:*:3:3::/:adm:*:4:4::/var/adm:/sbin/shuucp:*:5:3::/var/spool/uucppublic:/usr/lbin/uucp/uucicolp:*:9:7::/var/spool/lp:/sbin/shnuucp:*:11:11::/var/spool/uucppublic:/usr/lbin/uucp/uucicohpdb:*:27:1:ALLBASE:/:/sbin/shnobody:*:-2:-2::/:www:*:30:1::/:oracle:h9Umrzj0kJ2V6:101:101:,,,:/home/oracle:/usr/bin/shhong:I/7a2XSVYnK1w:102:4::/home/hong:/sbin/shnone:NtecfE83kRfRk:103:0::/home/none:/sbin/shoperator:fQpr1FFyIlsUg:104:2:,,,:/home/operator:/usr/bin/sh# cat /etc/grouproot::0:rootother::1:root,hpdbbin::2:root,binsys::3:root,uucpadm::4:root,admdaemon::5:root,daemonmail::6:rootlp::7:root,lptty::10:nuucp::11:nuucpusers::20:rootnogroup:*:-2:dba::101:#

40


3. /etc/hosts

# cat /etc/hosts# @(#)hosts $Revision: 1.9.214.1 $ $Date: 96/10/08 13:20:01 $## The form for each entry is:# <internet address> <official hostname> <aliases>## For example:# 192.1.2.34 hpfcrm loghost## See the hosts(4) manual page for more information.# Note: The entries cannot be preceded by a space.# The format described in this file is the correct format.# The original Berkeley manual page contains an error in# the format description.#

10.0.3.30 bjidcnms bjidcnms.cnc-idc.com127.0.0.1 localhost loopback10.0.7.3 bjrtccia751 10.0.7.4 bjrtccia752 10.0.7.1 bjfwcctp001 10.0.3.1 bjfwcctp001 10.0.7.2 bjfwcctp002 10.0.7.5 ap1000-1 10.0.7.6 ap1000-2 10.0.7.7 bjswccsa651 10.0.7.8 bjswccsa652 10.0.7.9 bjswccsa003 10.0.3.44 nms-manager 10.0.3.5 pns 10.0.3.6 sns 10.0.3.31 www www.cnc-idc.com210.51.0.18 idclinuxtest 210.51.8.10 ftp-download ftp2.download.com.cn 210.52.212.124 nms01 nms01.sh.cnc171.net #

41


4. /etc/nsswitch.conf

# cat /etc/nsswitch.conf## /etc/nsswitch.hp_defaults:## An example file that could be copied over to /etc/nsswitch.conf; it# uses NIS (YP) in conjunction with files.#

#passwd: compat#group: compathosts: files [NOTFOUND=continue] dns#networks: nis [NOTFOUND=return] files#protocols: nis [NOTFOUND=return] files#rpc: nis [NOTFOUND=return] files#publickey: nis [NOTFOUND=return] files#netgroup: nis [NOTFOUND=return] files#automount: files nis#aliases: files nis#services: nis [NOTFOUND=return] files#

42


5. /etc/rc.config.d/netconf

# cat /etc/rc.config.d/netconf# netconf: configuration values for core networking subsystems## @(#) $Revision: 1.6.119.6 $ $Date: 97/09/10 15:56:01 $## HOSTNAME: Name of your system for uname -S and hostname## OPERATING_SYSTEM: Name of operating system returned by uname -s# ---- DO NOT CHANGE THIS VALUE ----## LOOPBACK_ADDRESS: Loopback address# ---- DO NOT CHANGE THIS VALUE ----## IMPORTANT: for 9.x-to-10.0 transition, do not put blank lines between# the next set of statements

HOSTNAME="bjidcnms"OPERATING_SYSTEM=HP-UXLOOPBACK_ADDRESS=127.0.0.1

# Internet configuration parameters. See ifconfig(1m), autopush(1m)# # INTERFACE_NAME: Network interface name (see lanscan(1m))## IP_ADDRESS: Hostname (in /etc/hosts) or IP address in decimal-dot# notation (e.g., 192.1.2.3)## SUBNET_MASK: Subnetwork mask in decimal-dot notation, if different# from default## BROADCAST_ADDRESS: Broadcast address in decimal-dot notation, if # different from default## INTERFACE_STATE: Desired interface state at boot time.# either up or down, default is up.## DHCP_ENABLE Determines whether or not DHCP client functionality # will be enabled on the network interface (see # auto_parms(1M), dhcpclient(1M)). DHCP clients get # their IP address assignments from DHCP servers.# 1 enables DHCP client functionality; 0 disables it.

43


## For each additional network interfaces, add a set of variable assignments# like the ones below, changing the index to "[1]", "[2]" et cetera.## IMPORTANT: for 9.x-to-10.0 transition, do not put blank lines between# the next set of statements

INTERFACE_NAME[0]=lan0IP_ADDRESS[0]=10.0.3.30SUBNET_MASK[0]=255.255.255.192BROADCAST_ADDRESS[0]=""INTERFACE_STATE[0]=""DHCP_ENABLE[0]=0

# Internet routing configuration. See route(1m), routing(7)## ROUTE_DESTINATION: Destination hostname (in /etc/hosts) or host or network# IP address in decimal-dot notation, preceded by the word# "host" or "net"; or simply the word "default".## ROUTE_MASK: Subnetwork mask in decimal-dot notation, or C language# hexadecimal notation. This is an optional field.# A IP address, subnet mask pair uniquely identifies# a subnet to be reached. If a subnet mask is not given,# then the system will assign the longest subnet mask# of the configured network interfaces to this route.# If there is no matching subnet mask, then the system# will assign the default network mask as the route's# subnet mask. ## ROUTE_GATEWAY: Gateway hostname (in /etc/hosts) or IP address in# decimal-dot notation. If local interface, must use the# same form as used for IP_ADDRESS above (hostname or # decimal-dot notation). If loopback interface, i.e., # 127.0.0.1, the ROUTE_COUNT must be set to zero.## ROUTE_COUNT: An integer that indicates whether the gateway is a# remote interface (one) or the local interface (zero)# or loopback interface (e.g., 127.*).## ROUTE_ARGS: Route command arguments and options. This variable# may contain a combination of the following arguments:# "-f", "-n" and "-p pmtu".#

44


# For each additional route, add a set of variable assignments like the ones# below, changing the index to "[1]", "[2]" et cetera.## IMPORTANT: for 9.x-to-10.0 transition, do not put blank lines between# the next set of statements

# ROUTE_DESTINATION[0]=default# ROUTE_MASK[0]=""# ROUTE_GATEWAY[0]=""# ROUTE_COUNT[0]=""# ROUTE_ARGS[0]=""

# Dynamic routing daemon configuration. See gated(1m)## GATED: Set to 1 to start gated daemon.# GATED_ARGS: Arguments to the gated daemon.

GATED=0GATED_ARGS=""

## Router Discover Protocol daemon configuration. See rdpd(1m)## RDPD: Set to 1 to start rdpd daemon#

RDPD=0

## Reverse ARP daemon configuration. See rarpd(1m)## RARP: Set to 1 to start rarpd daemon#

RARP=0

ROUTE_GATEWAY[0]=10.0.3.1ROUTE_COUNT[0]=1ROUTE_DESTINATION[0]=defaultROUTE_MASK[0]=""ROUTE_ARGS[0]=""#

45


6. /.profile

# cat /.profile# @(#) $Revision: 74.2 $

# Default (example of) super-user's .profile file

# Do not put "." in PATH; it is a potential security breach.# Do not put "/usr/local/bin" in PATH; it is a potential security breach.# Example assumes /home/root exists. set +u

PATH=/usr/sbin:$PATH:/sbin:/home/root

# Be sure that VUE does not invoke tty commands

if [ ! "$VUE" ]; then

# Set up the terminal: if [ "$TERM" = "" ] then eval ` tset -s -Q -m ':?hp' ` else eval ` tset -s -Q ` fi stty erase "^H" kill "^U" intr "^C" eof "^D" stty hupcl ixon ixoff tabs

echo echo "Value of TERM has been set to \"$TERM\". " export TERM

EDITOR=vi export EDITOR

fi # if !VUE

# Set up shell environment:

set -u # error if undefined variable.

46


trap "echo 'logout root'" 0 # what to do on exit.

# Set up shell variables:

MAIL=/var/mail/root # don't export, so only login shell checks.

echo "WARNING: YOU ARE SUPERUSER !!\n"

. /opt/OV/bin/ov.envvars.sh export ORACLE_BASE=/opt/oracle export ORACLE_HOME=$ORACLE_BASE export ORACLE_SID=openview export ORACLE_TERM=hp export SHLIB_PATH=$ORACLE_HOME/lib export PATH=$PATH:$ORACLE_HOME/bin:/opt/OV/bin:/usr/local/microsoft/bin/

#

47


7. /home/oracle/.profile

$ cat .profile

# @(#) $Revision: 72.2 $

# Default user .profile file (/usr/bin/sh initialization).

# Set up the terminal: if [ "$TERM" = "" ] then eval ` tset -s -Q -m ':?hp' ` else eval ` tset -s -Q ` fi stty erase "^H" kill "^U" intr "^C" eof "^D" stty hupcl ixon ixoff tabs

# Set up the search paths: PATH=$PATH:.

# Set up the shell environment: set -u trap "echo 'logout'" 0

# Set up the shell variables: EDITOR=vi export EDITOR

export ORACLE_BASE=/opt/oracle export ORACLE_HOME=$ORACLE_BASE export ORACLE_SID=openview export ORACLE_TERM=hp export SHLIB_PATH=$ORACLE_HOME/lib export PATH=$PATH:$ORACLE_HOME/bin$

48


8. crontab -l

# crontab -l# -------------------------------------------------------------------------# Example cron entries for scheduling HP OpenView 6.0 Data Warehouse exports## These lines can be copied into the root user's crontab file to automate# exports to HP OpenView's Data Warehouse. (Use crontab -e to edit the# cron entries as user root.) It is recommended that the comment# lines be included to assist modification of these entries.# These are examples only. The HP OpenView Administrator should determine# the correct settings for your installation.## Note that cron is a standard feature of Unix. Windows NT uses a# different scheduling paradyme.# See the cron(1M) and crontab(1) man pages for more information about cron.# -------------------------------------------------------------------------

# Schedule a daily export of HP OpenView Topology information.# This program replaces existing Topology data in the Data Warehouse.# Schedule for 11:50pm every day.# You must use caution not to schedule this command near any backup# processes you are also performing on this machine.# See the ovdwtopo(1) man page for more information.50 23 * * * /opt/OV/bin/ovdwtopo -export

# Schedule the export of HP OpenView Event information.# This program adds new information the HP OpenView Event data store.# Only use the 'trim' option once a day.# Schedule for 15 minutes after the hours of 2,5,8,11,14,17 and 20 every day.# You must use caution not to schedule this command near any backup# processes you are also performing on this machine.# See the ovdwevent(1) man page for more information.15 1 * * * /opt/OV/bin/ovdwevent -export -trimdetail 9015 2,5,8,11,14,17,20,23 * * * /opt/OV/bin/ovdwevent -export

# Schedule the export of HP OpenView Trend information.# You must setup the capture of trend information using xnmcollect.# This program adds new information the HP OpenView Event data store.# Only use the 'trim' and 'sum' options once a day.# Schedule for 35 minutes after the hours of 2,5,8,11,14,17 and 20 every day.# You must use caution not to schedule this command near any backup# processes you are also performing on this machine.

49


# See the ovdwtrend(1) man page for more information.35 1 * * * /opt/OV/bin/ovdwtrend -export -sum -trim -trimpriorto 216035 2,5,8,11,14,17,20,23 * * * /opt/OV/bin/ovdwtrend -export

#

50


9. /etc/resolv.conf

# cat /etc/resolv.confdomain cnc-idc.comnameserver 10.0.3.5#

51


附录二网管工作站配置

1. bdf

# bdfFilesystem kbytes used avail %used Mounted on/dev/vg00/lvol3 143360 53755 84063 39% //dev/vg00/lvol1 83733 48919 26440 65% /stand/dev/vg00/lvol8 4096000 526095 3346935 14% /var/dev/vg00/lvol7 2048000 511064 1440902 26% /usr/dev/vg00/lvol4 409600 75674 313333 19% /tmp/dev/vg00/lvol6 4096000 3072713 959450 76% /opt/dev/vg01/nmsdata 16384000 944960 14956574 6% /nmsdata/dev/vg00/lvol5 20480 1127 18146 6% /home#

52


2. vgdisplay -v

--- Volume groups ---VG Name /dev/vg00VG Write Access read/write VG Status available Max LV 255 Cur LV 8 Open LV 8 Max PV 16 Cur PV 1 Act PV 1 Max PE per PV 4350 VGDA 2 PE Size (Mbytes) 4 Total PE 4340 Alloc PE 3045 Free PE 1295 Total PVG 0 Total Spare PVs 0 Total Spare PVs in use 0

--- Logical volumes --- LV Name /dev/vg00/lvol1 LV Status available/syncd LV Size (Mbytes) 84 Current LE 21 Allocated PE 21 Used PV 1

LV Name /dev/vg00/lvol2 LV Status available/syncd LV Size (Mbytes) 1536 Current LE 384 Allocated PE 384 Used PV 1


53







--- Physical volumes --- PV Name /dev/dsk/c3t6d0 PV Status available Total PE 4340 Free PE 1295 Autoswitch On

54


VG Name /dev/vg01VG Write Access read/write VG Status available Max LV 255 Cur LV 1 Open LV 1 Max PV 16 Cur PV 1 Act PV 1 Max PE per PV 8684 VGDA 2 PE Size (Mbytes) 4 Total PE 8681 Alloc PE 4000 Free PE 4681 Total PVG 0 Total Spare PVs 0 Total Spare PVs in use 0

--- Logical volumes --- LV Name /dev/vg01/nmsdata LV Status available/syncd LV Size (Mbytes) 16000 Current LE 4000 Allocated PE 4000 Used PV 1

--- Physical volumes --- PV Name /dev/dsk/c3t5d0 PV Status available Total PE 8681 Free PE 4681 Autoswitch On

55


3. ioscan -fn

Class I H/W Path Driver S/W State H/W Type Description=============================================================================bc 0 root CLAIMED BUS_NEXUS ioa 0 10 sba CLAIMED BUS_NEXUS System Bus Adapter (582)ba 0 10/0 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)lan 0 10/0/12/0 btlan3 CLAIMED INTERFACE PCI Ethernet (10110019) /dev/ether0audio 0 10/0/13/0 audio CLAIMED INTERFACE Built-in Audio /dev/audio /dev/audioEL_0 /dev/audioLL_0 /dev/audioBA /dev/audioEU /dev/audioLU /dev/audioBA_0 /dev/audioEU_0 /dev/audioLU_0 /dev/audioBL /dev/audioIA /dev/audioNA /dev/audioBL_0 /dev/audioIA_0 /dev/audioNA_0 /dev/audioBU /dev/audioIL /dev/audioNL /dev/audioBU_0 /dev/audioIL_0 /dev/audioNL_0 /dev/audioCtl /dev/audioIU /dev/audioNU /dev/audioCtl_0 /dev/audioIU_0 /dev/audioNU_0 /dev/audioEA /dev/audioLA /dev/audio_0 /dev/audioEA_0 /dev/audioLA_0 /dev/audioEL /dev/audioLL ext_bus 0 10/0/14/0 side CLAIMED INTERFACE IDEtarget 0 10/0/14/0.0 tgt CLAIMED DEVICE disk 0 10/0/14/0.0.0 sdisk CLAIMED DEVICE TEAC CD-532E-B /dev/dsk/c0t0d0 /dev/rdsk/c0t0d0target 1 10/0/14/0.7 tgt CLAIMED DEVICE ctl 0 10/0/14/0.7.0 sctl CLAIMED DEVICE Initiator /dev/rscsi/c0t7d0ba 1 10/0/14/1 superio CLAIMED BUS_NEXUS PCI Core I/O Adaptertty 0 10/0/14/1/1 asio0 CLAIMED INTERFACE Built-in RS-232C /dev/diag/mux0 /dev/mux0 /dev/tty0p0 tty 1 10/0/14/1/2 asio0 CLAIMED INTERFACE Built-in RS-232C /dev/diag/mux1 /dev/mux1 /dev/tty1p0 ext_bus 1 10/0/14/1/3 SCentIf CLAIMED INTERFACE Built-in Parallel Interface /dev/c1t0d0_lpusb 0 10/0/14/2 hcd CLAIMED INTERFACE Built-in USB Interfaceusbhub 0 10/0/14/2.1 hub CLAIMED DEVICE USB Root Hub /dev/hubusbhid 0 10/0/14/2.1.2 hid CLAIMED DEVICE USB HID Mouse(0) /dev/hid/firstkbd /dev/hid/kbd_007 /dev/hid/firstmouse /dev/hid/mouse_000

56


/dev/hid/kbd_000 /dev/hid/mouse_001 /dev/hid/kbd_001 /dev/hid/mouse_002 /dev/hid/kbd_002 /dev/hid/mouse_003 /dev/hid/kbd_003 /dev/hid/mouse_004 /dev/hid/kbd_004 /dev/hid/mouse_005 /dev/hid/kbd_005 /dev/hid/mouse_006 /dev/hid/kbd_006 /dev/hid/mouse_007 usbhid 1 10/0/14/2.1.3 hid CLAIMED DEVICE USB HID Kbd(1)ext_bus 2 10/0/15/0 c720 CLAIMED INTERFACE SCSI C896 Ultra Wide Single-Endedtarget 2 10/0/15/0.7 tgt CLAIMED DEVICE ctl 1 10/0/15/0.7.0 sctl CLAIMED DEVICE Initiator /dev/rscsi/c2t7d0ext_bus 3 10/0/15/1 c720 CLAIMED INTERFACE SCSI C896 Ultra2 Wide LVDtarget 3 10/0/15/1.5 tgt CLAIMED DEVICE disk 1 10/0/15/1.5.0 sdisk CLAIMED DEVICE SEAGATE ST336704LC /dev/dsk/c3t5d0 /dev/rdsk/c3t5d0target 4 10/0/15/1.6 tgt CLAIMED DEVICE disk 2 10/0/15/1.6.0 sdisk CLAIMED DEVICE QUANTUM ATLAS10K-18LVD /dev/dsk/c3t6d0 /dev/rdsk/c3t6d0target 5 10/0/15/1.7 tgt CLAIMED DEVICE ctl 2 10/0/15/1.7.0 sctl CLAIMED DEVICE Initiator /dev/rscsi/c3t7d0ba 2 10/1 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)ba 3 10/4 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)ba 4 10/6 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)graphics 0 10/6/2/0 graph3 CLAIMED INTERFACE PCI Display (103c1008)processor 0 32 processor CLAIMED PROCESSOR Processormemory 0 49 memory CLAIMED MEMORY Memory

57


4. swlist

# Initializing...# Contacting target "bjidcnms"...## Target: bjidcnms:/#

## Bundle(s):#

B6268AA B.11.00.03 Graphics and Technical Computing Software ECSCmgNNMHP11 A.03.00 ECS Config/Mgmt GUI for NNM (including Japanese support) ECSRunNNMHP11 A.03.00 ECS Runtime for NNM HPUXEng64RT B.11.00.01 English HP-UX 64-bit Runtime Environment HPUXSCh64RT B.11.00.01 Simplified Chinese HP-UX 64-bit Runtime Environment NNMEngHP11Doc B.06.10.00 Network Node Manager Online Runtime Manuals - English version NNMEngHP11Dyna A.03.01.01 Network Node Manager Manuals DynaText Browser - English version NNMEngHP11full B.06.10.00 Network Node Manager NNMEngHP11man B.06.10.00 Network Node Manager Man Pages NNMIspHP11full B.01.00.00 HP OpenView Customer Views for NNM NNMIspHP11man B.01.00.00 OpenView Customer Views for NNM Man Pages OVPtlEngHP11full B.01.00.00 HP OpenView Service Information Portal SNMPAgntHP11man B.11.01.00 Emanate SNMP simple Agent Man Pages SNMPAgntHPUX11x B.11.01.00 Emanate SNMP Agent UXCoreMedia-S B.11.00.01 HP-UX Simplified Chinese Media Kit (Reference Only. See Description) XSWGR1100 B.11.00.49.3 HP-UX General Release Patches, June 2000 ## Product(s) not contained in a Bundle:#

PHCO_13331 1.0 tztab(4) patch PHCO_13467 1.0 cumulative savecrash(1M) patch. PHCO_13542 1.0 tar(1) exit code for nonfatal errors. PHCO_13753 1.0 HP-UX Patch Tools and White Paper PHCO_13966 1.0 cpio(1) - Fix -p to report number of blocks. PHCO_13983 1.0 df(1M) cumulative patch PHCO_14194 1.0 quota(1) patch for NFS-quotas

58


PHCO_14244 1.0 vxdump patch PHCO_14625 1.0 bdf(1M) patch to skip autofs file systems. PHCO_15231 1.0 cumulative libpam patch. PHCO_16149 1.0 csh(1) cumulative patch PHCO_16244 1.0 vxrestore(1M) patch PHCO_16341 B.11.00.10 HP AutoRAID Manager cumulative patch PHCO_16405 1.0 cumulative fbackup(1M)/frecover(1M) patch PHCO_16720 1.0 st(1) New shared tape administration command PHCO_16795 1.0 memory windows cumulative patch PHCO_16847 1.0 XCurses cumulative patch. PHCO_16885 1.0 pax(1) restoring hard and soft links PHCO_17440 1.0 useradd(1M) cumulative patch. PHCO_17441 1.0 DLKM configuration tools cumulative patch PHCO_17553 1.0 Year 2000 cumulative cron/at/crontab patch PHCO_17556 1.0 fsck_vxfs(1M) cumulative patch PHCO_17792 1.0 cumulative SAM/ObAM patch PHCO_18074 1.0 lpspool subsystem cumulative patch PHCO_18102 1.0 cumulative 10.20 libc compatibility support PHCO_18183 1.0 Software Distributor (SD-UX) Cumulative Patch PHCO_18227 1.0 libc cumulative patch PHCO_18316 1.0 mount(1M) cumulative patch. PHCO_18447 1.0 sh-posix(1) cumulative patch PHCO_19091 1.0 cumulative fsck_hfs(1M) patch PHCO_19479 1.0 LVM commands cumulative patch PHCO_19486 B.11.00.05 HP Array Manager/60 cumulative patch PHKL_14119 1.0 32bit binary compatibility on 64bit systems PHKL_14750 1.0 Fix pthread_cond_timedwait(3T) error return PHKL_15687 1.0 mk_kernel:Eliminate debug related warnings PHKL_15689 1.0 AutoFS support patch PHKL_16983 1.0 Return correct value for open() PHKL_17333 1.0 scsi3 cumulative patch PHKL_17368 1.0 SCSI Pass thru driver cumulative patch PHKL_17935 1.0 libpthreads cumulative patch PHKL_19080 1.0 New tape support. Defect fix for 9840 tape. PHKL_19169 1.0 Correct VxFS process hangs PHKL_19204 1.0 vxfs mount,fsck cumulative patch PHKL_19311 1.0 Fixes a coherency corner case for mmap & I/O PHKL_19416 1.0 Fibre Channel Mass Storage Driver Patch PHKL_19800 1.0 fix unmount and MMF VxFS hangs PHKL_20123 1.0 PCI-PCI Bridge Fixes & V-class BA hints fix PHKL_20151 1.0 SBA wrkstn support & N/L class debug support PHKL_20153 1.0 Enable SuperIO parallel interface PHKL_20154 1.0 IDE/ATAPI hardware support patch PHKL_20155 1.0 Enable SuperIO floppy drive interface

59


PHKL_20156 1.0 Cumulative USB Driver patch PHKL_20157 1.0 SCSI cumulative patch PHKL_20158 1.0 Audio drvr data crrption fix +audio3 support PHKL_20159 1.0 VISUALIZE-fxe, legacy graphics, ITE patch PHKL_20164 1.0 LBA workstation support & PIOP for N/L class PHKL_20167 1.0 Directed range support & PIOP for N/L class PHKL_20171 1.0 Selective dump size warnings PHKL_20172 1.0 Remove spurious dump device warning PHKL_20176 1.0 FC connection, chassis codes, I2O RAIDs PHKL_20222 1.0 Fix boot,JFS; IO perf;PA8600; lg. data(1of8) PHKL_20223 1.0 mmap panic fix + large data space (2 of 8) PHKL_20226 1.0 Large Data Space (5 of 8) PHKL_20333 1.0 LVM Cumulative patch PHNE_14618 1.0 Bind 4.9.7 components PHNE_16091 1.0 r-commands cumulative mega-patch PHNE_17101 1.0 ONC cumulative patch PHNE_17586 1.0 NFS Kernel General Release/Performance Patch PHNE_18354 1.0 ftpd(1M) and ftp(1) patch PHNE_18527 1.0 telnetd(1M) patch PHNE_18668 1.0 PCI 100BT cumulative patch PHNE_18878 1.0 Fix for Streams Pty MP race condition PHNE_18972 1.0 Cumulative STREAMS Patch PHNE_19754 1.0 LAN product cumulative patch PHNE_19899 1.0 cumulative ARPA Transport patch PHNE_20150 1.0 Cumulative Mux and Pty Patch PHSS_15396 1.0 Asian Printer cumulative patch PHSS_16839 1.0 Assembler patch. PHSS_16849 1.0 LIBCL patch PHSS_17421 1.0 XClients JAN 99 Cumulative Patch PHSS_17980 1.0 ImagingSubsystem April 1999 Periodic Patch PHSS_20140 1.0 CDE Runtime OCT99 Cumulative Patch PHSS_20141 1.0 Xserver cumulative patch PHSS_20142 1.0 X/Motif2.1 Runtime OCT99 Cumulative Patch PHSS_20145 1.0 CDE Msg Cat OCT99 Cumulative Patch PHSS_20146 1.0 Firmware update for B1000, C3000 and J5000 PHSS_20147 1.0 Asian Input Method cumulative patch PHSS_20148 1.0 ASX release notes cumulative patch PHSS_21488 1.0 OV CVIEWS1.0 ovcustomer buffer overflow PHSS_22144 1.0 OV CVIEWS1.0 keySys and submBld problems. PHSS_22424 1.0 OV NNM6.1 Consolidated Patch 10/08/2000 PHSS_22936 1.0 AudioSubsystem Dec 2000 Periodic Patch

60


5. uname -a

# uname -aHP-UX bjidcnms B.11.00 A 9000/785 2012219903 two-user license#

61


6. swapinfo

# swapinfo Kb Kb Kb PCT START/ KbTYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAMEdev 1572864 0 1572864 0% 0 - 1 /dev/vg00/lvol2reserve - 382144 -382144memory 1577420 275620 1301800 17%#

62


7. lanscan

# lanscanHardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPIPath Address In# State NamePPA ID Type Support Mjr#10/0/12/0 0x001083FF57AB 0 UP lan0 snap0 1 ETHER Yes 119#

63


8. dmesg

Feb 16 11:05gate64: sysvec_vaddr = 0xc0002000 for 1 pages

NOTICE: autofs_link(): File system was registered at index 3.

NOTICE: nfs3_link(): File system was registered at index 5.

10 sba

10/0 lba

10/0/12/0 btlan3

10/0/13/0 audio

10/0/14/0 side

10/0/14/0.0 tgt

10/0/14/0.0.0 sdisk

10/0/14/0.7 tgt

10/0/14/0.7.0 sctl

10/0/14/1 superio

10/0/14/1/1 asio0

10/0/14/1/2 asio0

10/0/14/1/3 SCentIf

10/0/14/2 hcd

10/0/14/2.1 hub

10/0/14/2.1.2 hid

10/0/14/2.1.3 hid

64


10/0/15/0 c720

10/0/15/0.7 tgt

10/0/15/0.7.0 sctl

10/0/15/1 c720

10/0/15/1.5 tgt

10/0/15/1.5.0 sdisk

10/0/15/1.6 tgt

10/0/15/1.6.0 sdisk

10/0/15/1.7 tgt

10/0/15/1.7.0 sctl

10/1 lba

10/4 lba

10/6 lba

Variable size pages used to map 1000 graf pages at fffffffffb000000

10/6/2/0 graph3

32 processor

49 memory

btlan init: WARNING - Unable to setup Read/Write Prefetch lengths

btlan3: Initializing 10/100BASE-TX card at 10/0/12/0....

System Console is on the ITE

Logical volume 64, 0x3 configured as ROOT

65


Logical volume 64, 0x2 configured as SWAP

Logical volume 64, 0x2 configured as DUMP

Swap device table: (start & size given in 512-byte blocks)

entry 0 - major is 64, minor is 0x2; start = 0, size = 3145728

Dump device table: (start & size given in 1-Kbyte blocks)

entry 0 - major is 31, minor is 0x36000; start = 88928, size = 1572864

Starting the STREAMS daemons-phase 1

Create STCP device files

B2352B/9245XB HP-UX (B.11.00) #1: Wed Nov 5 22:38:19 PST 1997

Memory Information:

physical page size = 4096 bytes, logical page size = 4096 bytes

Physical: 2097152 Kbytes, lockable: 1573080 Kbytes, available: 1813972 Kbytes

66

hp openviewread.pudn.com/downloads12/doc/50545/hp11_nnm完全实施... · web viewhp openview...

Documents