Contents

1   Command Descriptions

Commands starting with “shoz” through commands starting with “sz” are included.

1.1   shutdown (ATM)

1.1.1   Purpose

Disables the specified Asynchronous Transfer Mode (ATM) OC, Ethernet, or Packet over SONET/SDH (POS) port.

1.1.2   Command Mode

• ATM OC configuration
• Port configuration

1.1.3   Syntax Description

This command has no keywords or arguments.

1.1.4   Default

All ports are disabled.

1.1.5   Usage Guidelines

Use the shutdown command to enable or disable the specified ATM, Ethernet, or POS port. No data is transmitted or received when the port is disabled (shut down).

Note:  

You must enable POS port before adding it to an Automatic Protection Switching (APS) group.

Note:  

By default, any ATM permanent virtual circuits (PVCs) that you configure on an ATM port are enabled, but you must enable the port for them to function.

Use the no form of this command to enable a port and have data transmitted or received on the port.

To display the port or channel state, enter the show port detail command (in any mode).

This command is also described in:

• Configuring Circuits for ATM, Frame Relay, and 802.1Q permanent virtual circuits (PVCs).
• Configuring Cross-Connections for cross-connected circuits.
• Configuring GRE Tunnels for Generic Routing Encapsulation (GRE) tunnel circuits.

1.1.6   Examples

The following example shows how to enable port 1 in for the Ethernet line card installed in slot 2:

[local]Redback(config)#port ethernet 2/1

[local]Redback(config-port)#no shutdown

1.2   shutdown (BGP)

1.2.1   Purpose

Administratively shuts down the Border Gateway Protocol (BGP) session with the specified neighbor or peer group.

1.2.2   Command Mode

• BGP neighbor configuration
• BGP peer group configuration

1.2.3   Syntax Description

This command has no keywords or arguments.

1.2.4   Default

None

1.2.5   Usage Guidelines

Use the shutdown command to administratively shut down the BGP session with the specified neighbor or peer group. This command is useful to temporarily shut down a session without removing the BGP neighbor from the SmartEdge® router configuration.

Use the no form of this command to restore the BGP session between the SmartEdge router and the specified neighbor.

1.2.6   Examples

The following example shows how to administratively shut down the BGP session with the neighbor at IP address 10.100.3.2:

[local]Redback(config-ctx)#router bgp 64001

[local]Redback(config-bgp)#neighbor 10.100.3.2 external

[local]Redback(config-bgp-neighbor)#shutdown

1.3   shutdown (Card)

1.3.1   Purpose

Takes the I/O carrier card, services card, or line card out of service.

1.3.2   Command Mode

• Card configuration mode

1.3.3   Syntax Description

This command has no keywords or arguments.

1.3.4   Default

The I/O carrier card, services card, or line card is in service.

1.3.5   Usage Guidelines

Use the shutdown command to take the specified I/O carrier card, services card, or line card out of service in preparation for an on-demand diagnostic (ODD) session. No data is transmitted or received on any port when the line card is out of service.

In the current release, you can test the following SmartEdge router line cards:

• ATM OC-12c/STM-3c, and second-generation ATM OC line cards
• 10/100 Ethernet and Fast Ethernet-Gigabit Ethernet (FE-GE) line cards
• Gigabit Ethernet (any version)
• SONET/SDH OC-3c/STM-1c, OC-12c/STM-4c, OC-48c/STM-16c, OC-192c/STM-64c line cards
• Advanced Services Engine

You can test the following SmartEdge 100 cards:

• Controller carrier card (Ethernet management port)
• I/O carrier card and MICs (native ports, MIC ports)

Note:  

The state of each port on the carrier card or line card, including any cross-connected circuits, is saved to allow it to be restored after the line card is placed in service.

Use the no form of this command to put the card in service and restore the operational state of its ports.

To display the port state, enter the show port detail command (in any mode).

1.3.6   Examples

The following example shows how to take the Ethernet line card installed in slot 3 out of service:

[local]Redback#configure

[local]Redback(config)#card ge-5-port 3

[local]Redback(config-card)#shutdown

1.4   shutdown (Channel)

1.4.1   Purpose

Disables the specified channel or channel group.

1.4.2   Command Mode

• DS-0 group configuration
• DS-1 configuration
• DS-3 configuration
• E1 configuration
• E3 configuration
• STM-1 configuration

1.4.3   Syntax Description

This command has no keywords or arguments.

1.4.4   Default

All channels are disabled.

1.4.5   Usage Guidelines

Use the shutdown command to enable or disable the specified channel or channel group.

No data is transmitted or received when the channel or channel group is shut down. You must use the no form of this command to enable any channel or channel group.

To display the channel state, enter the show port detail command (in any mode).

Use the no form of this command to enable a channel or channel group.

1.4.6   Examples

The following example shows how to enable DS-3 channel 1 on channelized OC-12 port 1 in slot 4:

[local]Redback(config)#card ch-oc12ds3-1-port 1

[local]Redback(config)#exit

[local]Redback(config)#port ds3 4/1:1

[local]Redback(config-ds3)#no shutdown

1.5   shutdown (Mobile IP)

1.5.1   Purpose

Disables or enables the foreign-agent (FA) instance, home-agent (HA) peer, or mobile node (MN) access to the SmartEdge router for an FA instance.

1.5.2   Command Mode

• FA configuration
• HA peer configuration
• Mobile IP interface configuration

1.5.3   Syntax Description

This command has no keywords or arguments.

1.5.4   Default

All FA instances, HA peers, and Mobile IP interfaces are enabled.

1.5.5   Usage Guidelines

Use the shutdown command to disable the FA instance, the HA peer, or the MN interface for an FA instance.

Use the no form of this command to enable the FA instance, the HA peer, or the MN interface for an FA instance.

1.5.6   Examples

The following example shows how to disable an FA instance:

[local]Redback(config)#context fa

[local]Redback(config-ctx)#router mobile-ip

[local]Redback(config-mip)#foreign-agent

[local]Redback(config-mip-fa)#shutdown

The following example shows how to disable an HA peer:

[local]Redback(config)#context fa

[local]Redback(config-ctx)#router mobile-ip

[local]Redback(config-mip)#foreign-agent

[local]Redback(config-mip-fa)#home-agent-peer 172.16.2.1

[local]Redback(config-mip-hapeer)#shutdown

The following example shows how to disable the MN interface for an FA instance:

[local]Redback(config-ctx)#router mobile-ip

[local]Redback(config-mip)#interface mn-access

[local]Redback(config-mip-if)#shutdown

1.6   shutdown (MSDP peers)

1.6.1   Purpose

Disables a configured Multicast Source Discovery Protocol (MSDP) peer.

1.6.2   Command Mode

MSDP peer configuration

1.6.3   Syntax Description

This command has no keywords or arguments.

1.6.4   Default

The peer is up when configured.

1.6.5   Usage Guidelines

Use the shutdown command to disable a configured MSDP peer.

Use the no form of this command to bring up a configured MSDP peer.

1.6.6   Examples

The following example shows how to disable an MSDP peer:

[local]Redback(config-ctx)#router msdp

[local]Redback(config-msdp)#peer 10.200.1.2 local-tcp-source lo1

[local]Redback(config-msdp-peer)#shutdown

1.7   shutdown (Port)

1.7.1   Purpose

Disables the specified port.

1.7.2   Command Mode

Port configuration

1.7.3   Syntax Description

This command has no keywords or arguments.

1.7.4   Default

All ports and channels are disabled.

1.7.5   Usage Guidelines

Use the shutdown command to enable or disable the specified port.

No data is transmitted or received when the port is shut down. You must use the no form of this command to enable any port.

To display the port state, enter the show port detail command (in any mode).

Use the no form of this command to enable a port.

1.7.6   Examples

[local]Redback(config)#port atm 4/1

[local]Redback(config-atm-oc)#no shutdown

The following example shows how to enable the Ethernet port 1 in slot 2.:

[local]Redback(config)#port ethernet 2/1

[local]Redback(config-port)#no shutdown

1.8   shutdown (PVC)

1.8.1   Purpose

Disables the specified link group or Asynchronous Transfer Mode (ATM), Frame Relay, or 802.1Q permanent virtual circuit (PVC).

1.8.2   Command Mode

• ATM PVC configuration
• dot1q PVC configuration
• Frame Relay PVC configuration
• Link group configuration
• Link PVC configuration

1.8.3   Syntax Description

This command has no keywords or arguments.

1.8.4   Default

All PVCs are enabled.

1.8.5   Usage Guidelines

Use the shutdown command to disable the specified link group or ATM, Frame Relay, or 802.1Q PVC. No data is transmitted or received when a PVC or link group is shut down.

Note:  

The SmartEdge 100 router does not support Frame Relay or ATM PVCs.

Use the no form of this command to enable anATM PVC, Frame Relay PVC, 802.1Q PVC, or link group.

Note:  

You must also enable the port, channel, or both port and channel, on which circuits are configured for the circuits to function.

This command is also described in:

• Configuring ATM, Ethernet, and POS Ports for ATM OC, Ethernet, and Packet over SONET/SDH (POS) ports.
• Configuring GRE Tunnels for Generic Routing Encapsulation (GRE) tunnel circuits.

