- Copyright
- PC System Architecture Series
- Figures
- Tables
- Acknowledgments
- About This Book
- Core Concepts
- QP Creation and Operation
- Protection Mechanisms
- Detailed Description of the Transport Services
- RC Transport Service
- RC Support Requirement
- RC Basic Operational Characteristics
- RC Connection Establishment
- Packet Opcodes
- RC Message Transfer Primer
- Structure of This Discussion
- QP State before Any Messages Are Transferred
- Standard Operation in Fast, Error-Free Environment
- Traffic Reduction
- Packet Delivery Delays
- Packet Loss
- Nak Errors
- RQ Logic's Error Detecting and Handling
- End-to-End Flow Control
- SQ Logic Can Use MSN to Complete WQEs
- Additional Reference Information
- UC Transport Service
- RD Transport Service
- UD Transport Service
- Raw Transport Service Types
- Goal: Tunneling Non-IBA Packets through IBA Network
- Solution: Disguise It as Special-Purpose IBA Packet
- Raw QPs Are Used to Transmit/Receive Non-IBA Packets
- Raw QP Support Requirement
- Raw Transport Services Are Unreliable
- Send and Receive Are Only Supported Operation Types
- Basic Operational Description
- Raw Datagrams Do Not Have an ICRC
- Raw Datagrams Do Not Have a Destination QP
- LRH:LNH Indicates Packet Type
- Raw IPv6 Datagrams
- Raw EtherType Datagrams
- Additional Reference Material
- Multicasting
- Automatic Path Migration
- Static Rate Control
- RC Transport Service
- Link and Physical Layer Descriptions
- Detailed Description of the Link Layer
- Link Layer Functional Overview
- Link State Machine
- Detailed Description of LRH
- QoS within the Subnet: SL and VLs
- Detailed Description of VL Arbitration
- Link-Level Flow Control
- Packet CRCs
- Intro to the Packet Delimiters
- Packet Receive State Machine
- Data Packet Check
- Link Packet (Flow Control Packet) Check
- Switch Performs Packet Forwarding
- Overview of Router Port's Link Layer
- Detailed Physical Layer Description
- Detailed Description of the Link Layer
- The SM and SA
- The SMI
- Purpose of the SMI (QP0)
- The SMI on a CA and Router
- The SMI on Switches
- Detailed Switch Handling of SMPs
- Detailed CA or Router Handling of SMPs
- SM Wishes to Access an Attribute in Its Local Device
- SM Can Reside in a Switch
- SMI Is a Privileged Resource
- SMI Only Communicates with Other SMIs
- Port States SMPs Can Be Sent and Received In
- SMPs Never Leave the Subnet
- Setting Up an HCA Port's SMI
- How the SM Sends a Message and Handles a Response
- SMP Source and Destination
- The SMI and the Q_Key
- The SMI and Partitions
- Additional Reference Material
- Detailed Description of MADs
- SM Methods and Attributes
- Multiple SMs
- Discovery
- The GSI
- Detailed Description of SA
- Purpose of the SA
- SA Accessed Using GMPs
- Location of the SA
- Requester Access Authorization
- SA Methods and Attributes
- Record Identifier (RID) Definition
- SubnAdmGet() Operation
- SubnAdmSet() Operation
- Definition of a Table
- SubnAdmConfig() Operation
- Database Queries Using SubnAdmGetTable()
- Fetch Entire Database
- Reliable Multi-Packet Transaction Protocol
- Additional Reference Information
- The SMI
- General Services
- Baseboard Management
- Roles of the Other Managers
- The BM Reaches behind the IBA Front-End
- Chassis and Module
- Chassis Baseboard Management Elements
- Passively Managed Chassis
- Module BM Elements
- Non-Module IBA Devices
- BM MAD Format
- BM Methods
- BM Attributes
- BM Sending a Command to the MME
- CME Sends a Command to the BM
- BM-related Traps
- Performance Management
- Communications Management
- Device Management
- Glossary
- Baseboard Management
- Index
Are You Alive?
The Master SM maintains an activity counter in the form of the SMInfo.ActCount attribute element.
ActCount increments each time the Master SM issues a request packet or performs any “other” management activities (the specification is vague). This counter is the Master SM's heartbeat.
Standby SMs periodically issue SubnGet(SMInfo) requests to see if the Master SM is still alive (i.e., has the counter incremented since the standby SM last read it).
The polling interval is set by the OS and is outside the scope of the specification.
If the Master SM appears dead (i.e., no response is received, or the response indicates that the ActCount is not changing), the standby SM transitions back to the Discovering state (more later).
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.