> MME-HSS Service Configuration Mode Commands
> The MME-HSS Service Configuration Mode is used to create and manage the HSS servers on Diameter protocol.
> diameter dictionary
> Specifies the Diameter Credit Control dictionary for the MME-HSS service.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> diameter dictionary { custom1 | standard }
> default diameter dictionary
> default
> Sets the dictionary to default for HSS service.
> custom1
> Default: Disabled
> This keyword sets the Diameter dictionary to customer specific dictionary. This is a customer specific diameter dictionary.
> standard
> Default: Enabled
> This keyword sets the Diameter dictionary to Standard dictionary. This is standard MME-HSS dictionary.
> Usage
> Use this command to select the Diameter dictionary for MME-HSS service.
> Example
> The following command sets the Diameter dictionary to IETF RFC 4006 specific:
> diameter dictionary standard
> diameter endpoint
> This commands associates a preconfigured Diameter origin endpoint with this MME-HSS service to manage S6a interface between MME and HSS.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> [ no ] diameter endpoint endpoint_name [-noconfirm]
> no
> Removes previously associated Diameter origin endpoint from this MME-HSS service.
> endpoint_name
> This is a preconfigured Diameter endpoint in Context configuration mode. The endpoint must be present in all Diameter messages and is the endpoint that originates the Diameter message.
> endpoint_name must be an preconfigured diameter endpoint name.
> If named endpoint is not configured earlier the system will create it and switch to the Diameter Endpoint Configuration mode in Context Configuration mode.
> -noconfirm
> Indicates that the command is to execute without any additional prompt and confirmation from the user.
> Warning: If this keyword option is used with no diameter endpoint endpoint_name command the Diameter endpoint named endpoint_name will be deleted with all active/inactive subscribers without prompting any warning or confirmation.
> Usage
> Use this command to associated a Diameter origin endpoint to create Diameter-based S6a interface in this MME-HSS service to provide AAA functionality to EPS bearer context.
> If named endpoint is not configured earlier the system will create it and switch to the Diameter Endpoint Configuration mode in Context Configuration mode.
> Refer Diameter Endpoint Configuration Mode Commands chapter for more information on Diameter endpoint configuration parameters.
> Example
> The following command associates the preconfigured Diameter endpoint hss_1 with this MME-HSS service for S6a interface support.
> diameter endpoint hss_1
> If named endpoint is not configured earlier the system will create it and switch to the Diameter Endpoint Configuration mode in Context Configuration mode and following prompt will appear:
> [context]host(config-ctx-diameter)#
> 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.
> failure-handling
> This command configures the failure handling behavior in the event of a failure with the MME-HSS service. It also defines the action on various error codes on Diameter interface during authentication or session activities.
> Product
> MME
> Privilege
> Security Administrator, Administrator
> Syntax
> failure-handling {authentication-information-request | check-identity-request | notify-request | purge-ue-request | update-location-request} { diameter-result-code start_error_code[to end_error_code] | request-timeout } action {continue | retry-and-terminate | terminate }
> no failure-handling {authentication-information-request | check-identity-request | notify-request | purge-ue-request | update-location-request} diameter-result-code start_error_code [to end_error_code]
> default failure-handling {authentication-information-request | check-identity-request | notify-request | purge-ue-request | update-location-request} request-timeout
> no
> Removes the preconfigured failure handling procedures for MME calls in an MME-HSS service.
> default
> Sets the default action for failure handling procedure for MME calls in an MME-HSS service.
> For default actions on Diameter result/error codes see Usage section of this section.
> authentication-information-request
> This keyword configures the MME-HSS service to handle the failures in Auth-Information-Request message.
> check-identity-request
> This keyword configures the MME-HSS service to handle the failures in Check-Identity-Information-Request message.
> notify-request
> This keyword configures the MME-HSS service to handle the failures in Notify-Request message.
> purge-ue-request
> This keyword configures the MME-HSS service to handle the failures in Purge-UE-Request message.
> update-location-request
> This keyword configures the MME-HSS service to handle the failures in Update-Location-Request message.
> diameter-result-code start_error_code [to end_error_code]
> This keyword configures the MME-HSS service to handle the failures for various request message having specific single or range of Diameter result code in request message.
> start_error_code specifies the individual error code on Diameter protocol and must be an integer from 3000 through 5999. This will be the starting of code if a range of error codes is specified with optional keyword to end_error_code.
> to end_error_code is used to specify a range of error codes to handle by this command. end_error_code specifies the end error code on Diameter protocol and must be an integer from 3000 through 5999.
> request-timeout
> This keyword configures the MME-HSS service to handle the failures for various request messages if response to that message is not received before timeout duration exhausted.
> action {continue | retry-and-terminate | terminate}
> This keyword specifies the action to be taken on failure of any message as policy of failure handling.

> • | continue: On receipt of any error, this action configuration will allow the MME-HSS service to continue with the session procedure without any interruption.

> • | retry-and-terminate: On receipt of any error, this action configuration will instruct the MME-HSS service to retry with the procedure. Sustem will retry up to the configured number of attempts and terminate the session/procedure if it received subsequent number of errors after retry attemps.

> • | terminate: This action configuration will allow the MME-HSS service to terminate the session procedure without any retry attemp on the event of any failure.

> Usage
> Use this command to configure the failure handling behavior in the event of a communication failure with the MME-HSS service.
> Following are the default action for Diameter result codes:
> For all protocol error codes 3000 to 3999 the default action is terminate. For all transient error codes 4000, 4001, 4004 to 4180, and 4182 to 4999 the default action is continue.
> For transient error codes 4002, 4003, and 4181 the default action is retry.
> For error code 4001 the default action is terminate.
> For permanent error codes 5000 to 5999 the default action is terminate
> Example
> The following command will allow MME-HSS service to continue if any failure in Auth-Information-Request message occurred with Diameter error code 3050:
> failure-handling authentication-information-request diameter-result-code 3050 action continue
> request timeout
> This command configures the application request timeout between MME-HSS service and HSS node. The MME system will wait for this duration before retransmitting the request to corresponding HSS node.
> Product
> MME
> Privilege
> Security Administrator, Administrator
> Syntax
> request timeout dur
> [ no | default ] request timeout
> no
> Disables the configured application request timeout value.
> default
> Sets the application request time out duration to default value of 300 seconds.
> dur
> Default: 300 seconds
> Specifies the application request timeout duration in seconds. The MME will wait for this duration before retrying the request with corresponding HSS.
> dur must be an integer from 1 through 300.
> Usage
> Use this command to set the waiting period for MME-HSS service in seconds after which the request is deemed to have failed or system will resend the request.
> Example
> The following example configures the application request timeout duration to 300 seconds:
> default request timeout
> test
> This command test the configured S6a interface between MME-HSS service and HSS server.
> Product
> MME
> Privilege
> Security Administrator, Administrator
> Syntax
> test s6a_inf_name
> [ no | default ] test
> no
> Removes the configured S6a test interface from this MME-HSS service.
> default
> Sets the S6a test interface to default interface configured from MME service.
> s6a_inf_name
> Specifies the name of the S6a interface which is to be used for testing the connectivity between MME and HSS node.
> s6a_inf_name is a preconfigured interface for S6a reference on system and must be an alpha and/or numerical string of 1 through 63 characters.
> Usage
> Use this command to set the S6a interface for testing between MME and HSSS node.
> Example
> The following command configures S6a test interface to s6a_1:
> test s6a_1

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