Alcatel-Lucentalcatel-lucent.de/enterprise/ipush/ipush79/EthernetOAM... · 2010-03-23 · CONFIGURATION COMMANDS ... This document describes the use of Ethernet OAM to monitor a Service

Ethernet OAM

Using Ethernet OAM to monitor Service Provider networks. Ethernet Services over Ring Topology using RSTP or ERP.

Alcatel-Lucent Enterprise Products Group Solutions Document

August 2009 ISSUE 1

Copyright © 2009 Alcatel-Lucent. Unpublished and not for publication. All rights reserved.

- 1 -

Table of Contents 1. INTRODUCTION .................................................................................................................................................................... 2 2. SCALABILITY ........................................................................................................................................................................ 3 3. TEST ENVIRONMENT - SOLUTIONS LAB ...................................................................................................................... 3 4. SOLUTION STRATEGY ........................................................................................................................................................ 4 5. CONFIGURATION COMMANDS........................................................................................................................................ 5 6. VERIFICATION COMMANDS............................................................................................................................................. 8 7. SNMP....................................................................................................................................................................................... 11 8. CONFIGURATION NOTES................................................................................................................................................. 13

8.1 7750 CONFIGURATION ..................................................................................................................................................... 13 8.2 6850 CONFIGURATION ..................................................................................................................................................... 15

1. INTRODUCTION This document describes the use of Ethernet OAM to monitor a Service Provider’s network in an Alcatel-Lucent based network. The Provider’s topology consists of ALU 7450/7750 PEs connected to an MPLS core, heading rings of ALU 6850/6400 Provider’s Access switches. In this setup, the rings use RSTP or ERP as their link redundancy and loop prevention protocol. It can scale to several provider Maintenance Domains with hundreds of rings per MD. Operator level domains are not detailed in this document, although many providers also own the some or all of networks in the operator level. The current OAM implementation is based on IEEE 802.1ag standard, we will update this document as this standard evolves and new standards (802.1ah and ITU Y.1731) gain widespread support.

- 2 -

2. SCALABILITY The Provider’s network can contain several Maintenance Domains, with hundreds of Access Rings per domain. To size the domains, it is best to plan the number of MEPs that we want to monitor per Maintenance Domain or per Maintenance Association. We also need to consider the number of MDs and MAs that we want to use per VLAN based on the number of MEPs, the CCM interval used and the bandwidth of the slowest links. We also need to consider CPU utilization on the devices that process the MEPs, and the maximum number of MEPs that he switches can associate with. e.g. The following 2 scenarios will have similar traffic load on a VLAN: Domain 1 with 1GB/s on its slowest ring, 200 MEPs with CCM interval of 1-second Domain 2 with 1GB/s on its slowest ring, 2,000 MEPs with CCM interval of 10-seconds However, MDs/MAs must be sized to limit the number of CCMs that will be sent to the CPUs of the Access switches. Also, consider the limit on the number of MEPs that a switch can associate with.

3. TEST ENVIRONMENT - SOLUTIONS LAB The lab’s topology samples 2 rings of 3 OS-6850 switches, each ring connected to a 7450 switch. Ring #50 uses RSTP and ring #125 uses ERP. The PEs are set to be the RSTP root bridges. 2 Customer switches are connected to Ethernet-Services UNI ports, using TLS services offered by the service provider.

Operators Domain

Opr1Opr2

SVLAN 255 - MgtSVLAN 4001 - OAMSVLAN 1001 - Cust1SVLAN 1002 - Cust2

D

Management

D

D

R

A

1/23

Sw4 6850

1/23 1/24NNI NNI

UNI

Sw1 6850

1/24

1/23

UNI NNI

NNI

Sw2 6850

1/231/24

UNI

NNI NNI

Sw6 68501/23

1/24

NNI

NNI UNI

Sw5 6850

1/24NNI NNI

UNI

R

D

R

Ring 50

RSTP

Ring 125

ERP

RPL

1/1 1/1

1/3

1/31/3

00:E0:B1:A9:74:8C

00:E0:B1:AA:58:EBAA:59:03

00:E0:B1:A9:73:74

A9:73:8C

A9:73:8D

AA:59:04

84:be:60 84:be:61

00:E0:B1:84:BE:48

a0:80:ba a0:80:bb

00:E0:B1:A0:80:A2

a9:74:a4

a9:74:a5

Cust1-1

dotq

Cust1-2

dotq1/1

1/1

1/241/24

a9:73:76a0:88:bc

a0:88:d3a9:72:e5

00:E0:B1:A0:88:BA00:e0:b1:a9:72:cc

UNI1/3

1/3UNI

1/2/8

MIPL4

L4MIPL4

L5

L3

RPL node

L3MIP

L4MIP

L4MIP

L3MIP

L5

L4

L3

L2L2

1/2/2

PE17450

1/2/1

R

SAPSAP

SAP

Service PathPE27450

1/2/1

1/2/2

R

SAP

SAP

Level 2 (Operator NNI-NNI)

D=Opr1, A=Met1

MEP MEP Level 2 (Operator NNI-NNI)

D=Opr2, A=Met2

MEP MEP

Level 4 (Provider UNI-UNI)D=Pro4, A=Pro4-A1

MEP MEP

Level 3 (Provider UNI-UNI)

D=Pro3, A=Pro3-A1

MEP MEP

Domain=Cust1, Association=Cust1

Level 5 (Customer UNI-UNI)MEP MEP

Sw3 6850

1/24 1/23

UNI

NNI NNI

1/3

00:E0:B1:84:C4:12

84:C4:2A 84:c4:2b

L3 L3

Up MEP

Down MEP

MIP

RSTP role

Figure 1

L3MIP

L3MIP

- 3 -

4. SOLUTION STRATEGY OAM standard implementation in ring topology presents the following challenges: 1) CCM messages travel across the active paths and only verify the MEPs and MIPs along that path 2) In a normal operating status, where all of the network nodes and links are operational, there is a need to

monitor the status of the alternate paths e.g.: If we only had Level 4 MEP in node 1 (see Figure 2) in each ring, a linktrace will only show the MIPs in nodes 2, 3, and 4 in each ring. Also, if we monitor MEPs at Level 4, the entire secondary path can be unavailable (nodes 5-8 down) and the failure will not be detected. OAM standards are not “Ring Aware”, therefore it is easier to look at the proposed configuration as having hub and spoke topology with each ring split into 2 spokes. We design the rings so that each spoke will have roughly equal number of nodes, by controlling the ERP RPL link or adjusting the path cost to determine the location of the RSTP Alternate port. We configure a Level 4 Up MEP on the last node of the primary path (the path from the RPL node or the node that contains the Alternate RSTP port to the root). We then configure Level 3 Down MEPs on the last nodes of the primary and secondary paths.

VPLS

RSTPERP

Figure 2

OmniSwitch 6850-P24 US

B

CONSOLE

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

CLASS 1 LASER

PRODUCT

21 22 23 24

OK

PRI

PWR

BPS

L3MIP

2


B

CONSOLE

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

CLASS 1 LASER

PRODUCT

21 22 23 24

OK

PRI

PWR

BPS

L3MIP

3

4

L3MIP


B

CONSOLE

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

CLASS 1 LASER

PRODUCT

21 22 23 24

OK

PRI

PWR

BPS

L3

8

Secondary path


B

CONSOLE

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

CLASS 1 LASER

PRODUCT

21 22 23 24

OK

PRI

PWR

BPS

L4

RPL

L3

1


B

CONSOLE

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

CLASS 1 LASER

PRODUCT

21 22 23 24

OK

PRI

PWR

BPS

L3MIP

2


B

CONSOLE

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

CLASS 1 LASER

PRODUCT

21 22 23 24

OK

PRI

PWR

BPS

L3MIP

3


B

CONSOLE

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

CLASS 1 LASER

PRODUCT

21 22 23 24

OK

PRI

PWR

BPS

L3MIP

4OmniSwitch 6850-P24 US

B

CONSOLE

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

CLASS 1 LASER

PRODUCT

21 22 23 24

OK

PRI

PWR

BPS

L3MIP

5


B

CONSOLE

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

CLASS 1 LASER

PRODUCT

21 22 23 24

OK

PRI

PWR

BPS

L3MIP

6


B

CONSOLE

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

CLASS 1 LASER

PRODUCT

21 22 23 24

OK

PRI

PWR

BPS

L3MIP

7


B

CONSOLE

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

CLASS 1 LASER

PRODUCT

21 22 23 24

OK

PRI

PWR

BPS

L4A

L3

Primary path

1L3

Secondary path


B

CONSOLE

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

CLASS 1 LASER

PRODUCT

21 22 23 24

OK

PRI

PWR

BPS 8


B

CONSOLE

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

CLASS 1 LASER

PRODUCT

21 22 23 24

OK

PRI

PWR

BPS

L3MIP

7


B

CONSOLE

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

CLASS 1 LASER

PRODUCT

21 22 23 24

OK

PRI

PWR

BPS

L3MIP

6


B

CONSOLE

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

CLASS 1 LASER

PRODUCT

21 22 23 24

OK

PRI

PWR

BPS 5

L3MIP

R

L3MIP

L3MIP

L3MIP

L3MIP


B

CONSOLE

1 2 3 4 5 6 7 8 9 10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

CLASS 1 LASER

PRODUCT

21 22 23 24

OK

PRI

PWR

BPS

Primary path

With this configuration, we can have a tiered approach to monitoring the entire network. To check the overall status of the network: 1) Check connectivity to all Level 4 remote MEPs from any end node (1) 2) Check connectivity to all Level 3 remote MEPs from any end node (1)

- 4 -

