DESCRIPTION     4/221 02-CRA 119 1170/1-V1 Uen B5    

Technical Product Description 

SmartEdge OS for SmartEdge Routers , Release 6.3.1

© Ericsson AB 2009-2010. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Trademark List

SmartEdge is a registered trademark of Telefonaktiebolaget L M Ericsson.
NetOp is a trademark of Telefonaktiebolaget L M Ericsson.

Contents

1Introduction

2

New and Enhanced Software Features
2.1New and Enhanced Software Features in Release 6.3.1.2
2.2New and Enhanced Software Features in Release 6.3.1.1

3

New Hardware
3.1New Hardware in Release 6.3.1.2
3.2New Hardware in Release 6.3.1.1

4

PPA Feature Support

5

APS Traffic Card and Feature Compatibility
5.1POS APS Ports

Glossary

Reference List


1   Introduction

This document describes the new and enhanced software features in Release 6.3.1 of the SmartEdge® OS for . It also describes the new hardware available with this product release.

Note:  
This document does not describe all features; it describes only those that are new or enhanced in the current release.

For software installation and upgrade instructions, see the installation documentation for your specific release listed in Reference List. For information on the changes to default system behavior that are introduced in this release, see Reference [10].

2   New and Enhanced Software Features

2.1   New and Enhanced Software Features in Release 6.3.1.2

The following software features are new or enhanced in Release 6.3.1.2.

2.1.1   PWFQ Support on 8-Port POS OC-3c/STM-1c and 4-Port POS OC-12c/STM-4c Line Cards

In Release 6.3.1.2, Priority Weighted Fair Queuing (PWFQ) is supported on the 8-port POS OC-3c/STM-1c and the 4-port POS OC-12c/STM-4c line cards.

2.1.2   IPv6 Subscriber Licensing

Table 1 describes feature support on PPA version 1, version 2, and version 3 for the SmartEdge OS, Release 6.3.1.2.

Table 1    PPA Support for Release 6.3.1.2

Feature

PPA1

PPA2

PPA3

Notes

IPv6 subscriber licensing

No

Yes

Yes

Supported on the following PPA2-based traffic cards only:


  • PPA2-based 10-port Gigabit Ethernet

  • 2-port 60 Fast Ethernet–Gigabit Ethernet

  • 1-port 10 Gigabit Ethernet


Supported on the following PPA3-based traffic cards only:


  • PPA3-based 10-port Gigabit Ethernet

  • PPA3-based 20-port Gigabit Ethernet

The SmartEdge router now requires you to enable an IPv6 subscriber license before you configure IPv6 subscriber services.

In software license configuration mode, use the subscriber command as follows to enable an IPv6 subscriber license on the SmartEdge router:

subscriber active ipv6 sub-num password password

Replace the sub-num argument with the number of active subscriber sessions licensed, using one of the following keywords:

Replace the password argument with the unencrypted paid license password required to enable the IPv6 subscriber function.

Note:  
For IPv6 subscriber sessions, the SmartEdge router supports only unencrypted passwords.

Consider the following when enabling an IPv6 license on the SmartEdge router:

The new show subscribers summary command displays information about the subscriber sessions on the system. You can display information about IPv4, IPv6, and dual-stack subscriber sessions.

The new show subscribers license summary command displays information about the subscriber licenses currently used by the system.

2.2   New and Enhanced Software Features in Release 6.3.1.1

The following software features are new or enhanced in Release 6.3.1.1.

2.2.1   Support for IPv6 Subscriber Services

When configured as a BRAS, the SmartEdge router now supports the address assignment and management of IPv6 PPP subscribers. The sections that follow describe the implementation and configuration of IPv6 subscriber services for single (IPv6 only) and dual stack (IPv6 and IPv4) PPP subscribers on a SmartEdge OS BRAS.

This feature description describes the following new features:

2.2.1.1   Hardware Support

IPv6 subscriber services are supported on the following SmartEdge routers:

Subscribers can be single stack or dual stack. Table 3 shows the number of dual-stack subscribers the SmartEdge router supports for each card type:

Table 2    Number of Dual-Stack Sessions per Card

Card Type

Number of Sessions per System

XCRP3 Controller card

32,000

XCRP4 Controller card

64,000

PPA2-based 10-port Gigabit Ethernet traffic card

16,000

PPA2-based 2-port 60 Fast Ethernet–Gigabit Ethernet traffic card

16,000

PPA2-based 1-port 10 Gigabit Ethernet traffic card

16,000

PPA3-based 10-port Gigabit Ethernet

24,000

PPA3-based 20-port Gigabit Ethernet

24,000

2.2.1.2   IPv6 Subscriber Service Support on the SmartEdge Router

The SmartEdge router supports IPv6 subscriber services for PPP and PPPoE subscribers only. IPv6 prefixes can be configured statically or through DHCPv6 PD using the formatting rules defined in RFC 4291, IP Version 6 Addressing Architecture. The SmartEdge router uses ND to assign an IPv6 prefix to the WAN link between the BRAS and CPE router.

The SmartEdge OS supports IPv6 subscriber services as follows:

See Reference [9] for more information about how IPv6 subscriber services are supported on the SmartEdge router.

2.2.1.3   Restrictions

2.2.2   How to Configure a BRAS for Dual-stack Subscriber Support

To configure IPv6 subscriber services on a SmartEdge router:

  1. Configure an interface with a GUA on the link between the BRAS and the CPE.
  2. Configure a DHCPv6 server policy on the SmartEdge router.
  3. Configure one or more multibind interfaces to use the DHCPv6 server policy.
  4. Enable RADIUS or local subscriber authentication.
  5. If you do not want to use the default ND profile, create and configure an ND profile.
  6. If you are using local subscriber authentication, configure the subscriber attributes in a subscriber record. If using a non-default ND profile, reference the ND profile you created in Step 5 in the subscriber record or profile.

    If you are using RADIUS authentication, skip this step. If you are using a RADIUS server for subscriber authentication, skip this step and perform Step 7.

  7. Configure a PPP- or PPPoE-encapsulated circuit on the WAN link between the BRAS and the CPE.