1.8.6   Examples

1.9   shutdown (RSVP LSP)

1.9.1   Purpose

Disables a Resource Reservation Protocol (RSVP) label-switched path (LSP).

1.9.2   Command Mode

RSVP LSP configuration

1.9.3   Syntax Description

This command has no keywords or arguments.

1.9.4   Default

The RSVP LSP is enabled when configured.

1.9.5   Usage Guidelines

Use the shutdown command to disable an RSVP LSP.

Use the no form of this command to enable an existing RSVP LSP that has been disabled.

1.9.6   Examples

The following example shows how to disable the RSVP LSP, test03:

[local]Redback(config-ctx)#router rsvp

[local]Redback(config-rsvp)#lsp test03

[local]Redback(config-rsvp-lsp)#shutdown

1.10   shutdown (Spanning Tree)

1.10.1   Purpose

Shuts down the Spanning Tree Protocol process on the bridge.

1.10.2   Command Mode

Spanning-tree configuration

1.10.3   Syntax Description

This command has no keywords or arguments.

1.10.4   Default

The Spanning Tree Protocol is running if enabled by the spanning-tree command (in bridge configuration mode).

1.10.5   Usage Guidelines

Use the shutdown command to shutdown the Spanning Tree Protocol process on the bridge.

1.10.6   Examples

The following examples shows how to shut down the Spanning Tree Protocol on a bridge.

[local]Redback(config-bridge-stp)#shutdown

1.11   shutdown (SSE)

1.11.1   Command Mode

Card configuration

1.11.2   Syntax Description

1.11.3   Default

Both disks on the SSE card are enabled if inserted.

1.11.4   Usage Guidelines

Disables the SSE card or specified SSE disk. No data is transmitted or received when the card is shut down.

If the SSE card is configured for Network RAID 1 redundancy with RAID 0 disks, shutting down one of the disks stops the service of the entire card, because the other disk cannot be used by itself under RAID 0 configuration.

If you issue this command on the active SSE card during data synchronization on any partition, the following warning message appears:Note: Executing the command during data synchronization on any of the partitions will cause data corruption. 30 Commit to continue; abort to exit without change.

Use the no form of this command to enable the SSE card or SSE disk.

Before you decommission an SSE card that is not configured for redundancy, you must shut it down, using the shutdown command on the SSE card.

1.11.5   Examples

The following example illustrates the shutdown of SSE disk 2.

[local]Redback(config)#card sse 2
[local]Redback(config-card)#shutdown disk 2

1.12   shutdown (Tunnel)

1.12.1   Purpose

Disables a tunnel.

1.12.2   Command Mode

Tunnel configuration

1.12.3   Syntax Description

This command has no keywords or arguments.

1.12.4   Default

All tunnels are disabled.

1.12.5   Usage Guidelines

Use the shutdown command to disable a tunnel. Use this command in tunnel configuration mode to disable a tunnel that you created using the peer-end-point command (in tunnel configuration mode).

Use the no form of this command to enable a tunnel.

1.12.6   Examples

The following example shows how to enable an overlay tunnel:

[local]Redback(config)#tunnel ipv6-manual DenverTn1

[local]Redback(config-tunnel)#no shutdown

1.13   slowsync

1.13.1   Purpose

Configures the SmartEdge router to slowly adjust its local clock rate to compensate for differences with a remote Network Time Protocol (NTP) clock source.

1.13.2   Command Mode

NTP server configuration

1.13.3   Syntax Description

This command has no keywords or arguments.

1.13.4   Default

Gradual adjustment of the local clock rate is disabled.

1.13.5   Usage Guidelines

Use the slowsync command to configure the SmartEdge router to slowly adjust its local clock rate to compensate for differences with a remote NTP clock source.

This command changes the rate of the SmartEdge router clock so that it gradually converges with the NTP server clock.

The NTP daemon adjusts the SmartEdge router clock within a few minutes if the difference between the SmartEdge router clock and the remote NTP server is greater than 5 seconds. This adjustment occurs within the first five minutes after the NTP daemon is started.

Use the no or default form of this command to disable gradual adjustment of the local clock rate.

1.13.6   Examples

The following example shows how to enable the gradual adjustment of the local clock rate:

[local]Redback(config-ntp-server)#slowsync

1.14   snmp alarm delete

1.14.1   Purpose

Deletes active or clear alarm entries.

1.14.2   Command Mode

exec

1.14.3   Syntax Description

1.14.4   Default

None.

1.14.5   Usage Guidelines

Use the snmp alarm delete command to delete entries in the alarmModelTable in ALARM-MIB.

If you use the active keyword you will delete active alarm entries. If you use the clear keyword, you will delete cleared alarm entries.

1.14.6   Example

[local]Redback(config)#snmp alarm delete

1.15   snmp alarm model

1.15.1   Purpose

Creates an entry in the alarmModelTable and configures an alarm model in ALARM-MIB.

1.15.2   Command Mode

Global configuration

1.15.3   Syntax Description

1.15.4   Default

None.

1.15.5   Usage Guidelines

Use the snmp alarm command to create an entry in the alarmModelTable in ALARM-MIB and create SNMP alarm models that allow you to configure how the system communicates certain notification events to allow for more detailed reporting between the SNMP manager and the reporting agent. Alarms are modeled as a series of states which are related using the alarmModelIndex in ALARM-MIB. Alarm states can be modeled using traditional notifications, generic alarm notifications (using the alarmActive State and the alarmClearState notifications defined in ALARM-MIB), or without the use of notifications.

Using the model keyword allows you to enter into the SNMP alarm model command mode in the CLI in order to access the following additional commands you can use to set up an alarm model:

• description
• eventtype
• notify
• probablecause
• res-prefix
• sp-pointer
• vb-index
• vb-subtree

Alarm states modeled using traditional notifications would specify a notification object identifier and optional one of the notification varbinds to identify the state. This alarm state is entered when the generated notification matches this information. The alarm would be added to the active alarm table.

Table 1 describes the values of the state argument. The alarm states are entered in the alarmModelTable in ALARM-MIB after being triggered by an event. The alarm is then added to the active alarm table based on the specified state (for example, if it is a clear event, it will be added to the alarm clear table).

Use the following show commands to display information about SNMP alarm models:

• show snmp alarm model command to display information about each alarm model.
• show snmp alarm active to display information about active alarms.
• show snmp alarm cleared to display information about cleared alarms.
• show snmp alarm stats to display general statistics about active alarms.

Enable debugging for snmp alarm models by using the debug snmp mib alarm command

Use the no form of this command to delete alarm entries.

1.15.6   Examples

The following example shows how to configure link up and link down notifications. The link up notification would be modeled as a clear event, the administrative link down as a warning and an operational link down as critical. The alarmModelTable has entries with the following values:

alarmModelListName		""
alarmModelIndex		3
alarmModelState 		1
alarmModelNotificationId	linkUp
alarmModelVarbindIndex	1
alarmModelVarbindValue	1
alarmModelDescription		"link Up"
alarmModelSpecificPointer	ituAlarmEntry.3.1
alarmModelVarbindSubtree 	ifIndex (1.3.6.1.2.1.2.2.1.1)
alarmModelResourcePrefix	0.0
alarmModelRowStatus		active (1)
ituAlarmEventType		communicationsAlarm (2)
ituAlarmPerceivedSeverity	cleared (1)
ituAlarmGenericModel		alarmModelEntry.0.3.1

alarmModelListName		""
alarmModelIndex		3
alarmModelState 		2
alarmModelNotificationId 	linkDown
alarmModelVarbindIndex	2
alarmModelVarbindValue 	down (2)
alarmModelDescription		"linkDown - administratively"
alarmModelSpecificPointer	ituAlarmEntry.3.6
alarmModelVarbindSubtree	ifIndex (1.3.6.1.2.1.2.2.1.1)
alarmModelResourcePrefix	0.0
alarmModelRowStatus		active (1)
ituAlarmEventType 		communicationsAlarm (2)
ituAlarmPerceivedSeverity 	warning (6)
ituAlarmGenericModel		alarmModelEntry.0.3.2

alarmModelListName		""
alarmModelIndex		3
alarmModelState		3
alarmModelNotificationId	linkDown
alarmModelVarbindIndex	2
alarmModelVarbindValue	up (1)
alarmModelDescription		"linkDown - confirmed problem"
alarmModelSpecificPointer	ituAlarmEntry.3.3
alarmModelVarbindSubtree	ifIndex (1.3.6.1.2.1.2.2.1.1)
alarmModelResourcePrefix 	0.0
alarmModelRowStatus		active (1)
ituAlarmEventType		communicationsAlarm (2)
ituAlarmPerceivedSeverity 	critical (3)
ituAlarmGenericModel		alarmModelEntry.0.3.3

To configure the link up and link down notifications as described above, enter the following in the CLI:

[local]Redback(config)#snmp alarm model 3 state clear 
[local]Redback(config-snmp-alarmmodel)#notify linkup 
[local]Redback(config-snmp-alarmmodel)#vb-index 1 vb-value 1 
[local]Redback(config-snmp-alarmmodel)#description	"link Up"
[local]Redback(config-snmp-alarmmodel)#vb-subtree	ifIndex
[local]Redback(config-snmp-alarmmodel)#sp-pointer ituAlarmEventType.0.3
[local]Redback(config-snmp-alarmmodel)#eventtype	communicationsAlarm
[local]Redback(config-snmp-alarmmodel)#exit 

