Home - Labnario

indoor and outdoor Huawei ATN905

7 Feb, 2014 2

As you know I try to avoid products descriptions here, on this blog. But last time I had possibility to see ATN905 boxes, available in the indoor and outdoor types. You can install them in various environment. The application scenarios of ATN905 are divided into the small-cell base station bearer scenario and the Ethernet demarcation device (EDD) scenario.

Let’s look at the pictures of the two types of this router:

Outdoor ATN905 can be wall and pole mounted. Indoor ATN905 can be installed in outside premises, street cabinets, indoor cabinets or just on a desk.

And the next interesting box:

The APM30H is an outdoor cabinet with heat exchangers. It supports AC power supply and DC power distribution, and can provide a 7 U installation space for user devices.

I allowed myself to place pictures from Huawei ATN905 documentation in this post.

from Huawei CLI – check …

4 Feb, 2014 0

Very useful command, especially when you are preparing and executing upgrade of a software of Huawei carrier class devices, like NE40E and CX600. Let’s look what can be checked by this command:

<labnario>check ?
  hardware-compatibility  hardware compatibility
  startup                 Check the version of the resource file
  system-software         system-software
  version                 check version

I personally use “check hardware-compatibility” before all planned upgrades. During a preparation phase of an upgrade, you have to read software release notes, to be sure that all software and hardware components will be compatible with the new software. You can check hardware compatibility by the command, instead of searching software documents.

Imagine that you’ve just uploaded a new software to CFcard of a router. The new software is v600r006c00spc300.

<labnario>check hardware-compatibility v600r006c00spc300.cc
Slot#    BoardType        Result           Detail
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
3        CR57LAXFB00      Compatible       NA
4        CR57LAXFB00      Compatible       NA
5        CR57EMGFB20      Compatible       NA
6        CR57EMGFB20      Compatible       NA
9        CR57SRU200A5     Compatible       NA
10       CR57SRU200A5     Compatible       NA
11       CR57SFU200C0     Compatible       NA
12       FRA200A          Compatible       NA
13       FRA200A          Compatible       NA

It’s very simple, isn’t it?

A second useful command before upgrade:

<labnario>check startup next
Main board:
Check startup software.......ok
Check configuration file.....ok
Check PAF....................ok
Check License................ok
Check Patch..................ok
PAF is fitted with startup software
License is fitted with startup software
Patch is fitted with startup software
Slave board:
Check startup software.......ok
Check configuration file.....ok
Check PAF....................ok
Check License................ok
Check Patch..................ok
PAF is fitted with startup software
License is fitted with startup software
Patch is fitted with startup software
Startup software in slave board is fitted with main board.

By this command we can check whether the next startup software is set properly.

Let’s look at the remaining options:

<labnario>check system-software v600r006c00spc300.cc
Info: Prepare to check system software cfcard:/v600r006c00spc300.cc, please wait..........
Info: System software CRC check OK!

<labnario>check version cfcard:/v600r006c00spc300.cc
Info: Software version match Ok!

I think these options don’t need any explanation.

You have to remember that this command is available from “user-view“.

new options in display elabel command

30 Jan, 2014 0

Some time ago I described how to display electronic labels. As you probably could see, the displayed information looked illegibly, especially for budding engineers.

Starting from V6R6 software of carrier class devices (like Huawei NE40E, CX600), it looks much better. You have all the information at a glance:

<labnario>display elabel brief
Slot     BoardType    BarCode                 Description
================================================================================
LPU 1    CR52LPUF40A  030KWD10AB000351        LPUF-40-A
  PIC 0  CR52L2XXN0   03675210A9000134        P40-2x10GBase LAN/WAN-XFP
  PIC 1  CR52L2XXN0   03675210A9000115        P40-2x10GBase LAN/WAN-XFP
LPU 2    CR52LPUF40A  030KWD10B7000867        LPUF-40-A
  PIC 0  CR52L2XXN0   03675210B7001018        P40-2x10GBase LAN/WAN-XFP
  PIC 1  CR52L2XXN0   03675210B7001188        P40-2x10GBase LAN/WAN-XFP
LPU 3    CR52LPUKD0   030KJY10A8000126        LPUF-21-A
  PIC 0  CR52L1XX0    030GSK10A9002012
  PIC 1  CR52L1XX0    030GSK10B7001228
LPU 7    CR52LPUKD0   030KJY10B1000383        LPUF-21-A
  PIC 0  CR52L1XX0    030GSK10A2001595
  PIC 1  CR52EBGF0    030GSH10B1000971
LPU 8    CR52LPUKD0   030KJY10CC001471        LPUF-21-A
  PIC 0  CR52L1XX0    030GSK10A2001005
  PIC 1  CR52EBGF0    030GSH10B1000795
MPU 9    CR57SRU40A4  030KSR10AA000258        SRUA4-40
MPU 10   CR57SRU40A4  030KSR10AA000175        SRUA4-40
SFU 11   CR57SFU40C0  030KSY10A9000472        SFUI-40-C
SFU 12
SFU 13

This is not the end. We have more options:

<labnario>display elabel ?
  <1-2,7-11>      The present slot
  backplane       The backplane
  brief           brief
  fuse-unit       Fuse Board
  optical-module  optical-module
  |               Matching output

