Passive Optical LAN Training: Module 2: System Architecture (Logical)

Passive Optical LAN Training: Module 2: System Architecture (Logical)
3HV01415AAAFUNZZA v August 2016

Presentation Outline Section 1: PON Fundamentals
Section 2: FX Logical Functions Section 3: OLT/ONT Software Section 4: POL Default Infrastructure Build Section 5: POL Initial Build Process Section 6: Perform Lab (module 2)

1 PON Fundamentals

PON Standards: ITU-T G.984.1 – GPON service requirements
specifies line rate configurations and service capabilities G – GPON physical medium specifies transceiver characteristics per line rate and per ODN class including burst overhead for each upstream line rate G – GPON transmission convergence specifies transmission convergence protocol, physical layer OAM, ranging mechanism G – GPON ONT management control interface based on OMCI for BPON, taking GPONs packet mode into account In 2001, the FSAN group initiated a effort for standardizing PON networks operating at bit rates above 1 Gbps. Apart from the need to support higher bit rates, the overall protocol had to be opened for reconsideration so that the solution would be most optimal and efficient to support multiple services and operation, administration, maintenance and provisioning (OAM&P) functionality and scalability. As a result of FSAN (Full Service Access Networks work group) efforts, a new solution emerged in the optical access market place – Gigabit PON (GPON), offering unprecedented high bit rate support (up to Gbps) while enabling the transport of multiple services, specifically data and TDM, in native formats and with extremely high efficiency. In January 2003, the GPON standards were ratified by ITU-T and are known as ITU-T Recommendations G.984.1, G and G G984.1 provides the GPON framework, and is known as the GPON service requirements (GSR). The GSR summarizes the operational characteristics that service providers expect of the network, in terms of transport speeds, tolerances, delay, etc. G984.2 provides the GPON physical medium dependant specifications (GPS). This includes operational parameters of the optical transmitters and transceivers, clock recovery and error correction mechanisms. G984.3 provides the GPON Transmission Convergence (GTC) specifications. The GTC is responsible for correct implementation of the data flow process in the physical layer and addresses issues such as the frame structure, the control sequence between the OLT and the ONTs, and the packet encryption function. G984.4 defines the ONT management and control interface (OMCI) for a GPON.

PON Fundamentals Point-to-Multi-Point used in GPON 1310 (P2MP) 1490
Optical PON wavelengths for the POL solution illustrated below. POL recommended split ratios for high bandwidth requirements are 32 ONTs per port or less, although split ratios of up to 128 can be used (SFP type dependent) (P2MP) Point-to-Multi-Point used in GPON 1:4/8/16/32/64/128 Splitter Optical Line Terminal (OLT) Downstream Upstream Optical Network Terminal (ONT) 1490 1310 Subscribers The FX GPON a Point to Multipoint connection where one PON port of the LT Line Card equipment can have up to 128 subscribers, using optical splitters. Since one fiber is used both to transmit and receive, there are two lambdas, one for upstream at 1310 nanometers), and the other is for downstream (at 1490 nanometers).

PON Fundamentals (cont)
Server Room ‘Per Floor’ PON Distribution Drops ONT’s 7360 FX 1:’x’Optical Splitters This illustration adapts the telco centric ‘feeder/distribution & drop’ domains to a POL scenario. With POL, it is almost exclusively going to consist of the following: ‘Server Room’: The location of the OLT ‘Per Floor PON Fiber Distribution’: A PON fiber run to a splitter (or multiple splitters) per building plate floor ‘Drops’: A fiber drop to each ONT per office desk layout, hotel room, apartment etc. The Distribution section is where the fiber is run to the splitter and a split ratio of 1:4, 1:8, 1:16, 1:32…1:128 etc is achieved via an optical splitter unit. Active Passive Active

PON – Passive Optical Network Passive components: Splitters + fibres Star topology: P2mp (point to multipoint) Ranging distance: 60 km maximum logical reach 20 km differential distance Split-ratio: Minimum 4, or /8/16/32/64/128 subscribers. POL solution recommends split ratio of 1/16 or less The FX GPON a Point to Multipoint connection where one PON port of the LT Line Card equipment can have up to 128 subscribers, using optical splitters. Since one fiber is used both to transmit and receive, there are two lambdas, one for upstream at 1310 nanometers), and the other is for downstream (at 1490 nanometers). The POL solution recommends split ratios of 16:1 or less (for very high bandwidth handling purposes). Discuss with your local Nokia representative if a higher split ratio (than the POL 1:16 solution recommendations) is desirable. Note that high split ratios of 1:128 will require a C+ optics SFP and therefore the POL ordering Bill of Materials would need modification.

Optical Budget: The amount of light you can use between transmitter (Tx) and receiver (Rx) Light Loss: Connectors, splices, fibers crimped, fiber aging. Scattering and Infrared Absorption Approx 0.3 dB / 0.1 dB Approx 3dB for a 1:2 split Ageing of the fibre Connector Splices Split Ratio Losses Fibre Impurities These are the typical losses in fiber. Even though this is fiber it still has a loss per km usually around 0.42db/km. The aging also adds some loss which usually is calculated around 1dB. The connectors and splices also add more losses: 0.3dB per connector and 0.1dB per splice. The splitter is the component which is responsible for the greatest loss since it splits the light. A one to two ratio will have a 3dB loss since it splits the light in two. The other major loss is caused by the impurities inside the fiber but only at certain wavelengths. This is caused by scattering and infrared absorption which effects mostly the lowest and highest wavelengths.