- If we have a failure at Level 4, there is a high probability that customers are experiencing service interruption. - If we have a failure at Level 3, there is a connectivity issue somewhere in the network which may or may not cause service interruption (a single link down will not be an issue, a node down will only affect that node). - If all remote nodes are reachable, it is safe to say that no customer is experiencing any service interruption. If we discover a connectivity failure at Level 3 or 4 we can go to the affected ring and troubleshoot further. This is the expected status at the end node of the primary path (node 1) 1) All level 4 remote MEPs are reachable 2) All level 3 remote MEPs are reachable 3) ERP ring state is Idle or RSTP has an alternate path to the root bridge. - If 1 & 2 are OK but 3 failed (ERP is in protection state or the ALT port is now DESG) then the only issue is with the link between node 1 and node 8. - If 1 is OK but 2 & 3 failed (Level 3 MEPs are unreachable) then we need to identify which MEPs are unreachable. If the Level 3 MEP in node 8 is unreachable but all other MEPs are OK, then the issue is along the secondary path.

5. CONFIGURATION COMMANDS See Figure 1 for reference topology. The following configuration steps are listed in the order of execution, Ethernet OAM relies on the underlying link redundancy & loop prevention protocols (STP or ERP) and the appropriate VLANs to transport its messages. 1) Ethernet-Services The following Ethernet-Services commands apply to RSTP ring nodes (non-ERP): ethernet-service management-vlan 255 name "Mgt" ethernet-service svlan 1001 name Cust1 ethernet-service svlan 1002 name Cust2 ethernet-service svlan 1003 name Cust3 ethernet-service svlan 4001 name OAM1 ! ethernet-service svlan 255 nni 1/23-24 ethernet-service svlan 1001 nni 1/23-24 ethernet-service svlan 4001 nni 1/23-24 ethernet-service sap-profile Bronze shared ingress-bandwidth 0 priority fixed 1 ethernet-service sap-profile NetMgt shared ingress-bandwidth 0 priority fixed 7 ethernet-service service-name Cust1 svlan 1001 ethernet-service sap 101 service-name Cust1 ethernet-service sap 101 sap-profile Bronze ethernet-service sap 101 uni 1/1 ethernet-service sap 101 cvlan 10-20 ethernet-service sap 101 cvlan 1000 ethernet-service service-name OAM1 svlan 4001 ethernet-service sap 1001 service-name OAM1 ethernet-service sap 1001 sap-profile NetMgt ethernet-service sap 1001 uni 1/3 ethernet-service sap 1001 cvlan 4094 The following Ethernet-Services commands apply to ERP ring nodes: ethernet-service management-vlan 255 name "Mgt" ethernet-service svlan 1001 name "Cust1" ethernet-service svlan 1002 name "Cust2" ethernet-service svlan 1003 name "Cust3" ethernet-service svlan 4001 name "OAM1-ERP"

- 5 -

! ethernet-service svlan 255 nni 1/23-24 ethernet-service svlan 1001 nni 1/23-24 erp ethernet-service svlan 1002 nni 1/23-24 erp ethernet-service svlan 1003 nni 1/23-24 erp ethernet-service svlan 4001 nni 1/23-24 erp ethernet-service sap-profile Bronze shared ingress-bandwidth 0 priority fixed 1 ethernet-service sap-profile NetMgt shared ingress-bandwidth 0 priority fixed 7 ethernet-service service-name Cust1 svlan 1001 ethernet-service sap 101 service-name Cust1 ethernet-service sap 101 sap-profile Bronze ethernet-service sap 101 uni 1/1 ethernet-service sap 101 cvlan 10-20 ethernet-service sap 101 cvlan 1000 ethernet-service service-name OAM1 svlan 4001 ethernet-service sap 1001 service-name OAM1 ethernet-service sap 1001 sap-profile NetMgt ethernet-service sap 1001 uni 1/3 ethernet-service sap 1001 cvlan 4094 2) Spanning Tree Switch 1 in Ring 50 (RSTP ring) to ensure that port 1/24 is the ALT port: bridge mode flat bridge 1 1/24 path cost 100 All other switches in Ring 50: bridge mode flat 3) ERP Switch 6 in Ring 125 (ERP ring) to set the RPL node and RPL port: erp-ring 125 port1 1/23 port2 1/24 service-vlan 4001 level 3 erp-ring 125 rpl-node port 1/24 erp-ring 125 protected-vlan 1001-1003 erp-ring 125 wait-to-restore-timer 1 erp-ring 125 enable All other switches in Ring 125: erp-ring 125 port1 1/23 port2 1/24 service-vlan 4001 level 3 erp-ring 125 protected-vlan 1001-1003 erp-ring 125 enable 4) Ethernet OAM MEPs Switch 1 in Ring 50 and Switch 6 in Ring 125 are the “Level 3-4 End Nodes” and contain L3 & L4 MEPs: ethoam domain D1L4 format string level 4 ethoam association A1L4 format string domain D1L4 vlan 4001 ethoam association A1L4 domain D1L4 endpoint-list 1050 ethoam association A1L4 domain D1L4 endpoint-list 1125 ! ethoam endpoint 1050 domain D1L4 association A1L4 direction up port 1/3 ethoam endpoint 1050 domain D1L4 association A1L4 admin-state enable ethoam endpoint 1050 domain D1L4 association A1L4 ccm enable ! ethoam domain D1L3 format string level 3 ethoam association A1L3 format string domain D1L3 vlan 4001

- 6 -

ethoam association A1L3 domain D1L3 endpoint-list 1050 ethoam association A1L3 domain D1L3 endpoint-list 1125 ethoam association A1L3 domain D1L3 endpoint-list 2050 ethoam association A1L3 domain D1L3 endpoint-list 2125 ! ethoam endpoint 2050 domain D1L3 association A1L3 direction down port 1/23 ethoam endpoint 2050 domain D1L3 association A1L3 admin-state enable ethoam endpoint 2050 domain D1L3 association A1L3 ccm enable Switch 3 in Ring 50 and Switch 5 in Ring 125 are the “Level 3 End Nodes” and contain L3 MEPs: ethoam domain 3 format string level 3 ethoam domain D1L3 format string level 3 ethoam association A1L3 format string domain D1L3 vlan 4001 ethoam association A1L3 domain D1L3 endpoint-list 2050 ethoam association A1L3 domain D1L3 endpoint-list 2125 ethoam association A1L3 domain D1L3 endpoint-list 1050 ethoam association A1L3 domain D1L3 endpoint-list 1125 ethoam default-domain vlan 4001 level 4 mhf default ethoam endpoint 2050 domain D1L3 association A1L3 direction down port 1/23 ethoam endpoint 2050 domain D1L3 association A1L3 admin-state enable ethoam endpoint 2050 domain D1L3 association A1L3 ccm enable 5) Ethernet OAM MIPs The following commands create MIPs by default in the specified level, it is recommended that Level 4 MIPs be configured along the “Primary Path” and Level 3 MIPs along the “Secondary Path”. The level can be changed when troubleshooting connectivity issues. On intermediate switches (2, 4), default domains can be configured: ethoam default-domain vlan 4001 level 4 mhf default ! or ethoam default-domain vlan 4001 level 3 mhf default On end switches (1, 6, 3, 5), to enable MIPs creation, MHF must be configured for the appropriate MAs: ethoam association A1L4 domain D1L4 mhf default ! or ethoam association A1L3 domain D1L3 mhf default 6) Ethernet OAM CCM interval This command changes the default 10 second CCM interval: ethoam association A1L4 domain D1L4 ccm-interval interval1s 7) Ethernet OAM configured on the CPE switches Ethernet OAM is configured over a VLAN that tagged on the port connected to the UNI port on the provider’s ring: ethoam domain Cust1 format string level 5 ethoam association Cust1 format string domain Cust1 vlan 1000 ethoam association Cust1 domain Cust1 mhf default ethoam association Cust1 domain Cust1 ccm-interval interval1s ethoam association Cust1 domain Cust1 endpoint-list 1 ethoam association Cust1 domain Cust1 endpoint-list 2 ethoam endpoint 1 domain Cust1 association Cust1 direction up port 1/24 ethoam endpoint 1 domain Cust1 association Cust1 admin-state enable ethoam endpoint 1 domain Cust1 association Cust1 ccm enable

- 7 -

6. VERIFICATION COMMANDS • Show Ethernet OAM configured: Sw1-> show ethoam

System Configuration

Ethernet OAM system mac address: 00:E0:B1:A9:73:74,

Number of Maintenance Domains: 2

Maintenance Domain: D1L4

Maintenance Association: A1L4

Maintenance Domain: D1L3

Maintenance Association: A1L3

• Show Ethernet OAM domain configured: Sw1-> show ethoam domain D1L4

MD Attributes

MD-Level : level-4,

MD-MHFstatus : mhfNone

Maintenance Association : A1L4

Vlan : 4001,

MA-MHFstatus : mhfDefault,

CCM-interval : interval1s,

MEP-List(MEP-Id) : 1050 1125

Total number of MAs configured in this MD = 1

• Show Ethernet OAM association configured: Sw1-> show ethoam domain D1L4 association A1L4

Vlan : 4001,

MA-MHFstatus : mhfDefault,

CCM-interval : interval1s,

MEP-List(MEP-Id) : 1050 1125,

Legend: MEP-Id: * = Inactive Endpoint

MEP-ID Admin State Direction Mac-Address Port

--------+-----------+----------+-------------------+------

1050 up up 00:E0:B1:A9:73:74 1/3

Total number of MEPs configured in this MA = 1

- 8 -

• Show the CFM stack on a port: Sw1-> show ethoam cfmstack port 1/23 MEP-Id: 1050 Vlan-id: 4001, Direction: down, MAC-Address: 00:E0:B1:A9:73:8C, Maintenance Association: A1L3, Maintenance Domain: D1L3, MD-level: 3 Up MHF Configured: Vlan-id: 4001, Direction: up, MAC-Address: 00:E0:B1:A9:73:74, Maintenance Association: A1L4, Maintenance Domain: D1L4, MD-level: 4 Down MHF Configured: Vlan-id: 4001, Direction: down, MAC-Address: 00:E0:B1:A9:73:8C, Maintenance Association: A1L4, Maintenance Domain: D1L4, MD-level: 4

• Show the CFM stack on an UP-MEP port Sw1-> show ethoam cfmstack port 1/3

MEP-Id: 1050

Vlan-id: 4001,

Direction: up,

MAC-Address: 00:E0:B1:A9:73:74,

Maintenance Association: A1L4,

Maintenance Domain: D1L4,

MD-level: 4

• Check that remote endpoints (MEPs) in an association are reachable, e.g. the local endpoint is receiving CCMs from those points:

Sw1-> show ethoam remote-endpoint domain D1L4 association A1L4 endpoint 1050 Legends: PortStatusTlv: 1 = psBlocked, 2 = psUp, 3 = psNoTlv InterfaceStatusTlv: 1 = ifUp, 2 = ifDown, 3 = ifUnknown MEP-ID RMEP OkFailed Mac Address Port Status I/f Status Status Time Tlv Tlv ------+--------------+-------------+------------------+-------------+---------- 1125 RMEP_OK 779600 00:E0:B1:A9:74:8C 2 1 Total number of remote MEPs = 1 Sw1-> show ethoam remote-endpoint domain D1L3 association A1L3 endpoint 1050 Legends: PortStatusTlv: 1 = psBlocked, 2 = psUp, 3 = psNoTlv InterfaceStatusTlv: 1 = ifUp, 2 = ifDown, 3 = ifUnknown

- 9 -

MEP-ID RMEP OkFailed Mac Address Port Status I/f Status Status Time Tlv Tlv ------+--------------+-------------+------------------+-------------+---------- 1125 RMEP_OK 633600 00:E0:B1:A9:74:A4 2 1 2050 RMEP_OK 621300 00:E0:B1:84:C4:2A 2 1 2125 RMEP_OK 605500 00:E0:B1:84:BE:60 2 1 Total number of remote MEPs = 3 • ”Ping” a remote endpoint (MEP) using loopback messages: Sw1-> ethoam loopback target-endpoint 1125 source-endpoint 1050 domain D1L4 association A1L4 number 3 LBR Receive Successful : Sender Mac Address: 00:E0:B1:A9:74:8C LBR Receive Successful : Sender Mac Address: 00:E0:B1:A9:74:8C LBR Receive Successful : Sender Mac Address: 00:E0:B1:A9:74:8C • ”Ping” a remote intermediate point (MIP) using loopback messages: Sw1-> ethoam loopback target-macaddress 00:E0:B1:A0:80:A2 source-endpoint 1050 domain D1L4 association A1L4 number 3 LBR Receive Successful : Sender Mac Address: 00:E0:B1:A0:80:A2 LBR Receive Successful : Sender Mac Address: 00:E0:B1:A0:80:A2 LBR Receive Successful : Sender Mac Address: 00:E0:B1:A0:80:A2 • Execute a Linktrace at Level 4 (the results will be stored in memory with a transaction ID): Sw1-> ethoam linktrace target-endpoint 1125 source-endpoint 1050 domain D1L4 association A1L4 Transaction Id:9140 • View the Linktrace stored: Sw1-> show ethoam linktrace-reply domain D1L4 association A1L4 endpoint 1050 tran-id 9140 Ttl : 60, LTM Forwarded : no, Terminal MEP : yes, Last Egress Identifier : 00:00:00:E0:B1:A0:80:A2, Next Egress Identifier : 00:00:00:E0:B1:A9:74:8C, Relay Action : RLY_HIT, Ingress Action : ING_OK, Ingress Mac : 00:E0:B1:A9:74:A4, Egress Action : EGR_NONE, Egress Mac : 00:00:00:00:00:00 Ttl : 61, LTM Forwarded : yes, Terminal MEP : no, Last Egress Identifier : 00:00:00:E0:B1:AA:58:EB, Next Egress Identifier : 00:00:00:E0:B1:A0:80:A2, Relay Action : RLY_FDB, Ingress Action : ING_OK, Ingress Mac : 00:E0:B1:A0:80:BA, Egress Action : EGR_OK, Egress Mac : 00:E0:B1:A0:80:BB

- 10 -

Ttl : 62, LTM Forwarded : yes, Terminal MEP : no, Last Egress Identifier : 00:00:00:E0:B1:A9:73:74, Next Egress Identifier : 00:00:00:E0:B1:AA:58:EB, Relay Action : RLY_FDB, Ingress Action : ING_OK, Ingress Mac : 00:E0:B1:AA:59:04, Egress Action : EGR_OK, Egress Mac : 00:E0:B1:AA:59:03 Ttl : 63, LTM Forwarded : yes, Terminal MEP : no, Last Egress Identifier : 00:00:00:E0:B1:A9:73:74, Next Egress Identifier : 00:00:00:E0:B1:A9:73:74, Relay Action : RLY_FDB, Ingress Action : ING_NONE, Ingress Mac : 00:00:00:00:00:00, Egress Action : EGR_OK, Egress Mac : 00:E0:B1:A9:73:8C Verify the status of RSTP or ERP on the rings: Sw1-> show spantree ports active Brdge Port Oper Status Path Cost Role -----+------+------------+---------+------- 1 1/23 FORW 4 ROOT 1 1/24 BLK 100 ALT S6-> show erp Legends: * - Inactive Configuration WTR - Wait To Restore MEG - Maintenance Entity Group Ring Ring Ring Ring Serv WTR Guard MEG Ring Ring ID Port1 Port2 Status VLAN Timer Timer Level State Node (min) (csec) ----------+------+------+---------+----+-----+-----+-----+-----------+-------- 125 1/23 1/24 enabled 4001 1 50 3 idle rpl Total number of rings configured = 1

7. SNMP Alarms can be monitored by an SNMP application. The following configuration enable an SNMP monitoring station: Sw1-> show configuration snapshot snmp ! SNMP : user snmpRW password abcd1234 read-write snmp all snmp security no security snmp community map mode off snmp community map "snmpRW" user "snmpRW" on snmp station 10.255.215.114 162 "snmpRW" v3 enable Sw1-> show user

- 11 -

User name = snmpRW, Password expiration = None, Password allow to be modified date = None, Account lockout = None, Password bad attempts = 0, Read Only for domains = None, Read/Write for domains = All , Snmp allowed = YES, Snmp authentication = NONE, Snmp encryption = NONE The Fault-Alarm time can be set between 250 centiseconds (2.5 seconds) to 1000 centiseconds (10 seconds), 2.5 seconds is the default. Command change the timer to 5 seconds: ethoam fault-reset-time 500 endpoint 1050 domain D1L4 association A1L4 The following example shows an SNMP trap generated by a switch after missing CCMs for 2.5 seconds, as seen by the SNMP station (OmniVista):

(Name) dot1agCfmFaultAlarm, (Synopsis) MEP: 00 e0 b1 a9 73 8c has lost contact with one or more MEPs. , (Agent) /10.255.215.191, (Agent Name) OAM-Sw1, (Date/Time) Fri Aug 28 09:47:52 PDT 2009, (Severity) Normal, (Acknowledged) false, Synopsis: MEP: 00 e0 b1 a9 73 8c has lost contact with one or more MEPs. Description: A MEP has lost contact with one or more MEPs. A notification

(fault alarm) is sent to the management entity with the OID of the MEP that has detected the fault. Whenever a MEP loses contact with one or more other MEPs, it may or may not generate a Fault Alarm to warn the system administrator of the problem, as controlled by the MEP Fault Notification Generator State Machine and associated Managed Objects. Only the highest-priority defect, as shown in Table 20-1, is reported in the Fault Alarm.

Name: dot1agCfmFaultAlarm Date/Time: Aug 28, 2009 9:47:52 AM

Severity: Normal

Agent: 10.255.215.191 Agent Name:

OAM-Sw1 Up Time:

1 day, 15 hours, 15 minutes, 4 seconds.

Source: 10.255.215.191 Trap OID: .1.0.8802.1.1.3.0.1 dot1agCfmMepMacAddress 00 e0 b1 a9 73

8c MAC address of the MEP.

dot1agCfmMepHighestPrDefect defRemoteCCM The highest priority defect that has been present since the MEPs Fault Notification Generator State Machine was last in the FNG_RESET state.

- 12 -

8. CONFIGURATION NOTES See Figure 1 above

• Current implementation uses AoS version 6.3.4.475.R01 on OmniSwitch 6xxx/9xxx provider’s access nodes and TiMOS 7.0R3 on 7450/7750 providers headend or PE nodes.

• At current release, do not configure any MIPs on the PEs in the same VLAN and same level as the access switches. The MIPs will not respond to linktraces and will block LTMs from crossing those interfaces to other rings.

• In ERP rings, if ring topology consistency is desired, make sure that ALL SVLANs are protected by ERP and then disable STP on the NNI ports. It is possible however to maintain 2 different topologies, 1 for ERP protected VLANs and 1 for RSTP enabled VLANs.

• The CPE equipment may be managed by the customer or service provider and can be useful for troubleshooting end to end connectivity by configuring MAs at level 5+.

