Configuring OLAN Timing
The Tellabs 1134/OLT6 and Tellabs 1150 (MDS5) OLTs support time division multiplexing (TDM) network timing over packet infrastructures.
- Timing Distribution Units (TDU1s) support timing in the Tellabs 1150 (MDS5.
- Ethernet Switch Units (ESU30 or ESU32) support timing in the Tellabs 1134/OLT6.
An OLT with a single or redundant pair of timing cards can be configured as either a timing server or timing client:
- A unicast timing server can be associated with and distribute timing from an external timing source to a maximum of 32 timing clients. As long as 31 or fewer unicast clients are defined. A multicast timing server can also be configured, which can distribute timing from an external timing source to an entire network of timing clients. Both the Tellabs 1150 (MDS5), and Tellabs 1134/OLT6 OLTs can be configured as a timing server.

Note: A Tellabs 1150 (MDS5) or Tellabs 1134/OLT6 OLT that has been turned up to support an IPv6 management interface supports Unicast timing configuration only.
- A timing client can be associated with only one timing server. Timing clients are always assigned (configured) from the timing server.
To configure a timing server and assign timing clients:
- Logon to EMS and in the Network common tree, right-click on the target OLT and select Properties from the dropdown list.
- Select and click the Timing tab.
OLT Property - Timing Tab


Note: If the OLT has been turned up to support Unicast timing with an IPv6 management interface, then the OLT is listed under Available Timing Clients in the Unicast Timing Configuration area of the screen. If this is the case, the Multicast Timing Configuration area of this screen is not shown.
- If the OLT is not configured, the Timing tab provides the option to configure it as a timing server.
- To configure it as a unicast timing server, select the check box to indicate Yes.

- To configure it as a multicast timing server, select the check box to indicate Yes:

- If configuring multicast timing, enter a Multicast VLAN. (Unicast timing uses the management VLAN.) Possible values range from 2 through 4094, with 10 VLANs reserved for internal use. Do not use VLANs 4000-4007, 4011, 4012 as these are only reserved for internal use.

Note: IGMP is always enabled. - The active TDU distributes timing using Timing A Port and Group Address A. The standby TDU distributes timing using Timing B Port and Group Address B. Do one or both of the following:
- For unicast timing, enter the Timing A Port and Timing B Port values. Entries must be greater than 1000 and the same number cannot be used for both ports.
Configure Timing A and Timing B Ports

- For multicast timing, enter IP addresses in Group Address A and Group Address B. The possible value range is 224.0.0.0 to 239.255.255.255.
- For unicast timing, enter the Timing A Port and Timing B Port values. Entries must be greater than 1000 and the same number cannot be used for both ports.
- If configuring multicast timing, and there is non-Tellabs equipment between the timing server’s uplink interface(s) and its timing clients (this is not usually the case), one or more multicast server forwarding interfaces must be configured. To do this, do the following:
- Next to MC Server Forwarding Interface(s), click the Edit button. The Uplink AID Selection Dialog is displayed:

- Click the uplink interface(s) that need to connect to timing clients across non-Tellabs equipment and click the Yes button.

Note 1: To de-select all currently selected uplink interfaces, click NONE, and then click Yes. To de-select a particular uplink interface, click that interface, and then click No. 
Note 2: It may also be necessary to configure the non-Tellabs equipment. Layer 2 devices that flood multicast generally don’t need any additional configuration. Layer 3 devices, and devices that have snooping enabled, must be configured.
- Next to MC Server Forwarding Interface(s), click the Edit button. The Uplink AID Selection Dialog is displayed:
- From the list of Available Timing Clients, select the OLTs to be assigned to this timing server.
Available Timing Clients


Note: To select multiple OLTs, press SHIFT (or CTRL) and click.
- Click the Add button to move the selected OLTs to the list of Assigned Timing Clients.
Assigned Timing Clients


Note 1: To remove OLTs from the Assigned Timing Clients list, select the OLT and click Remove. 
Note 2: If all of the timing clients are deleted from an existing timing server, Panorama PON considers the OLT unconfigured for timing. To refresh the Timing tab for this type of change, close and reopen the OLT properties dialog. - If configuring multicast timing, and adding only a single OLT, the following message is displayed:

- If this happens, and there is non-Tellabs equipment between this timing client and one or more other timing clients (this is not usually the case), click the Yes button. Otherwise, click the No button, and continue with Step 11. When the Yes button is clicked, the Uplink AID Selection Dialog is displayed:

- Click the uplink interface(s) that need to connect to timing clients across non-Tellabs equipment and click the Yes button.

Note: It may also be necessary to configure the non-Tellabs equipment. Layer 2 devices that flood multicast generally don’t need any additional configuration. Layer 3 devices, and devices that have snooping enabled, must be configured.
- Click the Apply button to save changes and update all affected OLTs. The Status for Update Time Configuration Settings dialog displays the update status. Click the Cloose button when finished. the confirmation message is displayed.
- Click the OK button to close the message.
- To review the timing configuration for any OLT that has been assigned as a timing client, select the OLT in the Common Tree, then click the Timing tab.

Note: When an OLT is configured as a timing client, the Timing tab displays the Timing Source field, which provides the OLT TID and IP address of the timing server. Configured Timing Client OLT Example


Note: an OLT from the database automatically deletes any timing associations that is related to that OLT.
Performing an ESU or TDU Cold Reset
|
ALERT! If an OLT’s existing timing configuration has changed (for example, the OLT was configured as a timing server and has been reconfigured as a timing client (or vice-versa)), a cold reset, or reset the timing card, must be performed to apply the change to the OLT. Performing a cold reset is a service-affecting procedure. If necessary, contact the next level of support for assistance. |
To perform a cold reset from Panorama PON:
- Go to the Equipment view.
- Right-click the Ethernet Switch Unit (ESU) or Timing Distribution Unit (TDU) and select Reset > Cold Reset (SA).