PON Fundamentals: Optical Loss
Example below is a theoretical mathematical demonstration using a 1:32 split ratio to illustrate loss characteristics: Loss in splitters (10 log x, x=split ratio) Cascaded splitter can be used if required e.g., 1:4 splitter followed by 1:8 splitter or vice versa So a one-step 1:32 splitter can be used Loss per km fiber (0.42dB/Km) Loss in connectors (0.3dB) Loss in splices (0.1dB) Loss in WDM coupler (1.3dB) Note: Example of loss characteristics only. As stated earlier in this training package, 1:16 split ratios are the maximum split ratio for POL High Bandwidth solutions. The 1:32 split ratio example in this slide is for demonstration purposes only. Here we see all the components that will introduce losses inside the PON network. The sum of these losses will determine the distance between the GPON node and the CPE (Customer Premises Equipment), called the ONT (Optical Network Termination). The biggest loss in a PON network is the splitter. It will depend on whether we have a 32, 64, or 128 split. With a split of 64, there is a loss of 18dB (10 log 64). Since it is not a perfect split, there is an extra loss of 1 to 3dBs. The other loss would be caused by the fiber, which depends on the lambda used, as seen previously in the graph and the quality of the fiber. Since there are two lambdas (plus an optional one), the worst case is used which is the upstream lambda of 1310 nano meters with a loss of 0.42dB/km. The connectors which connect the fiber to the equipment and the ONT will have a 0.3dB loss per connector. There could be more, for example in the optical distribution frame, both at the Central Office and the Customer Premises. Any splices which join different fiber sections present through out the path will introduce a 0.1dB loss per splice. The WDM (Wave Division Mux) coupler will only be needed if video overlay is used. This will add a 1.3 dB loss.

PON Fundamentals: Split Ratio Loss
Example: Splitter 1 x 8 Output Fiber 3.5dB 3.5dB Input Fiber 3.5dB Note: Example of loss characteristics only. As stated earlier in this training package, 1:16 split ratios are the maximum split ratio for POL High Bandwidth solutions. The 1:32 & 1:64 split ratio examples in this slide are for demonstration purposes only. The loss budget requirement for the PON, based on ITU Recommendation G.983.4, is 22 dB total loss budget for Class B PON and 27 dB for Class C PON. What differentiates Class B and Class C PON is the power of the laser used and, marginally, the quality of the optical components. This loss budget is really tight, especially when high-port-count splitters are used in the design. The splitters in a PON cause an inherent loss because the input power is divided between several outputs. Splitter loss depends on the split ratio and is about 3 dB for a 1 x 2 splitter, increasing by 3 dB each time the number of outputs is doubled. A 1 x 32 splitter has a splitter loss of at least 15 dB. This loss is seen for both downstream and upstream signals. Combine the losses of the WDM coupler, splices, connectors and fiber itself, and it is easy to understand why a precise bidirectional measurement of end-to-end optical loss at the installation is a must. In addition to the optical loss, the end-to-end link optical return loss (ORL) is very important to measure. Undesirable effects of ORL include: 1: Interference with light-source signals 2: Higher bit error rate in digital systems 3: Lower system optical-signal-to-noise ratio 4: Strong fluctuations in the laser output power 5: Permanent damage to the laser

PON Fundamentals: Optical Signal Range
Eric ITU-T G.984 Standard B+ Laser splitting best case worst case 1 : 64 14 Km 10 Km 1 : 32 21 Km 15 Km 1 : 16 30 Km 23 Km 1 : 8 38 Km 21 km 14 km 1:64 1:32 1:16 1:2 1:4 1:8 Note: Example of loss characteristics only. As stated earlier in this training package, 1:16 split ratios are the maximum split ratio for POL High Bandwidth solutions. The 1:32 & 1:64 split ratio examples in this slide are for demonstration purposes only. This is a rough estimation on maximum range per splitter-configuration using a B+ laser. Better results are achieved using a C+ laser. Splitters are the main part of the loss in the link between OLT and ONT. We have to consider that a split of 1:2 will have a 3dB loss or we can calculate the loss by this formula: 10log the split number. For example, a split of 64 will have a loss of 18 dB. Also, we have to take into account the attenuation of fiber per Km (around 0.3, 0.4dB/Km), the number of splices in the fiber (each splice has a 0.1dB loss), and the number of connectors (a 0.3dB loss per connector). We will have 2 connectors minimum, one in the OLT and another one in the ONT, but can have more, like in the distribution frame inside the CO and others inside the building of the subscriber. Considering all this, a table is shown to indicate roughly the distance between OLT and ONT in function of the splitters used. A splitter configuration can be one splitter or several splitters in cascade. The splitter configuration 1:8 can be one splitter of 1:8, or one splitter of 1:4 and one splitter of 1:2. 30 km 38 km

PON Fundamentals: Transmission Downstream
1490 nm 2500 Mb/s Standardized by ITU-T in G.984.x recommendation Communication between P-OLT and ONT GPON NODE ONT GPON has a many benefits, but the shared medium also presents us with some difficulties. Since we are using a point-to-multipoint topology, a specific transmission mechanism has to be implemented in order to benefit fully from this architecture. In the downstream direction, the transmission is defined as being broadcast. In other words, the same information is sent to all connected ONTs. For security reasons, this information can be encrypted. On top of that, the information contains a specific destination to allow each ONT to decide whether to accept or reject the packet. The broadcast traffic is continuous, i.e., there is always a signal on the fiber. We need to do this in order to allow the ONT to synchronize with the central office. As extra security, AES (Advanced Encryption Standard) can be activated as an optional per ONT configuration (and is included in the POL solution). OLT requests the encryption key to the ONT. The ONT generates the key and sends it to the OLT and the OLT will indicate to the ONT to activate the encryption. This encryption key automatically changes every ‘x-time’ (called churning). Downstream : broadcast traffic – use encryption for security (AES) ?

PON Fundamentals: Transmission Upstream
1310 nm 1250 Mb/s ONTs are located at different distances from Central Office Upstream : same wavelength + same fiber: Uses Time Division Multiplexing (TDMA) GPON NODE ONT In the upstream direction, the situation is more complex. We only have 1 fiber and all ONTs use the same wavelength (1310 nm) The OLT decides when each ONT can send traffic in the upstream direction. An important parameter in this decision process is the distance between the ONT and the central office. We know the speed (1.25 G), so if we know the distance, we can generate time windows in which the ONTs can send information. The process of determining the distance between ONT and OLT is called distance ranging (during this time, the PON light on the ONT will be blinking).The process of determining timeslots for each ONT s called access granting . That’s the concept behind TDMA : Time Division Multiple Access (using different timeslots on the same medium) So TDMA is implemented by using these three factors: 1: The distance from the ONT to the OLT must be measured. 2: Then timeslots are allocated to the ONT according to the distance. 3: The ONTs send data upstream only in their assigned timeslot. Distance OLT – ONT has to be measured Timeslots are allocated according to distance ONTs only send upstream according to granted timeslot

PON Fundamentals: Distance Ranging
20 km 20 km Logical distance and ranging: In normal network conditions, ONTs are located at different distances from the OLT. This results in transmission phase differences and the OLT may receive overlapping transmissions from the different ONTs. The PON concept has a specific method for synchronizing the ONT transmissions, called ranging. First, an ONT synchronizes itself to the downstream frame headers and waits for the ranging window to open. When the window opens, the network enters into the ranging procedure, during which the delay and phase differences between the OLT and all active ONTs are determined. As a result, the ONTs adjust their transmission phases and grants accordingly. Ranging is operated by the OLT, which opens a ranging window between configurable time periods. This means that the OLT sends a ranging grant and stops the traffic in the network and waits for the ONTs to send their ranging PLOAMs. The ranging window should be large enough to cover propagation and processing delays of all the ONUs, including the farthest ONU. The window size can be programmed to support transport distances up to 20 kilometers (B-PON). During the ranging procedure, each active ONU receives a PON-ID from the OLT, which uses the IDs to send data to each ONT individually. Moreover, the OLT measures the arrival phases of the ONU ranging cells, calculates the required equalization delays and communicates the information to the ONTs. The ONTs adjusts their transmission phases according to the determined values. After initialization, each active ONT can transmit data according to the given grants. 15 km deliberately putting equalization delay in for the purpose of avoiding collisions

PON Fundamentals: GPON Framing
GEM-segment downstream frame – 125 us ONU1 ONU2 ONU3 ONU4 ONU5 The GPON frame format is specified as part of ITU-T recommendation G.984.3: GTC – GPON transmission convergence. This recommendation is equivalent to layer 2 (the data transmission layer) in the OSI reference model, and besides the GPON frame format also describes the media access control protocol, the ranging scheme, operations and maintenance processes, and the information encryption method. The picture shows the GPON frame format, which has a fixed 125 us length. The frame consists of a physical control block (PCB) and a payload composed of a pure GEM segment. The PCB section contains the physical layer overhead information to control and manage the network. For example this is where the OLT grants the ONTs to transmit upstream. upstream frame – 125 us GEM-packet

PON Fundamentals: GPON Framing Format Downstream (cont)
downstream frame Tx Rx continuous mode Tx continuous mode Rx For the downstream, it is a “Continuous mode operation”. A signal is always present, even when no data is transmitted. So the laser is always on, but can be turned off administratively. We have to consider two elements: 1: Continuous mode transmitter, no need to adapt power level 2: Continuous mode receiver, clock extraction Power level consideration In continuous mode operation, the power level is high enough to reach all subscribers. Each ONT gets this signal, although attenuated differently because they all are at different distances from the central office. The attenuation shouldn’t be too big, so there still is enough power in the signal left. The attenuation shouldn’t be too small either, because then the power level of the signal going out of the fiber would be too big and this might damage the optical receiver. When the power level is in the dynamic range of the receiver, the ONT can easily do the clock extraction and pick up the data destined for it. Downstream- There’s always a signal even when there’s no user data to pass through except when the laser is administratively turned off

GEM-segment Physical Control Block In the downstream direction the PCBd (physical control block for frames going downstream) contains the following information: a 4-byte frame synchronization field (Psync). a 4-byte segment (Ident) that contains an 8-kHz counter, a downstream FEC status bit, an encryption key switchover bit, and 8 status bits reserved for further use. A 13-byte downstream physical layer OAM (PLOAMd) message, which handles functions such as OAM-related alarms or threshold crossing alerts. A 1-byte bit interleaved parity (BIP) field, used to estimate the bit error rate. A 4-byte downstream payload length indicator (Plend), which gives the length of the upstream bandwidth (US BW) map and the size of the ATM segment. The Plend field is sent twice for extra redundancy and error robustness. the N x 8-byte US BW map allocates N transmission time slots to the ONTs. Psynch Ident PLOAMd BIP PLend PLend US BW Map 4 bytes 4 bytes 13 bytes 4 bytes 4 bytes N*8 bytes 1 byte

Physical Control Block N*8 bytes Psynch Ident PLOAMd BIP PLend PLend US BW Map AllocID Flag SStart SStop CRC … AllocID … CRC The US BW map contains N entries associated with N time-slot allocation identifications for the ONTs. As the picture shows, each entry in the US BW map or access structure consists of: a 12-bit allocation identifier (AllocID) that is assigned to an ONT (will represent services on the ONT, see later) twelve flag bits that allow the upstream transmission of physical layer overhead blocks for a designated ONT (see slide p. 43) a 2-byte start pointer (SStart) that indicates when the upstream transmission window starts. This time is measured in bytes; the beginning of the upstream GTC frame is designated as time zero. a 2-byte stop pointer (SStop) that indicates when the upstream transmission window stops. a 1-byte CRC that provides a 2-bit error detection and 1-bit error correction on the bandwidth allocation field --- The AllocID identifies the T-CONT (Traffic container) The Port-ID identifies the queue on the ONT With a split to 128 users, this actually means 32 alloc-id’s can be assigned to a single ONT! 12 bits 12 bits 2 bytes 2 bytes 1 byte Entry for ONT#1 Entry for ONT#N

3 entries US BW Map ONT1 slot 75 slot 240 AllocID Start Stop ONT2 slot 280 slot 400 ONT3 slot 430 slot 550 upstream packet timing This slide gives an example of time-slot allocations for three ONTs. Here there are three entries in the US BW map field. The AllocID of the ONTs are 1, 2, and 3 for ONT1, ONT2, and ONT3, respectively. The center part of the picture shows start and stop time slots listed in the downstream US BW map field during which the various ONTs are allowed to transmit. The lower part of the picture shows the general format of the ensuing upstream information stream form the three ONTs. An appropriate guard time is placed between packets from different ONTs. So a GPON system allocates time slots for each ONT to ensure that the data of each ONT is received independently at the OLT. A system of pointers is used. The PCB holds the grant bytes/messages, which defines which ONU should use which time-slots/bytes in the upstream frame. This allocation can change frame after frame, so bandwidth is allocated dynamically. guard time guard time slot times: 75 240 280 400 430 550 time

PON Fundamentals: GPON Framing Format Upstream
upstream frame Rx Tx burst mode Rx burst mode Tx On the upstream we have “Burst mode operation”. There’s only a signal when an ONT needs to send information. A guard time of 26 ns is needed between 2 consecutive bursts. We have to consider two elements: burst mode transmitter and burst mode receiver. The transmitter operates in burst mode. It has three modes: no light, logic 0, and logic 1. In contrast to point-to-point systems, ONUs which are not permitted to transmit must turn off their lasers. There is a burst mode receiver resync on every single burst coming in. Power level consideration Assume all ONTs send their upstream data using the same power level. Due to the fact they are all at different distances, the attenuation imposed will be different for all of them. It even is possible that the power level of a logic 0 from a near ONT exceeds the power level of a logic 1 from a far ONT! So the receiver at the OLT has a hard time to distinguish a logical 1 from a logical 0. In order to do that, the receiver has to measure the power levels of a 0 and a 1 (amplitude ranging), and adapt the detection thresholds accordingly. And this has to happened for each burst coming in! That’s the reason why every burst of information is prepended with some bits/bytes referred to as burst overhead (BO). The transmitter operates in burst mode. It has three modes: no light, logic 0 and logic 1. In contrast to point-to-point systems, ONTs which are not permitted to transmit must turn off their lasers. At the input to the OLT’s receiver, the light corresponding to a logic 0 from a near ONU could well exceed the light corresponding to a logic 1 from a far ONU. (chapter 60/4 of Telecommunications engineer’s reference book, second edition) Upstream: There’s only a signal when an ONT needs to send When no ONT has info to send, there’s no light on the fiber at all Between 2 consecutive bursts, a guard time is needed: 26 ns