• STP may be local to each ring or span a number of rings across PEs. In this example, we extended STP across the core network, spanning the 2 rings, as we used only 1 SAP on PE1 to connect the entire network to the NOC.

8.1 7750 configuration

This mVPLS is created to participate in STP as root bridge in the RSTP rings, the SAPs are untagged in the access ports that connect to the access rings: PE1>config>service# info

vpls 999 customer 3 m-vpls create

stp

priority 4096

mode pmstp

no shutdown

exit

sap 1/2/1:0 create

exit

sap 1/2/2:0 create

exit

no shutdown

exit

This VPLS is created to connect Management VLANs to the NOC. 2 SAPs connect to the rings and 1 sap connects to the VLAN providing access to the NOC: PE1>config>service# info

vpls 255 customer 255 create

stp

shutdown

exit

- 13 -

sap 1/2/1:255 create

exit


exit

sap 1/2/8:0 create

exit

spoke-sdp 3:255 create

exit

no shutdown

exit

VPLS service to transports the OAM messages of the upper levels Maintenance Domains: PE1>config>service# info


stp

shutdown

exit


exit


exit

mesh-sdp 1:4001 create

exit

no shutdown

exit

Ethernet CFM global configuration: PE1>config>eth-cfm# info

domain 2 name "Opr2" level 2

association 2 format string name "A2L2"

bridge-identifier 4000

mhf-creation default

exit

ccm-interval 1

remote-mepid 2

exit

exit

VPLS service created to transports the OAM messages of the operator levels Maintenance Domains, the VPLS service ID matches the bridge-identifier configured above: PE1>config>service#

- 14 -


stp

shutdown

exit

mesh-sdp 1:4000 create

eth-cfm

mep 1 domain 2 association 2 direction down

ccm-enable

no shutdown

exit

exit

exit

no shutdown

exit

8.2 6850 configuration

=========================================================================

Service Provider Switch #1 (see Figure 1) =========================================================================

Sw1-> show configuration snapshot

!====================================

! section omitted

!====================================

vlan 1 enable name "VLAN 1"

ethernet-service management-vlan 255 name "Mgt"

ethernet-service svlan 1001 name "Cust1"



ethernet-service svlan 4001 name "OAM1"

!====================================

! section omitted

!====================================

! QOS :

qos port 1/1 default classification 802.1p




qos apply

- 15 -

!====================================

! section omitted

!====================================

! Interface :

interfaces 1/3 alias "UpMEP"

!====================================

! section omitted

!====================================

! Spanning tree :

bridge mode flat

bridge 1 1/24 path cost 100

!====================================

! section omitted

!====================================

! VLAN STACKING:

ethernet-service svlan 255 nni 1/23-24



ethernet-service sap-profile "Bronze" shared ingress-bandwidth 0 priority fixed 1

ethernet-service sap-profile "NetMgt" shared ingress-bandwidth 0 priority fixed 7

ethernet-service service-name "Cust1" svlan 1001

ethernet-service sap 101 service-name "Cust1"

ethernet-service sap 101 sap-profile "Bronze"

ethernet-service sap 101 uni 1/1

ethernet-service sap 101 cvlan 10-20

ethernet-service sap 101 cvlan 1000

ethernet-service service-name "OAM1" svlan 4001

ethernet-service sap 1001 service-name "OAM1"

ethernet-service sap 1001 sap-profile "NetMgt"



ethernet-service nni 1/23 tpid 0x8100


! Ethernet-OAM :

ethoam domain D1L4 format string level 4


ethoam association A1L3 format string domain D1L3 vlan 4001

ethoam association A1L3 domain D1L3 endpoint-list 1050




- 16 -


ethoam association A1L4 domain D1L4 mhf default

ethoam association A1L4 domain D1L4 ccm-interval interval1s



ethoam endpoint 1050 domain D1L4 association A1L4 direction up port 1/3

ethoam endpoint 1050 domain D1L4 association A1L4 admin-state enable

ethoam endpoint 1050 domain D1L4 association A1L4 ccm enable

ethoam endpoint 1050 domain D1L3 association A1L3 direction down port 1/23



! ERP :

=========================================================================

Service Provider Switch #2 =========================================================================

S2-> show configuration snapshot

!====================================

! section omitted

!====================================

! VLAN :







!====================================

! section omitted

!====================================

bridge mode flat

!====================================

! section omitted

!====================================

! VLAN STACKING:







- 17 -






ethernet-service sap 101 cvlan all













! Ethernet-OAM :

ethoam default-domain vlan 4001 level 4 mhf default

! ERP :

=========================================================================


S3-> show configuration snapshot

!====================================

! section omitted

!====================================







!====================================

! section omitted

!====================================

! Spanning tree :

bridge mode flat

- 18 -

!====================================

! section omitted

!====================================

! VLAN STACKING:















! Ethernet-OAM :

ethoam domain 3 format string level 3











! ERP :

=========================================================================



!====================================

! section omitted

!====================================

! VLAN :


- 19 -





