Oeb9fa331 Usn9810 v900r015c10 (Mme SGSN) Basic Service Configuration Issue1.00

USN9810 Basic Service Configuration
Confidential Information of Huawei. No Spreading Without Permission









 OMU boards are installed on basic subracks. The rear board of a switch board on the basic
subrack must be a TMI board.
 Basic subracks are central control nodes of the hardware of the USN9810.
 Basic subracks provide the operation and maintenance function, the clock source, and
Network Time Protocol (NTP) time synchronization.
 The logical subrack number of a basic subrack must be 0. No limitation is required on the
Rack number + Position number in the rack.
 Subrack T8280 cannot be cascaded to subrack T8290.

 All subracks except basic subracks are extension subracks.
 Extension subracks implement the service processing function.
 Extension subracks must be connected to basic subracks.






 OMU boards must be inserted in slots 0 and 2 in a basic subrack.
 SWU/TMI boards must be configured during subrack configuration.
 SMM/SDM boards are configured according to the default configuration.
 Boards can be configured by running ADD BRD.
 ECU, EPU, EPUB and ESU boards cannot be inserted in adjacent slots.
 The ECU, EPU, EPUB and ESU board must be configured in pairs.
 The mapping of slots where a pair of ECU, EPU and EPUB boards is as follows: 0-2, 1-3,
4-8, 5-9, 10-12, and 11-13.
 ESU, SWUB1, and SWIB0/B1 can be configured in only subrack T8290. ECU, EPU, EPUB,
SWUA1, and SWIA0/A1 can be configured only in subrack T8280.
 ESU and ECU/EPU/EPUB cannot be used together within a subrack.













 Active and standby relationship:

 0 and 2;
 1 and 3;
 4 and 8;
 5 and 9;
 6 and 7;
 10 and 12;
 11 and 13;










 ADD BRD is used to add a board to a slot in a subrack. You can add front boards, back
boards and daughter boards at the same time or only front boards based on actual
conditions. When running this command to add a board, you may use the command to
add the hard disk, sensor, or network interface data at the same time.








 This command is used to add a process group to a pair of boards. A process group is a
combination of fixedly configured processes on a pair of boards and is used to quickly
configure process data on the boards.
 You must add process groups in the following sequence: OMP process group, LCP/UIP
process group, ECU/EPU/ESU/LIP process group.
 Process groups on each board must also be configured on its peer board in the same
subrack. A board can have only one peer board.






 Parameters:
 Subrack number :This parameter specifies the subrack number based on which the system
assigns the E1/T1 port or the E1/T1 channel of the STM-1 port. You can run LST
ET1PORT to obtain the parameter value.
 Slot number :This parameter specifies the slot number based on which the system assigns
the E1/T1 port or the E1/T1 channel of the STM-1 ports.
 Port type :This parameter specifies the port type based on which the system assigns the
E1/T1 port or the E1/T1 channel of the STM-1 port.
 Start port number :This parameter specifies the start E1/T1 port number.
 End port number :This parameter specifies the end E1/T1 port number.
 Configured TDM type :This parameter specifies the configured TDM type.
 Configured E1 frame format :This parameter specifies the E1 frame format. DF(DF) or
CRC4(CRC4).
 Configured E1 encode format :This parameter specifies the configured E1 coding format.
This parameter is valid only when Port type is set to E1_T1(E1/T1).

 Parameters:
 Clock source type :This parameter specifies a clock source data record and specifies the
type of a clock source.
 Clock source priority :This parameter specifies the priority of a clock source. Priority level 1
(highest)
 Clock subrack number :This parameter specifies a subrack where the specified line clock
source is located. This parameter is valid only when Clock source type is set to
LINE1(Line1) or LINE2(Line2).
 Clock slot number :This parameter specifies the number of the slot where the specified line
clock source is located.
 Clock port type :This parameter specifies the port type of the slot where the specified line
clock source is located.
 Clock port name :This parameter specifies the port name of the slot where the specified
line clock source is located.
 Clock port number :This parameter specifies the port number of the slot where the
specified line clock source is located.



 SET CLKMODE is used to set the clock mode of the TDM in a narrowband central subrack
when the actual configuration is inconsistent with the office planning.
 Parameters:
 Clock level :This parameter specifies the clock precision level. LEVEL2 or LEVEL3 .
 Work mode :This parameter specifies the clock work mode.
 AUTO(Auto): Automatic clock mode. The system selects the clock source
according to the priority level of the clock source. If the current clock source is
faulty, the system selects the clock source with the next highest priority as the
current clock source.
 MANUAL(Manual): Manual clock mode. An external clock source needs to be

specified as the current clock. The system does not change the clock source
automatically.
 FREE(Free): Free running mode. In free running mode the clock of the device itself
is selected as the current clock source. The clock precision is low.
 Clock source type :This parameter specifies the clock source type. This parameter is valid
only when Work mode is set to MANUAL(Manual).




 This command is used to query the operating status of the ports of back board (including
Electrical ethernet, Fiber ethernet, 10 gigabit fiber ethernet, FC port and ATM), front board
and switch board.

 DSP ET1PORT is used to query the status of an E1/T1 port or E1/T1 channel.




 Internal service network
 By means of the internal communication network, EPUs or ESUs can communicate

with each other. A board switchover packet to be transmitted between EPUs or ESUs
can be forwarded through the internal communication network.
Internal communication IP address consists of the internal network segment, slot

number, and subrack number (126 indicates subrack 0).
 For example, if the default internal communication network segment is 192.168.0.0,

the internal communication IP address of the EPU or ESU installed in subrack 0 and slot
1 is 192.168.1.126. The length of the internal communication mask must be equal to
or smaller than 20.

 Each pair of EPUs act as routers to forward board-switchover packets between the ECU
and other EPUs.
 Each pair of ESU/ESUBs act as routers to forward board-switchover packets between the
ESU/ESUBs.
 IP addresses of ports on all EPUs or ESU/ESUBs cannot be in the same segment. (Only the
primary and secondary IP addresses of the same ATM port can be in the same segment.)

 If an IP network segment is defined as a public network segment, the port IP addresses of

different EPUs or ESUs can be in the IP segment. However, the port IP addresses of the
paired EPUs cannot be in the same segment.
 After the port IP addresses of different EPUs are configured in the public network segment,
each EPU can communicate with remote devices over its own PFI port.

 Ethernet trunk is used when multiple Ethernet ports are bound to act as one logic port, over
which various route protocols and services can be implemented. The use of Ethernet trunk
helps improve reliability of the links, share the load, and increase the bandwidth.
 Restrictions:
The Ethernet trunk feature does not support configuring active and standby ports. That
is, two Ethernet trunk logical ports cannot be configured as active and standby ports,
respectively.
The Ethernet trunk feature does not support layer-2 link detection.
Ethernet trunk supports manual aggregation and static Link Aggregation Control
Protocol (LACP) but not dynamic LACP.
The upper-limit threshold for the UP port in Ethernet trunk cannot be configured.
All member links of the Ethernet trunk must be set to be the same data rate and
duplex mode.
Half-duplex is not supported in LACP.
The Ethernet trunk cannot be configured between different boards. All physical ports
in Ethernet trunk must be on the same board or the paired board.

 The VRF is a new technology used in the router of an IP network. With the VRF, multiple
instances of one route table can exist in the same router and functions simultaneously.
 With the VRF, routes of different services are separated; specifically, default routes are
isolated to simplify the route configuration on the USN9810.
 Networks over various service ports are isolated. Ports cannot visit one another to ensure
the data security.
 The VRF is applicable to all IP-supportive ports except for the OM port.
 Restrictions:
Network location of the USN9810 is mainly performed on the CE side not the IP
backbone network. Therefore, the VPN tunnel to the CE device is unnecessary. Only
routes are isolated.
Local IP addresses (including the port IP address and service IP address) cannot be
overlapped. Service of the same IP address on the local end must use the same VRF.



 The EPU or ESU has no Ethernet physical port but the PFI has. The port of the PFI is used to
connect to the external IP device. All packet service (PS) data are processed on the EPU or
ESU thorough the port of the PFI is used.
 The EPU or ESU transmits PS data over the port of the PFI.
 The following configurations use this topology as an example.


 The IP address of the EPU or ESU is a logical IP address. Set the port IP address to the IP
address of the PFI port. The IP address of the EPU or ESU displayed on an external IP
device is the destination IP address while the IP address of the PFI port is the next-hop IP
address.
 The IP address of the PFI must be within the same segment with the connected router.


 The SET IPCBASEIP command is used to set the base IP address for inter-EPU/ESU
communication.
 To meet the requirements of packet forwarding between EPUs or ESUs, a port IP address
and routes for communicating with other boards are created based on the base IP address
of the inter-EPU/ESU communication and logical locations of the boards.
 All EPUs or ESUs need to be restarted after the IP segment of the internal network is