[local]Redback(config)#snmp alarm model 3 state warning 
[local]Redback(config-snmp-alarmmodel)#notify linkDown  
[local]Redback(config-snmp-alarmmodel)#vb-index 4 vb-value 2 
[local]Redback(config-snmp-alarmmodel)#sp-pointer ituAlarmEventType.0.3
[local]Redback(config-snmp-alarmmodel)#description "linkDown - 
administratively"
[local]Redback(config-snmp-alarmmodel)#vb-subtree	 ifindex
[local]Redback(config-snmp-alarmmodel)#eventtype	communicationsalarm
[local]Redback(config-snmp-alarmmodel)#probablecause 14
[local]Redback(config-snmp-alarmmodel)#exit

[local]Redback(config)#snmp	alarm model 3 state critical 
[local]Redback(config-snmp-alarmmodel)#notify linkDown  
[local]Redback(config-snmp-alarmmodel)#vb-index 4 vb-value 1 
[local]Redback(config-snmp-alarmmodel)#sp-pointer ituAlarmEventType.0.3
[local]Redback(config-snmp-alarmmodel)#description	"linkDown - 
confirmed problem"
[local]Redback(config-snmp-alarmmodel)#vb-subtree	 ifindex
[local]Redback(config-snmp-alarmmodel)#eventType	communicationsalarm
[local]Redback(config-snmp-alarmmodel)#probableCause 8

1.16   snmp community

1.16.1   Purpose

Creates a community string that permits access to Management Information Base (MIB) objects. This command is used for Simple Network Management Protocol (SNMP) version 1 (SNMPv1) and SNMP version 2c (SNMPv2) only.

1.16.2   Command Mode

Global configuration

1.16.3   Syntax Description

1.16.4   Default

The default context is local. The default access is read-only. The default view name is initial.

1.16.5   Usage Guidelines

Use the snmp community command to create a community string that permits access to MIB objects.

Note:  

This command is used with SNMPv1 and SNMPv2 only. You do not need to enable SNMP server capabilities before creating communities.

When you create an SNMP community, it is accessible by both SNMPv1 and SNMPv2 agents. The community string can contain up to 63 characters; the first 28 characters in the string must be unique. You cannot include the @ character in the community name because it is used in generating community names when you specify the all-contexts keyword.

Use the all-contexts keyword to trigger the automatic generation of community names for all managed contexts. This keyword allows you to create a community to support all contexts without having to enter the snmp community command for each context. For example, if a SmartEdge router has three configured contexts (local, aol, and uunet), the snmp community with the Fred all-contexts construct creates the structured community strings Fred@local, Fred@aol, and Fred@uunet.

Use the tag tag-name construct to link one or more SNMP communities to one or more IP addresses and thereby limit access to only the SNMP messages from those IP addresses.

The treatment of Border Gateway Protocol (BGP) peer up and peer down traps (bgpBackwardTransNotification and bgpEstablishedNotification) differs from the treatment of other context-specific traps:

• For BGP peer up and peer down traps:

  • If you specify the all-contexts keyword, the system reports traps from all contexts.
  • If you specify the context ctx-name construct, the system reports traps originating from the specified context.
  • If you specify neither the all-contexts keyword nor context ctx-name construct, the system reports only traps from the local context.
• For all other context-specific traps, the system reports traps from all contexts, regardless of whether the all-contexts keyword or context ctx-name construct is used.

Use the no form of this command to remove a community string.

1.16.6   Examples

The following command shows how to grant the public community read-only access to the MIB objects in the generic view, and trigger the automatic generation of community strings for the local context:

[local]Redback(config)#snmp community public view generic

1.17   snmp engine-id

1.17.1   Purpose

Specifies a unique engine ID for the Simple Network Management Protocol (SNMP) Version 3 (SNMPv3) local or remote systems.

1.17.2   Command Mode

Global configuration

1.17.3   Syntax Description

1.17.4   Default

The SNMP engine ID is a 24-character string consisting of the Redback Networks Enterprise Management Information Base (MIB) OID and the management port medium access control (MAC) address.

1.17.5   Usage Guidelines

Use the snmp engine-id command to specify a unique engine ID for SNMPv3.

Note:  

This command is used with SNMPv3 only. No equivalent exists for SNMP Version 1 (SNMPv1) or SNMP Version 2c (SNMPv2). You must enable the SNMP server using the snmp server command in global configuration mode before you can specify the engine ID.

Use the no form of this command to delete the remote engine ID. The local engine ID cannot be deleted.

Use the default form of this command to set the engine ID to the default value.

Note:  

It is recommended that you enable the SNMP server using the snmp server command (in global configuration mode) before you configure the engine ID, although it is not required. The recommended sequence of configuration tasks is described in Configure SNMPv3.

1.17.6   Examples

The following example specifies an engine ID of 01:02:03:04:ab:cd:

[local]Redback(config)#snmp engine-ID local 01:02:03:04:ab:cd

1.18   snmp group

1.18.1   Purpose

Creates a Simple Network Management Protocol (SNMP) Version 3 (SNMPv3) group.

1.18.2   Command Mode

Global configuration

1.18.3   Syntax Description

1.18.4   Default

A group, “initial”, is automatically created if needed (for instance, if the snmp user command is used in global configuration mode without specifying a group). This group uses the user security model with the noauth security level, and allows read access to the view, “restricted”. No write-view or notify-view is automatically defined. If the security-model keyword is not specified, the security model is usm and the security level is noauth.

1.18.5   Usage Guidelines

Use the snmp group command to create an SNMPv3 group.

Note:  

This command is used only with SNMPv3 to define access parameters for an SNMP group. You must enable the SNMP server using the snmp server command in global configuration mode before you can configure SNMP groups. For SNMP versions 1 and 2c, use the snmp community command (in global configuration mode).

Use the no form of this command to delete an SNMP group. If not specified in the no form of this command, optional parameters are set to their default values.

1.18.6   Examples

The following command shows how to create an SNMP group, Admin, that provides authorized read and modify access to the MIB objects defined in a view, Admin-View:

[local]Redback(config)#snmp group Admin security-model usm auth context
 local read Admin-View write Admin-View

1.19   snmp notify

1.19.1   Purpose

Defines a Simple Network Management Protocol (SNMP) notification entry and associates a tag name with the entry.

1.19.2   Command Mode

Global configuration

1.19.3   Syntax Description

1.19.4   Default

The notification type is trap.

1.19.5   Usage Guidelines

Use the snmp notify command to define an SNMP notification entry and to associate a tag name with the entry.

You must enable the SNMP server using the snmp server command (in global configuration mode) before you use this command.

Use this command in conjunction with the snmp notify-target command (in global configuration mode), which references the tag-name argument.

Use the no form of this command to remove a notification entry and tag name from the configuration.

1.19.6   Examples

The following example defines a notify entry with the notify and tag names both set to V3Traps:

[local]Redback(config)#snmp notify V3Traps V3Traps trap

1.20   snmp notify-filter

1.20.1   Purpose

Creates a Simple Network Management Protocol (SNMP) notify filter that includes or excludes specific notifications.

1.20.2   Command Mode

Global configuration

1.20.3   Syntax Description

1.20.4   Default

None

1.20.5   Usage Guidelines

Use the snmp notify-filter command to create an SNMP notify filter that includes or excludes specific notifications.

Note:  

You must enable the SNMP server using the snmp server command (in global configuration mode) before configuring a notify filter.

Use this command in conjunction with the snmp notify-target command (in global configuration mode), which references the filter-name argument.

Use the no form of this command to remove the specified notify filter from the configuration.

1.20.6   Examples

The following example displays the notify filter, F-NO-rpMau, excluding the rpMauNotifications notifications:

[local]Redback(config)#snmp notify-filter F-NO-rpMau rpMauNotifications excluded

1.21   snmp notify-target

1.21.1   Purpose

Configures the Simple Network Management Protocol (SNMP) target management station, which receives SNMP notifications.

1.21.2   Command Mode

Global configuration

1.21.3   Syntax Description

1.21.4   Default

The UDP port is 162. The context is local. The timeout value is five seconds. The number of retries is two.

1.21.5   Usage Guidelines

Use the snmp notify-target command to configure the SNMP target management station, which receives SNMP notifications.

Note:  

You must enable the SNMP server using the snmp server command (in global configuration mode) before you can configure the target management station.

The snmp target and the snmp notify-target commands are mutually exclusive. The snmp target command sets certain parameters to their default values; these parameters are notifyName, targParmName, tag, tagList, seconds, and count.

The snmp target command (in global configuration mode) is equivalent to the set of snmp notify-target, snmp notify, snmp target-parameters, and snmp group (only if the notify notify-view construct has not been set) commands.

Before specifying the notify-target-name argument, you must first create the name using the snmp notify command. You must enable the SNMP server using the snmp server command (in global configuration mode) before you can configure the target management station. Before specifying the parameters target-parameters construct, you must first create the name using the snmp target-parameters command (in global configuration mode). You must enable the SNMP server using the snmp server command (in global configuration mode) before you can configure the target management station. Before specifying the filter-name argument, you must first create the name using the snmp notify-filter command (in global configuration mode).