See Reference [9] for more information and examples of how to configure IPv6 subscriber services on the SmartEdge router.

2.2.3   New and Changed Commands

This section describes the new commands that have been added and existing commands that have been modified to support the configuration of IPv6 subscriber services on the SmartEdge router. Commands are organized in tables that fall into a particular functional group.

Table 3 describes the new RADIUS attribute command:

Table 3    New and Modified IPv6 RADIUS Attribute Commands

Command

Description

Command Mode

radius attribute NAS-IPV6-Address interface if-name


[no | default] radius attribute NAS-IPV6-Address interface if-name


Example:


[local]BRAS(config-ctx)#radius attribute NAS-IPV6-Address interface if1

Configures the IPv6 address of the NAS for RADIUS access-request and access-accounting messages.


Replace the if-name argument with the name of the interface whose primary IPv6 address is used as the source IPv6 address sent in RADIUS packets.


If the interface is not configured or is unreachable, the IPv6 address of the outgoing interface is used instead as the source IPv6 address for packets.

context configuration

Table 4 describes the new and modified IPv6 subscriber attribute commands:

Table 4    New and Modified IPv6 Subscriber Attribute Commands (for subscriber records and profiles)

Command

Description

Command Mode

dns6 {primary | secondary} ipv6-address


[no | default] dns6 {primary | secondary} ipv6-address


Example:


[local]BRAS(config-ctx)#subscriber name kenny


[local]BRAS(config-sub)#dns6 primary 2001:db:b:4f::2

Specifies the primary and secondary DNS IPv6 addresses.


  • primary—Configures the IPv6 address of a primary DNS server.

  • secondary—Configures the IPv6 address of a secondary DNS server.

  • ipv6-address—Specifies a DNS server IPv6 address.

subscriber record configuration

ipv6 delegated-prefix ipv6-prefix


[no | default] ipv6 delegated-prefix ipv6-prefix


Example


[local]BRAS(context)#subscriber name test


[local]BRAS(config-sub)#ipv6 delegated-prefix 2001:db8:1::/48

Specifies the delegated IPv6 prefix to use for DHCPv6 PD.


Replace the ipv6-prefix argument with the delegated IPv6 prefix to use for DHCPv6 PD.

subscriber record configuration

ipv6 framed-prefix ipv6-prefix


[no | default] ipv6 framed-prefix ipv6-prefix


Example


[local]BRAS(config-sub)#ipv6 framed-prefix 2001:db8:b:4f::/64

Specifies the prefix advertised to the subscriber using ND.


Replace the ipv6-prefix argument with the prefix advertised to the subscriber using ND.

Subscriber record configuration

ipv6 framed-route ipv6-prefix next-hop metrics


[no | default] ipv6 framed-route ipv6-prefix next-hop metrics


Example


[local]BRAS(config-sub)#ipv6 framed-route
2010:db8:b:5f::1/48 2002:db8:b:5f::1 1000

Specifies a static IPv6 route that will be installed for subscriber.


  • ipv6-prefix—Specifies an IPv6 prefix (in the form A:B:C:D:E:F:G:H) and prefix length, separated by the slash (/) character.

  • next-hop—Specifies the IPv6 address of a next hop router that can reach the target network or subnet.

  • metrics—Range is from 1 through 65536.

Subscriber
record configuration

ipv6 nd-profile name


[no | default] ipv6 nd-profile name


Example


[local]BRAS(context)#subscriber name test


[local]BRAS(config-sub)#ipv6 nd-profile abc

Assigns an ND profile to a subscriber or subscriber profile.


Use the name argument to specify an ND profile to be used with the subscriber or subscriber profile.

default subscriber
profile configuration


subscriber record configuration


subscriber profile configuration

ipv6 source-validation


[no | default] ipv6 source-validation


Example


[local]BRAS(config-ctx)#subscriber name test


[local]BRAS(config-sub)#ipv6 source-validation

Enables source validation for IPv6.

default subscriber
profile configuration


subscriber record configuration


subscriber profile configuration

Table 5 describes the new DHCPv6 commands:

Table 5    New DHCPv6 Commands

Command

Description

Command Mode

clear dhcpv6 statistics


Example:


[local]BRAS#clear dhcpv6 statistics

Clears Dynamic Host Configuration Protocol Version 6 (DHCPv6) statistics.

exec

dhcpv6 server {interface | ipv6-addr}


[no | default] dhcpv6 server {interface | ipv6-addr}


Example:


[local]BRAS(context)#interface test-last multibind lastresort


[local]BRAS(config-if)#ip unnumbered test-lb


[local]BRAS(config-if)#dhcpv6 server interface

Configures an interface to be a DHCPv6 server interface. The DHCPv6 server can use the primary IPv6 address of the interface as the server IP address or a specified IPv6 address.

Interface
configuration

option domain name-server server-address


[no | default] option domain name-server server-address


Example


[local]BRAS(config-ctx)#dhcpv6 server


[local]BRAS(config-dhcpv6-server)#option domain-name-server 2005:db8:b:3f::2

Specifies the IP address of a DNS name server.


Replace the server-address argument with the IP address of a DNS name server.

DHCPv6 server
policy configuration


DHCPv6 server
policy subnet configuration

option domain-search domain-name


[no | default] option domain-search domain-name


Example


[local]BRAS(config-ctx)#dhcpv6 server


[local]BRAS(config-dhcpv6-server)#option domain-search SJ1.com

Specifies a domain name for DNS resolution.


Replace the domain-name argument with the name of the domain for DNS resolution

DHCPv6 server
policy configuration


DHCPv6 server
policy subnet configuration

option preference integer


[no | default] option preference integer


Example


[local]BRAS(config-ctx)#dhcpv6 server


[local]BRAS(config-dhcpv6-server)#option preference 5

Configures the preference value for this DHCPv6 server.


Replace the integer argument with the preference value for this DHCPv6 server. A DHCPv6 server with a lower value is preferred over a server with a higher value. Range is from 0 through 255.

DHCPv6 server
policy configuration


DHCPv6 server
policy subnet configuration

option rapid-commit


[no | default] option rapid-commit


Example


[local]BRAS(config-ctx)#dhcpv6 server


[local]BRAS(config-dhcpv6-server)#option rapid-commit

Enables Rapid Commit for faster IPv6 prefix delegation.

DHCPv6 server
policy configuration


DHCPv6 server
policy subnet configuration

option information-refresh-time seconds





[no | default] option information-refresh-time seconds





Example


[local]BRAS(config-ctx)#dhcpv6 server


[local]BRAS(config-dhcpv6-server)#option information-refresh-time 3000000

Specifies the number of seconds a client waits before refreshing the configuration information received from DHCPv6 server.


Replace the seconds argument with the number of seconds a client waits before refreshing the configuration information received from DHCPv6 server. Range is from 600 through 4294967295 seconds.

DHCPv6 server
policy configuration


DHCPv6 server
policy subnet configuration

prefix lifetime {preferred seconds valid seconds | infinite}


[no | default] prefix lifetime {preferred seconds valid seconds | infinite}


Example


[local]BRAS(config-ctx)#dhcpv6 server


[local]BRAS(config-dhcpv6-subnet)#prefix lifetime preferred 900 valid 1200

Configures the length of time the subscriber router can use a delegated IPv6 prefix and a given DHCPv6 prefix.


  • preferred seconds—Number of seconds the IPv6 addresses using the delegated IPv6 prefix are preferred. Range is from 600 through 4294967294 seconds.

  • valid seconds—Number of seconds a delegated IPv6 prefix is valid and can be used by a client. Range is from 600 through 4294967294 seconds.

  • infinite—Configures both the preferred and valid lifetimes to be infinite.

DHCPv6 server
policy configuration


DHCPv6 server
policy subnet configuration

show dhcpv6 log [circuit slot/port:ch:sub] [duid hex-string] [prefix ipv6-prefix/length]


Example


[local]BRAS#show dhcpv6 log

Displays the DHCPv6-PD log history.


  • circuit slot/port:ch:sub—Filters log messages by circuit. The slot/port:ch:sub argument is the slot and port, channel, and subchannel numbers for a circuit.

  • duid hex-string—Filters log messages by DHCPv6 server DUID; hex-string is a colon-delimited hexadecimal number.

  • prefix ipv6-prefix/length—Filters log messages by IPv6 prefixes; the ipv6-prefix/length argument specifies an IPv6 prefix and length in the format A:B:C:D::E/length; the length can be from 0 to 128.

all modes

show dhcpv6 server duid


Example


[local]BRAS#show dhcpv6 server duid

Displays the DUID that the SmartEdge OS DHCPv6-PD Server is using as its identifier when communicating with clients.

all modes

show dhcpv6 server host [circuit slot/port:ch:sub | duid hex-string | prefix host-prefix | subnet prefix/length] [detail | summary]


Example


[local]BRAS#show dhcpv6 server host detail

Displays information about DHCPv6-PD server hosts, which you can filter by one of the following:


  • circuit slot/port:ch:sub—Filters DHCPv6 information by circuit. The slot/port:ch:sub argument is the slot and port, channel, and subchannel numbers for a circuit.

  • duid hex-string—Filters dhcpv6 information by DHCPv6 server DUID; hex-string is a colon-delimited hexadecimal number.


  • prefix ipv6-prefix/length—Displays information about the DHCPv6 server with the matching IPv6 prefixes; the ipv6-prefix/length argument specifies an IPv6 prefix and length in the format A:B:C:D::E/length; the length can be from 0 to 128.

  • subnet prefix/length—Displays information about the hosts on the specified subnet (per context). Filters by all subnets whose address part match the specified prefix and length.


You can add the detail or summary keyword after a filtering construct:


  • detail—Displays detailed information. Mutually exclusive with the summary keyword.

  • summary—Displays summarized information. Mutually exclusive with the detail keyword.

all modes

show dhcpv6 statistics [clear] [detail]


Example


[local]BRAS#show dhcpv6 statistics

Displays and optionally clears DHCPv6-PD statistics.


  • clear—Clears DHCPv6 statistics after producing the output.

  • detail—Displays detailed DHCPv6 statistics.

all modes

subnet ipv6-prefix


[no | default] subnet ipv6-prefix


Example


[local]BRAS(config-ctx)#dhcpv6 server


[local]BRAS(config-dhcp-server)#subnet 2001:a:b:3f::/64

Accesses DHCPv6 server policy subnet configuration mode, where you can configure DHCPv6 server attributes that are applicable only to subscribers in the specified subnet.


Replace the ipv6-prefix argument with an IPv6 prefix that does not match any other interface prefix.

DHCPv6 server
policy configuration

Table 6 describes the new and modified ND profile commands:

Table 6    New IPv6 ND Commands

Command

Description

Command Mode

nd profile profile-name


[no] nd profile profile-name


Example:


[local]BRAS(config-ctx)#nd profile ndpro2

Use the nd profile command in the context configuration mode to configure an ND profile or select an existing one for modification, and enter ND profile configuration mode. In ND profile configuration mode, you can configure the ND parameters to apply to the profile. After you create the profile, you can assign it to an IPV6 subscriber by specifying the profile name under the appropriate subscriber record using the ipv6 nd profile command.


Replace the profile-name argument with the name of the ND profile you want to configure.


If an ND profile is not assigned to an IPV6 subscriber circuit, ND assigns a default ND profile (GLOBAL DEFAULT PROFILE) to the circuit. This profile consists of default values for each ND parameter.

context
configuration

dad-transmits num-dad-transmits


[default] dad-transmits


Example:


[local]BRAS(config-ctx)#nd profile ndpro1


local]BRAS(config-nd-profile)#dad-transmits 3

Configures the number of NS messages the SmartEdge router sends to its peers for DAD to ensure that the link-local address of the SmartEdge router and the global unicast address of the interface that is bound to the circuit are unique. If the router does not receive a response after the last NS message is sent, the addresses are considered unique.


Replace the num-dad-transmits argument with the number of NS messages the SmartEdge router sends to its peers for DAD to ensure that the link-local address of the SmartEdge router and the global unicast address of the interface that is bound to the circuit are unique.

ND profile
configuration

ns-retry-interval retrans-timer


[no | default] ns-retry-interval


Example:


[local]BRAS(config-ctx)#nd profile ndpro1


[local]BRAS(config-nd-profile)#ns-retry-interval 100

Specifies the value for the Retrans Timer field, which is the time between retransmitted Neighbor Solicitation (NS) messages.


Replace the retrans-timer argument with a Retrans Timer value (in milliseconds). The range of values is 0 to 4294967295; the default value is 5,000

ND profile
configuration

preferred-lifetime {preferred-lifetime | infinite}


default preferred-lifetime


Example:


[local]BRAS(config-ctx)#nd profile ndpro1


[local]BRAS(config-nd-profile)#preferred-lifetime infinite

Specifies the preferred lifetime for one or more IPv6 prefixes advertised in an RA message. This value is the length of time in seconds that the IPv6 address generated from an IPv6 prefix remains preferred. In ND profile configuration mode, this command specifies the value for the subscribers using the specified ND profile.


  • preferred-lifetime—Value for the preferred lifetime, in seconds. The range of values is 0 to 4,294,967,295.

  • infinite—Sets the value of the preferred lifetime to the lifetime of the subscriber circuit. This is the default configuration.

ND profile
configuration mode

proto-down-on-dad


[no | default] proto-down-on-dad


Example:


[local]BRAS(config-ctx)#nd profile ndpro1


[local]BRAS(config-nd-profile)#proto-down-on-dad

Enables the SmartEdge router to send a request to bring down the IPv6 stack of the subscriber circuit in which a duplicate address detection (DAD) failure is detected. If the subscriber circuit consists of only an IPv6 stack (without an IPV4 stack), then the entire subscriber circuit is brought down.

ND profile
configuration mode

ra-intervalra-interval


default ra-interval


Example:


[local]BRAS(config-ctx)#nd profile ndpro1


[local]BRAS(config-nd-profile)#ra-interval 90

Configures the interval between transmissions for RA messages.


Replace the ra-interval argument with the RA interval between transmissions (in seconds). The range of values is 0 to 600. A value of 0 disables unsolicited RA messages.

ND profile
configuration

ra-lifetime ra-lifetime


default ra-lifetime


Example:


[local]BRAS(config-ctx)#nd ra ndpro1


[local]BRAS(config-nd-profile)#ra-lifetime 24000

Configures the lifetime of RA messages.


Replace the ra-lifetime argument with the RA lifetime (in seconds). The range of values is 30 to 36,000; the default value is 1,800.

ND profile
configuration

ra-managed-config


[no | default] ra-managed-config


Example:


[local]BRAS(config-ctx)#nd profile ndpro1


[local]BRAS(config-nd-profile)#ra-managed-config

Enables the managed-address configuration flag in RA messages. This setting indicates that the IPv6 address is available through the DHCPv6 protocol. If the managed-address configuration flag is disabled, the IPv6 address may or may not be available through this protocol.

ND profile
configuration

ra-on-link


[no | default] ra-on-link


Example:


[local]BRAS(config-ctx)#nd profile ndpro1


[local]BRAS(config-nd-profile)#ra-on-link

Enables the on-link flag for IPv6 prefixes in RA messages. This setting indicates that the IPv6 prefix advertised in RA messages is associated with an interface on a specific link. If the on-link flag is disabled, the prefix is not associated with an interface on a specific link.

ND profile
configuration

ra-other-config


[no | default] ra-other-config


Example:


[local]BRAS(config-ctx)#nd profile ndpro1


[local]BRAS(config-nd-profile)#ra-other-config

Enables the other-config flag in RA messages. This setting indicates that other configuration information is available in the RA messages. If the other-config flag is disabled, other configuration information is not available.

ND profile
configuration

valid-lifetime {lifetime | infinite}


[no | default] valid-lifetime


Example:


[local]BRAS(config-ctx)#nd profile ndpro1


[local]BRAS(config-nd-profile)#valid-lifetime 43200

Specifies the valid lifetime in the Prefix Information option for IPv6 prefixes included in an RA message. This value equals the length of time that an IPv6 prefix is valid for on-link determination. In ND profile configuration mode, this command specifies the value for this ND profile.


  • lifetime—Configures the valid lifetime, in seconds. The range of values is 0 to 4,294,967,295.

  • infinite—Sets the valid lifetime to the lifetime of the subscriber circuit.

ND profile
configuration mode

show nd circuit [circuit-handle | detail | interface]


Example:


[local]BRAS#show nd circuit

Displays ND circuit information for one or more ND circuits. Specify a circuit handle to display ND circuit information for the specified circuit. If the circuit handle is omitted, a summary for all circuits on the specified port or channel is displayed.


  • circuit-handle—Configures the circuit handle of the circuit, in the following syntax: slot/port:channel:sub-channel/circuit-id.

  • detail—Displays detailed ND circuit information.

  • interface—Displays all ND circuits bound to the interface.

All modes

show nd profile [profile-name]


Example:


[local]BRAS#show nd profile ndpro1

Displays ND profile information for a context. If the profile name is omitted from the command, all ND profiles within the context (including the default profile GLOBAL_DEFAULT_PROFILE) is displayed.


You can optionally replace the profile-name argument with the name of a specific profile to display all of the ND profile parameters for that profile.

All modes

Table 7 describes the new and modified commands used for monitoring and troubleshooting IPv6 subscriber services.