Let’s try to display optical modules:

<labnario>display elabel optical-module brief
Port      BoardType          BarCode         VendorName        Description
===============================================================================
Eth1/0/0  HUXF-MM85300-GP    XA9V200007      GBC PHOTONICS     9900Mb/s-850nm-L
                                                               C-300m(EBW 50/12
                                                               5um)-100m(50/125
                                                               um)-33m(62.5/125
                                                               um)

Eth1/0/1  FTLX1412M3BCL      UL109YQ         FINISAR CORP.     9900Mb/s-1310nm-
                                                               LC-10km(0.009mm)

Eth1/1/0  TRF5013FN-GA420    T10J17302       Opnext Inc.       10000Mb/s-1310nm
                                                               -LC-10km(0.009mm
                                                               )

Eth1/1/1  FTLX1412M3BCL      UHB00LR         FINISAR CORP.     9900Mb/s-1310nm-
                                                               LC-10km(0.009mm)

Eth2/0/0  XF-MM85300-GP      XA9V200003      GBC               9900Mb/s-850nm-L
                                                               C-300m(EBW 50/12
                                                               5um)-100m(50/125
                                                               um)-33m(62.5/125
                                                               um)
.
.
.

I think it’s a good solution yet simple, don’t you?

Huawei eNSP – news

24 Jan, 2014 0

We have been waiting and finally we have a simulator of Huawei firewall USG5500. They also added WDS function of WLAN and a new simulation device of WLAN – AC6605.

I am just downloading the newest version…

For those who are interested I am sending a link to it:

why does subinterface fail to forward packets

21 Jan, 2014 0

Let’s imagine that we have a simple topology like below:

Configure subinterfaces on both AR routers for VLAN tag termination:

[R1]interface GigabitEthernet 0/0/0.100
[R1-GigabitEthernet0/0/0.100]ip address 10.0.0.1 24
[R1-GigabitEthernet0/0/0.100]dot1q termination vid 100

[R2]int GigabitEthernet 0/0/0.100
[R2-GigabitEthernet0/0/0.100]ip address 10.0.0.2 24
[R2-GigabitEthernet0/0/0.100]dot1q termination vid 100

Try to ping IP address of neighboring router:

[R1]ping 10.0.0.2
  PING 10.0.0.2: 56  data bytes, press CTRL_C to break
    Request time out
    Request time out
    Request time out
    Request time out
    Request time out

  --- 10.0.0.2 ping statistics ---
    5 packet(s) transmitted
    0 packet(s) received
    100.00% packet loss

Let’s troubleshoot this problem by checking ARP table:

[R1]display arp all
IP ADDRESS      MAC ADDRESS     EXPIRE(M) TYPE        INTERFACE   VPN-INSTANCE 
VLAN/CEVLAN PVC                      
------------------------------------------------------------------------------
10.0.0.1        5489-98d1-3ea6            I -         GE0/0/0.100
------------------------------------------------------------------------------
Total:1         Dynamic:0       Static:0     Interface:1

Why can’t we see neighboring router in ARP table?

Because subinterfaces for VLAN tag termination discard broadcast packets after receiving the packets.

How to deal with it?

Just enable ARP broadcast on subinterfaces and check again:

[R1-GigabitEthernet0/0/0.100]arp broadcast enable

[R1]ping 10.0.0.2
  PING 10.0.0.2: 56  data bytes, press CTRL_C to break
    Reply from 10.0.0.2: bytes=56 Sequence=1 ttl=255 time=110 ms
    Reply from 10.0.0.2: bytes=56 Sequence=2 ttl=255 time=40 ms
    Reply from 10.0.0.2: bytes=56 Sequence=3 ttl=255 time=10 ms
    Reply from 10.0.0.2: bytes=56 Sequence=4 ttl=255 time=20 ms
    Reply from 10.0.0.2: bytes=56 Sequence=5 ttl=255 time=50 ms

  --- 10.0.0.2 ping statistics ---
    5 packet(s) transmitted
    5 packet(s) received
    0.00% packet loss
    round-trip min/avg/max = 10/46/110 ms

[R1]dis arp all
IP ADDRESS      MAC ADDRESS     EXPIRE(M) TYPE        INTERFACE   VPN-INSTANCE 
VLAN/CEVLAN PVC                      
------------------------------------------------------------------------------
10.0.0.1        5489-98d1-3ea6            I -         GE0/0/0.100
10.0.0.2        5489-9898-4fc2  20        DF0         GE0/0/0.100
 100/-
------------------------------------------------------------------------------
Total:2         Dynamic:1       Static:0     Interface:1

A packet can be forwarded, without ARP broadcast on the subinterface for VLAN tag termination, if the access device can send ARP packets.

If the access device cannot send ARP packets, the system discards the packet, when the arp broadcast enable command is not run on the subinterface for VLAN tag termination.

The system tags an ARP broadcast packet and forwards it through the subinterface for VLAN tag termination, when the arp broadcast enable command is run on the subinterface for VLAN tag termination.

Page 11 of 33« First...«9 101112 13 »20 30...Last »