Перейти до

SERCOMM RV6688 ONT - ZTE C320 OLT onu постоянно переподключается


pod

Рекомендованные сообщения

Имеется голова ZTE ZXA C320:



Rack Shelf Slot CfgType RealType Port    HardVer SoftVer         Status
-------------------------------------------------------------------------------
1    1     1    GTGO    GTGOG    8       120301  V1.2.5P3        INSERVICE    
1    1     3    PRAM    PRAM     3               V1.01           INSERVICE    
1    1     4    SMXA    SMXA     3       110702  V1.2.5P3        INSERVICE    

На ней работают онушки huawei, tp-link. Конфиг по минимуму, все в режиме моста. Все ок.
 
На днях попалась в руки ONU SERCOMM RV6688BCM.MGTS
Онушка подключается, даже проходят пинги, но она постоянно отключается от головы и снова подключается.
Возможно что-то нужно дописать в конфиг?

Дебаг с головы:

May 19 18:34:31 192.168.252.10 2016 May 19 18:34:31 ZTE debug-log:MAC: 29541.44s olt:7 onu:2(1) DEACTIVE ONU success
May 19 18:34:32 192.168.252.10 2016 May 19 18:34:31 ZTE debug-log:
OMCI: 29541.44s olt:7 ont:2 OMCI deactivate result: 0
May 19 18:34:34 192.168.252.10 2016 May 19 18:34:33 ZTE debug-log:MAC: 29543.45s olt:7 onu:2(1) SN:SCOM14173675
May 19 18:34:44 192.168.252.10 2016 May 19 18:34:43 ZTE debug-log:MAC: 29553.45s olt:7 onu:2(1) SN:SCOM14173675
May 19 18:34:54 192.168.252.10 2016 May 19 18:34:53 ZTE debug-log:MAC: 29563.45s olt:7 onu:2(1) SN:SCOM14173675
May 19 18:35:04 192.168.252.10 2016 May 19 18:35:03 ZTE debug-log:MAC: 29573.45s olt:7 onu:2(1) SN:SCOM14173675
May 19 18:35:04 192.168.252.10 2016 May 19 18:35:03 ZTE debug-log:MAC: 29573.45s olt:7 onu:2(1) MUX ACTIVE ONU return value:0
task:MuxOnuState
May 19 18:35:05 192.168.252.10 2016 May 19 18:35:04 ZTE debug-log:MAC: 29574.51s olt:7 onu:2(1) RANG OK:265515
May 19 18:35:05 192.168.252.10 2016 May 19 18:35:04 ZTE debug-log:MAC: 29574.51s olt:7 onu:2(1) RANG OK:265515
May 19 18:35:05 192.168.252.10 2016 May 19 18:35:04 ZTE debug-log:MAC: 29574.53s olt:7 onu:2(1) PASSWORD OK:
May 19 18:35:05 192.168.252.10 2016 May 19 18:35:04 ZTE debug-log:MAC: 29574.53s olt:7 onu:2(1) PASSWORD OK:
May 19 18:35:05 192.168.252.10 2016 May 19 18:35:04 ZTE debug-log:MAC: 29574.53s olt:7 onu:2(1) ACTIVE ONU success
May 19 18:35:05 192.168.252.10 2016 May 19 18:35:04 ZTE debug-log:MAC: 29574.55s olt:7 onu:2(1) OMCC OK
May 19 18:35:05 192.168.252.10 2016 May 19 18:35:04 ZTE debug-log:MAC: 29574.55s olt:7 onu:2(1) OMCC OK
May 19 18:35:05 192.168.252.10 2016 May 19 18:35:04 ZTE debug-log:MAC: 29574.58s olt:7 onu:2(1) ALLOCID OK tcont:1
May 19 18:35:05 192.168.252.10 2016 May 19 18:35:04 ZTE debug-log:MAC: 29574.59s olt:7 onu:2(1) ALLOCID OK tcont:257
May 19 18:35:06 192.168.252.10 2016 May 19 18:35:06 ZTE debug-log:
OMCI: 29576.39s olt:7 ont:2 Old ONT
May 19 18:35:06 192.168.252.10 2016 May 19 18:35:06 ZTE debug-log:MAC: 29576.39s olt:7 onu:2(1) REPORT OMCC OK
May 19 18:35:06 192.168.252.10 2016 May 19 18:35:06 ZTE debug-log:
OMCI: 29576.40s olt:7 ont:2 mibDataSyncAtOlt:91,mibDataSyncAtOnt:91
May 19 18:35:06 192.168.252.10 2016 May 19 18:35:06 ZTE debug-log:
OMCI: 29576.40s olt:7 ont:2 Not need trigger mib upload
May 19 18:35:06 192.168.252.10 2016 May 19 18:35:06 ZTE debug-log:
OMCI: 29576.40s olt:7 ont:2 Deliver finished
May 19 18:35:06 192.168.252.10 2016 May 19 18:35:06 ZTE debug-log:
OMCI: 29576.40s olt:7 ont:2 Mib upload finished, success! syncReason:2.1-period,2-reEst,3-start
Mib sync result report type:0.0-omccReady,1-no report,2-mibDataSync not equal for omccReady,3-mibDataSync not equal for RestoreAPI
May 19 18:35:12 192.168.252.10 2016 May 19 18:35:11 ZTE debug-log:MAC: 29581.64s olt:7 onu:2(1) MUX DEACTIVE ONU return value:0
task:tXponNpPlCtrl
May 19 18:35:12 192.168.252.10 2016 May 19 18:35:11 ZTE debug-log:MAC: 29581.66s olt:7 onu:2(1) DEACTIVE ONU success
May 19 18:35:12 192.168.252.10 2016 May 19 18:35:11 ZTE debug-log:
OMCI: 29581.66s olt:7 ont:2 OMCC lost
May 19 18:35:12 192.168.252.10 2016 May 19 18:35:11 ZTE debug-log:
OMCI: 29581.66s olt:7 ont:2 OMCI deactivate result: 0
May 19 18:35:14 192.168.252.10 2016 May 19 18:35:13 ZTE debug-log:MAC: 29583.45s olt:7 onu:2(1) SN:SCOM14173675
May 19 18:35:24 192.168.252.10 2016 May 19 18:35:23 ZTE debug-log:MAC: 29593.45s olt:7 onu:2(1) SN:SCOM14173675
May 19 18:35:34 192.168.252.10 2016 May 19 18:35:33 ZTE debug-log:MAC: 29603.45s olt:7 onu:2(1) SN:SCOM14173675
May 19 18:35:44 192.168.252.10 2016 May 19 18:35:43 ZTE debug-log:MAC: 29613.64s olt:7 onu:2(1) SN:SCOM14173675
May 19 18:35:44 192.168.252.10 2016 May 19 18:35:43 ZTE debug-log:MAC: 29613.64s olt:7 onu:2(1) MUX ACTIVE ONU return value:0
task:MuxOnuState
May 19 18:35:45 192.168.252.10 2016 May 19 18:35:44 ZTE debug-log:MAC: 29614.70s olt:7 onu:2(1) RANG OK:265515
May 19 18:35:45 192.168.252.10 2016 May 19 18:35:44 ZTE debug-log:MAC: 29614.70s olt:7 onu:2(1) RANG OK:265515
May 19 18:35:45 192.168.252.10 2016 May 19 18:35:44 ZTE debug-log:MAC: 29614.72s olt:7 onu:2(1) PASSWORD OK:


Конфиг головы:

Building configuration...
!**********Before interface -- show run on RP start!*********
!
sdisk disable
set-pnp enable
add-rack rackno 1 racktype C320Rack
add-shelf rackno 1 shelfno 1 shelftype C320_SHELF
add-subcard rackno 1 shelfno 1 slotno 4 subcardno 1 UCDC/1
add-card rackno 1 shelfno 1 slotno 1 GTGO
system-monitor watchdog rackno 1 shelfno 1 slotno 1 disable
system-monitor watchdog-duration rackno 1 shelfno 1 slotno 1 value 5
system-monitor endless-loop duration rackno 1 shelfno 1 slotno 1 value 75
system-monitor endless-loop reboot rackno 1 shelfno 1 slotno 1 disable
system-monitor task-suspend-reboot rackno 1 shelfno 1 slotno 1 all
system-monitor watchdog rackno 1 shelfno 1 slotno 3 disable
system-monitor watchdog-duration rackno 1 shelfno 1 slotno 3 value 5
system-monitor endless-loop duration rackno 1 shelfno 1 slotno 3 value 75
system-monitor endless-loop reboot rackno 1 shelfno 1 slotno 3 disable
system-monitor task-suspend-reboot rackno 1 shelfno 1 slotno 3 all
system-monitor watchdog rackno 1 shelfno 1 slotno 4 disable
system-monitor watchdog-duration rackno 1 shelfno 1 slotno 4 value 5
system-monitor endless-loop duration rackno 1 shelfno 1 slotno 4 value 75
system-monitor endless-loop reboot rackno 1 shelfno 1 slotno 4 disable
system-monitor task-suspend-reboot rackno 1 shelfno 1 slotno 4 all
!
system-monitor inner-port-check disable
!
his-performance sample disable
his-performance alarm disable
his-performance auto-upload disable
!
clock
!
ptp
!
security port-protect disable
!
eth-switch max-frame-length 1600
!
vlan database
vlan 20
!
vlan 20
ip dhcp snooping
!
epon
!
port-location access-node-identifier inband-mac
port-location hostname cc1afab43450
port-location flexible-syntax enable
port-location flexible-syntax add string zte
port-location flexible-syntax add variable access_node_id
port-location flexible-syntax add string Vlan
port-location flexible-syntax add variable cvlan
port-location flexible-syntax add string +1/
port-location flexible-syntax add variable slot
port-location flexible-syntax add string /
port-location flexible-syntax add variable port
port-location flexible-syntax add string :
port-location flexible-syntax add variable onu-id
!
dhcp-option82 enable
dhcp6-option18 disable
pppoe-plus disable
ndp-lio disable
!
igmp disable
mld disable
gpon
profile tcont 500M type 4 maximum 500000
!
gpon
!
pon
onu-type HG8010C gpon description 1GE
onu-type HG8010C gpon max-tcont 7
onu-type HG8010C gpon max-gemport 32
onu-type HG8010C gpon max-switch-perslot 1
onu-type HG8010C gpon max-flow-perswitch 8
onu-type HG8346M gpon description 4FE,2POTS,WIFI
onu-type HG8346M gpon max-tcont 7
onu-type HG8346M gpon max-gemport 32
onu-type HG8346M gpon max-switch-perslot 1
onu-type HG8346M gpon max-flow-perswitch 8
onu-type RV6688BMC gpon description 4GE,2POTS,WIFI
onu-type RV6688BMC gpon max-tcont 8
onu-type RV6688BMC gpon max-gemport 32
onu-type RV6688BMC gpon max-switch-perslot 8
onu-type RV6688BMC gpon max-flow-perswitch 8
onu-type RV6688BMC gpon max-iphost 1
onu-type RV6688BMC gpon service-mgmt-via-non-omci wifi enable
onu-type TLGP110 gpon description 1GE
onu-type TLGP110 gpon max-tcont 16
onu-type TLGP110 gpon max-gemport 64
onu-type TLGP110 gpon max-switch-perslot 1
onu-type TLGP110 gpon max-flow-perswitch 8
onu-type-if HG8010C eth_0/1
onu-type-if HG8346M eth_0/1
onu-type-if HG8346M eth_0/2
onu-type-if HG8346M eth_0/3
onu-type-if HG8346M eth_0/4
onu-type-if HG8346M pots_0/1
onu-type-if HG8346M pots_0/2
onu-type-if HG8346M wifi_0/1
onu-type-if RV6688BMC eth_0/1
onu-type-if RV6688BMC eth_0/2
onu-type-if RV6688BMC eth_0/3
onu-type-if RV6688BMC eth_0/4
onu-type-if RV6688BMC pots_0/1
onu-type-if RV6688BMC pots_0/2
onu-type-if TLGP110 eth_0/1
uncfg-onu-display-info model version mac sn pw hexpw loid loidpw rid
!
onu-pnp
!
ip-service ip-source-guard disable
ip dhcp snooping enable
fan high-threshold 75
!
interface gpon-olt_1/1/8
onu 2 type RV6688BMC sn SCOMxxxxxxxx
!
interface gpon-onu_1/1/8:2
name -
sn-bind enable sn
tcont 1 name T1 profile 500M
gemport 1 unicast tcont 1 dir both
switchport mode hybrid vport 1
service-port 1 vport 1 user-vlan 20 vlan 20
port-location format flexible-syntax vport 1
dhcp-option82 enable vport 1
dhcp-option82 trust true replace vport 1
ip dhcp snooping enable vport 1
!
interface gei_1/4/3
hybrid-attribute copper
negotiation auto
flowcontrol disable
port-protect disable
uplink-isolate disable
switchport mode trunk
switchport vlan 20 tag
!
!**********After interface -- show run on RP start!**********
!
pon
!
pon-onu-mng gpon-onu_1/1/8:2
service HSI type internet gemport 1 cos 0 vlan 20
vlan port eth_0/1 mode tag vlan 20
!
pon
!
mpnat trans-table aging-time 60
mpnat onu-telnet idle-time 3
mpnat onu-ftp aging-time 5
mpnat onu-snmp aging-time 30
mpnat onu-ftp-data aging-time 5
mpnat onu-mng-port auto-alloc disable
!
bcm-server listen-port 5000
!
auto-write disable
!
user-suspend mode none
!
alarm disable
alarm confirm
nms-hello-trap disable
alarm trap-confirm retry 1 timeout 30
!
control-panel
packet-limit all 1000
!
!
end

  
Дебаг с самой онушки:

 

