Showing posts with label Access. Show all posts
Showing posts with label Access. Show all posts

Sunday, May 29, 2016

Configuring Single-homed Inter-Board Link Aggregation

In inter-board link aggregation, one or more ports on two boards are added to a LAG. Inter-board link aggregation provides protection for boards configured with aggregated links. In single homing, only one upstream device is available, without differentiating between primary and slave devices.

Service Requirements

The bandwidth between the access device uplink ports and the upper-layer switch (such as
LS-S5700-24TP-PWR-SI-AC)is required to increase in load sharing mode. In addition, link protection is required. If one link becomes faulty, the upstream bandwidth is decreased, and the Internet access rate is reduced. However, the Internet access service must not be interrupted, and the access rate reduction slightly degrades user experience.
Board-level protection must be implemented in the LAG. If one board becomes faulty, services are not interrupted.

Networking

Two GIU boards on the access device are used for upstream transmission, and the access device is interconnected with another device. One LAG is configured on the two GIU boards of the access device, and the other LAG is configured on two boards of the interconnected device.

Prerequisite

  • Interconnected devices, hardware, and ports support LAGs.
  • The two aggregated ports do not have a static MAC address. To check whether an aggregated port has a static MAC address, run the display mac-address command.

Data Plan

Table 1 lists data plan for configuring single-homed inter-board link aggregation.
Table 1 Data plan for configuring single-homed inter-board link aggregation
Item Data Remarks
LAG member port
  • 0/19/0 (master port)
  • 0/20/0
  • The configuration of the slave port must be the same as that of the master device. Alternatively, the slave port is not configured.
  • It is recommended that you do not configure the slave port to prevent a service failure due to data inconsistency with the master port.
Aggregation type LACP aggregation When the access device connects to a device supporting LACP, the LACP aggregation mode is recommended. When the access device connects to a device not supporting LACP, only manual aggregation can be configured.
Load sharing type Load sharing A LAG works in load sharing mode by default.

Procedure

  1. (Mandatory) Create a LAG and select an aggregation type. Run the link-aggregation command to add multiple uplink Ethernet ports to the same LAG to protect ports and share load between the ports. The port with the smallest port ID is the master port.
  2. (Optional) Add a LAG member port. Perform this step when the LAG bandwidth or link reliability is required to improve. To do so, run the link-aggregation add-member command to add an Ethernet port to a LAG.
    NOTE:
    When adding a port to or deleting a port from a LAG, if this port has connected to the peer device, run the shutdown(Ethernet) command to deactivate this port or disconnect the optical fiber from this port to prevent a link loop.

  3. (Optional) Select a load bearing type. This step is required only when the LAG works in LACP aggregation mode.
    Configuring the maximum active links in a LAG implements traffic allocation in load non-sharing mode. For example, M+N links have been configured in a LAG. Then, run the link-aggregation max-link-number command to specify N active links. The remaining M links are standby ones. If an active link is interrupted, a standby link automatically changes to the active one.

  4. (Optional) Set the system priority and port priority. This step is required only when the LAG works in LACP aggregation mode.
    • LACP system priority: Run the lacp priority system command to set the LACP system priority of the access device.
    • LACP port priority: LACP port priority must be used with the maximum number of links. If a port is required preferentially for carrying services, set its priority higher. Run the lacp priority port command to change the link priority so that the standby link and the active link can be switched over.

  5. (Optional) Select a link revertive mode. This step is required only when the LAG works in LACP aggregation mode. Run the lacp preempt command to set whether traffic is switched back to the original link when the original link recovers.
  6. (Optional) Query LAG information. Run the display link-aggregation command to query the LAG information, including the master port, number of links, aggregation type (manual or LACP aggregation), and maximum number of links.

Result

The bandwidth between the access device uplink ports and the upper-layer switch is increased in load sharing mode. In addition, link protection is implemented. If one board in the LAG becomes faulty, services are not interrupted.

Example

The following configurations are used as an example to configure single-homed inter-board link aggregation:
  • The access device transmits data upstream using two GIU boards.
  • Uplink ports 0/19/0 and 0/20/0 on the active and standby GIU boards, respectively, are added to an inter-board LAG.
  • Packets are forwarded to these ports based on source and destination MAC addresses.
  • The LAG works in LACP aggregation mode.
