Zhone EtherXtend 3300 Series, User Manual

Page: 125 / 150

Modify EFM port interfaces
EtherXtend User’s Guide
123
can occur because over time errors can increase causing retransmissions and
lower throughput or cause a retrain of the link resulting in a lower traffic rate.
The efmWorstCaseMode allows the line to sync assuming line conditions are
the worst they can be by assuming that there are forty nine users/disburbers
even if they do not currently exist. Setting efmWorstCaseMode to true is the
most stable setting because the line’s SNR and stability are not effected when
other users come onto the line. The line typically trains to a lower rate to
allow for any SNR loss when these changes occur.
For n2n bonding, but not EFM bonding, you can set both the
efmCurrentConditionMode and the efmWorstCaseMode to true. This results
in a mixed mode that sets a more liberal train rate than efmWorstCaseMode,
but a more conservative train rate than in efmCurrentConditionMode.
Update the EFM bond
To update the efm-bond profile using 1 as an example, enter update
efm-bond :
zSH> update efm-bond
dynamic link: -----------------> {enabled}
Modify EFM port interfaces
Perform a list command
EFM ports are automatically created. To view EFM port profiles, enter list to
view what EFM profiles are available. The following example shows a list of
EFM specific EFM profiles that are available.
zSH> list
efm-bond: ifIndex
efm-port: ifIndex
efm-stats: ifIndex
EFM port default
To display the EFM port parameters in their default state enter get efm-port
interface/type :
zSH> get efm-port 1-1-1-0/shdsl
efm-port 1-1-1-0/shdsl
efmCuPAFAdminState: ----------------> {enabled}
efmCuPAFDiscoveryCode: -------------> {}
efmCuAdminProfile: -----------------> {0x01}
efmCuTargetDataRate: ---------------> {50000}
efmCuTargetWorstCaseSnrMgn: --------> {1}
efmCuThreshLowBandwidth: -----------> {0}
efmCuLowBandwidthEnable: -----------> {false}