Table 7    New IPv6 Subscriber Services Monitoring and Troubleshooting Commands

Command

Description

Command Mode

debug ipv6 prefix-library {all | error | general}


Example:


[local]BRAS>debug ipv6 prefix-library

Enables the generation of debug messages for the IPv6 prefix library.


  • all—Enables the generation of debug messages for all IPv6 prefix library events.

  • error—Enables the generation of debug messages for minor errors related to the IPv6 prefix library.

  • general—Enables the generation of debug messages for general IPv6 prefix library events.

exec

debug ipv6 prefix-list


Example:


[local]BRAS>debug ipv6 prefix-list

Enables the generation of debug messages for the maintenance of IP Version 6 (IPv6) prefix lists and for the comparison of IPv6 prefix entries to IPv6 prefix lists.

exec

ipv6 host hostname ipv6-addr


[no | default] ipv6 host hostname ipv6-addr


Example:


[local]BRAS(config-ctx)#ipv6 host hamachi 2007::1

Displays information about all IPv6 hosts stored in the local host table for the current context.


  • hostname—Specifies the name of a host whose information you want to display.

  • ipv6-addr—Specifies the IPv6 address of the host whose information you want to display.

context
configuration

show ipv6 all-host


Example


[local]BRAS>show ipv6 all-host

Displays information about all IPv6 hosts stored in the local host table for the current context.

all modes

show ipv6 dynamic-host


Example


[local]BRAS>show ipv6 dynamic-host

Displays IPv6 dynamic hostname and system ID mapping.

all modes

show ipv6 mroute [first-ipv6-address second-ipv6-address] [count | detail]


Example


[local]BRAS>show ipv6 mroute

Displays the IPv6 Protocol Independent Multicast (PIM) routing table.


  • first-ipv6-address—Specifies an IPv6 address in format A:B:C:D:E:F:G:H.

  • second-ipv6-address—Specifies a second IPv6 address in format A:B:C:D:E:F:G:H.

  • count—Displays IPv6 multicast counters.

  • detail—Displays detailed information for the specified IPv6 routes or for all IPv6 routes configured on the system.

all modes

2.2.4   IPv6 Route Redistribution

The SmartEdge OS now supports the redistribution of learned IPv6 routes into:

To support the redistribution of subscriber routes, the redistribute command has been updated in the following command modes:

The redistribute command includes the following new construct:

subscriber {address | dhcp-pd | nd | static}

Use one of the one of the following optional keywords to redistribute the specified type of subscriber routes into routing instance:

Use the new set ipv6 aggregate prefix-list-name command in route map configuration mode to summarize routes selected for redistribution if those routes match IPv6 prefixes specified in the IPv6 prefix list (instead of redistributing all the routes that match the prefix list). The command syntax is:

set ipv6 aggregate prefix-list-name

Replace the prefix-list-name argument with the name of an IPv6 prefix list to use for summarizing redistributed routes.

2.2.5   RSTP Phase 2

RSTP Phase 2 adds three new features to the SmartEdge OS implementation of Rapid Spanning-Tree Protocol (RSTP):

RSTP Phase 2 has no known impact on the functioning of other SmartEdge router features, nor does it cause any changes to the default behavior of the router.

2.2.5.1   Restrictions and Requirements

RSTP Phase 2 has the following restrictions and requirements.

Example 1   Binding to an Economical Access Link Group

link-group lg-eco access economical
 encapsulation dot1q
 bind interface client_bridge local        //binding to eco. LG not allowed at this level
 dot1q pvc 100
  bind interface client_bridge local       //binding to eco. LG allowed at this and Q-in-Q level

2.2.5.2   CLI Changes

2.2.5.3   RSTP over VPLS Pseudowires

When the RSTP is configured over VPLS pseudowires, a VPLS bridge can participate in a meshed RSTP network of bridges. This provides path redundancy and prevents bridging loops.

2.2.5.4   RSTP Tracking

In RSTP tracking, a bridge running RSTP is designated the tracking master, while one or more other bridges are designated as tracking clients. On any port in which the tracking master and clients have bridging interfaces, the blocking, forwarding, and tracking actions of the master are followed by the same actions of the clients' interfaces on the same port. This feature allows RSTP to control ports where both RSTP and non-RSTP bridges have interfaces.

Among the applications for this RSTP tracking provides essential functionality in a customer-edge (CE) dual-homed redundant topology, in a meshed bridge network providing multiple access circuits to a client, and in a meshed bridged network for interoperability with Cisco switches.

2.2.6   CLIPS Username Format

This feature has two parts:

2.2.6.1   CLI Changes

2.2.7   WAN-PHY

SmartEdge routers now support WAN-PHY on the 10ge-1-port (10 Gigabit Ethernet Aggregation card (1-port))

WAN-PHY is described in WAN Interface Sublayer (WIS), IEEE 802.3ae.

2.2.7.1   Requirements and Restrictions

2.2.7.2   CLI Changes

2.2.8   Ethernet CFM Phase 3

Ethernet CFM Phase 3 provides additional encapsulation support for MEPs:

2.2.8.1   Requirements and Restrictions

The following restrictions apply to MEPs on subscriber circuits:

2.2.9   NTP Server

With this release, you can configure the SmartEdge router as an NTP server. NTP servers and peers are now configured per context; previous configurations are converted automatically. Use administrative ACLs to secure NTP administration.

The following commands are new with this feature:

The previous NTP commands, ntp mode, ntp peer, and ntp server have been removed from the CLI.

For more information about this feature, see Reference [8] .

2.2.10   ISP Logging

The In-Service Performance (ISP) log collects information about predefined system events that can have a potential impact on applications and enable support representatives to perform root-cause analysis and troubleshooting on the SmartEdge router.

You can view the ISP log in the CLI or extract the ISP log from the system. The ISP log is persistent across switchovers and reboots.

When the ISP log file reaches the size limit you set with the isp-log size command, the system stops writing ISP log entries in the file, logs an ISP entry in the ISP file stating that the file is full, and displays an error message.

If you disable the ISP log or change the size limit, the system removes any existing ISP log file. To save an existing ISP log file before disabling ISP logging, use the copy command to extract the file from the system.

You can use the information in the ISP log to manually compute system downtime and other statistics or, in the event of an issue, you can send the extracted file to your support representative for analysis.

It tracks the following information:

The following new commands were added to configure and view the ISP log file:

2.2.11   Network Management Features

2.2.11.1   CLEI Code Information Available In ENTITY-MIB

The SmartEdge router now includes Common Language Equipment Identification (CLEI) code information in ENTITY-MIB. CLEI codes are 10-digit alphanumeric codes that identify network equipment.

For example, the output from a walkthrough of your SNMP management tool may look like this:

user@snmp_router getmany -v2c Router Administrator entityMIB
entPhysicalDescr.1 = SE800e Chassis CLEI code:SOM6T10NRA
entPhysicalDescr.2 = SE800e Backplane SN:B2014100400106 
Rev:01 ID:5a Ver:4 Mfg.Dt:28-JAN-2005 MAC Address 
0:30:88:1:45:8D CLEI code:SPLENDACHS
entPhysicalDescr.3 = SE800e Fan Tray SN:9W024100400130 Rev:02
ID:5a Ver:4 Mfg.Dt:28-JAN-2005 CLEI code:SNPQCUHXAA
entPhysicalDescr.4 = SE800e Data Slot
entPhysicalDescr.5 = SE800e Data Slot
entPhysicalDescr.6 = SE800e Data Slot
entPhysicalDescr.7 = SE800e Data Slot
entPhysicalDescr.8 = SE800e Data Slot
entPhysicalDescr.9 = SE800e Data Slot
entPhysicalDescr.10 = SE800e Data Slot
entPhysicalDescr.11 = SE800e Data Slot
entPhysicalDescr.12 = SE800e Data Slot
entPhysicalDescr.13 = SE800e Data Slot
entPhysicalDescr.14 = SE800e Data Slot
entPhysicalDescr.15 = SE800e Data Slot
entPhysicalDescr.16 = SE800e Data Slot
entPhysicalDescr.17 = SE800e Data Slot
entPhysicalDescr.18 = Ge4-20-port Card SN:F10R5230800061
Rev:00R ID:5a Ver:4 Mfg.Dt:13-JUN-2008 Entitle All Ports 
All CLEI code:SOUIA6PUAA
entPhysicalDescr.19 = Ethernet Port 2/1
entPhysicalDescr.20 = Ethernet Port 2/2

2.2.11.2   SNMP Support for MPLS-L3VPN-STD-MIB

SNMP for the SmartEdge router now supports MPLS-L3VPN-STD-MIB based on RFC 4382, MPLS/BGP Layer 3 Virtual Private Network (VPN) Management Information Base and enterprise MIB RBN-MPLS-L3VPN-STD-EXT-MIB.

Support for the following notifications is included with MPLS-L3VPN-STD-MIB:

The traps command was updated to include the new mplsl3vpn keyword to enable event notifications described in MPLS-L3VPN-STD-MIB.

2.2.11.3   SNMP Support for Ether-WIS-MIB

SNMP for the SmartEdge router now supports Ether-WIS-MIB based on RFC 3637Definitions of Managed Objects for the Ethernet WAN Interface Sublayer and if-INVERTED-STACK-MIB based on RFC 2864,The Inverted Stack Table Extension to the Interfaces Group MIB .

The debug snmp mib command was updated to include the new etherwis keyword to enable debugging messages for Ether-WIS-MIB.

2.2.12   Advanced Services Features

This section describes the Layer-4 to Layer 7 (L4L7) features in this release.

2.2.12.1   Direction Support for Rate Limiting

You can configure DPI QoS profiles and then reference them in DPI action class to rate-limit incoming (ingress) traffic, outgoing (egress) traffic, or both incoming and outgoing (bidirectional) traffic.

When you configure a DPI QoS policy and reference it in a DPI action class, to rate limit:

For DPI QoS policies, the mark priority command enables you to configure all packets to be marked with a priority group, the conform mark priority command enables you to configure packets that conform to the configured QoS rate to be marked with a priority group, and the exceed mark priority command enables you to configure packets that exceed the configured QoS rate and burst tolerance to be marked with a priority group. Optionally, for either command, a drop precedence setting can also be configured. A priority group determines the egress queue that inbound packets are placed.

The output of the show dpi asp traffic-management action policy labels QoS profiles as Bidirectional (if traffic is rate-limited in both directions), Policing (if ingress traffic is rate-limited) or Metering (if egress traffic is rate-limited), as appropriate.

2.2.12.1.1   Application Traffic Management CLI Changes

The following new commands support directional rate limiting:

The following commands are enhanced to support directional rate limiting:

2.2.12.2   Session Limit Support for P2P traffic

In this release, you can configure a single global value for the maximum number of sessions allowed per subscriber. When you configure this value, you can specify whether packets associated with sessions that exceed the value are dropped, or mapped to an action policy class.

2.2.12.2.1   Application Traffic Management CLI Changes

The new dpi traffic-management maximum sessions command supports limiting subscriber sessions.

The following commands are enhanced to support subscriber session limits:

2.2.13   Enhancements to the boot ROM between version 2.0.2.42 and 2.0.2.45

The following changes were made to the boot ROM between versions 2.0.2.42 and 2.0.2.45:

3   New Hardware

3.1   New Hardware in Release 6.3.1.2

This release introduces the following new card.

3.1.1   PPA2-Based 10-Port Gigabit Ethernet DDR Card

The 10-port Gigabit Ethernet DDR-based card is designed for traffic management by using the second generation of the PPAs. The product order number for this card is ROA1283411/1.

This 10-port GE DDR card can be installed in the SmartEdge 400, SmartEdge 600, SmartEdge 800, SmartEdge 1200, and SmartEdge 1200H routers. It supports a minimum of 1 GB of memory capacity and can process data internally to match the speed of the ports. It also has increased circuit density of 32K, of which a minimum of 24K with eight CoS queues.

Each port on this card requires separate SFP transceiver. The following types of SFP optical transceivers are supported on any of the ports:

Table 8    Slot Allocation for the 10-Port Gigabit Ethernet DDR Line Card

Chassis

Slots

SmartEdge 400

1 to 4

SmartEdge 600

1 to 6

SmartEdge 800

1 to 6 or 9 to 14

SmartEdge 1200

1 to 6 or 9 to 14

SmartEdge 1200H

1 to 6 or 9 to 14

SM 240

1 to 6

SM 480

1 to 6 or 9 to 14

For information about installing this 10-port GE DDR card, see Reference [11].

The following enhanced commands support this card:

Available in global configuration mode.

Specifies a line card for a slot, or selects one for modification, and enters line card configuration mode, where card-type is ge2-10-port or ge2-10-port-sm, specifying a 10-port Gigabit Ethernet DDR line card. Use this command to configure a line card and its associated ports, channels, and circuits before the line card is actually installed in the chassis of a SmartEdge or a SM Family router.

Available in all modes. Displays general port and slot information for a 10-port Gigabit Ethernet DDR line card.

Available in all modes. Displays information about system hardware.


3.2   New Hardware in Release 6.3.1.1

The following hardware is new in Release 6.3.1.1.

3.2.1   SmartEdge 1200HRouter

The SmartEdge 1200H router is a carrier-class product with an architecture that supports packetized traffic. It has a higher power rating than the SmartEdge 1200 router, allowing it to support a greater number of PPA3-based line cards. It can be used as an edge aggregation router and simultaneously as a broadband remote access server (BRAS) to directly connect customers to the network. The SmartEdge 1200H router enables service providers to offer full-service broadband applications, such as routing protocols, quality of service (QoS), and inbound and outbound access control lists (ACLs).

Because of the optimized packet-forwarding capabilities and support of high-bandwidth uplink interfaces, the SmartEdge 1200H router can also be used in the metropolitan core to aggregate traffic from other routers into the long-haul transit core.

3.2.2   New and Modified Cards

This release introduces the following modified cards.

3.2.2.1   SmartEdge Storage Engine

Release 6.3.1 of the SmartEdge OS supports a modified version of the SmartEdge Storage Engine (SSE) card with hard disk drives (HDDs) that have increased storage capacity of 300 GB.

3.2.2.2   End of Life and Unsupported Hardware Components

The SmartEdge 1200H does not support the XCRP3 Controller card in release 6.3.1.

3.2.2.3   PPA2-Based 8-Port POS OC-3c/STM-1c and 4-Port POS OC-12c/STM-4c Line Card

Release 6.3.1.1 of the SmartEdge OS supports two new PPA2-based POS line cards: 8-port POS OC-3c/STM-1c and 4-port POS OC-12c/STM-4c.

The 8-port POS OC-3c/STM-1c card functions as a subscriber-facing module and as well as a network uplink module. The product order number for this POS OC-3c/STM-1c line card is OIM-SE8-8OC3 or ROA1283250/1.

The 4-port POS OC-12c/STM-4c card functions as a network uplink module in edge routing and BRAS applications. The product order number for this POS OC-12c/STM-4c line card is OIM-SE8-4OC12 or ROA1283249/1.

These POS line cards can be installed in a SmartEdge 400, SmartEdge 600, SmartEdge 800, SmartEdge 1200, or SmartEdge 1200H router. They have the minimum memory capacity of 1 Gigabit and are fully compatible with all cards supported on these SmartEdge systems, including other line cards and controller cards. These cards are considered separate and distinguishable I/O cards for the SmartEdge system.

Both POS OC-3c/STM-1c and POS OC-12c/STM-4c cards support the Point-to-Point Protocol (PPP), High-level Data Link Control (HDLC), Frame Relay (FR) encapsulations, Modified Deficit Round Robin (MDRR), and POS Link Aggregation Group (LAG) features. Automatic Protection Switching (APS) is not supported on these line cards.

The POS cards are the same size as all other SmartEdge line cards and are designed to occupy a single slot in the chassis. Each port on these POS cards requires separate SFP transceiver. These SFPs support Short Reach and Intermediate Reach, with different wavelength ranges.


Table 9    Slot Allocations for the 8-Port POS OC-3c/STM-1c or 4-Port POS OC-12c/STM-4c Line Cards

Chassis

Slots

SmartEdge 400

1 to 4

SmartEdge 600

1 to 6

SmartEdge 800

1 to 6 or 9 to 14

SmartEdge 1200

1 to 6 or 9 to 14

SmartEdge 1200H

1 to 6 or 9 to 14

For information about installing either of these two POS line cards, see Quick Installation Guide for SmartEdge Packet over SONET/SDH line Cards. The following enhanced commands support this card:

Available in global configuration mode.

Specifies a line card for a slot, or selects one for modification, and enters line card configuration mode, where card-type is oc3e-8-port, specifying a 8-port POS OC-3c/STM-1c line card; and oc12e-4-port, specifying a 4-port POS OC-12c/STM-4c. Use this command to configure a line card and its associated ports, channels, and circuits before the line card is actually installed in the chassis of a SmartEdge router.

Available in all modes. Displays general port and slot information for a POS OC-3c/STM-1c or POS OC-12c/STM-4c line card.

Available in all modes. Displays information about system hardware.

4   PPA Feature Support

Table 10 describes the feature support on PPA versions 1, 2, and 3 in Release 6.3.1 of the SmartEdge OS. This matrix applies to the SmartEdge router only.

Note:  
For information about which traffic cards support each PPA version, see the router hardware guides.

Table 10    PPA Feature Support for Release 6.3.1

Feature

PPA1

PPA2

PPA3

Notes

Support for IPv6 Subscriber Services