modified.

 VRF is configured locally. The VRF name can be different from the Virtual Private Network
(VPN) on the peer end.
 VPN can to be configured on devices on the peer end while VRF is not configured on the
local end.

 This command is used to add an IP address to the service IP address pool of the
EPU/EPUB/ESU.
 Addresses used at the GTP-C, by the DNS or CDP must be IP addresses in the IP address
pool specific to the specified board. Different service interfaces are allowed to use the
same IP address or different IP addresses.
 A pair of active and standby EPUs/EPUBs/ESUs can be configured with up to 48 IPv4 or IPv6
addresses.

 This command is used to bind a board IP address to a virtual routing and forwarding (VRF).
A board IP address in the public network is added to a VRF so that the IP address is visible
only in this VRF. The address is inaccessible to other VRFs or the public network. So
services are separated.

 Active-standby ports indicate that two ports can act as active and standby ports mutually,
using the same port IP address.

address.

 This command is used to modify the attributes of a port, such as MTU(octet) and Work
mode.
Port type: This parameter specifies the type of the port to be modified. It is one of
the key parameters that identify the port.
Work mode: This parameter specifies the work mode of the port. For example, if this
parameter is set to Half-duplex, 10M/s, it indicates that the port works in 10 Mbit/s
half duplex mode.
MTU: This parameter specifies the maximum transmission unit of the port.

 Usually it is not allowed to set IP addresses of two EPU or ESU boards in one subnet. If
more than one EPU or ESU board and the same external node such as the GGSN user
panel are within one IP subnet, set this subnet as the public network segment. Therefore,
when setting the IP address for an EPU or ESU in this public network segment, there is no
indirect route between other EPU or ESU boards and the external equipment through the
IP address of this EPU or ESU board. That is, if an IP subnet is set as a public network
segment, then each EPU or ESU board must be configured with its own IP address to
connect to the external equipment.

 This command is used to bind an interface to a virtual routing and forwarding (VRF) so
that the interface is separated from the public network.
 Only the active port among the active and standby ports needs to be bound with the VRF.

 Requirement of interface IP address segment:

The IP addresses of an EPU or ESU must be in different network segments.
The IP address of an interface of the same type board does not include the IP address
of another interface, but the IP addresses of interfaces on the different EPU or ESU
boards can stay at the same public network segment.
The IP address segment of the EPU or ESU interface neither includes nor is included in
the public network segment, but they can stay at the same network segment.
The IP addresses of different EPU or ESU boards can be in the same network segment
only if this segment is a public network segment. You can configure a network
segment as a public network segment using ADD PUBNWIP.

 In fact, the parameter of dual active ports does not exist. Dual active ports indicate that
two independent ports are configured to act as two outlets of routes with the same
destination IP address, and act as each other's standby port at the route layer.

address.

 This command is used to modify the attribute of the port, such as the maximum
transmission unit (MTU ) and work mode.
PORTTYPE: This parameter indicates the type of the port to be modified, and is the
key parameter for identifying a port.
WORKMODE: This parameter indicates the work mode of the designated port to be
modified. If the work mode is set to 10M/S half-duplex, this port works in 10 Mbit/s
half-duplex mode.
MTU: This parameter indicates the maximum transmission unit over a port.

 Usually it is not allowed to set I addresses of two EPU or ESU boards in one subnet. If
more than one EPU or ESU board and the same external node such as the GGSN user
panel are within one IP subnet, set this subnet as the public network segment. Therefore,
when setting the IP address for an EPU or ESU in this public network segment, there is no
indirect route between other EPU or ESU boards and the external equipment through the
IP address of this EPU or ESU board. That is, if an IP subnet is set as a public network
segment, then each EPU or ESU board must be configured with its own IP address to
connect to the external equipment.

 Each active port needs to be bound with VRF.

 The IP addresses of an EPU or ESU must be in different network segments.
 The IP address of an interface of the same type board does not include the IP address of
another interface, but the IP addresses of interfaces on the different EPU or ESU boards can stay
at the same public network segment.
 The IP address segment of the EPU or ESU interface neither includes nor is included in the
public network segment, but they can stay at the same network segment.
 The IP addresses of different EPU or ESU boards can be in the same network segment only if
this segment is a public network segment. You can configure a network segment as a public
network segment using ADD PUBNWIP.




 The lower-limit threshold indicates that, when the number of member ports in the normal
state is smaller than this threshold, the state of the Ethernet trunk logical port turns to be
faulty. A value same to the number of member ports is recommended for this parameter.
 Static LACP is to perform parameter negotiation based on the LACP to select active links
