User's Manual

U-NII Config & User Guide 5.2 Axxcelera Broadband Wireless
1. Make sure the MAC address is correct. Without the correct MAC address the SU
can not register. You can verify this by tailing the adapcs.log file. In this example an SU with
this MAC address is trying to register and is not found in the database, which means when you
created the object it had the wrong MAC address.
[root@cs1 /root]# tail -f /var/log/adapcs.log
CS[5494.8192](16Dec 12:48:34.926 ): Protocol: 00 00 00 00 01 00 00 01 00 14 00 04 00 c0 69 0b 58 7f b5 10
CS[5494.8192](16Dec 12:48:34.926 ): RegistrarProtocol: Registering SU 00c0690b587f (MID 1)
CS[5494.8192](16Dec 12:48:34.926 ): DynAccessPointImpl (CLIP_S AP): handleRegisterSU (SU 00c0690b587f)
CS[5494.8192](16Dec 12:48:34.926 ): DynAccessPointImpl (CLIP_S AP): no key - fetch details from EMSAgent
CS[5494.8192](16Dec 12:48:34.930 ): DynAccessPointImpl: CORBA::BAD_PARAM exception thrown (minor code=0)
CS[5494.8192](16Dec 12:48:34.930 ): DynAccessPointImpl: An SU is trying to register but I can't talk to an EMSAgent
CS[5494.8192](16Dec 12:48:34.931 ): DynAP (CLIP_S AP): Couldn't get details for registering SU 00c0690b587f
CS[5494.8192](16Dec 12:48:34.931 ): RegistrarProtocol: Deferring deregistration of MID 1
CS[5494.8192](16Dec 12:48:35.426 ): EMSProtocol: received message REGMSG_REGISTER_SU for CS
CS[5494.8192](16Dec 12:48:35.426 ): Protocol: message contents (20 bytes)
CS[5494.8192](16Dec 12:48:35.426 ): Protocol: 00 00 00 00 01 00 00 01 00 14 00 04 00 c0 69 0b 58 7f b5 10
CS[5494.8192](16Dec 12:48:35.426 ): RegistrarProtocol: SU 00c0690b587f is already registering
2. The management address must be on the same subnet as the atm0 interface on the
Control Server. This only applies for the management address.
3. Check that the PVCs are mapped correctly in the switch. Since the problem is
with the SU not registering, pay close attention to the registration (61) and management (280)
PVC mapping.
ADMIN Access_NGI>show pvc list id 0
ADMIN Access_NGI>
----------------------------------------------------------------------------
PVC ID IPort IVPI IVCI BW OPort OVPI OVCI BW
----------------------------------------------------------------------------
1 101 0 32 0 102 0 61 0
2 101 0 33 0 102 0 33 0
3 101 0 36 0 102 0 36 0
4 101 0 35 0 106 0 35 0
4. Make sure the Control Server has the created the proper atmarp entries in it. There
should be an atmarp entry for every management address.
• Lists atmarp entries
March 10, 2003 Company Confidential Page 58 of 149