[PloamHandler] DIS SERIAL NUM 0.
[PloamHandler] DIS SERIAL NUM 1.
[PloamHandler] CONFIGURE PORT ID P65535 M1.
[PloamHandler] DACT ONU.
[PloamHandler] ASSIGN ONU ID 2.
[PloamHandler] CONFIGURE PORT ID P2 M0.
[MJ] socapi.c:5289: create OMCI channel[flow id:0, tcontId:0 tcont queue id:0, gem port2, isEncry:0, priority queue:0]
[PloamHandler] CONFIGURE PORT ID P2 M0.
[PloamHandler] CONFIGURE PORT ID P2 M0.
[PloamHandler] ENCRYPTED PORT ID P2 M0.
[MJ] socapi.c:5326: modify OMCI channel[isEncry:0]
[PloamHandler] ENCRYPTED PORT ID P2 M0.
[MJ] socapi.c:5326: modify OMCI channel[isEncry:0]
[PloamHandler] ENCRYPTED PORT ID P2 M0.
[MJ] socapi.c:5326: modify OMCI channel[isEncry:0]
[PloamHandler] ENCRYPTED PORT ID P130 M0.
[PloamHandler] ENCRYPTED PORT ID P130 M0.
[PloamHandler] ENCRYPTED PORT ID P130 M0.
[PloamHandler] ASSIGN ALLOC ID 2 S0.
[PloamHandler] ASSIGN ALLOC ID 2 S0.
[PloamHandler] ASSIGN ALLOC ID 2 S0.
[PloamHandler] ASSIGN ALLOC ID 257 S0.
[PloamHandler] ASSIGN ALLOC ID 257 S0.
[PloamHandler] ASSIGN ALLOC ID 257 S0.
OMCCRX:
RX time : sec 504, usec 649870
33 86 49 0A 01 01 00 00 40 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 28 4F C8 4C 6E

OMCI Request Message Header
+++++++++++++++++++++++++++++++++
Transaction id = 0x3386
Message type = 0x49 - Get, DB = 0, AR = 1, AK = 0
Device id = 0x0A
Entity class = 257 (0x0101) - Ont2G
Entity instance = 0x0000

OMCI Request Message Content
+++++++++++++++++++++++++++++++++
Attribute mask = 0x4000
Padding:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00

[iN] ontpmx.c:199: ProcessMsg: MEI50:0, AI9, IV0x000000A1.

OMCI Response Message Header
---------------------------------
Transaction id = 0x3386
Message type = 0x29 - Get, DB = 0, AR = 0, AK = 1
Device id = 0x0A
Entity class = 257 (0x0101) - Ont2G
Entity instance = 0x0000

OMCI Response Message Content
---------------------------------
Result = 0x00 - Command processed successfully
Attribute mask = 0x4000
OmccVersion = 0xA0
Padding:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
Optional attribute mask = 0x0000
Attribute execution mask = 0x0000

OMCCTX:
TX time : sec 504, usec 673130
33 86 29 0A 01 01 00 00 00 40 00 A0 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 28 89 0A 05 7A
[iN] ontpmx.c:342: CRCtx: TI13190, PRI0, AI9, MEIC257:0, CRC0x890A057A.
OMCCRX:
RX time : sec 504, usec 678677
33 87 49 0A 00 02 00 00 80 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 28 64 76 35 00

OMCI Request Message Header
+++++++++++++++++++++++++++++++++
Transaction id = 0x3387
Message type = 0x49 - Get, DB = 0, AR = 1, AK = 0
Device id = 0x0A
Entity class = 2 (0x0002) - OntData
Entity instance = 0x0000

OMCI Request Message Content
+++++++++++++++++++++++++++++++++
Attribute mask = 0x8000
Padding:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00

[iN] ontpmx.c:199: ProcessMsg: MEI51:0, AI9, IV0x000000A2.

OMCI Response Message Header
---------------------------------
Transaction id = 0x3387
Message type = 0x29 - Get, DB = 0, AR = 0, AK = 1
Device id = 0x0A
Entity class = 2 (0x0002) - OntData
Entity instance = 0x0000

OMCI Response Message Content
---------------------------------
Result = 0x00 - Command processed successfully
Attribute mask = 0x8000
MibDataSync = 0x5B
Padding:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
Optional attribute mask = 0x0000
Attribute execution mask = 0x0000

OMCCTX:
TX time : sec 504, usec 701374
33 87 29 0A 00 02 00 00 00 80 00 5B 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 28 F1 18 BB DA
[iN] ontpmx.c:342: CRCtx: TI13191, PRI0, AI9, MEIC2:0, CRC0xF118BBDA.
OMCCRX:
RX time : sec 504, usec 706304
33 88 49 0A 00 F7 00 00 20 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 28 D8 90 00 E8
[MN] pmutil.c:933: Unknown class number: ONU0:0, TI0x3388(13192), MT0x49(AI9), CNI247:0.
[MN] ontpm.c:3899: ValidateRxPacket() failed: TI13192, PRI0, AI9, MEIC247:0, RT0.

OMCI Response Message Header
---------------------------------
Transaction id = 0x3388
Message type = 0x29 - Get, DB = 0, AR = 0, AK = 1
Device id = 0x0A
Entity class = 247 (0x00F7) - None
Entity instance = 0x0000

OMCI Response Message Content
---------------------------------
Result = 0x00 - Command processed successfully
Attribute mask = 0x0000
[MN] pmprint.c:597: Unknown class number.
Padding:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00
Optional attribute mask = 0x0000
Attribute execution mask = 0x0000

OMCCTX:
TX time : sec 504, usec 720790
33 88 29 0A 00 F7 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 28 56 E2 E4 FA
[iN] ontpmx.c:342: CRCtx: TI13192, PRI0, AI9, MEIC247:0, CRC0x56E2E4FA.
[MN] ontpmx.c:217: OmciProcessRxPacket() failed.
OMCCRX:
RX time : sec 504, usec 726410
33 89 49 0A 01 07 01 01 00 08 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 28 28 CB F8 DB

OMCI Request Message Header
+++++++++++++++++++++++++++++++++
Transaction id = 0x3389
Message type = 0x49 - Get, DB = 0, AR = 1, AK = 0
Device id = 0x0A
Entity class = 263 (0x0107) - AniG
Entity instance = 0x0101

OMCI Request Message Content
+++++++++++++++++++++++++++++++++
Attribute mask = 0x0008
Padding:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00

[iN] ontpmx.c:199: ProcessMsg: MEI1:257, AI9, IV0x000000A3.

OMCI Response Message Header
---------------------------------
Transaction id = 0x3389
Message type = 0x29 - Get, DB = 0, AR = 0, AK = 1
Device id = 0x0A
Entity class = 263 (0x0107) - AniG
Entity instance = 0x0101

OMCI Response Message Content
---------------------------------
Result = 0x00 - Command processed successfully
Attribute mask = 0x0008
OntRspTime = 0x0000
Padding:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00
Optional attribute mask = 0x0000
Attribute execution mask = 0x0000

OMCCTX:
TX time : sec 505, usec 84136
33 89 29 0A 01 07 01 01 00 00 08 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 28 58 19 24 83
[iN] ontpmx.c:342: CRCtx: TI13193, PRI0, AI9, MEIC263:257, CRC0x58192483.
OMCCRX:
RX time : sec 505, usec 88642
33 8A 4B 0A 00 02 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 28 E6 AA C3 35

OMCI Request Message Header
+++++++++++++++++++++++++++++++++
Transaction id = 0x338A
Message type = 0x4B - Get all alarms, DB = 0, AR = 1, AK = 0
Device id = 0x0A
Entity class = 2 (0x0002) - OntData
Entity instance = 0x0000

OMCI Request Message Content
+++++++++++++++++++++++++++++++++
Padding:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[iN] ontpmx.c:199: ProcessMsg: MEI52:0, AI11, IV0x000000A4.

OMCI Response Message Header
---------------------------------
Transaction id = 0x338A
Message type = 0x2B - Get all alarms, DB = 0, AR = 0, AK = 1
Device id = 0x0A
Entity class = 2 (0x0002) - OntData
Entity instance = 0x0000

OMCI Response Message Content
---------------------------------
Number Of subsequent commands = 0x0001
Padding:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00

OMCCTX:
TX time : sec 505, usec 110953
33 8A 2B 0A 00 02 00 00 00 01 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 28 58 D6 AF 73
[iN] ontpmx.c:342: CRCtx: TI13194, PRI0, AI11, MEIC2:0, CRC0x58D6AF73.
OMCCRX:
RX time : sec 505, usec 116423
33 8B 49 0A 00 07 00 00 F0 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 28 4C 01 FC BD

OMCI Request Message Header
+++++++++++++++++++++++++++++++++
Transaction id = 0x338B
Message type = 0x49 - Get, DB = 0, AR = 1, AK = 0
Device id = 0x0A
Entity class = 7 (0x0007) - SwImage
Entity instance = 0x0000

OMCI Request Message Content
+++++++++++++++++++++++++++++++++
Attribute mask = 0xF000
Padding:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00

[iN] ontpmx.c:199: ProcessMsg: MEI72:0, AI9, IV0x000000A5.

OMCI Response Message Header
---------------------------------
Transaction id = 0x338B
Message type = 0x29 - Get, DB = 0, AR = 0, AK = 1
Device id = 0x0A
Entity class = 7 (0x0007) - SwImage
Entity instance = 0x0000

OMCI Response Message Content
---------------------------------
Result = 0x00 - Command processed successfully
Attribute mask = 0xF000
Version = 7363332E312E3433000000000000
IsCommitted = 0x00
IsActive = 0x00
IsValid = 0x01
Padding:
00 00 00 00 00 00 00 00
Optional attribute mask = 0x0000
Attribute execution mask = 0x0000

OMCCTX:
TX time : sec 505, usec 143087
33 8B 29 0A 00 07 00 00 00 F0 00 73 63 33 2E 31
2E 34 33 00 00 00 00 00 00 00 00 01 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 28 A4 B2 7C 6D
[iN] ontpmx.c:342: CRCtx: TI13195, PRI0, AI9, MEIC7:0, CRC0xA4B27C6D.
OMCCRX:
RX time : sec 505, usec 149119
33 8C 49 0A 00 07 00 01 F0 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 28 98 DD 68 00

OMCI Request Message Header
+++++++++++++++++++++++++++++++++
Transaction id = 0x338C
Message type = 0x49 - Get, DB = 0, AR = 1, AK = 0
Device id = 0x0A
Entity class = 7 (0x0007) - SwImage
Entity instance = 0x0001

OMCI Request Message Content
+++++++++++++++++++++++++++++++++
Attribute mask = 0xF000
Padding:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00

[iN] ontpmx.c:199: ProcessMsg: MEI72:1, AI9, IV0x000000A6.

OMCI Response Message Header
---------------------------------
Transaction id = 0x338C
Message type = 0x29 - Get, DB = 0, AR = 0, AK = 1
Device id = 0x0A
Entity class = 7 (0x0007) - SwImage
Entity instance = 0x0001

OMCI Response Message Content
---------------------------------
Result = 0x00 - Command processed successfully
Attribute mask = 0xF000
Version = 7363332E312E3433000000000000
IsCommitted = 0x01
IsActive = 0x01
IsValid = 0x01
Padding:
00 00 00 00 00 00 00 00
Optional attribute mask = 0x0000
Attribute execution mask = 0x0000

OMCCTX:
TX time : sec 505, usec 177895
33 8C 29 0A 00 07 00 01 00 F0 00 73 63 33 2E 31
2E 34 33 00 00 00 00 00 00 01 01 01 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 28 FB 12 B6 FC
[iN] ontpmx.c:342: CRCtx: TI13196, PRI0, AI9, MEIC7:1, CRC0xFB12B6FC.
OMCCRX:
RX time : sec 505, usec 517329
33 8D 4C 0A 00 02 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 28 4C DD 37 A2

OMCI Request Message Header
+++++++++++++++++++++++++++++++++
Transaction id = 0x338D
Message type = 0x4C - Get all alarms next, DB = 0, AR = 1, AK = 0
Device id = 0x0A
Entity class = 2 (0x0002) - OntData
Entity instance = 0x0000

