> S-GW Service Configuration Mode Commands
> The S-GW (Serving Gateway) Service Configuration Mode is used to create and manage the relationship between an eGTP service used for either ingress or egress control plane and user data plane network traffic.
> accounting context
> Configures the GTPP accounting context and group selection for S-GW service.
> Product
> S-GW
> Privilege
> Administrator
> Syntax
> accounting context name [ gtpp group name ]
> no accounting context
> no
> Removes the configured accounting context from this service.
> context name
> Specifies the context where GTPP accounting is performed. name must be an existing context configured on the system and be from 1 to 79 alpha and/or numeric characters.
> If an accounting context name is not configured in the S-GW service, the context where the S-GW service resides is considered the accounting context and the default GTPP group is used.
> gtpp group name
> Specifies a GTPP group used to perform GTPP accounting. name must be an existing GTPP group configured on the system and be from 1 to 79 alpha and/or numeric characters.
> If a GTPP group is not configured, the system will use the default GTPP group in the specified accounting context. If the accounting context is not specified, the system will use default GTPP group in the context where the S-GW service resides.
> Usage
> Use this command to specify the accounting context and/or GTPP accounting group the S-GW service will use to perform GTPP accounting.
> Example
> The following command specifies a GTPP accounting context named acct-2 and a GTPP accounting group named gtpp-grp-3 as the context and group the S-GW service will use:
> accounting context acct-2 gtpp group gtpp-grp-3
> associate
> Associates the S-GW service with QoS and policy control and charging configurations.
> Product
> S-GW
> Privilege
> Administrator
> Syntax
> associate { accounting-policy name | egress-proto { gtp | gtp-pmip | pmip } [ egress-context name [ egtp-service name ] [ mag-service name ] ] | ims-auth-service name | ingress egtp-service name | qci-qos-mapping name }
> no associate { accounting-policy name | egress-proto [ egress-context [ egtp-service ] [ mag-service ] ] | ims-auth-service name | ingress egtp-service | qci-qos-mapping name | }
> no
> Removes the specified association form the S-GW service.
> accounting-policy name
> Associates the S-GW service with an accounting policy configured in the same context. name must be an existing accounting policy and be from 1 to 63 alpha and/or numeric characters.
> Accounting policies are configured through the policy accounting command in the Context Configuration Mode.
> egress-proto { gtp | gtp-pmip | pmip } [ egress-context name [ egtp-service name ] [ mag-service name ] ]
> Associates and configures the egress protocol for this S-GW service.
> gtp: Specifies that GTP is to be used for the S-GW service egress.
> gtp-pmip: Specifies that either GTP or PMIP is to be used for the S-GW service egress.
> pmip: Specifies that PMIP is to be used for the S-GW service egress.
> egress-context name: Specifies that the context in this keyword is to be used for the S-GW service egress. name must be an existing context on this system and be from 1 to 63 alpha and/or numeric characters.
> egtp-service name: Specifies that the service in this keyword is to be used for the S-GW service egress. name must be an existing eGTP service on this system and be from 1 to 63 alpha and/or numeric characters.
> mag-service name: Specifies that the service in this keyword is to be used for the S-GW service egress. name must be an existing MAG service on this system and be from 1 to 63 alpha and/or numeric characters.
> ims-auth-service name
> Associates the S-GW service with an IMS authorization service configured in the same context. name must be an existing IMS auth service and be from 1 to 63 alpha and/or numeric characters.
> IMS authorization services are configured through the ims-auth-service command in the Context Configuration Mode.
> ingress egtp-service name
> Associates and configures the eGTP service ingress for this S-GW service. name must be an existing eGTP service on this system and be from 1 to 63 alpha and/or numeric characters.
> qci-qos-mapping name
> Associates the S-GW service with QCI to QoS mapping parameters. name must be an existing QCI-QoS mapping configuration and be from 1 to 63 alpha and/or numeric characters.
> QCI-QoS mapping is configured through the qci-qos-mapping command in the Global Configuration Mode.
> Usage
> Use this command to select a pre-configured QoS mapping and/or policy control and charging configuration to be used by the S-GW service.
> Example
> The following command associates the S-GW service with an IMS authorization service named ims-23:
> associate ims-auth-service ims-23
> egtp-service
> Configures an eGTP service to use as either an ingress (S1-U) or egress (S5/S8) service for the S-GW.
> Product
> S-GW
> Privilege
> Administrator
> Syntax
> egtp-service { egress { context name | service name } | ingress service name }
> no egtp-service { egress { context | service } | ingress service }
> no
> Removes the selected EGTP service from this service.
> egress { context name | service name }
> Specifies the egtp-service to be used as the egress eGTP service on a GTP based S5/S8 interface.
> context name: Specifies the name of the context where the eGTP service resides. name must be from 1 to 63 alpha and/or numeric characters and be an existing context name where an eGTP service resides.
> Caution: context name is not supported in this release.
> service name: Specifies the name of the egress eGTP service. name must be from 1 to 63 alpha and/or numeric characters and be an existing eGTP service name.
> ingress service name
> Specifies the egtp-service to be used as the ingress eGTP service on the S11 interface. name must be from 1 to 63 alpha and/or numeric characters and be an existing eGTP service name.
> Usage
> Use this command to configure the eGTP service to use with this S-GW service. The eGTP service must be existing and be configured with the appropriate parameters supporting the intended service type.
> Example
> The following command configures the S-GW service to use an eGTP service named s1u-egtp as it’s ingress service:
> egtp-service ingress service s1u-egtp
> end
> Exits the current mode and returns to the Exec Mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> end
> Usage
> Change the mode back to the Exec mode.
> exit
> Exits the current mode and returns to the previous mode.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> exit
> Usage
> Return to the previous mode.
> gtpu-error-ind
> Configures the actions to be taken upon receiving a GTP-U error indication from an eNodeB or P-GW.
> Product
> S-GW
> Privilege
> Administrator
> Syntax
> gtpu-error-ind { s1u { local-purge | page-ue [ custom1-behavior ] } | s5u { local-purge | signal-peer } }
> default gtpu-error-ind { s1u | s5u }
> default
> Rests the command to the default action for the specified interface. For S1-U, page-ue is the default action. For S5-U, local-purge is the default action.
> s1u { local-purge | page-ue [ custom1-behavior ] }
> Specifies the action to take when a GTP-U error indication is received from an eNodeB over the S1-U interface.
> local-purge: The S-GW clears the affected bearer (or PDN if error-ind is received on default bearer) locally without informing peer.
> page-ue [ custom1-behavior ]: The S-GW moves the complete UE state to S1-Idle and starts paging for this UE. If the custom1-behavior option is specified, the S-GW will guard the paging attempt with a timer of 60 seconds. Within this time the bearer must have the eNodeB TEID refreshed by an MME. Otherwise, the S-GW will clear the affected bearer with signaling. This is the default action for GTP-U error indication messages received on the S1-U interface.
> s5u { local-purge | signal-peer }
> Specifies the action to take when a GTP-U error indication is received from a P-GW over the S5-U interface.
> local-purge: The S-GW clears the affected bearer (or PDN if error-ind is received on a default bearer) locally without informing the peer. This is the default action for GTP-U error indication messages received on the S5-U interface.
> signal-peer: The S-GW initiates control signalling towards the peer MME and P-GW. When signalling:

> • | For a bearer deletion, the S-GW sends a Delete-Bearer-Command message to the P-GW and a Delete-Bearer-Request (with EBI) message to the MME.

> • | For PDN deletion, the S-GW sends a Delete-Session-Request message to the P-GW and a Delete-Bearer-Request (with LBI) message to the MME.

> • | The S-GW will not wait for Delete replies from the peer. The request will be sent only once and local resources will be reset.

> Usage
> Use this command to specify the action to taken upon receiving a GTP-U error indication from either an eNodeB across an S1-U interface or from a P-GW across an S5-U interface.
> Example
> The following command sets the action to take upon receipt of a GTP-U error indication from the eNodeB to clear affected bearer:
> gtpu-error-ind s1u local-purge
> mag-service
> Identifies the Mobile Access Gateway (MAG) egress service through which calls are to be routed for this S-GW service.
> Product
> S-GW
> Privilege
> Administrator
> Syntax
> mag-service egress service name
> no mag-service egress service
> no
> Removes the configured MAG egress service from this service.
> egress service name
> Specifies the MAG service name to be used as the egress MAG service on a PMIP based S5/S8 interface. name must be an existing MAG service and be from 1 to 63 alpha and/or numeric characters.
> Usage
> Use this command to specify the name of the MAG service where calls are to be routed.
> Example
> The following command specifies that an existing MAG service named mag3 is to be used to route call through for this S-GW service:
> mag-service egress service mag3
> path-failure
> Configures the action to take upon the occurrence of a path failure between the S-GW and the MME, P-GW, or eNodeB.
> Product
> S-GW
> Privilege
> Administrator
> Syntax
> path-failure { s11 | s1u | s5 | s5u } ( local-purge | signal-peer }
> default path-failure { s11 | s1u | s5 | s5u }
> default
> Returns the command to the default setting of “local purge” for the selected interface.
> { s11 | s1u | s5 | s5u }
> Specifies the interface to which the action will be applied.
> s11: Indicates that the path failure action is to be applied to the S11 interface between the S-GW and the MME.
> s1u: Indicates that the path failure action is to be applied to the S1-U interface between the S-GW and the eNodeB.
> s5: Indicates that the path failure action is to be applied to the S5 interface between the S-GW and the P-GW.
> s5u: Indicates that the path failure action is to be applied to the S5-U interface between the S-GW and the P-GW.
> ( local-purge | signal-peer }
> Specifies the action to apply to the selected interface.
> local-purge: The S-GW clears the affected bearer (or PDN if path failure is received on a default bearer) locally without informing the peer. This is the default action for all interface.
> signal-peer: The S-GW initiates control signalling towards the peer MME and P-GW. When signalling:

> • | For a bearer deletion, the S-GW sends a Delete-Bearer-Command message to the P-GW and a Delete-Bearer-Request (with EBI) message to the MME.

> • | For PDN deletion, the S-GW sends a Delete-Session-Request message to the P-GW and a Delete-Bearer-Request (with LBI) message to the MME.

> • | The S-GW will not wait for Delete replies from the peer. The request will be sent only once and local resources will be reset.

> Usage
> Use this command to specify the type of action to take when a path failure occurs on one of the supported interfaces.
> Example
> The following command sets the path failure action for the S5 interface to “signal peer”:
> path-failure s5 signal-peer

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883