PON Fundamentals: GPON Framing Format Upstream (cont)
ONU1 ONU2 ONU3 ONU4 ONU5 Header Payload Upstream GPON traffic consists of successive transmissions from one or more ONTs. As the picture on previous slide illustrates, the particular sequence of frames is based on the transmission time-slot allocations developed by the OLT. To allow proper reception of the individual burst-mode frames, a certain amount of burst-overhead is needed at the start of an ONT upstream burst. The slide on this page shows the format of an upstream frame, which consists of up to four types of PON overhead fields and a variable-length user data payload that contains a burst of transmission. The upstream header fields are the following: the physical layer overhead (PLOu) at the start of an ONT upstream burst contains the preamble, which ensures proper physical layer operation (e.g., bit and byte alignments) of the burst-mode upstream link. the upstream physical layer operation, administration and management (PLOAMu) field is responsible for management functions such as ranging, activation of an ONT, and alarm notifications. The 13-byte PLOAMu contains the PLOAM message as defined in G and is protected against bit errors by a cyclic redundancy check (CRC) that uses a standard polynomial error detection and correction code. the dynamic bandwidth report (DBRu) field informs the OLT of the queue length of each AllocID at an ONT. This allows the OLT to enable proper operation of the dynamic bandwidth allocation process. The DBRu is protected against bit errors by a CRC. Transmission of the PLOAMu, PLOu, and DBRu fields are optional depending on the downstream flags in the US BW map. PLOu PLOAMu DBRu Physical layer overhead Physical layer OAM Dynamic bandwidth report

PON Fundamentals: GPON Framing Format Upstream (cont)
TDM GEM header PLI PortID PTI CRC payload payload L bytes 12 bits 12 bits 3 bits 13 bits L bytes GPON encapsulation method (GEM) is used to accommodate all types of services (e.g. ATM, TDM, and Ethernet) efficiently. This method is based on a slightly modified version of the ITU-T recommendation G.7041 Generic Framing Procedure, which gives the specifications for sending IP packets over SONET or SDH networks. --- The GPON encapsulation method works similar to ATM, but is uses variable-length frames instead of fixed-length cells as in ATM. Thus, GEM provides a generic means to send different services over a GPON. The encapsulated payload can be up to 1500 bytes long. If an ONT has a packet to send that is larger than 1500 bytes, the ONT must break the packet into smaller fragments that fit into the allowed payload length. The destination equipment is responsible for reassembling the fragments into the original packet format. The picture above shows the GEM segment structure, which consists of four header fields and a payload that is L bytes long. The header fields are the following: A 12-bit payload length indicator (PLI) that gives the length in bytes of the GEM-encapsulated payload. A 12-bit port identification number that tells which service flow this fragment belongs to. A 3-bit payload type indicator which specifies if the fragment is the end of a user datagram, if the traffic flow is congested, or if the GEM payload contains OAM information. A 13-bit cyclic redundancy check for header error control that enables the correction of two erroneous bits and the detection of three bit errors in the header A key advantage of the GEM scheme is that it provides an efficient means to encapsulate and fragment user information packets. The reason for using encapsulation on a GPON is that it allows proper management of the multiple service flows from different ONTs that share a common optical fiber transmission link. The purpose of fragmentation is to send packets from a user efficiently regardless of their size and to recover the original packet format reliably from the physical layer transmission windows on the GPON. Ethernet Payload MACDA MACSA Type/ Length FCS

2 7360 FX Logical Functions

Network Uplink Architecture
The 7360 FX controller WAN facing interface settings and ports have multiple connectivity options. This is the logical component of the NT controller card(s), the FANT-F. This can be considered as a multi-port switch of which the 4 or 8 LT line cards (FX-4, FX-8) are connected via 4/8 backplane switch ports, and also includes the NT-A and NT-B uplink ports. Therefore the switch comprises of 4/8 LT ports and a maximum of 5 electrical/optical ports per NT card, making a total of 14/18 logical switch ports the Ihub can terminate in the POL solution offering. A uplink expander card can be optionally added to the OLT (physically residing between the NT-A/B cards). This adds to the available 14/18 logical switch ports but is not included in the POL solution. Based on discussions Channel Partners may have with their potential customers (which may in isolated cases drive the requirement for an FNIO card), Nokia can be engaged to provide design and configuration support for this card and uplink ports external to the default POL configuration offerings. By default, the Ihub logical ports operate by default as a split horizon group. All 4/8 LT ports are ‘leaf’ ports and cannot (by default) forward to each other and can only forward to a network uplink (‘root’) port; one of the NNI uplink (LAG) ports on the ISAM. Therefore any service VLAN configured between the customers serviced via the LT cards PON ports will forward traffic to/from the network ports, not the LT ports, known as intelligent (residential) Bridging, (i-bridge). Therefore a VLAN configured for a service hosting a chassis worth of customers will forward to/from the network port NNI interface, even if traffic is destined for another adjacent ONT hosted customer. This is essential for services that have a hub/spoke and client/server relationship architecture and is also essential for the likes of billing and lawful intercept. This baseline functionality can be changed by configuration to disable this split horizon behaviour on a per VVPLS/VLAN (i.e., per service) basis which is required for some service concepts.

Network Uplink Architecture (continued)
The configuration of the NT card(s) will have High Availability hosting two Network Controller cards (FANT-F). These are configured to operate as an ‘active/standby’ redundancy pair. A 2->8 ports optical 1/10G LACP LAG uplink (provisioned across the NT-A and NT-B controller cards) A dual uplink STP (2 x 1/10G single port or optical LAG) ‘east/west’ provisioned across the NT-A and NT-B controller cards VRRP Connectivity Support for the above. If optical LAG links are utilized and ‘Out of Band’ connectivity is also desired, the electrical (RJ45) uplink LAG Group can be configured for Out of Band OAM telnet/SSH connectivity as either LAG or (R)STP. Load-sharing between all links in the LAG group follow the hashing mechanism are as follows: For L2 traffic hashing algorithm the following is used: dst MAC address + src MAC address + VLAN-ID + Ethertype + INPORT For IP traffic hashing algorithm the following is used: Outer VLAN-ID + src-IP + dst-IP + IP PROTO+TCP/UDP-SRC+TCP/UDP-DST+INPORT All the multi-point VLAN (VVPLS) services that are configured into the ISAM 7360 FX are required to be mapped to whatever physical network facing LAG Group ports are configured as the desired uplink at the time of commissioning depending on the customer port preferences listed above.

