Basic Configurations

This section describes the basic configurations that are available for the ME 1200 Web GUI interface.

Set Device Hostname and admin User Password

In the left panel, click Configuration > System > Information.



Enter the new hostname in the System Name box.

To change the password for a user, click Configuration > Security > Switch > Users.



Click on the user whose password you wish to change, and enter the new password into the Password and Password (again) fields. Click Save.



Set VLAN IP Address

To set an address on a VLAN, first click Configuration > System > IP.



To create a new VLAN, click Add interface. To add an address or alter the address on an existing VLAN, simply type the new address into the appropriate text box along with the subnet mask.

Physical Port Configuration and Status

To configure ports:
  1. To view and alter port configurations, click Configuration > Ports. Configure physical port parameters like enable/disable port, change MTU, and so on.



  2. To monitor port status on the Chassis View, click Monitor > Ports > State.



  3. To monitor port statistics, click Monitor > Ports > Traffic Overview.



  4. To configure the management IP address on the ME 1200, click Configuration > System > IP.



Related Information
Configuring Ports
Monitoring Ports

L2 Switching

The IEEE 802.1Q standard VLANs are supported and the default configuration is as follows:

  • All ports are VLAN aware.

  • All ports are members of VLAN 1.

  • The switch management interface is on VLAN 1.

  • All ports have a Port VLAN ID (PVID) of 1.

  • All ports can send and receive both VLAN-tagged and untagged packets.

In the default configuration, any port is able to send traffic to any other port, and a PC connected to any port will be able to reach the management interface. Broadcast traffic, for example, will be flooded to all ports on the switch.

Note
1 is always reserved for the default VLAN. The range of the VLAN ID is 2 to 4095.

Configuring VLAN for UNI and NNI Ports


Note
It is recommended that you retain both ports as trunk ports with the range of all allowed VLANS.


For more information on configuring a private VLAN, see the Configuring Private VLANs section. .

Port Mode

The port mode (default is Access) determines the fundamental behavior of the port in question. A port can be in one of three modes as described below.

  • Access

    Access ports are normally used to connect to end stations. Dynamic features like Voice VLAN may add the port to more VLANs behind the scenes. Access ports have the following characteristics:

    • Member of exactly one VLAN, the Port VLAN (also called as Access VLAN), which by default is 1, accepts untagged frames and C-tagged frames.

    • Discards all frames that are not classified to the Access VLAN.

    • On egress all frames are transmitted untagged.

  • Trunk

    Trunk ports can carry traffic on multiple VLANs simultaneously, and are normally used to connect to other switches. Trunk ports have the following characteristics:

    • By default, a trunk port is member of all existing VLANs. This may be limited by the use of Allowed VLANs.

    • By default, all frames but frames classified to the Port VLAN (also called as Native VLAN) get tagged on egress. Frames classified to the Port VLAN do not get C-tagged on egress.

    • Egress tagging can be changed to tag all frames, in which case only tagged frames are accepted on ingress.

  • Hybrid

    Hybrid ports do resemble trunk ports in many ways, but adds additional port configuration features. In addition to the characteristics described for trunk ports, hybrid ports have these abilities:

    Port Type

    Ports in hybrid mode allow for changing the port type, that is, whether a frame's VLAN tag is used to classify the frame on ingress to a particular VLAN, and if so, which TPID it reacts on. Likewise, on egress, the Port Type determines the TPID of the tag, if a tag is required.

    Unaware: On ingress, all frames, whether carrying a VLAN tag or not, get classified to the Port VLAN, and possible tags are not removed on egress.

    C-Port: On ingress, frames with a VLAN tag with TPID = 0x8100 get classified to the VLAN ID embedded in the tag. If a frame is untagged or priority tagged, the frame gets classified to the Port VLAN. If frames must be tagged on egress, they will be tagged with a C-tag.

    S-Port: On ingress, frames with a VLAN tag with TPID = 0x8100 or 0x88A8 get classified to the VLAN ID embedded in the tag. If a frame is untagged or priority tagged, the frame gets classified to the Port VLAN. If frames must be tagged on egress, they will be tagged with an S-tag.

    S-Custom-Port: On ingress, frames with a VLAN tag with a TPID = 0x8100 or equal to the Ethertype configured for Custom-S ports get classified to the VLAN ID embedded in the tag. If a frame is untagged or priority tagged, the frame gets classified to the Port VLAN. If frames must be tagged on egress, they will be tagged with the custom S-tag.

Related Information
Configuring VLANs
Monitoring VLANs

MAC Table Configuration

The following per port configuration parameters are available for MAC Learning configuration:

  • Auto - Learning is done automatically as soon as a frame with unknown SMAC is received.

  • Disable - No learning is done.

  • Secure - Only static MAC entries are learned, all other frames are dropped.

The static entries can be configured in the MAC table for forwarding and the below parameters are allowed. The static MAC table can contain 64 entries.

To configure the MAC table, Configuration > MAC Table.



To view the MAC table, Monitor > MAC Table.



