Alcatel-Lucent 7210 SAS M Interface Configuration Manual page 170

• The maximum number of unique qinq-etypes configurable per node is limited. The resources needed for
configuration of qinq-etype is shared by the default dot1q-etype, default qinq-etype and user configured
values for qinq-etype. In other words, the number of unique dot1q-etypes allowed decreases if the num-
ber of unique qinq-etype configured is more. The converse is also true.
• The qinq-etype change is not allowed on hybrid port, if there is an interface or a SAP configured on the
port.
The no form of this command reverts the qinq-etype value to the default. The default value is not user
configurable.
Default 0x8100
Parameters
0x0600..0xffff — Specifies the qinq-etype to expect.
Values
The no form of the command sets the qinq-etype value to the default value.The default value is "0x8100", it
is not user configurable.
report-alarm
Syntax [no] report-alarm [signal-fail] [remote] [local]
Context config>port>ethernet
Description
Platforms Supported: 7210 SAS-R6, R12, M, T, Mxp and X (Only for 10 G ports).
This command specifies when and if to generate alarms and alarm clear notifications for this port.
Note: This command is supported only for 10G ports on 7210 SAS-M, 7210 SAS-X, 7210 SAS-T, 7210
SAS-Mxp, 7210 SAS-R6 and 7210 SAS-R12.
Parameters
signal-fail — Reports an Ethernet signal lost alarm.
remote — Reports remote faults.
local — Reports local faults.
port-clock
Syntax port-clock {master | slave | automatic}
Context config>port>ethernet
Description
Platforms supported: 7210 SAS-T devices (only for fixed copper ports).
With copper ports using 1G speed, the nodes need to determine who will be the master and slave with
respect to clock used for transmission and reception. The master-slave relationship between the two ports of
the nodes is determined during auto-negotiation of the link parameters and is automated; there is no
7210 SAS M, T, X, R6, R12, Mxp Interface Configuration Guide
1536 — 65535, in hexadecimal or decimal notation. Ensure that the values do not match
any of the IEEE reserved ethertype values such as 0x8a88, 0x9100, and 0x9200.
Interface Configuration
Page 165