Logical Architecture: Ihub
Ihub is the logical network facing switch Comprises of network uplink and LT card downlink ‘ports’ Operates in a split/non split horizon per service as required

Logical Architecture: Ihub (continued)
A POL Service is defined via a VPLS (Virtual Private LAN Service, aka ‘VLAN’) The VPLS is mapped to the Individual Ports or LAG uplink and all the LT cards To transport user traffic across the NT board, we configure a VLAN Virtual Private LAN Service ((v-)VPLS) instance per VLAN in the Ihub, providing 802.1Q framing via the network NNI uplink. The v-VPLS contains Service Access Points (SAPs) which are Layer 2 interfaces within the NT board. In all cases, the (v-)VPLS will contain 9 SAPs (FX-8) or 5 SAPs (FX-4). Using the example of a VLAN tag value of 100, one SAP will always be the uplink LAG and a VLAN (e.g. lag-1:100) and the other SAPs will be the LT facing interfaces connecting to the backplane and a VLAN (e.g. LT Line Card 1, lt:1/1/1:100 i.e., rack, shelf, line card, VLAN 100). This is built in the Ihub via the 5571 PCC Management System. Each POL service will have a dedicated (v-)VPLS instance that is built to the uplink network ports (NT-A/NT-B hosted LAG) and all LT Line Cards. This (v-)VPLS instance will have the following features enabled, disabled or common across all instances: 1: The Network Ports (NT-A and NT-B SFP ports) are defined as a LAG Group or STP uplink ports or LAG groups. This will be the ‘network’ ingress/egress SAP (Service Access Point) location(s). 2: The LT backplane ports LT1, LT2 -> LT4 or LT8 (FX-4 or FX-8) are the leaf SAP’s. 3: An Ingress QoS profile will be applied per service. This will forward the traffic in an appropriate queue dependent on the service. 4: MAC address limit = ‘4000’. This will limit the MAC learning database per service (VVPLS VLAN) in the Ihub to ‘4000’ entries. This is more than sufficient and provides protection to other services if one service ever experienced a DoS attack via an FDB table ‘thrashing’ preventing the global Ihub limit from being breached. Note: Further details will be covered in the Services training pack, but suffice to say, the LT cards will have multiple SAPs rather than just 1 SAP ID when a service option for FTT Data or HSI Data is selected.

The POL services have 1 Residential-Bridge VLAN/VPLS per service (excluding desktop data and HSI services that have 2 options). Any VLAN tag value can be used, examples as follows: FTT Desktop: v-VPLS/VLAN 100 (data) VOIP/PBX: v-VPLS/VLAN 200 Surveillance: v-VPLS/VLAN 400 WiFi Access Point: v-VPLS/VLAN 500 Security Access Control: v-VPLS/VLAN 600 Public Announcement / Intercom: v-VPLS/VLAN 700 Digital Signage: v-VPLS/VLAN 800 GPON Remote Console Access (Management): v-VPLS 4093 All services will be provided via a Residential i-Bridge VLAN and a v-VPLS, except FTT_Data and HSI which also has a ‘cross-connect VLAN/VPLS’ option as well. In the case of the Residential Bridge VLAN/VPLS solution, a singular 802.1Q VLAN per POL service within the 7360 FX POLT will provide connectivity and specific features enabled/disabled per service. The Channel Partner/Customer will have the flexibility to allocate their own VVPLS/VLAN numbering schemas as their network dictates. The VLAN allocations above are examples only. Therefore the Channel Partner/Customer will declare the v-VPLS, allocate a VLAN number, assign the LAG and LT ports to the service, set the maximum MAC address limit for the v-VPLS and assign the QoS queuing profile. The VPLS/VVPLS component resides in the NT card(s), the VLAN resides in the LT/ONT domain. The cross-connect VLAN/VPLS service option (for FTT Data and HSI) is detailed in the next slide.

The Desktop Data and HSI services have a service ‘option B’ of 1 VPLS and ‘1 per customer connection’ (cross-connect) VLAN per service. Any VLAN tag value can be used, examples as follows: FTT Desktop (data component): v-VPLS 101, ‘x, y, z’ VLAN ID’s for ‘x’ ‘y’ and ‘z’ customer UNI connections. The data component of FTT Desktop sits alongside the Voice component on the previous slide. HSI: As per above, 1 v-VPLS, e.g., ‘300’ (+ cross-connect VLAN per UNI). These two services can alternatively be provided via a cross-connect VLAN per UNI via a singular VPLS. A singular 802.1Q ‘internal’ VLAN is assigned with this per UNI. These VLANs are not ‘visible’ to the external network but are required to mitigate functional behaviour of the G.984 GPON standards behaviour in user-user mode if multicast packets need to be sent also. The different VLAN flag settings via the ‘5 Modes of Operation’ detail the requirements for the necessity of a x-connect/VPLS solution.