OMCI Request Message Content
+++++++++++++++++++++++++++++++++
Command sequence number = 0x0000
Padding:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00


OMCI Response Message Header
---------------------------------
Transaction id = 0x338D
Message type = 0x2C - Get all alarms next, DB = 0, AR = 0, AK = 1
Device id = 0x0A
Entity class = 2 (0x0002) - OntData
Entity instance = 0x0000

OMCI Response Message Content
---------------------------------
Entity class reported alarms = 0x0100 - OntG
Entity instance reported alarms = 0x0000
Alarms bitmap = 0x20000000000000000000000000000000000000000000000000000000

OMCCTX:
TX time : sec 505, usec 533802
33 8D 2C 0A 00 02 00 00 01 00 00 00 20 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 28 58 3D 7B C4
[iN] ontpmx.c:342: CRCtx: TI13197, PRI0, AI12, MEIC2:0, CRC0x583D7BC4.
[PloamHandler] DACT ONU.
[MJ] socapi.c:5367: remove OMCI channel[tcontId:0, rate control id:716231564, tcont queue id:0]
[PloamHandler] CONFIGURE PORT ID P65535 M1.
[PloamHandler] DACT ONU.
[PloamHandler] DACT ONU.

 

 
Подскажите в какую сторону копать?

Ссылка на сообщение
Поделиться на других сайтах

Не хочу вас обидеть уважаемый , но вы уже в третий раз пишете одно и то же в разных ветках , теперь в отдельном топике .  Как вы заметили ответов не очень много и их по ходу не будет  . 

Ссылка на сообщение
Поделиться на других сайтах

Попытайтесь раздобыть прошивки под ваши устройства , весьма возможно вы решите свою проблему , других вариантов лично я не вижу .

Ссылка на сообщение
Поделиться на других сайтах

Если вас не затруднит , для более предметного общения сделайте фото внутренностей девайса , какие чипы в наборе ? 

Ссылка на сообщение
Поделиться на других сайтах

Решение простое.

Перепрошейтесь.

Вам нужен с вероятностью 99% 1.2.5р2.

Уже были такие грабли на р3 с другими ону ;)

Ссылка на сообщение
Поделиться на других сайтах

Создайте аккаунт или войдите в него для комментирования

Вы должны быть пользователем, чтобы оставить комментарий

Создать аккаунт

Зарегистрируйтесь для получения аккаунта. Это просто!

Зарегистрировать аккаунт

Вхід

Уже зарегистрированы? Войдите здесь.

