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

Remote fault detection, Remote loopback

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 8 highlights

Ethernet OAM link events Errored frame event Errored frame period event Errored frame seconds event Description An errored frame event occurs when the number of detected error frames in the detection window (specified detection interval) exceeds the predefined threshold. An errored frame period event occurs when the number of frame errors in the detection window (specified number of received frames) exceeds the predefined threshold. An errored frame seconds event occurs when the number of errored frame seconds (the second in which an errored frame appears is called an "errored frame second") detected on a port in the detection window (specified detection interval) reaches the predefined threshold. Remote fault detection Information OAMPDUs are exchanged periodically among Ethernet OAM entities across established OAM connections. In a network where traffic is interrupted due to device failures or unavailability, the flag field defined in Information OAMPDUs allows an Ethernet OAM entity to send error information (any critical link event type shown in Table 4) to its peer. You can use the log information to track ongoing link status and troubleshoot problems promptly. Table 4 Critical link events Type Link Fault Dying Gasp Critical Event Description Peer link signal is lost. An unexpected fault, such as power failure, occurred. An undetermined critical event happened. OAMPDU transmission frequencies Once per second. Non-stop. Non-stop. This Switch Series is able to receive Information OAMPDUs carrying the critical link events listed in Table 4. This Switch Series does not support sending Information OAMPDUs carrying Link Fault events. This Switch Series is able to send Information OAMPDUs carrying Dying Gasp events when the device is rebooted or relevant ports are manually shut down. Physical IRF ports, however, are unable to send this type of OAMPDUs. This Switch Series is unable to send Information OAMPDUs carrying Critical Events. Remote loopback Remote loopback is available only after the Ethernet OAM connection is established. With remote loopback enabled, the Ethernet OAM entity in active mode sends non-OAMPDUs to its peer. After receiving these frames, the peer does not forward them according to their destination addresses. Instead, it returns them to the sender along the original path. Remote loopback enables you to check the link status and locate link failures. Performing remote loopback periodically helps to detect network faults promptly. Furthermore, performing remote loopback by network segments helps to locate network faults. 3

  • 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
3
Ethernet OAM link events
Description
Errored frame event
An errored frame event occurs when the number of detected error frames in
the detection window (specified detection interval) exceeds the predefined
threshold.
Errored frame period event
An errored frame period event occurs when the number of frame errors in
the detection window (specified number of received frames) exceeds the
predefined threshold.
Errored frame seconds event
An errored frame seconds event occurs when the number of errored frame
seconds (the second in which an errored frame appears is called an
"errored frame second") detected on a port in the detection window
(specified detection interval) reaches the predefined threshold.
Remote fault detection
Information OAMPDUs are exchanged periodically among Ethernet OAM entities across established
OAM connections. In a network where traffic is interrupted due to device failures or unavailability, the
flag field defined in Information OAMPDUs allows an Ethernet OAM entity to send error information (any
critical link event type shown in
Table 4
) to its peer. You can use the log information to track ongoing link
status and troubleshoot problems promptly.
Table 4
Critical link events
Type
Description
OAMPDU transmission frequencies
Link Fault
Peer link signal is lost.
Once per second.
Dying Gasp
An unexpected fault, such as power failure,
occurred.
Non-stop.
Critical Event
An undetermined critical event happened.
Non-stop.
This Switch Series is able to receive Information OAMPDUs carrying the critical link events listed in
Table
4
.
This Switch Series does not support sending Information OAMPDUs carrying Link Fault events.
This Switch Series is able to send Information OAMPDUs carrying Dying Gasp events when the device is
rebooted or relevant ports are manually shut down. Physical IRF ports, however, are unable to send this
type of OAMPDUs.
This Switch Series is unable to send Information OAMPDUs carrying Critical Events.
Remote loopback
Remote loopback is available only after the Ethernet OAM connection is established. With remote
loopback enabled, the Ethernet OAM entity in active mode sends non-OAMPDUs to its peer. After
receiving these frames, the peer does not forward them according to their destination addresses. Instead,
it returns them to the sender along the original path.
Remote loopback enables you to check the link status and locate link failures. Performing remote
loopback periodically helps to detect network faults promptly. Furthermore, performing remote loopback
by network segments helps to locate network faults.