Configuring Subscriber Policies

To configure a nondefault client subscriber policy:

1. From Global Configuration mode, create the subscriber policy and assign it an alphanumeric name.

   host1(config)#subscriber-policy client01

   This command accesses Subscriber Policy Configuration mode.

2. From Subscriber Policy Configuration mode, define the rules for each packet or attribute type for which you want to change the default value. (All other packet or attribute types will continue to use the default values listed in Table 22.)

   host1(config-policy)#broadcast permit

   host1(config-policy)#multicast deny

   host1(config-policy)#relearn deny

3. Exit Subscriber Policy Configuration mode.

   host1(config-policy)#exit

4. From Global Configuration mode, associate the new subscriber policy with the bridge group in which the subscriber (client) interface resides.

   host1(config)#bridge westford02 subscriber-policy client01

5. (Optional) Use the appropriate show commands to verify the creation of the subscriber policy and its association with the bridge group interface.

   host1#show subscriber-policy client01

   host1#show bridge westford02

arp

• Use to modify the subscriber policy for ARP to define whether a subscriber (client) bridge interface permits (forwards) or denies (filters or drops) ARP packets.
• Specify one of the following keywords:
  • permit—Forwards packets of this type
  • deny—Filters or drops packets of this type
• ARP packets are forwarded by default.
• Example

  host1(config-policy)#arp deny

• Use the no version to restore the default value.
• See arp.

bridge subscriber-policy

• Use to associate a subscriber (client) bridge interface with a nondefault subscriber policy.
• Specify the following:
  • bridgeGroupName—Alphanumeric name of the bridge group specified in the bridge command
  • subscriberPolicyName—Alphanumeric name of the subscriber policy specified in the subscriber-policy command
• Example

  host1(config)#bridge westford02 subscriber-policy client01

• Use the no version to remove the association with the subscriber policy.

  Note: You cannot change the default subscriber policy values for a trunk (server) bridge interface. As a result, you cannot use the bridge subscriber-policy command to associate a nondefault subscriber policy with a trunk bridge interface.

• See bridge subscriber-policy.

broadcast

• Use to modify the subscriber policy for the broadcast protocol to define whether a subscriber (client) bridge interface permits (forwards) or denies (filters or drops) broadcast packets.
• Specify one of the following keywords:
  • permit—Forwards packets of this type
  • deny—Filters or drops packets of this type
• Broadcast packets are filtered or dropped by default.
• Example

  host1(config-policy)#broadcast permit

• Use the no version to restore the default value.
• See broadcast.

ip

• Use to modify the subscriber policy for IP to define whether a subscriber (client) bridge interface permits (forwards) or denies (filters or drops) IP packets.
• Specify one of the following keywords:
  • permit—Forwards packets of this type
  • deny—Filters or drops packets of this type
• IP packets are forwarded by default.
• Example

  host1(config-policy)#ip deny

• Use the no version to restore the default value.
• See ip.

mpls

• Use to modify the subscriber policy for MPLS to define whether a subscriber (client) bridge interface permits (forwards) or denies (filters or drops) MPLS packets.
• Specify one of the following keywords:
  • permit—Forwards packets of this type
  • deny—Filters or drops packets of this type
• MPLS packets are forwarded by default.
• Example

  host1(config-policy)#mpls deny

• Use the no version to restore the default value.
• See mpls.

multicast

• Use to modify the subscriber policy for the multicast protocol to define whether a subscriber (client) bridge interface permits (forwards) or denies (filters or drops) multicast packets.
• Specify one of the following keywords:
  • permit—Forwards packets of this type
  • deny—Filters or drops packets of this type
• Multicast packets are forwarded by default.
• Example

  host1(config-policy)#multicast deny

• Use the no version to restore the default value.
• See multicast.

pppoe

• Use to modify the subscriber policy for PPPoE to define whether a subscriber (client) bridge interface permits (forwards) or denies (filters or drops) PPPoE packets.
• Specify one of the following keywords:
  • permit—Forwards packets of this type
  • deny—Filters or drops packets of this type
• PPPoE packets are forwarded by default.
• Example

  host1(config-policy)#pppoe deny

• Use the no version to restore the default value.
• See pppoe.

relearn

• Use to modify the relearning policy for a subscriber (client) bridge interface.
• The relearn command defines whether the bridge interface can relearn a MAC address entry on a different interface from the one initially associated with this entry in the forwarding table.
• Specify one of the following keywords:
  • permit—Enables relearning
  • deny—Prohibits relearning and forces the bridge interface to wait until an entry “ages out” of the forwarding table to relearn it on the new interface
• Relearning is enabled by default.
• Example

  host1(config-policy)#relearn deny

• Use the no version to restore the default value.
• See relearn.

subscriber-policy

• Use to create a nondefault subscriber policy for a subscriber (client) bridge interface.
• A subscriber policy is a set of forwarding and filtering rules that defines how the bridge interface handles various packet types.
• You must specify an alphanumeric name for the subscriber policy; the name can be a maximum of 32 characters and can use any combination of alphanumeric characters.
• Example

  host1(config)#subscriber-policy client01

• Use the no version to remove the nondefault subscriber policy.

  Note: You cannot change the default subscriber policy values for a trunk (server) bridge interface. As a result, you cannot use the subscriber-policy command to create a nondefault subscriber policy for a trunk interface.

• See subscriber-policy.

unicast

• Use to modify the subscriber policy for the unicast (user-to-user) protocol to define whether a subscriber (client) bridge interface permits (forwards) or denies (filters or drops) unicast packets.
• Specify one of the following keywords:
  • permit—Forwards packets of this type
  • deny—Filters or drops packets of this type
• Unicast packets are forwarded by default.
• Example

  host1(config-policy)#unicast deny

• Use the no version to restore the default value.
• See unicast.

unknown-destination

• Use to modify the subscriber policy for packets with unknown unicast DAs to define whether a subscriber (client) bridge interface permits (forwards) or denies (filters or drops) packets with unknown unicast DAs.
• Specify one of the following keywords:
  • permit—Forwards packets of this type
  • deny—Filters or drops packets of this type
• Packets with unknown unicast DAs are filtered or dropped by default.
• Example

  host1(config-policy)#unknown-destination permit

• Use the no version to restore the default value.
• See unknown-destination.

unknown-protocol

• Use to modify the subscriber policy for packets containing an unknown protocol to define whether a subscriber (client) bridge interface permits (forwards) or denies (filters or drops) these packets.
• An unknown protocol is any protocol other than ARP, IP, MPLS, or PPPoE.
• Specify one of the following keywords:
  • permit—Forwards packets of this type
  • deny—Filters or drops packets of this type
• Packets containing an unknown protocol are forwarded by default.
• Example

  host1(config-policy)#unknown-protocol deny

• Use the no version to restore the default value.
• See unknown-protocol.

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.