Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring Mobile Interfaces for APNs

    You configure the MobileNext Broadband Gateway with mobile interfaces (mif-) for access point name (APN) traffic. The mobile interfaces are distinct from other type of interfaces and are used to associate an APN with a physical interface in a virtual routing and forwarding table (VRF). You need to configure one mobile interface unit for every APN. Every APN is associated with a single logical interface (unit) on a physical port represented by a mobile interface unit.

    Before you begin, you should have done the following:

    • Installed the broadband gateway
    • Installed the boards of the broadband gateway
    • Decided how many initial or additional APNs are required (you can add APNs after initial configuration)

    To configure a mobile interface for mobility, you configure one or more logical interfaces (units) for the interface:

    1. Configure the logical interface.
      [edit interfaces]user@host# set mif unit 0 family inet
    2. Optionally, configure the maximum transmission unit (MTU) size for the mobile interface.
      [edit interfaces]user@host# set mif mtu 1200

      Note: MTU sizes are not mobility specific. However, MTU size is important because the GPRS tunneling protocol (GTP) header can cause a data unit to exceed the maximum frame size when the tunnel headers are added. This causes an error.

    3. Optionally, configure the access control list (ACL) filters to apply to uplink and downlink traffic. By default, the APN accepts all mobile traffic. You can selectively accept or reject mobile traffic based on filter actions.
      [edit interfaces]user@host# set mif unit 0 filter input input-mif-unit0-filter user@host# set mif unit 0 filter output output-mif-unit0-filter

      Note: Filter configuration is not covered as part of mobility topics. The filtering is not mobility specific.

    4. Optionally, configure the service filters to apply to uplink and downlink traffic at the APN level. Typically, these filters would provide services such as Network Address translation (NAT) to mobile traffic. By default, no such services are applied to mobile traffic:
      [edit interfaces]user@host# set mif unit 0 service input service-filter input-service-unit0 service-set nat-service-unit0user@host# set mif unit 0 service output service-filter input-service-unit0 service-set nat-service-unit0

      Note: Service filter configuration is not covered as part of mobility topics. Service filtering is not mobility specific.

    Published: 2011-11-22