No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Swap from MA5200G to ME60 make accident to static user

Publication Date:  2012-07-27 Views:  128 Downloads:  0
Issue Description
After Migration were done from MA5200G to ME60 , Customer complain that some service is Down,

In fact, Customer use the folowing topology

Alarm Information

Handling Process
Here is the ip-pool of VoIP, the MSAN ip address Manually configured in MSAN (without dhcp) is included in section 5 that pool :

The old configuration in MA5200G:

ip pool ngn bas local
vpn-instance NGN
section 0
section 1
section 2
section 3
section 4
section 5


static-user gateway vpn-instance NGN domain-name ngn

To solve that issue on ME60, we should make additional specific commands (not like MA5200G wich can accept directly MSAN traffic:

 Add IP and ARP Trigger on the sub-interface, in BAS mode , of BRAS:

Root Cause
For VOIP Service, clients use DHCP to get IP addresses from ME60, ME60 act as DHCP Server,
But for MSAN, some kind of users (TDM Clients) and also management of the MSAN : they use a static ip configured in MSAN, that’s means that for this IP, the MSAN don’t send DHCP Request to ME60 to get it, but it’s already configured, (this ip address of the MSAN are included inside the DHCP Ip pool on the ME60), so only arp/ip packet is sent.
But ME60 and MA5200G have different default behavior of command "arp-trigger", ME60 default to close this function while MA5200G default to enable it.

The Static user that his ip belong to DHCP Pool behavior is different between MA5200G and ME60 , more configuration and attention is required in ME60.