Logical Architecture: LT VLANs
To summarise the VLANs on the LT card side for services except ‘FTT Data/HSI x-connect/VPLS solutions): An LT VLAN that matches the VPLS ID is required for all services that ‘bonds’ the ONT UNI Bridge Ports/LT Cards to the VPLS instance (non desktop data services) Only 1 per Chassis for each service is required. This does not map specifically to LTs or LAG Group ports User2user communications, Secure Forwarding, New Broadcast Enablement & DHCP Option82 and queue access control are defined here The LT VLAN when built allows for the VLAN to be assigned to the customer ONT UNI port later in the service build process As well as the VVPLS service declarations in the Ihub, an LT (i-bridge) VLAN is also required to be declared in the IACM (LT Card Group set, acronym meaning ‘Intelligent ASAM Core Module’). This singular service instance applies to all LT cards and does not require assignment to any ‘ports’ (NT ports or LT cards). This VLAN once created globally is then provisioned onto ONT UNI bridge ports to achieve e2e service connectivity. The LT VLAN contains many service setting options. Only a selection of the full capability are used for the POL services and are listed as below. Note that only certain combinations can be selected via the ‘5 Modes of Operation’ detailed in the 4th POL Training module, ‘Services Description’: 1: Leave disabled, the ‘user2user communications’ for services that should not allow direct communications on the user (UNI) domain: HSI, Surveillance, WiFi Access Point, Security Access Control, Public Announcement and Digital Signage. 2: Enable ‘user2user communications’ within the v-VPLS instances for where user2user connectivity is desirable: FTT Desktop data and voice, and VOIP/PBX (to ensure RTP is looped back to minimise traffic to/from IP PBX) if desirable 3: When user2user communications is a desired feature, ‘new broadcast enablement’ is also required (it is disabled by default) as a user needs to downstream broadcast to another user to communicate directly 4: When a Client/Server relationship is required where the client does not ‘seek’ a session, say a phone that has an ARP entry that has timed out, enable ‘new broadcast enablement’ to allow downstream broadcast (it is disabled by default) to ensure the server always can connect to the client. Example being an incoming call to a phone that has no ISAM ARP entry and the SiP soft-switch is required to communicate SiP messaging with the phone. 5: Ingress-QoS profile: Filters all 802.1p markings to an appropriate QoS queue 6: Secure Forwarding: To ensure a heightened security, any fixed static IP address assigned to a device; if another device connects to the ONT UNI port, traffic will not pass for any device using another static IP address. Also, any DHCP issued address will have been snooped by the ISAM and only that source IP address traffic will pass. 7: DHCP Option 82: Will be turned ‘on’ to provide added fields for authentication.

Logical Architecture: LT VLANs (continued)
To summarise the requirements for ‘desktop data’ and ‘HSI’ specific services via x-connect/VPLS services: A unique VLAN is required per ONT UNI and is ‘bonded’ to the VPLS instance (non desktop data services) Therefore every ONT UNI created requires a specific unique VLAN ID A contiguous range of VLAN IDs for these services is recommended for allocation and troubleshooting simplicity User2user communications, Secure Forwarding, New Broadcast Enablement & DHCP Option82 and queue access control are also defined here The LT VLAN (in this configuration option, 1 VLAN per UNI) again contains many service setting options. Only a selection of the full capability are used for the POL services and are listed as follows: 1: Leave configured as default the disablement of ‘user2user communications’ for services that should not allow direct communications on the user (UNI) domain: HSI, Surveillance, WiFi Access Point, Security Access Control, Public Announcement and Digital Signage. 2: Enable ‘user2user communications’ within the VPLS instances for where user2user connectivity is desirable: FTT Desktop data and voice, and VOIP/PBX (to ensure RTP is looped back to minimise traffic to/from IP PBX) 3: When user2user communications is a desired feature, ‘new broadcast enablement’ is also required (it is disabled by default) as a user needs to downstream broadcast to another user to communicate directly 4: When a Client/Server relationship is required where the client does not ‘seek’ a session, say a phone that has an ARP entry that has timed out, downstream broadcast is required so the SIP server can learn the MAC of the IP phone. ‘new broadcast enablement’ to allow downstream broadcast does not need enablement (like a Residential Bridge VLAN) as it automatically is ‘enabled’ on xconnect VLANs, and trying to ‘re set’ this via CLI eventuates in an ‘error’ message. 5: Ingress-QoS profile: filters all 802.1p markings to an appropriate QoS queue 6: Secure Forwarding: To ensure a heightened security, any fixed static IP address assigned to a device; if another device connects to the ONT UNI port, traffic will not pass for any device using another static IP address. Also, any DHCP issued address will have been snooped by the ISAM and only that source IP address traffic will pass. 7: DHCP Option 82: Will be turned ‘on’ to provide added fields for authentication.

