Configuring Multiple Bind Addresses on N3 Interface

To configure multiple bind addresses on the N3 interface, use the following sample configuration:

config 
   context context_name 
      gtpu-service service_name 
         bind { ipv4-address ipv4_address | ipv6-address ipv6_address [ bearer-type { non-ims-media | ims-media | all } ] } 
         exit 

NOTES:

  • bind { ipv4-address ipv4_address | ipv6-address ipv6_address } —Bind the GTPU service to the IPv4 address or IPv6 address on the N3 interface.

  • [ bearer-type { non-ims-media | ims-media | all } ] —Specify the type of bearer to be associated with the bind address. bearer-type allows three types of media traffic:

    • non-ims-media —Configure bind address for non-ims media only.

    • ims-media —Configure bind address for ims-media traffic only.

    • all —Configure bind address to handle all types of bearer traffic. This is the default behavior.

Note

If GTPU echo is enabled in GTPU service, the Echo request will be started with the first bind address configured in GTPU service. The bind address configuration is stored in the sorted list. As a result, the GTPU echo starts with the numerically lowest bind IP address.