Use the no form of this command to remove a target from the configuration.

1.21.6   Examples

The following command configures the system to send notifications to a target, Nm-Station1, IP address 10.3.4.5, using the tag Inet-Informs, parameters, Param2, and notify filter, F-NO-rpMau:

[local]Redback(config)#snmp notify-target Nm-Station1 10.3.4.5 tag 
Inet-Informs parameters Param2 filter F-NO-rpMau

1.22   snmp ping

1.22.1   Purpose

Schedules an IPv4 ping test.

1.22.2   Command Mode

Context configuration

1.22.3   Syntax Description

1.22.4   Default

1.22.5   Usage Guidelines

Use the snmp ping command to schedule an IPv4 ping test. This configuration is saved across system reloads and XCRP switchovers. Ping tests will not be scheduled if the SNMP server is not configured.

See the ping command and RFC 4560 for additional information on the options available with the ping command.

Use the show snmp ping command to view the scheduled test results.

1.22.6   Examples

The following command shows how to enable an snmp ping test with the name test on the server100 host. The test ping sends a packet size of 32 bytes to the server every 30 seconds and sends a notification to the SNMP server when it is complete:

[local]Redback(config)#snmp ping test ip server100 frequency 30 
notify-complete size 32

The following command enables an snmp ping test with the name test on the server100 host. The test ping sends a packet size of 32 bytes to the server every 30 seconds and sends a notification to the SNMP server when it is complete:

[local]Redback#config

[local]Redback(config)#context local

[local]Redback(config-ctx)#snmp ping ping_name ip www.ericsson.com

1.23   snmp server

1.23.1   Purpose

Enables the Simple Network Management Protocol (SNMP) server for SNMP Version 1 (SNMPv1), SNMP Version 2c (SNMPv2), and SNMP Version 3 (SNMPv3), and enters SNMP server configuration mode.

1.23.2   Command Mode

Global configuration

1.23.3   Syntax Description

1.23.4   Default

SNMP server capabilities are disabled. The default port is 161.

1.23.5   Usage Guidelines

Use the snmp server command to enable the SNMP server. This command enables the protocol engines for all supported versions of SNMP.

Use the enhance ifmib keyword to add the following functions to the IF-MIB:

• Supports Asynchronous Transfer Mode (ATM), Frame Relay, and 802.1Q permanent virtual circuits (PVCs)
• Supports ATM operations, administration, and management (OAM) trap notifications when the state of an ATM PVC transitions as a result of the OAM function
• Sets the IF-MIB object, ifDescr equal, to ifName
• Supports the IF-MIB objects, ifHCInOctets and ifHCOutOctets, wherever ifInOctets and ifOutoctets are supported
• Supports quality of service (QoS) transmit counters for each queue for each circuit and port for all line cards
• To display aggregate traffic counter and link group hierarchical structure information for circuits.

Use the no form of this command to disable the SNMP server.

Note:  

You must enter the snmp server and no snmp server commands in separate transactions for both to take effect. Within a single transaction, entering the snmp server command, followed by the no snmp server command, simply enables the server without then disabling it. Similarly, entering the no snmp server command, followed in the same transaction by the snmp server command, disables the server without then re-enabling it. To terminate the current transaction, enter the commit command (in global configuration mode) before you can configure the target management station. Then enter the form of the snmp server command as required. For more information on the commit command, see Using the CLI.

1.23.6   Examples

The following command shows how to enable the SNMP server on the default User Datagram Protocol (UDP) port (161):

[local]Redback(config)#snmp server

1.24   snmp target

1.24.1   Purpose

Configures the SNMP notifications sent to the SNMP target management station.

1.24.2   Command Mode

Global configuration

1.24.3   Syntax Description

1.24.4   Default

The SNMP version is version 2c. The notification view created by the system is restricted. The notification type is trap. The port is 162.

1.24.5   Usage Guidelines

Use the snmp target command to configure the SNMP notifications sent to the SNMP target management station.

The snmp target and the snmp notify-target commands are mutually exclusive.

The snmp target command sets certain parameters to their default values; these parameters are notifyName, targParmName, tag, tagList, seconds, and count. It is equivalent to the set of snmp notify-target, snmp notify, snmp target-parameters, and snmp group commands (only if the notify notify-view construct has not been set).

Use the no form of this command to remove an SNMP target.

Note:  

SNMPv2 and SNMPv3 support both the inform and trap keywords, but SNMPv1 supports only the trap keyword.

1.24.6   Examples

The following example creates an SNMP target, NM-Station1, at IP address, 198.164.190.110, to receive SNMPv2 and SNMPv3 traps from the view, InetView, using a community name of Admin:

[local]Redback(config)#snmp target NM-Station1 198.164.190.110 
security-name Admin version 2c view InetView trap

1.25   snmp target-parameters

1.25.1   Purpose

Configures the security name and optionally the Simple Network Management Protocol (SNMP) version and security level used in notifications sent to the SNMP target management station.

1.25.2   Command Mode

Global configuration

1.25.3   Syntax Description

1.25.4   Default

None

1.25.5   Usage Guidelines

Use the snmp target-parameters command to configure the security name and optionally the SNMP version and security level used in notifications sent to the SNMP target management station.

Note:  

You must enable the SNMP server using the snmp server command (in global configuration mode) before you can configure target parameters.

Use this command in conjunction with the snmp notify-target command (in global configuration mode).

For the auth, noauth, and priv keywords, no authorization is provided in SNMPv1 and SNMPv2. You must specify the noauth keyword for SNMPv1 and SNMPv2. For SNMPv3, you can specify any of the three keywords. Enforcing either the optional auth or priv keyword applies authorization or privacy support to the designated SNMP target; use the optional noauth keyword to apply neither authorization nor privacy support.

Use the no form of this command to remove the specified target parameter information from the configuration.

1.25.6   Examples

The following command configures a set of parameters, Param2, that includes the security name, ADMIN, and specifies the SNMPv3 protocol using authorization:

[local]Redback(config)#snmp target-parameters Param2 security-name ADMIN version 3 security-level auth 

1.26   snmp traceroute

1.26.1   Purpose

Configures SNMP traceroute tests.

1.26.2   Command Mode

Context configuration

1.26.3   Syntax Description

1.26.4   Default

1.26.5   Usage Guidelines

Users are able to configure SNMP traceroute notifications (RFC-4560) by enabling the notification control options. SNMP traceroute test configurations are persistent across node reload or switchover. When using the CLI to create traceroute tests, configurations are automatically saved in reliability data bases (RDB). When using SNMP set requests to create traceroute tests, users can set the storage type (volatile or non-volatile) that they would like to use.

1.26.6   Examples

The following command configures a basic SNMP traceroute test for traceroute-test-name sample-test on ip-addr 192.168.0.1 using all default values.

[local]Redback(config-ctx)#snmp traceroute sample-test ip 192.168.0.1

1.27   snmp trap

1.27.1   Purpose

Enables SNMP trap notifications for cross-connect (pseudowire) state change events per Layer 2 virtual private network (L2VPN) profile or virtual private LAN services (VPLS) profile.

1.27.2   Command Mode

L2VPN cross-connect profile peer

VPLS profile neighbor

1.27.3   Syntax Description

This command has no keywords or arguments.

1.27.4   Default

SNMP trap notifications are not sent by default.

1.27.5   Usage Guidelines

Use the snmp trap command to enable SNMP trap notifications for cross-connect state change events per L2VPN or VPLS profile.

1.27.6   Examples

The following example shows how to enable SNMP trap notifications for cross-connect state change events associated with the L2VPN profile named l2vpn-customerA-profile:

[local]Redback(config)#l2vpn profile l2vpn-customerA-profile
[local]Redback(config-l2vpn-xc-profile)#peer 10.12.34.55
[local]Redback(config-l2vpn-xc-profile-peer)#snmp trap

The following example shows how to enable SNMP trap notifications for cross-connect state change events associated with the VPLS profile named vpls-customerB-profile:

[local]Redback(config)#vpls profile vpls-customerB-profile
[local]Redback(config-vpls-profile)#neighbor 10.12.34.55
[local]Redback(config-vpls-profile-neighbor)#snmp trap

1.28   snmp traps

1.28.1   Purpose

Enables or disables SNMP trap notifications for NetOp™ EMS.

1.28.2   Command Mode

NetOp configuration

1.28.3   Syntax Description

This command has no keywords or arguments.

1.28.4   Default

The system forwards SNMP trap information to NetOp EMS by default.

1.28.5   Usage Guidelines

Use the snmp traps command to forward SNMP trap information to NetOp EMS. Use the no snmp traps command to suppress the forwarding of SNMP trap information to NetOp EMS. Use the show netop command to view this configuration information in the SmartEdge router CLI.

1.28.6   Examples

The following example shows how to stop forwarding SNMP trap information to NetOp EMS:

[local]Redback(config-netop)#no snmp traps

[local]Redback(config-netop)#

1.29   snmp traps [ospf-traps]

1.29.1   Purpose

