Alcatel Unleashed

ip interface RTR1 address 192.168.1.2/24 rtr-port 1/24 rtr-vlan 3

-> show ip interface 
Total 3 interfaces
        Name            IP Address     Subnet Mask   Status Forward  Device
--------------------+---------------+---------------+------+-------+----------------------------------------------------
Loopback             127.0.0.1       255.0.0.0           UP      NO Loopback
RTR1                 192.168.2.1     255.255.255.0     DOWN      NO Rtr-Port 1/2 vlan 3 UNTAGGED
dhcp-client          0.0.0.0         0.0.0.0           DOWN      NO vlan 1  

15. Routed IP Port
Introduction:
AOS currently supports addition of an IP interface on a particular VLAN. The device type is set to
VLAN and the physical ports are attached to the particular VLAN. The current IP interface is not
directly associated with the physical port and the underlying VLAN can support a host of L2 protocols
and also VLAN switching. A routed port is a physical port on which we supporting L3 functionality. To
achieve this we also support an IP interface of new device type “RTR-PORT” and specify the rtr-vlan,
rtr-port and the type (tagged/ untagged VLAN frames) in one go. The user shall not be able to modify
any of these 3 parameters once specified, but will have to delete and recreate the IP interface to
change the association. The user will however be allowed to administratively disable the IP interface.
The underlying rtr-vlan will not switch in L2 as there is only one port associated with the VLAN.
Platforms supported:
OS6850, OS6855, OS6400, OS6850E, OS9000E.
CLI commands:
[no] ip interface <name> {vlan <num> | { rtr-port [<agg_num>| <slot/port>] rtr-vlan <num> [type
{tagged | untagged}]}

rtr-port: The physical port associated with the IP interface (device type “RTR -PORT”). This can be
the “slot/ port” to identify the port or the “agg-num” in the case of a link aggregation port. This
parameter is mandatory for a RTR-PORT IP interface.
rtr-vlan: An unused vlan on the system to be associated with this IP interface. This parameter is
mandatory for a RTR-PORT IP interface.
type: Tagged or untagged specifying whether to handle 802.1q frames or untagged frames on the
specified port. This parameter is optional and defaults to type “untagged” if not specified.
Examples :-
ip interface IP1 rtr-port 1/2 rtr-vlan 20 type untagged
ip interface IP2 rtr-port 3 rtr-vlan 40 type tagged
The IP interface needs to be associated with the rtr-port, rtr-vlan (an unused vlan) and the type
(tagged for handling 802.1q frames on the port or untagged to handle untagged frames) for setting
this to be a RTR-PORT IP interface. The options vlan / rtr-port are mutually exclusive - the device
type will be set to VLAN or RTR-PORT accordingly. Note that the other existing parameters like
address/ mask for an IP interface remain as they are as for a VLAN IP interface