Nokia — Proprietary and confidential
Use pursuant to applicable agreements
Page 2
FD 100/320Gbps NT and FX NT IHub Services Guide
Nokia is a registered trademark of Nokia Corporation. Other products and company
names mentioned herein may be trademarks or tradenames of their respective
owners.
The information presented is subject to change without notice. No responsibility is
assumed for inaccuracies contained herein.
Contains proprietary/trade secret information which is the property of Nokia and must
not be made available to, or copied or used by anyone outside Nokia without its
written authorization. Not to be used or disclosed except in accordance with
applicable agreements.
FD 100/320Gbps NT and FX NT IHub Services GuidePreface
1Preface
This preface provides general information about the documentation set for the
7302 Intelligent Services Access Manager (7302 ISAM), the 7330 Intelligent
Services Access Manager Fiber to the Node (7330 ISAM FTTN) and the
7360 Intelligent Services Access Manager FX (7360 ISAM FX).
1.1Scope
This documentation set provides information about safety, features and functionality,
ordering, hardware installation and maintenance, CLI and TL1 commands, and
software upgrade and migration procedures for the current release.
1.2Audience
This documentation set is intended for planners, administrators, operators, and
maintenance personnel involved in installing, upgrading, or maintaining the
7302 ISAM, the 7330 ISAM FTTN or the 7360 ISAM FX.
1.3Required knowledge
Readers must be familiar with general telecommunications principles.
1.4Product naming
When the term “ISAM” is used alone, then the 7302 ISAM, the 7330 ISAM FTTN and
the 7360 ISAM FX are meant. If a feature is valid for only one of the products, the
applicability will be explicitly stated.
1.5Documents
Refer to the Product Information document for your product to see a list of all relevant
customer documents and their part numbers.
1.6Acronyms and initialisms
See the ISAM Glossary for the expansion of acronyms and initialisms used in this
documentation set.
Issue: 133HH-11985-AAAA-TQZZA41
Page 42
Preface
FD 100/320Gbps NT and FX NT IHub Services Guide
1.7Safety information
For safety information, see the Safety Manual for your product.
1.8Special information
The following are examples of how special information is presented in this document.
Danger — Danger indicates that the described activity or
situation may result in serious personal injury or death; for
example, high voltage or electric shock hazards.
Warning — Warning indicates that the described activity or
situation may, or will, cause equipment damage or serious
performance problems.
Caution — Caution indicates that the described activity or
situation may, or will, cause service interruption.
Note — A note provides information that is, or may be, of
special interest.
1.9Release notes
Be sure to refer to the release notes (such as the Customer Release Notes or
Emergency Fix Release Note) issued for software loads of your product before you
install or use the product. The release notes provide important information about the
software load.
42
3HH-11985-AAAA-TQZZAIssue: 13
Page 43
FD 100/320Gbps NT and FX NT IHub Services GuideGetting Started
2Getting Started
2.1 In This Document
2.2 Services Command Reference
2.3 CLI Command Syntax Symbols
2.1In This Document
This document provides process flow information to configure provision services.
Table 1 lists the tasks necessary to configure services.
This guide is presented in an overall logical configuration flow. Each section
describes a software area and provides CLI syntax and command usage to configure
parameters for a functional area.
Table 1Configuration Process
AreaTaskChapter
SubscribersGlobal entitiesConfiguring Global Service Entities with CLI
VLL serviceVirtual Leased Line Services
VPLS serviceVirtual Private LAN Service
IES serviceInternet Enhanced Service
VPRN serviceVirtual Private Routed Network Service
Mirroring serviceMirror Services
2.2Services Command Reference
This document provides the command reference trees for the services.
Topics include:
•Global Services Commands
•Global Services Command Reference
Issue: 133HH-11985-AAAA-TQZZA43
Page 44
Getting Started
FD 100/320Gbps NT and FX NT IHub Services Guide
Service Configuration Commands
•
•VLL Services CLI Command Reference
•VPLS Service CLI Command Reference
•IES Services CLI Command Reference
•VPRN Services CLI Command Reference
•Mirror Service CLI Command Reference
2.3CLI Command Syntax Symbols
This section explains the symbols used throughout this manual within a CLI
command syntax, see Table 2.
Table 2Command Syntax Symbols
SymbolDescription
|A vertical line indicates that one of the parameters within the brackets or braces is required.
Example: tcp-ack {true|false}
[ ]Brackets indicate optional parameters.
Example: redirects [numberseconds]
< >Angle brackets indicate that you must enter text based on the parameter inside the brackets.
Example: interface <interface-name>
{ }Braces indicate that one of the parameters must be selected.
Example: default-action {drop|forward}
[{ }]Braces within square brackets indicate that you may choose one of the optional parameters or no
BoldCommands in bold indicate commands and keywords.
ItalicCommands in italics indicate command options.
parameter at all.
Example: sdpsdp-id [{gre|mpls}]
44
3HH-11985-AAAA-TQZZAIssue: 13
Page 45
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
3Services Overview
3.1 In this Chapter
3.2 Introduction
3.3 ISAM Service Model
3.4 Service Entities
3.5 Service Creation Process Overview
3.6 Deploying and Provisioning Services
3.7 Configuration Notes
3.8 Configuring Global Service Entities with CLI
3.9 Basic Configuration
3.10 Ethernet Connectivity Fault Management
3.11 G.8032 Ethernet Ring Protection Switching
3.12 DHCP Lease Query
3.13 DHCP Remote ID Check
3.14 GRE Tunnels Overview
3.16 Global Services Command Reference
3.17 Global Service Commands
3.1In this Chapter
This section provides an overview of the ISAM subscriber services, service model
and service entities. Additional details on the individual subscriber services can be
found in subsequent chapters.
Issue: 133HH-11985-AAAA-TQZZA45
Page 46
Services Overview
3.2Introduction
FD 100/320Gbps NT and FX NT IHub Services Guide
A service is a globally unique entity that refers to a type of connectivity service for
either Internet or VPN connectivity. Each service is uniquely identified by a service
ID within a service area. The ISAM service model uses logical service entities to
construct a service. In the service model, logical service entities provide a uniform,
service-centric configuration, management, and billing model for service
provisioning.
Services can provide Layer 2/bridged service or Layer3/IP routed connectivity
between a Service Access Point (SAP) on one ISAM and another service access
point (a SAP is where end-user traffic enters and exits the service). A distributed
service over the Internet requires that ISAMs are interconnected via SR-Series
routers.
Distributed services use service distribution points (SDPs) to direct traffic to another
PE through a service tunnel. SDPs are created on each participating ISAM/service
router, specifying the origination address (the ISAM participating in the service
communication) and the destination address of another ISAM/service router. SDPs
are then bound to a specific customer service. Without the binding process, far-end
service router/ISAM devices are not able to participate in the service (there is no
service without associating an SDP with a service).
3.2.1Service Types
The ISAM offers the following types of subscriber services which are described in
more detail in the referenced chapters:
•Virtual Private LAN Service (VPLS) — ISAM supports three types of VPLS
services: v-VPLS (VLAN VPLS), m-VPLS (management VPLS) and VPLS.
v-VPLS forwarders emulate the ISAM bridging service in the IHUB. v-VPLS
forwarders enable frames to be L2 forwarded between user side and network side
though IHUB and extend the reach of a VPRN IP interface (SAP) to several
physical ports. The m-VPLS forwarder is exclusively used to handle L2CP frames
(for example, spanning tree). The m-VPLS is not intended to forward data traffic.
For more information see “Virtual Private LAN Service”. VPLS (a Layer 2
multipoint-to-multipoint VPN) enables frames to be L2 forwarded between the
user side and the MPLS network side. Frames are encapsulated in MPLS Pseudo
wires (PW).
•Internet Enhanced Service (IES) — A direct Internet access service where the
customer is assigned an IP interface for Internet connectivity. See “Internet
Enhanced Service”.
•Virtual Leased Line Service (VLL) - Ethernet pipe (Epipe) — A Layer 2
point-to-point VLL service for Ethernet frames. See “Ethernet Pipe (Epipe)
Services”.
•Virtual Private Routed Network (VPRN) — A Layer 3 IP multipoint-to-multipoint
VPN service as defined in RFC 2547bis. See “Virtual Private Routed Network
Service”.
46
3HH-11985-AAAA-TQZZAIssue: 13
Page 47
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
3.2.2Service Policies
Common to all ISAM connectivity services are filter policies that are assigned to the
service. Filter policies are defined at a global level and then applied to a service on
the router. They are used to define ISAM service enhancements.
•Filter policies allow selective blocking of traffic matching criteria from ingressing
or egressing a SAP.
Filter policies, also referred to as access control lists (ACLs), control the traffic
allowed in or out of a SAP based on MAC or IP match criteria. Associating a filter
policy on a SAP is optional. Filter policies are identified by a unique filter policy ID.
A filter policy must be created before it can be applied to a SAP. A single ingress
and single egress filter policy can be associated with a SAP.
3.3ISAM Service Model
In the ISAM service model, the ISAMs are deployed at the subscriber access
network. From there, traffic is forwarded on VLANs or on MPLS PW towards service
edge routers deployed at the provider edge (ISAM or 7450).
The service model uses logical service entities to construct a service. The logical
service entities are designed to provide a uniform, service-centric configuration,
management, and billing model for service provisioning. Some benefits of this
service-centric design include:
•Many services can be bound to a single customer.
•Many services can be bound to a single tunnel.
•Tunnel configurations are independent of the services they carry.
•Changes are made to a single logical entity rather than multiple ports on multiple
devices. It is easier to change one tunnel rather than several services.
•The operational integrity of a logical entity (such as service end points) can be
verified rather than dozens of individual services improving management scaling
and performance.
•A failure in the network core can be correlated to specific subscribers and
services.
•Filter policies, and accounting policies are applied to each service instead of
correlating parameters and statistics from ports to customers to services.
Service provisioning uses logical entities to provision a service where additional
properties can be configured for bandwidth provisioning, QoS, security filtering,
accounting/billing to the appropriate entity.
Issue: 133HH-11985-AAAA-TQZZA47
Page 48
Services Overview
3.4Service Entities
FD 100/320Gbps NT and FX NT IHub Services Guide
The basic logical entities in the service model used to construct a service are:
•Customers
•Service Access Points (SAPs)
•Service Distribution Points (SDPs)
Figure 1Service Entities
SERVICE
ACCESS
SUBSCRIBERSSUBSCRIBERS
Customer
27
Customer
25
Customer
7
POINTS
SAPService
Cust-27
Cust-25
SAP
SAP
Service
Cust-7
Service
SERVICE
DISTRIBUTION
POINTS
SDP
DEMUX
ALA-AALA-B
DEMUX
SDP
3.4.1Customers
The most basic required entity is the customer ID value which is assigned when the
customer account is created. To provision a service, a customer ID must be
associated with the service at the time of service creation.
3.4.2Service Access Points (SAPs)
Service
Cust-27
Cust-25
Service
Cust-7
Service
SERVICE
ACCESS
POINTS
SAP
SAP
SAP
Customer
27
Customer
25
Customer
7
48
Each subscriber service type is configured with at least one service access point
(SAP). A SAP identifies the interface point for a service on an Nokia ISAM router
(Figure 2). The SAP configuration requires that slot information be specified. The slot
parameters must be configured prior to provisioning a service (see the “Port Features” section of the FD 100/320Gbps NT and FX NT IHub Interface Guide).
A SAP is a local entity to the ISAM and is uniquely identified by:
•The physical Ethernet port or Link Aggregate (LAG) port
•The encapsulation type (all SAPs use the Dot1Q encapsulation type)
•The encapsulation identifier (ID) (that is, the VLAN ID of the SAP)
SAPs can only be created on ports designated as “access” or “hybrid” in the physical
port configuration. SAPs cannot be created on ports designated as core-facing
“network” ports as these ports have a different set of features enabled in software.
3HH-11985-AAAA-TQZZAIssue: 13
Page 49
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
Customer
27
IP Network
SAP
3/1/6
dot1q
SAP
2/2/3
dot1q
Service
Cust-27
SAP
ALA-A
Customer
27
Figure 2Service Access Point (SAP)
3.4.2.1SAP Configuration Considerations
When configuring a SAP, consider the following:
•An SAP is a local entity and only locally unique to a given device. The same SAP
ID value can be used on another ISAM/service router.
•There are no default SAPs. All SAPs in subscriber services must be created.
•The default administrative state for a SAP at creation time is administratively
enabled.
•When a SAP is deleted, all configuration parameters for the SAP will also be
deleted. For Internet Enhanced Service (IES), the IP interface must be shutdown
before the SAP on that interface may be removed.
•A SAP is owned by and associated with the service in which it is created in each
ISAM.
•If a port is administratively shutdown, all SAPs on that port will be operationally
out of service.
•A SAP cannot be deleted until it has been administratively disabled (shutdown).
•Each SAP can have one each of the following policies assigned:
•Ingress filter policy
•Egress filter policy
3.4.3Service Distribution Points (SDPs)
A service distribution point (SDP) acts as a logical way to direct traffic from one ISAM
to another PE through a uni-directional (one-way) service tunnel. The SDP
terminates at the far-end ISAM/service router which directs packets to the correct
service egress SAPs on that device. A distributed service consists of a configuration
with at least one SAP on a local node, one SAP on a remote node, and an SDP
binding the service to the service tunnel.
Issue: 133HH-11985-AAAA-TQZZA49
Page 50
Services Overview
FD 100/320Gbps NT and FX NT IHub Services Guide
An SDP has the following characteristics:
•An SDP is locally unique to a participating ISAM. The same SDP ID can appear
on other service routers/ISAMs.
•An SDP uses the system IP address to identify the far-end PE.
•An SDP is not specific to any one service or any type of service. Once an SDP is
created, services are bound to the SDP. An SDP can also have more than one
service type associated with it.
•All services mapped to an SDP use the same transport encapsulation type
defined for the SDP (i.e MPLS).
•An SDP is a management entity. Even though the SDP configuration and the
services carried within are independent, they are related objects. Operations on
the SDP affect all the services associated with the SDP. For example, the
operational and administrative state of an SDP controls the state of services
bound to the SDP.
An SDP from the local device to a far-end PE requires a return path SDP from the
far-end PE back to the local ISAM. Each device must have an SDP defined for every
remote PE to which it wants to provide service. SDPs must be created first, before a
distributed service can be configured.
Figure 3SDP
Customer
27
Customer
27
SAP
3/1/6
dot1q
SAP
2/2/3
dot1q
3.4.3.1SDP Bindings
To configure a distributed service from ALA-A to ALA-B, the SDP ID must be
specified in the service creation process in order to “bind” the service to the tunnel
(the SDP). Otherwise, service traffic is not directed to a far-end point and the far-end
PE (ISAM or service router) cannot participate in the service (there is no service). To
configure a distributed service from ALA-B to ALA-A, the SDP ID must be specified.
Spoke and Mesh SDPs
Cust-27
Service
SDP
ALA-A
IP/MPLS Network
50
When an SDP is bound to a service, it is bound as either a spoke SDP or a mesh
SDP. The type of SDP indicates how flooded traffic is transmitted.
3HH-11985-AAAA-TQZZAIssue: 13
Page 51
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
A spoke SDP is treated like the equivalent of a traditional bridge “port” where flooded
traffic received on the spoke SDP is replicated on all other “ports” (other spoke and
mesh SDPs or SAPs) and not transmitted on the port it was received.
All mesh SDPs bound to a service are logically treated like a single bridge “port” for
flooded traffic where flooded traffic received on any mesh SDP on the service is
replicated to other “ports” (spoke SDPs and SAPs) and not transmitted on any mesh
SDPs.
SDP Encapsulation Types
The Nokia service model uses encapsulation tunnels through the core to
interconnect with service edge routers. An SDP is a logical way of referencing the
entrance to an encapsulation tunnel. The following encapsulation types are
supported: Layer 2 with LDP signaled.
3.4.3.2MPLS
Multi-Protocol Label Switching (MPLS) encapsulation has the following
characteristics:
•LSPs (label switched paths) are used through the network.These paths define
how traffic traverses the network from point A to B.
Paths can be manually defined or are based on the routing protocol (for example,
OSPF).
•An ISAM supports both signaled LSPs and non-signaled LSPs through the
network.
•Non-signaled paths are defined at each hop through the network.
•Signaled paths are communicated via protocol
Because services are carried in encapsulation tunnels and an SDP is an entrance
to the tunnel, an SDP has an implicit maximum transmission unit (MTU) value.
The MTU for the service tunnel can affect and interact with the MTU supported on
the physical port where the SAP is defined.
3.5Service Creation Process Overview
Figure 4 displays the overall process to provision core and subscriber services.
Issue: 133HH-11985-AAAA-TQZZA51
Page 52
Services Overview
CREATE SERVICE TYPE, SPECIFYING SERVICE ID AND CUSTOMER ID
START
ASSOCIATE POLICIES
ACCESS OPERATOR CONSOLE GUI
OR CLI VIA TELNET OR DIRECT ATTACHMENT
The service model provides a logical and uniform way of constructing connectivity
services. The basic steps for deploying and provisioning services can be broken
down into three phases.
52
3HH-11985-AAAA-TQZZAIssue: 13
Page 53
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
3.6.1Phase 1: Core Network Construction
Before the services are provisioned, the following tasks should be completed:
•Build the IP or IP/MPLs core network.
•Configure routing protocols.
•Configure MPLS LSPs (if MPLS is used).
•Construct the core SDP service tunnel mesh for the services.
3.6.2Phase 2: Service Administration
Perform preliminary policy configurations and SDP configurations to control traffic
flow, operator access, and to manage fault conditions and alarm messages.
3.6.3Phase 3: Service Provisioning
•Provision customer account information.
•Provision the customer services on the ISAM by defining SAPs, and then by
binding the service to appropriate SDPs as necessary.
3.7Configuration Notes
This section describes service configuration caveats.
3.7.1General
Service provisioning tasks can be logically separated into two main functional areas,
core tasks and subscriber tasks and are typically performed prior to provisioning a
subscriber service.
Core tasks include the following:
•Create customer accounts
•Create LSPs
•Create SDPs
Subscriber services tasks include the following:
•Create Epipe, VLL, IES, VPLS, or VPRN services
•Configure interfaces (where required) and SAPs
•Bind SDPs
Issue: 133HH-11985-AAAA-TQZZA53
Page 54
Services Overview
3.8Configuring Global Service Entities with CLI
3.8.1Service Model Entities
FD 100/320Gbps NT and FX NT IHub Services Guide
This section provides information to create subscriber (customer) accounts and
configure Service Distribution Points (SDPs) using the Command Line Interface
(CLI).
Topics include:
•Service Model Entities
•Configuring Customers
•Configuring an SDP
•Service Management Tasks
The Nokia service model uses logical entities to construct a service. The service
model contains four main entities to configure a service.
•Service Distribution Points (SDPs)
•Services:
•Configuring a VPLS Service with CLI
•Configuring a VLL Service with CLI
•Configuring an IES Service with CLI
•Configuring a VPRN Service with CLI
•Service Access Points (SAPs)
•Configuring SAP Parameters
3.8.2Configuring Customers
When configuring a service in the ISAM system, a customer ID is specified. The
customer ID is reserved for future extensions to ISAM, and therefore the default
value 1can be used, or a customer ID can be optionally created with another value.
Optional customer ID parameters include:
•Description
•Contact name
Use the following CLI syntax to create and input customer information:
•The system IP address of the originating PE and the far-end PE.
•An SDP encapsulation type =MPLS.
3.8.3.1SDP Configuration Tasks
This section provides a brief overview of the tasks that must be performed to
configure SDPs and provides the CLI commands.
Consider the following SDP characteristics:
•SDPs can only be created with encapsulation type MPLS.
•Each distributed service must have an SDP defined for every remote PE to
provide VLL, VPLS, and VPRN services.
•A distributed service must be bound to an SDP. By default, no SDP is associated
with a service. Once an SDP is created, services can be associated to that SDP.
•An SDP is not specific or exclusive to any one service or any type of service. An
SDP can have more than one service bound to it.
•The SDP IP address must be a peer PE system IP address.
•In order to configure an MPLS SDP, LSPs must be configured first and then the
LSP-to- SDP association must be explicitly created.
•In the SDP configuration, automatic ingress and egress labeling (targeted LDP) is
enabled by default. Ingress VC labels and egress VC labels are signaled over a
TLDP connection between two PEs.
Note that if signaling is disabled for an SDP, then services using that SDP must
configure ingress vc-labels and egress vc-labels manually.
To configure a basic SDP, perform the following steps:
1Specify an originating node.
2Create an SDP ID.
Issue: 133HH-11985-AAAA-TQZZA55
Page 56
Services Overview
3.8.3.2Configuring an SDP
FD 100/320Gbps NT and FX NT IHub Services Guide
3Specify an encapsulation type.
4Specify a far-end node.
When specifying MPLS SDP parameters, you can only specify a static LSP name,
an RSVP-based LSP or enable LDP. There cannot be 2 methods of transport in a
single SDP.
LSPs and static LSPs are configured in the configure>router>mpls context. See the
FD 100/320Gbps NT and FX NT IHub MPLS Guide for configuration and command
information.
Note — When you specify the far-end ip address, you are
creating the tunnel. In essence, you are creating the path from
Point A to Point B. When you configure a distributed service,
you must identify an SDP ID. Use the show service sdp
command to display the qualifying SDPs.
Use the following CLI syntax to create a MPLS SDP:
configure>service>sdp sdp-id mpls create
description description-string
far-end ip-address
ldp (when using ldp)
lsp lsp-name [lsp-name] (static or RSVP-based LSP)
path-mtu octets signaling {off|tldp}
no shutdown
The following displays an LSP-signaled MPLS SDP, and an LDP-signaled MPLS
SDP configuration.
The no form of the customer command removes a customer ID and all associated
information. All service references to the customer must be shut down and deleted
before a customer account can be deleted.
configure>service# [no] customer customer-id
3.8.4.3Modifying SDPs
To access a specific SDP, you must specify the SDP ID. To display a list of SDPs,
use the show service sdp command. Enter the parameter, such as description,
far-end, and lsp, and then enter the new information.
To match the incoming traffic’s TPID with SDP, you can use vlan-vc-etype. the
following scenarios can occur:
•For traffic ingress on SDP, the dataplane traffic whose TPID (Ethertype after the
MPLS label) does not match with the vlan-vc-etype configured on the SDP, then
the traffic would be forwarded with extra VLAN tag, for example, the user tag
preserved and outer tag added with VLAN of egress SAP and TPID of service.
•In case the ingress control plane traffic TPID does not match with the SDP TPID,
The no form of the sdp command removes an SDP ID and all associated information.
Before an SDP can be deleted, the SDP must be shutdown and removed (unbound)
from all customer services where it is applied.
For RSVP-based LSP refer to the FD 100/320Gbps NT and FX NT IHub MPLS
Guide. The syntax for static LSP is shown as a quick reference.
To display a list of static LSPs, use the show router mpls static-lsp command.
configure>router>mpls# static-lsp lsp-name
Example:
58
3HH-11985-AAAA-TQZZAIssue: 13
Page 59
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
configure>router>mpls# static-lsp to-headquarters
configure>router>mpls>static-lsp# push 105 nexthop 138.3.5.27
configure>router>mpls>static-lsp# to 1.1.1.1
configure>router>mpls>static-lsp# no shutdown
3.8.4.6Deleting LSPs
The no form of the lsp command removes an LSP ID and all associated information.
Before an LSP can be deleted, the LSP must be removed from all SDP associations.
The SDP must be administratively disabled before deleting LSPs.
configure>service# sdp 79
configure>service>sdp# no lsp 123
configure>service>sdp# exit all
# configure router
configure>router# mpls
configure>router>mpls# static-lsp 123
configure>router>mpls>static-lsp# shutdown
configure>router>mpls>static-lsp# exit
configure>router>mpls# no static-lsp 123
3.9Basic Configuration
The most basic service configuration must have the following:
•A customer ID
•A service type
•A service ID
•A SAP identifying a port and encapsulation value
•An interface (where required) identifying an IP address, IP subnet, and broadcast
address.
•For distributed services: an associated SDP
The following example provides an Epipe service configuration displaying the SDP
and Epipe service entities. SDP ID 2 was created with the far-end node
10.10.10.104. Epipe ID 6000 was created for customer ID 6 which uses the SDP ID
2.
A:ALA-B>configure>service# info detail
#-----------------------------------------...
sdp 2 mpls create
Issue: 133HH-11985-AAAA-TQZZA59
Page 60
Services Overview
3.10Ethernet Connectivity Fault Management
FD 100/320Gbps NT and FX NT IHub Services Guide
description "MPLS-10.10.10.104"
far-end 10.10.10.104
signaling tldp
path-mtu 4462
no shutdown
exit
epipe 6000 customer 6 create
service-mtu 1514
sap lt:1/1/2:0 create
no shutdown
exit
spoke-sdp 2:6111 create
no shutdown
exit
no shutdown
exit
Ethernet Connectivity Fault Management (ETH-CFM) is defined in two similar
standards: IEEE 802.1ag and ITU-T Y.1731. They both specify protocols,
procedures, and managed objects to support transport fault management, including
discovery and verification of the path, detection and isolation of a connectivity fault
for each Ethernet service instance.
The configuration is split into multiple areas. There is the base ETH-CFM
configuration which defines the different Management constructs and administrative
elements. This is performed in the ETH-CFM context. The individual management
points are configure within the specific service contexts in which they are applied.
The IHUB Services Guide will provide the basic service applicable material to build
the service specific management points, MEPs and MIPs. The different service types
support a subset of the features from the complete ETH-CFM suite.
The troubleshooting tools ETH-LBM/LBR, LTM/LTR defined by the IEEE 802.1ag
specification and the ITU-T Y.1731 recommendation are applicable to all MEPs
(MIPs where appropriate).
The advanced notification function AIS defined by the ITU-T Y is not supported on
MEPs configured on v-VPLS, VPLS and EPIPE service.
Y1731 performance monitoring functions two- way-delay,two-way-slm and
single-ended-loss are supported on down MEPs on V-VPLS,VPLS and EPIPE
SAPs. This functions are supported in on-demand mode and in proactive mode.
For a description of the individual features and functions that are supported by the
Ethernet-CFM, please refer to the FD 100/320Gbps NT and FX NT IHub System, Management and OAM Guide.
60
3HH-11985-AAAA-TQZZAIssue: 13
Page 61
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
Table 3Acronym callout
AcronymDescription
CCMContinuity check message
CFMConnectivity fault management
ETH-CFMEthernet Connectivity Fault Management
LBMLoopback message
LBRLoopback reply
LTMLinktrace message
LTRLinktrace reply
MEMaintenance entity
MAMaintenance association
MA-IDMaintenance association identifier
MDMaintenance domain
MEPMaintenance association end point
MEP-IDMaintenance association end point identifier
MHFMIP half function
MIPMaintenance domain intermediate point
OpCodeOperational Code
RDIRemote Defect Indication
ETH-CFM capabilities may be deployed in many different Ethernet service
architectures. The Ethernet based SAPs and SDP bindings provide the endpoint on
which the management points may be created. The basic functions can be used in
v-VPLS, VPLS and EPIPE service.
The following functions are supported:
•CFM can be enabled or disabled on a SAP or SDP bindings basis.
•The eight ETH-CFM levels are suggested to be broken up numerically between
customers 7-5, service provider 4-3 and Operator 2-1. These can be configured,
deleted or modified.
Issue: 133HH-11985-AAAA-TQZZA61
Page 62
Services Overview
FD 100/320Gbps NT and FX NT IHub Services Guide
For VPLS and v-VPLS services:
•
•CFM can be enabled or disabled on a SAP or SDP bindings basis.
•Up and/or down MEP with a MEP-ID on a SAP and SDP binding for each MD level
can be configured, modified, or deleted. Each MEP is uniquely identified by the
MA-ID, MEP-ID tuple.
•MEP creation on a SAP is allowed only for Ethernet ports (with null, q-tags, qinq
encapsulations).
•MIP creation on a SAP and SDP binding for each MD level can be enabled and
disabled. MIP creation is automatic or manual when it is enabled. When MIP creation
is disabled for an MD level, the existing MIP is removed.
•MIP creation is not supported on mesh SDP binding
•For EPIPE service:
•CFM can be enabled or disabled on a SDP binding basis.
•Down MEP with an MEP-ID on a SDP binding for each MD level can be configured,
modified, or deleted. Each MEP is uniquely identified by the MA-ID, MEP-ID tuple.
•MIP creation on a SDP binding for each MD level can be enabled and disabled. MIP
creation is automatic or manual when it is enabled. When MIP creation is disabled
for an MD level, the existing MIP is removed.
•Up MEP on a SDP binding, Down MEP, Up MEP and MIP on a SAP are not
supported.
Following are the key configurations for the Ethernet Connectivity Fault
Management. The MD and the MA are configured at system level while MEP and
MIP are configured on SAPs and SDPs of specific service instances.
Configuration of MEP and MIP in v-VPLS and VPLS is detailed in “Configuring
Management Points (MEPs/MIPs) for Ethernet CFM on SAPs”.
•Maintenance Domain (MD):
An MD contains one or more MAs that have the same MD level. There can be
three types of domains: customer domain, provider domain, and operator domain.
Each domain can be an OAM MD and can have one or more MAs.
MD level is an important CFM concept. Eight MD levels (0-7) are defined in CFM.
Level 0 is the lowest level; Level 7 is the highest level.
•Maintenance Association (MA):
A set of Maintenance End Points (MEPs) that have the same MA identifier (MAID)
and maintenance domain (MD) level within one service instance to verify the
integrity of the service.
•MA Endpoint (MEP):
MEPs initiate and terminate CFM messages, and are the origination and
termination points of the CFM operations.
•MD Intermediate Point (MIP):
MIPs receive CFM messages and respond to the originating MEP. A MIP never
initiates messages and does not expect any messages. MIPs respond to
loopback and link trace messages.
62
3HH-11985-AAAA-TQZZAIssue: 13
Page 63
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
3.10.1Configuring ETH-CFM with CLI
This section provides information to configure global ETH-CFM parameters using the
Command Line Interface (CLI).
Topics in this section include:
•Create a Maintenance Domain
•Create a Maintenance Association
3.10.1.1Create a Maintenance Domain
The first step in enabling CFM is to create the MD. Each MD created in the system
has an index, a name, and an MD level. When defining an MD in a system, the level
of the MD must be specified. One MD can contain one or more Maintenance
Associations (MAs). All MAs that belong to the same MD have the same MD level.
Use the following CLI syntax to create a Maintenance Domain.
configure>eth-cfm# info
---------------------------------------------domain 10 format none level 0
exit
3.10.1.2Create a Maintenance Association
After the MD has been created, the MA can be created under the MD. Three items
must be explicitly configured in the MA definition:
•MA Name:
The MAID is formed by the MA name and the MD level.
•Bridge Identification:
The identification of the service in which the MA is deployed
•Remote MEP ID:
The list of IDs for all remote MEPs that belong to this MA.
Use the following CLI Syntax to create a Maintenance Association
config>eth-cfm# info
---------------------------------------------domain 10 format none level 0
association 1 format string name "vpls5"
bridge-identifier 10
remote-mepid 1
exit
exit
Issue: 133HH-11985-AAAA-TQZZA63
Page 64
Services Overview
3.11G.8032 Ethernet Ring Protection Switching
FD 100/320Gbps NT and FX NT IHub Services Guide
After the MD and MAs are created, the MEP can be created under the SAP in the
v-VPLS service instances or SAP/SDP in the VPLS service instances or SDP in the
EPIPE service instances. When creating the MEP, MDs and MAs are associated.
Each MA defined in an MD has a complete view of all of its MEPs. All remote MEPs
have their IDs listed under the MA configuration. The local MEP is associated with
the MA under the configuration of the v-VPLS SAP/VPLS SAP or SDP/EPIPE SDP,
allowing the MA to be aware of all member MEPs in its MEP mesh.
Ethernet ring protection switching offers ITU-T G.8032 specification compliance to
achieve resiliency for Ethernet Layer 2 networks. Similar to G.8031 linear protection
(also called Automatic Protection Switching (APS)), G.8032 (Eth-ring) is also built on
Ethernet OAM and often referred to as Ring Automatic Protection Switching
(R-APS).
Ethernet rings are supported on VPLS SAPs (VPLS, v-VPLS). Eth-ring enables rings
for core network or access network resiliency. A single point of interconnection to
other services is supported. The Eth-ring service is a VLAN service providing
protection for ring topologies and the ability to interact with other protection
mechanisms for overall service protection. This ensures failures detected by Eth-ring
only result in R-APS switchover when the lower layer cannot recover and that higher
layers are isolated from the failure when possible.
Rings are desired in data networks where the native connectivity is laid out in a ring
or there is a desire for simple resilient LAN services. Due to the symmetry and the
simple topology, rings are viewed a good solution for access and core networks
where resilient LANS are required.
Eth-rings use one VID per control per ring instance and use one (typically) or multiple
VIDs for data instances per control instance. A dedicated control VLAN (ERP VLAN)
is used to run the protocol on the control VID. G.8032 controls the active state for the
data VLAN (ring data instances) associated with a control instance. Multiple control
instances allow logically separate rings on the same topology. The Nokia
implementation supports dot1q encapsulation for data ring instances and the control
channel.
3.11.1Overview of G.8032 operation
R-APS messages that carry the G.8032 protocol are sent on dedicated protocol
VLAN called ERP VLAN (or Ring Control Instance). In a revertive case: G.8032
Protocol ensures that one Ring Protection Link (RPL) owner blocks the RPL link.
RPL owner functionality is introduced in iHUB from R5.0.0.1 release.
64
3HH-11985-AAAA-TQZZAIssue: 13
Page 65
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
R-APS messages are periodically sent around in both directions to tell other nodes
in the Ring about the blocked port in the RPL owner node. In non-revertive mode any
link may be the RPLY link.1731 Ethernet OAM CC is the basis of the RAPS
messages used by nodes in the ring to monitor the health of each link in the ring in
both directions. However CCM messages are not mandatory. Other link layer
mechanisms could be considered - for example LOS (Loss of Signal) when the
nodes are directly connected.
Initially each Ring Node blocks one of its links and notifies other nodes in the ring
about the blocked link. Once a ring node in the ring learns that another link is blocked,
the node unblocks its blocked link possibly causing FDB flush in all links of the ring
for the affected service VLANs, controlled by the ring control instance. This
procedure results in unblocking all links but the one link and the ring normal (or idle)
state is reached. In revertive mode the RPL link will be the link that is blocked when
all links are operable after the revert time. In non-revertive mode the RPL link is no
different that other ring links. Revertive mode offers predictability particularly when
there are multiple ring instances and the operator can control which links are block
on the different instances. Each time there is a topology change that affects
Reachability, the nodes may flush the FDB and MAC learning takes place for the
affected service VLANs, allowing forwarding of packets to continue. Figure 5 shows
this operational state.
Figure 5Ring in the initial state
Upon a ring link's failure, a node or nodes detecting the failure (enabled by Y.1731
OAM CC monitoring) send R-APS message in both directions. This allows the nodes
at both ends of the failed link to block forwarding to the failed link preventing it from
becoming active. In revertive mode, the RPL Owner then unblocks the previously
blocked RPL and triggers FDB flush for all nodes for the affected service instances.
The ring is now in protecting state and full ring connectivity is restored. MAC learning
takes place to allow L2 packet forwarding on a ring. Figure 6 shows the failed link
scenario.
Issue: 133HH-11985-AAAA-TQZZA65
Page 66
Services Overview
FD 100/320Gbps NT and FX NT IHub Services Guide
Figure 6Ring in the protection state
Once the failed link recovers, the nodes that blocked the link again send the R-APS
messages indicating no failure this time. This in turn triggers RPL Owner to block the
RPL link and indicate the Blocked RPL link the ring in R-APS message, which when
received by the nodes at the recovered link cause them to unblock that link and
restore connectivity (again all nodes in the ring perform FBD Flush and MAC learning
takes place). The ring is back in the normal (or idle) state.
Within each path, Y.1731 Maintenance Entity Group (MEG) Endpoints (MEPs) are
used to exchange R-APS specific information (specifically to co-ordinate
switchovers) as well as optionally fast Continuity Check Messages (CCM) providing
an inherent fault detection mechanism as part of the protocol. Failure detection of a
working path by one of the mechanisms triggers to move from working to protecting
circuits. Upon failure, re-convergence times are dependent on the failure detection
mechanisms. In the case of Y.1731, the CCM transmit interval determines the
response time. The ISAM supports message timers as 100 milliseconds.
Alternatively, 802.3ah (Ethernet in the First Mile) or simple Loss of Signal can act as
a trigger for a protection switch where appropriate. In case of direct connectivity
between the nodes, there is no need to use Ethernet CCM messaging for liveliness
detection. This can be achieved by not provisioning a MEP on the primary path.
G.8032 supports multiple data channels (VIDs) or instances per ring control instance
(R-APS tag).G.8032 also supports multiple control instances such that each instance
can support RPLs on different links providing for a load balancing capability however
once services have been assigned to one instance the rest of the services that need
to be interconnected to those services must be on the same instance. In other words
each data instance is a separate data VLAN on the same physical topology. When
there is any one link failure or any one node failure in the ring, G.8032 protocols are
capable of restoring traffic between all remaining nodes in these data instances.
66
3HH-11985-AAAA-TQZZAIssue: 13
Page 67
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
Ethernet R-APS can be configured on any port configured for access or hybrid mode
using dot1q encapsulation enabling support for Ethernet RAPS protected services
on the service edge towards the customer site, or within the Ethernet backbone. The
intention of this is to cause minimum disruption to the service during Ethernet RAPS
failure detection and recovery.
In the ISAM implementation the Ethernet Ring is built from a VPLS (or v-VPLS)
service on each node with VPLS SAPs that provides Ring path with SAPs. As a
result, most of the VPLS SAP features are available on Ethernet rings if desired. This
results in a fairly feature rich ring service.
The control tag defined under each eth-ring is used for encapsulating and forwarding
the CCMs and the G.8032 messages used for the protection function. If a failure of
a link or node affects an active Ethernet ring segment, the services will fail to receive
the CC messages exchanged on that segment or will receive a fault indication from
the Link Layer OAM module.
For fault detection using CCMs three CC messages plus a configurable hold-off timer
must be missed for a fault to be declared on the associated path. The latter
mechanism is required to accommodate the existence of additional, 50 ms resiliency
mechanism in the optical layer. After it receives the fault indication, the protection
module will declare the associated ring link down and the G.8032 state machine will
send the appropriate messages to open the RPL and flush the learned addresses.
Flushing is triggered by the G.8032 state machine and the ISAM implementation
allows flooding of traffic during the flushing interval to expedite traffic recovery.
3.11.2Sample configuration
Configuring eth-ring instance and paths:
configure eth-ring 1
description "RPL owner mode"
revert-time 100
guard-time 5
ccm-hold-time down 100 up 200
rpl-node owner
path a nt-a:xfp:1 raps-tag 100
description "To A ring link"
eth-cfm
mep 1 domain 1 association 1
control-mep
ccm-enable
no shutdown
exit
exit
no shutdown
exit
path b lag-10 raps-tag 100
description "to B Ring Link"
eth-cfm
mep 2 domain 1 association 2
control-mep
ccm-enable
Issue: 133HH-11985-AAAA-TQZZA67
Page 68
Services Overview
FD 100/320Gbps NT and FX NT IHub Services Guide
no shutdown
exit
exit
no shutdown
no shutdown
exit
Associating eth-ring instance to a sap:
Configure service
vpls 20 customer 1 v-vpls vlan 100 create
description "Ring Control VID 100"
sap nt-a:xfp:1:100 eth-ring 1 create //control sap for
path-a
exit
sap lag-10:100 eth-ring 1 create // control sap for path-b
exit
no shutdown
exit
exit
3.11.3OAM considerations
Ethernet CFM can be enabled on each individual path under an Ethernet ring. Only
down MEPs can be configured on each of them and CCM sessions can be enabled
to monitor the liveliness of the path using intervals of 100 msec.
Different CCM intervals can be supported on the path a and path b in an Ethernet
ring. CFM is optional if the hardware supports Loss of Signal for example.
Up MEPs on service SAPs which multicast into the service and monitor the active
path may be used to monitor services.
3.11.4QinQ RAPS-Tag Considerations
From release R5.0.0.1, its possible to configure Double tagged (QinQ) Eth-ring path
RAPS-Tag over an Dot1q encapsulated Ethernet port.
With respect to iHub’s behavior, whenever a QinQ Raps-Tag is configured, it sends
out RAPS and CCM packets with double tags over the ring-ports.
Also iHub can receive double tagged RAPS and CCM packets from the peer-nodes,
but always process the corresponding packets whose outer-vlan matches the control
vlan; the inner vlan is never taken as input for validation or control plane processing.
The control vlan v-vpls configuration will remain singled tagged.
68
This facility is introduced in R5.0.0.1 to allow interoperation with 1830 PSS switch
which sends and receives only double tagged RAPS and CCM packets.
3HH-11985-AAAA-TQZZAIssue: 13
Page 69
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
3.11.5Duplex NT ERPS Performance considerations
This section suggests actions to be performed by the operator to optimize
performance impacts in the event of Active-NT switchover on a Duplex
Load-Balanced NT.
Handling NT Switchover Scenario in a Load-balanced Duplex NT:
•Most Preferred Approach: Use Multi NT lags (lags having ports from both NT), to
prevent NT Switchover from triggering ERP Switch. Forwarding databases (L2
Table, Multicast FIB, ARP, etc.) are not affected.
In case if Multi NT lags are not used, and each ERPS path is on different NT:
•Controlled Switchover case: Do a manual switchover of the ERPS path in the RPL
owner (incase of RPL owner is not ISAM) before administratively triggering NT
switchover in one of the NTs. This should be done to prevent extra outage during
NT switchover due to NT switchover delay, i.e. traffic is already switched to the
newly to-be Active NT before the NT switchover.
3.11.6Support Service and Solution Combinations
The Ethernet rings are supported Layer 2 service, VPLS and v-VPLS instances. The
following considerations apply:
•Only ports in access or hybrid mode can be configured as eth-ring paths.
•Dot1q ports are supported as eth-ring path members.
•A mix of regular and multiple eth-ring SAPs and PWs can be configured in the
same services.
3.11.7Configuration guide-lines
Below are the steps for configuring a ring path:
1Configure eth-ring
2Configure one of the ring paths with a control VLAN i.e r-aps tag. (a free control
VLAN should be available, that is, no SAP should exist with control VLAN)
3It is not allowed to make the path admin-up until an eth-cfm mep is configured for
that path.
4Configure eth-cfm mep for the ring path.
5Make the path admin-up.
6Enabling of CCM on eth-ring MEP is optional (required for CCM based signal
failure detection i.e for peers not connected directly).
Issue: 133HH-11985-AAAA-TQZZA69
Page 70
Services Overview
FD 100/320Gbps NT and FX NT IHub Services Guide
7If ccm-errors need not be propagated to the ring path (operational status),
configure all the defects as low-prio-defects for the eth-cfm mep of the
corresponding path.
8Configure a control SAP (on a v-VPLS service) for the ring path with VLAN as
r-aps tag.
Below are the steps for unconfiguring a ring path:
1Unconfigure the control SAP (as like any other sap) corresponding to the path to
be un-configured
2Shut down the ring path
3Shut down the eth-cfm mep on the ring-path
4Unconfigure the eth-cfm mep on the ring-path
5Unconfigure the ring path
Below are the CLI errors popped with some violations to the above guide-lines:
*A:FAD-Chassis# show servicesap-using
==================================================================
Service Access Points
==================================================================
PortIdSvcIdIng.Egr.AdmOpr
-----------------------------------------------------------------Number of SAPs : 7
-----------------------------------------------------------------==================================================================
A:FAD-Chassis>configure>eth-cfm# domain 100 format none level 4
*A:FAD-Chassis>configure>eth-cfm>domain# association 1 format string name
"dummy"
*A:FAD-Chassis>configure>eth-cfm>domain>assoc#
*A:FAD-Chassis>configure>eth-cfm>domain>assoc# ccm-interval 100ms
*A:FAD-Chassis>configure>eth-cfm>domain>assoc# exit all
*A:FAD-Chassis# configure eth-ring 10
*A:FAD-Chassis>configure>eth-ring# no shutdown
*A:FAD-Chassis>configure>eth-ring#
*A:FAD-Chassis>configure>eth-ring# path a lag-30 raps-tag 1001
INFO: ERMGR #1004 Already configured - SAP lag-30:1001 already configured
*A:FAD-Chassis>configure>eth-ring# path a lag-30 raps-tag 1002
*A:FAD-Chassis>configure>eth-ring>path# no shutdown
INFO: ERMGR #1001 Not permitted - must configure eth-cfm MEP first
*A:FAD-Chassis>configure>eth-ring>path>eth-cfm# mep 11 domain 100
association 1
*A:FAD-Chassis>configure>eth-ring>path>eth-cfm>mep# exit
*A:FAD-Chassis>configure>eth-ring>path>eth-cfm# exit
*A:FAD-Chassis>configure>eth-ring>path# no shutdown
70
3HH-11985-AAAA-TQZZAIssue: 13
Page 71
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
Base Route (Core 1)
NT
NP
DHCP Relay/
Agent
IP Routing
DHCP
server
LT Po r tLTONU
Broadcast MAC/Broadcast IP Lease Query (UDP)
Unicast MAC/Unicast IP Lease Query Response (UDP/TCP)
Unicast MAC (LT MAC)/Broadcast IP Lease Query Response (UDP)
LQ Request flow
Unicast MAC/Unicast IP Lease Query (UDP/TCP)
DHCP
server
Network port
Legend:
*A:FAD-Chassis>configure>eth-ring>path# eth-cfm
*A:FAD-Chassis>configure>eth-ring>path>eth-cfm# mep 11 domain 100
association 1
*A:FAD-Chassis>configure>eth-ring>path>eth-cfm>mep# control-mep
*A:FAD-Chassis>configure>eth-ring>path>eth-cfm>mep# no shutdown
*A:FAD-Chassis# configure service vpls 1002 customer 1 v-vpls vlan 1002
*A:FAD-Chassis>configure>service>vpls$ sap lag-30:1002
MINOR: SVCMGR #1602 The SAP-id is already in use - lag-30:1002 is already
configured under Ethernet ring 10
*A:FAD-Chassis>configure>service>vpls$ sap lag-30:1002 eth-ring 10
*A:FAD-Chassis>configure>service>vpls>sap$
*A:FAD-Chassis>configure>service>vpls>sap$ exit
*A:FAD-Chassis>configure>service>vpls# no shutdown
3.12DHCP Lease Query
DHCP Lease Query allows ISAM to learn backs its DHCP IPv4 bindings, IPv6
bindings, and IPV6 PD routes, from the configured DHCP servers using lease query
after power on reset.
Figure 7DHCP Lease Query
IHUB involves transactions in this lease query only when L3 DHCP relay is enabled,
and supports DHCPv4 single lease query based on IP address, and DHCPv4 and
DHCPv6 bulk lease query based on remote ID. Lease query based on other options
is not supported. IHUB involves transactions in this lease query only in base router
(IES) context, and maintains a maximum of 95 lease query sessions. That is to say,
Issue: 133HH-11985-AAAA-TQZZA71
Page 72
Services Overview
3.13DHCP Remote ID Check
3.14GRE Tunnels Overview
FD 100/320Gbps NT and FX NT IHub Services Guide
with 95 sessions for each type such as SLQ, BLQ IPv4, and BLQ IPv6, and with 5
queries x 19 LTs. IHUB supports lease query messages generated by the LT, and
legacy behavior of forwarding LQ packets will be maintained. For bulk lease query,
there will be system-wide support for a maximum of 8 TCP servers (first 8 configured
servers).
DHCP Remote ID Check allows ISAM to enable or disable the remote ID verification.
Remote ID will be verified when local proxy ARP is enabled.
When a ping between two CPEs is initiated, an ARP request is sent to ONU and, if
the ONU does not have the L2 flooding capacity, then to ISAM. If local proxy ARP is
enabled in ISAM, the DHCP remote ID of the source and destination CPEs are
verified. If both CPEs have the same remote ID, the ARP packets are dropped. When
DHCP remote ID check is disabled, ISAM does not drop the ARP packets and
responds to the request with its MAC address.
ISAM supports tunneling for unicast IPv4 traffic using GRE-IPv4 encapsulation when
traveling on IPv4 static routes with nexthop as the tunnel endpoint.
Figure 8Tunnels using GRE-IPv4 encapsulation
Tunnel src IP:
164.251.12.1/30
Tunnel-1
sap tunnel-1.private:200
10.0.0.2/30
C
VPRN 1
12.47.10.1/24
sap tunnel-1.public:201
164.251.12.2/30
B
IES 21
A
sap tunnel-1.public:201
164.251.12.1/30
Internet
12.47.10.0/24
Tunnel-1 is a logical object in ISAM.
The following three interfaces form the GRE tunnel as it travels to the endpoint:
A
IES 21
12.47.10.2/24
Tunnel-1
B
Tunnel src IP:
164.251.12.2/3
sap tunnel-1.private:200
10.0.0.1/30
C
VPRN 1
26449
72
•The interface to the Internet
•The tunnel destination can only be reached using a SAP
•This interface provides IP reachability
3HH-11985-AAAA-TQZZAIssue: 13
Page 73
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
Public tunnel interface
•
•This interface can be either an IES or VPRN interface
•This interface represents the public side of the GRE tunnel
•Private tunnel interface
•This interface is the VPRN interface
•This interface represents the private side of the GRE tunnel
•The address for this interface needs to be part of the same subnet as the public
interface address
3.14.1Public Tunnel SAPs
A VPRN or IES service (the delivery service) must have at least one IP interface
associated with a public tunnel SAP in order to receive and process GRE packets
associated with the GRE tunnel.
The public tunnel SAP has the format of tunnel-1.public:<index>, as shown in the
following CLI example:
config service ies 199 customer 1 create
interface “public-1” create
address 64.251.12.1/30
exit all
sap tunnel-1.public:200 create
3.14.2Private Tunnel SAPs
A VPRN service must have an IP interface to a GRE tunnel in order to forward IP
packets into the tunnel, where they are GRE encapsulated, and to receive IP packets
from the tunnel after encapsulation has been removed. The IP interface is associated
with a private tunnel SAP.
The private tunnel SAP has the format of tunnel-1.public:<index>, as shown in the
following CLI example where a GRE tunnel is configured under the SAP:
config service vprn 1 customer 1 create
interface “gre tunnel to ce1” tunnel create
address 10.0.0.1/30
sap tunnel-1.private:210 create
gre-tunnel ”to ce1” to 10.0.0.2
source 64.251.12.1
remote-ip 12.47.10.33
delivery-service 199
dscp afl1
no shutdown
exit
ingress
egress
exit all
Issue: 133HH-11985-AAAA-TQZZA73
Page 74
Services Overview
3.14.3GRE Tunnel Configuration
FD 100/320Gbps NT and FX NT IHub Services Guide
In the above example, the IP address 10.0.0.1 is the address of the GRE tunnel
endpoint from the perspective of the payload IP packets. This address belongs to the
address space of the VPRN 1 service and is not exposed to the public IP network
carrying GRE encapsulated packets. An IP interface associated with a private tunnel
SAP does not support unnumbered operations.
To associate a GRE tunnel with a private tunnel SAP, the GRE tunnel object should
configured under the SAP. When creating a GRE tunnel, the “to” keyword followed
by the private IP address of the remote tunnel endpoint is mandatory. If this remote
IP address is not within the subnet of the local private endpoint then the tunnel will
not come up. In the CLI sub-tree under GRE tunnel, configure the following
commands:
•The source address of the GRE tunnel
This is source IPv4 address of GRE encapsulated packets sent by the delivery
service. It must be an address in the subnet of the associated public tunnel SAP
interface.
•The remote IP address
If this address is reachable in the delivery service (there is an existing route) then
this is the destination IPv4 address of the GRE encapsulated packets sent by the
delivery service.
•The delivery service
This is the ID or name of the IES or VPRN service where GRE encapsulated
packets are injected and terminated. The deliver service can be the same service
where the private tunnel SAP interface resides.
74
The DSCP marking in the outer IP header of GRE encapsulated packets. If this
marking is not configured, the default setting is to copy the DSCP from the inner IP
header to the outer IP Header.
The show gre tunnel command allows the operator to view information about either
specific or all configured GRE tunnels. This command displays the following
information for each tunnel:
•service ID that owns the tunnel
•private tunnel SAP that owns the tunnel
•tunnel name
•source address
•remote IP address
•local (private) address
•destination (private) address
•delivery service: only ID (int value) allowed
•DSCP
•admin state
3HH-11985-AAAA-TQZZAIssue: 13
Page 75
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
oper state
•
•type (GRE-only)
3.14.4Statistics Collection
GRE tunnel statistics are enabled or disabled dynamically using CLI commands. The
statistics counter includes the number of Rx packets, Rx bytes, Tx packets, and Tx
bytes.
A maximum of 90 GRE tunnels can be enabled to collect statistics simultaneously.
3.14.5OAM Interactions
Ingress or egress traffic for an IES service associated with GRE tunnels can be
mirrored like other traffic. The ability to ping the remote end private interface IP is also
supported. ISAM can respond to the ping, traceroute over GRE encapsulation.
3.15DHCP6 Relay Prefix Stability
DHCP6 Prefix Stability allows ISAM to maintain the IPv6 Prefixes Delegated to a
device, when the device is moved from one ISAM to another ISAM. When device
movement happens, it is identified as follows:
•Offline Notification
When a device is brought down, an offline notification is sent to ISAM and a hold
down timer is initiated. When the device comes back online before the hold down
timer expires, the route table will be unaffected. If the timer expires, then route
cleanup will occur. DHCP6 lease states and MAC table entry will also be cleared.
•Route received by means of IGP
For a DHCPv6 PD route entry, an IGP route can be received. In such scenarios,
a ND reachability check is initiated and if the managed route entry's next hop is
reachable, then a Duplicate PD Alarm is raised to inform the administrator about
an invalid DHCP6 PD delegation. The alarm will be cleared when the invalid route
is removed.
Duplicate PD Alarm will be generated when:
•An IGP route is received for an existing DHCPv6 PD route entry which has a
reachable next hop
•A DHCPv6 PD route is received for an existing IGP route
Issue: 133HH-11985-AAAA-TQZZA75
Page 76
Services Overview
FD 100/320Gbps NT and FX NT IHub Services Guide
The same DHCPv6 PD is delegated to two different devices
•
Note — In this scenario, the PD is not delegated to the second
device, since it is considered to be an invalid delegation.
Duplicate PD Alarm will be cleared in the following scenarios:
•When the received IGP route is withdrawn by the IGP routing protocol
•When the lease time for a DHCPv6 PD entry expires
•When the device goes offline
•When an administrator manually clears an alarm by clearing the DHCPv6
lease-state entry using the CLI command provided.
Command: clear service id <service-id no> dhcp6 lease-state
Note 1 — For offline notification to be processed properly, it is
expected that prefix-stability is enabled in the relevant
interface.
Note 2 — DPOE offline notification will be sent to IHUB through
SNMP, and therefore SNMP context "ihub" must be configured
in Core-0.
Note 3 — When a route is received from more than one IGP
routing protocol, an alarm will be generated when an IGP route
is received, and cleared when an IGP route is withdrawn.
3.16Global Services Command Reference
3.16.1Command Hierarchies
•Customer Management Commands
•Ethernet CFM Global Commands
•Ethernet Ring Global Commands
•Show Commands
•Tools
76
3HH-11985-AAAA-TQZZAIssue: 13
Page 77
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
3.16.1.1Customer Management Commands
configure
— service
— customer customer-id [create]
—[no] customer customer-id
— contact contact-information
— no contact contact-information
— description description-string
— sdp sdp-id mpls
— no sdp sdp-id
— no description
—[no] adv-mtu-override
— description description-string
— no description
— far-end ip-addr
— no far-end
—[no] ldp
—[no] lsp lsp-name
— path-mtu octets
— no path-mtu
— signaling [off | tldp]
— no shutdown
— vlan-vc-etypeetype
— no vlan-vc-etype
3.16.1.2Ethernet CFM Global Commands
configure
— eth-cfm
— domain md-index [format {dns|mac|none|string}] name md-name level level
— domain md-index
— no domain md-index
— association ma-index [format {icc-based|integer|string|vid|vpn-id}] name ma-name
— association ma-index
— no association ma-index
—[no] bridge-identifier bridge-id
— mhf-creation {default | none | explicit}
— no mhf-creation
— ccm-interval interval
— no ccm-interval
—slm
— y1731pm
— [no] domain md-index association ma-index mep mep-idsessionsession-id create
—[no] remote-mepid mep-id
— [no] inactivity-timer
— [no] shutdown
priority priority
—
— period period
— data-size data-size
— measurement-period period
— mac-address mac-address
— type [none|two-way-delay | two-way-slm | single-ended-loss]
3.16.1.3Ethernet Ring Global Commands
configure
— eth-ring ring-index
—[no] revert-time time
—[no] ccm-hold-time { [down down-timeout] [up up-timeout] }
—[no] description description-string
—[no] guard-time time
—[no] node-id xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx
—[no] rpl-node {owner}
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
3.17.1.1description
Table 4description command
ItemDescription
Syntaxdescription description-string
no description
Contextconfigure>service>customer
configure>eth-ring
configure>eth-ring>path
DescriptionThis command creates a text description stored in the configuration file for a configuration
DefaultNo description associated with the configuration context.
Parametersdescription-string — The description character string. Allowed values are any string up to 80
context.
The description command associates a text string with a configuration context to help identify
the content in the configuration file.
The no form of this command removes the string from the configuration.
characters long composed of printable, 7-bit ASCII characters. If the string contains special
characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
Table 5description command
ItemDescription
Syntaxdescription description-string
no description
Contextconfigure>service>sdp
DescriptionThis command creates a text description stored in the configuration file for a configuration
DefaultNo description associated with the configuration context.
Parametersdescription-string — The description character string. Allowed values are any string up to 160
context.
The description command associates a text string with a configuration context to help identify
the content in the configuration file.
The no form of this command removes the string from the configuration.
characters long composed of printable, 7-bit ASCII characters. If the string contains special
characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
3.17.2Customer Management Commands
Issue: 133HH-11985-AAAA-TQZZA79
Page 80
Services Overview
3.17.2.1customer
FD 100/320Gbps NT and FX NT IHub Services Guide
Table 6customer command
ItemDescription
Syntaxcustomer customer-id [create]
no customer customer-id
Contextconfigure>service
DescriptionThis command creates a customer ID and customer context used to associate information with
a particular customer. Services can later be associated with this customer at the service level.
Each customer-id must be unique. The create keyword must follow each new customer
customer-id entry.
Enter an existing customer customer-id (without the create keyword) to edit the customer’s
parameters.
Default customer 1 always exists on the system and cannot be deleted.
The no form of this command removes a customer-id and all associated information. Before
removing a customer-id, all references to that customer in all services must be deleted or
changed to a different customer ID.
Parameterscustomer-id — Specifies the ID number to be associated with the customer, expressed as an
integer.
Values: 1...2147483647
3.17.2.2contact
Table 7contact command
ItemDescription
Syntaxcontactcontact-information
Contextconfigure>service>customer
DescriptionThis command allows you to configure contact information for a customer.
DefaultNo contact information is associated with the customer-id.
Parameterscontact-information — The customer contact information entered as an ASCII character string
no contactcontact-information
Include any customer-related contact information such as a technician’s name or account
contract name.
The no form of this command removes the contact information from the customer ID.
up to 80 characters in length. If the string contains special characters (#, $, spaces, etc.), the
entire string must be enclosed within double quotes. Any printable, seven bit ASCII characters
may be used within the string.
80
3HH-11985-AAAA-TQZZAIssue: 13
Page 81
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
3.17.3SDP Commands
3.17.3.1sdp
Table 8sdp command
ItemDescription
Syntaxsdp sdp-id mpls
no sdp sdp-id
Contextconfigure>service
DescriptionThis command creates or edits a Service Distribution Point (SDP). SDPs must be explicitly
Defaultnone
Parameterssdp-id — The SDP identifier.
configured.
An SDP is a logical mechanism that ties a far-end ISAM to a particular service without having
to specifically define far end SAPs. Each SDP represents a method to reach a ISAM router.
ISAM supports both signaled and non-signaled Label Switched Paths (LSPs) through the
network. Non-signaled paths are defined at each hop through the network. Signaled paths are
communicated via ldp protocol.
SDPs are created and then bound to services. Many services may be bound to a single SDP.
The operational and administrative state of the SDP controls the state of the SDP binding to
the service.
If sdp-id does not exist, a new SDP is created. When creating an SDP, the mpls keyword must
be specified. SDPs are created in the admin down state (shutdown) and the no shutdown
command must be executed once all relevant parameters are defined and before the SDP can
be used.
If sdp-id exists, the current CLI context is changed to that SDP for editing and modification. For
editing an existing SDP, the mpls keyword is not specified. If the keyword is specified for an
existing sdp-id, an error is generated and the context of the CLI will not be changed to the
specified sdp-id.
The no form of this command deletes the specified SDP. Before an SDP can be deleted, it
must be administratively down (shutdown) and not bound to any services. If the specified SDP
is bound to a service, the no sdp command will fail generating an error message specifying
the first bound service found during the deletion process. If the specified sdp-id does not exist
an error will be generated.
Values: 1...17407
mpls — Specifies the SDP will use MPLS encapsulation and one or more LSP tunnels to
reach the far-end ISAM. Multiple MPLS SDPs may be created to a given destination ISAM.
Multiple MPLS SDPs to a single destination ISAM are helpful when they use divergent paths.
3.17.3.2adv-mtu-override
Issue: 133HH-11985-AAAA-TQZZA81
Page 82
Services Overview
3.17.3.3far-end
FD 100/320Gbps NT and FX NT IHub Services Guide
Table 9adv-mtu-override command
ItemDescription
Syntax[no] adv-mtu-override
Contextconfigure>service>sdp sdp-id
DescriptionThis command overrides the advertised VC-type MTU. When enabled, the ISAM signals a VC
MTU equal to the service MTU (includes the Layer 2 header). Under normal operations it will
advertise the service MTU minus the Layer 2 header. In the receive direction, it will accept
either one.
The no form of the command disables the VC-type MTU override.
Defaultno adv-mtu-override
Table 10far-end command
ItemDescription
Syntaxfar-end ip-address
no far-end
Contextconfigure>service>sdp sdp-id
DescriptionThis command configures the system IP address of the far-end destination ISAM router for the
Defaultnone
Parametersip-address — The system address of the far-end ISAM for the SDP in dotted decimal notation.
Service Distribution Point (SDP) that is the termination point for a service.
The far-end IP address must be explicitly configured. The destination IP address must be a
ISAM system IP address.
The far-endip-address is used to check LSP names when added to the SDP. If the “to IP
address” defined within the LSP configuration does not exactly match the SDP far-end ip-address, the LSP will not be added to the SDP and an error will be generated.
An SDP cannot be administratively enabled until a far-end ip-address is defined. The SDP is
operational when it is administratively enabled (no shutdown) and the far-end ip-address is
contained in the IGP routing table as a host route. OSPF ABRs should not summarize host
routes between areas. This can cause SDPs to become operationally down. Static host routes
(direct and indirect) can be defined in the local ISAM to alleviate this issue.
The no form of this command removes the currently configured destination IP address for the
SDP. The ip-address parameter is not specified and will generate an error if used in the no
far-end command. The SDP must be administratively disabled using the configure service
sdp shutdown command before the no far-end command can be executed. Removing the
far-end IP address will cause all lsp-name associations with the SDP to be removed.
82
3HH-11985-AAAA-TQZZAIssue: 13
Page 83
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
3.17.3.4ldp
Table 11ldp command
ItemDescription
Syntax[no] ldp
Contextconfigure>service>sdp sdp-id
DescriptionThis command enables LDP-signaled LSPs on MPLS-encapsulated SDPs.
In MPLS SDP configurations either one LSP can be specified or LDP can be enabled. The
SDP ldp and lsp commands are mutually exclusive. If an LSP is specified on an MPLS SDP,
then LDP cannot be enabled on the SDP. To enable LDP on the SDP when an LSP is already
specified, the LSP must be removed from the configuration using the no lsplsp-name
command.
Alternatively, if LDP is already enabled on an MPLS SDP, then an LSP cannot be specified on
the SDP. To specify an LSP on the SDP, the LDP must be disabled. The LSP must have
already been created in the configure>router>mpls context with a valid far-end IP address.
Defaultno ldp (disabled)
3.17.3.5lsp
Table 12lsp command
ItemDescription
Syntaxlsplsp-name
Contextconfigure>service>sdp sdp-id
(1 of 2)
no lsp lsp-name
Issue: 133HH-11985-AAAA-TQZZA83
Page 84
Services Overview
FD 100/320Gbps NT and FX NT IHub Services Guide
ItemDescription
DescriptionThis command creates associations between one or more label switched paths (LSPs) and an
Multi- Protocol Label Switching (MPLS) Service Distribution Point (SDP). This command is
implemented only on MPLS-type encapsulated SDPs.
In MPLS SDP configurations either one LSP can be specified or LDP can be enabled. The SDP
ldp and lsp commands are mutually exclusive. If an LSP is specified on an MPLS SDP, then
LDP cannot be enabled on the SDP. To enable LDP on the SDP when an LSP is already
specified, the LSP must be removed from the configuration using the no lsp lsp-name
command.
Alternatively, if LDP is already enabled on an MPLS SDP, then an LSP cannot be specified on
the SDP. To specify an LSP on the SDP, the LDP must be disabled. The LSP must have
already been created in the configure>router>mpls context. with a valid far-end IP address.
If no LSP is associated with an MPLS SDP, the SDP cannot enter the operationally up state.
The SDP can be administratively enabled (no shutdown) with no LSP associations. The
lsp-name may be shutdown, causing the association with the SDP to be operationally down
(the LSP will not be used by the SDP).
LSP SDPs also require that the TLDP signaling is specified.
The no form of this command deletes the LSP association from an SDP. If the lsp-name does
not exist as an association or as a configured LSP, no error is returned. An lsp-name must be
removed from all SDP associations before the lsp-name can be deleted from the system. The
SDP must be administratively disabled (shutdown) before the last lsp-name association with
the SDP is deleted.
Defaultnone
Parameterslsp-name — The name of the LSP to associate with the SDP. An LSP name is case sensitive
and is limited to 32 ASCII 7-bit printable characters with no spaces. If an exact match of
lsp-name does not already exist as a defined LSP, an error message is generated. If
thelsp-name does exist and the LSP to IP address matches the SDP far-end IP address, the
association is created.
(2 of 2)
3.17.3.6path-mtu
Table 13path-mtu command
ItemDescription
Syntaxpath-mtu octets
no path-mtu
Contextconfigure>service>sdp sdp-id
DescriptionThis command configures the Maximum Transmission Unit (MTU) in bytes that the Service
DefaultThe default path-mtu defined on the system for the type of SDP is used.
Distribution Point (SDP) can transmit to the far-end ISAM router without packet dropping or IP
fragmentation overriding the SDP-type default path-mtu.
The default SDP-type path-mtu can be overridden on a per-SDP basis.
The no form of this command removes any path-mtu defined on the SDP and the SDP will
use the system default for the SDP type.
84
3HH-11985-AAAA-TQZZAIssue: 13
Page 85
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
3.17.3.7signaling
Table 14signaling command
ItemDescription
Syntaxsignaling {off | tldp}
Contextconfigure>service>sdp sdp-id
DescriptionThis command specifies the signaling protocol used to obtain the ingress and egress labels in
Defaulttdlp
Parametersoff — Ingress and egress signal auto-labeling is not enabled. If this parameter is selected, then
frames transmitted and received on the SDP. When signaling is off then labels are manually
configured when the SDP is bound to a service. The signaling value can only be changed while
the administrative status of the SDP is down.
The no form of this command is not applicable. To modify the signaling configuration, the SDP
must be administratively shut down and then the signaling parameter can be modified and
re-enabled.
each service using the specified SDP must manually configure VPN labels. This configuration
is independent of the SDP’s transport type, GRE, MPLS (RSVP or LDP).
tldp — Ingress and egress signaling auto labeling is enabled.
3.17.3.8shutdown
Table 15shutdown command
ItemDescription
Syntaxsignaling {off | tldp}
Contextconfigure>service>sdp sdp-id
DescriptionThis command administratively disables an entity. When disabled, an entity does not change,
(1 of 2)
reset, or remove any configuration settings or statistics.
The operational state of the entity is disabled as well as the operational state of any entities
contained within. Many objects must be shut down before they may be deleted.
Services are created in the administratively down (shutdown) state. When a no shutdown
command is entered, the service becomes administratively up and then tries to enter the
operationally up state. Default administrative states for services and service entities is
described below in Special Cases.
The no form of this command places the entity into an administratively enabled state.
Issue: 133HH-11985-AAAA-TQZZA85
Page 86
Services Overview
3.17.3.9vlan-vc-etype
FD 100/320Gbps NT and FX NT IHub Services Guide
ItemDescription
Special CasesService Admin State - Bindings to an SDP within the service will be put into the out-of-service
state when the service is shutdown. While the service is shutdown, all customer packets are
dropped and counted as discards for billing and debugging purposes.
SDP (global) - When an SDP is shutdown at the global service level, all bindings to that SDP
are put into the out-of-service state and the SDP itself is put into the administratively and
operationally down states. Packets that would normally be transmitted using this SDP binding
will be discarded and counted as dropped packets.
SDP (service level) - Shutting down an SDP within a service only affects traffic on that service
from entering or being received from the SDP. The SDP itself may still be operationally up for
other services.
(2 of 2)
Table 16vlan-vc-etype command
ItemDescription
Syntaxvlan-vc-etype etype
no vlan-vc-etype
Contextconfigure>service>sdp
DescriptionThis command enables the configuration of an alternate TPID value to be used at the SDP
Defaultno vlan-vc-etype
Parametersetype - specifies the etype value
level.
The no form of this command disables the configuration of an alternate TPID value..
Values are:
•hexadecimal: 0x0600 to 0xffff
•decimal: 1536 to 65535
3.17.4Ethernet CFM Global Commands
3.17.4.1eth-cfm
86
3HH-11985-AAAA-TQZZAIssue: 13
Page 87
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
Table 17eth-cfm command
ItemDescription
Syntaxeth-cfm
Contextconfigure
DescriptionThis command enables the context to configure 802.1ag CFM parameters
3.17.4.2domain
Table 18domain command
ItemDescription
Syntaxdomain md-index [format {dns | mac | none | string}] name md-name level level
levellevel - Specifies the integer identifying the maintenance domain level (MD Level). Higher
numbers correspond to higher maintenance domains, those with the greatest physical reach,
with the highest values for customers' CFM packets. Lower numbers correspond to lower
maintenance domains, those with more limited physical reach, with the lowest values for single
bridges or physical links.
Values: 0...7
Issue: 133HH-11985-AAAA-TQZZA87
Page 88
Services Overview
3.17.4.3association
FD 100/320Gbps NT and FX NT IHub Services Guide
Table 19association command
ItemDescription
Syntaxassociation ma-index [format {icc-based | integer |string | vid | vpn-id}] name ma-name
association ma-index
no association ma-index
Contextconfigure>eth-cfm>domain
DescriptionThis command configures the Maintenance Association (MA) for the domain
The no form of the command removes the MA index parameters from the configuration.
Parametersma-index — Specifies the Maintenance Association (MA) index value.
Values: 1...4294967295
format {icc-based | integer | string | vid | vpn-id} - Specifies a value that represents the type
(format).
Values:
icc-based: Allows for exactly a 13 character name.
integer: 0...65535 (integer value 0 means the MA is not attached to a VID.)
string: raw ascii
vid: 0...4095
vpn-id: RFC-2685, Virtual Private Networks Identifier xxx:xxxx, where x is a value between 00
and FF. For example 00164D:AABBCCDD
Default: integer
namema-name - Specifies a generic Maintenance Association (MA) name.
Values: 1...43 characters
88
3.17.4.4bridge-identifier
Table 20bridge-identifier command
ItemDescription
Syntax[no] bridge-identifier bridge-id
Contextconfigure>eth-cfm>domain>association
DescriptionThis command configures the service ID for the domain association. The value must be
configured to match the service-id of the service where MEPs for this association will be
created. Note that there is no verification that the service with a matching service-id exists. This
is not used for facility MEPs as they are not tied to services.
The no form of the command removes the service ID from the domain association.
(1 of 2)
3HH-11985-AAAA-TQZZAIssue: 13
Page 89
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
ItemDescription
Parametersbridge-id - Specifies the bridge ID for the domain association.
association- Maintenance Association for the Domain
mep - CFM Maintenance Endpoint
session - creates a session for the given mep
3.17.4.10shutdown
Table 26shutdown command
ItemDescription
Syntaxshutdown
Contextconfigure>eth-cfm>y1731pm>domain
DescriptionIndicates the desired administrative state of the y1731pm session.
DefaultDisabled
3.17.4.11priority
Table 27priority command
ItemDescription
Syntaxpriority type
Contextconfigure>eth-cfm>y1731pm>domain
DescriptionThe value of Priority specifies the priority used in the generated test frame for the Y1731 PM
The no form of the command will admin enable the y1731pm session.
(LM/DM/SLM) session.
This parameter can be set only when admin status is set to disabled.
The no form of the command reverts the value to the default.
(1 of 2)
Issue: 133HH-11985-AAAA-TQZZA91
Page 92
Services Overview
3.17.4.12period
FD 100/320Gbps NT and FX NT IHub Services Guide
ItemDescription
Default7
Parameterspriority — <0,1,2…7>
(2 of 2)
Table 28period command
ItemDescription
Syntaxperiod period
Contextconfigure>eth-cfm>y1731pm>domain
DescriptionThe value of period specifies the time to wait between the transmission of one OAM request
and the next. This parameter can be set only when admin status is set to disabled. The
applicability, range, and default value of this object vary with type, as described below.
The no form of the command reverts the value to the default.
Defaulttwo-way-slm — 1
two-way-delay — 1
single-end-loss — 60
Parameterstwo-way-slm (SLM) — 1...10
two-way-delay (DM) — 1...10
single-end-loss (LM) — 60...300
92
3.17.4.13data-size
Table 29data-size command
ItemDescription
Syntaxdata-size data-size
Contextconfigure>eth-cfm>y1731pm>domain
DescriptionSpecifies the number of octets in the Value field of the Data TLV of the Ethernet CFM packet.
If zero is specified, the packet has no Data TLV.
This parameter is optional and is valid only if type is specified as two-way-slm.
The no form of the command reverts the value to the default.
Default0
Parametersdata-size — [0...1500]
3HH-11985-AAAA-TQZZAIssue: 13
Page 93
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
3.17.4.14measurement-period
Table 30measurement-period command
ItemDescription
Syntaxmeasurement-period period
Contextconfigure>eth-cfm>y1731pm>domain
DescriptionThe value of measurement-period specifies the time after which the synthetic loss calculation
Default300 seconds
Parametersperiod — [60|300]
is made periodically. If the value of this object is set to 'X' seconds, loss measurement
calculations are done after every 'X' seconds. This includes the default SLM timeout of 5
seconds in which the agent will not transmit any further SLM PDUs and will wait for the
response from remote node. Upon the expiration of the timeout, the agent assumes that the
message response will not be received. Any response received after the timeout period has
expired is silently discarded. This parameter is optional and is valid only if type – two-way-slm.
This can be set only when admin status is set to disabled.
The no form of the command reverts the value to the default.
3.17.4.15mac-address
Table 31mac-address command
ItemDescription
Syntaxmac-address mac-address
Contextconfigure>eth-cfm>y1731pm>domain
DescriptionSpecifies the target unicast MAC address for the y1731pm session.
The no form of the command reverts the value to the default
Default00:00:00:00:00:00
Parametersperiod — [xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx]
3.17.4.16type
Table 32type command
ItemDescription
Syntaxtype type
(1 of 2)
Issue: 133HH-11985-AAAA-TQZZA93
Page 94
Services Overview
3.17.5Ethernet Ring Global Commands
3.17.5.1eth-ring
FD 100/320Gbps NT and FX NT IHub Services Guide
ItemDescription
Contextconfigure>eth-cfm>y1731pm>domain
Description The value of type indicates the type of y1731pm session this row details.
The no form of the command reverts the value to the default.
DescriptionThis command allows a sub second CCM enabled MEP to delay a transition to a failed state
Parametersdowndown-timeout - Specifies the time, in centiseconds, used for the hold-timer for
if a configured remote CCM peer has timed out. The MEP will remain in the UP state for 3.5
times CCM interval + downdelay.
associated Continuity Check (CC) Session down event dampening. This guards against
reporting excessive member operational state transitions. This is implemented by not
advertising subsequent transitions of the CC state to the Ethernet ring Group until the
configured timer has expired.
Values: 0...5000
Default: 0
upup-timeout - Specifies the time, in deciseconds, used for the hold-timer for associated
Continuity Check (CC) Session up event dampening. This guards against reporting excessive
member operational state transitions. This is implemented by not advertising subsequent
transitions of the CC state to the Ethernet ring Group until the configured timer has expired.
Values: 0...5000
Default: 20
3.17.5.4guard-time
Issue: 133HH-11985-AAAA-TQZZA95
Page 96
Services Overview
3.17.5.5node-id
FD 100/320Gbps NT and FX NT IHub Services Guide
Table 36guard-time command
ItemDescription
Syntaxguard-timetime
Contextconfigure>eth-ring
DescriptionConfigure the eth-ring guard time
Parameterstime - eth-ring guard time in deciseconds
Values: 1...20
Default: 5
Table 37node-id command
ItemDescription
Syntaxnode-idxx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx
Contextconfigure>eth-ring
DescriptionConfigure the node ID of the Ethernet Ring
Parametersxx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx - MAC address representing the node ID.
3.17.5.6rpl-node
Table 38rpl-node command
ItemDescription
Syntax[no] rpl-node {owner}
Contextconfigure>eth-ring
DescriptionThis command configures a node to act as a RPL owner in an Ethernet ring.
RPL Owner is the node connected to Ring Protection Link (RPL) that blocks traffic on RPL
during Idle state and unblocks during Protected state.
The no form of this command; removes the RPL owner functionality.
ParametersNone
96
3HH-11985-AAAA-TQZZAIssue: 13
Page 97
FD 100/320Gbps NT and FX NT IHub Services GuideServices Overview
3.17.5.7path
Table 39path command
ItemDescription
Syntaxpath {a|b} port-idraps-tagqtag|qinqtag
Contextconfigure>eth-ring
DescriptionThis command configures one of the two paths supported under the Ethernet ring.
The no form of this command removes the path from under the Ethernet ring.
Note: The associated SAP need to be un-configured before the path can be deleted.
Parametersport-id - Specifies the physical port /lag for the path.
raps-tag ) Specifies the VLAN-ID to be used for Ethernet CFM and G.8031 control plane
exchanges.
The Q-in-Q RAPS-Tag is allowed on port with Qtag Encapsulation in case of iHUB.
The range of Q-in-Q Inner-Tag is [0…4093], a value of 0 Inner-Tag in turn acts as an Qtag. i.e,
RAPS and CCM Packets will be sent with Single Outer Tag.
3.17.5.8control-mep
Table 40control-mep command
ItemDescription
Syntaxpath {a|b} port-idraps-tagqtag
Contextconfigure>eth-ring>path>eth-cfm>mep
DescriptionThis command enables the usage of the CC state by the Ethernet ring manager for
consideration in the protection algorithm. The use of the control-mep command is
recommended if fast failure detection is required, especially when Link Layer OAM does not
provide the required detection time.
The no form of this command disables the use of the CC state by the Ethernet ring manager
parameters are specified, all services defined on the system are displayed.
ies — Displays matching IES instances
vpls — Displays matching vpls instances
m-vpls — Displays matching m-vpls instances
v-vpls — Displays matching v-vpls instances
vprn — Displays matching VPRN services
mirror — Displays matching mirror services
sdp sdp-id — Displays only services bound to the specified SDP ID.
Default: Services bound to any SDP ID.
Values: 1...17407
customercustomer-id — Displays services only associated with the specified customer ID.
Default: Services associated with a customer.
Values: 1...2147483647
(2 of 2)
Table 44 describes the command output fields.
Table 44Show Service Service-using Command Output Fields
LabelDescription
Service IdThe service identifier.
TypeSpecifies the service type configured for the service ID.
AdmThe desired state of the service.
OprThe operating state of the service.
CustomerIDThe ID of the customer who owns this service.
Last Mgmt ChangeThe date and time of the most recent management-initiated change to this service.
Sample output:
*A:ALA-12# show service service-using customer 10
==================================================================
Services
============================================================================
ServiceIdTypeAdmOprCustomerIdLast Mgmt Change