Global Service Command Reference

Command Hierarchies

Global Service Configuration Commands

Customer Commands

config
— service
customer customer-id [create]
— no customer customer-id
customer contact-information
— no customer
description description-string
customer phone-number
[no] customer

SDP Commands

config
— service
sdp sdp-id [gre | mpls | ip] [create]
— no sdp sdp-id
[no] bgp-tunnel
description description-string
encryption-keygroup keygroup-id direction {inbound | outbound}
— no encryption-keygroup direction {inbound | outbound}
far-end ip-address
— no far-end
hello-time seconds
— no hello-time
hold-down-time seconds
max-drop-count count
message-length octets
[no] shutdown
timeout timeout
— no timeout
[no] ldp
[no] lsp lsp-name
metric metric
— no metric
path-mtu bytes
— no path-mtu
signaling {off | tldp}
[no] shutdown
vlan-vc-etype 0x0600..0xffff
— no vlan-vc-etype [x0600.0xffff]

SAP Commands

config
— service
apipe
sap sap-id [create]
— no sap sap-id
cpipe
sap sap-id [create]
— no sap sap-id
epipe
sap sap-id [create]
— no sap sap-id
fpipe
sap sap-id [create]
— no sap sap-id
hpipe
sap sap-id [create]
— no sap sap-id
ipipe
sap sap-id [create]
— no sap sap-id
ies
interface ip-int-name [create]
sap sap-id [create]
— no sap sap-id
vprn
interface ip-int-name [create]
sap sap-id [create]
— no sap sap-id
vpls
sap sap-id [create]
— no sap sap-id

ETH-CFM Commands

config
— eth-cfm
— domain md-index [format {dns | mac | none | string}] name md-name level level
— domain md-index
— no domain md-index
— association ma-index [format {icc-based | integer | string | vid | vpn-id}] name ma-name
— association ma-index
— no association ma-index
[no] bridge-identifier bridge-id
— vlan vlan-id
— no vlan
— ccm-interval {10ms | 100ms | 1 | 10 | 60 | 600}
— no ccm-interval
[no] remote-mepid mep-id
— slm
— inactivity-timer timeout
— no inactivity-timer
Note:

For information on configuring ETH-CFM commands, refer to the 7705 SAR OS OAM and Diagnostics Guide.

Show Commands

show
— service
customer customer-id
sdp [sdp-id | far-end ip-addr] [detail | keep-alive-history]
sdp-using sdp-id[:vc-id] | far-end ip-address]
service-using [epipe] [fpipe] [hpipe] [ies] [vprn] [mirror] [vpls] [apipe] [cpipe] [sdp sdp-id] [customer customer-id]

Command Descriptions

Global Service Configuration Commands

Generic Commands

description

Syntax 
description description-string
no description
Context 
config>service>customer
config>service>sdp
Description 

This command creates a text description stored in the configuration file for a configuration context.

The no form of this command removes the string from the context.

Default 

No description is associated with the configuration context.

Parameters 
description-string—
the description character string. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.

shutdown

Syntax 
[no] shutdown
Context 
config>service>sdp
config>service>sdp>keep-alive
Description 

The shutdown command administratively disables an entity. The operational state of the entity is disabled as well as the operational state of any entities contained within. When disabled, an entity does not change, reset, or remove any configuration settings or statistics. Many objects must be shut down before they may be deleted. Many entities must be explicitly enabled using the no shutdown command.

The no form of this command places the entity into an administratively enabled state.

Services are created in the administratively down state (shutdown). When a no shutdown command is entered, the service becomes administratively up and then tries to enter the operationally up state. Default administrative states for services and service entities are described in the following Special Cases.

Special Cases 
Service Admin State—
bindings to an SDP within the service will be put into the out-of-service state when the service is shut down. While the service is shut down, all customer packets are dropped and counted as discards for billing and debugging purposes.
SDP (global)—
when an SDP is shut down at the global service level, all bindings to that SDP are put into the out-of-service state and the SDP itself is put into the administratively and operationally down states. Packets that would normally be transmitted using this SDP binding will be discarded and counted as dropped packets.
SDP (service level)—
shutting down an SDP within a service only affects traffic on that service from entering or being received from the SDP. The SDP itself may still be operationally up for other services.
SDP Keepalives—
enables SDP connectivity monitoring keepalive messages for the SDP ID. Default state is disabled (shutdown), in which case the operational state of the SDP-ID is not affected by the keepalive message state.

Customer Commands

customer

Syntax 
customer customer-id [create]
no customer customer-id
Context 
config>service
Description 

This command creates a customer ID and customer context used to associate information with a particular customer. Services can later be associated with this customer at the service level.

