Proxim AP-2500 User Manual
128
Public Space Parameters
AAA Messages – XML
Bill Mirror
DHCP
Message
Meaning
USG_AAA: 4007 AAA_Interface added_by_administrator
00:50:04:29:37:56 Exp_time:24 hrs 0 min
00:50:04:29:37:56 Exp_time:24 hrs 0 min
User added
USG_AAA: 4800 AAA_XML Memory_updated__State_valid
00:50:04:29:37:56
00:50:04:29:37:56
Update Cache executed
USG_AAA: 4006 AAA_Interface
Removed_by_administrator a
Removed_by_administrator a
User Delete issued for user a
Message
Meaning
RMTLOG: rmtlogXmlTcpSend: Connect error
Bill Mirror enabled, but the server does not respond
RMTLOG: rmtlogXmlTcpSend: transmission Ok
Bill Mirror enabled, and response received from server
Message
Meaning
DHCP: dhcpsStart: dst port (68) not DHCP server port
This indicates that there is another DHCP server on the
subscriber side of the AP.
subscriber side of the AP.
DHCP: dhcpsStart: Invalid DHCP options packet
This means that the client sent an invalid DHCP cookie. If
this is seen, it could mean data errors in network or a
non-compliant DHCP client.
this is seen, it could mean data errors in network or a
non-compliant DHCP client.
DHCP: dhcpsStart: invalid IP header
This could be caused by a non-compliant DHCP client or
data errors in the network.
data errors in the network.
DHCP: garbage_collect: dangling bind structure
bindptr->data = 0x3efdb14 cid = 0x000000000000 IP =
61.193.248.17 -- I
bindptr->data = 0x3efdb14 cid = 0x000000000000 IP =
61.193.248.17 -- I
The AP code attempts to clean up DHCP bindings that have
been turned off and a subscriber in the subscriber table
appears with the same IP address.
been turned off and a subscriber in the subscriber table
appears with the same IP address.
DHCP: icmp_check: BAD... conflict: Req: MAC
00-00-0E-FE-87-09; In SubTable: IP 219.103.171.66 MAC
00-05-02-CB-58-23
00-00-0E-FE-87-09; In SubTable: IP 219.103.171.66 MAC
00-05-02-CB-58-23
This happens if the DHCP lease the AP wants to hand out
already exists in the Subscriber table. If it does, then the AP
will skip this lease and go on to the next one.
already exists in the Subscriber table. If it does, then the AP
will skip this lease and go on to the next one.
DHCP: turnoff_bind: binding passed is NULL!
This can happen if the code tries to turn off a resource
because there's someone on the subscriber side that is
already using that address. In this case, if the resource does
not have a corresponding binding, this syslog will result.
because there's someone on the subscriber side that is
already using that address. In this case, if the resource does
not have a corresponding binding, this syslog will result.
DHCP: Warning: DHCPDISCOVER - No available
addresses in the pool.
addresses in the pool.
There are no more available leases in the DHCP server
lease pool and a DHCP request has been received.
lease pool and a DHCP request has been received.
WARNING DHCP: read_bind_db: can't find resource
usg13d733121 in nmhashtable
usg13d733121 in nmhashtable
This occurs if the DHCP Lease pool settings have been
changed in the AP and the lease is not part of the new pool.
changed in the AP and the lease is not part of the new pool.
usgDHCPInit: server and relay are OFF
DHCP Services have been disabled on the AP.