FSP白皮书

Power5 FSP Basics and HMC Connectivity Overview Version 1.0 March 2005 1Introduction This intended purpose of this document is to help provide Field and Remote Support personnel with a better understanding of basic FSP functions and how the FSP interacts with the HMC. Also included are sections devoted to service strategy, common symptoms and solutions, known problems, and a question and answer section. Trend and failure analysis of FSP cards (or planars equipped with integrated FSP's) indicates that many parts are being replaced needlessly due to an inadequate understanding of how this new technology functions and/or inadequate Problem Determination procedures. By providing additional theory of operation and debug information, the expectation is that unnecessary FRU usage as well as duration of install and repair activity will be reduced. This subject is discussed in more detail the Service Strategy section that appears later in this document. Notes: 1) The information and concepts discussed in this document are based on Power5 i & pSeries entry and midrange systems. While many of the same concepts apply to high end Power5 systems which are equipped with redundant FSP's and bulk power subsystems. These system types or subsystems are not explicitly covered by or discussed in this document however content pertaining to these systems may be added in a future revision of this document. 2) This document is intended to be used as a supplement to existing service and education documentation. Questions or comments regarding this document may be directed to Bob Vidrick, Austin Product Engineering (rvidrick@). 2Section 1 - FSP Ethernet Connectivity Overview We will start by explaining how the FSP communicates with the HMC or other attached network device. When the FSP is in it's factory default configuration, it's Ethernet ports are configured as DHCP clients. When AC power applied to the system unit, the FSP will automatically begin it's boot process. Assuming that a network link on either of the FSP's Ethernet ports is in an active state, The FSP will issue a DHCP request on the active port(s). Note that active means that the link light is illuminated which indicates that the FSP is communicating with another device on the network (but NOT necessarily an HMC) The DHCP request will be issued during the first 60 second period after AC power is applied however the completion of the boot process to FSP standby will take 3 to 5 min. The DHCP request process will be repeated every time one of the following actions is performed: • AC power is cycled. • The FSP is reset (rebooted) via the Operator Panel pinhole reset method • The ASMI Reset Service Processor menu option is utilized Notes: 1) A common misconception is that if a Managed System has had AC power applied to it before the HMC is configured that extensive recovery steps (flipping FSP Dip switches, removing time of day battery etc) must be performed to allow the FSP to communicate correctly. This is NOT the case! 2) In addition to the 3 actions listed above, numerous other ASMI options exist that will cause the FSP to reboot when certain configuration changes have been made. 3) There is one other condition under which the FSP will generate a DHCP request. If the FSP Ethernet link is not active (no cable connected) during the FSP boot process and then an active connection is made after the FSP is booted to standby, a DHCP request will now be generated. Keep in mind that this operation will occur as soon as the link goes active, regardless of what device is on the other end of the link. Example: If an Ethernet switch is in the path between the FSP and the HMC, the connection between the switch and the HMC needs to be established before the connection between the FSP and the switch otherwise, the DHCP request will not be seen by the HMC. 4) Future Firmware releases beginning with the 01SF225 release will also allow a DHCP request to be generated anytime the network link is dropped for approximately 60 seconds and then re-established. Now we’ve established how and when a DHCP request is generated. What happens next depends on whether the FSP receives a response to it's request: 3Scenario #1: Response to DHCP request is NOT received The FSP will assign the following default IP addresses to it's ports: HMC1 - 192.168.2.147 HMC2 - 192.168.3.147 The assignment of these default addresses allows the user to configure and attach a network capable device such as a PC or Laptop, connect it directly to one of the FSP network ports and access the FSP's ASMI interface. Note that these addresses are NOT permanent, (static) but are just defaults which the FSP continues to use until the next DHCP request cycle is performed and a response is received. Scenario #2: Response to DHCP request IS received In this case, the FSP simply accepts the IP address it was administered by the DHCP server however this new IP address now replaces the default IP address the FSP would have assigned itself above in scenario #1. The new IP address now becomes the new default IP address for that port however just like in scenario #1, the DHCP request process will take place again on the next power or FSP reset cycle. If a DHCP response containing a different IP address is received, the FSP will accept it AND replace the previous default IP address with the new one. A few examples of how this can happen are listed below: • System (FSP) is attached to a different HMC (using the same FSP port that was previously configured) • If the HMC's disk drive is reloaded or replaced, the address may change, particularly if multiple systems are attached and are discovered in a different order. • An additional DHCP server such as another HMC configured as a DHCP server appears on the network As long as no configuration changes are made, the HMC should always assign the same IP address to a respective Ethernet port. It does this by keeping track of the network mac (hardware) addresses assigned to each Ethernet port. These mac addresses are unique for every Ethernet device.

本科学生社会实践活动

写实记录及考核登记表

姓 名：＿＿＿＿＿＿＿＿ 学 号：＿＿＿＿＿＿＿＿

学 院：＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿

专 业：＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿

年 级： □一年级 □二年级 □三年级 □其它________

所在团支部：＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿

山东大学制

1

填表须知

一.本表用于写实记录和登记考核我校学生的社会实践经历，是《形势政策与社会实践》必修课社会实践环节的考试试卷及向毕业生颁发《社会实践经历证书》的依据。内容由学生本人、团支部、社会实践接收单位(个人)、指导教师、辅导员、学院团委、学校团委等分别填写，一律用钢笔或签字笔填写。

二.本表每学年开学后第四周，由学校统一下发，平时由学生自己保存。每学年开学后第一周收回上一学年所发表格，并收取社会实践报告及辅助性证明材料，完成成绩考核后由各学院团委收齐，以班级团支部为单位按照必修课试卷归档要求装订成册，以学院为单位统一报送学校团委。

三.表A主要记录学生参加社会实践活动的概况，表B主要记录学生参加社会实践活动的过程，由学生本人本着写实性、集中性、实时性的原则填写; 表B要求以天为单位将每天的实践活动记录在1张表格上，并注意按照活动时间次序在“B”后的“（）”中标注阿拉伯数字序号。如果活动天数超过6天，可复制表B加页填写。

四.表C主要填写学生在某一时间段集中性开展某一类社会实践活动的总结及成绩成果，由学生本人填写，以及实践接收单位或个人对学生的评价意见，由实践接收单位负责人或实践接收个人签署，参加家庭角色体验类实践活动的由家长签署，并注明接收单位（个人）或家长的具体联系方式（固定电话及通讯地址），参加团队活动的学生还必须由团队指导教师签署评价意见。参加非家庭角色体验类实践活动的评价意见不得由家长签署，学生提供的联系方式不完整、不准确、不真实的视为弄虚作假。

本科学生社会实践活动

写实记录及考核登记表

姓 名：＿＿＿＿＿＿＿＿ 学 号：＿＿＿＿＿＿＿＿

学 院：＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿

专 业：＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿

年 级： □一年级 □二年级 □三年级 □其它________

所在团支部：＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿

山东大学制

1 填表须知

一.本表用于写实记录和登记考核我校学生的社会实践经历，是《形势政策与社会实践》必修课社会实践环节的考试试卷及向毕业生颁发《社会实践经历证书》的依据。内容由学生本人、团支部、社会实践接收单位(个人)、指导教师、辅导员、学院团委、学校团委等分别填写，一律用钢笔或签字笔填写。

二.本表每学年开学后第四周，由学校统一下发，平时由学生自己保存。每学年开学后第一周收回上一学年所发表格，并收取社会实践报告及辅助性证明材料，完成成绩考核后由各学院团委收齐，以班级团支部为单位按照必修课试卷归档要求装订成册，以学院为单位统一报送学校团委。

三.表A主要记录学生参加社会实践活动的概况，表B主要记录学生参加社会实践活动的过程，由学生本人本着写实性、集中性、实时性的原则填写; 表B要求以天为单位将每天的实践活动记录在1张表格上，并注意按照活动时间次序在“B”后的“（）”中标注阿拉伯数字序号。如果活动天数超过6天，可复制表B加页填写。

四.表C主要填写学生在某一时间段集中性开展某一类社会实践活动的总结及成绩成果，由学生本人填写，以及实践接收单位或个人对学生的评价意见，由实践接收单位负责人或实践接收个人签署，参加家庭角色体验类实践活动的由家长签署，并注明接收单位（个人）或家长的具体联系方式（固定电话及通讯地址），参加团队活动的学生还必须由团队指导教师签署评价意见。参加非家庭角色体验类实践活动的评价意见不得由家长签署，学生提供的联系方式不完整、不准确、不真实的视为弄虚作假。

产品规格

NetApp FAS9000 模块化混合

闪存系统

凭借行业领先的数据管理功能，跨闪存、磁盘和云资源快速响应苛

刻的存储需求。

主要优势

提升企业级应用程序性能

借助高出多达 50% 的性能降低延迟并

加快运营速度。

最大限度地延长正常运行时间

消除计划内停机。无中断添加、升级或

停用存储。

增强可靠性、可用性和可维护性

借助高级模块化设计简化维护和升级。

整合基础架构

最高扩展到 172 PB，与 NetApp® 全闪

存 FAS 系统组合成集群，并集成现有第

三方存储阵列。

更迅速地响应不断变化的需求

轻松进行重新配置以满足不断变化的性

能、容量和连接需求。

针对混合云进行了优化

便于跨内部资源和云资源实施面向服务

的 IT 架构。挑战

提供高性能和最大可用性，同时降低 TCO 并消除数据孤岛

对于如今的关键业务运营而言，性能和可用性至关重要。然而，为了保持性能和

可用性，基础架构可能变得更为复杂，导致管理成本上升、出现代价高昂错误的

可能性增加，而且需要专门的培训、技能和知识。

传统存储和数据架构的诸多结构性限制，导致许多企业裹足不前。虽然传统存储

阵列可以满足基本需求，但管理和维护起来都很复杂，而且每三至五年必须进行

更换，这样容易造成总成本上升。此外，它们还会在您的企业中形成数据孤岛。

解决方案

最大限度提高存储性能和可升级性

数据驱动型企业需要一种全新的存储方式，他们通过集成可扩展高性能硬件和自

适应存储软件，支持现有工作负载以及新应用程序。存储系统的设计应简化维护

并延长存储系统的使用寿命。

NetApp FAS9000 混合存储系统专为满足这些需求而设计。FAS9000 由 NetApp

ONTAP® 数据管理软件提供支持，可以整合 SAN 和 NAS 存储基础架构。

FAS9000 专为充分利用 40GbE 和 32 Gb FC 而设计，它不仅是 NetApp 所打造

的功能空前强大的 FAS 系统，而且其智能模块化设计可增强可靠性、可用性和可