huawei(config)#link-aggregation 0/19 0 0/20 0 egress-ingress workmode lacp-static
huawei(config)#display link-aggregation all
  -------------------------------------------------------------------------
  Master port  Link aggregation mode  Port NUM  Work mode  Max link number 
  -------------------------------------------------------------------------
  0/19/0       egress-ingress                4  lacp-static              -
  -------------------------------------------------------------------------
  Total: 1 link aggregation(s)

Configuration File

link-aggregation 0/19 0 0/20 0 egress-ingress workmode lacp-static



More related:

How to do when Abnormal Optical Power Reporting Caused by the Coupling Exception

Thursday, May 19, 2016

How Do I Restore the Default VLAN Configuration of an Interface?


The default VLAN configuration of an interface involves the default VLAN of the interface and the VLAN that the interface joins. By default, the default VLAN configuration of an interface is as follows:
  • Access: The default VLAN is VLAN 1, and an access interface joins VLAN 1 in untagged mode.
  • Trunk: The default VLAN is VLAN 1, and a trunk interface joins VLAN 1 to VLAN 4094 in tagged mode. That is, a trunk interface allows all VLANs.
  • Hybrid: The default VLAN is VLAN 1, and a hybrid interface joins VLAN 1 in untagged mode.
  • Dot1q-tunnel: The default VLAN is VLAN 1, and an dot1q-tunnel interface joins VLAN .1
  • Negotiation-auto or Negotiation-desirable: If the interface is negotiated as an access interface, the default VLAN configuration of the interface is the same as that of the access interface. If the interface is negotiated as a trunk interface, the default VLAN is VLAN 1 and the interface joins VLANs 1 to 4094 in tagged mode. That is, the interface allows all VLANs.
Run the display this include-default | include link-type command in the interface view to check the link type of the interface, and then perform one of the following configurations to restore the default configuration of the interface.
  • Restore the default VLAN configuration of an access or dot1q-tunnel interface.
    <HUAWEI> system-view
    [HUAWEI] interface gigabitethernet 0/0/1
    [HUAWEI-GigabitEthernet0/0/1] undo port default vlan
  • Restore the default VLAN configuration of a trunk interface.
    <HUAWEI> system-view
    [HUAWEI] interface gigabitethernet 0/0/1
    [HUAWEI-GigabitEthernet0/0/1] undo port trunk pvid vlan
    [HUAWEI-GigabitEthernet0/0/1] undo port trunk allow-pass vlan all
    [HUAWEI-GigabitEthernet0/0/1] port trunk allow-pass vlan 1
  • Restore the default VLAN configuration of a hybrid interface.
    <HUAWEI> system-view
    [HUAWEI] interface gigabitethernet 0/0/1
    [HUAWEI-GigabitEthernet0/0/1] undo port hybrid pvid vlan
    [HUAWEI-GigabitEthernet0/0/1] undo port hybrid vlan all
    [HUAWEI-GigabitEthernet0/0/1] port hybrid untagged vlan 1
  • Restore the default VLAN configuration of the Negotiation-auto or Negotiation-desirable interface.
    <HUAWEI> system-view
    [HUAWEI] interface gigabitethernet 0/0/1
    [HUAWEI-GigabitEthernet0/0/1] undo port default vlan
    [HUAWEI-GigabitEthernet0/0/1] undo port trunk pvid vlan
    [HUAWEI-GigabitEthernet0/0/1] port trunk allow-pass vlan all
    
More related:


Sunday, May 8, 2016

Basic voice features


