forum.bitel.ru http://forum.bitel.ru/ |
|
Pon Eltex http://forum.bitel.ru/viewtopic.php?f=44&t=8318 |
Страница 1 из 1 |
Автор: | sergey-xxi [ 31 июл 2013, 19:26 ] |
Заголовок сообщения: | Pon Eltex |
Добрый день! Пытаемся сейчас настроить PonEltex+RedBack формат 82 опции отличается от d-link. Код: вот что присылает на сервер сейчас: Packet type: Access-Request Identifier: 83 Authenticator: {88 DF 74 AC 4C 05 AB 57 5F F6 1B 8D D2 A7 CE BE} Attributes: User-Name=00:1a:79:08:0b:1e NAS-Port-Id=2/3 clips 232027 NAS-Identifier=RedBack User-Password=Redback NAS-IP-Address=192.168.12.247 NAS-Port=33751040 Service-Type=5 NAS-Port-Type=5 Called-Station-Id=10.10.10.1 Platform-Type=4 UNKNOWN[2352-201]={01 0A 0A 0A 01} Medium-Type=11 Agent-Remote-Id={00 00 00 00 06 [u]A8 F9 4B 89 07 19[/u]} DHCP-Option={3D 3D 1F 49 6E 66 6F 6D 69 72 4D 41 47 32 35 30 2D 30 30 3A 31 61 3A 37 39 3A 30 38 3A 30 62 3A 31 65} Agent-Circuit-Id={21 09 00 00 00 00 01 00 00 00 [u]65[/u]} OS-Version=6.5.1.5 Mac-Addr=00-1a-79-08-0b-1e UNKNOWN[2352-125]={49 6E 66 6F 6D 69 72 4D 41 47 32 35 30} NAS-Real-Port=33751040 UNKNOWN[3561--1]={02 0D 00 00 00 00 06 A8 F9 4B 89 07 19} UNKNOWN[3561--1]={01 0D 21 09 00 00 00 00 01 00 00 00 65} Пытаемся сделать авторизацию по мак+id ONT В конфиге устройства прописываю следующее: Код: dhcp.option82.agentRemoteId.code=1 dhcp.option82.agentRemoteId.position=5 dhcp.option82.agentRemoteId.length=6 dhcp.option82.interfaceId.code=1 dhcp.option82.interfaceId.position=10 dhcp.option82.interfaceId.length=1 В логах пишет следующее: Код: Packet type: Access-Request Identifier: 253 Authenticator: {CC F6 D6 27 53 B8 6F 83 45 20 D7 A7 9C 78 9A 78} Attributes: User-Name=0000000006a8f94b890719:2109000000000100000065 NAS-Port-Id=2/3 clips 199652 NAS-Identifier=RedBack User-Password=Redback NAS-IP-Address=192.168.12.247 NAS-Port=33751040 Service-Type=5 Calling-Station-Id=001a79080b1e NAS-Port-Type=5 Called-Station-Id=10.10.10.1 Platform-Type=4 UNKNOWN[2352-201]={01 0A 0A 0A 01} Medium-Type=11 Agent-Remote-Id={00 00 00 00 06 A8 F9 4B 89 07 19} DHCP-Option={3D 3D 1F 49 6E 66 6F 6D 69 72 4D 41 47 32 35 30 2D 30 30 3A 31 61 3A 37 39 3A 30 38 3A 30 62 3A 31 65} Agent-Circuit-Id={21 09 00 00 00 00 01 00 00 00 65} OS-Version=6.5.1.5 Mac-Addr=00-1a-79-08-0b-1e UNKNOWN[2352-125]={49 6E 66 6F 6D 69 72 4D 41 47 32 35 30} NAS-Real-Port=33751040 UNKNOWN[3561--1]={02 0D 00 00 00 00 06 A8 F9 4B 89 07 19} UNKNOWN[3561--1]={01 0D 21 09 00 00 00 00 01 00 00 00 65} radius 07-31/16:27:10 DEBUG [rdsLstnr-p-9-t-9] RadiusProcessor - Create new radius session. radius 07-31/16:27:10 DEBUG [rdsLstnr-p-9-t-9] InetNas - agentRemoteId=java.nio.DirectByteBufferR[pos=0 lim=9 cap=9] radius 07-31/16:27:10 INFO [rdsLstnr-p-9-t-9] InetNas - AgentDevice not found. radius 07-31/16:27:10 DEBUG [rdsLstnr-p-9-t-9] InetNas - findServ agentDeviceRuntime=null radius 07-31/16:27:10 INFO [rdsLstnr-p-9-t-9] InetNas - Search serv on deviceId=2; interfaceId=0 radius 07-31/16:27:10 INFO [rdsLstnr-p-9-t-9] InetRadiusProcessor - [username=0000000006a8f94b890719:2109000000000100000065] InetServ not found. radius 07-31/16:27:10 INFO [rdsLstnr-p-9-t-9] InetRadiusProcessor - Return code=1 radius 07-31/16:27:10 INFO [rdsLstnr-p-9-t-9] InetRadiusProcessor - RESPONSE_BEFORE_POSTPROCESS: или в нашей версии биллинга данные опции еще не работают или можно как то по другому заставить биллинг работать с форматом опции eltex? |
Автор: | skn [ 31 июл 2013, 21:19 ] |
Заголовок сообщения: | Re: Pon Eltex |
надо бы в словарик(dictionary.xml) добавить аттрибуты для вашего вендора, для начала. типа Код: <vendor code="14988" name="Mikrotik">
<attribute name="Mikrotik-Recv-Limit" type="integer" code="1" /> <attribute name="Mikrotik-Xmit-Limit" type="integer" code="2" /> <attribute name="Mikrotik-Group" type="string" code="3" /> <attribute name="Mikrotik-Wireless-Forward" type="integer" code="4" /> <attribute name="Mikrotik-Wireless-Skip-Dot1x" type="integer" code="5" /> <attribute name="Mikrotik-Wireless-Enc-Algo" type="integer" code="6" /> <attribute name="Mikrotik-Wireless-Enc-Key" type="string" code="7" /> <attribute name="Mikrotik-Rate-Limit" type="string" code="8" /> <attribute name="Mikrotik-Realm" type="string" code="9" /> <attribute name="Mikrotik-Host-IP" type="ipaddr" code="10" /> <attribute name="Mikrotik-Mark-Id" type="string" code="11" /> <attribute name="Mikrotik-Advertise-URL" type="string" code="12" /> <attribute name="Mikrotik-Advertise-Interval" type="integer" code="13" /> <attribute name="Mikrotik-Recv-Limit-Gigawords" type="integer" code="14" /> <attribute name="Mikrotik-Xmit-Limit-Gigawords" type="integer" code="15" /> </vendor> |
Автор: | dm777 [ 01 авг 2013, 01:02 ] |
Заголовок сообщения: | Re: Pon Eltex |
Код: dhcp.option82.interfaceId.code=1 может должно быть не 1 а 2 ??? |
Автор: | zavndw [ 01 авг 2013, 03:52 ] |
Заголовок сообщения: | Re: Pon Eltex |
настраивали без интеграции с биллингом option82 с элтексом, да же работало:) |
Автор: | Alex-XXI [ 01 авг 2013, 12:29 ] |
Заголовок сообщения: | Re: Pon Eltex |
skn писал(а): надо бы в словарик(dictionary.xml) добавить аттрибуты для вашего вендора, для начала. А готового словаря для Элтекса у вас нет? Я думаю мы не первые занимаемся его интеграцией с БГБ. dm777 писал(а): Код: dhcp.option82.interfaceId.code=1 может должно быть не 1 а 2 ??? Возможно, но как видно из логов сервер не находит даже само устройство, до интерфейса думаю дело просто не доходит. Цитата: Код: radius 07-31/16:27:10 DEBUG [rdsLstnr-p-9-t-9] RadiusProcessor - Create new radius session. radius 07-31/16:27:10 DEBUG [rdsLstnr-p-9-t-9] InetNas - agentRemoteId=java.nio.DirectByteBufferR[pos=0 lim=9 cap=9] radius 07-31/16:27:10 INFO [rdsLstnr-p-9-t-9] InetNas - AgentDevice not found. radius 07-31/16:27:10 DEBUG [rdsLstnr-p-9-t-9] InetNas - findServ agentDeviceRuntime=null |
Автор: | skn [ 01 авг 2013, 13:29 ] |
Заголовок сообщения: | Re: Pon Eltex |
Alex-XXI писал(а): skn писал(а): надо бы в словарик(dictionary.xml) добавить аттрибуты для вашего вендора, для начала. А готового словаря для Элтекса у вас нет? Я думаю мы не первые занимаемся его интеграцией с БГБ. если бы, был бы, то давно добавили. ![]() |
Автор: | Alex-XXI [ 01 авг 2013, 13:47 ] |
Заголовок сообщения: | Re: Pon Eltex |
Думаю проблема со словарем никак не связана. Верней всего проблема в том, что Элтекс присылает опции Agent-Remote-Id и Agent-Circuit-Id другой длины и формата. У Длинка они соответственно 16 и 12 байт, а у Элтекса по 22 байта. Длинк: Код: Attributes: User-Name=64:70:02:71:37:a1 NAS-Port-Id=2/3 clips 197244 NAS-Identifier=RedBack User-Password=Redback NAS-IP-Address=192.168.12.247 NAS-Port=33751040 Service-Type=5 NAS-Port-Type=5 Called-Station-Id=10.21.24.1 Platform-Type=4 UNKNOWN[2352-201]={01 0A 15 18 01} Medium-Type=11 Agent-Remote-Id={00 06 00 12 CF 99 8C 40} DHCP-Option={3D 3D 07 01 64 70 02 71 37 A1} Agent-Circuit-Id={00 04 04 00 01 0C} OS-Version=6.5.1.5 Mac-Addr=64-70-02-71-37-a1 UNKNOWN[2352-125]={4D 53 46 54 20 35 2E 30} NAS-Real-Port=33751040 UNKNOWN[3561--1]={02 0A 00 06 00 12 CF 99 8C 40} UNKNOWN[3561--1]={01 08 00 04 04 00 01 0C} radius 07-31/13:16:22 INFO [rdsLstnr-p-9-t-1] InetRadiusProcessor - REQUEST_AFTER_PREPROCESS: Packet type: Access-Request Identifier: 157 Authenticator: {DB 00 50 02 6A 13 8E 33 F5 DE D5 8C 36 CE EF 4A} Attributes: User-Name=00060012cf998c40:00040400010c NAS-Port-Id=2/3 clips 197244 NAS-Identifier=RedBack User-Password=Redback NAS-IP-Address=192.168.12.247 NAS-Port=33751040 Service-Type=5 Calling-Station-Id=6470027137a1 NAS-Port-Type=5 Called-Station-Id=10.21.24.1 Platform-Type=4 UNKNOWN[2352-201]={01 0A 15 18 01} Medium-Type=11 Agent-Remote-Id={00 06 00 12 CF 99 8C 40} DHCP-Option={3D 3D 07 01 64 70 02 71 37 A1} Agent-Circuit-Id={00 04 04 00 01 0C} OS-Version=6.5.1.5 Mac-Addr=64-70-02-71-37-a1 UNKNOWN[2352-125]={4D 53 46 54 20 35 2E 30} NAS-Real-Port=33751040 UNKNOWN[3561--1]={02 0A 00 06 00 12 CF 99 8C 40} UNKNOWN[3561--1]={01 08 00 04 04 00 01 0C} radius 07-31/13:16:22 DEBUG [rdsLstnr-p-9-t-1] RadiusProcessor - Create new radius session. radius 07-31/13:16:22 DEBUG [rdsLstnr-p-9-t-1] InetNas - agentRemoteId=java.nio.DirectByteBufferR[pos=0 lim=6 cap=6] radius 07-31/13:16:22 INFO [rdsLstnr-p-9-t-1] InetNas - Found agentDevice:49 radius 07-31/13:16:22 DEBUG [rdsLstnr-p-9-t-1] InetNas - findServ agentDeviceRuntime=ru.bitel.bgbilling.modules.inet.runtime.device.InetDeviceRuntime@d11fa6 radius 07-31/13:16:22 INFO [rdsLstnr-p-9-t-1] InetNas - Search serv on deviceId=49; interfaceId=12 radius 07-31/13:16:22 INFO [rdsLstnr-p-9-t-1] InetRadiusProcessor - [username=00060012cf998c40:00040400010c] Authenticated as inetServId:3592 Элтекс: Код: Attributes:
User-Name=00:1a:79:08:0b:1e NAS-Port-Id=2/3 clips 196442 NAS-Identifier=RedBack User-Password=Redback NAS-IP-Address=192.168.12.247 NAS-Port=33751040 Service-Type=5 NAS-Port-Type=5 Called-Station-Id=10.10.10.1 Platform-Type=4 UNKNOWN[2352-201]={01 0A 0A 0A 01} Medium-Type=11 Agent-Remote-Id={00 00 00 00 06 A8 F9 4B 89 07 19} DHCP-Option={3D 3D 1F 49 6E 66 6F 6D 69 72 4D 41 47 32 35 30 2D 30 30 3A 31 61 3A 37 39 3A 30 38 3A 30 62 3A 31 65} Agent-Circuit-Id={21 09 00 00 00 00 01 00 00 00 65} OS-Version=6.5.1.5 Mac-Addr=00-1a-79-08-0b-1e UNKNOWN[2352-125]={49 6E 66 6F 6D 69 72 4D 41 47 32 35 30} NAS-Real-Port=33751040 UNKNOWN[3561--1]={02 0D 00 00 00 00 06 A8 F9 4B 89 07 19} UNKNOWN[3561--1]={01 0D 21 09 00 00 00 00 01 00 00 00 65} Attributes: User-Name=0000000006a8f94b890719:2109000000000100000065 NAS-Port-Id=2/3 clips 196442 NAS-Identifier=RedBack User-Password=Redback NAS-IP-Address=192.168.12.247 NAS-Port=33751040 Service-Type=5 Calling-Station-Id=001a79080b1e NAS-Port-Type=5 Called-Station-Id=10.10.10.1 Platform-Type=4 UNKNOWN[2352-201]={01 0A 0A 0A 01} Medium-Type=11 Agent-Remote-Id={00 00 00 00 06 A8 F9 4B 89 07 19} DHCP-Option={3D 3D 1F 49 6E 66 6F 6D 69 72 4D 41 47 32 35 30 2D 30 30 3A 31 61 3A 37 39 3A 30 38 3A 30 62 3A 31 65} Agent-Circuit-Id={21 09 00 00 00 00 01 00 00 00 65} OS-Version=6.5.1.5 Mac-Addr=00-1a-79-08-0b-1e UNKNOWN[2352-125]={49 6E 66 6F 6D 69 72 4D 41 47 32 35 30} NAS-Real-Port=33751040 UNKNOWN[3561--1]={02 0D 00 00 00 00 06 A8 F9 4B 89 07 19} UNKNOWN[3561--1]={01 0D 21 09 00 00 00 00 01 00 00 00 65} radius 07-31/15:05:12 DEBUG [rdsLstnr-p-9-t-9] RadiusProcessor - Create new radius session. radius 07-31/15:05:12 DEBUG [rdsLstnr-p-9-t-9] InetNas - agentRemoteId=java.nio.DirectByteBufferR[pos=0 lim=9 cap=9] radius 07-31/15:05:12 INFO [rdsLstnr-p-9-t-9] InetNas - AgentDevice not found. radius 07-31/15:05:12 DEBUG [rdsLstnr-p-9-t-9] InetNas - findServ agentDeviceRuntime=null radius 07-31/15:05:12 INFO [rdsLstnr-p-9-t-9] InetNas - Search serv on deviceId=2; interfaceId=0 radius 07-31/15:05:12 INFO [rdsLstnr-p-9-t-9] InetRadiusProcessor - [username=0000000006a8f94b890719:2109000000000100000065] InetServ not found. |
Автор: | Amir [ 01 авг 2013, 14:09 ] |
Заголовок сообщения: | Re: Pon Eltex |
А какой интерфейс у Элтекса здесь? Цитата: Agent-Circuit-Id={21 09 00 00 00 00 01 00 00 00 65}
|
Автор: | sergey-xxi [ 01 авг 2013, 16:21 ] |
Заголовок сообщения: | Re: Pon Eltex |
Agent-Remote-Id={00 00 00 00 06 A8 F9 4B 89 07 19} мак железки. Agent-Circuit-Id={21 09 00 00 00 00 01 00 00 00 65} id ONT( для каждого терминала он уникален ). |
Автор: | Amir [ 01 авг 2013, 19:08 ] |
Заголовок сообщения: | Re: Pon Eltex |
Без предобработки не получится, т.к. запросы приходят от SE и через конфиг не получится указать, что если так - один вариант парсить, этак - другой. Только сейчас наткнулись еще на один вариант, когда там строкой передается, поэтому в примере три варианта парсинга. |
Автор: | Amir [ 01 авг 2013, 19:08 ] |
Заголовок сообщения: | Re: Pon Eltex |
Код: package custom.bgbilling.modules.inet.dyn.device.redback;
import java.io.UnsupportedEncodingException; import java.util.Arrays; import org.apache.log4j.Logger; import ru.bitel.bgbilling.kernel.network.dhcp.DhcpPacket; import ru.bitel.bgbilling.kernel.network.dhcp.DhcpProtocolHandler; import ru.bitel.bgbilling.kernel.network.radius.RadiusPacket; import ru.bitel.bgbilling.kernel.network.radius.RadiusProtocolHandler; import ru.bitel.bgbilling.modules.inet.dhcp.InetDhcpProcessor; import ru.bitel.bgbilling.modules.inet.radius.InetRadiusProcessor; public class SmartEdgeClipsProtocolHandler extends ru.bitel.bgbilling.modules.inet.dyn.device.redback.SmartEdgeClipsProtocolHandler implements RadiusProtocolHandler, DhcpProtocolHandler { private static final Logger logger = Logger.getLogger( SmartEdgeClipsProtocolHandler.class ); private static final byte[] eltexRemoteIdHeader = new byte[] { 0, 0, 0, 0, 6 }; private static boolean checkEltexRemoteIdHeader( byte[] remoteId ) { if( remoteId.length < eltexRemoteIdHeader.length ) { return false; } for( int i = 0; i < eltexRemoteIdHeader.length; i++ ) { if( remoteId[i] != eltexRemoteIdHeader[i] ) { return false; } } return true; } @Override protected void setAgentOptions( RadiusPacket request ) { byte[] remoteId = request.getByteAttribute( radiusVendor, Agent_Remote_Id, null ); // dlink if( remoteId.length == 8 ) { logger.info( "Parse as DLink" ); super.setAgentOptions( request ); return; } byte[] circuitId = request.getByteAttribute( radiusVendor, Agent_Circuit_Id, null ); // eltex bytes if( checkEltexRemoteIdHeader( remoteId ) ) { logger.info( "Parse as eltex bytes" ); request.setOption( InetRadiusProcessor.AGENT_REMOTE_ID, Arrays.copyOfRange( remoteId, 5, 6 ) ); request.setOption( InetRadiusProcessor.AGENT_CIRCUIT_ID, circuitId ); return; } try { String circuitIdString = new String( circuitId, "UTF8" ); // eltex string if( circuitIdString.startsWith( "eltex" ) ) { logger.info( "Parse as eltex string" ); request.setOption( InetRadiusProcessor.AGENT_REMOTE_ID, new String( remoteId, "UTF8" ) ); request.setOption( InetRadiusProcessor.AGENT_CIRCUIT_ID, circuitIdString ); String devicePortString = circuitIdString.substring( 5 ); int devicePort = (Integer.parseInt( devicePortString ) - 320) % 8; request.setOption( InetRadiusProcessor.INTERFACE_ID, devicePort ); } return; } catch( UnsupportedEncodingException ex ) { logger.error( ex.getMessage(), ex ); } super.setAgentOptions( request ); } @Override public void preprocessDhcpRequest( DhcpPacket request, DhcpPacket response ) throws Exception { byte[] remoteId = request.getSubOption( (byte)2 ).value; // dlink if( remoteId.length == 8 ) { logger.info( "Parse as DLink" ); return; } byte[] circuitId = request.getSubOption( (byte)1 ).value; // eltex bytes if( checkEltexRemoteIdHeader( remoteId ) ) { logger.info( "Parse as eltex bytes" ); request.setOption( InetDhcpProcessor.AGENT_REMOTE_ID, Arrays.copyOfRange( remoteId, 5, 6 ) ); request.setOption( InetDhcpProcessor.AGENT_CIRCUIT_ID, circuitId ); return; } try { String circuitIdString = new String( circuitId, "UTF8" ); // eltex string if( circuitIdString.startsWith( "eltex" ) ) { logger.info( "Parse as eltex string" ); request.setOption( InetDhcpProcessor.AGENT_REMOTE_ID, new String( remoteId, "UTF8" ) ); request.setOption( InetDhcpProcessor.AGENT_CIRCUIT_ID, circuitIdString ); String devicePortString = circuitIdString.substring( 5 ); int devicePort = (Integer.parseInt( devicePortString ) - 320) % 8; request.setOption( InetDhcpProcessor.INTERFACE_ID, devicePort ); return; } } catch( UnsupportedEncodingException ex ) { logger.error( ex.getMessage(), ex ); } } } |
Автор: | Amir [ 01 авг 2013, 19:15 ] |
Заголовок сообщения: | Re: Pon Eltex |
У вас "Parse as eltex bytes" В конфигурации SE Код: dhcp.deviceSearchMode=0 radius.agent.option.removeHeader=2 radius.agent.option.remoteId.position=0 dhcp.option82.removeHeader=2 dhcp.option82.agentRemoteId.code=2 dhcp.option82.agentRemoteId.position=0 dhcp.option82.agentRemoteId.length=0 В конфигурации DLink Код: radius.agent.option.removeHeader=2 dhcp.option82.removeHeader=2 dhcp.option82.interfaceId.code=1 dhcp.option82.interfaceId.position=3 dhcp.option82.interfaceId.length=1 Если интерфейс = 0x65, то в конфигурации Eltex Код: radius.agent.option.removeHeader=0
dhcp.option82.removeHeader=0 dhcp.option82.interfaceId.position=10 dhcp.option82.interfaceId.length=1 |
Автор: | Amir [ 01 авг 2013, 19:18 ] |
Заголовок сообщения: | Re: Pon Eltex |
Цитата: Только сейчас наткнулись еще на один вариант, когда там строкой передается Вот по таким причинам и сложно настраивать Inet.
|
Автор: | Alex-XXI [ 01 авг 2013, 19:21 ] |
Заголовок сообщения: | Re: Pon Eltex |
Этот класс нужно добавить в динамический код или изменить какой-то из имеющихся? |
Автор: | Amir [ 01 авг 2013, 19:24 ] |
Заголовок сообщения: | Re: Pon Eltex |
Добавить, в примере специально другой пакет: custom.bgbilling..., т.к. ru.bitel перетираются при обновлении. |
Автор: | Alex-XXI [ 02 авг 2013, 13:19 ] |
Заголовок сообщения: | Re: Pon Eltex |
Пробовали вчера задействовать предложенную вами схему, но возникли проблемы. Опции определяются и обрезаются как надо, агентское устройство и порт определяется верно. Но на каждом договоре появилось огромное количество сессий продолжительностью несколько секунд, некоторые даже без ip-адресов(видимо все пулы быстро закончились). Поэтому пришлось возвращать все обратно, логи к сожалению снять не успели. |
Автор: | sergey-xxi [ 08 авг 2013, 23:55 ] |
Заголовок сообщения: | Re: Pon Eltex |
Настроили стенд, но сессия не стартует. Вот что пишит access Код: radius 08-08/21:59:38 INFO [rdsLstnr-p-9-t-6] RadiusListenerWorker - REQUEST: Packet type: Access-Request Identifier: 59 Authenticator: {58 50 9E 95 3D C3 14 CA 4B AC 43 41 01 80 02 04} Attributes: User-Name=00:1a:79:08:0b:1e NAS-Port-Id=2/1 vlan-id 2 clips 134716 NAS-Identifier=RedBack2 User-Password=Redback NAS-IP-Address=192.168.12.202 NAS-Port=553648130 Service-Type=5 NAS-Port-Type=5 Called-Station-Id=10.10.10.1 Platform-Type=4 UNKNOWN[2352-201]={01 0A 0A 0A 01} Medium-Type=11 Agent-Remote-Id={00 00 00 00 06 A8 F9 4B 89 07 19} DHCP-Option={3D 3D 1F 49 6E 66 6F 6D 69 72 4D 41 47 32 35 30 2D 30 30 3A 31 61 3A 37 39 3A 30 38 3A 30 62 3A 31 65} Agent-Circuit-Id={21 09 00 00 00 00 01 00 00 00 6E} OS-Version=11.1.2.7p2 Mac-Addr=00-1a-79-08-0b-1e UNKNOWN[2352-125]={49 6E 66 6F 6D 69 72 4D 41 47 32 35 30} NAS-Real-Port=553648130 UNKNOWN[3561--1]={02 0D 00 00 00 00 06 A8 F9 4B 89 07 19} UNKNOWN[3561--1]={01 0D 21 09 00 00 00 00 01 00 00 00 6E} radius 08-08/21:59:38 INFO [rdsLstnr-p-9-t-6] SmartEdgeClipsProtocolHandler - Parse as eltex bytes radius 08-08/21:59:38 INFO [rdsLstnr-p-9-t-6] InetRadiusProcessor - REQUEST_AFTER_PREPROCESS: Packet type: Access-Request Identifier: 59 Authenticator: {58 50 9E 95 3D C3 14 CA 4B AC 43 41 01 80 02 04} Attributes: User-Name=0000000006a8f94b890719:210900000000010000006e NAS-Port-Id=2/1 vlan-id 2 clips 134716 NAS-Identifier=RedBack2 User-Password=Redback NAS-IP-Address=192.168.12.202 NAS-Port=553648130 Service-Type=5 Calling-Station-Id=001a79080b1e NAS-Port-Type=5 Called-Station-Id=10.10.10.1 Platform-Type=4 UNKNOWN[2352-201]={01 0A 0A 0A 01} Medium-Type=11 Agent-Remote-Id={00 00 00 00 06 A8 F9 4B 89 07 19} DHCP-Option={3D 3D 1F 49 6E 66 6F 6D 69 72 4D 41 47 32 35 30 2D 30 30 3A 31 61 3A 37 39 3A 30 38 3A 30 62 3A 31 65} Agent-Circuit-Id={21 09 00 00 00 00 01 00 00 00 6E} OS-Version=11.1.2.7p2 Mac-Addr=00-1a-79-08-0b-1e UNKNOWN[2352-125]={49 6E 66 6F 6D 69 72 4D 41 47 32 35 30} NAS-Real-Port=553648130 UNKNOWN[3561--1]={02 0D 00 00 00 00 06 A8 F9 4B 89 07 19} UNKNOWN[3561--1]={01 0D 21 09 00 00 00 00 01 00 00 00 6E} radius 08-08/21:59:38 DEBUG [rdsLstnr-p-9-t-6] RadiusProcessor - Create new radius session. radius 08-08/21:59:38 DEBUG [rdsLstnr-p-9-t-6] InetNas - agentRemoteId=a8f94b890719 radius 08-08/21:59:38 INFO [rdsLstnr-p-9-t-6] InetNas - Found agentDevice:156 radius 08-08/21:59:38 DEBUG [rdsLstnr-p-9-t-6] InetNas - findServ agentDeviceRuntime=ru.bitel.bgbilling.modules.inet.runtime.device.InetDeviceRuntime@124ed52 radius 08-08/21:59:38 INFO [rdsLstnr-p-9-t-6] InetNas - Search serv on deviceId=156; interfaceId=110 radius 08-08/21:59:38 INFO [rdsLstnr-p-9-t-6] InetRadiusProcessor - [username=0000000006a8f94b890719:210900000000010000006e] Authenticated as inetServId:3676 radius 08-08/21:59:38 DEBUG [rdsLstnr-p-9-t-6] InetRadiusProcessor - MAC-address from request: radius 08-08/21:59:38 DEBUG [rdsLstnr-p-9-t-6] InetAccountingPeriodList - Create: radius 08-08/21:59:38 DEBUG [rdsLstnr-p-9-t-6] InetAccountingPeriodList - Create: script 08-08/21:59:38 INFO [rdsLstnr-p-9-t-6] ScriptEventListener - Caught event: ru.bitel.bgbilling.modules.inet.api.server.event.InetAccountingPeriodActivateEvent script 08-08/21:59:38 INFO [rdsLstnr-p-9-t-6] ScriptEventListener - Process time => 4 script 08-08/21:59:38 INFO [rdsLstnr-p-9-t-6] ScriptEventListener - Not enough money to open a period!! radius 08-08/21:59:38 DEBUG [rdsLstnr-p-9-t-6] InetServRuntime - Accounting period not found for inetServ:3676 radius 08-08/21:59:38 INFO [rdsLstnr-p-9-t-6] InetApplication - Accounting period not available radius 08-08/21:59:38 DEBUG [rdsLstnr-p-9-t-6] InetRadiusProcessor - AccessCode is 4. Set to disable realm (rejectToAccept) radius 08-08/21:59:38 INFO [rdsLstnr-p-9-t-6] InetRadiusProcessor - Write new waiting connection to DB radius 08-08/21:59:38 INFO [rdsLstnr-p-9-t-6] InetRadiusProcessor - New connection id=621016 radius 08-08/21:59:38 INFO [rdsLstnr-p-9-t-6] InetRadiusProcessor - Return code=0 radius 08-08/21:59:38 INFO [rdsLstnr-p-9-t-6] InetDhcpHelperProcessor - Put auth accept 157:156:110:001A79080B1E radius 08-08/21:59:38 INFO [rdsLstnr-p-9-t-6] InetRadiusProcessor - RESPONSE_BEFORE_POSTPROCESS: Packet type: Access-Accept Identifier: 59 Authenticator: {} Attributes: Reply-Message=4 Framed-IP-Address=10.10.10.84 DHCP-Max-Leases=1 Forward-Policy=in:HTTP-REDIRECT HTTP-Redirect-Profile-Name=NOAUTH Process time auth: 11 radius 08-08/21:59:38 DEBUG [rdsLstnr-p-9-t-6] ProcessorRequest - Sending to /192.168.12.202:1812 radius 08-08/21:59:38 INFO [rdsLstnr-p-9-t-6] InetRadiusListenerWorker - RESPONSE: Packet type: Access-Accept Identifier: 59 Authenticator: {39 75 4D FC B6 CE 44 08 B7 5C 69 9F 28 B0 1A CA} Attributes: Reply-Message=4 DHCP-Max-Leases=1 Forward-Policy=in:HTTP-REDIRECT HTTP-Redirect-Profile-Name=NOAUTH accounting Код: Authenticator: {A8 E3 90 31 66 4C 72 09 4D D7 36 6D E4 37 B6 79} Attributes: User-Name=00:1a:79:08:0b:1e NAS-Identifier=RedBack2 NAS-IP-Address=192.168.12.202 NAS-Port=553648130 Service-Type=5 Acct-Input-Octets=0 Acct-Output-Octets=0 Acct-Status-Type=2 Acct-Session-Time=0 Acct-Input-Packets=0 Acct-Session-Id=0100FFFF78000CAC-5203D33A Acct-Authentic=1 NAS-Port-Id=2/1 vlan-id 2 clips 134316 Acct-Terminate-Cause=17 Acct-Output-Packets=0 Event-Timestamp=1375982395 Acct-Output-Gigawords=0 Acct-Input-Gigawords=0 NAS-Port-Type=5 Called-Station-Id=10.10.10.1 Acct-Mcast-Out-Packets-64={00 00 00 00 00 00 00 00} Medium-Type=11 UNKNOWN[2352-201]={01 0A 0A 0A 01} Platform-Type=4 Agent-Remote-Id={00 00 00 00 06 A8 F9 4B 89 07 19} Session-Error-Msg=Authentication failure Agent-Circuit-Id={21 09 00 00 00 00 01 00 00 00 6E} Session-Error-Code=24 Acct-Output-Octets-64={00 00 00 00 00 00 00 00} Acct-Input-Octets-64={00 00 00 00 00 00 00 00} Acct-Output-Packets-64={00 00 00 00 00 00 00 00} Acct-Input-Packets-64={00 00 00 00 00 00 00 00} Acct-Mcast-In-Octets-64={00 00 00 00 00 00 00 00} Acct-Mcast-In-Packets-64={00 00 00 00 00 00 00 00} Acct-Mcast-Out-Octets-64={00 00 00 00 00 00 00 00} OS-Version=11.1.2.7p2 Mac-Addr=00-1a-79-08-0b-1e Acct-Mcast-In-Octets=0 Acct-Mcast-Out-Octets=0 Acct-Mcast-In-Packets=0 Acct-Mcast-Out-Octets=0 Acct-Mcast-In-Packets=0 NAS-Real-Port=553648130 Acct-Mcast-Out-Packets=0 UNKNOWN[3561--1]={02 0D 00 00 00 00 06 A8 F9 4B 89 07 19} UNKNOWN[3561--1]={01 0D 21 09 00 00 00 00 01 00 00 00 6E} radius 08-08/21:33:41 INFO [rdsLstnr-p-8-t-2] RadiusListenerWorker - RESPONSE: Packet type: Accounting-Response Identifier: 2 Authenticator: {19 AD 50 9A 2E C6 BF 7A EE 43 A4 9A 42 94 10 FB} Attributes: Process time start: 101 radius 08-08/21:33:41 INFO [rdsLstnr-p-8-t-9] update - REQUEST: Packet type: Accounting-Request radius 08-08/21:33:41 INFO [rdsLstnr-p-8-t-10] SmartEdgeClipsProtocolHandler - Parse as eltex bytes radius 08-08/21:33:41 INFO [rdsLstnr-p-8-t-10] InetRadiusProcessor - REQUEST_AFTER_PREPROCESS: Packet type: Accounting-Request Identifier: 13 Authenticator: {A8 E3 90 31 66 4C 72 09 4D D7 36 6D E4 37 B6 79} Attributes: User-Name=0000000006a8f94b890719:210900000000010000006e NAS-Identifier=RedBack2 NAS-IP-Address=192.168.12.202 NAS-Port=553648130 Service-Type=5 Acct-Input-Octets=0 Acct-Output-Octets=0 Acct-Status-Type=2 Acct-Session-Time=0 Acct-Input-Packets=0 Acct-Session-Id=0100FFFF78000CAC-5203D33A Acct-Authentic=1 NAS-Port-Id=2/1 vlan-id 2 clips 134316 Acct-Terminate-Cause=17 Acct-Output-Packets=0 Event-Timestamp=1375982395 Acct-Output-Gigawords=0 Acct-Input-Gigawords=0 Calling-Station-Id=001a79080b1e NAS-Port-Type=5 Called-Station-Id=10.10.10.1 Acct-Mcast-Out-Packets-64={00 00 00 00 00 00 00 00} Medium-Type=11 UNKNOWN[2352-201]={01 0A 0A 0A 01} Platform-Type=4 Agent-Remote-Id={00 00 00 00 06 A8 F9 4B 89 07 19} Session-Error-Msg=Authentication failure Agent-Circuit-Id={21 09 00 00 00 00 01 00 00 00 6E} Session-Error-Code=24 Acct-Output-Octets-64={00 00 00 00 00 00 00 00} Acct-Input-Octets-64={00 00 00 00 00 00 00 00} Acct-Output-Packets-64={00 00 00 00 00 00 00 00} Acct-Input-Packets-64={00 00 00 00 00 00 00 00} Acct-Mcast-In-Octets-64={00 00 00 00 00 00 00 00} Acct-Mcast-In-Packets-64={00 00 00 00 00 00 00 00} Acct-Mcast-Out-Octets-64={00 00 00 00 00 00 00 00} Acct-Mcast-Out-Octets-64={00 00 00 00 00 00 00 00} OS-Version=11.1.2.7p2 Mac-Addr=00-1a-79-08-0b-1e Acct-Mcast-In-Octets=0 Acct-Mcast-Out-Octets=0 Acct-Mcast-In-Packets=0 NAS-Real-Port=553648130 Acct-Mcast-Out-Packets=0 UNKNOWN[3561--1]={02 0D 00 00 00 00 06 A8 F9 4B 89 07 19} UNKNOWN[3561--1]={01 0D 21 09 00 00 00 00 01 00 00 00 6E} radius 08-08/21:33:41 INFO [rdsLstnr-p-8-t-10] InetNas - Found agentDevice:156 radius 08-08/21:33:41 INFO [rdsLstnr-p-8-t-10] InetNas - Search serv on deviceId=156; interfaceId=110 radius 08-08/21:33:41 WARN [rdsLstnr-p-8-t-10] InetRadiusProcessor - Creating NasConnection from accounting packet [statusType=2] radius 08-08/21:33:41 ERROR [rdsLstnr-p-8-t-10] InetRadiusProcessor - Session ip address not found in packet! radius 08-08/21:33:41 WARN [rdsLstnr-p-8-t-10] InetNas - NasConnection not found radius 08-08/21:33:41 INFO [rdsLstnr-p-8-t-10] RadiusListenerWorker - RESPONSE: Packet type: Accounting-Response Identifier: 13 Authenticator: {0D 87 DC 79 58 8A 3A BD 02 61 3B 65 C9 D1 48 12} Attributes: Process time stop: 83 в пакете аккаутинга видно что авторизация не проходит Session-Error-Msg=Authentication failure и нет Assigned-IP-Address |
Автор: | Amir [ 09 авг 2013, 00:02 ] |
Заголовок сообщения: | Re: Pon Eltex |
Когда полная копия - нормально работает, когда изменяете - не работает? Попробуйте добавить connection.start.fromAccept=1 Возможно, в access не все логи - Accept выдал, а DHCP-запроса не видно, или он не пришел? |
Автор: | sergey-xxi [ 09 авг 2013, 12:11 ] |
Заголовок сообщения: | Re: Pon Eltex |
с данным параметром ситуация не меняется. Начинаю припоминать похожую ситуацию, когда в место InetDhcpHelperProcessor у нас стоял в конфиге access'a InetDhcpProcessor. В предложенном вами java скрипте как раз присутствует InetDhcpProcessor, а у нас по идеи должно работает с InetDhcpHelperProcessor .... |
Автор: | Amir [ 09 авг 2013, 15:36 ] |
Заголовок сообщения: | Re: Pon Eltex |
У вас точно полная копия рабочей версии? В рабочей версии java класс не меняли? |
Автор: | sergey-xxi [ 14 авг 2013, 12:39 ] |
Заголовок сообщения: | Re: Pon Eltex |
Вот копия рабочей версии, та что используется сейчас. Код: package ru.bitel.bgbilling.modules.inet.dyn.device.redback; import java.nio.ByteBuffer; import java.util.List; import ru.bitel.bgbilling.kernel.network.dhcp.DhcpPacket; import ru.bitel.bgbilling.kernel.network.dhcp.DhcpProtocolHandler; import ru.bitel.bgbilling.kernel.network.radius.RadiusAttribute; import ru.bitel.bgbilling.kernel.network.radius.RadiusDictionary; import ru.bitel.bgbilling.kernel.network.radius.RadiusPacket; import ru.bitel.bgbilling.kernel.network.radius.RadiusPacket.RadiusPacketOption; import ru.bitel.bgbilling.kernel.network.radius.RadiusProtocolHandler; import ru.bitel.bgbilling.modules.inet.api.common.bean.InetDevice; import ru.bitel.bgbilling.modules.inet.api.common.bean.InetDeviceType; import ru.bitel.bgbilling.modules.inet.radius.InetRadiusProcessor; import ru.bitel.bgbilling.server.util.Setup; import ru.bitel.common.ParameterMap; import ru.bitel.common.Utils; import ru.bitel.common.sql.ConnectionSet; public class SmartEdgeClipsProtocolHandler extends SmartEdgeProtocolHandler implements RadiusProtocolHandler, DhcpProtocolHandler { public static final int Agent_Remote_Id = 96; public static final int Agent_Circuit_Id = 97; public static final int Mac_Addr = 145; public static final int DHCP_Option = 202; /** * Код атрибута - agent-remote-id */ protected int agentOptionRemoteIdType; /** * Код атрибута - agent-circuit-id */ protected int agentOptionCircuitIdType; /** * Нужно ли удалять заголовок (2 байта, тип+длина) из значения DHCP-опции */ protected int agentOptionRemoveHeader; /** * Тип поиска сервиса */ protected int servSearchMode; @Override public void init( Setup setup, int moduleId, InetDevice inetDevice, InetDeviceType inetDeviceType, ParameterMap deviceConfig ) throws Exception { super.init( setup, moduleId, inetDevice, inetDeviceType, deviceConfig ); agentOptionRemoteIdType = deviceConfig.getInt( "radius.agent.option.remoteId.type", deviceConfig.getInt( "radius.agentRemoteId.type", Agent_Remote_Id ) ); agentOptionCircuitIdType = deviceConfig.getInt( "radius.agent.option.circuitId.type", Agent_Circuit_Id ); agentOptionRemoveHeader = deviceConfig.getInt( "radius.agent.option.removeHeader", 2 ); servSearchMode = deviceConfig.getInt( "radius.servSearchMode", deviceConfig.getInt( "radius.serviceSearchMode", InetDevice.SERV_SEARCH_MODE_LOGIN ) ); } /** * Установка username * @param request */ protected void setUsername( final RadiusPacket request ) { String macAddr = request.getStringAttribute( radiusVendor, Mac_Addr, null ); if( macAddr != null ) { String callingStation = macAddr.replaceAll( "\\-", "" ); request.setStringAttribute( -1, RadiusDictionary.Calling_Station_Id, callingStation ); } byte[] remoteId = request.getByteAttribute( radiusVendor, Agent_Remote_Id, null ); byte[] circuitId = request.getByteAttribute( radiusVendor, Agent_Circuit_Id, null ); if( remoteId != null && circuitId != null ) { // String userName; // if (circuitId.length == 11) { // userName = Utils.bytesToString( remoteId, true, null ).substring(10, 22) + ":" + Utils.bytesToString( circuitId, true, null ).substring(20, 22); // } // else // { // userName = Utils.bytesToString( remoteId, true, null ) + ":" + Utils.bytesToString( circuitId, true, null ); // } // // // userName = userName.toLowerCase(); // request.setStringAttribute( -1, 1, userName ); String userName = Utils.bytesToString( remoteId, true, null ) + ":" + Utils.bytesToString( circuitId, true, null ); userName = userName.toLowerCase(); request.setStringAttribute( -1, 1, userName ); } } /** * Установка опции option c удалением заголовка, если необходимо (обычно два байта - тип и длина DHCP-субопции) * @param request * @param ra * @param remove * @param option */ protected void setAgentOption( final RadiusPacket request, final RadiusAttribute<?> ra, int remove, final RadiusPacketOption<Object> option ) { if( remove > 0 ) { ByteBuffer data = ra.getData(); data.position( remove ); data = data.slice(); request.setOption( option, data ); System.out.println( Utils.bytesToString (Utils.byteBufferAsArray( data ), false, " ") ); } else { request.setOption( option, ra.getValue() ); } } protected void setAgentOption( final RadiusPacket request, final List<RadiusAttribute<?>> ras, int position, int value, int remove, final RadiusPacketOption<Object> option ) { for( int i = 0, size = ras.size(); i < size; i++ ) { RadiusAttribute<?> ra = ras.get( i ); ByteBuffer data = ra.getData(); if( data.get( position ) == value ) { data.position( remove ); data = data.slice(); request.setOption( option, data ); } } } /** * Установка опций в запрос устройства-агента для последующей обработки * @param request */ protected void setAgentOptions( final RadiusPacket request ) { switch( agentOptionRemoteIdType ) { case 0: break; case DHCP_Option: { List<RadiusAttribute<?>> ras = request.getAttributes( radiusVendor, DHCP_Option ); if( ras != null ) { setAgentOption( request, ras, 3, 1, 4, InetRadiusProcessor.AGENT_REMOTE_ID ); } break; } default: { RadiusAttribute<?> ra = request.getAttribute( radiusVendor, agentOptionRemoteIdType ); if( ra != null ) { setAgentOption( request, ra, agentOptionRemoveHeader, InetRadiusProcessor.AGENT_REMOTE_ID ); } break; } } System.out.println( agentOptionCircuitIdType ); switch( agentOptionCircuitIdType ) { case 0: break; case DHCP_Option: { List<RadiusAttribute<?>> ras = request.getAttributes( radiusVendor, DHCP_Option ); if( ras != null ) { setAgentOption( request, ras, 3, 2, 4, InetRadiusProcessor.AGENT_CIRCUIT_ID ); } break; } default: { RadiusAttribute<?> ra = request.getAttribute( radiusVendor, agentOptionCircuitIdType ); System.out.println( Utils.bytesToString (Utils.byteBufferAsArray( ra.getData() ), false, " ") ); if( ra != null ) { setAgentOption( request, ra, 0, InetRadiusProcessor.AGENT_CIRCUIT_ID ); } break; } } } @Override public void preprocessAccessRequest( final RadiusPacket request, final RadiusPacket response, final ConnectionSet connectionSet ) throws Exception { super.preprocessAccessRequest( request, response, connectionSet ); // устанавливаем поле username setUsername( request ); // устанавливаем agent-remote-id setAgentOptions( request ); } @Override public void postprocessAccessRequest( final RadiusPacket request, final RadiusPacket response, final ConnectionSet connectionSet ) throws Exception { super.postprocessAccessRequest( request, response, connectionSet ); response.removeAttributes( -1, RadiusDictionary.Framed_IP_Address ); } @Override protected void preprocessAccountingRequestImpl( final int acctStatusType, final RadiusPacket request, final RadiusPacket response, final ConnectionSet connectionSet ) throws Exception { super.preprocessAccountingRequestImpl( acctStatusType, request, response, connectionSet ); switch( acctStatusType ) { // если сервисный аккаунтинг case 101: case 102: case 103: { } break; default: { // устанавливаем поле username setUsername( request ); // устанавливаем agent-remote-id setAgentOptions( request ); } break; } } @Override public void preprocessDhcpRequest( DhcpPacket request, DhcpPacket response ) throws Exception { // необходимо для старого поиска по логину if( servSearchMode == InetDevice.SERV_SEARCH_MODE_LOGIN ) { // подмена try { byte[] circuitId = request.getSubOption( (byte)1 ).value; byte[] remoteId = request.getSubOption( (byte)2 ).value; byte[] mac = new byte[6]; byte[] port = new byte[1]; System.arraycopy( circuitId, 5, port, 0, 1 ); System.arraycopy( remoteId, 2, mac, 0, 6 ); request.setSubOption( (byte)1, port ); request.setSubOption( (byte)2, mac ); } catch( java.lang.NullPointerException e ) { return; } } } @Override public void postprocessDhcpRequest( DhcpPacket request, DhcpPacket response ) throws Exception { } } предложенный вами код для парсинга эльтекса был подправлен по поиску remoteid, не корректно находил мак: request.setOption( InetDhcpProcessor.AGENT_REMOTE_ID, Arrays.copyOfRange( remoteId, 5, 11 ) ); |
Автор: | sergey-xxi [ 28 авг 2013, 20:02 ] |
Заголовок сообщения: | Re: Pon Eltex |
сейчас айпи выдается, но сервисной сессии нет на ельтексе Код: Packet type: Access-Request
Identifier: 53 Authenticator: {C8 E5 28 2F 09 54 73 A5 56 BA BE AF B4 F2 2B 8E} Attributes: User-Name=a8:f9:4b:06:ec:41 NAS-Port-Id=2/1 vlan-id 2 clips 140486 NAS-Identifier=RedBack2 User-Password=Redback NAS-IP-Address=192.168.12.202 NAS-Port=553648130 Service-Type=5 NAS-Port-Type=5 Called-Station-Id=10.10.10.1 Platform-Type=4 UNKNOWN[2352-201]={01 0A 0A 0A 01} Medium-Type=11 Agent-Remote-Id={00 00 00 00 06 A8 F9 4B 89 07 19} Agent-Circuit-Id={21 09 00 00 00 00 00 00 00 00 0B} OS-Version=11.1.2.7p2 Mac-Addr=a8-f9-4b-06-ec-41 NAS-Real-Port=553648130 UNKNOWN[3561--1]={02 0D 00 00 00 00 06 A8 F9 4B 89 07 19} UNKNOWN[3561--1]={01 0D 21 09 00 00 00 00 00 00 00 00 0B} radius 08-28/09:34:16 INFO [rdsLstnr-p-8-t-8] SmartEdgeClipsProtocolHandler - Parse as eltex bytes radius 08-28/09:34:16 INFO [rdsLstnr-p-8-t-8] InetRadiusProcessor - REQUEST_AFTER_PREPROCESS: Packet type: Access-Request Identifier: 53 Authenticator: {C8 E5 28 2F 09 54 73 A5 56 BA BE AF B4 F2 2B 8E} Attributes: User-Name=0000000006a8f94b890719:210900000000000000000b NAS-Port-Id=2/1 vlan-id 2 clips 140486 NAS-Identifier=RedBack2 User-Password=Redback NAS-IP-Address=192.168.12.202 NAS-Port=553648130 Service-Type=5 Calling-Station-Id=a8f94b06ec41 NAS-Port-Type=5 Called-Station-Id=10.10.10.1 Platform-Type=4 UNKNOWN[2352-201]={01 0A 0A 0A 01} Medium-Type=11 Agent-Remote-Id={00 00 00 00 06 A8 F9 4B 89 07 19} Agent-Circuit-Id={21 09 00 00 00 00 00 00 00 00 0B} OS-Version=11.1.2.7p2 Mac-Addr=a8-f9-4b-06-ec-41 NAS-Real-Port=553648130 UNKNOWN[3561--1]={02 0D 00 00 00 00 06 A8 F9 4B 89 07 19} UNKNOWN[3561--1]={01 0D 21 09 00 00 00 00 00 00 00 00 0B} Common options: {agentRemoteId=[B@2a761c0a, agentCircuitId=[B@302aea4d} radius 08-28/09:34:16 DEBUG [rdsLstnr-p-8-t-8] RadiusProcessor - Create new radius session. radius 08-28/09:34:16 DEBUG [rdsLstnr-p-8-t-8] InetNas - agentRemoteId=a8f94b890719 radius 08-28/09:34:16 INFO [rdsLstnr-p-8-t-8] InetNas - Found agentDevice:3 radius 08-28/09:34:16 DEBUG [rdsLstnr-p-8-t-8] InetNas - findServ agentDeviceRuntime=ru.bitel.bgbilling.modules.inet.runtime.device.InetDeviceRuntime@28b5655 9 radius 08-28/09:34:16 INFO [rdsLstnr-p-8-t-8] InetNas - Search serv on deviceId=3; interfaceId=11 radius 08-28/09:34:16 INFO [rdsLstnr-p-8-t-8] InetRadiusProcessor - [username=0000000006a8f94b890719:210900000000000000000b] Authenticated as inetServId:2 radius 08-28/09:34:16 DEBUG [rdsLstnr-p-8-t-8] InetRadiusProcessor - MAC-address from request: radius 08-28/09:34:16 DEBUG [rdsLstnr-p-8-t-8] InetAccountingPeriodList - Create: radius 08-28/09:34:16 DEBUG [rdsLstnr-p-8-t-8] InetAccountingPeriodList - AccountingPeriod: 2: 22.08.2013 00:00:00.0 - 31.08.2013 23:59:59.999 radius 08-28/09:34:16 INFO [rdsLstnr-p-8-t-8] InetApplication - inetServ[id=2] balance ok: 0.00 [0] radius 08-28/09:34:16 INFO [rdsLstnr-p-8-t-8] InetApplication - TariffOptionMap: {} radius 08-28/09:34:16 INFO [rdsLstnr-p-8-t-8] InetRadiusProcessor - Set ip from pool radius 08-28/09:34:16 INFO [rdsLstnr-p-8-t-8] InetRadiusProcessor - Write new waiting connection to DB radius 08-28/09:34:16 INFO [rdsLstnr-p-8-t-8] InetRadiusProcessor - New connection id=37279 radius 08-28/09:34:16 INFO [rdsLstnr-p-8-t-8] InetRadiusProcessor - Return code=0 radius 08-28/09:34:16 INFO [rdsLstnr-p-8-t-8] InetDhcpHelperProcessor - Put auth accept 2:3:11:A8F94B06EC41 radius 08-28/09:34:16 INFO [rdsLstnr-p-8-t-8] InetRadiusProcessor - RESPONSE_BEFORE_POSTPROCESS: Packet type: Access-Accept Identifier: 53 Authenticator: {} Attributes: Acct-Interim-Interval=900 Framed-IP-Address=10.10.10.181 Process time auth: 10 radius 08-28/09:34:16 DEBUG [rdsLstnr-p-8-t-8] ProcessorRequest - Sending to /192.168.12.202:1812 radius 08-28/09:34:16 INFO [rdsLstnr-p-8-t-8] InetRadiusListenerWorker - RESPONSE: Packet type: Access-Accept Identifier: 53 Authenticator: {0E 0F 5D 86 83 F2 D7 CF 7F D9 E3 CF BF 3D D6 15} Attributes: Acct-Interim-Interval=900 Process time auth: 12 mq 08-28/09:34:16 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] m oduleId: 2; pluginId: no; cid: 1; scid: -1; userId: 0; type: 1; deviceId: 2; connectionId: 37278; timestamp: 1377668056466 mq 08-28/09:34:16 INFO [event-proc-p-2-t-1] InetConnectionManager - Add connection: InetConnection [id=37278-37277, iface=2:553648130, sessId=0100FFFF780024 C5-521D8CCB-SE-C7D03E70, start=28.08.2013 09:34:16, uname=SE, addr=[IpAddress:null]] mq 08-28/09:34:16 INFO [event-proc-p-2-t-1] InetDhcpHelperProcessor - Ip is null 2:4:1: connection 08-28/09:34:16 DEBUG [sa-p-12-t-4] AcknowledgeConsumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaAccou ntingEvent] moduleId: 2; pluginId: no; cid: 2; scid: -1; userId: 0; type: 1; deviceId: 2; connectionId: 37279; timestamp: 1377668056940 connection 08-28/09:34:16 INFO [sa-p-12-t-4] ServiceActivatorDeviceWorker - Do task deviceId: 2; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetS aAccountingEvent] moduleId: 2; pluginId: no; cid: 2; scid: -1; userId: 0; type: 1; deviceId: 2; connectionId: 37279; timestamp: 1377668056940 connection 08-28/09:34:16 INFO [sa-p-12-t-4] InetApplication - TariffOptionMap: {} connection 08-28/09:34:16 INFO [sa-p-12-t-4] ServiceActivatorDeviceWorker - Command result event: ServiceActivatorEvent type=4; inetServId: 2; call: true; o ldState: 1; newState: 1; oldOptionSet: ; newOptionSet: connection 08-28/09:34:16 INFO [sa-p-12-t-4] ServiceActivatorDeviceWorker - Processing deviceId:2; command ServiceActivatorEvent type=4; inetServId: 2; call : true; oldState: 1; newState: 1; oldOptionSet: ; newOptionSet: connection 08-28/09:34:16 INFO [sa-p-12-t-4] ServiceActivatorSet - Invoking onAccountingStart connection 08-28/09:34:16 INFO [sa-p-12-t-4] ServiceActivatorDeviceWorker - Process event type[4] result=true mq 08-28/09:34:17 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] m oduleId: 2; pluginId: no; cid: 2; scid: -1; userId: 0; type: 1; deviceId: 2; connectionId: 37279; timestamp: 1377668056940 mq 08-28/09:34:17 INFO [event-proc-p-2-t-1] InetConnectionManager - Add connection: InetConnection [id=37279-0, iface=2:553648130, sessId=0100FFFF780024C6-5 21D8CCC, start=28.08.2013 09:34:16, uname=0000000006a8f94b890719:210900000000000000000b, addr=10.10.10.181] mq 08-28/09:34:17 INFO [event-proc-p-2-t-1] InetDhcpHelperProcessor - Put connection add 2:3:11:A8F94B06EC41 dhcp 08-28/09:34:17 DEBUG [dhcpLstnr-p-10-t-3] InetDhcpDeviceMap - Found device by giaddr id=2 dhcp 08-28/09:34:17 INFO [dhcpLstnr-p-10-t-3] InetAbstractDhcpProcessor - REQUEST: аккаутинг radius 08-28/09:34:16 INFO [rdsLstnr-p-7-t-2] RadiusListenerWorker - REQUEST: Packet type: Accounting-Request Identifier: 113 Authenticator: {36 1D CD 4D B0 35 B0 9B 13 6A B7 E0 3D D2 F7 0B} Attributes: User-Name=a8:f9:4b:06:ec:41 NAS-Identifier=RedBack2 NAS-IP-Address=192.168.12.202 NAS-Port=553648130 Service-Type=5 Acct-Status-Type=1 Acct-Session-Id=0100FFFF780024C6-521D8CCC Acct-Authentic=1 Acct-Interim-Interval=900 NAS-Port-Id=2/1 vlan-id 2 clips 140486 Event-Timestamp=1377668301 NAS-Port-Type=5 Called-Station-Id=10.10.10.1 DHCP-Max-Leases=1 Medium-Type=11 UNKNOWN[2352-201]={01 0A 0A 0A 01} Platform-Type=4 Agent-Remote-Id={00 00 00 00 06 A8 F9 4B 89 07 19} Agent-Circuit-Id={21 09 00 00 00 00 00 00 00 00 0B} NAT-Policy-Name=nat-policy Qos-Policing-Profile-Name=DEF-IPOE-IN OS-Version=11.1.2.7p2 Acct-Update-Reason=1 Mac-Addr=a8-f9-4b-06-ec-41 NAS-Real-Port=553648130 Qos-Metering-Profile-Name=DEF-IPOE-OUT UNKNOWN[3561--1]={02 0D 00 00 00 00 06 A8 F9 4B 89 07 19} UNKNOWN[3561--1]={01 0D 21 09 00 00 00 00 00 00 00 00 0B} radius 08-28/09:34:16 INFO [rdsLstnr-p-7-t-2] SmartEdgeClipsProtocolHandler - Parse as eltex bytes radius 08-28/09:34:16 INFO [rdsLstnr-p-7-t-2] InetRadiusProcessor - REQUEST_AFTER_PREPROCESS: Packet type: Accounting-Request Identifier: 113 Authenticator: {36 1D CD 4D B0 35 B0 9B 13 6A B7 E0 3D D2 F7 0B} Attributes: User-Name=0000000006a8f94b890719:210900000000000000000b NAS-Identifier=RedBack2 NAS-IP-Address=192.168.12.202 NAS-Port=553648130 Service-Type=5 Acct-Status-Type=1 Acct-Session-Id=0100FFFF780024C6-521D8CCC Acct-Authentic=1 Acct-Interim-Interval=900 NAS-Port-Id=2/1 vlan-id 2 clips 140486 Event-Timestamp=1377668301 Calling-Station-Id=a8f94b06ec41 NAS-Port-Type=5 Called-Station-Id=10.10.10.1 DHCP-Max-Leases=1 Medium-Type=11 UNKNOWN[2352-201]={01 0A 0A 0A 01} Platform-Type=4 Agent-Remote-Id={00 00 00 00 06 A8 F9 4B 89 07 19} Agent-Circuit-Id={21 09 00 00 00 00 00 00 00 00 0B} NAT-Policy-Name=nat-policy Qos-Policing-Profile-Name=DEF-IPOE-IN OS-Version=11.1.2.7p2 Acct-Update-Reason=1 Mac-Addr=a8-f9-4b-06-ec-41 NAS-Real-Port=553648130 Qos-Metering-Profile-Name=DEF-IPOE-OUT UNKNOWN[3561--1]={02 0D 00 00 00 00 06 A8 F9 4B 89 07 19} UNKNOWN[3561--1]={01 0D 21 09 00 00 00 00 00 00 00 00 0B} Common options: {agentRemoteId=[B@2412b03e, agentCircuitId=[B@46f0c8f2} radius 08-28/09:34:16 INFO [rdsLstnr-p-7-t-2] InetNas - Found agentDevice:3 radius 08-28/09:34:16 INFO [rdsLstnr-p-7-t-2] InetNas - Search serv on deviceId=3; interfaceId=11 radius 08-28/09:34:16 INFO [rdsLstnr-p-7-t-2] InetRadiusProcessor - Creating NasConnection from radius accounting packet radius 08-28/09:34:16 INFO [rdsLstnr-p-7-t-2] InetRadiusProcessor - Connection exist in db radius 08-28/09:34:16 INFO [rdsLstnr-p-7-t-2] Accounting - Update connection to DB radius 08-28/09:34:16 INFO [rdsLstnr-p-7-t-2] Accounting - Write new session to DB radius 08-28/09:34:16 INFO [rdsLstnr-p-7-t-2] Accounting - New session's id=19960 radius 08-28/09:34:16 INFO [rdsLstnr-p-7-t-2] connection - 37279:19960 Register ip: 10.10.10.181 radius 08-28/09:34:16 INFO [rdsLstnr-p-7-t-2] RadiusListenerWorker - RESPONSE: Packet type: Accounting-Response Identifier: 113 Authenticator: {D4 56 6F 03 B4 0E 28 72 97 B2 64 64 50 82 63 B2} Attributes: Process time start: 15 radius 08-28/09:34:17 INFO [rdsLstnr-p-7-t-9] update - REQUEST: Packet type: Accounting-Request Identifier: 114 Authenticator: {CA 92 C4 55 AD 69 96 20 DB 17 16 82 CA 11 F4 C1} Attributes: User-Name=a8:f9:4b:06:ec:41 NAS-Identifier=RedBack2 NAS-IP-Address=192.168.12.202 NAS-Port=553648130 Service-Type=5 Acct-Input-Octets=0 Acct-Output-Octets=0 Acct-Status-Type=3 Acct-Session-Time=0 Acct-Input-Packets=0 Acct-Session-Id=0100FFFF780024C6-521D8CCC Acct-Authentic=1 Acct-Interim-Interval=900 NAS-Port-Id=2/1 vlan-id 2 clips 140486 Acct-Output-Packets=0 Event-Timestamp=1377668301 Acct-Output-Gigawords=0 Acct-Input-Gigawords=0 NAS-Port-Type=5 Called-Station-Id=10.10.10.1 Acct-Mcast-Out-Packets-64={00 00 00 00 00 00 00 00} DHCP-Max-Leases=1 UNKNOWN[2352-201]={01 0A 0A 0A 01} Acct-Output-Octets-64={00 00 00 00 00 00 00 00} Acct-Input-Octets-64={00 00 00 00 00 00 00 00} Acct-Output-Packets-64={00 00 00 00 00 00 00 00} Acct-Input-Packets-64={00 00 00 00 00 00 00 00} Acct-Mcast-In-Octets-64={00 00 00 00 00 00 00 00} Assigned-IP-Address=10.10.10.181 Acct-Mcast-In-Packets-64={00 00 00 00 00 00 00 00} Acct-Mcast-Out-Octets-64={00 00 00 00 00 00 00 00} Qos-Policing-Profile-Name=DEF-IPOE-IN Acct-Update-Reason=10 Mac-Addr=a8-f9-4b-06-ec-41 Acct-Mcast-In-Octets=0 Acct-Mcast-Out-Octets=0 Acct-Mcast-In-Packets=0 Qos-Metering-Profile-Name=DEF-IPOE-OUT Acct-Mcast-Out-Packets=0 Platform-Type=4 Medium-Type=11 Agent-Remote-Id={00 00 00 00 06 A8 F9 4B 89 07 19} Agent-Circuit-Id={21 09 00 00 00 00 00 00 00 00 0B} NAT-Policy-Name=nat-policy OS-Version=11.1.2.7p2 NAS-Real-Port=553648130 UNKNOWN[3561--1]={02 0D 00 00 00 00 06 A8 F9 4B 89 07 19} UNKNOWN[3561--1]={01 0D 21 09 00 00 00 00 00 00 00 00 0B} radius 08-28/09:34:17 INFO [rdsLstnr-p-7-t-9] SmartEdgeClipsProtocolHandler - Parse as eltex bytes radius 08-28/09:34:17 INFO [rdsLstnr-p-7-t-9] InetRadiusProcessor - REQUEST_AFTER_PREPROCESS: Packet type: Accounting-Request Identifier: 114 Authenticator: {CA 92 C4 55 AD 69 96 20 DB 17 16 82 CA 11 F4 C1} Attributes: User-Name=0000000006a8f94b890719:210900000000000000000b NAS-Identifier=RedBack2 NAS-IP-Address=192.168.12.202 NAS-Port=553648130 Service-Type=5 Acct-Input-Octets=0 Acct-Output-Octets=0 Acct-Status-Type=3 Acct-Session-Time=0 Acct-Input-Packets=0 Acct-Session-Id=0100FFFF780024C6-521D8CCC Acct-Authentic=1 Acct-Interim-Interval=900 NAS-Port-Id=2/1 vlan-id 2 clips 140486 Acct-Output-Packets=0 Event-Timestamp=1377668301 Acct-Output-Gigawords=0 Acct-Input-Gigawords=0 Calling-Station-Id=a8f94b06ec41 NAS-Port-Type=5 Called-Station-Id=10.10.10.1 Acct-Mcast-Out-Packets-64={00 00 00 00 00 00 00 00} DHCP-Max-Leases=1 UNKNOWN[2352-201]={01 0A 0A 0A 01} Acct-Output-Octets-64={00 00 00 00 00 00 00 00} Acct-Input-Octets-64={00 00 00 00 00 00 00 00} Acct-Output-Packets-64={00 00 00 00 00 00 00 00} Acct-Input-Packets-64={00 00 00 00 00 00 00 00} Acct-Mcast-In-Octets-64={00 00 00 00 00 00 00 00} Assigned-IP-Address=10.10.10.181 Acct-Mcast-In-Packets-64={00 00 00 00 00 00 00 00} Acct-Mcast-Out-Octets-64={00 00 00 00 00 00 00 00} Qos-Policing-Profile-Name=DEF-IPOE-IN Acct-Update-Reason=10 Mac-Addr=a8-f9-4b-06-ec-41 Acct-Mcast-In-Octets=0 Acct-Mcast-Out-Octets=0 Acct-Mcast-In-Packets=0 Qos-Metering-Profile-Name=DEF-IPOE-OUT Acct-Mcast-Out-Packets=0 Platform-Type=4 Medium-Type=11 Agent-Remote-Id={00 00 00 00 06 A8 F9 4B 89 07 19} Agent-Circuit-Id={21 09 00 00 00 00 00 00 00 00 0B} NAT-Policy-Name=nat-policy OS-Version=11.1.2.7p2 NAS-Real-Port=553648130 UNKNOWN[3561--1]={02 0D 00 00 00 00 06 A8 F9 4B 89 07 19} UNKNOWN[3561--1]={01 0D 21 09 00 00 00 00 00 00 00 00 0B} Common options: {agentRemoteId=[B@3680c7bd, agentCircuitId=[B@40b9653f} radius 08-28/09:34:17 INFO [rdsLstnr-p-7-t-9] InetRadiusProcessor - Session 0100FFFF780024C6-521D8CCC found. r |
Автор: | Amir [ 29 авг 2013, 15:33 ] |
Заголовок сообщения: | Re: Pon Eltex |
В Access-Accept пакете не выдаются сервисы CLIPS, которые нужно включить. Возможно что-то с конфигурацией не то. |
Автор: | Alex-XXI [ 30 авг 2013, 12:46 ] |
Заголовок сообщения: | Re: Pon Eltex |
В мониторе в текущих сессиях отображается порядка 9000 соединений с длительностью несколько секунд, все сессии одного абонентского устройства, статус всех сессий завершен, состояние подключено. При попытке вручную закрыть эти сессии выскакивают разные ошибки, сессия не закрывается. Сервер: вер. 5.2 сборка 1538 от 23.08.2013 15:51:00, inet вер. 5.2 сборка 1230 от 26.08.2013 16:27:19 В логе клиента пишет: Код: http://192.168.1.50:8080/bgbilling/executer/ru.bitel.bgbilling.modules.inet.api/2/InetSessionService?wsdl -> {http://service.common.api.inet.modules.bgbilling.bitel.ru/}InetSessionService:connectionFinish <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><ns5:connectionFinish xmlns:ns5="http://service.common.api.inet.modules.bgbilling.bitel.ru/" xmlns:common="http://common.bitel.ru" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><arg0>37472</arg0></ns5:connectionFinish></S:Body></S:Envelope> javax.xml.ws.soap.SOAPFaultException: ru.bitel.bgbilling.kernel.event.EventProcessorException: ru.bitel.bgbilling.common.BGException: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '20155-30-10-0-0' for key 1 at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:193) at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:134) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:123) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:93) at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:144) at $Proxy36.connectionFinish(Unknown Source) at ru.bitel.bgbilling.modules.inet.api.client.monitor.InetMonitorPanel$10.actionPerformedImpl(InetMonitorPanel.java:408) at ru.bitel.common.client.AbstractBGUPanel.actionPerformed(AbstractBGUPanel.java:238) at ru.bitel.common.client.AbstractBGUPanel$DefaultAction.actionPerformed(AbstractBGUPanel.java:92) at ru.bitel.common.client.DelegateAction.actionPerformed(DelegateAction.java:21) at ru.bitel.common.client.BGSwingUtilites$1.actionPerformed(BGSwingUtilites.java:178) at javax.swing.AbstractButton.fireActionPerformed(Unknown Source) at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.setPressed(Unknown Source) at javax.swing.AbstractButton.doClick(Unknown Source) at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source) at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown Source) at java.awt.Component.processMouseEvent(Unknown Source) at javax.swing.JComponent.processMouseEvent(Unknown Source) at java.awt.Component.processEvent(Unknown Source) at java.awt.Container.processEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Window.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEventImpl(Unknown Source) at java.awt.EventQueue.access$400(Unknown Source) at java.awt.EventQueue$2.run(Unknown Source) at java.awt.EventQueue$2.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source) at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source) at java.awt.EventQueue$3.run(Unknown Source) at java.awt.EventQueue$3.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) Caused by: ru.bitel.bgbilling.kernel.event.EventProcessorException: ru.bitel.bgbilling.kernel.event.EventProcessorException: ru.bitel.bgbilling.common.BGException: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '20155-30-10-0-0' for key 1 at ru.bitel.bgbilling.kernel.event.EventProcessor.request(EventProcessor.java:917) at ru.bitel.bgbilling.modules.inet.api.server.service.InetSessionServiceImpl.connectionFinish(InetSessionServiceImpl.java:229) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at ru.bitel.bgbilling.kernel.container.service.server.ServiceInfo.invoke(ServiceInfo.java:102) at ru.bitel.bgbilling.kernel.container.ws.server.AbstractJaxWsHandler.invoke(AbstractJaxWsHandler.java:192) at ru.bitel.bgbilling.kernel.container.ws.server.JaxWsHandler.access$1(JaxWsHandler.java:1) at ru.bitel.bgbilling.kernel.container.ws.server.JaxWsHandler$2.run(JaxWsHandler.java:312) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:396) at ru.bitel.bgbilling.kernel.container.ws.server.JaxWsHandler.invoke(JaxWsHandler.java:306) at ru.bitel.bgbilling.kernel.container.ws.server.AbstractJaxWsHandler$ServiceInstanceResolver$1.invoke(AbstractJaxWsHandler.java:304) at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:150) at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:261) at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:100) at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:641) at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:600) at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:585) at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:482) at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:314) at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:608) at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:259) at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:162) at ru.bitel.common.server.JaxWSAdapter.handle(JaxWSAdapter.java:374) at bitel.billing.server.Executer.doPost(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:641) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at bitel.billing.server.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:164) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:563) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:403) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:301) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:162) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:309) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) Caused by: ru.bitel.bgbilling.kernel.event.EventProcessorException: ru.bitel.bgbilling.common.BGException: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '20155-30-10-0-0' for key 1 at ru.bitel.bgbilling.kernel.event.Producer.request(Producer.java:254) at ru.bitel.bgbilling.kernel.event.EventProcessor.request(EventProcessor.java:902) ... 47 more Код: http://192.168.1.50:8080/bgbilling/executer/ru.bitel.bgbilling.modules.inet.api/2/InetSessionService?wsdl -> {http://service.common.api.inet.modules.bgbilling.bitel.ru/}InetSessionService:connectionFinish
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><ns5:connectionFinish xmlns:ns5="http://service.common.api.inet.modules.bgbilling.bitel.ru/" xmlns:common="http://common.bitel.ru" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><arg0>19221</arg0></ns5:connectionFinish></S:Body></S:Envelope> javax.xml.ws.soap.SOAPFaultException: ru.bitel.bgbilling.kernel.event.EventProcessorException: ru.bitel.bgbilling.common.BGException: Соединение не найдено (connectionId=19221, deviceId=2, servId=3) at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:193) at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:134) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:123) at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:93) at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:144) at $Proxy36.connectionFinish(Unknown Source) at ru.bitel.bgbilling.modules.inet.api.client.monitor.InetMonitorPanel$10.actionPerformedImpl(InetMonitorPanel.java:408) at ru.bitel.common.client.AbstractBGUPanel.actionPerformed(AbstractBGUPanel.java:238) at ru.bitel.common.client.AbstractBGUPanel$DefaultAction.actionPerformed(AbstractBGUPanel.java:92) at ru.bitel.common.client.DelegateAction.actionPerformed(DelegateAction.java:21) at ru.bitel.common.client.BGSwingUtilites$1.actionPerformed(BGSwingUtilites.java:178) at javax.swing.AbstractButton.fireActionPerformed(Unknown Source) at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.setPressed(Unknown Source) at javax.swing.AbstractButton.doClick(Unknown Source) at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source) at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown Source) at java.awt.Component.processMouseEvent(Unknown Source) at javax.swing.JComponent.processMouseEvent(Unknown Source) at java.awt.Component.processEvent(Unknown Source) at java.awt.Container.processEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Window.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEventImpl(Unknown Source) at java.awt.EventQueue.access$400(Unknown Source) at java.awt.EventQueue$2.run(Unknown Source) at java.awt.EventQueue$2.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source) at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source) at java.awt.EventQueue$3.run(Unknown Source) at java.awt.EventQueue$3.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) Caused by: ru.bitel.bgbilling.kernel.event.EventProcessorException: ru.bitel.bgbilling.kernel.event.EventProcessorException: ru.bitel.bgbilling.common.BGException: Соединение не найдено (connectionId=19221, deviceId=2, servId=3) at ru.bitel.bgbilling.kernel.event.EventProcessor.request(EventProcessor.java:917) at ru.bitel.bgbilling.modules.inet.api.server.service.InetSessionServiceImpl.connectionFinish(InetSessionServiceImpl.java:229) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at ru.bitel.bgbilling.kernel.container.service.server.ServiceInfo.invoke(ServiceInfo.java:102) at ru.bitel.bgbilling.kernel.container.ws.server.AbstractJaxWsHandler.invoke(AbstractJaxWsHandler.java:192) at ru.bitel.bgbilling.kernel.container.ws.server.JaxWsHandler.access$1(JaxWsHandler.java:1) at ru.bitel.bgbilling.kernel.container.ws.server.JaxWsHandler$2.run(JaxWsHandler.java:312) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:396) at ru.bitel.bgbilling.kernel.container.ws.server.JaxWsHandler.invoke(JaxWsHandler.java:306) at ru.bitel.bgbilling.kernel.container.ws.server.AbstractJaxWsHandler$ServiceInstanceResolver$1.invoke(AbstractJaxWsHandler.java:304) at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:150) at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:261) at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:100) at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:641) at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:600) at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:585) at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:482) at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:314) at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:608) at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:259) at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:162) at ru.bitel.common.server.JaxWSAdapter.handle(JaxWSAdapter.java:374) at bitel.billing.server.Executer.doPost(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:641) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at bitel.billing.server.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:164) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:462) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:563) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:403) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:301) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:162) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:309) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) Caused by: ru.bitel.bgbilling.kernel.event.EventProcessorException: ru.bitel.bgbilling.common.BGException: Соединение не найдено (connectionId=19221, deviceId=2, servId=3) at ru.bitel.bgbilling.kernel.event.Producer.request(Producer.java:254) at ru.bitel.bgbilling.kernel.event.EventProcessor.request(EventProcessor.java:902) ... 47 more |
Автор: | Amir [ 30 авг 2013, 16:44 ] |
Заголовок сообщения: | Re: Pon Eltex |
Это на тестовой? Похоже при переносе БД какая-то ошибка произошла, что сессии с дублирующимся ID были. Для 5.2: 1017 19.11.2012 18:23:52 ИСПРАВЛЕНО Inet: После перезагрузки mysql могли дублироваться ID сессий: InnoDB каждый раз инициализирует AUTO_INCREMENT по максимальному значению. Тестовая же вроде бы сначала была более старая? |
Страница 1 из 1 | Часовой пояс: UTC + 5 часов [ Летнее время ] |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |