![]() |
COMMAND DESCRIPTION 12/190 82-CRA 119 1170/1-V1 Uen A | ![]() |
Copyright
© Copyright Ericsson AB 2009. All rights reserved.
Disclaimer
No part of this document may be reproduced in any form without the written permission of the copyright owner. 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. |
1 | Command Descriptions |
1.1 | mp endpoint-discriminator |
1.2 | mpls |
1.3 | mpls shortcuts |
1.4 | mpls to qos |
1.5 | mpls traffic-engineering |
1.6 | mpls use-ethernet |
1.7 | mpls use-ip |
1.8 | mp mrru |
1.9 | mrinfo |
1.10 | mrouter |
1.11 | mtrace |
1.12 | mtu (ATM, Ethernet, POS) |
1.13 | mtu (card) |
1.14 | mtu (channel) |
1.15 | mtu (tunnel) |
1.16 | multicast destination |
1.17 | multicast output |
1.18 | multicast rate-limit |
1.19 | multi-paths |
1.20 | multi-topology transition |
1.21 | national |
1.22 | native-vlan-tag |
1.23 | nat policy |
1.24 | nat policy-name |
1.25 | nbns |
1.26 | neighbor |
1.27 | neighbor (BFD) |
1.28 | neighbor (BGP) |
1.29 | neighbor (OSPF) |
1.30 | neighbor password |
1.31 | neighbor profile |
1.32 | neighbor targeted |
1.33 | neighbor (VPLS) |
1.34 | net |
1.35 | netop |
1.36 | network |
1.37 | network-type |
1.38 | next-hop |
1.39 | next-hop-on-lsp |
1.40 | next-hop-self |
1.41 | nexthop triggered |
1.42 | nexthop triggered delay |
1.43 | nexthop triggered holdtime |
1.44 | no debug all |
1.45 | notify |
1.46 | ns-retry-interval |
1.47 | nssa-range |
1.48 | ntp mode |
1.49 | ntp peer |
1.50 | ntp server |
1.51 | num-queues |
Commands starting with “mp” through commands starting the “n” are included.
mp endpoint-discriminator {hostname | ip | user-defined text}
{no | default} mp endpoint-discriminator
Specifies the type of endpoint discriminator to be used for negotiation for a Multilink Point-to-Point Protocol (MP) bundle.
hostname |
Specifies the system hostname of the SmartEdge router. |
ip |
Specifies the IP address assigned to the interface to which you bind the MP bundle. |
user-defined text |
User-defined endpoint discriminator. The text argument is a string of up to 20 characters. |
The endpoint discriminator is the system hostname.
Use the mp endpoint-discriminator command to specify the endpoint discriminator to be used for negotiation for an MP bundle. The endpoint discriminator identifies peers to the system and distinguishes peers from one another in the system. This identification ensures that the correct links are bundled together in the same MP bundle.
Use the no or default form of this command to return the endpoint discriminator identification to the system hostname.
The following example shows how to specify the endpoint discriminator as the IP address of the interface to which the MP bundle will be bound:
[local]Redback(config)#link-group lg-multi mp [local]Redback(config-link-group)#mp endpoint-discriminator ip [local]Redback(config-link-group)#exit
mpls {encrypted 1 | password} password
no mpls
Enables Multiprotocol Label Switching (MPLS) features and functions.
encrypted 1 |
Specifies that the password that follows is encrypted. |
password |
Specifies that the password that follows is not encrypted. |
password |
Paid license password that is required to enable MPLS features and functions. The password argument is unique for MPLS and is provided at the time the software license is paid. Optional only when using the no form. |
MPLS features and functions are disabled.
Use the mpls command to enable MPLS features and functions. You can specify the password argument in either encrypted or unencrypted form. Neither form displays by the show configuration command command (in any mode). For more information on the show configuration command, see Using the CLI.
Use the no form of this command to disable MPLS features and functions. A password is not required if you are disabling the license for MPLS features and functions; it is ignored if entered.
The following example licenses MPLS. The password is in an unencrypted form:
[local]Redback(config-license)#mpls password mpls-password
mpls shortcuts
Enables the use of Multiprotocol Label Switching (MPLS) label-switched paths (LSPs) as intra-area next hops.
OSPF router configuration
This command has no keywords or arguments.
The use of MPLS LSPs is disabled.
Use the mpls shortcuts command to enable the use of MPLS LSPs as intra-area next hops.
The following example enables the use of MPLS LSPs as intra-area next hops:
[local]Redback(config-ctx)#router ospf [local]Redback(config-ospf)#mpls shortcuts
mpls {exp-value | all} to qos pd-value
default mpls {exp-value | all}
Translates Multiprotocol Label Switching (MPLS) experimental (EXP) values to packet descriptor (PD) quality of service (QoS) values on ingress.
class map configuration
exp-value |
An integer from 0 (lowest priority) to 7 (highest priority) representing the contents of the three EXP bits in the MPLS label header. |
all |
Maps all valid values for the source value to the specified target value. Any existing configuration for the classification map is overridden. |
pd-value |
An integer from 0 to 63 (six bits), with the packet priority encoded in three higher-order bits and the packet drop precedence in the three lower-order bits. You can enter the value in decimal or hexadecimal format, for example 16 or 0x10. You can also enter a standard Differentiated Services Code Point (DSCP) marking label. The scale used by this command for packet priority, from 0 (lowest priority) to 7 (highest priority), is the relative inverse of the scale used by the mark priority command. For details on this command, see Configuring Rate-Limiting and Class-Limiting. |
None
Use the mpls to qos command to define ingress mappings from MPLS EXP values to PD QoS values.
If you specify the all keyword, all valid MPLS EXP values are mapped to the specified PD value. Any existing configuration for the classification map is overridden. You can use the all keyword to specify a single default value for all the mapping entries, then override that value for a subset of entries by entering subsequent mapping commands without this keyword.
Use the default form of this command to revert map entries to either the default 8P0D or mapping schema values, if a mapping schema has been specified.
The following example defines the classification map exp-to-pd to determine initial MPLS values on ingress, defines the default mapping schema using 7P1D values, then maps MPLS EXP value 1 to the PD value 0x24:
[local]Redback(config)#qos class-map exp-to-pd mpls in [local]Redback(config-class-map)#mapping-schema 7P1D [local]Redback(config-class-map)#mpls 1 to qos 0x24
mpls traffic-engineering
Enables Open Shortest Path First (OSPF) advertisement of traffic engineering metrics.
OSPF router configuration
This command has no keywords or arguments.
The use of Multiprotocol Label Switching (MPLS) traffic engineering is disabled.
Use the mpls traffic engineering command to cause OSPF to advertise traffic engineering metrics for OSPF interfaces.
The following example enables the use of MPLS traffic engineering:
[local]Redback(config-ctx)#router ospf [local]Redback(config-ospf)#mpls traffic-engineering
mpls {exp-value | all} use-ethernet [class-map map-name]
{no | default} mpls {exp-value | all}
Determines initial packet descriptor (PD) values by mapping Ethernet 802.1p values rather than directly mapping from Multiprotocol Label Switching (MPLS) experimental (EXP) values for received MPLS packets with the specified EXP value.
class map configuration
exp-value |
An integer from 0 (lowest priority) to 7 (highest priority) representing the contents of the three EXP bits in the MPLS label header. |
all |
Maps all valid values for the source value to the specified target value. Any existing configuration for the classification map is overridden. |
use-ethernet |
Enables a secondary mapping lookup using the packet’s 802.1p bits as input. If no classification map is specified for the secondary lookup, the default 8P0D 802.1p-to-PD mapping is used. |
class-map map-name |
Optional. Name of the secondary classification map. |
Ingress MPLS classification map entries use the 8P0D EXP-to-PD mapping, where the EXP value is copied to the PD priority field. The PD drop-precedence field is set to zero.
Use the mpls use-ethernet command to determine initial PD values by mapping Ethernet 802.1p values rather than directly mapping from MPLS EXP values for received MPLS packets with the specified EXP value. If a received packet with the specified EXP value does not include an Ethernet header, the SmartEdge router uses the default mapping instead of the specified mapping.
If you specify the all keyword, all valid MPLS EXP values are configured to use the 802.1p-to-PD mapping. Any existing configuration for the classification map is overridden. You can use the all keyword to specify a single default value for all the mapping entries, then override that value for a subset of entries by entering subsequent mapping commands without this keyword.
If you specify the optional class-map map-name construct, the resulting mapping uses the specified 802.1p-to-PD classification map. The secondary classification map must have a value of ethernet for the marking-type argument and a value of in for the mapping direction. If you do not specify a secondary classification map, the default mapping is used.
Use the no or default form of this command to revert one or all map entries to either the default 8P0D or mapping schema values, if a mapping schema has been specified.
mpls {exp-value | all} use-ip [class-map map-name]
default mpls {exp-value | all}
Determines packet descriptor (PD) values by mapping Differentiated Services Code Point (DSCP) values rather than Multiprotocol Label Switching (MPLS) experimental (EXP) values on ingress for IP packets.
class map configuration
exp-value |
An integer from 0 (lowest priority) to 7 (highest priority) representing the contents of the three EXP bits in the MPLS label header. |
all |
Maps all valid values for the source value to the specified target value. Any existing configuration for the classification map is overridden. |
class-map map-name |
Optional. Name of the secondary classification map. |
None
Use the mpls use-ip command to determine PD values by mapping DSCP values rather than MPLS EXP values on ingress for IP packets.
If you specify the all keyword, all valid EXP values are configured to use the DSCP-to-PD mapping. Any existing configuration for the classification map is overridden. You can use the all keyword to specify a single default value for all the mapping entries, then override that value for a subset of entries by entering subsequent mapping commands without this keyword.
If you specify the optional class-map map-name construct, the resulting mapping uses the specified DSCP-to-PD classification map. The secondary classification map must have a value of ip for the marking-type argument, and a value of in for the mapping direction. If you do not specify a secondary classification map, the default mapping is used.
Use the default form of this command to revert values for one or all map entries to either the default 8P0D or mapping schema values, if a mapping schema has been specified.
The following example defines the classification map dscp-to-pd to determine initial quality of service (QoS) PD values on ingress, and specifies 7P1D encoding as a default mapping schema. It then overrides the default 7P1D values for EXP value 1 with PD value 0x24, and specifies the IP header DSCP value to determine the initial QoS PD value for packets received with EXP value 3. The secondary classification map exp-to-dscp is used for translation:
[local]Redback(config)#qos class-map dscp-to-pd mpls in [local]Redback(config-class-map)#mapping-schema 7P1D [local]Redback(config-class-map)#mpls 1 to qos 0x24 [local]Redback(config-class-map)#mpls 3 use-ip exp-to-dscp
mp mrru value
{no | default} mp mrru
Sets the size of the maximum received reconstructed unit (MRRU) to be used to negotiate a Multilink Point-to-Point Protocol (MP) bundle.
value |
Optional. The MRRU size for the MP bundle. The range of values is 256 to 128000. |
If no MRRU is specified, 1524 is maximum size that can be negotiated.
Use the mp mrru command to set the MRRU to be used to negotiate an MP bundle. The SmartEdge router uses this value when calculating the maximum receive unit (MRU) or MRRU value to send in the Link Control Protocol (LCP) Configure Request to the peer.
MRRU configuration is supported on channelized E1 cards, channelized OC-3 and OC-12 cards, and clear-channel E3 cards. MRRU configuration is supported for static MP links only; it is not supported for subscriber links.
Use the no or default form of this command to return the MRRU to the default value.
The following example shows how to specify the endpoint discriminator as the IP address of the interface to which the MP bundle is bound:
[local]Redback(config)#link-group lg-multi mp [local]Redback(config-link-group)#mp mrru 4470 [local]Redback(config-link-group)#exit
mrinfo target-mrouter-addr
Queries a neighboring multicast router to determine which routers are peers of the local router.
exec
target-mrouter-addr |
IP address of the target neighboring multicast router. |
None
Use the mrinfo command to query a neighboring multicast router to determine which routers are peers of the local router. This command sends a query to a target multicast router and displays the response containing information about the target’s neighboring routers.
The following example queries a target multicast router, 10.3.1.3, and displays information about the target’s neighboring routers:
[local]Redback>mrinfo 10.3.1.3
10.3.1.3 (10.3.1.3) [version 21.3,mtrace]: 10.4.1.3 -> 10.4.1.2 (10.4.1.2) [1/0/pim/querier] 10.5.1.3 -> 10.5.1.4 (10.5.1.4) [1/0/pim]
mrouter [static]
no mrouter
Configures the multicast router discovery setting for circuits attached to the specified IGMP snooping profile.
static |
Configures all circuits attached to the specified IGMP snooping profile to be static multicast router circuits. |
IGMP router monitoring is enabled on every circuit.
Use the mrouter command to configure the multicast router discovery setting for all circuits attached to a specified IGMP snooping profile. All circuits attached to the IGMP snooping profile assume the multicast routing setting specified in the profile.
Use the no form of this command to disable the multicast router discovery setting on all circuits attached to the specified IGMP snooping profile.
If you do not include the optional static keyword with the mrouter command, IGMP packets are monitored on the circuits. If IGMP queries are received by an associated circuit, that circuit is declared to be a multicast routing circuit.
By default, every circuit is enabled for monitoring of IGMP packets. This behavior can be overwritten by configuring a bridge profile with the mrouter setting disabled or set to static.
The following example shows how to enable IGMP router monitoring on every circuit attached to an IGMP snooping profile called p1:
[local]router#configure [local]router(config)#igmp snooping profile p1 [local]router(config-igmp-snooping-profile)#mrouter
The following example shows how to configure all circuits attached to an IGMP snooping profile called sanjose1 to be static multicast router circuits:
[local]router#configure [local]router(config)#igmp snooping profile sanjose1 [local]router(config-igmp-snooping-profile)#mrouter static
The following example shows how to disable multicast router discovery on all circuits attached to an IGMP snooping profile called milpitas1:
[local]router#configure [local]router(config)#igmp snooping profile milpitas1 [local]router(config-igmp-snooping-profile)#no mrouter
mtrace {src-addr | src-name} [gateway {gateway-addr | gateway-name}] [group {group-addr | group-name}] [hops hop-count] [interval trace-interval] [local_addr if-addr] [loop] [multicast] [no-router-alert] [numerical] [query query-count] [receiver {rec-addr | rec-name}] [response {host-addr | hostname}] [short_form] [ttl ttl] [unicast] [verbose] [wait wait-interval]
Traces the path from a source to a destination branch on a multicast distribution tree.
exec
src-addr |
IP address of the source to end the process of tracing the path. |
src-name |
Name of the source to end the process of tracing the path. |
gateway |
Optional. Specifies the last hop router of the multicast receiver. |
gateway-addr |
IP address of the last hop router of the multicast receiver. |
gateway-name |
Name of the last hop router of the multicast receiver. |
group |
Optional. Specifies the group for which the path tracing is performed. |
group-addr |
IP address of the group for which the path tracing performed. |
group-name |
Name of the group for which the path tracing is performed. |
hops hop-count |
Optional. Maximum number of hops that can be traced. |
interval trace-interval |
Optional. Interval, in seconds, between statistics gathering traces. |
local_addr if-addr |
Optional. IP address of the local interface used for sourcing the query. |
loop |
Optional. Loops indefinitely printing statistics. |
multicast |
Optional. Specifies that responses are always requested using multicast routing. |
no-router-alert |
Optional. Sends request without router alert IP option. |
numerical |
Optional. Specifies that hop addresses be printed in dotted decimal format only. |
query query-count |
Optional. Maximum number of query attempts. |
receiver |
Optional. Specifies a receiver to begin the process of tracing the path. |
rec-addr |
IP address of receiver to begin the process of tracing the path. |
rec-name |
Name of receiver to begin the process of tracing the path. |
response |
Optional. Specifies a host to receive the path tracing responses. |
host-addr |
IP address of the host to receive the path tracing responses. |
hostname |
Name of host to receive the path tracing responses. |
short_form |
Optional. Enables short form output, and no statistics are displayed. |
ttl ttl |
Optional. Time-to-live (TTL) value for multicast trace queries and responses. The range of values is 1 to 255; the default value is 5. |
unicast |
Optional. Specifies that responses are always requested using unicast routing. |
verbose |
Optional. Enables verbose mode. |
wait wait-interval |
Optional. Interval, in seconds, to wait for a trace response. |
None
Use the mtrace command to trace the path from a source to a destination branch on a multicast distribution tree. The trace query is passed hop by hop along the direction from the receiver to the source, collecting each hop’s IP address, packet counts, and routing error codes. At the end of this path, a response to returned to the response IP address.
If the command is issued without specifying any trace query parameters, it interactively prompts for the parameters.
The following example displays the short form results of tracing a path from the source IP address, 11.1.1.21, to the multicast receiver’s last hop router IP address, 10.4.1.2, using the Internet Group Management Protocol (IGMP) group with the IP address, 224.121.121.1:
[local]Redback>mtrace 11.1.1.21 group 224.121.121.1 gateway 10.4.1.2 short_form
Mtrace from 11.1.1.21 to 10.4.1.2 via group 224.121.121.1 Querying full reverse path... * switching to hop-by-hop: 0 ? (10.4.1.2) -1 ? (10.4.1.2) PIM threshold 0 Reached RP/Core -2 * * ? (10.2.1.1) PIM threshold 0 -3 ? (11.1.1.21) Round trip time 15 ms; total ttl of 1 required.
The following example displays detailed results of tracing a path from the source IP address, 11.1.1.21, to the multicast receiver’s last hop router IP address, 10.4.1.2, using the IGMP group with the IP address, 224.121.121.1:
[local]Redback>mtrace 11.1.1.21 group 224.121.121.1 gateway 10.4.1.2
Mtrace from 11.1.1.21 to 10.4.1.2 via group 224.121.121.1 Querying full reverse path... * switching to hop-by-hop: 0 ? (10.4.1.2) -1 ? (10.4.1.2) PIM threshold 0 Reached RP/Core -2 * * ? (10.2.1.1) PIM threshold 0 -3 ? (11.1.1.21) Round trip time 17 ms; total ttl of 1 required. Waiting to accumulate statistics...Results after 10 seconds: Source Response Dest Overall Packet Statistics For Traffic From 11.1.1.21 10.3.1.3 Packet 11.1.1.21 To 224.121.121.1 v __/ rtt 17 ms Rate Lost/Sent = Pct Rate 0.0.0.0 (null) v ^ ttl 2 ^ 0 pps 0/0 = -- 0 pps 11.1.1.1 10.2.1.1 ? v ^ ttl 2 0/0 = -- 0 pps 10.2.1.2 10.4.1.2 ? Reached RP/Core v \__ ttl 3 ?/0 0 pps? 10.4.1.2 10.3.1.3 Receiver Query Source
mtu size
default mtu
Specifies the maximum transmission unit (MTU) size of the payload without fragmentation for an Asynchronous Transfer Mode (ATM) OC port, an ATM DS-3 port, an Ethernet or Gigabit Ethernet port, or a Packet over SONET/SDH (POS) port.
size |
MTU payload size in bytes. The range of values and the default depend on the type of port; see Table 1. |
The default MTU payload size is dependent on the type of port; see Table 1.
Use the mtu command to specify the MTU size of the payload without fragmentation for an ATM, Ethernet, or Gigabit Ethernet, or POS port.
Table 1 lists the range of values and default for each type of port.
Port Type |
Range of Values (Bytes) |
Default (Bytes) |
---|---|---|
ATM OC or DS-3 |
256 to 12,800 |
4470 |
Ethernet |
1500 | |
Gigabit Ethernet |
256 to 9198 |
1500 |
POS |
256 to 12800 |
4470 |
(1) FE ports on an FE-GE traffic card support guaranteed lossless flow
control for MTUs up to 2000 bytes.
(2) FE ports on an FE-GE traffic card support guaranteed lossless flow
control for MTUs up to 9600 bytes if the ports are explicitly configured
for lossless flow control.
The Layer 2 headers are automatically added to the payload size and do not cause fragmentation; you do not include them when selecting the value of the size argument.
Use the default form of this command to specify the default MTU payload size.
The following example shows how to specify a MTU payload size of 1000 bytes for Ethernet port 1 in slot 4:
[local]Redback(config)#port ethernet 4/1 [local]Redback(config-port)#mtu 1000
In this example, the Layer 2 headers for an Ethernet port include an 18-byte Ethernet header, a 4-byte 802.1Q header, and up to four 4-byte multiprotocol label switching (MPLS) labels, for a total of 38 bytes. Thus, in this example, the actual maximum packet size without fragmentation is 1038 bytes.
mtu size
{no | default} mtu
Specifies the maximum transmission unit (MTU) size of the payload without fragmentation for all Fast Ethernet (FE) ports on the Fast Ethernet-Gigabit Ethernet (FE-GE) traffic card.
size |
MTU payload size in bytes. The range of values is 256 to 9600 bytes. The default value is 1500 bytes. |
The default MTU payload size is 1,500 bytes.
Use the mtu command to specify the MTU size of the payload without fragmentation for an all FE ports on the FE-GE traffic card.
The Layer 2 headers are automatically added to the payload size and do not cause fragmentation; you do not include them when selecting the value of the size argument.
You can override the MTU setting for individual FE ports by using this command in port configuration mode.
Use the no or default form of this command to specify the default MTU payload size.
The following example shows how to specify an MTU payload size of 9600 bytes for the FE ports on the FE-GE traffic card in slot 4:
[local]Redback(config)#card fege-60-2-port 4 [local]Redback(config-card)#mtu 9600
mtu size
default fault mtu
Specifies the maximum transmission unit (MTU) payload size of the packet without fragmentation for a clear-channel DS-3 channel or port, clear-channel E3 port, E1 channel or port, DS-1 channel on a channelized DS-3 channel or port, or DS-0 channel group on a channelized E1 channel or port.
size |
MTU payload size of the packet in bytes. The range of values is 256 to 12,800. The default depends on the type of channel or port; see Table 2. |
The default MTU payload size depends on the type of channel or port; for more information see Table 2.
Use the mtu command to specify the MTU payload size of the packet without fragmentation for a clear-channel DS-3 channel or port, E3 port, E1 channel or port, a DS-1 channel on a channelized DS-3 channel or port, or a DS-0 channel group on a channelized E1 channel or port.
Table 2 lists the range of values and default for each type of channel or port.
Channel or Port Type |
Range of Values (Bytes) |
Default (Bytes) |
---|---|---|
Clear-channel DS-3 |
256 to 12,800 |
4,470 |
Clear-channel E3 |
256 to 9,192 |
4,470 |
E1 |
256 to 12,800 |
1,500 |
DS-1 |
256 to 12,800 |
1,500 |
DS-0 channel group |
256 to 12,800 |
1,500 |
The Layer 2 headers are automatically added to the payload size and do not cause fragmentation; you do not include them when selecting the value of the size argument.
Use the default form of this command to specify the default value of the MTU payload size of the packet.
The following example shows how to specify the MTU payload size of the packet to be 2000 on clear-channel DS-3 port 1:
[local]Redback(config)#port ds3 3/1 [local]Redback(config-ds3)#mtu 2000
mtu bytes
no mtu
Sets the maximum transmission unit (MTU) size for packets sent in a tunnel.
tunnel configuration
bytes |
MTU size in bytes. The range of values is 256 to 16384. |
MTU for the interface to which the tunnel is bound.
Use the mtu command to set the MTU for packets sent in a tunnel. If an IP packet exceeds the MTU, the system fragments that packet.
A tunnel uses the MTU size for the interface to which you have bound it with the bind interface command (in tunnel configuration mode), unless you explicitly configure the MTU using this command. After you configure an MTU for the tunnel, the system determines the effective MTU by comparing the configured MTU with the interface MTU and selecting the lesser of the two values.
Use the no form of this command to delete the configured MTU and use the interface MTU.
The following example shows how to set the maximum IP packet size for the DenverTnl to 1024 bytes:
[local]Redback(config)#tunnel ipv6v4 DenverTnl [local]Redback(config-tunnel)#mtu 1024
multicast destination [if-name ctx-name [group-list acl-name]]
no multicast destination
Enables the forwarding of multicast data for Internet Group Management Protocol (IGMP) messages received on the Point-to-Point Protocol over Ethernet (PPPoE) subscriber circuits on an out-of-band (separated from the PPPoE circuit) IP over Ethernet (IPoE) interface.
IGMP service profile configuration
if-name |
Optional. Multicast-enabled interface name. |
ctx-name |
Optional. Context name in which the multicast-enabled interface resides. |
group-list acl-name |
Optional. Name of the access control list (ACL) used to filter IGMP control messages. |
Forwarding multicast data on an out-of-band IPoE interface is disabled.
Use the multicast destination command to enable the forwarding of multicast data for IGMP messages received on the PPPoE subscriber circuits on an out-of-band IPoE interface.
The IGMP service profile must be bound to a subscriber record through a configuration or a Remote Authentication Dial-In User Service (RADIUS) attribute.
Use the no form of this command to disable the forwarding of multicast data for IGMP messages received on the PPPoE subscriber circuits on an out-of-band IPoE interface.
The following example enables the to_dslam5 interface on the local context to forward multicast data, and configures the foo IGMP service profile to enable the forwarding of multicast data received on a PPPoE subscriber circuit on the to_dslam5 interface:
[local]Redback(config)#context local [local]Redback(config-ctx)#interface to_dslam5 [local]Redback(config-if)#multicast output [local]Redback(config-if)#exit [local]Redback(config-ctx)#igmp service-profile foo [local]Redback(config-igmp-service-profile)#multicast destination to_dslam5
multicast output [accept-unknown-mac]
{no | default} multicast output [accept-unknown-mac]
Enables an interface to forward multicast data, and to send and receive Internet Group Management Protocol (IGMP) control messages.
interface configuration
accept-unknown-mac |
Optional. Accepts IGMP control packets with unknown medium access control (MAC) addresses. |
No interface is enabled for multicast data.
Use the multicast output command to enable an interface to forward multicast data, and to send and receive IGMP control messages.
An IP over Ethernet (IPoE) circuit, on a Gigabit Ethernet port or an 802.1Q permanent virtual circuit (PVC) configured on it, must be configured on the interface to carry the multicast services. The MAC addresses received from IGMP control packets on the IPoE circuit are compared to the subscriber’s MAC address received on the corresponding Point-to-Point Protocol over Ethernet (PPPoE) circuit. By default, if the MAC addresses do not match, the IGMP control packet is dropped. Use the accept-unknown-mac keyword to accept IGMP control packets that have MAC addresses that do not match the subscriber’s MAC address.
Use the no form of this command to disable an interface from forwarding multicast data, and from sending and receiving IGMP control messages.
The following example enables the to_dslam5 interface on the local context to forward multicast data, and configures the foo IGMP service profile to enable the forwarding of multicast data received on a PPPoE subscriber circuit on the to_dslam5 interface:
[local]Redback(config)#context local [local]Redback(config-ctx)#interface to_dslam5 [local]Redback(config-if)#multicast output accept-unknown-mac [local]Redback(config-if)#exit [local]Redback(config-ctx)#igmp service-profile foo [local]Redback(config-igmp-service-profile)#multicast destination to_dslam5
multicast rate-limit kbps burst-size bytes
no multicast rate-limit
Sets the rate and burst tolerance for multicast traffic on any port, circuit, or Virtual Private LAN Services (VPLS) pseudowire circuit to which you assign this bridge profile.
kbps |
Rate in kilobits per second. The range of values is 5 to 1,000,000. |
burst-size bytes |
Optional. Burst tolerance in bytes. The range of values is 1 to 12,000,000. |
No rate limiting is imposed on multicast traffic on any port, circuit, or VPLS pseudowire circuit to which you assign this bridge profile.
Use the multicast rate-limit command to set the rate and burst tolerance for multicast traffic on any port, circuit, or VPLS pseudowire circuit to which this profile is assigned. For more information about VPLS pseudowire circuits, see Configuring VPLS.
Use the no form of this command to remove any rate limiting for multicast traffic.
The following example shows how to create the prof-isp1 bridge profile and rate limits the multicast traffic to 6000000 kbps and the burst size to 10000 bytes:
[local]Redback(config)#bridge profile prof-isp1 [local]Redback(confg-bridge-profile)#multicast rate-limit 600000 burst-size 10000
multi-paths {external path-num [internal path-num] | internal path-num [external path-num] | eibgp path-num}
{no | default} multi-paths {external path-num [internal path-num] | internal path-num [external path-num] | eibgp}
Configures the Border Gateway Protocol (BGP) routing process to use multiple equal-cost best paths for load-balancing outgoing BGP traffic packets.
BGP router configuration
external path-num |
External BGP (eBGP) equal-cost paths. Optional when internal BGP (iBGP) equal-cost paths are specified. The path-mum argument specifies the maximum number of equal-cost best paths. The range of values is 1 to 8; the default value is 1. |
internal path-num |
eBGP equal-cost paths. Optional when eBGP equal-cost paths are specified. The path-mum argument specifies the maximum number of equal-cost best paths. The range of values is 1 to 8; the default value is 1. |
eibgp path-num |
Configures multipath load balancing using a mixture of both external Border Gateway Protocol (eBGP) and internal BGP (iBGP) equal-cost paths in a BGP/Multiprotocol Label Switching (MPLS) Virtual Private Network (VPN). Replace the path-mum argument with the maximum number of equal-cost paths to use when balancing the traffic load. The range of values is 1 to 8. |
The command is disabled.
Use the multi-paths command to configure the BGP routing process to use multiple equal-cost BGP best paths for load-balancing outgoing traffic packets.
Use the external keyword to balance loads among equal-cost paths from different eBGP neighbors that reside in a single autonomous system (AS). For eBGP, equal-cost means that each path shares the same weight, local preference, AS path length, origin type, and Multi-Exit Discriminator (MED) attributes. If one of these attributes is different, the path is not considered to be an equal-cost path. In addition, the eBGP paths uses originate from the same AS.
Use the internal keyword to balance loads among equal-cost paths from different iBGP neighbors. For iBGP, equal-cost means that each path shares the same weight, local preference, AS path length, origin type, and MED attributes. In addition, each path must share the same Interior Gateway Protocol (IGP) metric to the next hop.
For more information about the multi-paths command, see the Command List.
Use the no or default form of this command to restore the default setting.
The following example load balances outgoing traffic packets between 2 eBGP paths and 5 iBGP paths:
[local]Redback(config)#router bgp 64001 [local]Redback(config-bgp)#multi-paths external 2 internal 5
The following example configures multipath load balancing among any combination of up to 7 eBGP and iBGP equal cost paths:
[local]Redback#config [local]Redback(config)#context local [local]Redback(config)#router bgp [local]Redback(config-bgp)#multi-paths eibgp 7 [local]Redback(config-bgp)#
multi-topology transition
no multi-topology transition
For IP Version 6 (IPv6) Intermediate System-to-Intermediate-System (IS-IS) routing, places an IS-IS instance in multitopology transition mode.
This command has no keywords or arguments.
Multitopology transition mode is disabled for an IS-IS instance.
For IPv6 IS-IS routing, use the multi-topology transition command to place an IS-IS instance in multitopology transition mode.
Temporarily enter the multitopology transition mode if you want the SmartEdge router to route IPv6 traffic and you have existing IPv6 IS-IS routers in the area that are operating in single-topology mode. This transition mode enables routers in single- and multitopology modes to interoperate while you upgrade all routers to multitopology mode. If you do not enter multitopology transition mode, any routers in single-topology mode and those in multitopology mode lose IPv6 connectivity and the resulting IPv6 topology contains holes.
Routers in single-topology mode continue to operate in single-topology mode during the transition. However, they send two types of type-length-values (TLVs) in link-state packets (LSPs) for all configured IPv6 addresses: TLVs for single-topology mode and TLVs for multitopology mode. The topological restrictions of single-topology mode no longer apply when all routers in the area are in multitopology mode.
Use the show configuration isis command to see if a particular IS-IS instance is running in multitopology transition mode.
Use the no form of this command to remove the transition mode from the SmartEdge router configuration. Do so after you upgrade all routers in the area to support multitopology IPv6 IS-IS routing.
The following example shows how to enter multitopology transition mode:
[local]Redback(config-ctx)#router isis isis2 [local]Redback(config-isis)#address-family ipv6 unicast [local]Redback(config-isis-af)#multi-topology transition
national
{no | default} national
Enables or disables the national bit (bit 12 of set 1) in the E3 frame.
This command has no keywords or arguments.
The national bit is disabled
Use the national command to enable the national bit (bit 12 of set 1) in the E3 frame.
You enable the national bit if the digital path crosses a geographical border and only if the port is configured with G.751 framing (the default).
Use either the no or default form of this command to disable the national bit.
The following example shows how to enable the national bit for the E3 port 1 on the clear-channel E3 traffic card in slot 4:
[local]Redback(config)#port e3 4/1 [local]Redback(config-e3)#framing g751 [local]Redback(config-e3)#national
native-vlan-tag value
no native-vlan-tag
Configures a native virtual LAN (VLAN) tag for transporting untagged 802.1Q permanent virtual circuit (PVC) traffic across a pseudowire.
VPLS profile neighbor configuration
value |
Native VLAN tag value. The range of values is 1 to 4,095. |
The native VLAN tag is not configured.
Use the native-vlan-tag command to configure a native VLAN tag for transporting untagged 802.1Q PVC traffic across a pseudowire.
The native VLAN tag value is configurable on the SmartEdge router to enable interoperability with the native VLAN tag used by other devices in the network.
When the native VLAN tag is configured for a pseudowire instance:
Use the no form of this command to remove the native VLAN tag configuration.
The following example configures a native VLAN tag with a tag value of 23:
[local]Redback#config [local]Redback(config)#vpls profile foo [local]Redback(config-vpls-profile)#neighbor 10.10.10.1 [local]Redback(config-vpls-profile-neighbor)#native-vlan-tag 23
nat policy pol-name [radius-guided]
no nat policy pol-name
Configures a Network Address Translation (NAT) policy name and enters NAT policy configuration mode.
context configuration
pol-name |
NAT policy name. |
radius-guided |
Optional. Specifies a Remote Authentication Dial-In User Service (RADIUS) guided policy and allows the policy to be modified by dynamic access control lists (ACLs). |
None
Use the nat policy command to configure a NAT policy name and enter NAT policy configuration mode.
Use the radius-guided keyword to specify a RADIUS-guided policy and to allow the policy to be modified by dynamic ACLs. You cannot remove a dynamic policy ACL from the policy after you have configured it, nor can you change the policy type from static to RADIUS-guided. To remove a dynamic policy ACL or change its type, delete the policy and then recreate it as a static policy.
Use the no form of this command to remove the NAT policy.
The following example translates source addresses for NAT policy, p2, which is applied to packets received on the pos2 interface:
[local]Redback(config-ctx)#nat policy p2 [local]Redback(config-policy-nat)#ip static in source 34.34.34.34 35.35.35.35 [local]Redback(config-policy-nat)#exit [local]Redback(config-ctx)#interface pos2 [local]Redback(config-if)#ip nat p2
nat policy-name pol-name
no nat policy-name pol-name
Attaches the specified Network Address Translation (NAT) policy name to the subscriber’s circuit.
subscriber configuration
pol-name |
NAT policy name. |
None
Use the nat policy-name command to attach the specified NAT policy to the subscriber’s circuit.
Use the no form of this command to remove the NAT policy from the subscriber’s circuit.
The following example attaches the NAT policy, nat-pol-1, to the circuit attached to the nat-sub subscriber’s circuit:
[local]Redback(config-ctx)#subscriber name nat-sub [local]Redback(config-sub)#nat policy-name nat-pol-1
nbns {primary | secondary} ip-addr
no nbns {primary | secondary} ip-addr
Specifies the IP address of the primary or secondary NetBIOS Name Server (NBNS) in the subscriber record or profile.
primary |
Specifies that the IP address is for the primary NBNS. |
secondary |
Specifies that the IP address is for the secondary NBNS. |
ip-addr |
IP address of the primary or secondary NBNS. |
NBNS information is not provided to the subscriber.
Use the nbns command to specify the IP address of the primary or secondary NBNS in the subscriber record or profile.
Use the no form of this command to remove the IP address of the primary or secondary NBNS from the subscriber profile or record.
The following example specifies the primary address of the NBNS in the record for subscriber SamQ:
[local]Redback(config-ctx)#subscriber name SamQ [local]Redback(config-sub)#nbns primary 10.1.1.20
neighbor ipv6-addr mac-addr
no neighbor ipv6-addr mac-addr
Specifies a static neighbor for this Neighbor Discovery (ND) router interface.
ipv6-addr |
IPv6 address for this neighbor in the format A:B:C:D:E:F:G:H. |
mac-addr |
Medium access control (MAC) address for this neighbor. |
No static neighbors are specified for any interface.
Use the neighbor command to specify a static neighbor for this ND router interface. Enter this command multiple times to configure more than one neighbor.
Use the no form of this command to delete the neighbor from the configuration for this ND router interface.
The following example specifies a neighbor with IPv6 address, 2006::1/112, and MAC address, 00:30:88:00:0a:30, for the int1 ND router interface:
[local]Redback(config)#context local [local]Redback(config-ctx)#router nd [local]Redback(config-nd)#interface int1 [local]Redback(config-nd-if)#neighbor 2006::1/112 00:30:88:00:0a:30
neighbor ip-addr
no neighbor ip-addr
Creates a new Bidirectional Forwarding Detection (BFD) neighbor, or selects an existing one for modification, and enters BFD neighbor configuration mode.
ip-addr |
BFD neighbor IP address, in the form A.B.C.D. |
No BFD neighbors are configured.
Use the neighbor command to create a new BFD neighbor, or select an existing one for modification, and enter BFD neighbor configuration mode.
Use the no form of this command to delete a BFD neighbor configuration.
The following example creates a new BFD neighbor, 10.10.10.1:
[local]Redback(config)#context local [local]Redback(config-ctx)#router bfd [local]Redback(config-bfd)#neighbor 10.10.10.1 [local]Redback(config-bfd-nbr)#
neighbor {ip-addr | ipv6-addr} {external | internal}
no neighbor ip-addr {external | internal}
Configures a Border Gateway Protocol (BGP) neighbor and enters BGP neighbor configuration mode.
BGP router configuration
ip-addr |
BGP neighbor IP address in the form A.B.C.D. |
ipv6-addr |
BGP neighbor IP Version 6 (IPv6) address in the form A:B:C:D:E:F:G. |
external |
Identifies the peer as an external BGP (eBGP) neighbor. |
internal |
Identifies the peer as an internal BGP (iBGP) neighbor. |
There are no preconfigured neighbors.
Use the neighbor command to configure a BGP neighbor and enter BGP neighbor configuration mode. If you enter the external keyword, you must also enable the remote-as command in BGP neighbor configuration mode. If you enter the internal keyword, the remote-as command is not needed.
When the neighbor command is issued, the address family for that neighbor defaults to unicast. For an IP Version 4 (IPv4) address family, you can modify this setting through the address-family ipv4 command in BGP neighbor configuration mode.
Use the no form of this command to remove a configured BGP neighbor.
The following example configures an eBGP neighbor at IP address, 102.210.210.1, and enters BGP neighbor configuration mode:
[local]Redback(config-ctx)#router bgp 100 [local]Redback(config-bgp)#neighbor 102.210.210.1 external [local]Redback(config-bgp-neighbor)#
The following example configures an iBGP neighbor at IPv6 address, 28FF:AA12:0DB8:85A3::2000, and enters BGP neighbor configuration mode:
[local]Redback(config-ctx)#router bgp 100 [local]Redback(config-bgp)#neighbor 28FF:AA12:0DB8:85A3::2000 internal [local]Redback(config-bgp-neighbor)#
neighbor {ip-addr | ipv6-addr} [cost cost] [poll-interval interval] [router-priority priority]
no neighbor {ip-addr | ipv6-addr} [cost cost] [poll-interval interval] [router-priority priority]
Configures an Open Shortest Path First (OSPF) or OSPF Version 3 (OSPFv3) neighbor.
ip-addr |
OSPF neighbor IP address in the form A.B.C.D. |
ipv6-addr |
OSPFv3 neighbor IP Version 6 (IPv6) address in the form A:B:C:D:E:F:G. |
cost cost |
Optional. Cost to reach the neighbor. This cost overrides the interface cost set through the cost command (in OSPF or OSPF3 interface configuration mode). The range of values is 1 to 65,535; the default value is 1. |
poll-interval interval |
Optional. Interval, in seconds, at which the neighbor is polled when it is unreachable or down. The range of values is 1 to 65,535; the default value is 120. |
router-priority priority |
Optional. Priority setting for the neighbor. The range of values is 0 to 255; the default value is 1. |
If a cost value is not specified, the value set through the cost command is used; otherwise, the cost is 1. The poll interval is 120 seconds; the router priority is 1.
Use the neighbor command to configure an OSPF or OSPFv3 neighbor.
You can only use the router-priority priority construct for nonbroadcast multiaccess (NBMA) networks when designated and backup routers are elected.
Use the no form of this command to remove a neighbor configuration.
The following example sets a cost of 10 for the neighbor at IP address 193.12.3.2:
[local]Redback(config-ospf-if)#neighbor 193.12.3.2 cost 10
neighbor ip-addr password password
no neighbor ip-addr password
Assigns an encrypted Message Digest 5 (MD5) password to a Label Distribution Protocol (LDP) neighbor.
LDP router configuration
ip-addr |
Neighbor IP address in the form A.B.C.D. |
password |
Alphanumeric string consisting of up to 80 characters. |
MD5 password is disabled.
Use the neighbor password command to assign an encrypted MD5 password to an LDP neighbor.
Use the no form of this command to remove the password from an LDP neighbor.
The following example assigns the password, secret, to LDP neighbor, 10.1.1.1:
[local]Redback(config-ctx)#router ldp [local]Redback(config-ldp)#neighbor 10.1.1.1 password secret
neighbor profile prof-name
no neighbor profile prof-name
Creates an empty Access Node Control Protocol (ANCP) profile for an ANCP neighbor peer, and accesses ANCP neighbor configuration mode.
prof-name |
ANCP neighbor profile name. |
No ANCP neighbor profile exists.
Use the neighbor profile command to create an ANCP neighbor profile and access ANCP neighbor configuration mode.
The SmartEdge router listens for incoming ANCP sessions, using the Transmission Control Protocol (TCP) local port that you have configured with the tcp-port local command (in ANCP configuration mode). When an ANCP session is received, its attributes must match the attributes you have configured for one of the ANCP neighbor profiles. This means that the session must match each attribute that you have configured for the profile. If an attribute is not configured, then any value for that attribute is accepted. For example, if the remote TCP port is not configured, then the incoming session can have any source port number, as long as the other items match. An empty neighbor profile with no attributes configured allows all incoming connections.
Use the no form of this command to delete this ANCP neighbor profile.
The following example creates the ancp-profile ANCP neighbor profile and accesses ANCP neighbor configuration mode:
[local]Redback(config-ancp)#neighbor profile ancp-profile [local]Redback(config-ancp-neighbor)#
neighbor ip-addr targeted
no neighbor ip-addr targeted
Configures a remote Label Distribution Protocol (LDP) neighbor and enables extended LDP discovery of the specified neighbor.
LDP router configuration
ip-addr |
IP address of the remote LDP neighbor in the form A.B.C.D. |
Extended LDP discovery is disabled.
There are two types of LDP neighbor discovery mechanisms: basic LDP discovery and extended LDP discovery. Basic LDP discovery is used to discover immediate neighbors; extended LDP discovery is used to discover neighbors that can be multiple hops away.
There are two types of LDP Hello messages: link Hello messages and targeted Hello messages. Link Hello messages are multicast on an interface to immediate neighbors. Link Hello messages are used in basic LDP discovery. Targeted Hello messages are unicast directly to remote neighbors, and are used in extended LDP discovery. Two LDP speaking label-switched routers (LSRs) can form LDP adjacencies after discovering each other. LDP adjacencies discovered by link Hello messages are link Hello adjacencies. LDP adjacencies discovered by targeted Hello messages are targeted Hello adjacencies.
Use the neighbor targeted command to configure a remote LDP neighbor and enable extended LDP discovery of the specified neighbor. Targeted Hello messages can be transmitted or accepted to or from the specified neighbor.
Use the no form of this command to remove a configured remote LDP neighbor, and to disable extended LDP discovery of the specified neighbor.
The following example configures a remote neighbor of address 10.1.1.1:
[local]Redback(config-ctx)#router ldp [local]Redback(config-ldp)#neighbor 10.1.1.1 targeted
neighbor ip-addr
{no | default} neighbor ip-addr
Creates a new neighbor, or selects an existing one for modification, and enters Virtual Private LAN Services (VPLS) profile neighbor configuration mode.
VPLS profile configuration
ip-addr |
Neighbor IP address, in the form A.B.C.D. |
None
Use the neighbor command to create a new neighbor, or select an existing one for modification, and enter VPLS profile neighbor configuration mode.
The neighbor is identified by the IP address of the remote provider edge (PE) device. It is used along with the pseudowire ID from the VPLS instance configuration to establish a pseudowire between the local and remote PE devices. Multiple peering sessions (created by VPLS profiles) can be established to the same PE device; different profiles can reference the same remote PE IP address.
Use the no or default form of this command to remove a configured neighbor.
The following example creates a new VPLS neighbor with the IP address, 10.10.10.1:
[local]Redback#config [local]Redback(config)#vpls profile foo [local]Redback(config-vpls-profile)#neighbor 10.10.10.1 [local]Redback(config-vpls-profile-neighbor)#
net net
no net net
Configures a network entity title (NET) for the Intermediate System-to-Intermediate System (IS-IS) routing process.
IS-IS router configuration
net |
Area address and system ID for the IS-IS routing process. This argument can be either an address in hexadecimal-dotted byte format or a name. |
A NET is mandatory for IS-IS operation. If this option is not configured, the IS-IS instance is disabled.
Use the net command to configure a NET for the IS-IS routing process.
Network entity titles can be anywhere between 8 and 20 bytes in length, and are provided in a hexadecimal-dotted byte format, such as 47.0005.80ff.e200.02aa.0a00.0002.00. The last byte, which is the Network Service Access Point (NSAP) n-selector, must be zero. The 6 bytes before the last byte indicate the system ID. This ID must be the same for all NETs configured for the system, and must be unique within the IS-IS domain. The bytes before that indicate an area ID, which is a variable from 1 to 13 bytes. Multiple areas can be specified in scenarios of area merges and the necessity of renumbering. The protocol will not form a level 1 adjacency between two devices if they have no areas in common.
Use the no form of this command to remove a NET.
The following example assigns a NET of 47.0001.0002.0002.0002.00 to the ip-backbone IS-IS instance:
[local]Redback(config-ctx)#router isis ip-backbone [local]Redback(config-isis)#net 47.0001.0002.0002.0002.00
netop
no netop
Enables the NetOp daemon, which allows the SmartEdge router to communicate with the NetOp Element Management System (EMS) server, and enters NetOp configuration mode.
global configuration
This command has no keywords or arguments.
The NetOp daemon is disabled.
Use the netop command to enable the NetOp daemon, which allows the SmartEdge router to communicate with the NetOp EMS server, and enter NetOp configuration mode.
Use the no form of this command to disable communication with the NetOp EMS server.
The following example enables the SmartEdge router to communicate with the NetOp EMS server and enters NetOp configuration mode:
[local]Redback(config)#netop [local]Redback(config-netop)#
network {ip-addr/prefix-length | ipv6-addr/prefix-length} [route-map map-name]
no network {ip-addr/prefix-length | ipv6-addr/prefix-length} [route-map map-name]
Originates Border Gateway Protocol (BGP) routes that are advertised to peers for the BGP address family.
BGP address family configuration
ip-addr/prefix-length |
Specifies the IP address, in the form A.B.C.D, and the prefix length, separated by the slash (/) character. The range of values for the prefix-length argument is 0 to 32. |
ipv6-addr/prefix-length |
Specifies the IP Version 6 (IPv6) address, in the form A:B:C:D:E:F:G:H,and the prefix length, separated by the slash (/) character. The range of values for the prefix-length argument is 0 to 128. |
route-map map-name |
Optional. Route map conditions to apply to the prefix. |
No routes are specified.
Use the network command to originate BGP routes that are advertised to peers.
Use the route-map map-name construct to apply a route map to modify the BGP attributes of these routes. Routes specified in the network command must exist in the routing table to generate those routes into BGP.
Use the no form of this command to remove routes.
The following example advertises unicast route 120.34.56.0/24 to unicast BGP neighbors. Multicast route 40.0.0.0/8 is advertised to multicast BGP neighbors using a metric of 100. The two ip route commands in context configuration mode statically add these routes to the routing table:
[local]Redback(config-ctx)#ip route 40.0.0.0/8 null0 [local]Redback(config-ctx)#ip route 120.34.56.0/24 null0 [local]Redback(config-ctx)#route-map map1 [local]Redback(config-route-map)#set metric 100 [local]Redback(config-route-map)#exit [local]Redback(config-ctx)#router bgp 100 [local]Redback(config-bgp)#address-family ipv4 unicast [local]Redback(config-bgp-af)#network 120.34.56.0/24 [local]Redback(config-bgp-af)#exit [local]Redback(config-bgp)#address-family ipv4 multicast [local]Redback(config-bgp-af)#network 40.0.0.0/8 route-map map1
network-type {broadcast | non-broadcast | point-to-point | point-to-multipoint}
no network-type
Configures the Open Shortest Path First (OSPF) or OSPF Version 3 (OSPFv3) network type.
broadcast |
Specifies that the interface is attached to a broadcast network. |
non-broadcast |
Specifies that the interface is attached to a nonbroadcast network. |
point-to-point |
Specifies that the interface is attached to a point-to-point (P2P) network. |
point-to-multipoint |
Specifies that the interface is attached to a point-to-multipoint (P2MP) network. |
The media type determines the network type; for example, an Ethernet interface defaults to the broadcast type.
Use the network-type command to configure the following types of OSPF or OSPF3 networks:
Use the no form of this command to return the network type to its default value.
The following example configures the network type as a broadcast network:
[local]Redback(config-ospf-if)#network-type broadcast
next-hop next-hop-addr {loose | strict}
no next-hop next-hop-addr
Configures a next-hop entry for a Resource Reservation Protocol (RSVP) explicit route, or for a static label-switched path (LSP).
next-hop-addr |
IP address of the next-hop label-switched router (LSR). |
loose |
Specifies that the next hop does not need to be directly connected to the previous node. |
strict |
Specifies that the next hop is directly connected to the previous node in the path. |
Strict.
Use the next-hop command to configure a next-hop entry for an RSVP explicit route, or for a static LSP.
Use the no form of this command to remove a next-hop entry from an RSVP explicit route. You cannot remove a next-hop entry from a static LSP.
The following example configures two next-hop entries for an RSVP explicit route:
[local]Redback(config-ctx)#router rsvp [local]Redback(config-rsvp)#explicit-route ex-route02 [local]Redback(config-rsvp-explicit-route)#next-hop 13.1.1.2 [local]Redback(config-rsvp-explicit-route)#next-hop 14.1.1.2
The following example configures two next-hop entries for a static LSP:
[local]Redback(config-ctx)#router mpls-static [local]Redback(config-mpls-static)#lsp 24 [local]Redback(config-mpls-static-lsp)#next-hop 20.20.20.10 [local]Redback(config-mpls-static-lsp)#next-hop 30.20.20.16
next-hop-on-lsp
no next-hop-on-lsp
Requires the next hop of a Border Gateway Protocol (BGP) Virtual Private Network (VPN) path to be reachable through a Multiprotocol Label Switching (MPLS) label-switched path (LSP) or a tunnel in order for a VPN route to be considered active.
BGP router configuration
This command has no keywords or arguments.
The next hop of a BGP VPN path must be reachable through an MPLS LSP or a tunnel in order for the VPN route to be considered active.
Use the next-hop-on-lsp command to require the next hop of a BGP VPN path to be reachable through an MPLS LSP or a tunnel, in order for a VPN route to be considered active.
Use the no form of this command to enable a BGP VPN path to be considered active without requiring the next hop of a VPN path to be reachable through an MPLS LSP or a tunnel.
One common application for this command is configuring a BGP route reflector that is not part of an MPLS network, but is used to reflect BGP VPN routes to its clients within that MPLS network. In this configuration, the next hops of the VPN paths may not be reachable through an MPLS LSP or a tunnel from the route reflector's point of view. To solve the problem, use the no form of this command to disable the LSP or tunnel reachability check for the next hops, and therefore allow the BGP route reflector to correctly select the best paths and reflect the best paths to its clients.
The following example enables the sending of BGP VPN routes when the next hop is not resolved or reachable:
[local]Redback(config)#context local [local]Redback(config-ctx)#router bgp [local]Redback(config-bgp)#next-hop-on-lsp [local]Redback(config-bgp)#
next-hop-self
no next-hop-self
Advertises the local peer address as the next-hop address for all external Border Gateway Protocol (eBGP) routes sent to the specified neighbor or peer group.
This command has no keywords or arguments.
The command is disabled.
Use the next-hop-self command to advertise the local peer address as the next-hop address for all eBGP routes sent to the specified BGP neighbor or peer group. This command disables the sending of third-party next-hop information to peers.
By default, when it receives BGP routes from an eBGP neighbor, the BGP routing process forwards eBGP routes to its internal BGP (iBGP) neighbors without changing the next-hop address; this is still the case if the eBGP neighbors are on the same subnet as the local BGP speaker.
When you enable the next-hop-self command, the BGP routing process changes the next-hop address, advertising the local peer address as the next-hop address for all received eBGP routes.
Use the no form of this command to restore the default behavior of sending third-party next-hop information to peers.
The following example ensures that all updates destined for the neighbor at IP address, 10.100.1.102, advertise this SmartEdge router as the next hop:
[local]Redback(config-ctx)#router bgp 64001 [local]Redback(config-bgp)#neighbor 10.100.1.102 external [local]Redback(config-bgp-neighbor)#remote-as 64001 [local]Redback(config-bgp-neighbor)#next-hop-self
The following example provides output from the show bgp neighbor command where the neighbor views the SmartEdge router as the next hop for all received routes:
[local]Redback>show bgp neighbor 10.100.1.102 BGP neighbor: 10.100.1.102, remote AS: 64001, internal link Version: 4, router identifier: 10.100.1.102 State: Established for 00:41:01 . . . Next hop set to self (next-hop-self) . . . Prefixes: advertised 99877, accepted 2, active 2
nexthop triggered
no nexthop triggered
Enables the triggering of an immediate BGP best-path calculation on notification of a next-hop change by the RIB.
BGP address family configuration
This command has no keywords or arguments.
Next-hop triggering is disabled.
Use the nexthop triggered command to the triggering of an immediate BGP best-path calculation on notification of a next-hop change by the RIB.
Use the no form of this command to disable next-hop triggering on a BGP instance.
The following example shows how to enable the triggering of an immediate BGP best-path calculation on notification of a next-hop change by the RIB:
[local]Redback#configure [local]Redback(config)#context local [local]Redback(config-ctx)#router bgp 100 [local]Redback(config-bgp)#address-family ipv4 vpn [local]Redback(config-bgp-af)#nexthop triggered
nexthop triggered delay seconds
no nexthop triggered delay seconds
Defines the minimum interval, in seconds, between next-hop scans.
BGP address family configuration
seconds |
Minimum number of seconds allowed between next-hop scans. Values range from 0 through 30 seconds. (1)A value of 0 triggers an immediate next-hop scan. |
3 seconds
Use the nexthop triggered delay command to configure the minimum number of seconds allowed between next-hop scans. This delay allows time for network convergence when frequent next-hop change notifications occur.
Use the no form of this command to return the router to the default setting in which next-hop scans occur every 3 seconds.
The following example shows how to configure the minimum interval between next-hop scans to be 20 seconds:
[local]Redback#configure [local]Redback(config)#context local [local]Redback(config-ctx)#router bgp 100 [local]Redback(config-bgp)#address-family ipv4 vpn [local]Redback(config-bgp-af)#nexthop triggered delay 20
nexthop triggered holdtime seconds [backoff seconds] [delay seconds]
no nexthop triggered holdtime
Defines the minimum interval, in seconds, between triggered RIB scans.
BGP address-family configuration
seconds |
Time, in seconds, between next-hop scans. The range of values is 1 through 30 seconds; the default value is 3. A value of 0 triggers an immediate next-hop scan. |
backoffseconds |
Optional. Time, in seconds, by which BGP increases the RIB scan frequency. The range of values is 0 through 30 seconds. |
delayseconds |
Optional. Number of seconds BGP waits before adding the configured backup value to the RIB scan frequency. |
holdtime seconds = 3 seconds
Use the nexthop triggered holdtime command to define the minimum interval, in seconds, between triggered RIB scans.
Use the no form of this command to disable next-hop triggering on a BGP instance.
The following example shows how to configure the triggering of immediate BGP best path calculation on notification of a next-hop change by the RIB:
[local]Redback#configure [local]Redback(config)#context local [local]Redback(config-ctx)#router bgp 100 [local]Redback(config-bgp)#address-family ipv4 vpn [local]Redback(config-bgp-af)#nexthop triggered holdtime 15
debug all
Disables the generation of all debug message types supported by the SmartEdge router.
This command has no keywords or arguments.
Debugging is disabled.
Use the no debug all command to disable the generation of all debug messages types supported by the SmartEdge router. The no debug all command displays the functions of the debug commands, which are listed in Table 3.
Feature |
Command |
---|---|
General system processes |
debug rcm, debug snmp, debug ssh |
IP routing |
debug ip routing, debug isis all, debug ospf, debug policy general, debug rip, debug vrrp |
BGP routing |
debug bgp event, debug bgp listen, debug bgp message, debug bgp policy, debug bgp rib, debug bgp session-state, debug bgp update |
IP services |
debug arp, debug dhcp-relay, debug ip dns, debug nat, debug ntp |
Quality of service |
debug qos |
Access control lists |
debug cls, debug ip-access-list |
Authentication |
debug aaa |
The following example disables the generation of all debugging messages:
[local]Redback#no debug all
notify notify-oid
no notify
Identifies the name of the notification you want to use for the SNMP alarm model.
notify-oid |
Object identifier (OID) in words or numbers of the notification you are using for the SNMP alarm model. |
None
Use the notify command to identify the name of the notification to use for the SNMP alarm model. Set the name by identifying the OID (in name or number) of the notification to configure.
Use the no form of this command to remove the name of the notification for this alarm model.
The following example shows how to name the linkup notification as the notification for this alarm model.
[local]jazz#config [local]jazz(config)#snmp alarm model 1 state clear [local]jazz(config-snmp-alarmmodel)#notify linkUp [local]jazz(config-snmp-alarmmodel)#
ns-retry-interval retrans-timer
{no | default} ns-retry-interval
Specifies the value for the Retrans Timer field.
retrans-timer |
Value for the Retrans Timer field (in milliseconds). The range of values is 0 to 4294967295; the default value is 0. |
The Retrans Timer field is 0 (unspecified).
Use the ns-retry-interval command to specify the value for the Retrans Timer field. In ND router configuration mode, this command specifies the global value for all interfaces; in ND router interface mode, it specifies the value for this Neighbor Discovery (ND) router interface. If specified, the setting for the interface overrides the global setting.
Use the no or default form of this command to specify the default value for the Retrans Timer field.
The following example specifies 100 milliseconds for the Retrans Timer field for the ND router:
[local]Redback(config)#context local [local]Redback(config-ctx)#router nd [local]Redback(config-nd-if)#ns-retry-interval 100
The following example specifies 20 milliseconds for the Retrans Timer field for the ND router interface, int1, which overrides the global setting:
[local]Redback(config)#context local [local]Redback(config-ctx)#router nd [local]Redback(config-nd)#interface int1 [local]Redback(config-nd-if)#ns-retry-interval 20
nssa-range ip-addr {netmask | /prefix-length} [not-advertise | tag tag]
no nssa-range ip-addr {netmask | /prefix-length} [not-advertise | tag tag]
Summarizes not-so-stubby-area (NSSA) routes advertised by an area border router (ABR).
ip-addr |
IP address in the form A.B.C.D. |
netmask |
Network mask in the form E.F.G.H. |
prefix-length |
Prefix length. The range of values is 0 to 32. |
not-advertise |
Optional. Prevents all routes in the specified range from being advertised in interarea route summarizations. |
tag tag |
Optional. Route tag included in translated external route summarization Type 5 link-state advertisements (LSAs). An unsigned 32-bit integer, the range of values is 1 to 4,294,967,295; the default value is 0. |
Address ranges for NSSA route summarization are not specified.
Use the nssa-range command to summarize NSSA routes advertised by an ABR. This command is used for NSSA-translated external route summarization and is only relevant when the router is configured as an ABR.
Use the optional not-advertise keyword to prevent the specified route from being advertised in translated external route summarizations.
Use the no form of this command to disable route summarization for a particular summary range. All individual routes contained in the summary range are advertised to other areas.
The following example sends routes that fall into the range 10.1.0.0 255.255.0.0 as a single autonomous system (AS) external advertisement:
[local]Redback(config-ospf-area)#nssa-range 10.1.0.0 255.255.0.0
ntp mode
Enters NTP configuration mode.
global configuration
This command has no keywords or arguments.
None
Use the ntp mode command to enter NTP configuration mode.
The following example changes the mode from global configuration to NTP configuration:
[local]Redback(config)#ntp mode [local]Redback(config-ntp)#
ntp peer ip-addr [context ctx-name] [prefer] [source if-name] [version ver-num]
no ntp peer [ip-addr]
Configures peer association for symmetric synchronization of the SmartEdge router time and remote Network Time Protocol (NTP) peer time.
global configuration
ip-addr |
IP address of the remote NTP peer. Optional when used with the no form of this command. |
context ctx-name |
Optional. Context in which the destination address is reachable. This construct is used when the NTP peer must be reached through a context other than local. |
prefer |
Optional. Marks the NTP peer as the preferred peer when multiple NTP peers are configured. |
source if-name |
Optional. SmartEdge interface that is to be used for NTP traffic. |
version ver-num |
Optional. NTP version. Version options are 1, 2, and 3; the default value is 3. |
The context for the NTP peer is the local context. The NTP version is Version 3.
Use the ntp peer command to configure a peer association for symmetric synchronization of the SmartEdge router time and remote NTP peer time.
Use the no form of this command to disable NTP services on the peer device.
Caution! | ||
Risk of data loss. If you use the no form without
specifying the IP address of a specific peer, all existing NTP peer
associations are removed. To reduce the risk, of losing NTP peer associations,
always specify the IP address when using the no form.
|
The following example configures the SmartEdge router to symmetrically synchronize with the remote NTP peer at IP address, 155.53.32.75. The peer is also marked as the preferred peer:
[local]Redback(config)#ntp peer 155.53.32.75 prefer
ntp server ip-addr [context ctx-name] [prefer] [source if-name] [version ver-num]
no ntp server [ip-addr]
Configures the SmartEdge router to synchronize to a remote Network Time Protocol (NTP) server.
global configuration
ip-addr |
IP address of the remote NTP server. Optional when used with the no form of this command. |
context ctx-name |
Optional. Context in which the destination address is reachable. This construct is used when the NTP server must be reached through a context other than local. |
prefer |
Optional. Marks the NTP server as the preferred server when multiple NTP servers are configured. |
source if-name |
Optional. SmartEdge interface that is to be used for NTP traffic. |
version ver-num |
Optional. NTP version. Version options are 1, 2, and 3; the default value is 3. |
NTP is disabled.
Use the ntp server command to start the NTP daemon and configure the SmartEdge router to synchronize to a remote NTP server.
Use the no form of this command to disable NTP services on the device. If you use the no form without specifying the IP address of a specific server, all existing NTP server associations are removed.
The following example configures the NTP client to synchronize with an NTP remote server at IP address, 155.53.12.12, and makes it the preferred server:
[local]Redback(config)#ntp server 155.53.12.12 prefer
In EDRR, MDRR, PQ, and PWFQ policy configuration modes, the command syntax is:
num-queues {1 | 2 | 4 | 8}
{no | default} num-queues
In ATMWFQ policy and queue map configuration modes, the command syntax is:
num-queues {2 | 4 | 8}
{no | default} num-queues
In ATMWFQ, EDRR, MDRR, PQ, or PWFQ policy configuration mode, specifies the number of queues for the policy.
In queue map configuration mode, specifies the number of queues for the quality of service (QoS) queue map, and enters num-queues configuration mode.
1 |
Specifies that the policy has one queue.(1) |
2 |
Specifies that the policy has two queues.(2) |
4 |
Specifies that the policy has four queues. (1) |
8 |
Specifies that the policy has eight queues. (1) |
(1) In EDRR, MDRR, PQ, and PWFQ policy configuration
modes
(2) In ATMWFQ and queue map configuration modes
Use the num-queues command in ATMWFQ policy, EDRR policy, MDRR policy, PQ policy, or PWFQ policy configuration mode to specify the number of queues to be used for the policy.
Use the num-queues command in queue map configuration mode to specify number of queues for the queue map, and to enter num-queues configuration mode.
Caution! | ||
Risk of dropping packets. Modifying the parameters of an ATMWFQ
policy will momentarily interrupt the traffic on all ATM permanent
virtual circuits (PVCs) using the policy. To reduce the risk, use
caution when modifying ATMWFQ policy parameters.
|
Caution! | ||
Risk of traffic disruption. Modifying the parameters of an MDRR
policy momentarily removes the rate applied to all 10GE circuits using
the policy. The rate is restored as soon as the change is effective.
To reduce the risk, use caution when modifying MDRR policy parameters.
|
Use the no or default form of this command to specify the default number of queues.
The following example configures the PQ policy, firstout, to have 4 queues:
[local]Redback(config)#qos policy firstout pq [local]Redback(config-policy-pq)#num-queues 4