No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FAQ-Why CAR Is Invalid for the Downstream Traffic on the Large Board of the ME60 and How to Identify the Large Board and Small Board of the ME60

Publication Date:  2012-07-27 Views:  43 Downloads:  0
Issue Description

Q:

For the five levels of QoS scheduling of the large board of the ME60, the downstream rate in the scheduler-profile is implemented through GTS. The configured CAR is invalid. Why CAR is invalid for the downstream traffic on the large board of the ME60 and how to identify the large board and small board of the ME60?

 

      
Alarm Information

Null

      
Handling Process

A:

For the five levels of QoS scheduling of the ME60, the commands in the scheduler-profile can be used to implement CAR for the upstream and downstream traffic. The commands are as follows:
[ME60]scheduler-profile 1
[ME60-scheduler-1]car cir 1024 ?
  cbs         Committed burst size
  downstream  Downstream
  pir         Peak information rate
  upstream    Upstream
[ME60.96-scheduler-1]car cir 1024 upstream
[ME60.96-scheduler-1]car cir 1024 downstream      
For the ME60 of all present versions (all V1R2, V1R5, and V1R6 released before March 1st, 2008), CAR for the downstream traffic is invalid. You must use GTS to implement CAR. The commands are as follows:
[Test_ME60.96-scheduler-1]gts cir 1024 ?
  pir           Peak information rate
  queue-length  Queue length
  <cr>          
Note: Only CAR for the downstream traffic of the large board is invalid. The configuration of the small board is normal. GTS supports CAR for the downstream traffic. The configuration of CAR for the upstream traffic is normal and valid.
cir: Set the CIR. The traffic whose average rate is greater than the CIR is shaped. The CIR ranges from 70 to 100000 kbit/s.
pir: set the PIR. The traffic whose average rate is greater than the CIR is shaped. The PIR ranges from 70 to 100000 kbit/s. If the CIR is set, the PIR must be greater than or equal to the CIR.
How to identify the large board and small board?
Use the display version command, and you can view information about the PCB:

 LPU version information:
PCB version: ME01LPUA REV B    //If the version starts from ME, it is a new large board.

PCB version: CR52LPUA REV C  //If the version starts from CR, it is an old large board. Identify the large board and small board through the following information:
  ……
Host processor:
  1. SDRAM Memory Size: 512M  bytes    // The memory of the small board is 512 M, but the memory of the large board is 1 G.
  2. Flash Memory Size: 32M   bytes
  Network processor:
  1. RDRAM Memory Size: 96M   bytes   // The RDAM of the small board is 96 M, but the RDAM of the large board is 192 M.
……
PIC0's version information:
1. PCB version: CR52EAGF REV A     //Small board, CAR is supported. If it is the large board, information in red fonts is displayed as EAGFY. 

      
Root Cause

Null

      
Suggestions

Null

END