Table 1 Basic voice features
Basic Feature Description
Protocol
Voice protocols are used for communication between an access device and an upper-layer gateway control device. The access device supports H.248, Media Gateway Control Protocol (MGCP), and Session Initiation Protocol (SIP). You can run the display protocol support command to query the protocol used on the device. If the protocol used on the device is different from the planned protocol, run the protocol support command to switch the protocol.
SIP
H.248
MGCP
Access Mode
A voice access mode is based on terminal type and service requirements. The access device supports POTS, ISDN, and R2 access modes. Voice communication also supports fax and modem services.
  • A POTS network is a connection-oriented circuit switched network based on timeslot switching. Each circuit connection uses a timeslot in a pulse code modulation (PCM) group. That is, the circuit switched rate is 64 kbit/s.
  • The ISDN access can be basic rate access (BRA) or primary rate access (PRA). The BRA access provides 2 B channels and 1 D channel. The rates of B and D channels are 64 kbit/s and 16 kbit/s, respectively. The PRA access provides 30 B channels and 1 D channel. The rates of B and D channels are both 64 kbit/s.
  • In R2 access mode, the access device connects to a private branch exchange (PBX), which communicates with the access device through R2 signaling.
ISDN
POTS
R2
FoIP
MoIP
Key Techniques for Improving Voice Service Quality
The VoIP technology provides a series of technologies, such as codec, echo cancellation (EC), and voice activity detector (VAD) to improve the voice quality.
Key Techniques for Improving Voice Service Quality


Table 2 Voice service features
Service Type Description
VoIP
The VoIP service uses the IP packet switched network for transmission after the traditional analog voice signals are compressed and packetized, to lower the cost of the voice service.
MoIP
The modem over Internet Protocol (MoIP) refers to the modem service provided on the IP network or between the IP network and the traditional PSTN network.
FoIP
The fax over Internet Protocol (FoIP) refers to the fax service provided on the IP network or between the IP network and the traditional PSTN network.
Line hunting
Line hunting is a feature that allows a group of ports to share a group of called party numbers by specifying a hunting group and hunting policy. Only the SIP protocol supports this feature.
POTS IP SPC
To configure an IP SPC, configure the data (including the local IP address, local UDP port, remote IP address, and remote UDP port), set up an IP direct connection between the two ends of the voice service. In this manner, the voice media data can be directly transmitted to the peer end.
You can buy OSN 3500 from us.


More related:

Tuesday, March 15, 2016

How to Upgrade the LSW Chip of the H801SCUN Board

H801SCUN is a control board for the MA5600T and uses the BCM56820 LAN switch chip. After the hardware of the BCM56820 LAN switch chip is upgraded (that is, the BCM56820 LAN switch chip of a new hardware version is used), the software of the H801SCUN board needs to be changed accordingly. It is learnt that from Mar. 2010, the H801SCUN board to be delivered will use the LAN switch chip of Ver.B. In this case, if the software version of the H801SCUN board is earlier than V800R006C02SPC110, the H801SCUN board will fail to start.
Sub-product lineAccess                     ProductMA5600T

Problem Description
Trigger condition: 
In terms of the H801SCUN board (the LAN switch chip used is of Ver.B) to be delivered from Mar. 2010
1. If you downgrade the H801SCUN board to a version earlier than V800R006C02SPC110, the H801SCUN board will fail to start.
2. If you delete the patch of V800R006C02SPC110, the H801SCUN board fails to start.
Problem phenomena: 
When the H801SCUN board fails to start, the following information is displayed:
Transferring control to the loaded program...OK!
Starting system application init......successfully! 
Starting system configuration data init...successfully!
Drv_Lsw_Init: Drv_StackInit return error!
PHY initial step 2  error!  ---> Init LSW card error!
A Fatal Error Occured!!! System Must be reboot!!

Judge method: 
1. If you downgrade the H801SCUN board to a version earlier than V800R006C02SPC110
2. If you delete the patch of V800R006C02SPC110, the H801SCUN board fails to start

Cause Analysis
When the hardware of the BCM56820 LAN switch chip used by the H801SCUN board is upgraded from Ver.A to Ver.B, the software of the H801SCUN board is incorrect. 

Impact and Risk
The H801SCUN board fails to start.

Measures and Solutions
Recover Measures:
Upgrade the software version of the H801SCUN board to V800R006C02SPC110 or later.

Avoidance Measures:
None

