Ethernet Port Commands
Page 190 7210 SAS M, T, X, R6, R12, Mxp, S, Sx Interface Configuration Guide
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, Sx/S, 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-Sx/S 1/10GE, 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, 7210 SAS-R6 and 7210 SAS-R12(16-port copper IMM-sas-r-b
(IMMv2), Combo ports of 7210 SAS-Mxp, Combo ports on 7210 SAS-Sx 1/10GE fiber variant, all copper
variants of 7210 SAS-Sx/S 1/10GE.
NOTE: For 7210 SAS SAS-Mxp and 7210 SAS-Sx/S 1/10GE devices, the user needs to configure the
combo port ‘connection-type’ to ‘copper’, before using the port-clock command. In other words, the use of
connection-type is automatic, and the user is not allowed to configure port-clock without configuring
‘connection-type’ to ‘copper’.
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
management intervention in this process. Once this process is complete, the master port’s transmit clock will
be used for receiving the packets on the slave port. However, when syncE is in use, to maintain clock
distribution hierarchy (for example, master will be synchronized to a stable reference and will distribute this
clock to the slave) one needs to make sure that one of the ports behave as a master while the remote port of
the ink in question behaves as a slave.
This command allows the user to force the copper port to be a master or slave. Using a value of master,
ensures that the local node is the syncE master. A syncE master port, distributes the system timing over the
copper port to the remote peer node. Using a value of slave, ensures that the local node is a syncE slave. A
syncE slave port uses the incoming timing information.