Enables or disables one or more OSPF-TRAP-MIB notifications.

1.29.2   Command Mode

OSPF configuration

1.29.3   Syntax Description

1.29.4   Default

The system enables the OSPF-MIB IfStateChange, VirtIfStateChange, NbrStateChange, and VirtNbrStateChange notifications by default.

1.29.5   Usage Guidelines

Use this command to allow you to enable or disable each OSPF-TRAP-MIB notification in router ospf mode. The snmp traps command enables the OSPF-TRAP-MIB notification you specify from Table 4. Use the default keyword with this command to enable the IfStateChange, VirtIfStateChange, NbrStateChange, and VirtNbrStateChange notifications.

Use the no snmp traps form of this command to disable all OSPF-MIB notifications.

The following table describes the OSPF traps and the keywords that enable them in this command.

1.29.6   Examples

The following examples shows how to enable the TxReTransmit notification for OSPF-TRAP-MIB:

[local]jazz(config-ospf)#snmp traps txretransmit

[local]jazz(config-ospf)#

1.30   snmp user

1.30.1   Purpose

Configures a Simple Management Network Protocol (SNMP) version 3 (SNMPv3) user.

1.30.2   Command Mode

Global configuration

1.30.3   Syntax Description

1.30.4   Default

The default security model is USM with no authentication.

1.30.5   Usage Guidelines

Use the snmp user command to configure an SNMPv3 user. You must first enable the SNMP server using the snmp server command (in global configuration mode) before configuring a user.

Use the no form of this command to remove an SNMP user.

1.30.6   Examples

The following command creates an SNMP user, Admin, that is part of the group, Group4, and uses MD5 authentication with the password xyzzy, and an optional des56 password, loopy:

[local]Redback(config)#snmp group Group4 all-contexts read all write all security-model usm priv
[local]Redback(config)#snmp user Admin group Group4 security-model usm md5 password md5_password des56 des56_password

Note:  

The command snmp user security-model needs to match the group security-model. In this example, the option priv in the user group, therefore; the SNMP user must specify the authentication type and password and the data encryption (des56) password.

1.31   snmp version

1.31.1   Purpose

Specifies the version of the Simple Network Management Protocol (SNMP) traps that the NetOp Element Management System (EMS) server receives.

1.31.2   Command Mode

NetOp configuration

1.31.3   Syntax Description

1.31.4   Default

SNMPv2c traps are sent to the NetOp EMS server.

1.31.5   Usage Guidelines

Use the snmp version command to specify the version of SNMP traps that the SmartEdge router sends to the NetOp EMS server.

Use the no form of this command to specify the default.

Note:  

You must configure the SNMP community before you specify the version of the SNMP traps sent to the NetOp EMS server.

1.31.6   Examples

The following example configures the SmartEdge router to send SNMPv1 traps to the NetOp EMS server:

[local]Redback(config)#netop

[local]Redback(config-netop)#snmp version 1

1.32   snmp view

1.32.1   Purpose

Defines a Simple Network Management Protocol (SNMP) Management Information Base (MIB) view.

1.32.2   Command Mode

Global configuration

1.32.3   Syntax Description

1.32.4   Default

A default view, “restricted”, is enabled when it is referenced by a user creating a community without a specific view. This view provides access to the following MIB groups: system, snmp, snmpEngine, and snmpMPDStats.

1.32.5   Usage Guidelines

Use the snmp view command to define an SNMP MIB view. MIB views control which SNMP communities have access to specific MIB objects.

Use the no form of this command to remove the specified MIB view entry.

1.32.6   Examples

The following example shows how to create a view that includes all objects in the Internet subtree:

[local]Redback(config)#snmp view everything internet included

The following example shows how to create a view that includes only the system group and the interface MIB objects for the port with a value of 6:

[local]Redback(config)#snmp view port6 system include

[local]Redback(config)#snmp view port6 ifEntry.*.6 included

1.33   software license

1.33.1   Purpose

Enables software licensing and accesses software license configuration mode.

1.33.2   Command Mode

Global configuration

1.33.3   Syntax Description

This command has no keywords or arguments.

1.33.4   Default

No software licensed features or functions are enabled.

1.33.5   Usage Guidelines

Use the software license command to enable software licensing and access software license configuration mode.

Use the no or default form to disable software licensing and remove any existing licenses.

1.33.6   Examples

The following example shows how to enable software licensing and accesses software license configuration mode:

[local]Redback(config)#software license

[local]Redback(config-license)#

1.34   source

1.34.1   Purpose

Configures the source IP address and port number to put into the NetFlow packet for a NAT logging profile.

1.34.2   Command Mode

NAT Logging Profile

1.34.3   Syntax

1.34.4   Usage Guidelines

Use the source command to configure the source IP address to put into the NetFlow packet and that the port number is the L4 port for a NAT logging profile.

Use the no form of this command to delete the source IP address value and port number.

For more information about how to configure NAT logging, see nat logging-profile and Configure an Enhanced NAT Policy with Logging and Paired Mode.

1.34.5   Example

	[local]Ericsson#configuration     <-
	Enter configuration commands, one per line, 'end' to exit
	[local]Ericsson(config)#context nat-context
	[local]Ericsson(config-ctx)#nat logging-profile nat-log-profile
	[local]Ericsson(config-nat-profile)#source 10.10.10.1 port 4242

1.35   source-address

1.35.1   Purpose

Configures the packet source IP address value for a dynamically verified static routing (DVSR) profile.

1.35.2   Command Mode

DVSR profile configuration

1.35.3   Syntax Description

1.35.4   Default

Source IP address is not set.

1.35.5   Usage Guidelines

Use the source-address command to configure the packet source IP address value for a DVSR profile. Because some routers can only recognize the stable address of a router, such as the loopback address, you must configure the source IP address to ensure that the verified host has the route to reach the routers.

Use the no or default form of this command to delete the packet source IP address value from a DVSR profile.

1.35.6   Examples

The following example defines a DVSR profile source address of 10.1.1.1:

[local]Redback(config-ctx)#dvsr-profile abc-webfarm

[local]Redback(config-dvsr)#source-address 10.1.1.1

1.36   source-path

1.36.1   Purpose

Assigns a configured explicit route to a label-switched path (LSP).

1.36.2   Command Mode

RSVP LSP configuration

1.36.3   Syntax Description

1.36.4   Default

None

1.36.5   Usage Guidelines

Use the source-path command to assign a configured explicit route to an LSP.

Before you can assign a source path to an LSP, you must configure an explicit route to use as the source path. Use the explicit-route command in RSVP router configuration mode to indicate a list of specific hops through a network, and then use the source-path command to assign that explicit route to your LSP.

Use the no form of this command to remove an explicit route from an LSP.

1.36.6   Examples

The following example shows how to assign the explicit route ER03 as the source path for the LSP, Prod23:

[local]Redback(config-ctx)#router rsvp

[local]Redback(config-rsvp)#lsp Prod23

[local]Redback(config-rsvp-lsp)#source-path ER03

1.37   spanning-tree (bridge)

1.37.1   Purpose

Enables the Rapid Spanning Tree Protocol (RSTP) for the current bridge or bridged VPLS pseudowire and enters the spanning-tree configuration mode.

1.37.2   Command Mode

• Bridge configuration
• VPLS neighbor configuration

1.37.3   Syntax Description

This command has no keywords or arguments.

1.37.4   Default

RSTP is not enabled.

1.37.5   Usage Guidelines

Use this command to enable RSTP for the current bridge or VPLS pseudowire and enter spanning-tree configuration mode. RSTP is not supported on ATM.

Use the no form of this command to disable RSTP for the current bridge.

1.37.6   Examples

The following example illustrates the context-specific RSTP commands and the spanning-tree configuration mode:

[local]jeudi.lab(config)#context isp4
[local]jeudi.lab(config-ctx)#bridge grp1
[local]jeudi.lab(config-bridge)#spanning-tree
[local]jeudi.lab(config-bridge-stp)#?

1.38   spanning-tree profile

1.38.1   Purpose

In global configuration mode, enables the configuration of Rapid Spanning Tree Protocol (RSTP) attributes. In other modes, assigns a spanning-tree profile to a circuit, port, or VPLS pseudowire.

1.38.2   Command Mode

• dot1q PVC configuration
• Global configuration
• Port configuration
• Link group configuration
• VPLS profile neighbor configuration

1.38.3   Syntax Description

1.38.4   Default

Spanning-tree profile attributes are set to their default values.

1.38.5   Usage Guidelines

Use the spanning-tree profile command to enable the configuration of RSTP attributes (global configuration mode). In other modes, use the command to assign a spanning-tree profile to a circuit, port, or VPLS pseudowire.

To configure the spanning-tree profile attributes or create a spanning-tree profile, enter the spanning-tree profile command in global configuration mode.

To assign the spanning-tree profile attributes to a 801.1Q permanent virtual circuit (PVC) or to a port, enter the spanning-tree profile command in 802.1Q PVC and port configuration modes, respectively.

Use the no form of this command (global configuration mode) to delete a spanning-tree profile.

1.38.6   Examples

The following example illustrates how the spanning-tree profile command creates the spanning-tree profile womp:

[local]Redback(config)#spanning-tree profile womp

