Download
efm cu mib n.
Skip this Video
Loading SlideShow in 5 Seconds..
EFM-CU-MIB PowerPoint Presentation

EFM-CU-MIB

82 Vues Download Presentation
Télécharger la présentation

EFM-CU-MIB

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. EFM-CU-MIB Issues

  2. Issues • ifStackTable/efmCuAvailableStackTable • Reference to SHDSL/VDSL MIBs • Notifications • MAU-MIB • Single Profile/Parametric Configuration • TC/PME layer

  3. ifStackTable/efmCuAvailableStackTable • ifStackTable – describes/configures actual PCS/PMEs cross-connect • efmCuAvailableStackTable – describes cross-connect capability (read only) • Alternative: reverse Is it the right choice?

  4. SHDSL/VDSL MIBs • SHDSL/VDSL versions described in HDSL2-SHDSL-LINE-MIB/VDSL-LINE-MIB differs from EFM. • Simplicity and Name Consistency • Current EFM-CU-MIB defines everything inside. Is it the right choice?

  5. Notifications • Currently defined: • LineDefect • LineAtnCrossing (Local/Remote) • SnrMgnCrossing (Local/Remote) • Possible additions: • ES, SES, CRCanomalies, LOSWS, UAS, DeviceFault, PowerLoss…

  6. MAU-MIB • New values for ifMauType: • dot3MauType2BaseTL • dot3MauType10PassTS Should we add –O/-R subtype?

  7. Single Profile/Parametric Configuration • 2BaseTL profile consists of: DataRate, Region, PSD, Constellation • Possible configurations: • Single Profile (pre-configured set of params) • Individual Parameters • Precedence if both are used? Should we have both possibilities?

  8. TC/PME layer • D3.1 defines new TC layer Options: • Keep it under current efmCuPmeEntry Sequence • Add a new entry