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

Backbone-to-edge device sharing (no FCIP con d in backbone), Limitations

Page 95 highlights

FC routing 3 Backbone-to-edge device sharing (no FCIP configured in backbone) • Figure 40 shows the data model for backbone-to-edge device sharing. If only the backbone fabric is being managed through Brocade Network Advisor, then only instances in the BackBone fabric view are discovered. If only the edge fabric is being managed through Brocade Network Advisor, refer to the "Limitations" section. If both the backbone and the edge fabrics are being managed through Brocade Network Advisor, then all instances and associations are discoverable. • In the case of backbone edge device sharing, there is only one front phantom domain and two xlate phantom domain switches. On the Edge fabric side, there is one front domain and one xlate domain switch instance created. On the BackBone fabric side, there is only an xlate domain switch created and no front phantom domain. Because the xlate phantom domain switch is always behind the front phantom domain switch, the backbone switch itself represents the front phantom domain. In addition to the logical port instance on the front phantom in the edge fabric, FOS creates another instance of the logical port on the backbone logical switch. This is the logical port instance that is connected to another logical port instance on the xlate phantom through a SANActiveConnection. Brocade Network Advisor SMI Agent Developer's Guide 83 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
83
53-1002169-01
FC routing
3
Backbone-to-edge device sharing (no FCIP configured
in backbone)
Figure 40
shows the data model for backbone-to-edge device sharing. If only the backbone
fabric is being managed through Brocade Network Advisor, then only instances in the
BackBone fabric view are discovered. If only the edge fabric is being managed through
Brocade Network Advisor, refer to the
“Limitations”
section. If both the backbone and the edge
fabrics are being managed through Brocade Network Advisor, then all instances and
associations are discoverable.
In the case of backbone edge device sharing, there is only one front phantom domain and two
xlate phantom domain switches. On the Edge fabric side, there is one front domain and one
xlate domain switch instance created. On the BackBone fabric side, there is only an xlate
domain switch created and no front phantom domain. Because the xlate phantom domain
switch is always behind the front phantom domain switch, the backbone switch itself
represents the front phantom domain. In addition to the logical port instance on the front
phantom in the edge fabric, FOS creates another instance of the logical port on the backbone
logical switch. This is the logical port instance that is connected to another logical port
instance on the xlate phantom through a SANActiveConnection.