Each customer-id must be unique and the create keyword must follow each new customer customer-id entry.

To edit a customer’s parameters, enter the existing customer customer-id without the create keyword.

Default customer 1 always exists on the system and cannot be deleted.

The no form of this command removes a customer-id and all associated information. Before removing a customer-id, all references to that customer in all services must be deleted or changed to a different customer ID.

Parameters 
customer-id—
specifies the ID number to be associated with the customer, expressed as an integer
Values—
1 to 2147483647

contact

Syntax 
contact contact-information
no contact
Context 
config>service>customer
Description 

This command allows you to configure contact information for a customer. Include any customer-related contact information such as a technician’s name or account contract name.

The no form of this command removes the contact information from the customer ID.

Default 

No contact information is associated with the customer-id.

Parameters 
contact-information—
the customer contact information entered as an ASCII character string. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.

phone

Syntax 
[no] phone phone-number
Context 
config>service>customer
Description 

This command adds telephone number information for a customer ID.

The no form of this command removes the phone number value from the customer ID.

Default 

No telephone number information is associated with a customer.

Parameters 
phone-number—
the customer phone number entered as an ASCII string. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.

SDP Commands

sdp

Syntax 
sdp sdp-id [gre | mpls | ip] [create]
no sdp sdp-id
Context 
config>service
Description 

This command creates or edits an SDP. SDPs must be explicitly configured.

An SDP is a (logical) service entity that is created on the local router. An SDP identifies the endpoint of a logical, unidirectional service tunnel. Traffic enters the tunnel at the SDP on the local router and exits the tunnel at the remote router. Thus, it is not necessary to specifically define far-end SAPs.

The 7705 SAR supports generic routing encapsulation (GRE) tunnels, multiprotocol label switching (MPLS) tunnels, and IP tunnels.

For MPLS, a 7705 SAR supports both signaled and non-signaled label switched paths (LSPs) through the network. Non-signaled paths are defined at each hop through the network. Signaled LSPs are established in LDP-DU (downstream unsolicited) mode.

SDPs are created and then bound to services. Many services may be bound to a single SDP. The operational and administrative state of the SDP controls the state of the SDP binding to the service.

If sdp-id does not exist, a new SDP is created. SDPs are created in the admin down state (shutdown). Once all relevant parameters are defined, the no shutdown command must be executed before the SDP can be used.

If sdp-id exists, the current CLI context is changed to that SDP for editing and modification. If editing an existing SDP, the gre, mpls, or ip keyword is not specified. If a keyword is specified for an existing sdp-id, an error is generated and the context of the CLI is not changed to the specified sdp-id.

The no form of this command deletes the specified SDP. Before an SDP can be deleted, it must be administratively down (shutdown) and not bound to any services. If the specified SDP is bound to a service, the no sdp command fails, generating an error message specifying the first bound service found during the deletion process. If the specified sdp-id does not exist, an error is generated.

Default 

n/a

Parameters 
sdp-id—
the SDP identifier
Values—
1 to 17407
gre—
specifies that the SDP will use GRE encapsulation tunnels. Only one GRE SDP is supported to a given destination 7705 SAR or 7710/7750 SR.
mpls—
specifies that the SDP will use MPLS encapsulation and one or more LSP tunnels to reach the far-end 7705 SAR or 7710/7750 SR. Multiple MPLS SDPs are supported to a given destination service router. Multiple MPLS SDPs to a single destination service router are helpful when they use divergent paths.
ip—
specifies that the SDP will use IP encapsulation tunnels. Only one IP SDP is supported to a given destination 7705 SAR because the SDP is tied to the system address of the destination LER.

adv-mtu-override

Syntax 
[no] adv-mtu-override
Context 
config>service>sdp
Description 

This command overrides the advertised VC-type MTU. When enabled, the 7705 SAR signals a VC MTU equal to the service MTU that includes the Layer 2 header. Under normal operations it will advertise the service MTU minus the Layer 2 header. In the receive direction, it will accept either one.

The no form of this command disables the VC-type MTU override.

Default 

no adv-mtu-override

bgp-tunnel

Syntax 
[no] bgp-tunnel
Context 
config>service>sdp
Description 

This command allows the use of BGP route tunnels available in the tunnel table to reach SDP far-end nodes. BGP route tunnels are only available with MPLS SDPs. Only one transport method is allowed per SDP: LDP, RSVP-LSP or BGP-Tunnel.

The no form of the command disables the use of BGP route tunnels for the SDP far-end.

Default 

no bgp-tunnel

encryption-keygroup

Syntax 
encryption-keygroup keygroup-id direction {inbound | outbound}
no encryption-keygroup direction {inbound | outbound}
Context 
config>service>sdp
Description 