for aggregation. Enabling LACP is recommended.
 LACP period indicates the time for the member ports to receive the LACP packets, and can
be set to 3s or 90s. 3s is recommended.
 MTU indicates the MTU for transmitting and receiving packets. After physical ports are
added to the Ethernet trunk port, the MTU is set based on the Ethernet trunk port.

 Generally, one Ethernet trunk port includes two member ports. In this example, one
member port is included in the Ethernet trunk port.

 Bind only the Ethernet trunk port not the member ports with VRF.

 The IP addresses of an EPU or ESU must be in different network segments.
 The IP address of an interface of the same type board does not include the IP address
of another interface, but the IP addresses of interfaces on the different EPU or ESU
boards can stay at the same public network segment.
 The IP address segment of the EPU or ESU interface neither includes nor is included in
the public network segment, but they can stay at the same network segment.
 The IP addresses of different EPU or ESU boards can be in the same network segment
only if this segment is a public network segment. You can configure a network
segment as a public network segment using ADD PUBNWIP.



 This command is used to configure the default IP route of the EPU or ESU. IP packets are
transmitted over the default route of the EPU or ESU.

 In this example, the dynamic OSPF route is configured based on IP address of dual active
ports.


 Negotiation parameters are configured according to the network plan.
 If parameters such as the area, area type, network type, hello, dead, and authentication
mode and password are inconsistent with those on the peer device, the OSPF
interoperation will fail.
 Port cost must also be consistent with that on the peer device.

 USN9810 supports multi-process OSPF.
 ADD OSPFPRCSS is used to configure the OSPF process ID. Multiple processes are
supported in OSPF. Different OSPF processes are independent from one another.
Interaction between routes of different OSPF processes is equivalent to the interaction
between routes of different route protocols. One process can involve multiple ports while
one port only belongs to one OSPF process. Multiple processes can be used to isolate
route areas over different ports.
 The VRF of an OSPF process is configured according to the local network plan.

 USN9810 supports multi-process OSPF.
 ADD OSPFPRCSS is used to configure the OSPF process ID. Multiple processes are
supported in OSPF. Different OSPF processes are independent from one another.
Interaction between routes of different OSPF processes is equivalent to the interaction
between routes of different route protocols. One process can involve multiple ports while
one port only belongs to one OSPF process. Multiple processes can be used to isolate
route areas over different ports.
 The VRF of an OSPF process is configured according to the local network plan.

 This command is used to add an OSPF area. It can also used to configure the
authentication type and area type for this area. If an authentication type is configured for
a specified OSPF area, all interfaces in this area use this authentication type.
 To use the OSPF protocol, run this command to add an OSPF area to which the devices
belong based on the network plan.
 This command should be executed before ADD OSPFNW is executed.

 To configure an OSPF network corresponding to a port, set the segment address to the IP
address of the segment over the port, and the IP address wildcard to the complement on
the mask of the segment over the port.
 To configure an OSPF network corresponding to a board IP address, set the segment

address to the board IP address, and the IP address wildcard to 0.

 This command is used to set the attributes of an OSPF interface on an EPU, EPUB and ESU.
The interface attributes include the interval at which the interface sends Hello packets,
time before which a Hello packet becomes invalid, cost for the interface to send packets,
interface priority, network type, and retransmission interval.

 This command is used to add authentication to an interface running the OSPF protocol.
The OSPF interface authenticates the received OSPF packets using the configured
authentication type. Only the authenticated packets can be handled and the
authentication information will be added to the authenticated packets to be sent.
 This command applies to the scenario where all interfaces in an OSPF area use the
authentication type configured for this area to authenticate packets but you need to
specify another authentication type for a specific interface.
 When interface authentication and area authentication are both configured, interface
authentication is preferentially used to establish OSPF neighbors.

 The subrack number and slot number in the ping command is the subrack number and slot
number of the active EPU or ESU.
 If a test is performed to check whether the remote node is reachable, the destination IP
address is the service IP address of the network element (NE) on the peer end, the source
IP address is the IP address of the EPU or ESU on the local end (default configuration), and
VRF is the VRF of the source IP address on the local end.
 If a test is performed to check whether the connected 0neighboring device is reachable,

the destination IP address is the port IP address of the peer device, the source IP address is
the port IP address on the local end, and VRF is the VRF of the source IP address on the
local end.
 If a test is performed to check whether a fragmented packet can reach the device on the