1.39   speed (DS-1)

1.39.1   Purpose

Sets the speed for all DS-0 channels in a DS-1 channel on a channelized DS-3 channel or port.

1.39.2   Command Mode

DS-1 configuration

1.39.3   Syntax Description

1.39.4   Default

The default value is 64 kbps.

1.39.5   Usage Guidelines

Use the speed command to set the speed for all DS-0 channels in a DS-1 channel on a channelized DS-3 channel or port.

Use the default form of this command to set the speed for all DS-0 channels in a DS-1 channel to the default speed.

1.39.6   Examples

The following example shows how to set the DS-0 channel speed to 56 kbps:

[local]Redback(config-ds1)#speed 56

1.40   speed (port)

1.40.1   Purpose

Specifies the speed of the SmartEdge 100 native or Gigabit Ethernet (GE) copper-based port if auto-negotiation is disabled.

1.40.2   Command Mode

Port configuration

1.40.3   Syntax Description

1.40.4   Default

The speed of the port is 1000 Mbps.

1.40.5   Usage Guidelines

Use the speed command to specify the speed of the SmartEdge 100 native or GE copper-based port if auto-negotiation is disabled. If auto-negotiation is enabled, this command is ignored.

To specify the copper interface for this port, use the medium-type command (in port configuration mode). To set the mode for this port, use the duplex command (in port configuration mode).

This command does not apply to GE ports on any other SmartEdge router or to any Fast Ethernet (FE) port on any SmartEdge router. To set the speed of an FE port, use the medium command (in port configuration mode).

Use the no or default form of this command to set the port speed to the default condition.

1.40.6   Examples

The following example sets the speed of a SmartEdge 100 native port 1 to 100 Mbps:

[local]Redback(config)#port ethernet 2/1

[local]Redback(config)#speed 100

1.41   spf holddown

1.41.1   Purpose

Modifies the delay time between an event that triggers a Shortest Path First (SPF) calculation and the calculation itself.

1.41.2   Command Mode

IS-IS router configuration

1.41.3   Syntax Description

1.41.4   Default

The SPF holddown is 5 seconds. When you enter this command without specifying level-1 or level-2 routing, SPF holddown value is the same for both level 1 and level 2.

1.41.5   Usage Guidelines

When fast convergence is not enabled, the spf holddown command modifies the delay time between an event that triggers an SPF calculation and the calculation itself. This delay capitalizes on the fact that computation triggers, such as new link-state protocol data units (LSPs), tend to occur in bursts. Starting the computation after the first event would cause another computation to be scheduled immediately after that due to further events.

When fast convergence is enabled, the holddown time acts as a window within which a specified number of SPFs are run. Because SPF calculations are performed when the topology changes, increasing this value reduces CPU usage, especially in large topologies, but slows the convergence of the network.

Use the no form of this command to restore the default delay value.

1.41.6   Examples

The following example shows how to set the delay between the event that triggers an SPF calculation and the calculation itself to 20 seconds for level-1 routing:

[local]Redback(config-ctx)#router isis isis1

[local]Redback(config-isis)#spf holddown 20 level-1

1.42   spf interval

1.42.1   Purpose

Configures the minimum interval between Shortest Path First (SPF) calculations.

1.42.2   Command Mode

IS-IS router configuration

1.42.3   Syntax Description

1.42.4   Default

The SPF interval is 10 seconds. When you enter this command without specifying level-1 or level-2 routing, the same SPF interval is used for both levels.

1.42.5   Usage Guidelines

Use the spf interval command to configure the minimum interval between SPF calculations.

Because SPF calculations are performed when the topology changes, increasing this value reduces CPU usage, especially in large topologies, but slows the convergence of the network.

Note:  

The spf interval command has no effect when fast convergence is enabled.

Use the no form of this command to restore the default SPF interval.

1.42.6   Examples

The following example shows how to set the minimum time between SPF calculations to 25 seconds:

[local]Redback(config-ctx)#router isis isis1

[local]Redback(config-isis)#spf interval 25

1.43   spf-timers

1.43.1   Purpose

Configures the delay time between the receipt of a topology change and the start of the Shortest Path First (SPF) calculation, and to configure the hold time between two consecutive SPF calculations.

1.43.2   Command Mode

• OSPF router configuration
• OSPF3 router configuration

1.43.3   Syntax Description

1.43.4   Default

The delay is 5 seconds. The hold time is 10 seconds.

1.43.5   Usage Guidelines

Use the spf-timers to configure the delay time between the receipt of a topology change and the start of the SPF calculation, and to configure the hold time between two consecutive SPF calculations. Setting the delay and hold time to a low value enables faster switching to an alternate path in the event of failure. However, it also consumes more CPU processing time.

Use the spf-timers 0 0 command to enable OSPF fast convergence. With OSPF fast convergence, route recalculation occurs as soon as new events arise.

Use the no or default form of this command to return the delay and hold time values to their default values.

1.43.6   Examples

The following example shows how to set the SPF delay and hold time to 2 and 5:

[local]Redback#config

[local]Redback(config)#context local

[local]Redback(config-ctx)#router ospf 1

[local]Redback(config-ospf)#spf-timers 2 5

[local]Redback(config-ospf)#

1.44   spi

1.44.1   Purpose

Specifies a security parameter index (SPI) for this key chain.

1.44.2   Command Mode

Key chain configuration

1.44.3   Syntax Description

1.44.4   Default

None

1.44.5   Usage Guidelines

Use the spi command to specify an SPI for this key chain. Use the in and out keywords to limit the SPI number to incoming or outgoing packets, respectively. If you do not specify the direction, the SPI is assigned to both incoming and outgoing traffic.

Use the no form of this command to remove the SPI from the key chain.

1.44.6   Examples

The following example shows how to assign an SPI number of 256 to incoming traffic:

[local]Redback(config-ctx)#key-chain key-in key-id 101

[local]Redback(config-key-chain)#spi in 256

1.45   split-horizon

1.45.1   Purpose

Enables Routing Information Protocol (RIP) or RIP next generation (RIPng) split-horizon processing on the specified interface.

1.45.2   Command Mode

• RIP interface configuration
• RIPng interface configuration

1.45.3   Syntax Description

1.45.4   Default

Simple split-horizon processing is enabled.

1.45.5   Usage Guidelines

Use the split-horizon command to enable RIP or RIPng split-horizon processing on the specified interface.

Split-horizon processing prevents routing loops in distance-vector routing protocols. When simple split-horizon is enabled, it blocks route information from being advertised out any interface from which the information originated. The split-horizon mechanism is intended to speed up convergence after a link failure.

Split-horizon processing with poisonous reverse can break the loops more quickly by advertising routes with metric infinity (16) to the link from which they are learned.

Note:  

This command does not apply to loopback interfaces.

Use the no or default form of this command to disable split-horizon processing on the specified interface.

1.45.6   Examples

The following example shows how to disable split-horizon processing on the fe01 interface:

[local]Redback(config-ctx)#router rip rip002

[local]Redback(config-rip)#interface fe01

[local]Redback(config-rip-if)#no split-horizon

1.46   sp-pointer

1.46.1   Purpose

Identifies the value of the OID of the first accessible object in the corresponding model-specific MIB definition.

1.46.2   Command Mode

SNMP alarm model configuration

1.46.3   Syntax Description

1.46.4   Default

None

1.46.5   Usage Guidelines

Use the sp-pointer command to identify value of the OID of the first accessible object in the corresponding model-specific MIB definition.

Use the no form of this command to remove the value of the OID of the first accessible object in the corresponding model-specific MIB definition.

1.46.6   Examples

The following example shows how to name the ituAlarmEventType.0.3 OID as the value of the OID of the first accessible object in the corresponding model-specific MIB definition.

[local]jazz#config
[local]jazz(config)#snmp alarm model 1 state clear
[local]jazz(config-snmp-alarmmodel)#sp-pointer ituAlarmEventType.0.3
[local]jazz(config-snmp-alarmmodel)#

1.47   sse group

1.47.1   Command Mode

Global configuration

1.47.2   Syntax Description

1.47.3   Default

No SSE group is configured.

1.47.4   Usage Guidelines

Creates an SSE group. Redundancy settings using the network-redundant [raid-0] or disk-redundant keywords must be configured when you first provision an SSE group.

If network redundancy is configured, up to two SSE cards can be assigned to a group. If disk redundancy is configured, only one SSE card can be assigned to a group. The raid-0 keyword specifies that both disks on each SSE card are used to form a RAID 0 hard disk; if not specified, the SSE disks operate independently.

An SSE group can only be deprovisioned if no card is bound to it.

1.47.5   Examples

The following examples shows how to create an SSE group.

[local]Redback(config)#sse group sse_group_1 network-redundant

1.48   sse group switch-over

1.48.1   Command Mode

exec

1.48.2   Syntax Description

1.48.3   Default

The SSE group uses the active SSE card or SSE disk.

1.48.4   Usage Guidelines

Performs a manual switchover on an SSE group configured with redundancy to the standby SSE card or SSE disk. The standby SSE card or SSE disk must be available.

Use the show sse group detail command to view switchover status and notification of switchover failure.

1.48.5   Examples