Solution:
Scenario 1: The software version of the H801SCUN board is downgraded from V800R006C02SPC110 to V800R006C02SPC100, and as a result the H801SCUN board fails to start.
If the SPH110 hot patch is not deleted, during the H801SCUN board startup process, reload the V800R006C02SPC110 version during the extended BIOS booting. 
Operation: In the following stage,
The last update date of extended BIOS is : Feb 16 2009, 11:29:49
Extended BIOS version is 105 
Press <D> key to stop auto-boot    0              //Input d.
Load the package file of V800R006C02SPC110 through TFTP.
Scenario 2: The SPH110 hot patch of V800R006C02SPC110 is deleted, and as a result the H801SCUN board fails to start.
In such a condition, load the firm file to the H801SCUN board. The firm file is not available to technical support engineers. Therefore, contact the MA5600T-related R&D engineer Li Chao (67686) for a solution.

Disposal for Replaced Material
None

Reconstruction Scope and End time
The software version of the H801SCUN board on the current network is upgraded to V800R006C02SPC110 or V800R007C00 or their later versions.

Reconstruction Guidance]
None
Attachment
None 


More blog:

How to Upgrade the LSW Chip of the H801SCUN Board


Tuesday, March 8, 2016

How to Upgrade the LSW Chip of the H801SCUN Board

H801SCUN is a control board for the MA5600T and uses the BCM56820 LAN switch chip. After the hardware of the BCM56820 LAN switch chip is upgraded (that is, the BCM56820 LAN switch chip of a new hardware version is used), the software of the H801SCUN board needs to be changed accordingly. It is learnt that from Mar. 2010, the H801SCUN board to be delivered will use the LAN switch chip of Ver.B. In this case, if the software version of the H801SCUN board is earlier than V800R006C02SPC110, the H801SCUN board will fail to start.
Sub-product lineAccess                     ProductMA5600T

Problem Description
Trigger condition: 
In terms of the H801SCUN board (the LAN switch chip used is of Ver.B) to be delivered from Mar. 2010
1. If you downgrade the H801SCUN board to a version earlier than V800R006C02SPC110, the H801SCUN board will fail to start.
2. If you delete the patch of V800R006C02SPC110, the H801SCUN board fails to start.
Problem phenomena: 
When the H801SCUN board fails to start, the following information is displayed:
Transferring control to the loaded program...OK!
Starting system application init......successfully! 
Starting system configuration data init...successfully!
Drv_Lsw_Init: Drv_StackInit return error!
PHY initial step 2  error!  ---> Init LSW card error!
A Fatal Error Occured!!! System Must be reboot!!

Judge method: 
1. If you downgrade the H801SCUN board to a version earlier than V800R006C02SPC110
2. If you delete the patch of V800R006C02SPC110, the H801SCUN board fails to start

Cause Analysis
When the hardware of the BCM56820 LAN switch chip used by the H801SCUN board is upgraded from Ver.A to Ver.B, the software of the H801SCUN board is incorrect. 

Impact and Risk
The H801SCUN board fails to start.

Measures and Solutions
Recover Measures:
Upgrade the software version of the H801SCUN board to V800R006C02SPC110 or later.

Avoidance Measures:
None

Solution:
Scenario 1: The software version of the H801SCUN board is downgraded from V800R006C02SPC110 to V800R006C02SPC100, and as a result the H801SCUN board fails to start.
If the SPH110 hot patch is not deleted, during the H801SCUN board startup process, reload the V800R006C02SPC110 version during the extended BIOS booting. 
Operation: In the following stage,
The last update date of extended BIOS is : Feb 16 2009, 11:29:49
Extended BIOS version is 105 
Press <D> key to stop auto-boot    0              //Input d.
Load the package file of V800R006C02SPC110 through TFTP.
Scenario 2: The SPH110 hot patch of V800R006C02SPC110 is deleted, and as a result the H801SCUN board fails to start.
In such a condition, load the firm file to the H801SCUN board. The firm file is not available to technical support engineers. Therefore, contact the MA5600T-related R&D engineer Li Chao (67686) for a solution.

Disposal for Replaced Material
None

Reconstruction Scope and End time
The software version of the H801SCUN board on the current network is upgraded to V800R006C02SPC110 or V800R007C00 or their later versions.

Reconstruction Guidance]
None
Attachment
None


more bloh: