CHAPTER 6-1 Connected Utilities - Field Area Network 2.0 Design and Implementation Guide 6 Service Deployment for SAToP with Alstom Relays This chapter includes the following major topics: • Alstom, page 6-1 • SAToP Circuit Overview, page 6-4 • Using IOS CLI for Provisioning Relay Connectivity over SAToP, page 6-5 • Using IOS CLI to Validate Relay Connectivity over SAToP, page 6-7 • Using NMS for Provisioning Relay Connectivity over SAToP, page 6-10 Alstom Alstom P545 Line Differential Relays Overview Figure 6-1 illustrates the components of the Alstom Line Differential Relay solution.
Transcript
Design and Implementation Guide
C H A P T E R 6
Service Deployment for SAToP with Alstom Relays
This chapter includes the following major topics:
• Alstom, page 6-1
• SAToP Circuit Overview, page 6-4
• Using IOS CLI for Provisioning Relay Connectivity over SAToP, page 6-5
• Using IOS CLI to Validate Relay Connectivity over SAToP, page 6-7
• Using NMS for Provisioning Relay Connectivity over SAToP, page 6-10
Alstom
Alstom P545 Line Differential Relays OverviewFigure 6-1 illustrates the components of the Alstom Line Differential Relay solution.
6-1Connected Utilities - Field Area Network 2.0
Chapter 6 Service Deployment for SAToP with Alstom Relays Alstom
Figure 6-1 Alstom P545 Line Differential Relays
Alstom Relay SettingsFigure 6-2 and Figure 6-3 illustrate the settings applied to the Alstom Line Differential Relay solution.
Figure 6-2 Alstom Relay Settings—1
6-2Connected Utilities - Field Area Network 2.0
Design and Implementation Guide
Chapter 6 Service Deployment for SAToP with Alstom Relays Alstom
Figure 6-3 Alstom Relay Settings—2
Alstom Relay Status with GPS AssistFigure 6-4 illustrates the behavior of the Alstom Line Differential Relay solution when GPS is available.
Figure 6-4 Alstom Relay Status with GPS Assist
Alstom E1/T1 ConvertersFigure 6-5 illustrates the various converters available for the Alstom Line Differential Relay solution.
6-3Connected Utilities - Field Area Network 2.0
Design and Implementation Guide
Chapter 6 Service Deployment for SAToP with Alstom Relays SAToP Circuit Overview
Figure 6-5 Alstom E1/T1 Converters
Special ConsiderationsThe TDM circuit emulation pseudowire employs a de-jitter buffer to compensate for the network Packet Delay Variation (PDV).
Note The ASR900 de-jitter buffer is configurable between 1-500msec. There is a trade-off between de-jitter buffer and latency. A large de- jitter buffer will impact the end-to-end latency of the protection scheme, and therefore its size must be optimally tuned to smooth out network PDV to maintain TDM line synchronization and not more.
SAToP Circuit Overview
Alstom Relay Clear Channel E1 ProtectionThe data rate from Alstom relays over the optical interface is 64kbps. Alstom Serial Converters convert the 64kbps optical signal into a 2 Mbps E1 clear-channel signal.
ASR900 substation routers enable circuit emulation for transporting E1 relay telegrams to the remote end using a SAToP pseudowire over MPLS/IP. The SAToP pseudowire de-jitter buffer is configured at 1msec. See Figure 6-6.
Figure 6-6 SAToP Circuit Overview
ASR900 substation routers are frequency synchronized for TDM circuit emulation using SyncE. The pseudowire traffic is carried over MPLS-TE tunnels using explicit routing or MPLS-TP tunnels to ensure symmetrical forward and return paths.
TE-FRR protection is used to achieve 50ms recovery against failures in the transport network.
3750
13
AlstomDifferential
Relay-1
AlstomSerial
Converter
OpticalInterface
64kbps
Clear-Channel E1InterfaceCEM 0/5/3
E1 2MbpsCisco
ASR-903
Structured Circuit Emulation VC 6660001
SAToP Pseudowire
CiscoASR-903
AlstomDifferential
Relay-2
OpticalInterface
64kbps
AlstomSerial
Converter
Clear-Channel E1InterfaceCEM 0/5/3
E1 2Mbps
6-4Connected Utilities - Field Area Network 2.0
Design and Implementation Guide
Chapter 6 Service Deployment for SAToP with Alstom Relays Using IOS CLI for Provisioning Relay Connectivity over SAToP
Alstom LatencyThe primary MPLS label switched path traverses a direct link between the two ASR900s.The backup MPLS label switched path traverses 5 ASR900 routers. Latency delta between 1-hop and 5-hops is only 83usec due to ASR900 centralized architecture and Cisco low-latency ASIC.
Note Latency numbers reflected here do not account for distances between substations. Add 1msec propagation delay (speed of light through fiber optic) for every 200km between substations.
Using IOS CLI for Provisioning Relay Connectivity over SAToP
MPLS-TP Tunnel EndpointsConfigure MPLS-TP Tunnel Endpoints. The following is a sample endpoint configuration on the ASR902-W2413:
Chapter 6 Service Deployment for SAToP with Alstom Relays Using IOS CLI for Provisioning Relay Connectivity over SAToP
MPLS-TP Tunnel MidpointsConfigure MPLS-TP LSP at midpoint routers. In the bottom ring in the system topology, the following router midpoints need configuration:
Chapter 6 Service Deployment for SAToP with Alstom Relays Using IOS CLI to Validate Relay Connectivity over SAToP
forward-alarm ais forward-alarm rai cem-group 0 unframed !
SAToP E1 CEM InterfaceThe following is a sample SAToP E1 circuit emulation (CEM) interface:
interface CEM0/3/3 no ip address load-interval 30 cem 0
Pseudowire The following is a sample SAToP E1 circuit emulation (CEM) pseudowire configuration:
interface CEM0/3/3 cem 0 service-policy input PMAP-UNI-TPR-IN cem class TPR-CEM-SATOPxconnect 100.25.4.1 6660001 encapsulation mpls pw-class SAToPSN !
Using IOS CLI to Validate Relay Connectivity over SAToP
Validate MPLS PW Circuit EmulationThe following verifications are made when the short path (MPLS-TP working path) is ACTIVE:
ASR903-W2504#sho xconnect allLegend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State UP=Up DN=Down AD=Admin Down IA=Inactive SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2 ------+---------------------------------+--+---------------------------------+-- UP pri ac CE0/5/3:0(SATOP E1) UP mpls 100.24.13.1:10003 UP
ASR903-W2504#sh mpls l2 vc 10003 det Local interface: CE0/5/3 up, line protocol up, SATOP E1 0 up Destination address: 100.24.13.1, VC ID: 10003, VC status: up Output interface: Tp0, imposed label stack {133 17} Preferred path: Tunnel-tp0, active Default path: ready Next hop: point2point Create time: 6d18h, last status change time: 5d21h Last label FSM state change time: 5d21h Signaling protocol: LDP, peer 100.24.13.1:0 up Targeted Hello: 100.25.4.1(LDP Id) -> 100.24.13.1, LDP is UP Graceful restart: configured and enabled Non stop routing: not configured and not enabled Status TLV support (local/remote) : enabled/supported
6-7Connected Utilities - Field Area Network 2.0
Design and Implementation Guide
Chapter 6 Service Deployment for SAToP with Alstom Relays Using IOS CLI to Validate Relay Connectivity over SAToP
LDP route watch : enabled Label/status state machine : established, LruRru Last local dataplane status rcvd: No fault Last BFD dataplane status rcvd: Not sent Last BFD peer monitor status rcvd: No fault Last local AC circuit status rcvd: No fault Last local AC circuit status sent: No fault Last local PW i/f circ status rcvd: No fault Last local LDP TLV status sent: No fault Last remote LDP TLV status rcvd: No fault Last remote LDP ADJ status rcvd: No fault MPLS VC labels: local 36, remote 17 Group ID: local 0, remote 0 MTU: local 0, remote 0 Remote interface description: Sequencing: receive disabled, send disabled Control Word: On SSO Descriptor: 100.24.13.1/10003, local label: 36 Dataplane: SSM segment/switch IDs: 4113/20492 (used), PWID: 5 VC statistics: transit packet totals: receive 2831480767, send 2830620632transit byte totals: receive 175552155546, send 152853514352 transit packet drops: receive 0, seq error 0, send 0
ASR903-W2504#ping mpls pseudowire 100.24.13.1 10003 Sending 5, 72-byte MPLS Echos to 100.24.13.1, timeout is 2 seconds, send interval is 0 msec:
Chapter 6 Service Deployment for SAToP with Alstom Relays Using IOS CLI to Validate Relay Connectivity over SAToP
'P' - no rx intf label prot, 'p' - premature termination of LSP, 'R' - transit router, 'I' - unknown upstream index, 'l' - Label switched with FEC change, 'd' - see DDMAP for return code, 'X' - unknown return code, 'x' - return code 0
Type escape sequence to abort. 0 10.24.13.1 MRU 1500 [Labels: explicit-null Exp: 0] ! 1 10.24.13.0 2 ms
The following verifications are made when the long path (MPLS-TP protect path) is ACTIVE:
ASR903-W2504#sh xconnect allLegend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State UP=Up DN=Down AD=Admin Down IA=Inactive SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2 ------+---------------------------------+--+---------------------------------+-- UP pri ac CE0/5/3:0(SATOP E1) UP mpls 100.24.13.1:10003 UP
ASR903-W2504#sho mpls l2 vc 10003 det Local interface: CE0/5/3 up, line protocol up, SATOP E1 0 up Destination address: 100.24.13.1, VC ID: 10003, VC status: up Output interface: Tp0, imposed label stack {108 17} Preferred path: Tunnel-tp0, active Default path: ready Next hop: point2point Create time: 6d18h, last status change time: 5d21h Last label FSM state change time: 5d21h Signaling protocol: LDP, peer 100.24.13.1:0 up Targeted Hello: 100.25.4.1(LDP Id) -> 100.24.13.1, LDP is UP Graceful restart: configured and enabled Non stop routing: not configured and not enabled Status TLV support (local/remote) : enabled/supported LDP route watch : enabled Label/status state machine : established, LruRru Last local dataplane status rcvd: No fault Last BFD dataplane status rcvd: Not sent Last BFD peer monitor status rcvd: No fault Last local AC circuit status rcvd: No fault Last local AC circuit status sent: No fault Last local PW i/f circ status rcvd: No fault Last local LDP TLV status sent: No fault Last remote LDP TLV status rcvd: No fault Last remote LDP ADJ status rcvd: No fault MPLS VC labels: local 36, remote 17 Group ID: local 0, remote 0 MTU: local 0, remote 0 Remote interface description: Sequencing: receive disabled, send disabled Control Word: On SSO Descriptor: 100.24.13.1/10003, local label: 36 Dataplane: SSM segment/switch IDs: 4113/20492 (used), PWID: 5 VC statistics: transit packet totals: receive 2832426862, send 2831566806 transit byte totals: receive 175610813436, send 152904607748 transit packet drops: receive 0, seq error 0, send 0
ASR903-W2504#ping mpls pseudowire 100.24.13.1 10003 Sending 5, 72-byte MPLS Echos to 100.24.13.1, timeout is 2 seconds, send interval is 0 msec:
Type escape sequence to abort. 0 10.25.3.1 MRU 1500 [Labels: 36 Exp: 0] L 1 10.25.3.0 MRU 1500 [Labels: 39 Exp: 0] 3 ms L 2 10.25.2.0 MRU 1500 [Labels: 18 Exp: 0] 3 ms L 3 10.24.15.0 MRU 1500 [Labels: 42 Exp: 0] 4 ms L 4 10.24.14.0 MRU 1500 [Labels: explicit-null Exp: 0] 3 ms ! 5 10.24.13.2 3 ms
Using NMS for Provisioning Relay Connectivity over SAToP
Configuration Collection in Cisco Prime ProvisioningComplete the following steps to run a configuration collection on all routers through which an MPLS-TP tunnel will traverse (all midpoints and endpoints) in Cisco Prime Provisioning:
Step 1 Launch Prime Provisioning from Cisco Prime Central’s Fulfill – Service Request Manager menu, as shown in Figure 6-7.
Figure 6-7 Launch Cisco Prime Provisioning
Step 2 Select Devices from Inventory - Physical Inventory – Devices, as shown in Figure 6-8.
6-10Connected Utilities - Field Area Network 2.0
Design and Implementation Guide
Chapter 6 Service Deployment for SAToP with Alstom Relays Using NMS for Provisioning Relay Connectivity over SAToP
Figure 6-8 Cisco Prime Provisioning Select Devices
Step 3 Select Device(s) and go to Actions - Config Collect, as shown in Figure 6-9.
Figure 6-9 Cisco Prime Provisioning Configuration Collection
Step 4 Once the configuration collection is scheduled, you should receive a Success message, as shown in Figure 6-10.
Figure 6-10 Cisco Prime Provisioning—Configuration Collection Success
MPLS-TP Discovery in Cisco Prime ProvisioningIn Cisco Prime Provisioning, complete the following steps to run an MPLS-TP discovery on all routers through which an MPLS-TP tunnel will traverse (all midpoints and endpoints):
Step 1 Launch Prime Provisioning from the Fulfill – Service Request Manager menus in Prime Central, as shown in Figure 6-11.
6-11Connected Utilities - Field Area Network 2.0
Design and Implementation Guide
Chapter 6 Service Deployment for SAToP with Alstom Relays Using NMS for Provisioning Relay Connectivity over SAToP
Figure 6-11 Launch Cisco Prome Provisioning
Step 2 Select Devices from Inventory - Physical Inventory – Devices, as shown in Figure 6-12.
Figure 6-12 Cisco Prime Provisioning Devices
Step 3 Select Device(s) and go to Actions - MPLS-TP Discovery, as shown in Figure 6-13.
Figure 6-13 Cisco Prime Provisioning MPLS-TP Discovery
Confirm Status of Last TaskAfter running a configuration collection and MPLS-TP discovery, you can confirm the status of these or any other tasks by completing the following steps:
Step 1 Select Operate – Tasks - Task Logs, as shown in Figure 6-14.
6-12Connected Utilities - Field Area Network 2.0
Design and Implementation Guide
Chapter 6 Service Deployment for SAToP with Alstom Relays Using NMS for Provisioning Relay Connectivity over SAToP
Figure 6-14 Cisco Prime Provisioning Task Logs
Step 2 Look under the last column for status of the operation, as shown in Figure 6-15.
Figure 6-15 Cisco Prime Provisioning Task Status
Create a CEM CLASS with Dejitter Buffer of 2 and 46 Byte PayloadTo create a CEM CLASS with dejitter buffer of 2 and 46 byte payload, complete the following steps:
Step 1 Select Inventory - Logical Inventory - CEM Class, as shown in Figure 6-16.
Figure 6-16 Cisco Prime Provisioning CEM Class
Step 2 Click the Create button and the new CEM class window opens up, as shown in Figure 6-17.
6-13Connected Utilities - Field Area Network 2.0
Design and Implementation Guide
Chapter 6 Service Deployment for SAToP with Alstom Relays Using NMS for Provisioning Relay Connectivity over SAToP
Figure 6-17 Cisco Prime Provisioning New CEM Class from SAToP
Step 3 Click Save when finished.
Create a TP Tunnel InterfaceTo create a TP Tunnel interface, compete the following steps:
Step 1 Starting from Cisco Prime Provisioning, select Operate – Service Requests – Create Service Request, as shown in Figure 6-18.
Figure 6-18 Cisco Prime Provisioning Create a Service Request
You can also start from Cisco Prime Network Vision, by selecting the TP tunnel endpoints, right-clicking, and choosing Fulfill – Create Service, as shown in Figure 6-19.
6-14Connected Utilities - Field Area Network 2.0
Design and Implementation Guide
Chapter 6 Service Deployment for SAToP with Alstom Relays Using NMS for Provisioning Relay Connectivity over SAToP
Figure 6-19 Prime Network Create a Service Request
Step 2 Select the policy TP Tunnel (MPLS-TP policy type), as shown in Figure 6-20.
Figure 6-20 TP Tunnel Service Request—1
Step 3 Enter the service description and click Next, as shown in Figure 6-21.
6-15Connected Utilities - Field Area Network 2.0
Design and Implementation Guide
Chapter 6 Service Deployment for SAToP with Alstom Relays Using NMS for Provisioning Relay Connectivity over SAToP
Figure 6-21 TP Tunnel Service Request—2
Step 4 Enter relevant information around the tunnel characteristics and click Next, as shown in Figure 6-22.
Figure 6-22 TP Tunnel Service Request—3
Step 5 Enter relevant information around the tunnel end points and click Next, as shown in Figure 6-23.
Figure 6-23 TP Tunnel Service Request—4
6-16Connected Utilities - Field Area Network 2.0
Design and Implementation Guide
Chapter 6 Service Deployment for SAToP with Alstom Relays Using NMS for Provisioning Relay Connectivity over SAToP
Step 6 Review routing information about the calculated path, as shown in Figure 6-24.
Figure 6-24 TP Tunnel Service Request—5
Step 7 Review routing information about the working path, as shown in Figure 6-25.
Figure 6-25 TP Tunnel Service Request—6
Step 8 Review routing information about the protect path and click Finish, as shown in Figure 6-26.
6-17Connected Utilities - Field Area Network 2.0
Design and Implementation Guide
Chapter 6 Service Deployment for SAToP with Alstom Relays Using NMS for Provisioning Relay Connectivity over SAToP
Figure 6-26 TP Tunnel Service Request—7
Step 9 An MPLS-TP tunnel endpoint configuration preview is shown in Figure 6-27.
Figure 6-27 TP Tunnel Service Request—8
Step 10 An MPLS-TP tunnel midpoint configuration preview is shown in Figure 6-28.
6-18Connected Utilities - Field Area Network 2.0
Design and Implementation Guide
Chapter 6 Service Deployment for SAToP with Alstom Relays Using NMS for Provisioning Relay Connectivity over SAToP
Figure 6-28 TP Tunnel Service Request—9
Step 11 Once you deploy the service, check the status to confirm deployment by selecting Operate – Service Requests – Service Request Manager, as shown in Figure 6-29.
Figure 6-29 Cisco Prime Provisioning Service Request Manager
Note The MPLS-TP tunnel number for future use. In the screenshots above, the TP tunnel number is 0.
6-19Connected Utilities - Field Area Network 2.0
Design and Implementation Guide
Chapter 6 Service Deployment for SAToP with Alstom Relays Using NMS for Provisioning Relay Connectivity over SAToP
Create a Pseudowire Class that Uses the TP Tunnel (Tunnel-tp0)To create a pseudowire class that uses the TP tunnel (Tunnel-tp0), complete the following steps:
Step 1 Select Inventory - Logical Inventory - Pseudowire Class, as shown in Figure 6-30.
Figure 6-30 Cisco Prime Provisioning Pseudowire Classes
Step 2 Fill in the information, as shown in Figure 6-31.
Figure 6-31 Cisco Prime Provisioning Pseudowire Class Creation
Create a Teleprotection PolicyTo create a teleprotection policy, complete the following steps:
Step 1 Select Service Design - Policies - Policy Manager, as shown in Figure 6-32.
6-20Connected Utilities - Field Area Network 2.0
Design and Implementation Guide
Chapter 6 Service Deployment for SAToP with Alstom Relays Using NMS for Provisioning Relay Connectivity over SAToP
Figure 6-32 Cisco Prime Provisioning Policy Manager
Step 2 Fill in basic service information, including the name of the policy, as shown in Figure 6-33.
Figure 6-33 Cisco Prime Provisioning New Policy—1
Step 3 Select service options, as shown in Figure 6-34.
Note The Alstom relays use SAToP over E1.
Figure 6-34 Cisco Prime Provisioning New Policy—2
Step 4 Select service attributes, as shown in Figure 6-35.
Figure 6-35 Cisco Prime Provisioning New Policy—3
Step 5 Fill in pseudowire and CEM details and select a pseudowire class, as shown in Figure 6-36.
6-21Connected Utilities - Field Area Network 2.0
Design and Implementation Guide
Chapter 6 Service Deployment for SAToP with Alstom Relays Using NMS for Provisioning Relay Connectivity over SAToP
Figure 6-36 Cisco Prime Provisioning New Policy—4
Step 6 Enable and select a CEM class, as shown in Figure 6-37.
Figure 6-37 Cisco Prime Provisioning New Policy—5
Commissioning the Service on a New E1 CEM InterfaceTo create an E1 interface using correct timeslots and an EVC Service that applies the CEM Class and Pseudowire Class, complete the following steps:
Step 1 Launch Topology from Prime Vision. Select the devices for which to create a service, as shown in Figure 6-38.
6-22Connected Utilities - Field Area Network 2.0
Design and Implementation Guide
Chapter 6 Service Deployment for SAToP with Alstom Relays Using NMS for Provisioning Relay Connectivity over SAToP
Figure 6-38 Cisco Prime Network Select Devices for Service Fulfillment
Step 2 Once Cisco Prime Provisioning is launched, select the Teleprotection_TP_SAToP (EVC) service request. Select CEM Class and interfaces, as shown in Figure 6-39.
Figure 6-39 Cisco Prime Provisioning New Teleprotection_TP_SAToP Service Request—1
Step 3 Edit the Link Attributes. Enter a CEM group ID, clock source internal, timeslots 1, and select pseudowire class, as shown in Figure 6-40.
6-23Connected Utilities - Field Area Network 2.0
Design and Implementation Guide
Chapter 6 Service Deployment for SAToP with Alstom Relays Using NMS for Provisioning Relay Connectivity over SAToP
Figure 6-40 Cisco Prime Provisioning New Teleprotection_TP_SAToP Service Request—2
Step 4 Save the service request, as shown in Figure 6-41.
Figure 6-41 Cisco Prime Provisioning New Teleprotection_TP_SAToP Service Request—3
Step 5 Preview the configurations to be applied, as shown in Figure 6-42.
Figure 6-42 Cisco Prime Provisioning New Teleprotection_TP_SAToP Service Request—4
