lumenok

А после прописывания ону сброс и ресет онушки делали? send omci restore interface ont 0/111

Да дело в том что когда я пингую клиентом по ethernet , то такой проблемы нет!

ВСем привет, я все по старой проблеме , плавает пинг, когда клиент смотрит ютуб или качает торренты, то есть при нагрузке канала. С gpon ранее дело не имели, если канал не нагружен, то пинг до шлюза 2-3 ms, иногда подскакивает до 10, это норма для gpon'a? Скриншоты приложил.

Поделитесь мибами, пожалуйста!

>Если он не умеет терминировать, то почему вы называете его брас? Наверное лишь часть функций браса, радиус сессии абонентов и применяемые им политики , а так режем на нем скорости! По цене это индивидуально, покрайней мере у нас было!

Перешли с redback' ов se100 на rdp который econat2040, терминировать не умеет, ставился в разрез, делаем на нем брас и нат, а также фильтрацию ркн, есть свои нюансы, но все устраивает.

Olt, только L2

День добрый! Тестирует zte c320 прошивка 1.2.5p3. Никто сталкивался такой проблемой. У абонента на gpon пинг плавает, даже до шлюза, а если абонен тсмотрит например видео в ютубу то даже до шлюза может прыгать до 40 мс? Абонентов всего пять , все тестовые.

CSCva92216 Help | Feedback Feedback BGP session is reset when unrecognized capability received in OPEN message CSCva92216 Description Symptom: BGP session will not come up with peer if an unrecognized or unsupported capability is received from the peer in the BGP OPEN. Message similar to the following might be observed: Aug 4 16:20:22.627: %BGP-3-NOTIFICATION: sent to neighbor 10.100.100.100 active 2/0 (open: unspecific subcode) 0 bytes Aug 4 16:20:22.627: %BGP-4-MSGDUMP: unsupported or mal-formatted message received from 10.100.100.100: Expected behavior is that the local device should ignore the unrecognized/unsupported capability and bring the session up with the known capabilities, but that does not occur. Conditions: Local device is an IOS or IOS-XE device running a release that has the changes introduced in CSCuz20869. Remote BGP peer sends a BGP OPEN which advertises a capability that is not recognized or not supported by the local device. Workaround: Identify the unsupported capability that is being advertised, and reconfigure the remote peer to suppress advertisement of this capability. The exact method to do so will vary based on the remote peer's platform, software version, etc; The unsupported capability can be identified by enabling "debug bgp ipv4 unicast in" on the local peer. For example the following debug messages tell us that the peer is sending as BGP capability 5 which is not supported by the local peer: *Sep 11 18:31:14.867: BGP: 10.128.129.134 active OPEN has CAPABILITY code: 5, length 6 *Sep 11 18:31:14.867: BGP: 10.128.129.134 active unrecognized capability code: 5 *Sep 11 18:31:14.867: BGP: 10.128.129.134 active malformed/un-supported OPEN capability *Sep 11 18:31:14.867: BGP: 10.128.129.134 active went from OpenSent to Closing *Sep 11 18:31:14.867: %BGP-3-NOTIFICATION: sent to neighbor 10.128.129.134 active 2/0 (open: unspecific subcode) 0 bytes Further Problem Description: This defect is unintended collateral caused by the fix of CSCuz20869. If a given release does not have the prior fix, then it is not impacted by this problem. Никто не словил еще такой же сюрприз на cisco по bgp? Описание на cisco.com

Не забывайте нас освещать!)

В режим конфигурирования нас входили ? config nas

