При добавлении шлюза на договор состояние шлюза - удален
только добавил шлюз:
Код:
mq 06-26/10:43:12 INFO [event-proc-p-2-t-1] InetServRuntimeMap - Caught event: Event[ru.bitel.bgbilling.modules.inet.api.server.event.InetServModifiedEvent] moduleId: 5; pluginId: no; cid: 47208; scid: -1; userId: 2; timestamp: 1529973792290
mq 06-26/10:43:12 INFO [event-proc-p-2-t-1] InetServRuntimeMap - Adding new InetServRuntime: 4198
mq 06-26/10:43:12 INFO [event-proc-p-2-t-1] InetServRuntimeMap - Loading inetServ from database.
mq 06-26/10:43:12 INFO [event-proc-p-2-t-1] InetServRuntimeMap - Adding InetServRuntime: 4198
mq 06-26/10:43:12 INFO [event-proc-p-2-t-1] InetServRuntimeMap - ContractId: 47208; status: 0; servId: 4198
123.456.789.001
Options [] TariffModuleTreeSet [172:01.01.2015-…; ]
Device state: -1; optionSet:
спустя какое то время состояние шлюза меняется на включен, но на свичах никакие команды не выполняет:
Код:
connection 06-26/11:02:46 INFO [sa-p-12-t-26] ServiceActivatorSet - Connecting to device
connection 06-26/11:02:46 INFO [sa-p-12-t-26] cisco - Connected
connection 06-26/11:02:46 INFO [sa-p-12-t-26] cisco - bill
Password:
connection 06-26/11:02:46 INFO [sa-p-12-t-26] cisco - Login entered
connection 06-26/11:02:46 INFO [sa-p-12-t-26] cisco -
6506-3BXL>
connection 06-26/11:02:46 INFO [sa-p-12-t-26] cisco - Password entered
connection 06-26/11:02:46 INFO [sa-p-12-t-26] cisco - terminal length 0
6506-3BXL>
connection 06-26/11:02:46 INFO [sa-p-12-t-26] cisco - terminal width 0
6506-3BXL>
connection 06-26/11:02:46 INFO [sa-p-12-t-26] cisco - enable 5
Password:
connection 06-26/11:02:46 INFO [sa-p-12-t-26] cisco -
6506-3BXL#
connection 06-26/11:02:46 INFO [sa-p-12-t-26] cisco - config t
Enter configuration commands, one per line. End with CNTL/Z.
6506-3BXL(config)#
connection 06-26/11:02:47 INFO [sa-p-12-t-26] linksys - Connected
connection 06-26/11:02:47 INFO [sa-p-12-t-26] linksys - bill
Password:
connection 06-26/11:02:47 INFO [sa-p-12-t-26] linksys - Login entered
connection 06-26/11:02:47 INFO [sa-p-12-t-26] linksys - ****************
SW1#
connection 06-26/11:02:47 INFO [sa-p-12-t-26] linksys - Password entered
connection 06-26/11:02:47 INFO [sa-p-12-t-26] linksys - config t
SW1(config)#
connection 06-26/11:02:47 INFO [sa-p-12-t-26] ServiceActivatorDeviceWorker - Do task deviceId: 27; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaStateModifyEvent] moduleId: 5; pluginId: no; cid: 47208; scid: -1; userId: 0; deviceId: 27; inetServId: 4198; connectionId: 0; state: 1; accessCode: 0; timestamp: 1529974965921
connection 06-26/11:02:47 INFO [sa-p-12-t-26] InetApplication - TariffOptionMap: {}
connection 06-26/11:02:47 INFO [sa-p-12-t-26] InetApplication - OptionSet: []
connection 06-26/11:02:47 INFO [sa-p-12-t-26] ServiceActivatorDeviceWorker - Command result event: ServiceActivatorEvent type=2; inetServId: 4198; call: false; oldState: -1; newState: 1; oldOptionSet: ; newOptionSet:
connection 06-26/11:02:47 INFO [sa-p-12-t-26] ServiceActivatorDeviceWorker - Processing deviceId:27; command ServiceActivatorEvent type=2; inetServId: 4198; call: false; oldState: -1; newState: 1; oldOptionSet: ; newOptionSet:
connection 06-26/11:02:47 INFO [sa-p-12-t-26] ServiceActivatorSet - Invoking serviceModify
connection 06-26/11:02:47 INFO [sa-p-12-t-26] AbstractTerminalServiceActivator - serviceOptionsModify
connection 06-26/11:02:47 INFO [sa-p-12-t-26] AbstractTerminalServiceActivator - switchOptions
connection 06-26/11:02:47 INFO [sa-p-12-t-26] AbstractTerminalServiceActivator - serviceOptionsModify
connection 06-26/11:02:47 INFO [sa-p-12-t-26] AbstractTerminalServiceActivator - switchOptions
connection 06-26/11:02:47 INFO [sa-p-12-t-26] ServiceActivatorDeviceWorker - Process event type[2] result=true
connection 06-26/11:02:47 INFO [sa-p-12-t-26] ServiceActivatorDeviceWorker - Changing InetServ:4198 state and/or options
mq 06-26/11:02:47 INFO [event-proc-p-2-t-1] InetServRuntimeMap - Caught event: Event[ru.bitel.bgbilling.modules.inet.access.event.InetServDeviceStateAndOptionsModifiedEvent] moduleId: 5; pluginId: no; cid: global; scid: -1; userId: -1; deviceId: 27; inetServId: 4198; state: 1; optionSet: ; timestamp: 1529974967402
connection 06-26/11:02:52 INFO [sa-p-12-t-26] ServiceActivatorSet - Disconnecting from device
connection 06-26/11:02:52 INFO [sa-p-12-t-26] cisco - executeAsync: exit
connection 06-26/11:02:52 INFO [sa-p-12-t-26] linksys - executeAsync: exit
Если сделать синхронизацию шлюза, то все ок, все команды выполняются.
Но есть одно большое НО, если расторгнуть договор, и дать этот же влан\порт\ip, то абонента может отключить через несколько часов\дней.
Код:
нформация о версии:
Клиент: вер. 6.1.818 / 22.12.2014 22:04:39
os: Windows 10; java: Java HotSpot(TM) 64-Bit Server VM, v.1.8.0_151
ВНИМАНИЕ: Спецификация версии 1.8 не рекомендуется
Сервер: вер. 6.1.1018 / 25.12.2014 18:48:07
os: Linux; java: Java HotSpot(TM) 64-Bit Server VM, v.1.7.0_71
bill: вер. 6.1.250 / 10.09.2014 16:16:54
dialup: вер. 6.1.312 / 12.09.2014 16:44:17
inet: вер. 6.1.637 / 24.12.2014 21:09:06
ipn: вер. 6.1.230 / 13.11.2014 17:24:24
npay: вер. 6.1.181 / 19.11.2014 14:51:58
phone: вер. 6.1.242 / 25.12.2014 19:24:32
reports: вер. 6.1.195 / 21.11.2014 19:30:55
Окружение:
Клиент:
os: Windows 10 amd64, 10.0
java: Java HotSpot(TM) 64-Bit Server VM, v.1.8.0_151
jre home: C:\Program Files\Java\jre1.8.0_151
default tz: 26.06.2018 11:23 VLAT +1000 (Asia/Vladivostok)
user tz: 26.06.2018 11:23 VLAT +1000 (Asia/Vladivostok)
Сервер:
os: Linux amd64, 4.9.0-4-amd64
java: Java HotSpot(TM) 64-Bit Server VM, v.1.7.0_71
jre home: /root/jdk1.7.0_71/jre
default tz: 26.06.2018 11:23 VLAT +1000 (Asia/Vladivostok)
биллинг и access на разных серверах.