Cisco Prime Nerk 43 User Guide
Have a look at the manual Cisco Prime Nerk 43 User Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 53 Cisco manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
18-137 Cisco Prime Network 4.3.2 User Guide Chapter 18 Managing Carrier Ethernet Configurations OSPF Topology Table 18-60 describes the information that is displayed in link properties window. Service Alarms As part of the topological link support, two new service alarms OSPF link down and OSPF link up are introduced. These alarms are generated on the OSPF links in cases such as misconfigurations, shutting down of physical interfaces or any other scenario that might break the OSPF neighborship. Correlation The OSPF link down alarm is a ticketable event. It also can be correlated under the physical link alarms. If OSPF configured interface goes down, the OSPF link also goes down. For e.g, In case of interface shut down, the OSPF link down alarm is generated and correlated to the Link down due to admin service alarm. Table 18-60 OSPF Link Properties window Field Description Link Type The link protocol, which is OSPF in this instance. Type The type of link, which is Dynamic. Bi Directional Indicates whether the link is bidirectional. OSPF Information tab OSPF Process ID The unique code to identify the OSPF process. OSPF Router ID The IP address of the OSPF router. OSPF Version The OSPF version, which can be v1, v2, or v3. Neighbor State The status of the OSPF neighbor, which can be Full and Two-Way. Neighbor Provides IP address of the OSPF Neighbor OSPF Interface The link to the OSPF interface.
18-138 Cisco Prime Network 4.3.2 User Guide Chapter 18 Managing Carrier Ethernet Configurations Monitoring the CPT 50 Ring Support Monitoring the CPT 50 Ring Support The Cisco Carrier Packet Transport (CPT) Product Family with CPT600, CPT200 and CPT50 Series sets the industry benchmark as a compact carrier-class converged access and aggregation platform for Unified Packet Transport architectures. The CPT 50 is a compact and operationally simple, yet highly scalable and flexible platform optimized for delivering TDM like Ethernet Private 4.3.2 as well as multipoint capabilities for Business, Residential, Mobile Backhaul, Data Center, and Video Services. Its unique satellite architecture is designed to scale, simplify and enhance the operational and deployment aspects of service-delivery networks. The CPT system also provides the ability to operate CPT 50 in a physical ring homed back to a single CPT 600 or CPT 200 chassis. This feature provides the flexibility of connecting CPT 50 in a closed-ended ring or an open-ended ring. As a result, the failure of a line or uplink card does not impact the traffic in a ring. CPT 50 in a ring works like a route processor and each CPT 50 interacts with Transport Node Controller (TNC) directly. CPT 50 supports the following types of rings: Single Homed—A ring that is subtending from a single CPT-600 or CPT 200. There are two types of single home rings: –Open Ended Ring—Connects to the CPT-600 or CPT-200 through one interface only. Hence, there is only one unprotected path available to the traffic on the ring. –Closed—Connects to the CPT-600/200 through two interfaces. Hence there is a protected path available for the traffic either through the east or west interface on the ring. Dual Homed —A ring whose east port exists on one CPT 200 or CPT 600 (Working Ring Controller) and west port exists on another CPT 200 or CPT 600 (Protected Ring Controller). If WRC fails, this type of ring provides access to all the CPT 50s in the ring by switching the traffic to the other controller. The following figure depicts the CPT 50 dual homed in Prime Network: In the above figure, the dual ring home starts in one CPT 600 device and ends in another CPT 600 device. The CPT 600 device from which the dual ring starts is the Working Ring Controller (WRC) and the other CPT 600 device is the Protected Ring Controller (PRC).
18-139 Cisco Prime Network 4.3.2 User Guide Chapter 18 Managing Carrier Ethernet Configurations Monitoring the CPT 50 Ring Support NoteTo view more details about the device, right-click the device and choose Inventory to view the inventory details. The Node Role field in the content pane denotes whether the CPT device is WRC or PRC. Configuring CPT The following commands can be launched from the inventory by right-clicking the appropriate node and choosing Commands > Configuration. Your permissions determine whether you can run these commands. To find out if a device supports these commands, see the Cisco Prime Network 4.3.2 Supported Cisco VNEs. Command Navigation Description Configure L2 Control ProtocolPhysical Inventory > Chassis > Ba ckplane >slot > right-click on the Ethernet card >Commands> ConfigurationUse this command to configure the L2 Control Protocol. Show L2 Control ProtocolPhysical Inventory > Chassis > Ba ckplane >slot > right-click on the Ethernet card >Commands> ShowUse this command to view details of the L2 Control protocol parameters configured for the selected port. Add Loopback Physical Inventory > Chassis > Ba ckplane >slot > right-click on the Ethernet card >Commands> ConfigurationUse these commands to add and remove a loop-back respectively. NoteLoop-back refers to the process of routing electronic signals or digital data streams, back to their source with processing or modifying it. Remove Loopback Configure CDP Physical Inventory > Chassis > Backplane >slot > right-click on the Ethernet card >Commands> ConfigurationUse this command to configure CDP. NoteCisco Discovery Protocol (CDP) is used to obtain protocol addresses of neighboring devices and discover the platform of those devices. It can also be used to show information about the interfaces your router uses. Configure EthernetUse this command to configure Ethernet parameters.
18-140 Cisco Prime Network 4.3.2 User Guide Chapter 18 Managing Carrier Ethernet Configurations Viewing the G8032 ERPS Configuration Viewing the G8032 ERPS Configuration Ethernet Ring Protection Switching is an effort at ITU-T under G.8032 Recommendation to provide sub-50ms protection and recovery switching for Ethernet traffic in a ring topology and at the same time ensuring that there are no loops formed at the Ethernet layer. An Ethernet ring consists of multiple Ethernet ring nodes. Each Ethernet ring node is connected to adjacent Ethernet ring nodes using two independent ring links. A ring link prohibits formation of loops that affect the network. The Ethernet ring uses a specific link to protect the entire Ethernet ring. This specific link is called the Ring Protection Link (RPL). A ring link is bound by two adjacent Ethernet ring nodes and a port for a ring link (also known as a ring port). There must be at least two Ethernet ring nodes in an Ethernet ring. Ring Protection Switching Architecture works based on the following fundamentals: Principle of Loop Avoidance—Loop avoidance is achieved by guaranteeing that traffic flows on all but one of the ring links at any point of time. The one ring link from which traffic does not flow is called the Ring Protection Link (RPL), which is generally blocked. A designated Ethernet ring node—the RPL owner node—is responsible for blocking traffic at one end of the RPL. In the event of an Ethernet ring failure, the RPL owner node must unblock its end of the RPL and allow the RPL to be used for traffic. Utilization of learning, forwarding, and filtering database mechanisms defined in the Ethernet Flow Forwarding Function—Failure of Ethernet ring results in protection switching of traffic, which is controlled by the Ethernet Flow Forwarding Function. An APS protocol is used to coordinate the protection action over the ring, which transmits Ring Automatic Protection Switching (R-APS) messages. Ethernet rings also supports multi ring/ladder network that consists of conjoined Ethernet rings by one or more interconnection points. The protection switching mechanisms and protocol are also applicable for multi ring/ladder network on adherence of certain principles.Show Ethernet ParametersPhysical Inventory > Chassis > Ba ckplane >slot > right-clic k on the Ethernet card >Commands>ShowUse this command to view details of the Ethernet parameters configured for the selected Ethernet port. Configure Port ParametersPhysical Inventory > Chassis > Backplane >slot > right-click on the Ethernet card >Commands> ConfigurationUse this command to configure port parameters. Show Port ParametersPhysical Inventory > Chassis > Backplane >slot > right-click on the Ethernet card >Commands> ShowUse this command to view the port parameters configured for the selected port. Command Navigation Description
18-141 Cisco Prime Network 4.3.2 User Guide Chapter 18 Managing Carrier Ethernet Configurations Viewing the G8032 ERPS Configuration The G8032 technology also supports multiple ERP instances over a ring. An ERP instance is an entity that is responsible for the protection of subset of VLANs carried over the physical ring and it should configure its own R-APS channel, RPL, RPL Owner and RPL Neighbor nodes. Ring protection switching process also occurs based on the detection of defects on the transport entity on the ring link, and the transport entity can have a failed or non-failed condition. To monitor these defects, Ethernet ring protection may use any one of the following methods: Inherent—The fault condition status of each link connection is derived from the status of the underlying server layer trail. Sub-layer—Each ring link is monitored using Tandem Connection Monitoring (TCM). Test trail—An extra test trail is used to detect defects, which is setup along each ring link. In Prime Network, the G8032 Ethernet Ring Protection Switching configuration can be viewed in the following nodes: Profile—This node displays the G8032 profile details. Each G8032 ring is associated to a profile, which consists of several timers. The timer displays details of the time frame the ring needs to wait before, during and after performing an action to avoid race conditions and unnecessary switching operations. If a ring is not associated to a profile, the default profile is automatically associated to it. Ring—This node displays the properties of the ring as well as the properties that are shared across all ERP instances To view the G8032 Ethernet Ring Protection Switching Profile configuration: Step 1Right-click on the required device and choose the Inventory option. Step 2In the Inventory window, choose Logical Inventory>G8032>Profiles. A list of all the G8032 profiles are displayed in the content pane. Step 3In the content pane, right-click on the profile name to view the G8032 Profile Properties window. Table 18-61 describes the information displayed in the G8032 Profile Properties window. Table 18-61 G8032 Profile Properties Field Description Profile Name The unique name of the profile associated to the G8032 ring. WTR Interval The Wait-to-Restore interval (in minutes) applicable to the G8032 ring. This interval refers to the duration before traffic is restored to the state, when it is found that a failure is no longer occurring. This interval also avoids toggling protection states in case of intermittent defects. This field defaults to 5 minutes. Guard Interval The Guard Interval (in milliseconds) that denotes the duration the node waits before performing a node state transition. This is done to block outdated R-APS messages from causing unnecessary node state changes. This field defaults to 500.
18-142 Cisco Prime Network 4.3.2 User Guide Chapter 18 Managing Carrier Ethernet Configurations Viewing the G8032 ERPS Configuration To view the G8032 Ethernet Ring Protection Switching Ring configuration: Step 1Right-click on the required device and choose the Inventory option. Step 2In the Inventory window, choose Logical Inventory>G8032>Ring>ring name. The details of the ring are displayed in the content pane. Table 18-62 describes the Ring properties. Holdoff Timer The duration (in seconds) applicable for the G8032 ring. The node waits for the specified duration to expire before reporting faults to the ring protection mechanism. Mode Type The operating mode applicable for the G8032 ring, which can be any one of the following: Revertive—In case the condition causing the switch is cleared, the traffic channel is restored to the working transport entity. Non revertive—In case the condition causing the switch is cleared, the traffic channel continues to use the RPL. This field defaults to Revertive. Table 18-61 G8032 Profile Properties Field Description Table 18-62 G8032 Ring Properties Field Description Ring Name The name of the ring. Ring Type The ring type, which can be any one of the following: Open—When the ring is terminated by an Ethernet access such as VPLS. Closed—When the arcs or links in the ring are simple Ethernet links. Excluded VLAN ID The range of VLAN ID that are excluded by the ring. In other words, the VLAN ID included in this range are not serviced by the ring and not blocked by the ring switching mechanism. Untagged in Excluded VLANsIndicates whether untagged Ethernet traffic is also blocked by the VLAN exclusion list. Ring Ports Entries tab Port Number The port number associated to the ring. Local Port The link to the local physical port that is used for this ring port. Monitor Interface The link to the interface that is used as the monitor interface. A monitor interface is used to monitor the ring port and detect ring failures. Blocked VLAN IDs The range of VLAN IDs that are blocked by the ring port. Untagged in Blocked VLANsIndicates whether untagged traffic is blocked by the ring port.
18-143 Cisco Prime Network 4.3.2 User Guide Chapter 18 Managing Carrier Ethernet Configurations Viewing the G8032 ERPS Configuration Unblocked VLAN IDs The list of VLAN IDs that are not blocked by the ring port. Untagged in Unblocked VLANsIndicates whether untagged traffic is unblocked by the ring port. Ring Instance Entries tab Instance The unique code assigned to the instance. Node Type The node type that determines the node’s responsibility towards the instance. This can be Normal, Owner, Neighbor, or Next Neighbor. Node State The state of the node for a specific instance, which can be any one of the following: Idle, Pending, Protection, Forced Switch, and Manual Switch. This state is configured by the administrator or determined by the APS as part of the G8032 protection protocol. Port 0 State The status of the port that is configured as Port 0, which can be N/A, RPL-Link, Faulty, Blocked, Local Forced Switch, or Local Manual Switch. Port 1 State The status of the port that is configured as Port 1, which can be N/A, RPL-Link, Faulty, Blocked, Local Forced Switch, or Local Manual Switch. Instances tab ID The unique code assigned to the instance. Instance Description The description of the instance. Profile The link to the ring profile associated to the instance. Included VLAN IDs The list of VLAN IDs included or served by this instance, which includes all VLANs associated with the ring instance. RPL Port Role The Ring Protection Link (RPL) port in charge of the RPL, which enables it to turn the RPL on or off according to the ring instance functionality. This port can be Port 0 or Port 1. APS Channel Level The APS Channel Level for the ring instance, which can be any value between 0 and 7. This value is defined by the Maintenance Entity group Level (MEL) and is used to differentiate various Ethernet problems and to signal them. Configuration State The configuration status of the ring instance, which can be Resolved or Unresolved. Unresolved Reason The feedback to the configurator that explains the reason for the unresolved configuration state. Table 18-62 G8032 Ring Properties Field Description
18-144 Cisco Prime Network 4.3.2 User Guide Chapter 18 Managing Carrier Ethernet Configurations Configuring REP and mLACP Configuring REP and mLACP The following commands can be launched from the inventory by right-clicking the appropriate node and choosing Commands > Configuration. Your permissions determine whether you can run these commands (see Permissions for Managing Carrier Ethernet, page B-12). To find out if a device supports these commands, see the Cisco Prime Network 4.3.2 Supported Cisco VNEs. Viewing the Remote Loop Free Alternate Configurations When a link or router in the network fails, there is loss of data during the time it takes for the routers to converge after a topology change. Since it takes hundreds of milliseconds for the router to converge, the application traffic is sensitive to losses especially in the case of interactive multimedia services such as VoIP and pseudowires. The Loop Free Alternate Fast ReRoute (LFA-FRR) technology helps reduce the packet loss that happens in the event of link or router failure. It reduces the failure reaction time to tens of milliseconds. This is achieved by using a pre-computed alternate next-hop. If the currently selected primary next-hop fails, then the alternate next-hop is used in the event of failure. A network that is configured with the LFA-FRR experiences less traffic loss and micro-looping of packets when compared to a network without LFA-FRR. The Remote LFA-FRR technology is an extension of LFA that covers all topologies. It can dynamically compute its LFA node and forward traffic around a failed node to a remote LFA that is more than one hop away. After a node dynamically determines an alternate node (which is not directly connected to it), it establishes a directed Label Distribution Protocol (LDP) session to the alternate node. The directed LDP session exchanges labels for the particular forward error correction (FEC). When the network experiences link failure, the node manages to forward the data to the destination by using label stacking. By configuring Remote LFA-FRR on your network, you can eliminate additional traffic engineering protocols, simplify operations with minimum configuration, prevent hair-pinning that occurs in TE-FRR, and compute node dynamically without manual provision. In Prime Network, Remote LFA-FRR is configured using IS-IS and OSPF configurations. To view the OSPF Remote LFA configuration: Step 1Right-click on the required device and choose the Inventory option. Step 2In the Inventory window, choose Logical Inventory>OSPF Processes>OSPF Process (version) ID. The OSPF process details are displayed in the content pane. For more information, see Vi ew i n g I S - I S Properties, page 18-130. Command Navigation Description REP Command Show REP Segment InformationCommands > Show This action performed at the command launch point. mLACP Commands Show Group Show MPLS LDP Show Channel Show LACP InternalCommands > Show These actions are performed at the command launch point.
18-145 Cisco Prime Network 4.3.2 User Guide Chapter 18 Managing Carrier Ethernet Configurations Viewing the Remote Loop Free Alternate Configurations Step 3In the content pane, click the RLFA Tunnels tab as shown in Figure 18-78. Figure 18-78 RLFA Tunnels tab Table 18-63 describes the information that is displayed in the RLFA Tunnels tab. To view the IS-IS Remote LFA configuration: Step 1Right-click on the required device and choose the Inventory option. Step 2In the Inventory window, choose Logical Inventory>IS-IS>Process. The IS-IS process details are displayed in the content pane. For more information, see Viewing IS-IS Properties, page 18-130. Table 18-63 OSPF Processes - RLFA Tunnels tab Field Description Tunnel Name The name of the RLFA tunnel. Out-Interface The outgoing interface of the tunnel, which is used to reach the end point. Clicking this link will take you to the relevant entry in the physical inventory node. Next Hop The IP address of the next hop in the path. End Point The end point of the RLFA tunnel. Protected Interface The interface protected by the Remote RLFA tunnel. Protected Interface IP AddressThe IP Address of the interface protected by the Remote RLFA tunnel.
18-146 Cisco Prime Network 4.3.2 User Guide Chapter 18 Managing Carrier Ethernet Configurations Viewing the Remote Loop Free Alternate Configurations Step 3In the content pane, click the RLFA Tunnels tab. For more information, see Table 18-63. Tie-Breaking Rules for Remote LFA A primary path can have multiple LFAs. A routing protocol is used to implement tie-breaking rules. When the primary path fails, then these rules help to eliminate multiple candidate LFAs, select one LFA per primary path, and distribute the traffic over multiple LFAs. NoteThe tie-breaking rule has certain conditions and attributes based on which multiple candidate LFAs are eliminated. If a rule eliminates all candidate LFAs, then the rule is omitted. Configuring OSPF and ISIS with Remote LFA The following can be launched from the inventory by right-clicking on the appropriate node and choosing Commands > Configuration. Your permissions determine whether you can run these commands (see Permissions for Managing Carrier Ethernet, page B-12). To find out if a device supports these commands, see the Cisco Prime Network 4.3.2 Supported Cisco VNEs. Command Navigation Description Create OSPF ProcessIn the Inventory window, right-click on the device > Commands>Configurat ion>OSPF.Create a new OSPF process. The new OSPF process created here will be available under the OSPF Processes node in the Logical Inventory. Show OSPF DatabaseView the OSPF database details. Create OSPF NetworkLogical Inventory> OSPF Processes>OSPF Process. Right-click on the process and choose Commands > Configurat ion.Create one or more of the following OSPF Networks—Broadcast, Non-broadcast, Point-to-multipoint, and Point-to-point. Delete OSPF NetworkDelete an OSPF Network created using the Create OSPF Network command. Delete OSPF ProcessDelete an OSPF process created using the Create OSPF Process command. Modify OSPF ProcessModify details of the OSPF process created using the Create OSPF Process command. Create OSPF Passive InterfaceCreate a passive interface for an OSPF process. Delete OSPF Passive InterfaceDelete a passive interface for an OSPF process.