set vlan 1712 add port 1-24 untag set vlan 1712 add port 25-28 tag set vlan 3046 add port 1-24 untag set vlan 3046 add port 25-28 tag set vlan 1712 enable set vlan 3046 enable ... set igmp snooping enable set igmp snooping add vlan 1712,3046 set igmp snooping fastleave enable set igmp snooping multicast-ring enable set igmp snooping multicast-ring add cascade port 25-28 ... iptv control enable iptv cac-rule enable iptv channel-group mvlan 1712 grouplist 239.195.0.0 239.195.255.255 name CHGNAME0 id 0 iptv channel-group mvlan 1712 grouplist 233.166.0.0 233.166.255.255 name CHGNAME1 id 1 iptv port 1 service start iptv port 1 control-mode channel iptv port 1 channel-group id-list 0-1 order iptv port 2 service start iptv port 2 control-mode channel iptv port 2 channel-group id-list 0-1 order iptv port 3 service start iptv port 3 control-mode channel iptv port 3 channel-group id-list 0-1 order iptv port 4 service start iptv port 4 control-mode channel iptv port 4 channel-group id-list 0-1 order iptv port 5 service start iptv port 5 control-mode channel iptv port 5 channel-group id-list 0-1 order iptv port 6 service start iptv port 6 control-mode channel iptv port 6 channel-group id-list 0-1 order iptv port 7 service start iptv port 7 control-mode channel iptv port 7 channel-group id-list 0-1 order iptv port 8 service start iptv port 8 control-mode channel iptv port 8 channel-group id-list 0-1 order iptv port 9 service start iptv port 9 control-mode channel iptv port 9 channel-group id-list 0-1 order iptv port 10 service start iptv port 10 control-mode channel iptv port 10 channel-group id-list 0-1 order iptv port 11 service start iptv port 11 control-mode channel iptv port 11 channel-group id-list 0-1 order iptv port 12 service start iptv port 12 control-mode channel iptv port 12 channel-group id-list 0-1 order iptv port 13 service start iptv port 13 control-mode channel iptv port 13 channel-group id-list 0-1 order iptv port 14 service start iptv port 14 control-mode channel iptv port 14 channel-group id-list 0-1 order iptv port 15 service start iptv port 15 control-mode channel iptv port 15 channel-group id-list 0-1 order iptv port 16 service start iptv port 16 control-mode channel iptv port 16 channel-group id-list 0-1 order iptv port 17 service start iptv port 17 control-mode channel iptv port 17 channel-group id-list 0-1 order iptv port 18 service start iptv port 18 control-mode channel iptv port 18 channel-group id-list 0-1 order iptv port 19 service start iptv port 19 control-mode channel iptv port 19 channel-group id-list 0-1 order iptv port 20 service start iptv port 20 control-mode channel iptv port 20 channel-group id-list 0-1 order iptv port 21 service start iptv port 21 control-mode channel iptv port 21 channel-group id-list 0-1 order iptv port 22 service start iptv port 22 control-mode channel iptv port 22 channel-group id-list 0-1 order iptv port 23 service start iptv port 23 control-mode channel iptv port 23 channel-group id-list 0-1 order iptv port 24 service start iptv port 24 control-mode channel iptv port 24 channel-group id-list 0-1 order iptv port 25 service start iptv port 25 control-mode channel iptv port 25 channel-group id-list 0-1 order iptv port 26 service start iptv port 26 control-mode channel iptv port 26 channel-group id-list 0-1 order iptv port 27 service start iptv port 27 control-mode channel iptv port 27 channel-group id-list 0-1 order iptv port 28 service start iptv port 28 control-mode channel iptv port 28 channel-group id-list 0-1 order iptv port 25 vlan 1712 service start iptv port 25 vlan 1712 control-mode channel iptv port 25 vlan 1712 channel-group id-list 0-1 order iptv port 26 vlan 1712 service start iptv port 26 vlan 1712 control-mode channel iptv port 26 vlan 1712 channel-group id-list 0-1 order iptv port 27 vlan 1712 service start iptv port 27 vlan 1712 control-mode channel iptv port 27 vlan 1712 channel-group id-list 0-1 order iptv port 28 vlan 1712 service start iptv port 28 vlan 1712 control-mode channel iptv port 28 vlan 1712 channel-group id-list 0-1 order Это на 2928E, может поможет. 1712 это мультикаст вилан, а 3046 это абонентский вилан.

Отвлекусь в сторону dgs-1100-10/me, у нас пропадали настройки dhcp_relay после перезагрузки на некоторых коммутаторах, обновляли на тот момент до прошивки 1.01.B091, но все равно пробелма оставлась. Решали следующим образом, выгружали конфиг, сбрасывали коммутатор в default, конфиг заливали обратно и после этого он их запоминал.

Спасибо.

mse.rus777, а с разбором проблем у вас не возникало? Вообще как разбирается, есть тонкости сложности?