HP Brocade 8/12c Brocade Network Advisor SMI Agent Developer's Guide - Page 51

Prerequisites, Registration, Data model, The instances for the CIM classes Brocade_SoftwareIdentity

Page 51 highlights

Fabric profile 3 Prerequisites Only the HBAs that register a FDMI host name in the Name Server (NS) on the switch or fabric support the Brocade_Platform model. Currently, the EOS switches do not support FDMI. Therefore, HBAs connected to EOS switches do not support the Brocade_Platform model, including the instance classes and association classes. NOTE The switch connected to an FDMI-enabled HBA runs on Fabric OS v7.0.0. Also, the seed switch runs on Fabric OS v7.0.0 to support this profile. Registration Refer to "Registration" on page 18. Data model Figure 19 shows the class diagram of the classes and properties supported in the FDMI subprofile. The instances for the CIM classes Brocade_SoftwareIdentity, Brocade_HBAProduct, Brocade_PhysicalHBA, and Brocade_PortController are available as part of the FDMI subprofile provided the switches are running Fabric OS v7.0.0. For a single-node single-port HBA, there is a single Brocade_Node instance hosted on a Brocade_Platform and a single Brocade_PortController representing the logical aspects of the Brocade_PhysicalHBA controlling a single Brocade_NodeFCPort. For a single-node dual-port HBA, there is a single Brocade_Node hosted on a Brocade_Platform and a single Brocade_PortController representing the logical aspects of the Brocade_PhysicalHBA controlling both Brocade_NodeFCPort instances. For a dual-node dual-port HBA, there are two Brocade_Node instances hosted on the same Brocade_Platform and a single Brocade_PortController representing the logical aspects of the Brocade_PhysicalHBA controlling both Brocade_NodeFCPort instances. Brocade Network Advisor SMI Agent Developer's Guide 39 53-1002169-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168

Brocade Network Advisor SMI Agent Developer’s Guide
39
53-1002169-01
Fabric profile
3
Prerequisites
Only the HBAs that register a FDMI host name in the Name Server (NS) on the switch or fabric
support the Brocade_Platform model. Currently, the EOS switches do not support FDMI. Therefore,
HBAs connected to EOS switches do not support the Brocade_Platform model, including the
instance classes and association classes.
NOTE
The switch connected to an FDMI-enabled HBA runs on Fabric OS v7.0.0. Also, the seed switch runs
on Fabric OS v7.0.0 to support this profile.
Registration
Refer to
“Registration”
on page 18.
Data model
Figure 19
shows the class diagram of the classes and properties supported in the FDMI subprofile.
The instances for the CIM classes Brocade_SoftwareIdentity, Brocade_HBAProduct,
Brocade_PhysicalHBA, and Brocade_PortController are available as part of the FDMI subprofile
provided the switches are running Fabric OS v7.0.0.
For a single-node single-port HBA, there is a single Brocade_Node instance hosted on a
Brocade_Platform and a single Brocade_PortController representing the logical aspects of the
Brocade_PhysicalHBA controlling a single Brocade_NodeFCPort.
For a single-node dual-port HBA, there is a single Brocade_Node hosted on a Brocade_Platform
and a single Brocade_PortController representing the logical aspects of the Brocade_PhysicalHBA
controlling both Brocade_NodeFCPort instances.
For a dual-node dual-port HBA, there are two Brocade_Node instances hosted on the same
Brocade_Platform and a single Brocade_PortController representing the logical aspects of the
Brocade_PhysicalHBA controlling both Brocade_NodeFCPort instances.