Installation guide

GPON and Active Ethernet UI based zNID
68 FTTH Application Guide
2-8Mbps or even higher and all of the packets for one channel are in a single
packet flow. That is, all of the packets for a single channel look nearly
identical except for the data being transported. Source and destination
addresses, Quality of Service (QoS) markings, and port numbers are the same
for every packet streaming down from the provider's network to the end-user's
STB.
In many networks multicast and unicast video streams constitute the majority
of bandwidth used by the customer and therefore will probably represent the
most processing work for the zNID. If the video traffic is on its own VLAN
we can take advantage of a Zhone browser-based zNID feature called Fast
Path. Fast Path acts as a short cut for packets traveling in the ingress and
egress direction through the zNID. A VLAN configured for Fast Path will
bypass the network processor functions of the zNID which is responsible for
firewall, access lists, security, and any other function that would require the
zNID to look at the packet/frame header values. The main benefit of enabling
Fast Path is speed. By taking a processing load away from the zNID's
network processor faster speeds can be achieved without concern for how
many features are enabled on the unit.
For our configuration, as in the real world environment, you would have
separate private networks for voice and video, and a public networks for data.
Since we are expecting to get a separate IP addresses for voice termination
and data on the zNID, this requires separate DHCP servers on separate
networks in our lab environment and if you follow our example closely, your
environment as well. DHCP servers can only provide one IP address per
MAC address.
These examples are designed to be accomplished in a minimum amount of
time and provide a foundation for understanding other important network
edge access concepts.
Creating the browser-based GPON and Active Ethernet solutions are very
similar
• Use the same Web based user interface
• Use the same uplinks/upstream bridge interfaces, VLANs, and upstream
servers/gateways
The differences in creating the GPON and Active Ethernet solutions are
• In the Web UI you have WAN PON and WAN Ethernet physical
interfaces
• The downlink/downstream bridge interfaces are based on transport media
and there is a GPON specific parameter — GPON traffic profile
• Active Ethernet does not have an activation step for the OLT to recognize
the zNID. Once the bridges are active and the zNID connected, it is ready
to communicate.
The procedures for each solution will be covered separately to avoid
confusion. If you read through both procedures you will see many of the same