This command is used to bind a key group to an SDP for inbound or outbound packet processing. When configured in the outbound direction, packets egressing the node use the active-outbound-sa associated with the key group configured. When configured in the inbound direction, received packets must be encrypted using one of the valid security associations configured for the key group. Services using the SDP will be encrypted.

Encryption is enabled once the outbound direction is configured.

The no form of the command removes the key group from the SDP in the specified direction (inbound or outbound).

Default 

n/a

Parameters 
keygroup-id—
the number of the key group being configured
Values—
1 to 15 or keygroup-name (up to 64 characters)
direction {inbound | outbound}
mandatory keywords when binding a key group to a service for a particular direction

far-end

Syntax 
far-end ip-address
no far-end
Context 
config>service>sdp
Description 

This command configures the system IP address of the far-end destination 7705 SAR, 7710 SR, 7750 SR, or other router ID platform for the SDP that is the termination point for a service.

The far-end IP address must be explicitly configured. The destination IP address must be a 7705 SAR, 7710 SR, 7750 SR, or other router ID platform system IP address.

If the SDP uses GRE or IP for the destination encapsulation, the local 7705 SAR might not know that the ip-address is actually a system IP interface address on the far-end service router.

If the SDP uses MPLS encapsulation, the far-end ip-address is used to check LSP names when added to the SDP. If the “to IP address” defined within the LSP configuration does not exactly match the SDP far-end ip-address, the LSP will not be added to the SDP and an error message will be generated.

An SDP cannot be administratively enabled until a far-end ip-address is defined. The SDP is operational when it is administratively enabled (no shutdown).

The no form of this command removes the currently configured destination IP address for the SDP. The ip-address parameter is not specified and will generate an error message if used in the no far-end command. The SDP must be administratively disabled using the config>service>sdp>shutdown command before the no far-end command can be executed. Removing the far-end IP address will cause all lsp-name associations with the SDP to be removed.

Default 

n/a

Parameters 
ip-address—
the system address of the far-end 7705 SAR for the SDP
Values—
a.b.c.d

ldp

Syntax 
[no] ldp
Context 
config>service>sdp
Description 

This command enables LDP-signaled LSPs on MPLS-encapsulated SDPs.

In MPLS SDP configurations, either one LSP can be specified or LDP can be enabled. The SDP ldp and lsp commands are mutually exclusive. If an LSP is specified on an MPLS SDP, then LDP cannot be enabled on the SDP. To enable LDP on the SDP when an LSP is already specified, the LSP must be removed from the configuration using the no lsp lsp-name command.

Alternatively, if LDP is already enabled on an MPLS SDP, then an LSP cannot be specified on the SDP. To specify an LSP on the SDP, LDP must be disabled. The LSP must have already been created in the config>router>mpls context with a valid far-end IP address.

Default 

no ldp (disabled)

lsp

Syntax 
[no] lsp lsp-name
Context 
config>service>sdp
Description 

This command creates an association between an LSP and an MPLS SDP. This command is implemented only on MPLS-type encapsulated SDPs.

In MPLS SDP configurations, either one LSP can be specified or LDP can be enabled. The SDP ldp and lsp commands are mutually exclusive. If an LSP is specified on an MPLS SDP, then LDP cannot be enabled on the SDP. To enable LDP on the SDP when an LSP is already specified, the LSP must be removed from the configuration using the no lsp lsp-name command.

Alternatively, if LDP is already enabled on an MPLS SDP, then an LSP cannot be specified on the SDP. To specify an LSP on the SDP, LDP must be disabled. The LSP must have already been created in the config>router>mpls context with a valid far-end IP address. Refer to the 7705 SAR OS MPLS Guide for CLI syntax and command usage.

If no LSP is associated with an MPLS SDP, the SDP cannot enter the operationally up state. The SDP can be administratively enabled (no shutdown) with no LSP associations. The lsp-name may be shut down, causing the association with the SDP to be operationally down (the LSP will not be used by the SDP).

LSP SDPs also require that the T-LDP signaling be specified and that the SDP keepalive parameter be enabled and not timed out.

The no form of this command deletes an LSP association from an SDP. If the lsp-name does not exist as an association or as a configured LSP, no error is returned. An lsp-name must be removed from all SDP associations before the lsp-name can be deleted from the system. The SDP must be administratively disabled (shutdown) before the last lsp-name association with the SDP is deleted.

Default 

No LSP names are defined.

Parameters 
lsp-name—
the name of the LSP to associate with the SDP. An LSP name is case-sensitive and is limited to 32 ASCII 7-bit printable characters with no spaces. If an exact match of lsp-name does not already exist as a defined LSP, an error message is generated. If the lsp-name does exist and the LSP to IP address matches the SDP far-end IP address, the association is created.

