resident_k

Первый толковый совет, спасибо. Согласен с п.1, более-менее понятен и реальный п.3, по п.2 - можно ссылку на софт СКАТ - погуглил очень много разного софта с таким названием.

На 500 баксов можно отправить больше 150 тысяч смс )) А 10000смс как раз будет 2500р. это где такие расценки - $0,003 за смс?

Ну да, они платные. 2000р в месяц обрушат ваш бизнес? Тогда и заморачиваться таким бизнесом не стоит, наверное )) К примеру, мне необходимо разослать сообщение броадкастом всем абонентам. Если абонентов, к примеру, 10000, то это уже выльется где-то в $500-700, которые на дороге не валяются. Но это мы уже от темы отклонились, вопрос сформулирован конкретно - как отправить сообщение абоненту в браузере.

СМС посылайте и емыл. Из практики - и-мейлы, абонент может не читать неделями, а СМСки - платные

Как реализовать? Подробнее можно? Биллинг при том, что абоненту надо послать какой-то месседж, к примеру, что деньги на счету заканчиваются.

а подробнее ... абонентофф довольно много

Некоторые провайдеры отправляют свои абонентам сообщения в браузере. Как это реализовать имея в хозяйстве Lanbilling ?

Juniper MX80 не получатся реализовать схему Http-redirect для пользователей заблокированных по балансу. Для подключения пользователей с положительным балансом используем фильтры: set firewall family inet filter fltr-100Mb-NAT interface-specific set firewall family inet filter fltr-100Mb-NAT term 1 from source-prefix-list NAT-PREFIX-LIST set firewall family inet filter fltr-100Mb-NAT term 1 then service-accounting set firewall family inet filter fltr-100Mb-NAT term 1 then routing-instance NAT-RI set firewall family inet filter fltr-100Mb-NAT term 2 then service-accounting set firewall family inet filter fltr-50Mb-NAT interface-specific set firewall family inet filter fltr-50Mb-NAT term 1 from source-prefix-list NAT-PREFIX-LIST set firewall family inet filter fltr-50Mb-NAT term 1 then policer plcr-100Mb set firewall family inet filter fltr-50Mb-NAT term 1 then service-accounting set firewall family inet filter fltr-50Mb-NAT term 2 then policer plcr-100Mb set firewall family inet filter fltr-50Mb-NAT term 2 then service-accounting set firewall policer plcr-100Mb logical-interface-policer set firewall policer plcr-100Mb if-exceeding bandwidth-limit 1g set firewall policer plcr-100Mb if-exceeding burst-size-limit 38400000 set firewall policer plcr-100Mb then discard Для заблокированных по балансу пытались сделать через фильтр такого плана: set firewall family inet filter fltr-http-redirect term 1 from source-prefix-list NAT-PREFIX-LIST set firewall family inet filter fltr-http-redirect term 1 from protocol icmp set firewall family inet filter fltr-http-redirect term 1 from port bootpc set firewall family inet filter fltr-http-redirect term 1 from port dhcp set firewall family inet filter fltr-http-redirect term 1 from port domain set firewall family inet filter fltr-http-redirect term 1 from port netbios-ns set firewall family inet filter fltr-http-redirect term 1 then policer plcr-8Mb set firewall family inet filter fltr-http-redirect term 1 then count service_accept set firewall family inet filter fltr-http-redirect term 1 then accept set firewall family inet filter fltr-http-redirect term 2 from port http set firewall family inet filter fltr-http-redirect term 2 then policer plcr-8Mb set firewall family inet filter fltr-http-redirect term 2 then count redirected set firewall family inet filter fltr-http-redirect term 2 then routing-instance http-redirect set firewall family inet filter fltr-http-redirect term 3 then count else_discard set firewall policer plcr-8Mb logical-interface-policer set firewall policer plcr-8Mb if-exceeding bandwidth-limit 8m set firewall policer plcr-8Mb if-exceeding burst-size-limit 1920000 set firewall policer plcr-8Mb then discard set routing-instances http-redirect instance-type forwarding set routing-instances http-redirect routing-options static route 0.0.0.0/0 next-hop xxx.xxx.xxx.xxx Но данная схема не заработала.

Подскажите - как сделать копирование всех файлов с резервной флешки на основную для Juniper МХ80 ? request system snapshot - копирование всех файлов с текущей nand флешки на резервную а какой командой сделать обратное действие ?

В тех.поддержку обратились, в компанию продавшую дивайс, они перемаршрутизовали запрос в Эриксон, но толкового совета не дают :( Посоветовали полностью сделать перепрошивку устройства. Еще нюанс - У нас шесть портов собраны в два LACP, по три порта в каждом. Заметили особенность - на этом БРАСе было всего 254 реальных адреса и более 2000 онлайн абонентов, увеличили диапазон реальных адресов. Хотя сегодня абонентов онлайн было не так много, а LACP разваливалось и порты отпадали.

У нас два таких BRASa стоит, на втором версия софта, по-моему, поновее. Используем IPOE. До этого полгода работали без сбоев. Глюкануло два дня назад вечером кратковременно,минут на 20, отвалилось, потом само восстановилось. Позавчера было два таких картковременных отпадения на 20 мин, тоже в вечернее время. Вчера отвалилось в 21-00 и практически уже не поднималось. [inet]Redback_1#sh subs act us e8:94:f6:63:88:51 e8:94:f6:63:88:51 Session state Up Circuit lg id 825 clips 136442 Internal Circuit 255/22:13:58/7/2/5370 Interface bound CLIENTS2 Current port-limit unlimited Session time left 858105 Protocol Stack IPV4 dhcp max-addrs 1 (applied) ip source-validation 1 (applied from sub_default) dns primary 10.100.2.1 (applied from sub_default) dns secondary 8.8.8.8 (applied from sub_default) dhcp vendor class id MSFT 5.0 (applied) dhcp option client id <E8><94><F6>c<88>Q (applied) dhcp option hostname 0x0c09544c2d57523734304e (applied) timeout absolute 864000 (applied) acct-interim-interval 600 (applied) qos-policing-policy qos-15-5-in (applied) qos-metering-policy qos-15-5-out (applied) nat policy-name CGNAT (applied) timeout idle 1800 (applied as dhcp lease time) IP host entries installed by DHCP: (max_addr 1 cur_entries 1) 10.120.14.211 e8:94:f6:63:88:51 [inet]Redback_1#sh subs act us f4:f2:6d:60:69:59 f4:f2:6d:60:69:59 Session state Up Agent Remote ID "<FC><FA><F7>^V<E2><A2>" Agent Circuit ID "^AK" Circuit lg id 825 clips 136294 Internal Circuit 255/22:13:58/7/2/5222 Interface bound CLIENTS2 Current port-limit unlimited Session time left 858060 Protocol Stack IPV4 dhcp max-addrs 1 (applied) ip source-validation 1 (applied from sub_default) dns primary 10.100.2.1 (applied from sub_default) dns secondary 8.8.8.8 (applied from sub_default) dhcp vendor class id MSFT 5.0 (applied) dhcp option client id <F4><F2>m`iY (applied) dhcp option hostname 0x0c09544c2d57523834314e (applied) timeout absolute 864000 (applied) acct-interim-interval 600 (applied) qos-policing-policy qos-50-10-in (applied) qos-metering-policy qos-50-10-out (applied) nat policy-name CGNAT (applied) timeout idle 1800 (applied as dhcp lease time) IP host entries installed by DHCP: (max_addr 1 cur_entries 1) 10.120.12.38 f4:f2:6d:60:69:59

[inet]Redback_1#sh version Redback Networks SmartEdge OS Version SEOS-12.1.1.10p2-Release Built by sysbuild@eussjlx7009.sj.us.am.ericsson.se Sun Aug 23 20:25:14 PDT 2015 Copyright © 1998-2015, Redback Networks Inc. All rights reserved. System Bootstrap version is PowerPC,rev2.0.1.4 Installed minikernel version is 2.6 Router Up Time - 1 hour 59 minutes 4 secs [inet]Redback_1# [inet]Redback_1#show licenses Software Feature License Configured -------------------------- ------------------ subscriber active 8000 YES subscriber bandwidth 60 YES nat enhanced YES Total active subscriber license configured 8000 netflow - не используем

Отпадают все интерфейсы на Ericsson Redback Smartedge SE100. После того, как появилась данная проблема - открыли устройство пропылесосили, посмотрели вздутых конденсаторов нет на плате и т.п. На вид выглядит нормально, в лог пишет: May 17 20:38:53: %PM-1-ALERT: Process IPPA IPC SLOT 2, pid 0x80020023, is not responding. May 17 20:38:56: %SYSMON-5-GEN_FTP: Core file /ata0/p01/ppa/crashSlot02Ippa.gz FTPed to /md/ successfully May 17 20:39:00: %CSM-6-PORT: ethernet 2/1 link state DOWN service state DOWN, overall admin is UP May 17 20:39:00: %CSM-6-PORT: ethernet 2/1 link state down, trigger source: Hardware removed May 17 20:39:00: %CSM-6-PORT: ethernet 2/2 link state DOWN service state DOWN, overall admin is UP May 17 20:39:00: %CSM-6-PORT: ethernet 2/2 link state down, trigger source: Hardware removed May 17 20:39:00: %CSM-6-PORT: ethernet 2/3 link state DOWN service state DOWN, overall admin is UP May 17 20:39:00: %CSM-6-PORT: ethernet 2/3 link state down, trigger source: Hardware removed May 17 20:39:00: %CSM-6-PORT: ethernet 2/4 link state DOWN service state DOWN, overall admin is UP May 17 20:39:00: %CSM-6-PORT: ethernet 2/4 link state down, trigger source: Hardware removed May 17 20:39:00: %CSM-6-PORT: ethernet 2/15 link state DOWN service state DOWN, overall admin is UP May 17 20:39:00: %CSM-6-PORT: ethernet 2/15 link state down, trigger source: Hardware removed May 17 20:39:00: %CSM-6-PORT: ethernet 2/16 link state DOWN service state DOWN, overall admin is UP May 17 20:39:00: %CSM-6-PORT: ethernet 2/16 link state down, trigger source: Hardware removed May 17 20:39:00: %CSM-6-CARD: card carrier REMOVED from slot 2 May 17 20:39:02: %PM-1-ALERT: Process EPPA IPC SLOT 2, pid 0x81020021, is not responding. May 17 20:39:02: [0002]: %DHCP-5-MRKG_SV_DEAD: Marking server: 192.168.11.1 in context: inet dead May 17 20:39:02: %LG-3-GRP_LOG: link-group LACP_SE100 state: DOWN May 17 20:39:02: %LG-3-GRP_LOG: link-group LACP_SE100 PVC:300 state: DOWN May 17 20:39:02: %LG-3-GRP_LOG: link-group LACP_SE100 PVC:301 state: DOWN May 17 20:39:02: %LG-3-GRP_LOG: link-group LACP_SE100 PVC:302 state: DOWN May 17 20:39:02: %LG-3-GRP_LOG: link-group LACP_SE100 PVC:333 state: DOWN May 17 20:39:02: %LG-3-GRP_LOG: link-group LACP_local2 state: DOWN May 17 20:39:10: %CSM-6-CARD: card carrier INSERTED in slot 2 May 17 20:39:15: %PUBSUB-3-ERR: SNMPD [rbn_pubsub_cache_attr_read]: Instance(20) out of range(0..18) for data id(128) May 17 20:39:15: %PUBSUB-3-ERR: SNMPD [rbos_pubsub_data_get]: rbn_pubsub_cache_attr_read failed (-1), instance (20), id (128) May 17 20:39:15: %PUBSUB-3-ERR: SNMPD [rbn_pubsub_cache_attr_read]: Instance(21) out of range(0..18) for data id(128) May 17 20:39:15: %PUBSUB-3-ERR: SNMPD [rbos_pubsub_data_get]: rbn_pubsub_cache_attr_read failed (-1), instance (21), id (128) May 17 20:39:17: %CSM-6-CARD: MIC number 1 ge-2-port REMOVED from slot 2 May 17 20:39:17: %SNMP-6-INFO: The last entity configuration change notification was sent out2.00 (less than 5.00) seconds before. Suppressing this one. May 17 20:39:19: %CSM-6-CARD: MIC number 2 ge-2-port REMOVED from slot 2 May 17 20:39:19: %SNMP-6-INFO: The last entity configuration change notification was sent out4.00 (less than 5.00) seconds before. Suppressing this one. May 17 20:39:19: %CSM-6-CARD: MIC number 1 ge-2-port INSERTED in slot 2 May 17 20:39:19: %PUBSUB-3-ERR: SNMPD [rbn_pubsub_cache_attr_read]: Instance(20) out of range(0..18) for data id(128) May 17 20:39:19: %PUBSUB-3-ERR: SNMPD [rbos_pubsub_data_get]: rbn_pubsub_cache_attr_read failed (-1), instance (20), id (128) May 17 20:39:19: %PUBSUB-3-ERR: SNMPD [rbn_pubsub_cache_attr_read]: Instance(21) out of range(0..18) for data id(128) May 17 20:39:19: %PUBSUB-3-ERR: SNMPD [rbos_pubsub_data_get]: rbn_pubsub_cache_attr_read failed (-1), instance (21), id (128) May 17 20:39:19: %SNMP-6-INFO: The last entity configuration change notification was sent out4.00 (less than 5.00) seconds before. Suppressing this one. May 17 20:39:20: %CSM-6-CARD: MIC number 2 ge-2-port INSERTED in slot 2 May 17 20:39:20: %PUBSUB-3-ERR: SNMPD [rbn_pubsub_cache_attr_read]: Instance(32) out of range(0..18) for data id(128) May 17 20:39:20: %PUBSUB-3-ERR: SNMPD [rbos_pubsub_data_get]: rbn_pubsub_cache_attr_read failed (-1), instance (32), id (128) May 17 20:39:20: %PUBSUB-3-ERR: SNMPD [rbn_pubsub_cache_attr_read]: Instance(33) out of range(0..18) for data id(128) May 17 20:39:20: %PUBSUB-3-ERR: SNMPD [rbos_pubsub_data_get]: rbn_pubsub_cache_attr_read failed (-1), instance (33), id (128) May 17 20:39:25: %QOS-6-INFO: qos info: PPA just reborn 0 May 17 20:39:25: %PPAINFRA-6-ISTART_INFO: 42e04e7e/0000000002/925500000:02/IPPA/EU00:Ready to receive packets May 17 20:39:25: %QOS-6-INFO: qos info: iPPA reg on slot 2 May 17 20:39:25: %CSM-6-CARD: card carrier INSERTED in slot 2 READY May 17 20:39:26: %PPAINFRA-6-ISTART_INFO: 4d2375be/0000000003/390800000:02/EPPA/EU00:Ready to receive packets May 17 20:39:26: %CSM-6-PORT: ethernet 2/4 link state UP service state UP, overall admin is UP May 17 20:39:26: %CSM-6-CARD: Card in slot 2 entering In Service state. May 17 20:39:26: %CSM-6-PORT: ethernet 2/3 link state UP service state UP, overall admin is UP May 17 20:39:26: %CSM-6-PORT: ethernet 2/15 link state UP service state UP, overall admin is UP May 17 20:39:26: %CSM-6-PORT: ethernet 2/16 link state UP service state UP, overall admin is UP May 17 20:39:26: %PPAINFRA-6-IFACE_INFO: 588d172e/0000000003/908300000:02/IPPA/EU00:ROUTING_READY sent to CSM May 17 20:39:26: %QOS-6-INFO: qos info: PPA just reborn 0 May 17 20:39:26: %QOS-6-INFO: qos info: ePPA reg on slot 2 May 17 20:39:28: %CSM-6-PORT: ethernet 2/1 link state UP service state UP, overall admin is UP May 17 20:39:28: %CSM-6-PORT: ethernet 2/2 link state UP service state UP, overall admin is UP May 17 20:39:30: %LG-3-GRP_LOG: link-group LACP_SE100 state: UP May 17 20:39:30: %LG-3-GRP_LOG: link-group LACP_SE100 PVC:300 state: UP May 17 20:39:30: %LG-3-GRP_LOG: link-group LACP_SE100 PVC:301 state: UP May 17 20:39:30: %LG-3-GRP_LOG: link-group LACP_SE100 PVC:302 state: UP May 17 20:39:30: %LG-3-GRP_LOG: link-group LACP_SE100 PVC:333 state: UP May 17 20:39:37: %PM-1-ALERT: Process IPPA IPC SLOT 2, pid 0x80020025, is not responding. May 17 20:39:37: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLICY to EPPA, pol_grid 1 May 17 20:39:38: %NAT-3-INT_ERR: work thread: failed to send UNBIND POLIC.. Из-за чего может быть проблема?

не помогло и отключение ISG. Пока удалось решить данную проблему включением БДКОМ-ов через дополнительный свитч Конфигурация данного коммутатора отличается от С704 (в который раньше были включены BDCOMы) включенным DHCP-snooping binding. Конфигурация портов: Interface Ethernet1/25 description BDCOM_1x8 ip multicast destination-control access-group 6000 switchport mode trunk switchport trunk allowed vlan 303;331;400 ip access-group 100 in loopback-detection specified-vlan 303;331;400 loopback-detection control shutdown arp-guard ip 192.168.7.1 arp-guard ip 192.168.6.1 arp-guard ip 192.168.5.1 arp-guard ip 192.168.4.1 arp-guard ip 192.168.3.1 arp-guard ip 192.168.11.1 arp-guard ip 192.168.10.1 arp-guard ip 10.100.0.10 arp-guard ip 192.168.2.1 arp-guard ip 192.168.1.1 arp-guard ip 192.168.0.1 arp-guard ip 10.100.2.9 arp-guard ip 10.0.0.1 arp-guard ip 10.120.0.1 arp-guard ip 10.100.2.7 arp-guard ip 10.100.2.1 ip dhcp snooping action shutdown recovery 180 на С704: (в который раньше были включены BDCOMы) Interface Ethernet4/11 description BDCOM_1x8 ip multicast destination-control access-group 6011 switchport mode trunk switchport trunk allowed vlan 303;331;400 ipv6 access-group 600 in loopback-detection specified-vlan 300;303;331-332;400 loopback-detection control shutdown ipv6 security-ra enable arp-guard ip 10.100.0.10 arp-guard ip 192.168.2.1 arp-guard ip 192.168.1.1 arp-guard ip 192.168.0.1 arp-guard ip 10.120.0.1 arp-guard ip 10.0.0.1 arp-guard ip 10.100.2.1 anti-arpscan trust supertrust-port Уже более 5 дней наблюдаем нормальную работу БДКОМ-ов. До этого каждый день, по несколько раз возникал некий штром со 100% загрузкой процессоров всех БДКОМов одновременно. Похоже что есть ошибка в прошивке БДКОМ-ов относительно DHCP-snooping. Какие может будут Ваши идеи по данному оборудованию?

ОЛТы подключены не каскадом. ОЛТ: Р3310 - 1 шт. (резервный 1 абонент) Р3608 - 1 шт. 58 ОНУшек Р3616 - 2 шт. 390 и 458 ОНУшек Команда FFP доступна только на ОЛТ Р3310, на других моделях ее нет.