Logical Architecture: Resiliency
All LT cards are connected to an ‘A’ and ‘B’ back-plane bus Either NT-A or NT-B can physically (card wise or fibre wise) fail and the LT cards will forward to the back-up NT card The illustration above shows the backplane connectivity to the NT-A and NT-B controllers and in the event of a control card failure, the alternate backplane is used. The Link Aggregation NNI uplinks will connect in an ‘active/active’ state from optical links via both controller cards. The Channel Partner and their Customer is expected to factor into an e2e resiliency model that the uplink switch/router that the 7360 FX is connected to has sufficient fibre path ‘A’ and ‘B’ resiliency and potentially, card/blade and/or multi chassis resiliency dependent on the vendor implementation.

Logical Architecture: PON Resiliency
Fiber duplex system OLT-only duplex system Type A Type B Drop Drop Feeder Feeder Full duplex system Partial duplex system Drop Drop Distribution Feeder Feeder All Protection schemes are defined on “ITU-T G General Characteristics”. The G specifies four types of redundancy between the OLT and ONT. 1: Scenario type A supports spare fiber (the feeder fiber), with no additional LTs or ONTs. 2: Scenario type B defines redundancy to the splitter. LTs and feeder fibers to the first splitter are redundant. One particular case is just feed redundancy but no LT redundancy. In this case we talk about “Type B-” . 3: Scenario type C considers redundancy through the entire path including redundant LTs, fibers, splitters, and fiber to the ONTs. 4: And finally Type D, which is similar to type C but takes into consideration the two splitter levels. The two splitters are found at the ends of the distribution section. Separate geographical paths are required for two feeders to avoid simultaneous fiber cuts. The 7360 FX Uses Type B Type C Type D

Logical Architecture: PON Resiliency (cont)
LT cards are as an option, protected via ‘Type B’ PON redundancy. LT1 (PON ports 1-16) are protected by LT2 (PON ports 1-16) , LT2 (PON ports 1-16) is protected by LT3 (PON ports 1-16) , etc. All PON ports will have the option of dual redundant feed to each optical splitter as per ITU-T G ‘Subscriber Interface Redundancy’. This is an optional function that can be implemented if desired. The layout for utilising this feature is as follows: LT1 PON port 1 and LT2 PON port 1 to the same splitter LT1 PON port 2 and LT2 PON port 2 to the same splitter LT3 PON port 1 and LT4 PON port 1 to the same splitter, etc Therefore every ‘even’ LT slot in the FX-8 chassis (LT cards 2, 4, 6, 8) are the standby redundant PON support for the ‘odd’ numbered LT cards (1, 3, 5, and 7) with the PON port redundancy allocation umbering aligned per splitter in a 1:1, 2:2...16:16 schema. It is essential that the LT cards in a pair are of the same ‘type’ (FGLT-A with FGLT-A for instance). The solution will automatically switch to the standby PON interface when the following link failures are detected on the interface: Loss of G.984 framing LOS (Loss of Signal) Excessive Errors on the active PON based on threshold settings defined in the POL Detailed Design

3 OLT/ONT Software

OLT Software An OLT Shelf (via NT Controllers NT-A/NT-B) has the capability of containing 2 Overall Software Packages (OSWP1 and OSWP2) One OSWP is ‘active’ and one is ‘standby’ These OSWP’s can be switched as an upgrade function The POL solution has only 1 loaded and already set to ‘active’ This OSWP contains the NT cards, and LT cards software files

ONT Software ONT software are discrete files labeled (3)FE12345ABCD01 where the ‘blue’ is ONT model specific, the ‘red’ is the software version for that ONT model Each ONT variant will have a separate ONT software file These ONT s/w files are located in the OLT controller card(s) and downloaded to the ONTs when the ONTs are connected to the PON (and provisioned) ONTs are upgraded by adding new files to the OLT and ‘pointing’ the ONTs to the new s/w file

4 POL Default Infrastructure Build

OLT Infrastructure A full 4Gbyte Compact Flash s/w image is provided for POL OLT s/w provided Customer via CLI and 5571 PCC will load the following: Management VLAN QoS Policies, Bandwidth Shapers and Bandwidth Profiles QoS Queue Definitions Basic Alarm Severities Planning of NT-A/NT-B, shelf and NT redundancy A full listing of infrastructure build is in Appendix B (POL Solution Installation and Configuration Guide)

5 POL Initial Build Process

OLT Initial Build Process: Logical Build
Section 2 -> 4.1 of the ‘POL Solution Installation and Configuration Guide (3HV01415AAAAPCZZA)’ covers this: Perform a checksum integrity check on the Compact Flash Image Burn (chassis specific image) on NT-A/NT-B CF’s Re-insert 2 x NT cards and power up chassis Configure uplink optical ports, LAG groups Add OLT Management IPv4 address/Gateway

OLT Initial Build Process: Logical Build (cont)
Add SNMP Community settings for the PCC 5571 Management System Declare LT Cards Enable 1 or more of the 8/16 PON ports PON Port Protection enabled (if required) Check uplink interface and PON port status Check for alarm status Next step is ONTs and Services…

6 Perform Lab (module 2)

End of Module 2

Passive Optical LAN Training: Module 2: System Architecture (Logical)

Similar presentations

Presentation on theme: "Passive Optical LAN Training: Module 2: System Architecture (Logical)"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Passive Optical LAN Training: Module 2: System Architecture (Logical)

Similar presentations

Presentation on theme: "Passive Optical LAN Training: Module 2: System Architecture (Logical)"— Presentation transcript:

Similar presentations

About project

Feedback