type interface

       type interface-device
       type interface-unit
       type interface-wildcard
       type atm-vci

Mode: Configuration Mode

Description:

The value accepted by all DDL interface types always includes a portion that represents the physical device itself. The acceptable value for this portion depends on the kind of interface.

          type-fpc/pic/port[:channel]

type specifies the media type, such as at for atm interfaces or ge for Gigabit Ethernet interfaces.

fpc is the number for the flexible PIC concentrator (FPC) that houses the physical interface.

pic is the number of the Physical Interface Card (PIC) that houses the physical interface.

port is the number of the port on the PIC that corresponds to the physical interface.

channel is the channel number assigned to the interface. It is required for channelized interfaces, but optional for all other kinds.

DDL has the following interface types defined:

           name of the physical interface device plus an optional channel identifier (e.g. fe-0/0/0)

          name of either a physical interface device or logical interface device. (eg. fe-0/0/0 or fe-0/0/0.0)

          name of a logical interface device. It is the interface-device type plus an optional unit number. If the user does not provide the logical-unit-number, the CLI assigns the default value of 0 (zero). (e.g. fe-0/0/0.1)

          a logical-interface device name that has wildcards in one or more fields. Each field in the name accepts a numerical value can contain instead contain the * (asterisk) wildcard. (e.g. fe-0/*/1.*)

          to require that the user provide a virtual circuit identifier (VCI) for an Asynchronous Transfer Mode (ATM) interface. The vpi portion defines the Virtual Path Identifier (VPI) for the ATM interface and can range from 0 to 255. The vci defines the VCI and can range from 0 to the maximum value value defined for VPIs in the configuration: the absolute possible maxima differ for regular and multicast circuits. A VPI/VCI pairing of 0.0 is not a legal pairing.

Example:

        object newbie {
            help "Newbie DDL testing";
            flag setof list ;

            object interface {
                help "Interface-unit example (has to be atm)";
                flag identifier nokeyword;
                type interface-unit;
                match "at";
            }

            attribute atm-vci {
                 help "Test atm-vci type";
                 type atm-vci;
            }
        }

Display:

        user@router# set example newbie ?
        Possible completions:
          <interface>          Interface-unit example (has to be atm)
        [edit]
        user@router# set example newbie at-1/1/1.1 ?
        Possible completions:
          <[Enter]>            Execute this command
          atm-vci              Test atm-vci type
          |                    Pipe through a command
        [edit]
        user@router# set example newbie at-1/1/1.1 atm-vci 1.1 

        [edit]
        user@router# set example newbie at-2/2/2.2 atm-vci 2.2 

        [edit]
        user@router# show    
        example {
            newbie at-1/1/1.1 {
                atm-vci 1.1;
            }
            newbie at-2/2/2.2 {
                atm-vci 2.2;
            }
        }

        [edit]

See also:

Reference (to programmers guide/style guide):


2007-2008 Juniper Networks, Inc. All rights reserved. The information contained herein is confidential information of Juniper Networks, Inc., and may not be used, disclosed, distributed, modified, or copied without the prior written consent of Juniper Networks, Inc. in an express license. This information is subject to change by Juniper Networks, Inc. Juniper Networks, the Juniper Networks logo, and JUNOS are trademarks of Juniper Networks, Inc.
Generated on Sun May 30 20:23:12 2010 for DDL Reference Guide by doxygen 1.4.5