[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]


Classifying Interfaces

To define interface classification scripts with SDX Admin:

  1. In the SDX Admin navigation pane, access a router object in o=network, o=umc.
  2. Click the Interface Classification tab.

The following pane appears.

  1. Use the information in Selecting Interface Classification Criteria and Configuring Interface Classification Targets to configure an interface classification script.

Selecting Interface Classification Criteria

Interface classification criteria define match criteria that are used to find a policy group. Use the fields in this section to define classification criteria.

broadcastAddr

ifAlias

ifDesc

interfaceName

For JUNOS routing platforms: interfaceName="fe-0/1/0.0"

For forwarding interface: interfaceName="FORWARDING_INTERFACE"

ipAddress

ipMask

mtu

nasPortId

pppLoginName

radiusClass

serviceBundle

userIpAddress

virtualRouterName

For JUNOS routing platforms: name of the routing instance

Configuring Interface Classification Targets

The targets of the interface classification scripts are DNs of policy group objects defined in the directory. For example, policyGroupName=DHCP, o=Policies, o=umc

Example: Managing Interfaces for Premium and Basic PPP and DHCP Subscribers

In this scenario, the router manages two types of PPP interfaces—DHCP subscriber interfaces and static IP interfaces. The fastEthernet4/0.1 to fastEthernet4/0.999 interfaces are VLAN interfaces used to terminate DHCP subscribers.

The service provider has separated the PPP subscribers into a premium subscriber group and a basic subscriber group. These groups are distinguished by a different set of default policies applied to the PPP interface. The RADIUS class attribute in the RADIUS profile for premium subscribers is set to Premium. The interface classification script for this scenario is:

The script is processed as follows:

  1. If pppLoginName is not blank and radiusClass is Premium, the PPP-premium policy group is sent to the SAE, and script processing stops.
  2. If script processing proceeds and pppLoginName is not blank, the PPP-basic policy group is sent to the SAE, and script processing stops.
  3. If script processing proceeds and interfaceName is fastEthernet 4/0.0 through fastEthernet 4/0.999, the DHCP policy group is sent to the SAE, and script processing stops.

Example: Managing Specific Interfaces

This example causes the SAE to load the DHCP policy group on IP interfaces on Fast Ethernet modules in slot 3/port 1, slot 1/port 1, or any port on slot 2. The SAE then manages these interfaces.

[policyGroupName=DHCP,o=Policies,o=umc]
interfaceName=FastEthernet3/1
interfaceName=FastEthernet1/1
interfaceName=FastEthernet2/*

Example: Managing Interfaces by Using the Interface Description

This example causes the SAE to load the DHCP policy group on any interface where the ifAlias starts with DHCP-subscribers.

[policyGroupName=DHCP,o=Policies,o=umc]
ifAlias="DHCP-subscribers*"

For this approach, you will need to use the ip description command to configure interface aliases that begin with DHCP-subscribers for all interfaces that support DHCP subscribers.


[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]