Customer integrating nodeB using the recently installed N1EGS4. However, the traffic somehow cannot pass through and customer suspect the LAG setting between the working GE port and protection GE port might be causing the problem. Only after deleting the LAG the traffic can get through normally again.
1, Replace with new EGS4 board as request new MAC address required to go e-flow process which might take some time for approval.
2, Inset new EGS4 board, configure LAG and running test again, signal can through. Result at test gear show normal. Test scenario: NE A ------------ NE B (LAG create at NE B) Inloop Pump signal from test gear.
1, Collect data and send to HQ for analysis.
2, Check on EGS4 MAC address to confirm exactly the MAC address is exist. #9-8102:szhw [8102-PRDA-S16M11 ][2011-03-14 16:42:23+08:00]> :ethn-debug:5,"DRV::aptm::get-sys-MacAddr"; : SysMacAddr: 00-00-00-00-00-00
3, Results 00-00-00-00-00-00 show it confirmed EGS4 has no MAC address.
4, Refer to HQ and R&D suggest either to add MAC address or replace with new EGS4 board.
For ethernet services either FE or GE, MAC address is an important element, without MAC address services cannot run through. Thus need to check to confirm exactly the MAC address is exist.