Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Creating Grouped Configurations for the SRC 3GPP Gy (SRC CLI)

    Configuration groups enable you to share SRC's Gy configuration with different SRC's Gy instances in the SRC network. You can also set up different configurations for different instances.

    You can then create a grouped SRC's Gy configuration that is shared among multiple SRC's Gy instances. For example, if you create two different SRC's Gy groups called 3gpp-gy-share and 3gpp-gy-share1 within the shared SRC's Gy configuration, you could select SRC's Gy configuration that should be associated with a particular SRC's Gy instance.

    Use the shared option of the slot number gy-3gpp statement to select the group for an SRC's Gy instance as part of the local configuration. Use the shared gy-3gpp group name configuration statements to configure the group.

    To select and configure a group:

    1. From configuration mode, select a group for an SRC's Gy instance. For example, to select a group called 3gpp-gy-share in the root group:
      [edit]user@host# set slot 0 gy-3gpp shared /3gpp-gy-share
    2. Commit the configuration.
      [edit]user@host# commit commit complete.
    3. From configuration mode, configure a group. For example, to configure a group called 3gpp-gy-share, specify the group as part of SRC's Gy configuration.
      [edit]user@host# edit shared gy-3gpp group 3gpp-gy-share
    4. (Optional) Verify your configuration.
      [edit shared gy-3gpp group 3gpp-gy-share]
      user@host# show 
      configuration { 
        nic-proxy-configuration { 
          sessionHdl {
            resolution { 
              key-type SessionHandle;
              resolver-name /realms/sessionHandle/A1;
              value-type SaeId;
            }
            test-nic-bindings { 
              key-values {
                ANY_KEY corbaloc::127.0.0.1:8801/SAE;
              }
              use-test-bindings;
            }
          }
        }
        subscriber-types { 
          session-handle {
            nic-proxy sessionHdl;
            subscriber-id-type session-handle;
          }
        }
      }
      

    Modified: 2015-06-17