peer end, the packet length in the ping command is equal to or larger than the MTU over
the port.




 Resolves the IP address of the GGSN based on APN during the PDP activation.
 Resolves the IP address of the peer SGSN based on RAI during the inter-SGSN RAU.
 Resolves the IP address of the peer SGSN based on the target RNC ID during the
relocation.

 Resolve TAI or APN during an EPS attach or PDN connection procedure to obtain the IP of
the S-GW and P-GW.
 Resolve the TAI during a TAU on the new MME to obtain the IP of the S-GW.
 Resolve the GUTI during a attach or TAU on the new MME to obtain the IP of old MME.
 Resolve the new TAI in the handover procedure to obtain the IP of the new S-GW or new
MME.



 NAPTR: naming authority pointer
 FQDN: fully qualified domain name







 This command is used to add a DNS server. The DNS server is dedicated to resolving
domain names on a network.
 A maximum of 38 DNS server groups can be added, and a maximum of 6 DNS servers can
be configured in each group.
 During the DNS query, if no corresponding DNS server group can be found based on the
matching principle configured in ADD DNSQ, DNS server group 0 will be used for query by
default. If no DNS server is configured in group 0, the query fails.

 This command is used to bind a DNS client IP address to a DNS entity for communicating
with a DNS server.
 If only one local port number is configured for DNS purpose in the entire system, this
command needs to be executed.
 One DNS client IP address can be bound to only one ECU/ESU, and the IP address must
have been added by running ADD DNSCLTIP.
 This command cannot be executed if the local port number has been added by running
ADD SIGLOCPORT.

 This command is used to add one or more local port numbers for implementing DNS
functions.
 In multi-port mode, one port number needs to be configured for each pair of ECUs or
ESUs. Different pairs of ECUs or ESUs have different ports.
 This command can be executed only when there is no data configured in the
BINDDNSCLTIP (LST BINDDNSCLTIP) table.

 This command is used to set the parameters related to DNS resolution, including the
response waiting period and number of retransmission attempts. Based on these
parameters, the DNS resolver (an entity responsible for resolving domain names in the SPP
process) sends resolution requests to the DNS server to obtain the corresponding IP
addresses.
 Generally, DNS related parameters do not need to be modified.





 This command is used to add IPv4 address information for an NE.
 If a domain name is configured with multiple IP addresses, domain name resolution

records are sorted by PRIORITY and WEIGHT:
 A host name can correspond to a maximum of 64 IP addresses. At least one of these IP

addresses must be a valid IP address in [1.0.0.0,255.255.255.254].
 The information of IP addresses configured for a domain name must be all configured
either on the USN9810 or on the DNS server.


 This command is used to configure a mapping relationship between a fully qualified

domain name (FQDN) and an NE.
 The S-GW, P-GW, or MME needs to be selected and the IP addresses of these NEs need to
be resolved during an attach, PDN connection setup, tracking area update (TAU), or
handover procedure.





 The time synchronization procedure is as follows:

 The NTP client sends an NTP data packet with a time synchronization request to
the NTP server. The data packet contains the timestamp when the data packet
leaves the NTP client. For example, the timestamp is 10:00:00 a.m., as shown in
above figure.
 When the NTP data packet reaches the NTP server, the NTP server adds the
timestamp 10:00:03 a.m that it receives the packet to this data packet.
 The NTP server sends the received data packet to the NTP client and adds the
timestamp (10:00:05 a.m.) of that the server sends the packet.
 When the NTP client receives the response data packet from the NTP server, the
NTP client adds a new timestamp, that is, 10:00:04 a.m.











Oeb9fa331 Usn9810 v900r015c10 (Mme SGSN) Basic Service Configuration Issue1.00

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oeb9fa331 Usn9810 v900r015c10 (Mme SGSN) Basic Service Configuration Issue1.00

Uploaded by

Copyright:

Available Formats

USN9810 Basic Service Configuration

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Subrack T8280 cannot be cascaded to subrack T8290.

Confidential Information of Huawei. No Spreading Without Permission

 All subracks except basic subracks are extension subracks.

 Extension subracks implement the service processing function.

 Extension subracks must be connected to basic subracks.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 OMU boards must be inserted in slots 0 and 2 in a basic subrack.

 SWU/TMI boards must be configured during subrack configuration.

 SMM/SDM boards are configured according to the default configuration.

 Boards can be configured by running ADD BRD.

 ESU and ECU/EPU/EPUB cannot be used together within a subrack.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Active and standby relationship:

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission