HP 6125XLG R2306-HP 6125XLG Blade Switch High Availability Configuration Guide - Page 19

Maintenance point

Get HP 6125XLG PDF manuals and user guides View all HP 6125XLG manuals
Add to My Manuals
Save this manual to your list of manuals

Page 19 highlights

An MA serves the specified VLAN or no VLAN. An MA that serves a VLAN is considered carrying VLAN attribute. An MA that serves no VLAN is considered having no VLAN attribute. An MP can receive packets sent by other MPs in the same MA. The level of an MA equals the level of the MD that the MA belongs to. Maintenance point An MP is configured on a port and belongs to an MA. MPs include the following types: maintenance association end points (MEPs) and maintenance association intermediate points (MIPs). • MEP MEPs define the boundary of the MA. Each MEP is identified by a MEP ID. The MA to which a MEP belongs defines the VLAN of packets sent by the MEP; the level of a MEP equals the level of the MD that the MEP belongs to, and the level of packets sent by a MEP equals the level of the MEP. The level of a MEP determines the levels of packets that the MEP can process. A MEP forwards packets at a higher level and processes packet of its level or lower. The processing procedure is specific to packets in the same VLAN. Packets of different VLANs are independent. MEPs include inward-facing MEPs and outward-facing MEPs: { An outward-facing MEP sends packets to its host port. { An inward-facing MEP does not send packets to its host port. Rather, it sends packets to other ports on the device. • MIP A MIP is internal to an MA. It cannot send CFD packets actively; however, it can handle and respond to CFD packets. By cooperating with MEPs, a MIP can perform a function similar to ping and traceroute. A MIP forwards packets of a different level without any processing and only processes packet of its level. The MA to which a MIP belongs defines the VLAN of packets that the MEP can receive; the level of a MIP is defined by its generation rule and the MD to which the MIP belongs. MIPs are generated on each port automatically according to related MIP generation rules: { Default rule-If no lower-level MIP exists on an interface, a MIP is created on the current level. A MIP can be created even if no MEP is configured on the interface. { Explicit rule-If no lower-level MIP exists and a lower-level MEP exists on an interface, a MIP is created on the current level. A MIP can be created only when a lower-level MEP is created on the interface. If a port has no MIP, the system will check the MAs in each MD (from low to high levels), and follow the procedure as described in Figure 3 to create or not to create MIPs at the current level. 14

  • 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
14
An MA serves the specified VLAN or no VLAN. An MA that serves a VLAN is considered carrying VLAN
attribute. An MA that serves no VLAN is considered having no VLAN attribute. An MP can receive
packets sent by other MPs in the same MA. The level of an MA equals the level of the MD that the MA
belongs to.
Maintenance point
An MP is configured on a port and belongs to an MA. MPs include the following types: maintenance
association end points (MEPs) and maintenance association intermediate points (MIPs).
•
MEP
MEPs define the boundary of the MA. Each MEP is identified by a MEP ID.
The MA to which a MEP belongs defines the VLAN of packets sent by the MEP; the level of a MEP
equals the level of the MD that the MEP belongs to, and the level of packets sent by a MEP equals
the level of the MEP. The level of a MEP determines the levels of packets that the MEP can process.
A MEP forwards packets at a higher level and processes packet of its level or lower. The
processing procedure is specific to packets in the same VLAN. Packets of different VLANs are
independent.
MEPs include inward-facing MEPs and outward-facing MEPs:
{
An outward-facing MEP sends packets to its host port.
{
An inward-facing MEP does not send packets to its host port. Rather, it sends packets to other
ports on the device.
•
MIP
A MIP is internal to an MA. It cannot send CFD packets actively; however, it can handle and
respond to CFD packets. By cooperating with MEPs, a MIP can perform a function similar to ping
and traceroute. A MIP forwards packets of a different level without any processing and only
processes packet of its level.
The MA to which a MIP belongs defines the VLAN of packets that the MEP can receive; the level
of a MIP is defined by its generation rule and the MD to which the MIP belongs. MIPs are
generated on each port automatically according to related MIP generation rules:
{
Default rule
—If no lower-level MIP exists on an interface, a MIP is created on the current level.
A MIP can be created even if no MEP is configured on the interface.
{
Explicit rule
—If no lower-level MIP exists and a lower-level MEP exists on an interface, a MIP is
created on the current level. A MIP can be created only when a lower-level MEP is created on
the interface.
If a port has no MIP, the system will check the MAs in each MD (from low to high levels), and follow
the procedure as described in
Figure 3
to create or not to create MIPs at the current level.