CosNamingFT - a fault-tolerant CORBA naming service
- 格式:pdf
- 大小:142.99 KB
- 文档页数:9
存储HCIP考试模拟题含答案一、单选题(共38题,每题1分,共38分)1.生产中心有 2080GB 的数据,需要备份到灾备中心。
备份窗为 6 小时,不进行重删,带宽利用率为 0.8。
则至少需要多大的带宽才能满足此备份要求。
A、49.28MB/sB、61.6MB/sC、98.56MB/sD、123.2MB/s正确答案:D2.存储设备产生了故障告警,以下方法中,哪一项不能收集存储系统故障信息()A、检查 Zone 配置B、检查所有事件C、导出系统数据D、检查告警信息正确答案:A3.以下哪项不是 oceanstor cloud service 具备的功能?A、自动检查存储健康状态B、时刻发现设备告警C、自动解决故障D、故障信息即时传输到云端服务器正确答案:C4.在 oceanstor v3 存储中,edevlun 哪个信息是有华为存储直接提供的存储空间A、meta volumeB、external lunC、data volumeD、taget lun正确答案:A5.华为容灾方案中,关于同步远程复制顺序的描述正确的是:1 主存储阵列写 I/O 数据到主 LUN,并发送 IO 到从 LUN2 主机发送 IO 到主存储阵列。
3 主存储阵列向主机返回写成功的信息。
4 写 IO 数据到主从LUN 中。
A、2->1->4->3B、1->4->3->2C、3->2->1->4D、1->2->3->4正确答案:A6.配置主备容灾时,主端和备端阵列上的 LUN 需满足以下哪个条件?A、备端 LUN 大小需大于等于主端 LUN。
B、备端需配置相同的 RAID 级别,并且备端 LUN 需和主端 LUN 大小一致。
C、只需备端 LUN 和主端 LUN 大小一致。
D、备端需配置相同类型的硬盘,备端 LUN 大小需大于等于主端 LUN。
正确答案:C7.华为 Oceanstor 9000 InfoTier 文件池策略将决定文件创建的存储位置,以及文件重条带化时的目标分级,以下关于文件池策略说法不正确的是哪一项?A、策略参数组合间为“或”的关系B、default 策略优先级最低C、default 策略可以被修改D、最多可支持配置 128 条文件池策略正确答案:A8.以下关于 oceanstor 9000 InfoLocker 特性说法不正确的是哪一项?A、WORM 文件能进行修改和删除B、WORM 时钟只允许设置一次,设置成功后不再允许更改C、当一个目录配置为 WORM 根目录时,该目录的所有子目录、新增目录和新建文件自动获取父目录的WORM 属性D、WORM 保护的提交方式只支持自动提交正确答案:A9.下面对重复数据删除技术原理描述不正确的是哪项?A、相同的数据块物理上只存储一次。
存储HCIP试题库(含参考答案)一、单选题(共38题,每题1分,共38分)1.以下关于备份组网LAN-free和Server-free的说法正确的是哪一项?A、Server-free在数据备份时要产生一个副本,该副本会被mount 到备份服务器。
B、Server-free组网可实现直接将备份数据备份到备份介质。
C、LAN-free备份组网对生产主机没有影响。
D、LAN-free备份数据流的路径是生产存储->备份服务器->备份介质。
正确答案:A2.下列选项中不属于全局缓存带来的优势的是:A、提升系统整体性能B、提升缓存数据访问命中率C、提升缓存空间利用率D、提升系统安全可靠性正确答案:D3.华为存储oceanstor的cli管理模式下查看控制器状态的命令是:A、showsysB、showcotrolinfoC、showsystemgeneralD、showcotrollergeneral正确答案:D4.以下关于Oceanstor9000维护说法不正确的是哪一项?A、系统默认提供admin(超级管理员)账户,该管理员账户不允许被B、只有超级管理员用户才能执行createsystemuser命令创建用户C、查看所有账户的信息可用命令cat/etc/passwd。
D、ps-ef命令检查TCP服务/端口正确答案:D5.OceanStorV318800产品不支持以下哪种线缆?A、minisas线缆B、sas线缆C、AOC线缆D、fc线缆正确答案:B6.华为OceanstorV3SmartCache特性适用于以下哪个场景?A、写随机小io场景B、读随机小io场景C、写顺序io场景D、读书须io场景正确答案:B7.大数据时代对传统技术升级已经满足不了了大数据处理的需求,以下哪一项不是大数据时代技术发展的方向?A、向虚拟化方向发展B、网络向更高苏,协议开销更低,更有效的方向发展C、由非关系型数据库想关系型数据库发展D、计算向集群化发展正确答案:C8.华为Oceanstor9000通过什么文件系统,对外提供统一的业务访问A、NTFSB、HDFSC、WushanFSD、EXT3正确答案:C9.在Oceanstor9000中,对WushanFS全局缓存技术理解错误的是哪一项A、WushanFS中的GlobalCache将所有存储服务器上的内存空间在逻辑上组成一个整体内存资源池B、某一节点缓存中的数据不能被其他节点的读写业务命中C、全局缓存技术有助于提升节点内存资源共享D、WushanFS利用分布式锁实现全局缓存数据管理,同一业务数据只在某个节点缓存一份,当其他节点需要访问该数据时,通过申请锁,获取该缓存数据正确答案:B10.在oceanstorv3存储中,NFS不支持如下哪一种验证方式?A、NISB、LADPC、本地认证D、AD域正确答案:D11.关于华为Oceanstor9000软件模块的描述不正确的事哪一项?A、OBS(Object-BasedStore)为文件系统元数据和文件数据提供可靠性的对象存储功能B、CA(ChentAgent)负责NFS/CIFS/FTP等应用协议的语义解析,并发送给底层模块处理C、快照、分级存储、远程复制等多种增值特性功能是由PVS模块提供的D、MDS(MetaDataService)管理文件系统的元数据,系统的每一个节点存储可所以元数据正确答案:D12.在华为Oceanstor9000(C30)中以下哪个特征不需要激活相应License?A、自动分级存储B、配额管理C、目录快照D、轮循负载均衡正确答案:D13.以下OceanStor9000的软件特性中,能够提供文件系统快照的特性是哪个特性?A、InfoEqualizerB、InfoStamperC、InfoProtectorD、InfoLocker正确答案:B14.一个同事在制定双活容灾方案,通过测试仲裁服务器到两端存储系统带宽为4Mbit/s,时延RTT≤是40ms,丢包率≤1%,那么这个方案:A、不可行,因为双活容灾时延RTT≤120msB、不可行,因为双活容灾丢包率必须≤0.1%。
Sun M5000Solaris 10系统的安装、打补丁及IPMP的配置目录一、安装准备 (3)节 1.01 1 M5000的初始设置 (4)节 1.02 2 添加用户及给机器加电 (4)二、安装系统 (15)三、打补丁 (49)四、做镜像 (86)五、配置IPMP (92)一、安装准备首先使用串口线将笔记本与M5000连接,端口的设置请看(图1-1):图1-1操作系统安装以及IP地址配置如下:系统的分区如下:节 1.01 1 M5000的初始设置新出厂的机器,XSCF没有设置用户,需要使用串口进行初始用户的创建。
机器加插上电源后,XSCF启动完成后出现登陆提示符:根据提示,输入用户名default后,将前面板钥匙由锁定位置拧到维护位置,按回车,等待5秒后,将钥匙由维护位置拧到锁定位置,敲回车,这样系统就进入XSCF提示符了。
(钥匙顺序也可以相反,即开始本来在维护位置,那么就拧到锁定,再由锁定到维护)节 1.02 2 添加用户及给机器加电Change the panel mode switch to Service and press return...Leave it in that position for at least 5 seconds. Change the panel mode switch to Locked, and press return...XSCF>adduser eis-installerXSCF> setprivileges eis-installer platadm useradm auditadm/*添加用户并设置权限*//*添加用户eis-installer并设置权限,主要是platadm useradm*/XSCF> showuser –l /*查看状态*/User Name: eis-installerUID: 100Status: EnabledMinimum: 0Maximum: 99999Warning: 7Inactive: -1Last Change: Dec 24, 2009Password Expires: NeverPassword Inactive: NeverAccount Expires: NeverPrivileges: useradmplatadmauditadmXSCF> password eis-installer/*修改密码,此M5000密码为admin123*/ New XSCF password:BAD PASSWORD: it is too shortRetype new XSCF password:Sorry, passwords do not matchNew XSCF password:BAD PASSWORD: it is based on a dictionary wordRetype new XSCF password:XSCF>XSCF>XSCF>XSCF>XSCF> exitlogoutlogin: eis-installerPassword:XSCF>XSCF>XSCF>XSCF>XSCF>showhardconf /*加电后的M5000用此条命令确认内部配置*/SPARC Enterprise M5000;+ Serial:BEF0949C90; Operator_Panel_Switch:Locked;+ Power_Supply_System:Single; SCF-ID:XSCF#0;+ System_Power:Off; System_Phase:Cabinet Power Off;Domain#0 Domain_Status:Powered Off;MBU_B Status:Normal; Ver:0201h; Serial:BE0948104A ;+ FRU-Part-Number:CF00541-0478 08 /541-0478-08 ;+ Memory_Size:32 GB;CPUM#0-CHIP#0 Status:Normal; Ver:0401h; Serial:PP094605MN ;+ FRU-Part-Number:CA06761-D202 E1 /375-3568-05 ;+ Freq:2.400 GHz; Type:32;+ Core:4; Strand:2;CPUM#0-CHIP#1 Status:Normal; Ver:0401h; Serial:PP094605MN ;+ FRU-Part-Number:CA06761-D202 E1 /375-3568-05 ;+ Freq:2.400 GHz; Type:32;+ Core:4; Strand:2;CPUM#1-CHIP#0 Status:Normal; Ver:0401h; Serial:PP0946056Q ;+ FRU-Part-Number:CA06761-D202 E1 /375-3568-05 ;+ Freq:2.400 GHz; Type:32;+ Core:4; Strand:2;CPUM#1-CHIP#1 Status:Normal; Ver:0401h; Serial:PP0946056Q ;+ FRU-Part-Number:CA06761-D202 E1 /375-3568-05 ;+ Freq:2.400 GHz; Type:32;+ Core:4; Strand:2;MEMB#0 Status:Normal; Ver:0101h; Serial:BF0944FVV3 ;+ FRU-Part-Number:CF00541-0545 08 /541-0545-08 ;MEM#0A Status:Normal;+ Code:ce0000000000000001M3 93T5660QZA-CE6 4151-522563a9;+ Type:2A; Size:2 GB;MEM#0B Status:Normal;+ Code:ce0000000000000001M3 93T5660QZA-CE6 4151-5225644f;+ Type:2A; Size:2 GB;MEM#1A Status:Normal;+ Code:ce0000000000000001M3 93T5660QZA-CE6 4151-522563aa;+ Type:2A; Size:2 GB;MEM#1B Status:Normal;+ Code:ce0000000000000001M3 93T5660QZA-CE6 4151-52256376;+ Type:2A; Size:2 GB;MEM#2A Status:Normal;+ Code:ce0000000000000001M3 93T5660QZA-CE6 4151-522563fd;+ Type:2A; Size:2 GB;MEM#2B Status:Normal;+ Code:ce0000000000000001M3 93T5660QZA-CE6 4151-52256377;+ Type:2A; Size:2 GB;MEM#3A Status:Normal;+ Code:ce0000000000000001M3 93T5660QZA-CE6 4151-5225640a;+ Type:2A; Size:2 GB;MEM#3B Status:Normal;+ Code:ce0000000000000001M3 93T5660QZA-CE6 4151-522563b7;+ Type:2A; Size:2 GB;MEMB#1 Status:Normal; Ver:0101h; Serial:BF0944FVVD ;+ FRU-Part-Number:CF00541-0545 08 /541-0545-08 ;MEM#0A Status:Normal;+ Code:ce0000000000000001M3 93T5660QZA-CE6 4151-522551be;+ Type:2A; Size:2 GB;MEM#0B Status:Normal;+ Code:ce0000000000000001M3 93T5660QZA-CE6 4151-522551bf;+ Type:2A; Size:2 GB;MEM#1A Status:Normal;+ Code:ce0000000000000001M3 93T5660QZA-CE6 4151-52256405;+ Type:2A; Size:2 GB;MEM#1B Status:Normal;+ Code:ce0000000000000001M3 93T5660QZA-CE6 4151-52256400;+ Type:2A; Size:2 GB;MEM#2A Status:Normal;+ Code:ce0000000000000001M3 93T5660QZA-CE6 4151-522551ba;+ Type:2A; Size:2 GB;MEM#2B Status:Normal;+ Code:ce0000000000000001M3 93T5660QZA-CE6 4151-522551bb;+ Type:2A; Size:2 GB;MEM#3A Status:Normal;+ Code:ce0000000000000001M3 93T5660QZA-CE6 4151-522551b0;+ Type:2A; Size:2 GB;MEM#3B Status:Normal;+ Code:ce0000000000000001M3 93T5660QZA-CE6 4151-522551b9;+ Type:2A; Size:2 GB;DDC_A#0 Status:Normal;DDC_A#1 Status:Normal;DDC_A#2 Status:Normal;DDC_A#3 Status:Normal;DDC_B#0 Status:Normal;DDC_B#1 Status:Normal;IOU#0 Status:Normal; Ver:0101h; Serial:BF0941ENU2 ;+ FRU-Part-Number:CF00541-2240 05 /541-2240-05 ;DDC_A#0 Status:Normal;DDCR Status:Normal;DDC_B#0 Status:Normal;XSCFU Status:Normal,Active; Ver:0101h; Serial:BF0941EM56 ;+ FRU-Part-Number:CF00541-0481 04 /541-0481-04 ;OPNL Status:Normal; Ver:0101h; Serial:BF0941EDBC ;+ FRU-Part-Number:CF00541-0850 06 /541-0850-06 ;PSU#0 Status:Normal; Serial:0017527-0940025271;+ FRU-Part-Number:CF00300-2011 0250 /300-2011-02-50;+ Power_Status:Off; AC:200 V;PSU#1 Status:Normal; Serial:0017527-0940025268;+ FRU-Part-Number:CF00300-2011 0250 /300-2011-02-50;+ Power_Status:Off; AC:200 V;PSU#2 Status:Normal; Serial:0017527-0940025267;+ FRU-Part-Number:CF00300-2011 0250 /300-2011-02-50;+ Power_Status:Off; AC:200 V;PSU#3 Status:Normal; Serial:0017527-0940025266;+ FRU-Part-Number:CF00300-2011 0250 /300-2011-02-50;+ Power_Status:Off; AC:200 V;FANBP_C Status:Normal; Ver:0501h; Serial:BF0940EA5H ;+ FRU-Part-Number:CF00541-3099 01 /541-3099-01 ;FAN_A#0 Status:Normal;FAN_A#1 Status:Normal;FAN_A#2 Status:Normal;FAN_A#3 Status:Normal;XSCF>settimezone -c settz -s Asia/Shanghai/*设置时区及时间,完成后重启XSCF*/ Asia/ShanghaiXSCF> showdateThu Dec 24 16:56:06 CST 2009XSCF>XSCF> setdscp/*设置管理网口IP地址DSCP network [0.0.0.0 ] > 192.168.0.0DSCP netmask [255.255.255.0 ] >XSCF address [192.168.0.1 ] > 192.168.0.3Domain #00 address [192.168.0.2 ] > 192.168.0.4Domain #01 address [192.168.0.3 ] > 192.168.0.5Domain #02 address [192.168.0.4 ] > 192.168.0.6Domain #03 address [192.168.0.5 ] > 192.168.0.7Commit these changes to the database? [y|n] : yXSCF>showdscpDSCP Configuration:Network: 192.168.0.0Netmask: 255.255.255.0Location Address---------- ---------XSCF 192.168.0.3Domain #00 192.168.0.4Domain #01 192.168.0.5Domain #02 192.168.0.6Domain #03 192.168.0.7XSCF> rebootxscfThe XSCF will be reset. Continue? [y|n] :yexecute K000endXSCF> -- completeexecute S10ioxoff -- completeDec 24 08:56:51 localhost XSCF[104]: XSCF shutdown sequence start execute K000end -- completeexecute K100end -- completeexecute K101end -- completeunmount /hcp0/linuxunmount /hcp0/scfprogunmount /hcp0/gendata -- completeunmount /hcp0/remcscm -- completeunmount /hcp1/linuxunmount /hcp1/scfprogunmount /hcp1/gendataunmount /hcp1/remcscmunmount /hcpcommon/setup -- completeunmount /hcpcommon/obp -- completeunmount /hcpcommon/tmp -- completeunmount /hcpcommon/varunmount /hcpcommon/scflog1 -- completeunmount /hcpcommon/scflog2 -- completeXSCF reset.Please stand by while rebooting the system.(15)Restarting system.XSCF uboot 01080001 (May 8 2009 - 15:09:36)XSCF uboot 01080001 (May 8 2009 - 15:09:36)SCF board boot factor = 4040DDR Real size: 256 MBDDR: 224 MB## Booting image at ff800000 ...Image Name: XSCF kernel 01090000 2.6.11.12-sImage Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 1456903 Bytes = 1.4 MBLoad Address: 00000000Entry Point: 00000000Verifying Checksum ... OKUncompressing Kernel Image ... OK## Loading RAMDisk Image at ff980000 ...Image Name: XSCF rootfs 01090000 ,2009/07/30Image Type: PowerPC Linux RAMDisk Image (gzip compressed)Data Size: 5457580 Bytes = 5.2 MBLoad Address: 00000000Entry Point: 00000000Verifying Checksum ... OKLoading Ramdisk to 0bacb000, end 0bfff6ac ... OKLinux version 2.6.11.12-sec (gcc version 3.4.4) #1 Thu Jul 30 14:14:57 JST 2009new message buffer at 0f700000 size 1048576log_buf_len: 1048576mpc85xx_cds_setup_archBuilt 1 zonelistsKernel command line: root=/dev/ram rw console=ttyS0,9600 init=/sbin/init_change_root panic=1 mem=240MOpenPIC Version 1.2 (1 CPUs and 44 IRQ sources) at fbe79000PID hash table entries: 1024 (order: 10, 16384 bytes)Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)Memory: 218752k available (2188k kernel code, 668k data, 316k init, 0k highmem)Mount-cache hash table entries: 512 (order: 0, 4096 bytes)Freeing initrd memory: 5329k freedRAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksizei2c-algo-cpm: CPM2 I2C algorithm module version 0.1 (Mar 22, 2005)FCC ENET Version 0.3TCP established hash table entries: 8192 (order: 4, 65536 bytes)TCP bind hash table entries: 8192 (order: 3, 32768 bytes)ip_tables: (C) 2000-2002 Netfilter core teamarp_tables: (C) 2002 David S. MillerVFS: Mounted root (ext2 filesystem).Freeing unused kernel memory: 316k initswitching initrd filesystem, ramdisk to tmpfsSCF Linux Boot Script 2006/03/04 for ROM boot environmentfsl-sec2 hardware crypt accelerator model3a ver 0.02 enabledXSCF initial process start (pid=104)load /scf/modules/lites_ldrv.ko -- completeload /scf/modules/drvscftrace.ko -- completeload /scf/modules/sec2_rsa.ko -- completeload /scf/modules/sec2_md5.ko -- completeload /scf/modules/sec2_des.ko -- completeload /scf/modules/sec2_arc4.ko -- completeload /scf/modules/sec2_aes.ko -- completeload /scf/modules/sec2_sha256.ko -- completeload /scf/modules/sec2_sha1.ko -- completeload /scf/modules/hw_random.ko -- completeload /scf/modules/scsi_mod.ko -- completeload /scf/modules/sd_mod.ko -- completeload /scf/modules/usbcore.ko -- completeload /scf/modules/ohci-hcd.ko -- completeload /scf/modules/usb-storage.ko -- completeload /scf/modules/drvbootfmem.ko -- completeload /scf/modules/drvmbc.ko -- completeload /scf/modules/drvnand.ko -- completeload /scf/modules/drvffc.ko -- completeload /scf/modules/drvffcint.ko -- completeload /scf/modules/drvrtc.ko -- completeload /scf/modules/drvxscfuart.ko -- completeload /scf/modules/drvrci.ko -- completeload /scf/modules/drvtimer.ko -- completeload /scf/modules/drvsdic.ko -- completeload /scf/modules/sm2s.ko -- completeload /scf/modules/spkmdrv.ko -- completemount /dev/mtdblock0 -> /hcp0/linux -- completemount /dev/mtdblock1 -> /hcp0/scfprog -- completemount /dev/mtdblock2 -> /hcp0/gendata -- completemount /dev/mtdblock3 -> /hcp0/remcscm -- completemount /dev/mtdblock4 -> /hcpcommon/setup -- complete mount /dev/mtdblock5 -> /hcpcommon/obp -- completemount /dev/mtdblock6 -> /hcpcommon/tmp -- completemount /dev/mtdblock11 -> /hcpcommon/var -- completemount /dev/mtdblock12 -> /hcpcommon/scflog1 -- complete mount /dev/mtdblock13 -> /hcpcommon/scflog2 -- complete execute S00mtab -- completeexecute S00portmap -- completeexecute S00tmpmake -- completeexecute S00varclean -- completeexecute S10ldconfig -- completeexecute S15last_dmesg -- completeexecute S20cfgcreate -- completeexecute S50iptables -- completeexecute S60check -- completeexecute S61restore -- completeexecute S99syslogd -- completeinitialize XSCF common database (STANDALONE) -- complete start /scf/sbin/dbs (pid=302)start /scf/sbin/ksyseventd (pid=303)start /scf/init/scf_cmgrd (pid=323)start /scf/init/scf_coremgr (pid=324)start /scf/init/dualprocess (pid=325)check SCF operation mode (for OPNL access) -- complete initialize OPNL -- completecheck SCF operation mode -- complete (ACTIVE)start /scf/sbin/dbs (pid=337)initialize XSCF common database (OWN) -- complete synchronize setup data (XSCF -> OPNL) -- complete initialize XSCF common database (ACTIVE) -- complete wait for database synchronization -- completeexecute S00clis_all -- completeexecute S10restore_um -- completeexecute S11network.sh -- completeexecute S15ntpcheck.sh -- completeexecute S21daemons -- completeexecute S51scflog_SCFboot.sh -- completeexecute S82cod -- completeexecute S98bui -- completeexecute S00clis_active -- completeexecute S00cmem_check -- completeexecute S00tmp_login -- completeexecute S18restorefmdlog -- completeexecute S19setfmurl -- completeexecute S29setfmconf -- completeexecute S50setupSCFboot.sh -- completeexecute S83setservicetagdata -- completestart /scf/sbin/scf_panelmgr (pid=640)start /scf/sbin/auditd (pid=641)start /scf/sbin/cmd (pid=642)start /scf/sbin/cmd_sub (pid=643)start /scf/sbin/errhandd (pid=644)start /scf/sbin/fjdrd (pid=645)start /scf/sbin/frura (pid=646)start /scf/sbin/mond (pid=647)start /scf/sbin/mond (pid=648)start /scf/sbin/powerd (pid=649)start /scf/sbin/rci (pid=650)start /scf/sbin/rci_dual (pid=651)start /scf/sbin/reset (pid=652)start /scf/sbin/resetra (pid=653)start /scf/sbin/rsyncprocess (pid=654)start /scf/sbin/scf_firmup_exed (pid=655)start /scf/sbin/scf_loganalyze (pid=657)start /scf/sbin/scf_procmeas (pid=658)start /scf/sbin/sequence (pid=659)start /scf/sbin/ttyd (pid=660)start /scf/sbin/apcsd (pid=661)start /scf/sbin/codd (pid=662)start /scf/sbin/scf_firmup_ctld (pid=663)start /scf/sbin/fmd (pid=664)start /scf/sbin/dscpd (pid=722)start /scf/sbin/monitor_msg (pid=723)start /scf/sbin/picld (pid=724)start /scf/sbin/sunmcrund (pid=725)start /scf/sbin/stdiscoverer (pid=726)start /scf/sbin/stlistener (pid=727)start /scf/sbin/dfrud (pid=728)start /scf/sbin/iomgrd (pid=729)start /scf/sbin/archd (pid=772)wait for SCF_READY -- completeexecute S20setupSCFready.sh -- completeexecute S99rcclear -- completeexecute S10iobox_scan -- completeexecute S10restore_um -- completeexecute S84snmpd -- completeexecute S85sunmc_esd -- completeexecute S86limits -- completeexecute S87opnl -- completeexecute S99dr_recover.sh -- completeXSCF Initialize complete.Dec 24 17:01:03 localhost XSCF[104]: XSCF Initialize complete.login: eis-installerPassword:XSCF>XSCF> poweron -d 0DomainIDs to power on:00Continue? [y|n] :y00 :Powering on*Note*This command only issues the instruction to power-on.The result of the instruction can be checked by the "showlogs power".XSCF>console -d 0Connect to DomainID 0?[y|n] :yPOST Sequence 01 CPU CheckPOST Sequence 02 BannerLSB#00 (XSB#00-0): POST 2.11.0 (2009/06/18 09:29)POST Sequence 03 Fatal CheckPOST Sequence 04 CPU RegisterPOST Sequence 05 STICKPOST Sequence 06 MMUPOST Sequence 07 Memory InitializePOST Sequence 08 MemoryPOST Sequence 09 Raw UE In CachePOST Sequence 0A Floating Point UnitPOST Sequence 0B SCPOST Sequence 0C Cacheable InstructionPOST Sequence 0D SoftintPOST Sequence 0E CPU Cross CallPOST Sequence 0F CMU-CHPOST Sequence 10 PCI-CHPOST Sequence 11 Master DevicePOST Sequence 12 DSCPPOST Sequence 13 SC Check Before STICK DiagPOST Sequence 14 STICK StopPOST Sequence 15 STICK StartPOST Sequence 16 Error CPU CheckPOST Sequence 17 System ConfigurationPOST Sequence 18 System Status CheckPOST Sequence 19 System Status Check After SyncPOST Sequence 1A OpenBoot Start...POST Sequence Complete.Sun SPARC Enterprise M5000 Server, using Domain consoleCopyright 2009 Sun Microsystems, Inc. All rights reserved.Copyright 2009 Sun Microsystems, Inc. and Fujitsu Limited. All rights reserved. OpenBoot 4.24.11, 32768 MB memory installed, Serial #88430282.Ethernet address 0:21:28:45:56:ca, Host ID: 854556ca.Dec 24 17:04:44 localhost dscpd[722]: Failed to start DSCP for domain0 (error=2) Boot device: disk File and args:SunOS Release 5.10 Version Generic_141414-10 64-bitCopyright 1983-2009 Sun Microsystems, Inc. All rights reserved.Use is subject to license terms.二、安装系统在OK模式下从光盘启动{12} ok{12} ok boot cdrom /*进入OK模式下,通过cdrom启动*/ Resetting...POST Sequence 01 CPU CheckPOST Sequence 02 BannerLSB#00 (XSB#00-0): POST 2.11.0 (2009/06/18 09:29)POST Sequence 03 Fatal CheckPOST Sequence 04 CPU RegisterPOST Sequence 05 STICKPOST Sequence 06 MMUPOST Sequence 07 Memory InitializePOST Sequence 08 MemoryPOST Sequence 09 Raw UE In CachePOST Sequence 0A Floating Point UnitPOST Sequence 0B SCPOST Sequence 0C Cacheable InstructionPOST Sequence 0D SoftintPOST Sequence 0E CPU Cross CallPOST Sequence 0F CMU-CHPOST Sequence 10 PCI-CHPOST Sequence 11 Master DevicePOST Sequence 12 DSCPPOST Sequence 13 SC Check Before STICK DiagPOST Sequence 14 STICK StopPOST Sequence 15 STICK StartPOST Sequence 16 Error CPU CheckPOST Sequence 17 System ConfigurationPOST Sequence 18 System Status CheckPOST Sequence 19 System Status Check After SyncPOST Sequence 1A OpenBoot Start...POST Sequence Complete.Sun SPARC Enterprise M5000 Server, using Domain consoleCopyright 2009 Sun Microsystems, Inc. All rights reserved.Copyright 2009 Sun Microsystems, Inc. and Fujitsu Limited. All rights reserved. OpenBoot 4.24.11, 32768 MB memory installed, Serial #88430282.Ethernet address 0:21:28:45:56:ca, Host ID: 854556ca.Dec 25 08:42:34 localhost dscpd[724]: Failed to start DSCP for domain0 (error=2) Rebooting with command: boot cdromBoot device: /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/disk@3,0:f File and args: SunOS Release 5.10 Version Generic_139555-08 64-bitCopyright 1983-2009 Sun Microsystems, Inc. All rights reserved.Use is subject to license terms.Configuring devices.Using RPC Bootparams for network configuration information.Attempting to configure interface e1000g1...Skipped interface e1000g1Attempting to configure interface e1000g0...Skipped interface e1000g0Attempting to configure interface bge1...Skipped interface bge1Attempting to configure interface bge0...Skipped interface bge0Reading ZFS config: done.Setting up Java. Please wait...Serial console, reverting to text installBeginning system identification...Searching for configuration file(s)...Search complete.Discovering additional network configuration...Select a Language /*选择语言*/0. English1. French2. German3. Italian4. Japanese5. Korean6. Simplified Chinese7. Spanish8. Swedish9. Traditional ChinesePlease make a choice (0 - 9), or press h or ? for help: 0 /*选择0,英文*/Select a Locale /*选择本地语言*/0. English (C - 7-bit ASCII)1. Albania (ISO8859-2)2. Australia (ISO8859-1)3. Belgium-Flemish (ISO8859-1)4. Belgium-Flemish (ISO8859-15 - Euro)5. Bosnia (ISO8859-2)6. Brazil (ISO8859-1)7. Brazil (UTF-8)8. Bulgaria (ISO8859-5)9. Canada-English (ISO8859-1)10. Catalan, Spain (ISO8859-1)11. Catalan, Spain (ISO8859-15 - Euro)12. Croatia (ISO8859-2)13. Czech Republic (ISO8859-2)14. Czech Republic (UTF-8 + euro)15. Czech Republic (UTF-8)16. Denmark (ISO8859-1)17. Denmark (ISO8859-15 - Euro)18. Egypt (ISO8859-6)Press Return to show more choices.Please make a choice (0 - 63), or press h or ? for help: 0 /*选择0英文*/What type of terminal are you using? /*使用的终端类型*/1) ANSI Standard CRT2) DEC VT523) DEC VT1004) Heathkit 195) Lear Siegler ADM316) PC Console7) Sun Command Tool8) Sun Workstation9) Televideo 91010) Televideo 92511) Wyse Model 5012) X Terminal Emulator (xterms)13) CDE Terminal Emulator (dtterm)14) OtherType the number of your choice and press Return: 3 /*选择3,DEC VT100*/Completing system identification...in.rdisc: No interfaces upq The Solaris Installation Program qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqThe Solaris installation program is divided into a series of short sectionswhere you'll be prompted to provide information for the installation. Atthe end of each section, you'll be able to change the selections you'vemade before continuing.About navigation...- The mouse cannot be used- If your keyboard does not have function keys, or they do notrespond, press ESC; the legend at the bottom of the screen qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq q/*以上提示告诉安装人员,Solaris的安装分好几个部分,每一部分后面都要你进行确认,如果发现有错,可以更改你先前输入的信息。
第一章课后练习1. 选择题(1)在5G移动通信系统网络架构中, 无线接入网的设备是( C )。
A. BTSB. BSCC. gNodeBD. eNodeB(2)从物理层次划分时, 5G承载网被分为( ABD )。
A. 前传网B. 中传网C. 后传网D. 回传网(3)为了满足低时延业务需要, 核心网的部分网络需要下沉到( D )中。
A. 核心DCB. 中心DCC. 区域DCD. 边缘DC(4)全球3G标准包含(ABCD )。
A. WCDMAB. CDMA2000C. TD-SCDMAD. WiMAX(5)4G使用的多址接入技术是(D)。
A. FDMAB. CDMAC. TDMAD. OFDMA2. 简答题(1)请写出ITU定义的5G的八大能力目标。
(2)请描述5G的三大应用场景。
5G的应用场景分为三大类: 增强移动带宽(enhanced Mobile Broadband, eMBB)、超高可靠低时延通信(Ultra Reliable and Low Latency Communication, URLLC)、海量物联网通信(massive Machine Type of Communication, mMTC), 不同应用场景有着不同的关键能力要求。
其中, 峰值速率、时延、连接数密度是关键能力。
eMBB场景下主要关注峰值速率和用户体验速率等, 其中, 5G的峰值速率相对于LTE的100Mbit/s提升了100倍, 达到了10Gbit/s;URLLC场景下主要关注时延和移动性, 其中, 5G的空口时延相对于LTE的50ms降低到了1ms;mMTC场景下主要关注连接数密度, 5G的每平方千米连接数相对于LTE 的104个提升到了106个。
第二章(1)以下可用于5G无线接入网部署的组网方式为( D )。
A. DRANB. CRANC. Cloud RAND. 以上都可以(2)以下不属于DRAN架构优势的是( D )。
存储HCIP习题库及参考答案一、单选题(共40题,每题1分,共40分)1、对源 lun 做了一次快照后,在同一位置进行修改后,修改后的数据会写在哪个位置?A、独享映射表B、快照卷C、原卷D、cow 卷正确答案:C2、下列哪个接口模块是 SX6018 上用于升级防火墙软件以及其他高级调试的:A、I2C 接口B、管理网口C、USB 接口D、CONSOLE 口正确答案:A3、关于存储层数据复制容灾技术,以下哪种说法是正确的?A、减少对服务器性能的影响:兼容性要求比较高,选择面小。
B、技术成熟,选择面大,连接距离限制小,稳定性高。
C、投入较少,兼容性好。
影响服务器性能。
D、服务器上安装专用的数据复制软件。
正确答案:B4、NAS 系统专注对于以下哪种类型的数据进行存储和管理?A、小块消息B、连续数据块C、大块数据D、文件数据正确答案:D5、帐户是使用对象存储服务(兼容 Amazon S3 接口)的凭证,其管理功能不包括:A、证书管理B、跨域访问策略管理C、签约业务管理D、帐户基本管理正确答案:B6、先把数据块存储在缓存中,等系统空闲时再进行去重处理。
优点是不影响数据传输性能,缺点是需要额外的存储空间“。
以上描述的是哪种重删技术,A、全局重删B、并行重删C、源端重删D、目标端重删正确答案:D7、HyperSnap 的共享映射表存放在哪个位置?A、COW DataB、Source LUNC、Cow MetaD、Snapshot LUN正确答案:C8、在存储规划设计流程中,以下哪一项不属于业务规划流程()A、网络规划B、容量规划C、基础业务D、增值功能正确答案:C9、在 oceanstor v3 存储中,edevlun 哪个信息是有华为存储直接提供的存储空间A、external lunB、meta volumeC、taget lunD、data volume正确答案:B10、关于华为 Oceanstor 9000 系统的组网,以下哪个选项描述是正确的?A、前端业务网络的交换机可进行堆叠,后端存储网络交换机不推荐进行堆叠B、无论是前端业务网络、还是后端存储网络,都推荐使用两台交换机连接所有的节点,实现冗余C、仅需要将存储节点连接到管理网络,其他设备不需要连接到管理网络D、为满足管理需求,仅需要集群的前三个节点连接到管理网络正确答案:B11、下列关于 FusionStorago 管理网络描述错误的是:A、只部署 FusionStorage 文件或对象存储服务,集群中前 3~5 个节点作为管理节点,并为其分配 1 个管理网络 IP 地址,自动在这几个节点的NIC1 接口上浮动B、部署了 DSS/OMS /FSM 的节点,两个接口组成逻辑上的 bond 接口,为bond 接口分配 1 个管理网络 IP 地址。
K-SIT/5VAS 505x -在线故障代码设备手册支持2008年8月20日 19:06 主编:A.Ptassek ,2008 年 5 月 12 日© 大众汽车公司版权所有 文件版本: 1.0.3.0 审阅:W.Weindok ,2008 年 5 月 19 日参照版本: 1.0.0.0第1页/共53页发布:D.v.d.Vorst ,2008 年 6 月 20 日版本 1.0.4.0 版本 发布版日期 2008年7月23日文件VAS505x-Online-Fehlercodes_1.0.4.0_sup.xls设备手册支持2008年8月20日 19:06 主编:S.Dörpmund,2008年7月23日目录:BTI VAS:反馈信息CBS CPNBB:登录服务CER CPNBB:维修说明CPB CPNBB:一般故障CPR CPNBB:协议服务CSU CPNBB:大众汽车软件版本管理服务CSV CPNBB:软件版本管理服务DC RCODE-服务器FAZ FAZIT-服务器MQS MQ-通信NES VAS:设置主机名PIN CPNBB:PIN服务PRO 协议服务器RSI VAS:RSIS-远程诊断SUS SUSI-服务器VAD VAS:在线测试VAK VAS:在线通信VAU VAS:在线升级其他其他故障报告设备手册支持2008年8月20日 19:06 主编:S.Dörpmund,2008年7月23日历史记录:日期 版本 说明 修改自2004年2月26日 1.0.0.0 扩展了手册支持中的故障代码BOB2004年3月1日 1.0.0.1 形式化BOB2004年3月31日 1.0.0.2 补充了 VAD0032W至VAD0046E BOB2004年4月28日 1.0.0.3 补充了 CPB1032E CKK2004年5月12日 1.0.0.4 补充了 VAK0200W至VAK0203W BOB2004年6月3日 1.0.0.5 补充了有关 HTTP-Error的 VAD0046E BOB2004年10月13日 1.0.0.6 扩展了 VAK0001E,补充了VAK0007E BOB2004年11月24日 1.0.0.7 补充了 CPB0100E,更新了CPBxxxxX GFH2005年1月27日 1.0.0.8 补充了 VAK0002E(ElsaWin) BOB2005年2月9日 1.0.0.9 补充了 VAK0007E(ElsaWin) BOB2005年9月2日 1.0.1.0 定义第3级;补充其他故障;BOB取消了HC – 新增DISS2;补充:BTI0006E 和CBS*2006年3月6日 1.0.2.0 重新定义第 3 级(PSC:“AMS-SPK VAS 505x A”BOBSUS 故障列表的补充2006年5月30日 1.0.2.1 VAD0046E [一般] 更新了链接WFE2006年9月7日 1.0.2.2 扩展了 VAD0046E 的网络故障代码BOB2008年5月13日 1.0.3.0 补充了维修说明服务(CER) APKCBS:新增故障代码 CBS0009E根据模板调整格式2008年7月23日 1.0.4.0 CBR:新增列表DOEMQS:扩展了列表,使故障代码更精确ERP:新增列表修正了联系人和小组名称清除了 SUSI 故障报告设备手册支持2008年8月20日 19:06 主编:S.Dörpmund,2008年7月23日BTI(VAS:反馈信息)在成功完成在线测试后反馈信息的过程中生成故障代码(管理 -->网络设置 -->在线连接自测试)。
正确答案:B11. IMS域内的核心功能实体使用()协议作为其呼叫和会话的控制信令。
VA MGCPB * SIPCD SIGTRAN正确答案:B12.()是IMS网络架构中控制层的核心。
VA * CSCFB HSSC BGCFD MGCF正确答案:A13.()是IMS用户使用的,归属网络分配的全球唯一标识,用于管理、注册、鉴权。
VA 豆IMPUB ' IMPIC IMSID PSI正确答案:B14. MGCF的主要功能是? ( )V《软交换技术与NGN》练习题一、填空题1.广义的下一代网络涉及的内容十分广泛,实际上包含下一代传送网、、下一代交换网、和。
2.狭义的下一代网络特指以为控制核心,能够实现语音、数据和业务的开放的分层体系架构。
3.下一代网络在功能上可分为、核心媒体层、和业务/应用层四层。
4.下一代网络能够实现与呼叫控制分离、与接入和承载分离。
5.下一代网络的运送层主要完成和信令流的传送,一般为网络或ATM网络。
6.软交换网络以网作为承载网络,呼叫控制集中在设备上。
7.对本地网络进行智能化改造,就是在固定电话本地网建立、和,通过三个中心快速实现网络低成本快速化、移动化和综合化。
8.本地网智能化改造的核心思想是建立本地网集中的,对本地网所有的用户数据进行集中管理,并在每次呼叫接续前增加用户业务属性查询机制。
9.基于R4的移动核心网CS域中MSC被分为和,实现了CS域中呼叫与承载的分离,并支持信令的承载。
10.接口是R4核心网中MSCServer与媒体网关MGW之间的接口,接口上采用协议,该协议增加了针对3GPP特殊需求的及定义。
11.Nc接口是R4核心网中之间的呼叫控制信令接口,该接口采用协议,该协议提供在宽带转输网上等同于的信令功能。
12.Nb接口是R4核心网中之间的接口,用来在R4核心网内承载用户的话音媒体流,有与承载两种方式。
13.IP协议采用的地址是。
14.IP地址包括网络地址和两部分,现在采用的IPv4地址包含位二进制数。
CosNamingFT -
A Fault-Tolerant CORBA Naming Service
Lau Cheuk Lung, Joni da Silva Fraga e Jean-Marie FarinesLaboratório de Controle e MicroinformáticaUniv. Federal de Santa Catarina; Florianópolis - Brazillau, fraga, farines@lcmi.ufsc.br
Michael Ogg, Aleta RicciardiInformation Science Research CenterBell Laboratories; Murray Hill, NJ - USAogg, aleta@research.bell-labs.com
AbstractThis paper describes the design and implementation ofa fault-tolerant CORBA naming service - CosNamingFT.Every CORBA object is accessed through itsInteroperable Object Reference (IOR), which is registeredwith the CORBA name service. The name servicetherefore is a critical gateway to all objects in adistributed system; to avoid having a single point offailure, the name service should be made fault-tolerant.CosNamingFT uses the GroupPac package [6], aCORBA-compliant suite of protocols, to replicate thename server. GroupPac services are built from CommonObject Services that function as building blocks toimplement fault-tolerant applications. This paper aims todemonstrate the usefulness of some of these objectservices and to demonstrate the importance of opensolutions issues in replicating distributed objects.Keywords: naming service, fault-tolerant, CORBA,open systems.
1. IntroductionA name service plays an important role in anydistributed system. Roughly speaking, its primary role isto facilitate access to the system’s resources; it is acommonly known “meeting room” for objects, services,and resources. As defined by the CORBA (CommonObject Request Broker Architecture) specifications, the
name service is a critical gateway for all objects in aCORBA-based distributed system. All CORBA objectsare registered with the name service, allowing them to befound and used by any other object in the system. Thus,each object that participates in a CORBA-basedcomputation accesses the name service at least one: either
to register itself via its IOR (Interoperable ObjectReference), or to locate other CORBA objects’ IORs. One
of the OMG’s (Object Management Group) CommonObject Services (COSes) is a name service standard,called CosNaming [9, 10]. The CosNaming specificationtakes into account the portability, interoperability andreusability aspects that are important concepts in opensystems. However, these specifications do not includerequirements of fault tolerance that are very important fordistributed systems.One possible way to implement a fault-tolerant nameservice would to use the COS persistence service [10], aunique interface for persistent storage services for objects’states. We decided not to follow a persistence-basedstrategy due to concerns over recovery time forapplications requiring more stringent availability; torecover from a crash, a new name service must be startedand its state loaded from file.Here, we describe CosNamingFT, a name servicewhich adheres to the OMG’s CosNaming and usesprimary-backup replication [2] to achieve fault tolerance.
Primary-backup replication can provide continuousservice availability (the degree of fault tolerance dependson the model of computation assumed), but cannotguarantee once-and-only-once semantics. Primary-backupreplication has a shorter fail-over time than strategiesbased on persistence, and lower overhead than activereplication strategies. We used the GroupPac package [6],a set of common object services for implementing variousgroup-based communication models, for the primary-backup infrastructure. In addition, these service objectscan be combined in different ways allowing theimplementation of different fault tolerance schemes. Thispaper demonstrates the usefulness of these services aswell as the possibility of obtaining open solutions forreplicating distributed objects.
Proceeding of the 18th International Symposium on Reliable Distributed Systems - SRDS'99, IEEEComputer Society. Lausanne, Suiça - Outubro de 1999.At present, there is no sanctioned COS specificationfor fault-tolerant CORBA objects through replication andgroup-based processing, though this is expected within theyear [11]. Electra [7] was an integration-based approachto build replicated CORBA objects, building the ORB ontop of a group-communication subsystem, although anycommunication substrate could have been used (forexample, an adaptor for TCP was as sensible as theoriginal adaptor for Isis [1] and a later for Ensemble(originally called Horus) [14]). While Electra used Isis’sactive replication model, this was an early implementationchoice; Isis’s coordinator-cohort (passive replication)model could equally well have been used.Eternal [8] is an interception-based approach, alsomaking use of an existing group-communicationsubsystem, but in this case intercepting IIOP messagesand mapping them to calls of the group-communicationsystem. The advantage of this approach is that nomodifications to the ORB are required; neither the ORBnor the objects need ever be aware of being intercepted.The shortcomings are that the approach is only possible ifthe host operating system permits interception. In bothintegration and interception, until there are OMGspecifications for multicast and group communicationsemantics, both strategies must be considered“proprietary”.The approach taken by the Object Group Service(OGS) [4] is most similar to ours, in that both adhere tothe common object service model of the OMG. Theprimary difference is in how the group service itself isactivated. In OGS the object’s interface explicitly inheritsfrom the OGS Groupable interface:interface FOO: mGroupAdmin:Groupable { void m0();};This makes fault tolerance visible to applicationobjects since they must be aware of the existence of theOGS objects to use their services. Application objectsconvey their invocations and responses, via the DynamicInvocation Interface and the Dynamic Skeleton Interface,to their associated OGS objects, which then coordinatewith each other to perform the operation on the replicas ofthe object and to return the results appropriately.The GroupPac package [6] is a set of common objectservices for implementing various group-basedcommunication models, for different fault tolerancestrategies. In contrast to OGS, GroupPac does not requireany explicit change to an application’s interface (e.g., it isnot necessary to inherits any group service interface).Instead, to use GroupPac, the application create a instanceof a portable interceptor (from CORBA spec), whichimplements the mechanisms to invoke GroupPac services.Fault tolerance is not visible to the application.In Section 2 we present OMG’s CosNamingspecification. Section 3 describes GroupPac and Section 4describes the implementation of CosNamingFT withGroupPac. In Section 5 we resent some performance testsfor CosNamingFT and comparisons with related work.