Calix Community  
 

Integrating Accedian Devices to Service Verify

0
Started ‎03-23-2017 by
Modified ‎05-26-2017 by

Accedian Direct Configuration

In order to add a new MetroNID, configuration is required in two places:

  • MetroNID CLI or EWI
  • Service Verify GUI

MetroNID CLI or EWI Configuration

  • Verify NTP is configured and sync'd:

    show ntp
  • Grab the serial number and host name to save for the SV GUI config.  Check the NID firmware version and note it for later.

    CARYNC/APETERSO/0000: board show info

    Product name       : AMN-1000-TE-H

    MAC base address   : 00:15:AD:03:7F:10

    Unit identifier    : CARYNC/APETERSO/0000

    Firmware version   : AEN_6.4.1.2_35204

    Serial number      : G024-0953

    Assembly           : 500-016-01:5:14:0B

    Hardware options   : Hardened

     

     

  • Configure the history collection functions - this sets up data binning for stats.

    history edit local policy-state enable soamdmm-state enable
    soamslm-state enable policy-filing enable policy-period 1 soamdmm-filing enable
    soamdmm-period 1 soamslm-filing enable soamslm-period 1
  • Configure the transfer of history data. You will need the password supplied by Calix.

    history edit file include-previous enable include-disabled disable url
    sftp://echovc@<SV-IP>:1035/opt/echocsvconnector/csvresults scp-password <PASSWORD>
    period-mode new local-periods 32
  • Configure the scheduling of the data transfer.  On Accedian 6.4 and above, the node can do 5-minute periods.  Version 6.3 and below can only do 15-minute.

     
    # This works on Accedian 6.4 and above
    history edit scheduling local-hours 00H00 local-minutes 00H00 local-state enable local-period 5 local-mode periodic
    # Optional if you have many NIDs and don't want them all starting SFTP sessions at the same exact second:
    history edit scheduling local-random-offset 60
     
    # This works on Accedian 6.3 and below - transfer every 15 minutes, all day.
    history edit scheduling local-hours 00H00,01H00,02H00,03H00,04H00,05H00,06H00,07H00,08H00,09H00,10H00,11H00,12H00,13H00,14H00,15H00,16H00,17H00,18H00,19H00,20H00,21H00,22H00,23H00 local-minutes 00H00,00H15,00H30,00H45 local-state enable
    # Again optional random perturbation
    history edit scheduling local-random-offset 60

     

    Add MEG

     

    cfm add meg name US0000/LAB1 name-format icc-based ccm-interval 1000 index 1 mhf-creation defer sndr-id-perm none level 4 mepid-list 100,101 vid-list 2003 vlan-type c-vlan

     

     

    Add MEP

     

    cfm add mep active yes cci-enable yes ccm-seq-number enable csf-enable no direction down fault-propagation disable fng-alarm-time 2500 fng-reset-time 10000 index 1 lowest-alarm-pri all ma-idx 1 meg-idx 1 mep-id 100 port Network priority 0 pvid 2003
    
     

     

    Add delay-measurement (DMM)

     

    cfm add dmm enable yes index 1 interval 1000 mep-idx 1 priority 0 reference-period 1 rmep-id  tw-delay enable tw-dv enable
    
     

     

    Add loss-measurement (SLM)

     

    cfm add slm enable yes index 1 mep-idx 1 reference-period 1 rmep-id 101
    

     

     

    Verification and Troubleshooting

    To verify connectivity, try to ping and TCP connect to the Service Verify server. You will likely need to find the IP by doing dig or ping on another machine first.

     

    ping 199.71.143.999
    tcp-connect host 199.71.143.999 port 1035
    Verify the transfer configuration:

     

     

    history show file
    history show scheduling
    history show local
    Show MEG/MEP statistics:

     

     

    cfm show meg configuration
    cfm show meg statistics
    cfm show mep configuration
    cfm show mep statistics
    cfm show dmm results

     

     

    Service Verify GUI Configuration

    • To add a new Accedian node in Service Verify:
      • Add Node.  This requires the Accedian node's serial number ("Node ID")
      • Add MEG.  No MEP Profile is required, just the MEP IDs on each end.
      • Add Policy, SLA-Meter Y.1731.
        • Priority value must match what is configured on the Accedian node as CCM/LTM priority, SLM priority and DMM priority.
        • Loss Measurement Mode for NID = SLM  (CCM is a proprietary method only Accedian supports, and it does not support Near-end vs Far-end)
Contributors