metric

Syntax 
metric metric
no metric
Context 
config>service>sdp
Description 

This command specifies the metric to be used within the tunnel table manager for decision-making purposes. When multiple SDPs going to the same destination exist, this value is used as a tie-breaker by tunnel table manager users to select the route with the lower value.

Parameters 
metric—
specifies the SDP metric
Values—
1 to 17407

path-mtu

Syntax 
path-mtu bytes
no path-mtu
Context 
config>service>sdp
Description 

This command configures the Maximum Transmission Unit (MTU) in bytes that the SDP can transmit to the far-end router without packet dropping or IP fragmentation overriding the default SDP-type path MTU.

The default SDP-type path-mtu can be overridden on a per-SDP basis.

Dynamic maintenance protocols on the SDP may override this setting.

If the physical mtu on an egress interface indicates that the next hop on an SDP path cannot support the current path-mtu, the operational path-mtu on that SDP will be modified to a value that can be transmitted without fragmentation.

The no form of this command removes any path-mtu defined on the SDP and the SDP will use the system default for the SDP type.

Default 

The default path-mtu defined on the system for the type of SDP is used.

Parameters 
bytes —
specifies the number of bytes in the path MTU
Values—
576 to 9194

signaling

Syntax 
signaling {off | tldp}
Context 
config>service>sdp
Description 

This command specifies the signaling protocol used to obtain the ingress and egress labels in frames transmitted and received on the SDP. When signaling is off, then labels are manually configured when the SDP is bound to a service. The signaling value can only be changed while the administrative status of the SDP is down.

The no form of this command is not applicable. To modify the signaling configuration, the SDP must be administratively shut down and then the signaling parameter can be modified and re-enabled.

Default 

tldp

Parameters 
off—
ingress and egress signal auto-labeling is not enabled. If this parameter is selected, then each service using the specified SDP must manually configure VPN labels. This configuration is independent of the SDP transport type, MPLS (LDP).
tldp—
ingress and egress signaling auto-labeling is enabled

vlan-vc-etype

Syntax 
vlan-vc-etype 0x0600..0xffff
no vlan-vc-etype [0x0600..0xffff]
Context 
config>service>sdp
Description 

This command configures the VLAN VC Ethertype. The no form of this command returns the value to the default. The etype value populates the Ethertype field in the Ethernet frame. It is used to indicate which protocol is being transported in the Ethernet frame. The default value indicates that the payload is an IEEE 802.1q-tagged frame.

Default 

no vlan-vc-etype (0x8100)

Parameters 
0x0600..0xffff—
specifies a valid VLAN etype identifier

SDP Keepalive Commands

keep-alive

Syntax 
keep-alive
Context 
config>service>sdp
Description 

This command is the context for configuring SDP connectivity monitoring keepalive messages for the SDP-ID.

SDP-ID keepalive messages use SDP Echo Request and Reply messages to monitor SDP connectivity. The operating state of the SDP is affected by the keepalive state on the SDP-ID. SDP Echo Request messages are only sent when the SDP-ID is completely configured and administratively up. If the SDP-ID is administratively down, keepalives for that SDP-ID are disabled. SDP Echo Requests, when sent for keepalive messages, are always sent with the originator-sdp-id. All SDP-ID keepalive SDP Echo Replies are sent using generic IP OAM encapsulation.

When a keepalive response is received that indicates an error condition, the SDP ID will immediately be brought operationally down. Once a response is received that indicates the error has cleared and the hold-down-time interval has expired, the SDP ID will be eligible to be put into the operationally up state. If no other condition prevents the operational change, the SDP ID will enter the operational state.

A set of event counters track the number of keepalive requests sent, the size of the message sent, non-error replies received and error replies received. A keepalive state value is kept, indicating the last response event. A keepalive state timestamp value is kept, indicating the time of the last event. With each keepalive event change, a log message is generated, indicating the event type and the timestamp value.

Table 13 describes keepalive interpretation of SDP Echo Reply response conditions and the effect on the SDP ID operational status.

Table 13:  SDP Echo Reply Response Conditions  

Result of Request

Stored Response State

Operational State

keepalive request timeout without reply

Request Timeout

Down

keepalive request not sent due to non-existent orig-sdp-id  1

Orig-SDP Non-Existent

Down

keepalive request not sent due to administratively down orig-sdp-id

Orig-SDP Admin-Down

Down

keepalive reply received, invalid origination-id

Far End: Originator-ID Invalid

Down

keepalive reply received, invalid responder-id

Far End: Responder-ID Error

Down

keepalive reply received, No Error

Success

Up (if no other condition prevents)

    Note:

  1. This condition should not occur.

hello-time

Syntax 
hello-time seconds
no hello-time
Context 
config>service>sdp>keep-alive
Description 

This command configures the time period between SDP keepalive messages on the SDP-ID for the SDP connectivity monitoring messages.

The no form of this command resets the hello-time seconds value to the default setting.

Parameters 
seconds—
the time period in seconds between SDP keepalive messages, expressed as a decimal integer
Values—
1 to 3600
Values—
10

hold-down-time

Syntax 
hold-down-time seconds
no hold-down-time
Context 
config>service>sdp>keep-alive
Description 

This command configures the minimum time period the SDP will remain in the operationally down state in response to SDP keepalive monitoring.

This parameter can be used to prevent the SDP operational state from “flapping” by rapidly transitioning between the operationally up and operationally down states based on keepalive messages.

When an SDP keepalive response is received that indicates an error condition or the max-drop-count keepalive messages receive no reply, the sdp-id will immediately be brought operationally down. If a keepalive response is received that indicates the error has cleared, the sdp-id will be eligible to be put into the operationally up state only after the hold-down-time interval has expired.

The no form of this command resets the hold-down-time seconds value to the default setting.

Parameters 
seconds—
the time in seconds, expressed as a decimal integer, the sdp-id will remain in the operationally down state after an SDP keepalive error before it is eligible to enter the operationally up state. A value of 0 indicates that no hold-down-time will be enforced for sdp-id.
Values—
0 to 3600
Values—
10

max-drop-count

Syntax 
max-drop-count count
no max-drop-count
Context 
config>service>sdp>keep-alive
Description 

This command configures the number of consecutive SDP keepalive failed request attempts or remote replies that can be missed after which the SDP is operationally downed.

If the max-drop-count consecutive keepalive request messages cannot be sent or no replies are received, the SDP-ID will be brought operationally down by the keepalive SDP monitoring.

The no form of this command resets the max-drop-count count value to the default settings.

Parameters 
count—
the number of consecutive SDP keepalive requests that can fail to be sent or replies missed before the SDP is brought down, expressed as a decimal integer
Values—
1 to 5
Values—
3

message-length

Syntax 
message-length octets
no message-length
Context 
config>service>sdp>keep-alive
Description 

This command configures the size of SDP monitoring keepalive request messages transmitted on the SDP.

The no form of this command resets the message-length octets value to the default setting.

Parameters 
octets—
the size of keepalive request messages in octets, expressed as a decimal integer. The size keyword overrides the default keepalive message size.

The message length should be equal to the SDP operating path MTU as configured in the path-mtu command.

If the default size is overridden, the actual size used will be the smaller of the operational SDP-ID path MTU and the size specified.

Values—
72 to 1500
Values—
0

timeout

Syntax 
timeout timeout
no timeout
Context 
config>service>sdp>keep-alive
Description 

This command configures the time interval that the SDP waits before tearing down the session.

Parameters 
timeout—
the timeout in seconds, expressed as a decimal integer
Values—
1 to 10
Values—
5

Show Commands

Note:

The following command outputs are examples only; actual displays may differ depending on supported functionality and user configuration.

customer

Syntax 
customer customer-id
Context 
show>service
Description 

This command displays service customer information.

Parameters 
customer-id—
displays only information for the specified customer ID
Values—
1 to 2147483647
Values—
all customer IDs display
Output 

The following output is an example of customer information, and Table 14 describes the fields.

Sample Output
*A:ALU-12# show service customer
==========================================================
Customers
==========================================================
Customer-ID : 1
Contact : Manager
Description : Default customer
Phone : (123) 555-1212
 
Customer-ID : 2
Contact : Tech Support
Description : ABC Networks
Phone : (234) 555-1212
 
Customer-ID : 3
Contact : Fred
Description : ABC Networks
Phone : (345) 555-1212
 
Customer-ID : 6
Contact : Ethel
Description : Epipe Customer
Phone : (456) 555-1212
 
Customer-ID : 7
Contact : Lucy
Description : VPLS Customer
Phone : (567) 555-1212
 
Customer-ID : 8
Contact : Customer Service
Description : IES Customer
Phone : (678) 555-1212
 
Customer-ID : 274
Contact : Mssrs. Beaucoup
Description : ABC Company
Phone : 650 123-4567
 
Customer-ID : 94043
Contact : Test Engineer on Duty
Description : TEST Customer
Phone : (789) 555-1212
------------------------------------------------------
Total Customers : 8
-----------------------------------------------------------
*A:ALU-12#
*A:ALU-12# show service customer 274
==============================================================================
Customer 274
==============================================================================
Customer-ID : 274
Contact : Mssrs. Beaucoup
Description : ABC Company
Phone : 650 123-4567
------------------------------------------------------------------------------
Total Customers : 1
------------------------------------------------------------------------------
*A:ALU-12#
Table 14:  Show Customer Command Output Fields 

Label

Description

Customer-ID

Displays the unique customer identification number

Contact

Displays the name of the primary contact person

Description

Displays generic information about the customer

Phone

Displays the telephone or pager number used to reach the primary contact person

Total Customers

Displays the total number of customers configured

sdp

Syntax 
sdp [sdp-id | far-end ip-address] [detail | keep-alive-history]
Context 
show>service
Description 

This command displays SDP information.

If no optional parameters are specified, a summary SDP output for all SDPs is displayed.

Parameters 
sdp-id—
the SDP ID for which to display information
Values—
1 to 17407
Values—
all SDPs
ip-address
displays only SDPs matching with the specified far-end IP address
Values—
SDPs with any far-end IP address
detail—
displays detailed SDP information
keep-alive-history—
displays the last fifty SDP keepalive events for the SDP
Output 

The following output is an example of service SDP information, and Table 15 describes the fields.

Sample Output
*A:ALU-12# show service sdp
===============================================================================
Services: Service Destination Points
===============================================================================
SdpId    Adm MTU   Opr MTU   IP address       Adm  Opr         Deliver Signal
-------------------------------------------------------------------------------
10       0         0         10.10.10.24      Up   Down        LDP     TLDP
20       0         0         10.10.10.24      Up   Down        MPLS    TLDP
30       4462      1514      10.20.1.21       Up   Up          GRE     TLDP
-------------------------------------------------------------------------------
Number of SDPs : 3
-------------------------------------------------------------------------------
===============================================================================
*A:ALU-12#
*A:ALU-12# show service sdp 10
===============================================================================
Service Destination Point (Sdp Id : 10)
===============================================================================
SdpId    Adm MTU   Opr MTU   IP address       Adm  Opr         Deliver Signal
-------------------------------------------------------------------------------
10       0         0         10.10.10.24      Up   Down        LDP     TLDP
===============================================================================
*A:ALU-12#
*A:ALU-12# show service sdp 8 detail
===============================================================================
Service Destination Point (Sdp Id : 8) Details
===============================================================================
-------------------------------------------------------------------------------
 Sdp Id 8  -(10.10.10.104)
-------------------------------------------------------------------------------
Description           : MPLS-10.10.10.104
SDP Id                : 8                    SDP-Source         : manual
Admin Path MTU        : 0                    Oper Path MTU      : 1550
Delivery              : MPLS                    
Far End               : 10.10.10.104         Delivery           : MPLS
Admin State           : Up                   Oper State         : Down 
Signaling             : TLDP                 Metric             : 0  
Last Status Change    : 02/01/2007 09:11:39  Adv. MTU Over.     : No
Last Mgmt Change      : 02/01/2007 09:11:46  VLAN VC Etype      : 0x8100
Flags                 : SignalingSessDown TransportTunnDown
KeepAlive Information :
Admin State          : Disabled              Oper State         : Disabled
Hello Time           : 10                    Hello Msg Len      : 0
Hello Timeout        : 5                     Unmatched Replies  : 0
Max Drop Count       : 3                     Hold Down Time     : 10
Tx Hello Msgs        : 0                     Rx Hello Msgs      : 0
Associated LSP LIST :
Lsp Name             : to-104
Admin State          : Up                    Oper State         : Down
Time Since Last Tran*: 01d07h36m
===============================================================================
* indicates that the corresponding row element may have been truncated.
*A:ALU-12#
*A:ALU-12>show>service# sdp 5001 keep-alive-history
===============================================================================
Service Destination Point (Sdp Id : 5001)
===============================================================================
Time of Probe Report      RTT(ms) Size   Status
-------------------------------------------------------------------------------
2010/11/30 11:27:32       1011    72     Response Received                     
2010/11/30 11:27:22       1001    72     Response Received                     
2010/11/30 11:27:12       1001    72     Response Received                     
2010/11/30 11:27:02       1001    72     Response Received                     
2010/11/30 11:26:58       1002    72     Response Received                     
===============================================================================
*A:ALU-12>show>service#
Table 15:  Show Service SDP Output Fields 

Label

Description

SDP Id

Identifies the SDP

Description

Identifies the SDP by the text description stored in its configuration file

SDP Source

Specifies the SDP source type

Adm MTU (Adm Path MTU)

Specifies the desired largest service frame size (in octets) that can be transmitted through this SDP to the far-end router

Opr MTU (Opr Path MTU)

Specifies the actual largest service frame size (in octets) that can be transmitted through this SDP to the far-end router

Delivery

Specifies the delivery routing protocol

Far End

Specifies the IP address of the remote end of the GRE or MPLS tunnel defined by this SDP

Adm (Admin State)

Specifies the desired state of the SDP

Opr (Oper State)

Specifies the operating state of the SDP

Deliver (Delivery)

Specifies the type of delivery used by the SDP: MPLS, GRE, or IP

Flags

Specifies all the conditions that affect the operating status of this SDP

Signal (Signaling)

Specifies the signaling protocol used to obtain the ingress and egress labels used in frames transmitted and received on the SDP

Metric

Specifies the value used as a tie-breaker by the tunnel table manager to select a route

Last Status Change

Specifies the time of the most recent operating status change to this SDP

Last Mgmt Change

Specifies the time of the most recent management-initiated change to this SDP

Adv. MTU Over

Specifies the state of the advertised VC-type MTU override command

VLAN VC Etype

Specifies the VLAN VC Ethertype for the SDP

Number of SDPs

Specifies the total number of SDPs displayed according to the criteria specified

Keepalive Information:

Hello Time

Specifies how often the SDP Echo Request messages are transmitted on this SDP

Hello Msg Len

Specifies the length of the SDP Echo Request messages transmitted on this SDP

Hello Timeout

Specifies the number of seconds to wait for an SDP echo response message before declaring a timeout

Unmatched Replies

Specifies the number of SDP unmatched message replies timer expired

Max Drop Count

Specifies the maximum number of consecutive SDP Echo Request messages that can be unacknowledged before the keepalive protocol reports a fault

Hold Down Time

Specifies the amount of time to wait before the keepalive operating status is eligible to enter the alive state

TX Hello Msgs

Specifies the number of SDP echo request messages transmitted since the keepalive was administratively enabled or the counter was cleared

Rx Hello Msgs

Specifies the number of SDP echo request messages received since the keepalive was administratively enabled or the counter was cleared

Collect Stats.

Specifies that the collection of accounting and statistical data for the SDP is enabled or disabled

Associated LSP LIST:

Note: If the SDP type is GRE, the following message displays: SDP Delivery Mechanism is not MPLS

Lsp Name

For MPLS: identifies the name of the static LSP

Time since Last Trans*

For MPLS: specifies the time that the associated static LSP has been in service

Time of Probe Report

Indicates the date and time of the report

RTT (ms)

Indicates round-trip time (RTT), in milliseconds.

Size

Indicates the size of the packet, in bytes

Status

Indicates the status of the response

Group Encryption

Inbound Keygroup Id

Indicates the key group used to decrypt inbound traffic for the service

Outbound Keygroup Id

Indicates the key group used to encrypt outbound traffic for the service

sdp-using

Syntax 
sdp-using [sdp-id[:vc-id] | far-end ip-address]
Context 
show>service
Description 

This command displays services using SDP or far-end address options.

Parameters 
sdp-id
displays only services bound to the specified SDP ID
Values—
1 to 17407
vc-id—
the virtual circuit identifier
Values—
1 to 4294967295
ip-address
displays only services matching with the specified far-end IP address
Values—
services with any far-end IP address
Output 

The following output is an example of service SDP-using information, and Table 16 describes the fields.

Sample Output
*A:ALU-1# show service sdp-using 300
===============================================================================
Service Destination Point (Sdp Id : 300)
===============================================================================
SvcId       SdpId               Type Far End        Opr State I.Label  E.Label
-------------------------------------------------------------------------------
1           300:1               Spok 10.0.0.13      Up        131071   131071
2           300:2               Spok 10.0.0.13      Up        131070   131070
100         300:100             Spok 10.0.0.13      Up        131069   131069
101         300:101             Spok 10.0.0.13      Up        131068   131068
102         300:102             Spok 10.0.0.13      Up        131067   131067
-------------------------------------------------------------------------------
Number of SDPs : 7
-------------------------------------------------------------------------------
===============================================================================
*A:ALU-1#
Table 16:  Show Service SDP-Using Output Fields 

Label

Description

SvcId

Identifies the service

SdpId

Identifies the SDP

Type

Indicates the type of SDP (mesh or spoke)

Far End

Displays the far-end address of the SDP

Opr State

Displays the operational state of the service

I. Label

Displays the ingress label used by the far-end device to send packets to this device in this service by this SDP

E. Label

Displays the egress label used by this device to send packets to the far-end device in this service by this SDP

service-using

Syntax 
service-using [epipe] [fpipe] [hpipe] [ies] [vpls] [vprn] [mirror] [apipe] [ipipe] [cpipe] [sdp sdp-id] [customer customer-id]
Context 
show>service
Description 

This command displays the services matching certain usage properties.

If no optional parameters are specified, all services defined on the system are displayed.

Parameters 
epipe—
displays matching Epipe services
ies—
displays matching IES services
vpls—
displays matching VPLS services
vprn—
displays matching VPRN services
mirror—
displays matching mirror services
apipe—
displays matching Apipe services
cpipe—
displays matching Cpipe services
fpipe—
displays matching Fpipe services
hpipe—
displays matching Hpipe services
sdp-id
displays only services bound to the specified SDP ID
Values—
1 to 17407
Values—
services bound to any SDP ID
customer-id
displays services only associated with the specified customer ID
Values—
1 to 2147483647
Values—
services associated with a customer
Output 

The following outputs are examples of service-using information, and Table 17 describes the fields.

Sample Output all services used in system
*A:ALU-12# show service service-using 
===============================================================================
Services 
===============================================================================
ServiceId    Type      Adm    Opr        CustomerId        Service Name    
-------------------------------------------------------------------------------
1            Cpipe     Down   Down       1                 cpipe_1_global 
2            Apipe     Down   Down       1                 apipe_2 
103          Epipe     Up     Up         104               epipe_103_sales 
104          Epipe     Up     Up         104               epipe_104_marketing 
105          Epipe     Up     Up         104               epipe_105_finance 
303          Cpipe     Up     Up         104                
304          Cpipe     Up     Up         104                
305          Cpipe     Up     Up         104                
701          Apipe     Up     Down       1                  
702          Apipe     Up     Down       1                  
703          Apipe     Up     Down       1                  
704          Apipe     Up     Down       1                  
807          Apipe     Up     Down       1                  
808          Apipe     Up     Down       1                  
903          Cpipe     Up     Up         1                  
904          Cpipe     Up     Up         1                  
5000         VPLS      Down   Down       1                  vpls_5000_sales
5001         VPLS      Down   Down       1                  
-------------------------------------------------------------------------------
Matching Services : 19
*A:7705:Dut-A# show service service-using 
===============================================================================
Services 
===============================================================================
ServiceId    Type      Adm    Opr        CustomerId        Service Name    
-------------------------------------------------------------------------------
100          Mirror    Up     Up         1                 XYZ Mirror 100 
1000         Epipe     Up     Up         1                 XYZ Epipe 1000 
2000         VPLS      Up     Up         1                
2100         VPLS      Up     Up         1                 rVpls2100 
2200         Ipipe     Up     Up         1                  
3000         IES       Up     Up         1                 XYZ Ies 3000 
3500         VPRN      Up     Up         1                 XYZ Vprn 3500 
4050         IES       Up     Up         1                 XYZ Ies 4050
-------------------------------------------------------------------------------
Matching Services : 8
Sample Output services used by customer
*A:ALU-12# show service service-using customer 1
===============================================================================
Services  Customer 1
===============================================================================
ServiceId    Type      Adm    Opr        CustomerId        Service Name    
-------------------------------------------------------------------------------
1            Cpipe     Down   Down       1                 cpipe_1_global 
2            Apipe     Down   Down       1                 apipe_2
701          Apipe     Up     Down       1                  
702          Apipe     Up     Down       1                 
703          Apipe     Up     Down       1                  
704          Apipe     Up     Down       1                 
807          Apipe     Up     Down       1                  
808          Apipe     Up     Down       1                  
903          Cpipe     Up     Up         1                  
904          Cpipe     Up     Up         1                  
5000         VPLS      Down   Down       1                  vpls_5000_sales
5001         VPLS      Down   Down       1                 
-------------------------------------------------------------------------------
Matching Services : 13
*A:ALU-12#
Sample Output services by service type (epipe)
*A:ALU-12# show service service-using epipe
===============================================================================
Services [epipe]
===============================================================================
ServiceId    Type      Adm    Opr        CustomerId        Service Name    
-------------------------------------------------------------------------------
103          Epipe     Up     Up         104               epipe_103_sales 
104          Epipe     Up     Up         104               epipe_104_marketing 
105          Epipe     Up     Up         104               epipe_105_finance 
-------------------------------------------------------------------------------
Matching Services : 3
*A:ALU-12#
Table 17:  Show Service service-using Output Fields  

Label

Description

Service Id

Identifies the service

Type

Specifies the service type configured for the service ID

Adm

Displays the desired state of the service

Opr

Displays the operating state of the service

CustomerID

Displays the ID of the customer who owns this service

Service Name

The service name