[local]Redback#sse group switch-over sse_group_1

1.49   ssh

1.49.1   Purpose

Establishes a Secure Shell (SSH) session from the SmartEdge router to a host using SSH.

1.49.2   Command Mode

exec

1.49.3   Syntax Description

1.49.4   Default

The session uses SSH Version 1 with Triple Data Encryption Standard (3DES) encryption.

1.49.5   Usage Guidelines

Use the ssh command to establish a SSH session from the SmartEdge router to a host using SSH. You can use the hostname argument only if DNS is enabled using the ip domain-lookup, ip domain-name, and ip name-servers commands (in context configuration mode). For more information about these commands, see the Command List.

Table 4-2 lists the keywords for the optional cipher name construct.

1.49.6   Examples

The following example shows how to establish an SSH session with a host at IP address, 192.168.190.32:

[local]Redback>ssh 192.168.190.32

1.50   ssh server full-drop

1.50.1   Purpose

Specifies the maximum number of concurrent Secure Shell (SSH) sessions permitted on the system.

1.50.2   Command Mode

Global configuration

1.50.3   Syntax Description

1.50.4   Default

A maximum of 16 concurrent SSH sessions is permitted on the system.

1.50.5   Usage Guidelines

Use the ssh server full-drop command to specify the maximum number of concurrent SSH sessions permitted on the system. The system drops all SSH connection requests after the maximum number of concurrent sessions is established.

The SmartEdge router supports up to 32 concurrent administrative sessions (Telnet and SSH) plus one connection to the console port. If the number of concurrent SSH sessions reaches the maximum set by this command, the remaining administrative sessions must be Telnet sessions.

While this command specifies a global system-wide limit to the number of SSH administrative sessions, you can also specify context-specific maximums for administrative sessions (Telnet and SSH) in one or more contexts, using the aaa authentication administrator command (in context configuration mode) with the maximum sessions num-sess construct. The number of concurrent Telnet and SSH sessions is governed by the configuration of context-specific limits as follows:

• Within a context, if the maximum number of permitted administrative sessions is larger than the maximum number of globally permitted SSH sessions, the remaining sessions (num-sess–max-num) for that context must be Telnet sessions.
• Within the system, the maximum number of concurrent sessions permitted is either 32 or the sum of all sessions permitted for each context, whichever is smaller. If the maximum number of concurrent sessions permitted on the system is greater than the maximum number of permitted SSH sessions, the remaining sessions must be Telnet sessions.

Use the default form of this command to return an attribute to the default value.

1.50.6   Examples

The following example shows how to limit the number of concurrent SSH sessions on the system to 10. It limits the maximum number of concurrent administrative sessions in the local context to 10 and in the isp1 context to 2:

[local]Redback(config)#ssh server full-drop 10

[local]Redback(config)#context local

[local]Redback(config-ctx)#aaa authentication administrator maximum 
sessions 10

[local]Redback(config)#context isp1

[local]Redback(config-ctx)#aaa authentication administrator maximum 
sessions 2

As a result, there can be no more than 12 concurrent administrative sessions on the system and at least two of them must be Telnet sessions.

1.51   ssh server-keygen

1.51.1   Purpose

Generates a new Secure Shell (SSH) key on the system.

1.51.2   Command Mode

exec

1.51.3   Syntax Description

This command has no keywords or arguments.

1.51.4   Default

None

1.51.5   Usage Guidelines

Use the ssh server-keygen command to generate a new SSH key on the system. If a key already exists, the existing key is replaced.

1.51.6   Examples

The following example enables SSH on the system:

[local]Redback>ssh server-keygen

1.52   ssh server rate-drop

1.52.1   Purpose

Specifies the rate at which the system drops Secure Shell (SSH) connection requests when the start drop value has been reached.

1.52.2   Command Mode

Global configuration

1.52.3   Syntax Description

1.52.4   Default

The drop value is 100%.

1.52.5   Usage Guidelines

Use the ssh server rate-drop command to specify the rate at which the system drops SSH connection requests when the start drop value has been reached.

This command is used in conjunction with the ssh server full-drop and ssh server start-drop commands (in global configuration mode) to instruct the system how to handle incoming SSH connection requests. After the number of sessions established on the system equals the number configured for the ssh server start-drop value, the system drops incoming SSH connection requests at the value specified by the ssh server rate-drop command.

Use the default form of this command to return an attribute to the default value.

1.52.6   Examples

The following example shows how to configure the maximum number of SSH sessions to the system to 10; the starting drop number to 5, and the drop value to 50. With this configuration, the system establishes the first five SSH sessions. The system then drops 50% (or one out of every two) subsequent connection requests until ten concurrent sessions are established. The system does not accept any additional SSH connections after ten concurrent SSH sessions are established:

[local]Redback(config)#ssh server start-drop 5
[local]Redback(config)#ssh server rate-drop 50
[local]Redback(config)#ssh server full-drop 10

1.53   ssh server start-drop

1.53.1   Purpose

Configures the number of Secure Shell (SSH) connections after which the system can start to drop connection requests.

1.53.2   Command Mode

Global configuration

1.53.3   Syntax Description

1.53.4   Default

The system drops connections after 16 concurrent sessions.

1.53.5   Usage Guidelines

Use the ssh server start-drop command to configure the number of SSH connections after which the system can start to drop connection requests.

This command is used in conjunction with the ssh server rate-drop and ssh server full-drop commands (in global configuration mode) to instruct the system how to handle incoming SSH connection requests. After this value has been exceeded, the system can drop subsequent SSH connection requests at the rate configured by the ssh server rate-drop command. After the number of connections specified by the ssh server full-drop command are established, the system drops all subsequent connection requests.

Use the default form of this command to return to the default value.

1.53.6   Examples

The following example shows how to configure the maximum number of SSH sessions to the system to 10; the starting drop number to 5, and the drop rate to 50. The result is that five SSH connections to the system are allowed. After the fifth connection, subsequent connection requests have a 50% chance of being dropped. The system will not accept any SSH connections after ten concurrent SSH sessions are established:

[local]Redback(config)#ssh server start-drop 5
[local]Redback(config)#ssh server rate-drop 50
[local]Redback(config)#ssh server full-drop 10

1.54   ssh server v1

1.54.1   Purpose

Enables and disables SSHv1.

1.54.2   Command Mode

exec

1.54.3   Syntax Description

This command has no keywords or arguments.

1.54.4   Default

SSHv1 is enabled by default

1.54.5   Usage Guidelines

Use the ssh server v1 and default ssh server v1 versions of this command to enable SSHv1 on the system. Use the no ssh server v1 version of this command to disable SSHv1 on the system.

1.54.6   Examples

The following example shows how to disable SSHv1 on the system:

[local]Redback>no ssh server v1

1.55   ssm-map

1.55.1   Purpose

Enables the router to determine one or more multicast source addresses for group G. The mapping translates IGMPv1 or IGMPv2 membership reports to an IGMPv3 report, enabling the router to continue as if it had initially received an IGMPv3 report.

1.55.2   Command Mode

• igmp service profile configuration
• igmp snooping profile configuration

1.55.3   Syntax Description

1.55.4   Default

No SSM map exists. IGMPv1 and IGMPv2 membership reports are not translated to IGMPv3 reports.

1.55.5   Usage Guidelines

The source-specific multicast (SSM) mapping feature is an extension of multicast routing where traffic is forwarded to receivers from only those multicast sources to which the receivers have explicitly joined. For multicast groups configured to use SSM, only source-specific multicast distribution trees are created, and not shared trees.

You can enable the router to determine one or more multicast source addresses for group reported in IGMPv1 or IGMPv2 membership reports. The SSM mapping translates IGMPv1 or IGMPv2 membership reports to an IGMPv3 report enable the router to continue as if it had initially received an IGMPv3 report.

When you configure SSM mapping, the SmartEdge router can discover source addresses from a statically configured table.

The following guidelines apply to the use of the ssm-map command:

• You must configure IGMPv3 on the interface.
• You usually have a map with IGMP. However, if you do not have a map or the map is broken because of a non-existent ACL, you will be running in the (*G) mode, which indicates no map has been established and the multicast is received. If the map is running correctly, you will be running in the (S,G) mode, which indicates a map has been established.
• When you enter the no ssm-map command, the router removes all SSM map (S,G) states and establishes a (*,G) state.
• SSM mapping does not require all hosts to support IGMPv3. SSM mapping translates IGMPv1 or IGMPv2 membership reports to an IGMPv3 report. This allows hosts running IGMPv1 or IGMPv2 to participate in SSM until the hosts transition to IGMPv3.
• Run the show igmp group detail and show igmp profile commands to verify SSM mapping status and operation.

For more information about the ssm-map command, see Configuring IP Multicast.

1.55.6   Examples

1.55.6.1   IGMPv3 Router with SSM Map Configuration and Verification

[core]Redback#show configuration
Building configuration...

Current configuration:
!
context core
!
 no ip domain-lookup
!
 interface routing_if
  ip address 10.1.1.1/24
  igmp version 3
  igmp service-profile cust_profile
  pim sparse-mode
 no logging console
!
 ip access-list group_acl
  seq 10 permit igmp 225.0.0.0 0.0.0.255
!
 igmp service-profile cust_profile
  ssm-map 1.1.1.1 group_acl
!
!
!
!
end

Check the status and operation of the IGMPv3 router with the show igmp group detail and show igmp profile commands

[core]Redback#show igmp group detail
Group             : 225.0.0.0
  Interface       : routing_if
  Circuit         : 2/3:511:63:31/1/1/8
  Uptime          : 00:00:48
  Expires         : 00:03:44
  Last reporter   : 100.5.19.2
  Running version : v3
  Compatible mode : v2
  Host Count      : 0
  Filter mode     : Include
  Source list     :
    Source Address  Uptime     Expires    Forwarding  Reporter

   1.1.1.1         00:00:48   00:03:44   Yes          100.5.19.2
   SSM Mapping Source List:
   1.1.1.1

[core]Redback#show igmp profile cust_profile
Service Profile : cust_profile
 Circuit (Interface) : 2/3:511:63:31/1/1/8 (routing_if)
  Bandwidth used (kbps)/port percent : 0/0%
  Groups (Max Allowed/Joined/Sticky) : 0/1/0
  Priority : 0
  Groups dropped
   Max count exceeded : 0
   Bandwidth exceeded : 0
   Priority drops : 0
   No bandwidth : 0
   Access denied : 0
 ssm-map (1.1.1.1,rtr_acl)

1.55.6.2   IGMP Snooper with SSM Map Configuration and Verification

! IGMP global configuration
igmp snooping profile snoop_profile
 ssm-map 1.1.1.1 group_acl
!
!
service multiple-contexts
!
!
!
! Bridge global configuration
bridge profile customer_profile
 igmp snooping profile snoop_profile
!


[customer]Redback#show configuration
Building configuration...

Current configuration:
!
context customer
!
 no ip domain-lookup
!
 interface to_ce bridge
  bridge name metro
 no logging console
!
 ip access-list group_acl
  seq 10 permit igmp 225.0.0.0 0.0.0.255
!
 bridge metro
  igmp snooping
   version 3
!
!
!
!
!
end
!
port ethernet 2/2
 no shutdown
 bind interface to_ce bridge
  bridge profile customer_profile

Check the status and operation of the IGMP snooper using the show igmp group detail command:

[customer]Redback#show igmp group detail
Group             : 225.0.0.0
  Interface       : metro
  Circuit         : 2/2:511:63:31/1/1/6
  Uptime          : 00:02:28
  Expires         : 00:02:01
  Last reporter   : 100.5.19.2
  Running version : v3
  Compatible mode : v2
  Host Count      : 0
  Filter mode     : Include
  Source list     :
    Source Address  Uptime     Expires    Forwarding  Reporter

   1.1.1.1         00:02:28   00:02:01   Yes          100.5.19.2
   SSM Mapping Source List:
   1.1.1.1

1.56   standby

1.56.1   Purpose

Configures the IP address or hostname of a standby Dynamic Host Configuration Protocol (DHCP) server.

1.56.2   Command Mode

DHCP relay server configuration

1.56.3   Syntax Description

1.56.4   Default

No standby DHCP server is assigned.

1.56.5   Usage Guidelines

Use the standby command to configure the IP address or hostname of a standby DHCP server.

Note:  

When a DHCP server is unreachable, you either forward packets to its standby DHCP server, or forward packets to all other DHCP servers in a DHCP server group, but not both; the standby and forward-all commands are mutually exclusive.

Use the no form of this command to remove the assignment of the standby DHCP server.

1.56.6   Examples

The following example shows how to configure 10.30.40.55 as the IP address for the standby DHCP server, where 192.168.1.10 is the IP address for the associated primary DHCP server:

[local]Redback(config-ctx)#dhcp relay server 192.168.1.10

[local]Redback(config-dhcp-relay)#standby 10.30.40.55

[local]Redback(config-dhcp-relay)#

1.57   standby-for

1.57.1   Purpose

Enables a neighbor as a standby neighbor for a primary neighbor.

1.57.2   Command Mode

VPLS profile neighbor configuration

1.57.3   Syntax Description

1.57.4   Default

No standby neighbor is configured.

1.57.5   Usage Guidelines

Use the standby-for command to enable a neighbor as a standby neighbor for a primary neighbor. A neighbor can serve as a standby for only one primary neighbor. This method of configuring a standby neighbor to reference a primary neighbor allows for establishing the primary and standby pseudowires using independent sets of attributes.

Before a standby neighbor can be enabled, the following conditions must be met:

• A primary neighbor must be configured in the same profile.
• A spoke connection type must be set for the neighbor.
• Local mode must be set to multitenant unit switch (MTU-s).
• No other standby neighbor in the Virtual Private LAN Services (VPLS) profile can reference the same primary neighbor IP address.

Use the no or default form of this command to disable a neighbor from being a standby neighbor for a primary neighbor.

1.57.6   Examples

The following example shows how to create a standby neighbor, 10.10.10.1, for the primary neighbor, 20.20.5.5:

[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)#standby-for 20.20.5.5

[local]Redback(config-vpls-profile-neighbor)#

1.58   static

1.58.1   Purpose

Configures static membership in a multicast group for all circuits associated with an IGMP snooping profile. All circuits attached to the specified IGMP snooping profile will have a static membership in the specified multicast group.

1.58.2   Command Mode

IGMP snooping profile configuration

1.58.3   Syntax Description

1.58.4   Default

No static memberships are added to the IGMP snooping profile.

1.58.5   Usage Guidelines

Use the static command to configure the static membership for multicast groups setting in an IGMP snooping profile. All circuits attached to the specified IGMP snooping profile will have a static membership with the specified multicast group.

Use the no form of this command to delete a static membership for a multicast group.

1.58.6   Examples

The following example shows how to configure an IGMP snooping profile called sanjose1 with a static membership for a multicast group with the 233.1.1.1 IP address:

[local]Router#configure

[local]Router(config)#igmp snooping profile sanjose1

[local]Router(config-igmp-snooping-profile)#static 233.1.1.1

1.59   static encapsulation

1.59.1   Purpose

Configures fixed values for the L2TPv3 tunnel cookie and session-id parameters. The L2TPv3 tunnel is running in a VPLS pseudowire.

1.59.2   Command Mode

VPLS profile neighbor configuration

1.59.3   Syntax Description

1.59.4   Default

The session-ID and cookie parameters are dynamically configured (not static) when the L2TPv3 sessions begins.

1.59.5   Usage Guidelines

Use this command to configure fixed values for the L2TPv3 tunnel cookie and session-id parameters. The L2TPv3 tunnel is running in a VPLS pseudowire.

Note:  

You must configure the source address of L2TPv3 encapsulated packets by entering it using the ip soft-gre command as shown in the example below.

Use the no form of this command to delete the fixed values set for the L2TPv3 session-ID and cookie parameters.

1.59.6   Examples

The following example shows the fixed configuration of the L2TPv3 cookie and session-ID parameters for the VPLS pseudowire bound to the interface targeted to the neighbor with IP address 67.1.1.2. The L2TPv3 tunnel is configured only for outbound cookies:

[local]Router#configure
[local]Router(config)#context local
[local]Router(config-ctx)#ip soft-gre 10.10.10.1                          //source address
[local]Router(config-ctx)#exit
[local]Router(config)#vpls profile P11
[local]Router(config-vpls-profile)#neighbor 67.1.1.2                      //destination address
[local]Router(config-vpls-profile-neighbor)#pw-label in 5001 out 5001
[local]Router(config-vpls-profile-neighbor)#static encapsulation l2tpv3 session-id in 30 out 30
[local]Router(config-vpls-profile-neighbor)#static encapsulation l2tpv3 cookie out 32 0 15
[local]Router(config-vpls-profile-neighbor)#end

1.60   static-group

1.60.1   Purpose

Creates a static multicast route, (*,G) or (S,G), with a subscriber circuit as the outgoing interface (OIF).

1.60.2   Command Mode

IGMP service profile configuration

1.60.3   Syntax Description

1.60.4   Default

None

1.60.5   Usage Guidelines

Use the static-group command in create a static multicast route, (*,G) or (S,G), with a subscriber circuit as the OIF.

Note:  

Protocol Independent Multicast (PIM) normally creates dynamic multicast routes; the static-group command allows you to create static multicast routes.

An OIF is an outgoing circuit that receives traffic destined for a given multicast group. When the static multicast route is configured in IGMP service profile configuration mode, the OIF is a subscriber circuit.

To configure all subscriber circuits on a multibind interface to receive multicast traffic for a specified multicast group, configure the static-group command in an Internet Group Management Protocol (IGMP) service profile that is bound to a subscriber (default) profile.

Use the no form of this command to delete the static multicast route.

1.60.6   Examples

The following example shows how to create a static multicast route, 10.10.10.1 20.20.20.0, for IGMP service profile, pro78, and then applies the service profile to the default subscriber profile:

[local]Redback(config-context)#igmp service-profile pro78

[local]Redback(config-igmp-service-profile)#static-group 10.10.10.1 
20.20.20.2

[local]Redback(config-igmp-service-profile)#exit

[local]Redback(config-context)#subscriber default

[local]Redback(config-sub)#ip igmp service-profile pro78