ethernet-service svlan 4001 name "OAM1-ERP"

!====================================

! section omitted

!====================================

! Spanning tree :

bridge mode flat

bridge 1 1/23 disable


!====================================

! section omitted

!====================================

! VLAN STACKING:

ethernet-service svlan 255 nni 1/23-24 erp














! Ethernet-OAM :


! ERP :

erp-ring 125 port1 1/23 port2 1/24 service-vlan 4001 level 3

erp-ring 125 protected-vlan 1001-1003

erp-ring 125 enable

=========================================================================



- 20 -

!====================================

! section omitted

!====================================

! VLAN :







!====================================

! section omitted

!====================================

! Spanning tree :

bridge mode flat



!====================================

! section omitted

!====================================

! VLAN STACKING:




















! Ethernet-OAM :

- 21 -











! ERP :



erp-ring 125 enable

=========================================================================


6-> show configuration snapshot

!====================================

! section omitted

!====================================

! VLAN :







!====================================

! section omitted

!====================================

! Spanning tree :

bridge mode flat



!====================================

! section omitted

!====================================

! VLAN STACKING:


- 22 -




















! Ethernet-OAM :









ethoam association A1L4 domain D1L4 mhf default

ethoam association A1L4 domain D1L4 ccm-interval interval1s






ethoam endpoint 1125 domain D1L4 association A1L4 direction up port 1/3



! ERP :


erp-ring 125 rpl-node port 1/24


- 23 -

erp-ring 125 wait-to-restore-timer 1

erp-ring 125 enable

=========================================================================

CPE Switch #1 =========================================================================

Cust1-1-> show configuration snapshot ! Stack Manager : ! Chassis : system name Cust1-1 ! Configuration: ! VLAN : vlan 1 enable name "VLAN 1" vlan 10 enable name "VLAN 10" vlan 11 enable name "VLAN 11" vlan 12 enable name "VLAN 12" vlan 13 enable name "VLAN 13" vlan 14 enable name "VLAN 14" vlan 15 enable name "VLAN 15" vlan 16 enable name "VLAN 16" vlan 17 enable name "VLAN 17" vlan 18 enable name "VLAN 18" vlan 19 enable name "VLAN 19" vlan 20 enable name "VLAN 20" vlan 1000 enable name "VLAN 1000" vlan 1000 port default 1/24 ! VLAN SL: ! IP : ip service all ip interface "10" address 192.168.10.1 mask 255.255.255.0 vlan 10 ifindex 2 ip interface "11" address 192.168.11.1 mask 255.255.255.0 vlan 11 ifindex 3 ip interface "12" address 192.168.12.1 mask 255.255.255.0 vlan 12 ifindex 4 ip interface "1000" address 10.10.10.1 mask 255.255.255.0 vlan 1000 ifindex 5 !====================================

! section omitted

!====================================

! 802.1Q : vlan 10 802.1q 1/1 "TAG PORT 1/1 VLAN 10" vlan 11 802.1q 1/1 "TAG PORT 1/1 VLAN 11" vlan 12 802.1q 1/1 "TAG PORT 1/1 VLAN 12" vlan 13 802.1q 1/1 "TAG PORT 1/1 VLAN 13" vlan 14 802.1q 1/1 "TAG PORT 1/1 VLAN 14" vlan 15 802.1q 1/1 "TAG PORT 1/1 VLAN 15" vlan 16 802.1q 1/1 "TAG PORT 1/1 VLAN 16" vlan 17 802.1q 1/1 "TAG PORT 1/1 VLAN 17" vlan 18 802.1q 1/1 "TAG PORT 1/1 VLAN 18" vlan 19 802.1q 1/1 "TAG PORT 1/1 VLAN 19" vlan 20 802.1q 1/1 "TAG PORT 1/1 VLAN 20" vlan 1000 802.1q 1/1 "TAG PORT 1/1 VLAN 1000" ! Spanning tree : bridge mode 1x1 !====================================

! section omitted

!====================================

- 24 -

! VLAN STACKING: ! Ethernet-OAM : ethoam domain Cust1 format string level 5 ethoam association Cust1 format string domain Cust1 vlan 1000 ethoam association Cust1 domain Cust1 mhf default ethoam association Cust1 domain Cust1 ccm-interval interval1s ethoam association Cust1 domain Cust1 endpoint-list 1 ethoam association Cust1 domain Cust1 endpoint-list 2 ethoam endpoint 1 domain Cust1 association Cust1 direction up port 1/24 ethoam endpoint 1 domain Cust1 association Cust1 admin-state enable ethoam endpoint 1 domain Cust1 association Cust1 ccm enable ! ERP :

- 25 -

Documents

Alcatel-Lucentalcatel-lucent.de/enterprise/ipush/ipush79/EthernetOAM... · 2010-03-23 · CONFIGURATION COMMANDS ... This document describes the use of Ethernet OAM to monitor a Service