7210 sas m - rel 3.0 - access uplink and ies

All Rights Reserved © Alcatel-Lucent 2008
7210 – SAS
R 3.0 Configuration Note
SAS-E SAS-M

Introduction
With the introduction of the access uplink feature, operators intending to
have QinQ link in the L2 access networks can use the 7210 SAS-M variants, where
operators have a requirement for the 10G Ethernet interfaces. Additionally,
capabilities such as Y.1731 hardware timestamp, SyncE, 1588v2 of the 7210 SAS-M
platform can be availed by the customers.
Though 7210 SAS-E platform supports access uplinks prior to Rel 3.0, it does not
provide the support for 10G Ethernet interfaces. With the support of access uplink
on 7210 SAS-M platforms, operators can have 10G Ethernet interface for their L2
access networks.
Pre-requisite
The first step towards making the box operate with access uplink capabilities is -
modifying the bof settings to support this feature.
A new option in the bof “uplink-mode” has been introduced, which would make the
box to operate either in the network mode or access-uplink mode.
A sample configuration option is shown below:
A:SASM1>bof# uplink-mode
- uplink-mode {access-uplink|network}
<access-uplink|net*> : keywords
Once the uplink-mode is set to access-uplink, it is mandatory to reboot the SAS-M,
in order to make it work in access-uplink mode.
Note: Ensure that the bof settings are saved after modification, before rebooting
the box. Without a reboot, access-uplink feature will NOT work.
Access Uplink & IES Feature
Last Updated: Jan 2011

Alcatel-Lucent 7210 SAS-M - R1.1 Configuration Note
Here’s a sample bof configuration snapshot that shows the uplink-mode as “access-
uplink”.
A:SASM1# show bof
===============================================================================
BOF (Memory)
===============================================================================
135.254.170.22/import/panos_builds/nightly/3.0/R1/MTU-sultan/both.tim
primary-config cf1:srikkanth_access_uplink.cfg
ping-address 135.254.170.32
#eth-mgmt Port Settings:
no eth-mgmt-disabled
eth-mgmt-address 10.135.4.33/24
eth-mgmt-route 135.254.0.0/16 next-hop 10.135.4.1
eth-mgmt-autoneg
eth-mgmt-duplex full
eth-mgmt-speed 100
#uplinkA Port Settings:
uplinkA-port 1/1/1
uplinkA-address 10.135.4.33/24
uplinkA-vlan 0
uplinkA-route 10.135.0.0/16 next-hop 10.135.4.1
uplinkA-route 135.254.170.0/24 next-hop 10.135.4.1
#System Settings:
wait 3
persist on
console-speed 115200
uplink-mode access-uplink
use-expansion-card-type m4-ds1-ces
===============================================================================
Configuration & Verification
After the box reboots and comes back up in access-uplink mode, all the port’s
default mode will be access and can be configured as access-uplink but can no
longer be configured as network ports.
“Uplink” option is available to change the mode from “access” to “access-uplink”
as shown in the below example.
A:SASM1>config>port>ethernet# mode access
- access [uplink]
<uplink> : keyword
2

