Port is a device in the EcoRouter, that works at the data-link level. Physical ports are located on the front panel of the router.

The logic of naming and enumeration are described in the Equipment section.

By default, all ports are enabled on your device.

Below the basic port configuration commands are shown.

The transition to the level of a specific port's configuration. Where te1 is its name:

ecorouter (config) #port te1

Setting mtu values different from the standard in the range of 1504-9728. Optional parameter.

ecorouter (config-port) #mtu 1600

For administrative port shutdown use shutdown command in the port configuration context.

For administrative port turn on use no shutdown command in the port configuration context.

For both of these commands you will see report about link state changing.

If the port is turned off by system you will see in show port command its state like "administratively down".

All interfaces and service instances that are bound to the switched off port will be also switched off.

Example:

ecorouter#show port

Gigabit Ethernet [igb] port ge3 is up
 MTU: 9728
 LACP priority: 32767
 Input packets 12757610, bytes 4507446111, errors 0
 Output packets 41139047, bytes 47165314669, errors 0
 Service instance ge3.olia is up
 ingress encapsulation untagged
 ingress rewrite none
 egress encapsulation untagged
 egress none
 Connect bridge raccoon symmetric
 Input packets 12757610, bytes 4507446111
 Output packets 41139681, bytes 47165195683

Gigabit Ethernet [igb] port ge4 is down
 MTU: 9728
 LACP priority: 32767
 Input packets 1468304, bytes 249589783, errors 0
 Output packets 4598726, bytes 5586328327, errors 0
 Service instance ge4.sergey is down
 ingress encapsulation untagged
 ingress rewrite none
 egress encapsulation untagged
 egress none
 Connect bridge raccoon symmetric
 Input packets 1468303, bytes 249590010
 Output packets 4653951, bytes 5592867728

Gigabit Ethernet [igb] port ge5 is up
 MTU: 9728
 LACP priority: 32767
 Input packets 6878595, bytes 3664083768, errors 0
 Output packets 13210832, bytes 14688926470, errors 0
 Service instance ge5.alexander is up
 ingress encapsulation untagged
 ingress rewrite none
 egress encapsulation untagged
 egress none
 Connect bridge raccoon symmetric
 Input packets 6878604, bytes 3664084308
 Output packets 13212782, bytes 14688868859

Gigabit Ethernet [igb] port ge6 is down
 MTU: 9728
 LACP priority: 32767
 Input packets 3103204, bytes 504476889, errors 0
 Output packets 5093754, bytes 4810094601, errors 0
 Service instance ge6.timurr is down
 ingress encapsulation untagged
 ingress rewrite none
 egress encapsulation untagged
 egress none
 Connect bridge raccoon symmetric
 Input packets 3103202, bytes 504475973
 Output packets 5125510, bytes 4812650924

Gigabit Ethernet [igb] port ge7 is down
 MTU: 9728
 LACP priority: 32767
 Input packets 0, bytes 0, errors 0
 Output packets 0, bytes 0, errors 0

ecorouter(config)#port te0

ecorouter(config-port)#shutdown

ecorouter(config-port)#[Fri Sep  2 08:31:10 2016][INFO] PHYS: LINK is DOWN  on port 'te0(0)'

ecorouter#show port

 10 Gigabit Ethernet [none] port te0 is administratively down

  MTU: 9728

  LACP priority: 32767

   link state DOWN;

  Input packets 0, bytes 0, errors 0

  Output packets 0, bytes 0, errors 0

   Service instance te0.100 is down

    ingress encapsulation none

    ingress rewrite none

    egress encapsulation none

    egress none

    Input packets 0, bytes 0

    Output packets 0, bytes 0

   Service instance te0.200 is down

    ingress encapsulation dot1q any

    ingress rewrite none

    egress encapsulation dot1q any

    egress none

    Input packets 0, bytes 0

    Output packets 0, bytes 0

 10 Gigabit Ethernet [none] port te1 is up

  MTU: 9728

  LACP priority: 32767

   link state UP;

  Input packets 0, bytes 0, errors 0

  Output packets 0, bytes 0, errors 0

ecorouter(config-port)#no shutdown

ecorouter(config-port)#[Fri Sep  2 08:34:28 2016][INFO] PHYS: LINK is UP  on port 'te0(0)'

ecorouter#show port

 10 Gigabit Ethernet [none] port te0 is up

  MTU: 9728

  LACP priority: 32767

   link state UP;

  Input packets 0, bytes 0, errors 0

  Output packets 0, bytes 0, errors 0

   Service instance te0.100 is up

    ingress encapsulation none

    ingress rewrite none

    egress encapsulation none

    egress none

    Input packets 0, bytes 0

    Output packets 0, bytes 0

   Service instance te0.200 is up

    ingress encapsulation dot1q any

    ingress rewrite none

    egress encapsulation dot1q any

    egress none

    Input packets 0, bytes 0

    Output packets 0, bytes 0

 10 Gigabit Ethernet [none] port te1 is up

  MTU: 9728

  LACP priority: 32767

   link state UP;

  Input packets 0, bytes 0, errors 0

  Output packets 0, bytes 0, errors 0

Aggregated channel's interface

Interface is a logical interface for the L3 address. Interface name is given by the administrator and is case sensitive (for example: intQQ and intqq, - are different interfaces). Only uppercase and lowercase letters, digits and '.' dot are allowed in the interface names.

In EcoRouterOS, there are L3 interfaces which serve to support certain functional (IP Demux, loopback interfaces, etc.) and are called respectively. As the name of ordinary logical interfaces for L3 addressing, you can not use the names of special interfaces (ALL NAMES ARE REGISTER-DEPENDENT):

• demux.<number>,
• loopback.<number>,
• pppoe.<number>,
• Null,
• vlan.

The basic interface configuration going in the configuration mode:

ecorouter(config)#interface NAME

Creating a user interface. Where NAME is arbitrary name.

General view of the command line to configure interface (context mode of interface configuration).

ecorouter(config-if)#

An assignment of IP address with prefix.

ecorouter(config-if)#ip address 10.10.10.1/24    

An assignment of IP address with a subnet mask.

ecorouter(config-if)# ip address 10.10.10.1 255.255.255.0

ecorouter (config-if) # static-mac 1c87.7640.fa02

Start the interface.

ecorouter(config-if)#no shutdown    

Shut down the interface.

ecorouter(config-if)# shutdown    

Loopback Interface is a virtual loop L3 interface. The name of the loopback interface is defined by the administrator and is case sensitive (for example: Int loopback.QQ and Int loopback.qq, - are different interfaces). The format of the name of the interface: loopback.<NAME> where <NAME> is a number.

In EcoRouterOS, loopback interface numbers must be unique among all created virtual routers. That is, the name loopback.100 can not be used in VR1 and VR2. If one try to use the same name in another virtual device, EcoRouterOS will display an error message explaining that the interface is being used on another device.

Basic setting of the loopback interface:

ecorouter(config)#interface loopback.111

Creating the loopback interface.

ecorouter(config-if-loopback)#ip address 1.1.1.1/32

An assignment of IP address with prefix.

Or:   

ecorouter(config-if-loopback)#ip address 1.1.1.1 255.255.255.255

Assignment of IP address with a subnet mask.

ecorouter(config-if-loopback)#no shutdown

Start the interface.

ecorouter(config-if-loopback)#shutdown

Shut down the interface.

IP Demux Interface is a virtual L3 interface which can be assigned to the IP address from the routed subnet.

Sending packets to the other subnets will be performed by means of binding to a specific port with a set of service instances.

Basic setup of IP demux interface:

Example:

ecorouter(config)#interface demux.0

ecorouter(config-if-demux)#ip address 10.10.10.1/24

Bridge domain is the local broadcast domain of the second OSI model layer, which  exists separate from the concept of VLAN and operates virtual subnets. Bridge domain is created on each device separately and is relevant only for it.

This separation allows you to define different virtual subnets to the one port and to manage individual virtual domains flexibly. Thereby the scalability limit caused by the global VLAN bound to a specific device of the segment is removed.

Bridge domain is constructed from one or more L2 service interfaces, called service-instance.

Command to create bridge domain: bridge <NAME>. Where NAME is an arbitrary name.

Bridge Domain Interface (BDI) is a logical interface that allows you to organize a bi-directional flow of traffic between the networks from the bridge domain to the L3 routing interfaces.

Basic configuration of the interface:

Example:

ecorouter(config)#interface NAME

ecorouter(config-if)#ip address 10.10.10.1 255.255.255.255

ecorouter(config-if)#connect to bridge NAME

PPPoE interface

The Point-to-Point Protocol over Ethernet (PPPoE) is a network protocol for encapsulating PPP frames inside Ethernet frames. The PPPoE mostly used by xDSL services and provides additional features (authentication, encryption, and compression).

The PPPoE server configuration command in EcoRouter are shown in the table below.

pppoe-profile <PROFILE_NAME>

interface pppoe.<IF_NUMBER>

profile <PROFILE_NAME>

Service instance (subinterface, SI) is a logical subinterface operating between L2 and L3 levels. This type of interface is needed to connect the physical port with L3 interface, a bridge, ports. It is used for flexible traffic management which is based on the presence of VLAN tags in the frames, or the lack thereof. Through the service instance passes all traffic that entering the port. There can be a lot of service instances at the one port that handle different VLAN tags in the different ways.

The command to create the service instance: service-instance <NAME>.

Subinterface name is set by the administrator. In every line of service instance can have only one traffic attribute.

Example:

ecorouter(config)#port te0

The service instance is created in the port configuration mode.

ecorouter(config-port)#service-instance 100

ecorouter(config-service-instance)#encapsulation dot1q 4

Specifies the number of processed VLAN.

ecorouter(config-service-instance)#rewrite pop 1

Specifies the operation.

ecorouter(config-service-instance)#connect ip interface e1

Specifies in which interface you want to send the processed frames.