Related References
Configuring MAC Table
Related Information
Monitoring MAC Table

Ethernet Services

MEF standards describe services provided to customers at User Network Interfaces (UNIs). Inside provider networks, nodes are connected using Internal Network-to-Network Interfaces (I-NNIs). Connections between service providers are done using External Network-to-Network Interfaces (E-NNIs). An Ethernet Virtual Connection (EVC) is an association of two or more UNIs.

Port Configuration

The EVC per Port configurations that are allowed are as shown below. Retain the default configuration for the MEF services.



Related Concepts
EVC Port Configuration

Bandwidth Profiles Configuration

The EVC ingress bandwidth profile configurations are allowed as shown. These policers may be used to limit the traffic received on UNI ports.
Policer Mode Coupled , Aware
CIR 0 to 10000000 kbps
CBS 0 to 100000 bytes
EIR 0 to 10000000 kbps
EBS 0 to 100000 bytes


Related Concepts
EVC Bandwidth Profile Configuration

EVC

The EVC configurations that are allowed are as shown in the following table.
Configurable Parameter Allowed Range
NNI Port Any port number of the switch
EVC ID 1 to 128
VLAN ID 1 to 4095
Internal/ Classified VLAN ID 1 to 4095


ECE

The EVC Control Entry configurations that are allowed are as shown below.

These parameters vary according to the Tag type selected. The User Network Interface (UNI) port(s) needs to be selected for the ECE, and then the Tag type. Different parameter options are displayed depending on the Tag type selected.





For details of each parameter, refer to the Help section on the GUI. The EVC/ECE Service statistics can be viewed via the Monitor pages.

EVC Statistics



ECE Statistics



EPL Service between UNI and NNI

To set up an EPL service between UNI and NNI:

  • Set up an EPL service (all to one bundling) on a UNI (port 1).

  • On NNI (port 4) egress, add a tag (54).

  • On UNI egress, pop or remove the tag.



First, create EVC as shown below. VID is 54, for IVID, that is, the internal VID used for internal classification is also set to 54, but any unique value can be used. Learning is disabled because this is a point to point service and the NNI port is 4. Double VLAN tagging on the NNI is not used, so no inner tag is specified. The Outer Tag VID used for uni-directional NNI to UNI service and is not used here.



Then, create EVC Control Entry (ECE). The ECE controls the UNI configuration. The following parameters are used for this service:

  • UNI port is port 1.

  • UNI matching is any for all to one bundling.

  • MAC parameters are set to any.

  • NNI outer tag allows inserting a tag on the UNI. This is for unidirectional services only.

    Actions: EVC ID is 1.

    • Direction is both equal to a bidirectional service.

    • Tag Pop Count is 0 for EPL service, that is, all frames are passed to the EVC without popping any tags.

    • The policy ID is used to point to an ACL. The ACL can then be used to select an EVC policer. This service is not using any policer, policy ID 0 is used.





EVPL Service between UNI and NNI (bundle #1)



Set up an EVPL service (bundling) on a UNI (port 2) for CEVLAN IDs 10-20.

  • On NNI (port 4) egress, add a tag 54.

  • On UNI egress, pop or remove the tag.

EVC configuration is the same as the first example.

ECE Configuration

Create ECE (EVC Control Entry)

The following parameters are used for this service:

  • UNI port is port 2.

  • Uni Matching VID 10-20.

  • MAC parameters are set to any.

  • NNI outer tag allows to insert a tag on the UNI. This is for uni-directional services only, and is not used here.

Actions: EVC ID is 2.

  • Direction is both equal to a bidirectional service.

  • Tag Pop Count is 0 for EVPL service, that is, all frames are passed to the EVC without popping any tags. The UNI tag is preserved.

  • The policy ID is used to point to an ACL. The ACL can then be used to select an EVC policer. This service is not using any policer, policy ID 0 is used.



EVPL service between UNI and NNI (bundle #2), same UNI, NNI as above



Set up an EVPL service (bundling) on a UNI (port 2) for CEVLAN IDs 61, 64, 70.

  • On NNI (port 4) egress, add a tag 54.

  • On UNI egress, pop or remove the tag.

First, create EVC as shown in figure. VID is 54, Inner VID is 54. Learning is disabled because this is a point-to-point service and the NNI port is 4. Then, create ECE (EVC Control Entry).

The following parameters are used for this service:

  • UNI port is port 2.

  • UNI Matching VID 61.

  • MAC parameters are set to any.

  • NNI outer tag allows to insert a tag on the UNI. This is for unidirectional services only, and is not used here.

Actions: EVC ID is 3.

  • Direction is both equal to a bidirectional service.

  • Tag Pop Count is 0 for EVPL service, that is, all frames are passed to the EVC without popping any tags. The UNI tag is preserved.

  • The policy ID is used to point to an ACL. The ACL can then be used to select an EVC policer. This service is not using any policer, policy ID 0 is used.


Create similar ECE for 64 and 70 with the same EVC ID.