Войти сейчас
  • Зараз на сторінці   0 користувачів

    Немає користувачів, що переглядають цю сторінку.

  • Схожий контент

    • Від AlinaQuan
      Запрошений продукт, GPON WIFI 6 AX3000 ONU, є високоякісним обладнанням, призначеним для надання швидкісного та надійного доступу до Інтернету через оптичну мережу. Дозволяє забезпечити стабільне підключення та передачу даних у високій швидкості.
      Основні характеристики:
      1. **1 * інтерфейс GPON**: Підтримує стандартний інтерфейс SC/UPC/APC, відповідає стандартам GPON.
      2. **4 * інтерфейси Ethernet**: Підтримує інтерфейси 10 MBPS / 100 MBPS, 1000 MBPS, RJ - 45, відповідає стандарту IEEE802.3-2005.
      3. **1 * інтерфейс USB**: Стандартний інтерфейс USB 3.0 для зручного підключення різноманітних пристроїв.
      4. **Двосмуговий WIFI6 AX3000 (2 ×2 MIMO (2.4G&5G))**: Забезпечує швидкість передачі даних до 3000 Мбіт/с, що дозволяє користувачам насолоджуватися швидким та стабільним бездротовим зв'язком.
       
      Цей продукт ідеально підходить для використання в домашніх, офісних та комерційних мережах. Завдяки своїм передовим технологіям та високій продуктивності, він забезпечить надійне та швидке підключення до Інтернету для вашого пристрою.
    • Від ikoko
      Продам olt bdcom 3310b з 2 блоками живлення б.у.
      2 порта epon не працює і 1 порт езернет порт також не працює - 4 000 грн. за олт.
    • Від AlinaQuan
      🚀 Introducing Our High-Performance OLT Solutions for Next-Gen Networks! 🚀
       
      Are you ready to elevate your network infrastructure to unparalleled levels of efficiency and speed? Look no further! Our cutting-edge GPON and EPON OLT solutions are here to revolutionize your network operations.
       
      🔹 GPON OLT: With options ranging from 4 to 16 ports, our GPON OLT delivers lightning-fast connectivity and unparalleled reliability. Whether you're managing a small-scale deployment or a large enterprise network, our GPON OLTs offer the scalability and performance you need to stay ahead of the curve.
      30000UAH/pcs
       
      🔹 EPON OLT: Experience the power of simplicity with our EPON OLT solutions. Available in 4 and 8 port configurations, our EPON OLTs provide seamless integration and hassle-free management for your network infrastructure. Say goodbye to complexity and hello to streamlined operations!
      20000UAH/pcs
       
      Why Choose Our OLT Solutions?
      ✅ Scalability: Scale your network effortlessly with our versatile OLT solutions, accommodating growing demands without compromising performance. ✅ Reliability: Built to withstand even the most demanding network environments, our OLTs ensure uninterrupted connectivity and minimal downtime. ✅ Ease of Management: Simplify your network operations with intuitive management interfaces and robust monitoring capabilities. ✅ Future-Proof: Stay ahead of technological advancements with our forward-thinking OLT solutions, designed to support future network requirements.
       
      Don't miss out on this opportunity to supercharge your network infrastructure! Contact us today to learn more about our GPON and EPON OLT solutions and take your network to the next level.
    • Від AlinaQuan
      Hi, it's so great to meet you here. We are a Chinese factory that located in Shenzhen, China. Most of our clients are Operator and ISP.
       
      We have only 3 main product line currently, 
       
      Product Line 1: GPON/EPON/XGPON OLT, and we are the only factory that work XGSPON OLT out in similar level factory. No company has XGSPON OLT, except company like Huawei, ZTE!
       8300 to 118290UAH  FOR EPON/ GPON OLT
       
      Product Line 2: GPON/EPON/XGPON ONU WIFI 5 and WIFI 6, we are working on XGSPON ONU. And MDU, 4, 8 ports, no POE and with POE port!
      800-3000UAH/pcs (Retail Price) 4GE WIFI 6 AX3000 Dual Band GPON/EPON ONU With CATV por
       
      Product Line 3: It's our Switches, we got Enthernet Switch, All-optical Switch,Access Layer,Distribution Layer,Core Layer, we all have. 
      2500UAH/pcs  to 120000UAH FOR Ethernet, All-optical switch
      And you can also buy OLT from Ukraine local, saving your time, shipping cost !
      Anyway, welcome to contact me for more details! Whatsapp/Viber / Wechat: +8618086327779 !
      Wish you guys have a nice day!
    • Від AlinaQuan
      Привіт усім!
      Сьогодні я хочу поділитися з вами деякою інформацією про PON (Passive Optical Network), а також про переваги використання GPON (Gigabit Passive Optical Network) у проектах FTTH (Fiber to the Home).
       
      PON - це технологія передачі даних, яка використовує оптичні волокна для передачі сигналів до кінцевих користувачів без необхідності використання активного обладнання на шляху. Це дозволяє зменшити витрати на енергію та обслуговування мережі.
       
      Звіт про PON мережеву архітектуру та порівняння GPON, EPON і XGSPON у вигляді таблиці зображений нижче:
       
      Однією з найпопулярніших реалізацій PON є GPON. GPON забезпечує велику пропускну здатність і високу якість обслуговування для кінцевих користувачів. У FTTH проектах використання GPON має численні переваги, такі як зменшення витрат на інфраструктуру, покращення якості послуг та забезпечення масштабованості мережі.
      У моделі GPON мережі є два основних компонента: GPON OLT (Optical Line Terminal) та GPON ONU (Optical Network Unit). GPON OLT знаходиться на стороні провайдера і забезпечує з'єднання зі структурою оптичної мережі. GPON ONU розташовується на стороні користувача і використовується для підключення до оптичної мережі.
       
      При будівництві XGSPON мережі, хоча вона забезпечує найвищу на сьогоднішній день швидкість передачі даних, пристрої XGSPON OLT та XGSPON ONU, які використовуються в ній, мають високу вартість, що не є оптимальним вибором для домашніх мереж. Таким чином, на сьогоднішній день, GPON здається найбільш вигідним рішенням для мережі!
       
      Примітка: усе це перекладено програмним забезпеченням. Ласкаво просимо вказати на це, якщо є проблеми з граматикою чи орфографією.
       
×
×
  • Створити нове...