7210 – SAS
The encapsulation type is set to “qinq” on changing the port mode to access-
uplink. Null/Dot1q encapsulation types are not supported on access-uplink ports.
The configured port mode can be verified as below…
A:SASM1# show port 1/1/1
===============================================================================
Ethernet Interface
===============================================================================
Description : 10/100/Gig Ethernet SFP
Interface : 1/1/1 Oper Speed : 1 Gbps
Link-level : Ethernet Config Speed : 1 Gbps
Admin State : up Oper Duplex : full
Oper State : up Config Duplex : full
Physical Link : Yes MTU : 1522
Single Fiber Mode : No
IfIndex : 35684352 Hold time up : 0 seconds
Last State Change : 12/31/2001 00:12:18 Hold time down : 0 seconds
Last Cleared Time : N/A DDM Events : Enabled
Configured Mode : access Encap Type : QinQ
Dot1Q Ethertype : 0x8100 QinQ Ethertype : 0x8100
PBB Ethertype : 0x88e7
Ing. Pool % Rate : 100 Egr. Pool % Rate : 100
Ing. Pool Policy : n/a
Egr. Pool Policy : n/a
Net. Egr. Queue Pol: default Network Qos Pol : 1
Egr. Sched. Pol : default Access Egr. Qos *: n/a
Auto-negotiate : true MDI/MDX : MDI
Accounting Policy : None Collect-stats : Disabled
Egress Rate : Default Max Burst : Default
LACP Tunnel : Disabled
Uplink : Yes
Split Horizon Group: (Not Specified)
Down-when-looped : Disabled Keep-alive : 10
Loop Detected : False Retry : 120
Use Broadcast Addr : False
Sync. Status Msg. : Disabled Rx Quality Level : N/A
Configured Address : 00:25:ba:01:81:62
Hardware Address : 00:25:ba:01:81:62
Cfg Alarm :
Alarm Status :
Transceiver Data
Transceiver Type : SFP
Model Number : 3HE00027AAAA02 ALA IPUIAELDAB
TX Laser Wavelength: 850 nm Diag Capable : yes

Connector Code : LC Vendor OUI : 00:90:65
Manufacture date : 2009/06/15 Media : Ethernet
Serial Number : PFR0M2E
Part Number : FTRJ8519P2BNL-A5
Optical Compliance : GIGE-SX
Link Length support: 300m for 50u MMF; 150m for 62.5u MMF
===============================================================================
Transceiver Digital Diagnostic Monitoring (DDM), Internally Calibrated
===============================================================================
Value High Alarm High Warn Low Warn Low Alarm
-------------------------------------------------------------------------------
Temperature (C) +30.1 +95.0 +90.0 -20.0 -25.0
Supply Voltage (V) 3.23 3.90 3.70 2.90 2.70
Tx Bias Current (mA) 6.6 17.0 14.0 2.0 1.0
Tx Output Power (dBm) -4.53 -2.00 -2.00 -11.02 -11.74
Rx Optical Power (avg dBm) -6.21 1.00 -1.00 -18.01 -20.00
===============================================================================
===============================================================================
Traffic Statistics
===============================================================================
Input Output
-------------------------------------------------------------------------------
Octets 1506042 0
Packets 15881 0
Errors 0 0
===============================================================================
* indicates that the corresponding row element may have been truncated.
===============================================================================
Port Statistics
===============================================================================
Input Output
-------------------------------------------------------------------------------
Unicast Packets 0 0
Multicast Packets 15881 0
Broadcast Packets 0 0
Discards 0 0
Unknown Proto Discards 0
===============================================================================
===============================================================================
Ethernet-like Medium Statistics
===============================================================================
Alignment Errors : 0 Sngl Collisions : 0
FCS Errors : 0 Mult Collisions : 0
SQE Test Errors : 0 Late Collisions : 0
CSE : 0 Excess Collisns : 0
Too long Frames : 0 Int MAC Tx Errs : 0
Symbol Errors : 0 Int MAC Rx Errs : 0
===============================================================================
4

7210 – SAS
Svc-sap-type:
3 service-sap-type options are available while creating a service.
1. Null-Star
2. Dot1q-preserve
3. Any
A:M2>config>service# vpls
- no vpls <service-id>
- vpls <service-id> [customer <customer-id>] [create] [vpn <vpn-id>]
[m-vpls] [svc-sap-type {null-star|dot1q-preserve|any}] [customer-vid
<vlan-id>] [uplink-type {l2|mpls}]
Note: if the svc-sap-type is not specified while creating the service, the default
svc-sap-type will be “any”.
Please refer to the table below that shows the SAP and service combinations
allowed:
svc-sap-type Access SAPs allowed
Uplink SAPs
allowed
Limitations Tag restrictions
null-star
Null SAP,
dot1q Default SAP
Q.* SAP,
0.* SAP
No tag restrictions apply for
ingress packets
dot1q-preserve dot1q, Q1.Q2 Q1.Q2
The outer tag of the
dot1q-preserve SAP and
the inner tag of the
Q1.Q2 SAP (i.e. Q1 tag)
should be the same
No tag restrictions apply for
ingress packets
any
Null SAP,
dot1q SAP,
dot1q E.N SAP,
Q1.Q2 SAP,
Q.* SAP,
0.* SAP
Q1.Q2 SAP,
Q.* SAP,
0.* SAP
Null SAP can accept only
untagged packets.
In case of “any” svc-sap-type, null sap does not accept tagged packets. For cases
where this is not desired, the service can be configured with svc-sap-type as null-
star, so that null sap can accept & process the packets with one or more tags.
Configuration Example:
Svc-sap-type

In this following example, we configure a service with svc-sap-type as dot1q-
preserve. Referring to the table above, we can only configure an access sap of type
dot1q/Q1.Q2 and/or an uplink Q1.Q2 sap.
Note: For this svc-sap-type,
 Customer VLAN id must be specified while creating the service.
 All Access/uplink SAPs in the service must have the same encapsulation
value (customer VLAN id)
A:M2>config>service# info
----------------------------------------------
customer 1 create
description "Default customer"
exit
vpls 1 customer 1 svc-sap-type dot1q-preserve customer-vid 4 uplink-type l2
create
shutdown
stp
shutdown
exit
sap 1/1/2:4 create
exit
sap 1/1/4:5.4 create
exit
exit
----------------------------------------------
Verification
The following output shows VPLS 1 configured with svc-sap-type as dot1q-preserve:
A:M2# show service id 1 base
===============================================================================
Service Basic Information
===============================================================================
Service Id : 1 Vpn Id : 0
Service Type : VPLS
Description : (Not Specified)
6
Must be same

7210 – SAS
Customer Id : 1
Last Status Change: 04/08/2011 06:36:11
Last Mgmt Change : 04/08/2011 07:35:04
Admin State : Up Oper State : Up
SAP Count : 2
Uplink Type: : L2
SAP Type: : Dot1q Preserve Customer vlan: : 4
-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/2:4 q-tag 1518 1518 Up Up
sap:1/1/4:5.4 qinq 1522 1522 Up Up
===============================================================================
IES Service with Access-uplink SAP
With the introduction of access uplink feature, we can configure an IES
service on SAS-M. An IES has one or more logical IP routing interfaces each with a
SAP which acts as the access point to the management network. As you know,
only access uplink SAPs can be configured under an IES service.
Note: The configuration of IES service in SAS-M is very similar to SAS-E.
Configuration:-
The following output shows that the port is configured as access uplink.
A:SASM1>config>port# info
----------------------------------------------
ethernet
mode access uplink
exit
no shutdown
----------------------------------------------
Here’s a sample configuration that shows an access uplink SAP in an IES.

A:SASM1>config>service# info
----------------------------------------------
customer 1 create
description "Default customer"
exit
ies 1 customer 1 create
interface "test1" create
address 10.135.4.33/24
sap 1/1/1:0.* create
exit
exit
no shutdown
exit
----------------------------------------------
Verification:-
The following output shows the operational status of the service and SAP.
A:SASM1# show service id 1 base
===============================================================================
Service Basic Information
===============================================================================
Service Id : 1 Vpn Id : 0
Service Type : IES
Description : (Not Specified)
Customer Id : 1
Last Status Change: 12/31/2001 01:23:30
Last Mgmt Change : 12/31/2001 01:22:38
Admin State : Up Oper State : Up
SAP Count : 1
-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/1:0.* qinq 1522 1522 Up Up
===============================================================================
8

7210 sas m - rel 3.0 - access uplink and ies

Recommended

Recommended

More Related Content

What's hot

What's hot (18)

Similar to 7210 sas m - rel 3.0 - access uplink and ies

Similar to 7210 sas m - rel 3.0 - access uplink and ies (20)

7210 sas m - rel 3.0 - access uplink and ies