User Guide for FibeAir® IP-20 All-Outdoor Products, CeraOS 10.5
Page 557 of 825
Ceragon Proprietary and Confidential
17.1.2
General Guidelines for Provisioning Ethernet Services (CLI)
When provisioning Ethernet services, it is recommended to follow these
guidelines:
•
Use the same Service ID for all service fragments along the path of the service.
•
Do not re-use the same Service ID within the same region. A region is defined
as consisting of all IP-20 devices having Ethernet connectivity between them.
•
Use meaningful EVC IDs.
•
Give the same EVC ID (service name) to all service fragments along the path of
the service.
•
Do not reuse the same EVC ID within the same region.
It is recommended to follow these guidelines for creating service points:
•
Always use SNP service points on NNI ports and SAP service points on UNI
ports.
•
For each logical interface associated with a specific service, there should
never be more than a single service point.
•
The transport VLAN ID should be unique per service within a single region.
That is, no two services should use the same transport VLAN ID.
17.1.3
Defining Services (CLI)
Use the commands described in the following sections to define a service and its
parameters. After defining the service, you must add service points to the service
in order for the service to carry traffic.
17.1.3.1
Adding a Service (CLI)
To add a service, enter the following command in root view:
root> ethernet service add type <service type> sid <sid> admin
<service admin mode> evc-id <evc-id> description <evc-
description>
Table 126: Adding Ethernet Service CLI Parameters
Parameter
Input Type
Permitted Values
Description
service type
Variable
p2p
mp
Defines the service type:
p2p - Point-to-Point
mp
–
Multipoint
sid
Number
Any unused value
from 1-256
A unique ID for the service.
Once you have added the
service, you cannot change
the Service ID. Service ID
257 is reserved for a pre-
defined management
service.
service admin mode
Variable
Operational
reserved
The administrative state of
the service:
