WAN传输故障总结

LAN/WAN-PHY是基于IEEE 802.3ae标准的。WAN-PHY控制器只能被用于PTE(Path Terminating Equipment)。当部署作为终端或者路由器间的PTE的EthernetWAN接口时，WAN-PHY不能和PoS(Packet over Sonet)或者EoS(Ethernet over Sonet)终端协同工作。X1在传输设备间时(LTE - Line Terminating Equipment or STE - SectionTerminating Equipment)，终端设备可以是分差复用(ADM)或密集波分复用(DWDM) OC-192c POS接口。

采用WAN-PHY的目的是使得10 Gigabit Ethernet兼容于SONET STS-192c的格式速率。因此，WIS(Wan Interface Sublayer)必须被插入到10Gigabit Ethernet物理编码子层中。

10Gigabit Ethernet可用于同步的SONET/SDH传输中，它被透明地在当前的密集波分复用(DWDM)网络，而不是直接让以太网帧和SONET/SDH相映射。在更高的层次上，WIS有以下特征：WIS允许WAN-PHY设备产生以太网数据流，以此来和物理层的OC-192c 或 VC-4-64c负载相联系，而不是让MAC和更高的层来处理。

理论上说，一个10BGBASE-W接口不能直接和SONET/SDH设备协同工作，因为WAN-PHY不能完全兼容于SONET/SDH光电信号参数。在实验中，SONET/SDH 可以和10GBASE-W 接口协同工作。

以下是POS和10GBASE-W的不同之处：

●POS和10GBASE-W不能协同工作，是因为协议体系结构并不一样。POS是基于像PPP这样的

串行协议。以此从帧的角度上讲，逻辑和物理上都不同于以太网。

●从SP的角度上讲，POS是一个3层point-to-point服务，而WAN-PHY却是2层的以太网传输。

因此，WAN-PHY和EoS(Ethernet over SONET)比较起来，封装技术并不是一样的。

POS的光电信号可以和SONET/SDH协议兼容，而WAN-PHY却不能。

●CISCO POS支持APS(Automatic Protection Switching),可以在50毫秒内恢复链路故

障，而WAN-PHY不被支持。

transport

1

transport

2

C1

Te2/14/1/0

③

在上图表示的①-③处出现链路故障故障时，传输设备会发出不同的信号给数据设备。现结合实际链路测试，对传输告警信号作出总结。

1.在①处出现传输链路路故障时，理论上传输设备OT2会在相同数据流方向上产生lais

告警给下游设备X1，会在相反方向上产生lrdi告警给上游设备XX1。下面是实际的测试记录。

X1：

RP/0/RP0/CPU0:XX-XX-XX-XX#sh controllers wanphy 2/13/1/0 alarms

Fri Jul 27 00:19:33.288 GMT

Interface: wanphy2/13/1/0

Configuration Mode: WAN Mode

SECTION

LOF = 3, LOS = 1, BIP(B1) = 156

LINE

AIS = 3, RDI = 2, FEBE = 488513983, BIP(B2) = 31524

PATH

AIS = 3, RDI = 0, FEBE = 7703, BIP(B3) = 39

LOP = 0, NEWPTR = 0, PSE = 0, NSE = 0

WIS ALARMS

SER = 8, FELCDP = 3, FEAISP = 5

WLOS = 1, PLCD = 0

LFEBIP = 488513983, PBEC = 39, PLMP = 2

Active Alarms[All defects]: lof, path ais, line ais, sef,

Active Alarms[Highest Alarms]: lof

Rx(K1/K2): N/A, Tx(K1/K2): N/A

S1S0 = N/A, C2 = N/A

PATH TRACE BUFFER

Remote IP addr:

BER thresholds: N/A

TCA thresholds: N/A

实际测试结果：X1收到lof, path ais, line ais, sef告警，主要的告警为lof。XX1：

dis transmission-alarm GigabitEthernet 3/0/0

Interface: GigabitEthernet3/0/0

Filter function: disabled

Damping function: disabled

Last reset time: 0-0-0,0:0:0.0

Alarm auais

Status: Down

Flapping count: 0

Alarm b3tca

Status: Down

Flapping count: 704

Alarm lais

Status: Down, If down

Flapping count: 24556

Alarm lof

Status: Down, If down

Flapping count: 8

Alarm lom

Status: Down

Flapping count: 0

Alarm lop

Status: Down

Flapping count: 6

Alarm los

Status: Down, If down Flapping count: 4

Alarm lrdi

Status: Up

Flapping count: 47275

Alarm lrei

Status: Down

Flapping count: 0

Alarm oof

Status: Down

Flapping count: 8

Alarm pais

Status: Down

Flapping count: 0

Alarm prdi

Status: Up

Flapping count: 7500733

Alarm prei

Status: Down

Flapping count: 0

Alarm pplm

Status: Down

Flapping count: 20

Alarm rdool

Status: Down

Flapping count: 0

Alarm rrool

Status: Down

Flapping count: 0

Alarm sdbere

Status: Down

Flapping count: 8

Alarm sfbere

Status: Down

Flapping count: 6

Alarm trool

Status: Down

Flapping count: 0

Alarm puneq

Status: Down

Flapping count: 48

Alarm lcd

Status: Down

Flapping count: 8

Alarm wlnk

Status: Down, If down, Log

Flapping count: 8

lof, path ais, line ais, sef告警。

实际测试结果XX1收到了lrdi,prdi告警，跟预期的结果一致。

结论：

默认配置下X1的10BGBASE-W端口开启了对SF(Signal Failure)告警的支持，也就是收到lof告警，就一定会down端口。

而XX1会收到lrdi、prdi告警，huawei默认未开启对上述告警的支持。因此它不会down 端口。

2.在②处出现传输链路路故障时，理论上传输设备OT1会在相同数据流方向上产生lais

告警给下游设备XX1，会在相反方向上产生lrdi告警给上游设备X1。下面是实际的测试记录。

XX1：

[XX-XX-XX-XX]dis transmission-alarm GigabitEthernet 3/0/0

Interface: GigabitEthernet3/0/0

Filter function: disabled

Damping function: disabled

Last reset time: 0-0-0,0:0:0.0

Alarm auais

Status: Down

Flapping count: 0

Alarm b3tca

Status: Up

Flapping count: 707

Alarm lais

Status: Down, If down

Flapping count: 24556

Alarm lof

Status: Up, If down

Flapping count: 9

Alarm lom

Flapping count: 0

Alarm lop

Status: Up

Flapping count: 7

Alarm los

Status: Down, If down Flapping count: 4

Alarm lrdi

Status: Down

Flapping count: 47278

Alarm lrei

Status: Down

Flapping count: 0

Alarm oof

Status: Up

Flapping count: 9

Alarm pais

Status: Down

Flapping count: 0

Alarm prdi

Status: Down

Flapping count: 7500748

Alarm prei

Status: Down

Flapping count: 0

Alarm pplm

Status: Up

Flapping count: 21

Alarm rdool

Flapping count: 0

Alarm rrool

Status: Down

Flapping count: 0

Alarm sdbere

Status: Up

Flapping count: 9

Alarm sfbere

Status: Up

Flapping count: 7

Alarm trool

Status: Down

Flapping count: 0

Alarm puneq

Status: Down

Flapping count: 48

Alarm lcd

Status: Up

Flapping count: 9

Alarm wlnk

Status: Up, If down, Log

Flapping count: 9

实际测试结果XX1收到了b3tca,lof, lop,oof,pplm,sdbere,sfbere,lcd,wlnk告警，跟预期的结果稍有差异。

X1：

RP/0/RP0/CPU0:XX-XX-XX-XX#sh controllers wanphy 2/13/1/0 alarms

Fri Jul 27 00:29:25.929 GMT

Interface: wanphy2/13/1/0

Configuration Mode: WAN Mode

SECTION

LOF = 4, LOS = 1, BIP(B1) = 205

LINE

AIS = 4, RDI = 3, FEBE = 502390473, BIP(B2) = 42572

PATH

AIS = 4, RDI = 0, FEBE = 62935, BIP(B3) = 54

LOP = 0, NEWPTR = 0, PSE = 0, NSE = 0

WIS ALARMS

SER = 11, FELCDP = 4, FEAISP = 7

WLOS = 1, PLCD = 0

LFEBIP = 502390473, PBEC = 54, PLMP = 6

Active Alarms[All defects]: rdi, path far end ais, path feais,

Active Alarms[Highest Alarms]: rdi

Rx(K1/K2): N/A, Tx(K1/K2): N/A

S1S0 = N/A, C2 = N/A

PATH TRACE BUFFER

Remote IP addr:

BER thresholds: N/A

TCA thresholds: N/A

实际测试结果：X1收到rdi, path far end ais, path feais告警，主要的告警为rdi，跟预期的结果一致。

结论：

XX1会收到b3tca,lof, lop,oof,pplm,sdbere,sfbere,lcd,wlnk告警，huawei默认开启对lof的支持，就一定会down端口。同时wlnk时10GE-WAN端口独有的告警，该告警不可配置，且默认动作是down端口。

默认配置下X1的10BGBASE-W端口未开启了对SD(Signal Degrade)告警的支持，也就是默认收到rdi告警，不会down端口。

3.在①、②处同时出现传输链路路故障时，理论上传输设备OT1和OT2会在相同数据流方向上产生lais告警给下游设备X1和XX1，会在相反方向上产生lrdi告警给上游设备XX1

和X1。下面是实际的测试记录。

X1：

RP/0/RP0/CPU0:XX-XX-XX-XX#sh controllers wanphy 2/13/1/0 alarms

Fri Jul 27 00:35:27.496 GMT

Interface: wanphy2/13/1/0

Configuration Mode: WAN Mode

SECTION

LOF = 5, LOS = 1, BIP(B1) = 221

LINE

AIS = 5, RDI = 4, FEBE = 971779674, BIP(B2) = 45686

PATH

AIS = 5, RDI = 0, FEBE = 60526, BIP(B3) = 57

LOP = 0, NEWPTR = 0, PSE = 0, NSE = 0

WIS ALARMS

SER = 12, FELCDP = 4, FEAISP = 9

WLOS = 1, PLCD = 0

LFEBIP = 971779674, PBEC = 57, PLMP = 6

Active Alarms[All defects]: lof, rdi, path ais, line ais, sef,

Active Alarms[Highest Alarms]: lof

Rx(K1/K2): N/A, Tx(K1/K2): N/A

S1S0 = N/A, C2 = N/A

PATH TRACE BUFFER

Remote IP addr:

BER thresholds: N/A

TCA thresholds: N/A

实际测试结果：X1收到lof, rdi, path ais, line ais, sef,告警，主要的告警为lof。跟预期一致。

XX1：

[XX-XX-XX-XX] dis transmission-alarm GigabitEthernet 3/0/0

Interface: GigabitEthernet3/0/0

Filter function: disabled

Damping function: disabled

Last reset time: 0-0-0,0:0:0.0

Alarm auais

Status: Down

Flapping count: 0

Alarm b3tca

Status: Up

Flapping count: 723

Alarm lais

Status: Down, If down

Flapping count: 24556

Alarm lof

Status: Up, If down

Flapping count: 11

Alarm lom

Status: Down

Flapping count: 0

Alarm lop

Status: Up

Flapping count: 9

Alarm los

Status: Down, If down Flapping count: 4

Alarm lrdi

Status: Down

Flapping count: 47278

Alarm lrei

Status: Down

Alarm oof

Status: Up

Flapping count: 11

Alarm pais

Status: Down

Flapping count: 0

Alarm prdi

Status: Up

Flapping count: 7500903 Alarm prei

Status: Down

Flapping count: 0

Alarm pplm

Status: Up

Flapping count: 23

Alarm rdool

Status: Down

Flapping count: 0

Alarm rrool

Status: Down

Flapping count: 0

Alarm sdbere

Status: Up

Flapping count: 11

Alarm sfbere

Status: Up

Flapping count: 9

Alarm trool

Status: Down

Alarm puneq

Status: Down

Flapping count: 48

Alarm lcd

Status: Up

Flapping count: 11

Alarm wlnk

Status: Up, If down, Log

Flapping count: 11

实际测试结果：XX1收到b3tca,lof, lop, oof, prdi,pplm,sdbere,sfbere,lcd,wlnk 告警。跟预期基本一致。

4.在③处出现传输链路路故障时，虽然这次的测试并未涉及到该项内容。然后仍然可以预期到测试结果。传输设备OT1和OT2不会发告警给上下游设备。XX1在收到los、lof告警后默认会down端口。同时它会将该告警转发给下游路由器X1，同理，X1在收到该告警后，默认会down端口。

通过以上的测试内容，我们不难发现，传输链路的物理层故障，对上层的数据设备影响很大。特别是链路单通情况的发生，会造成流量异常。严重危及到网络正常的数据流量。而且，不同厂家的设备对告警的支持也不尽相同。但是只要清楚了告警信息的分类，以及告警信息产生的原因，再针对该情况做一些配置优化，就可以杜绝该隐患的发生。

下面是具体的优化配置：

●huawei：

interface GigabitEthernet3/0/0

transmission-alarm down laislof lop los lrdipaisprdi

●CISCO：

configure

controllerwanphy 2/13/1/0

reportsd-ber

thresholdsd-ber 7

thresholdsf-ber 4