No

Yes

Yes

Supported on the following PPA2-based traffic cards only:


  • PPA2-based 10-port Gigabit Ethernet

  • 2-port 60 Fast Ethernet–Gigabit Ethernet

  • 1-port 10 Gigabit Ethernet


Supported on the following PPA3-based traffic cards only:


  • PPA3-based 10-port Gigabit Ethernet

  • PPA3-based 20-port Gigabit Ethernet

IPv6 Route Redistribution

No

Yes

Yes

Supported on the following PPA2-based traffic cards only:


  • PPA2-based 10-port Gigabit Ethernet

  • 2-port 60 Fast Ethernet–Gigabit Ethernet

  • 1-port 10 Gigabit Ethernet


Supported on the following PPA3-based traffic cards only:


  • PPA3-based 10-port Gigabit Ethernet

  • PPA3-based 20-port Gigabit Ethernet

RSTP Phase 2

No

Yes

Yes

 

CLIPS Username Format

Yes

Yes

Yes

 

WAN-PHY

No

Yes

No

10ge-1-port only

Ethernet CFM Phase 3

Yes

Yes

No

 

5   APS Traffic Card and Feature Compatibility

This section describes the traffic cards and features supported by Automatic Protection Switching (APS) port for SmartEdge routers.

5.1   POS APS Ports

Table 11 lists the traffic cards that support POS APS ports.

Table 11    Traffic Cards That Support POS APS

Traffic Cards Supported

Notes

OC-3c/STM-1c


OC-12c/STM-4c


OC-48c/STM-16c

Working and protection ports must be on the same type of card.


Working and protection ports must have identical configuration.

Note:  
POS APS is not supported on the 4-port POS OC-48c/STM-16c card.

Table 12 summarizes encapsulation and feature compatibility for POS APS ports.

Table 12    POS APS Feature Compatibility

Feature

Supported

Notes

Encapsulation

   

Cisco HDLC

Yes

Required

PPP

Yes

 

Static CLIPS

No

 

Dynamic CLIPS

No

 

Routing RIP

Yes

 

OSPF

Yes

 

ISIS

Yes

 

PIM

Yes

 

BGP

Yes

 

IP Services

Yes

 

IP Service Policies

   

NAT

Yes

 

Forward policy

Yes

 

Service policy

Yes

 

IP Security

   

AAA

Yes

 

RADIUS

Yes

 

TACACS+

Yes

 

Circuit Types

   

On-demand

No

 

On-demand via AAA

No

 

Explicit ranges

No

 

Tunnels GRE

Yes

 

L2TP LNS

Yes

 

L2TP LAC

Yes

 

QoS Policing/metering

Yes

 

PWFQ (queuing)

No

 

Flow Admission Control

No

PPA2 cards only

Management

   

NetOp EMS

Yes

Configuration and monitoring of Frame Relay circuits is supported

SNMP

Yes

 

APS

   

RDI-P

Yes

Required

REI-P

Yes

Required

1+1

Yes

 

1:1

No

 

1:N

No

 

Bidirectional switching

Yes

 

Unidirectional switching

No

 

Revertive switching

Yes

 

Nonrevertive switching

Yes

Default

Use of protection line for extra traffic

Yes

Can be enabled or disabled

MPLS Services

   

Cross-connect

No

 

Bridging (VPLS)

No

 

L2VPNs

Yes

Frame Relay DLCI; no Ethernet resiliency

MPLS

Yes

 

Scalability

   

Maximum PVCs per group

16,000

 

Maximum protected PVCs per system

48,000

 

Maximum APS groups per system

8

 

Switchover time

<2.5 seconds

 

Glossary

APS
Automatic Protection Switching
 
ASE
Advanced Services Engine
 
ASP
Application Services Processor
 
BRAS
Broadband remote access server
 
CAC
Connection admission control
 
DDR
Double Data Rate. Data accepted by receiver at rising and falling edge.
 
DPI
Deep Packet Inspection
 
DSCP
Differentiated Services Code Point
 
ECR
Edge collector router
 
ERDI-P
Path Enhanced Remote Defect Indication
 
FR
Frame Relay
 
HDD
Hard Disk Drive
 
HDLC
High-level Data Link Control
 
IMS
IP multimedia subsystem
 
LAG
Link Aggregation Group
 
LCD-P
Path Loss of Code-Group Delineation
 
MBS
Maximum burst size
 
MDRR
Modified Deficit Round Robin
 
PDR
Peak data rate
 
PLM-P
Path Payload Label Mismatch
 
PPP
Point-to-Point Protocol
 
PWFQ
Priority Weighted Fair Queuing
 
RDI-P
Path remote defect indication
 
RTCP
RTP Control Protocol
 
SBG
Session Border Gateway
 
SDR
Sustained data rate
 
SGC
Session Gateway Controller
 
SPDF
Service policy decision function
 
SSE
SmartEdge Storage Engine
 
VPN
Virtual Private Network

Reference List

SmartEdge OS
[1] Configuring Bridging.
[2] Configuring CLIPS.
[3] Configuring Ethernet CFM.
[4] Configuring ATM, Ethernet, and POS Ports.
[5] Installing Release 6.3.1.1.
[6] Installing Release 6.3.1.2.
[7] Configuring ACLs.
[8] Configuring NTP.
[9] Configuring IPv6 Subscriber Services.
[10] Changes to Default System Behavior, SmartEdge OS for SmartEdge Routers.
[11] Quick Installation Guide for SmartEdge Fast Ethernet and Gigabit Ethernet Line Cards.
Other CPI
[12] SmartEdge Border Gateway Function.
Standards and Recommendations
[13] WAN Interface Sublayer, IEEE 802.3ae.
[14] Link Aggregation, IEEE 802.3ad.
[15] ETHERLIKE-MIB, RFC 2665.
[16] ETHER-WIS-MIB, RFC 3637.
[17] IF-INVERTED-STACK-MIB, RFC 2864.