Cisco Cisco ASR 5000
RIM Message Transfer from BSC or RNC to eNodeB
▀ Configuring RIM Msg Transfer to or from eNodeB
▄ SGSN Administration Guide, StarOS Release 18
Configuring RIM Msg Transfer to or from eNodeB
To enable successful RIM message transfer to/from an eNodeB, the following must be included in the SGSN's
configuration:
configuration:
Configuring RIM functionality to work on SGSN
Associating previously configured SGTP and IuPS services
Configuring the peer-MME's address, in one or both of two ways
Configuring the peer-MME address locally
Configuring the DNS server
Configuring RIM Functionality
The following command sequences are used to enable RAN information management (RIM) functionality on the SGSN.
The order in which these two configurations are performed is not significant.
The order in which these two configurations are performed is not significant.
The first command sequence enables RIM for the entire SGSN (global level).
configure
sgsn-global
ran-information-management
end
The second command sequence associates the RNC configuration, the part of the IuPS service configuration governing
the SGSN communication with any RNC, needs to have the RIM functionality enabled.
the SGSN communication with any RNC, needs to have the RIM functionality enabled.
configure
context context_name
iups-service service_name
rnc id rnc_id
ran-information-management
end
Associating Previously Configured SGTP and IuPS Services
The SGTP service configuration is a mandatory part of the SGSN's setup (refer to Configuring an SGTP Service in the
SGSN Administration Guide), so an SGTP service configuration must already exist. The SGTP service is needed to
send and/or receive GTPv1 protocol messages.
SGSN Administration Guide), so an SGTP service configuration must already exist. The SGTP service is needed to
send and/or receive GTPv1 protocol messages.
It is also a good idea to associate the IuPS service for the SGSN service to use for communication with the RAN.