Group by VLAN

The following VLAN Property Table displays the existing VLAN assignments and configurations.

• ID - The VLAN ID (1-4081)

  Note: Clicking on the plus (+) symbol displays the configuration of the interface that the VLANs are associated with.

• Assigned Net Interface - The ESU external interfaces are named "NET1" through "NET12". are assigned to the interface.
• Description - Free form user-defined field to name or describe this uplink interface. Since a VLAN can appear on more than one interface it can be useful for defining where each path terminates (i.e. NET1 (Uplink)).
• IGMP proxy Enabled (True/False) - Defines whether the IGMP proxy should be enabled on the interface. It is assumed that the Network Interface that has the IGMP proxy enabled is the Network Interface where the originator of the IGMP query is found. It is allowed to enable the IGMP Proxy on multiple interfaces when redundant paths are defined.
• User Label - The Name of the VLAN (i.e. Wire Management)
• ACL Mode - Defines the default behavior of the VLAN
• Bridging Type - Defines the basic bridging behavior
• DAI Enabled - Dynamic/Static
• Action > Edit - Provides Editing of the following:
  • User Label - Free form user-defined field to name or describe this uplink interface
  • ACL Mode - Dropdown list of the following:
    • Disable All ACLs - This is the default behavior which disables ACLs on the VLAN results in all traffic being permitted unless an ACL exists on a specific port that denies it. 
    • Basic ACL Default Deny - Only Basic ACLs are allowed on the VLAN, up to 2048 per PON port, up to a total of 8192 per PON card. A permit ACL with a match is required to pass traffic on the port.
    • Extended ACL Default Deny - Basic and Extended ACLs are allowed up to a total of 512 per PON card. System behavior is to deny all traffic unless explicitly permitted by the filter. A permit ACL with a match is required to pass traffic on the port. Deny ACLs are used to discard traffic that is not wanted from the port.
    • Extended ACL Default Permit - Basic and Extended ACLs are allowed up to a total of 512 per PON card. System behavior is to permit all traffic unless explicitly denied by the filter
  • Bridging Type - Dropdown of the following:
    • TLS (Transparent LAN Service) - The successor to SSL or secure sockets layer. Provides secure end to end connections between to applications or users.
    • Full Bridging - This setting is used when a typical Enterprise networking type of bridge behavior is desired. The Full Bridging option bridges any type of traffic and is a standard L2 bridge. This bridge type supports IPv4, IPv6 and any other protocol that runs over Ethernet such as Notables. This bridge type is not protocol aware and therefore many protocol aware functions are not available such as Option 82 insertion, DHCP relay agent, etc. Full Bridging enables flooding of unknown unicast, broadcast, or multicast.

      Multicast flooding is both L2+L3 for N:N connections and L2 for N:N+IPTV connections.

    • Private VLANs - Allows private VLAN service that prevents port to port bridging for untrusted ports. This is typically used to force traffic from ONTs to be sent only to the uplink ports to the network. It prevents user to user bridging.
  • DAI Enabled - Check box:
    • Checked = Enabled (Dynamic)
    • Unchecked = Disabled (Static)
  • MST ID - Current Multiple Spanning Tree Instance (MSTI) ID.
    • Not Implemented
  • Create Uplink Interface - For each Tellabs 1100 Series shelf up to 12 available interfaces (NET1 - NET12) can be configured in Panorama for use by the ONT. To use an interface, at least one ESU port must be assigned. A port can belong to only one interface.
    • Not Implemented

Add VLANS

Note: It is recommended that VLANs 4000-4007, 4011 and 4012 are not used for configuring the system and services. These VLANs are reserved for internal use by the Tellabs 1100 Series system.

Tellabs 1100 Series OLTs use a range of internal network VLANs (2-4094) to route incoming traffic. Within this internal VLAN range, 10 VLANs are reserved for management traffic, control functions, and to transport internal services. The reserved VLAN range defaults to 4000-4007, 4011 and 4012, respectively. Do not use this range of VLANs for other purposes.

The following are typical VLAN naming assignments:

• 100 - Desktop Service
• 200 - Guest Services
• 300 - Remediation
• 350 - PPG
• 2995 - VOIP

Adding VLAN Procedure 

Adding a VLAN is a three-step process:

• Step 1 - Add a VLAN to the System
• Step 2 - Configure the VLAN
• Step 3 - Assign the VLAN to a Network.

Step 1 - Add VLAN

1. Go to Devices and select an OLT (i.e. DallasCorpOLT1-1), click Configuration on the Menu Bar, Verify Group by VLAN option is checked and click on the Add VLANS(s) button.
   
   
    
2.  The Add VLANS dialog is displayed.
3. Add new VLANs (i.d. 2038, 2036, 2037) and click on the + symbol to add to the display window.
4. Repeat until all new VLANs have been entered.
5. Click on the Save button to add the VLANS to the database.
   
   
    
6. When a VLAN is added, default parameters will be applied to the VLAN configuration.

Step 2 - Configure VLAN

1. Go to Devices and select an OLT (i.e. DallasCorpOLT1-1), click Configuration on the Menu Bar, Verify Group by VLAN is checked and click on the Edit button.
   
   
    
2. Select VLAN (i.e. 2037), add User Label (i.e. Testing Portal), select ACL Mode, Bridge Type, and DIA Enabled condition parameters for the selected VLAN.
   
   
    
3. After editing, click on the Save button.

Step 3 - Assign the VLAN to a Network

1. Go to Devices and select an OLT (i.e. DallasCorpOLT1-2), click Configuration on the Menu Bar, Select the Group by NNI option and click on the Assign Vlan button.
   
   
    
2. The Assign VAN(s) to NET2 dialog is displayed.
   
   
    
3. Click on the dialog window to select the available VLANs from the drop-down list to add to the NNI and click on the Save button.
   
   
    

4. Click on the plus (+) symbol to verify the VLAN has been added to the Uplink Network.
   
   
    

Delete VLANS

• Not Implemented

Previous    |   Next