Maintenance commands

Last Updated : Feb 14, 2020 |
This section contains information about the Avaya Breeze® platform commands available for maintaining Device Adapter. All commands in this section require suser privileges.
System Manager also provides administration and maintenance of Device Adapter. Refer to Device Adapter administration in System Manager for a list of the available screens.
Important:
You must not use the dasrvstart start <app_name | all> and dasrvstart stop <app_name | all> commands in the following conditions:
  • For operations related to attribute changes.
  • For operations related to database changes.
You can perform the Device Adapter start and stop operation on the System Manager web interface by navigating to Elements Avaya Breeze® Service Management Service and selecting the correct version of Device Adapter. Click Start to start an application or Stop to stop a running application.
Note:
The default user available to run commands is cust. The cust user has permissions to run maintenance and troubleshooting commands.
Command
Description
dasrvstart start <app_name | all>
Starts an individual service or all services.
dasrvstart stop <app_name | all>
Stops an individual service or all services.
Important:
  • The following is the impact on endpoint registration if the dsa, pbx, pbxserver, or tps service is stopped on a node:
    • If a load balancer is not configured within the cluster, and if the cluster is a single-node cluster, then stopping any of these services has an impact on endpoint registrations, which results in loss of connection and calls functionality.
    • If the node that has the load balancer configured is running properly, and if any of these services is stopped on any node other than the load balancer node within the cluster, then endpoint registration and re-registration are performed normally.
    • If the cluster is a multi-node cluster, and if any of these services is stopped on the active load balancer node within the cluster, then endpoint registration and re-registration is impacted regardless of the state of other nodes and services within the cluster.
  • Stopping the csv service has an impact on the endpoint registration.
Avaya recommends that you stop and start these services during the maintenance period to minimize endpoint registration and call handling problems.
dasrvstart status <app_name | all>
Lists the status of an individual service or all services.
dsaShow
Displays statistical information per SDK instance. The dsaShow command does not require any parameters.
Example:
dsaShow
endpointShow <TN | Extension>
Displays information about the specified endpoint, such as handle, time zone, and Call Forward All Calls destination number configured for the endpoint.
Example:
endpointShow 112-0-0-1
endpointShow 1000003
endpointUnlockSCPW <TN | Extension>
Sends a request to unlock the station control password for the specified TN or extension.
Example:
endpointUnlockSCPW 3460144
endpointUnlockSCPW 112-0-0-1
fwUpgrade <TN> <LanguageSet> [<Mode>]
Where:
  • TN must be in the loop-shelf-card-unit format.
  • LanguageSet can be set to one of the following:
    • global10: Global 10 Languages (English, French, German, Spanish, Swedish, Italian, Norwegian, Brazilian Portuguese, Finnish, Japanese Katakana)
    • weurope: Western Europe 10 Languages (English, French, German, Spanish, Swedish, Norwegian, Danish, Finnish, Italian, Brazilian Portuguese)
    • eeurope: Eastern Europe 10 Languages (English, French, German, Dutch, Polish, Czech, Hungarian, Russian, Latvian, Turkish)
    • namerica6: North America 6 Languages (English, French, German, Spanish, Brazilian Portuguese, Japanese Katakana)
    • wasia: Spare Group A (English, French, German, Russian, Latvian, Turkish, Ukrainian, Estonian, Lithuanian)
    • spareb: Spare Group B (Not used)
    • Hebrew: Packaged Languages (M3904: English, French, Hebrew, Spanish;
      M3902, M3903 and M3905: English, French, German, Dutch, Polish, Czech, Hungarian, Russian, Latvian, Turkish)
  • Mode (optional) can be set to one of the following:
    • normal: This is the default mode.
    • idle: Waits for a busy set to become idle before starting the download.
    • forced: Downloads the set even if it has current firmware or is busy.
Example:
fwUpgrade 112-0-0-1 global10 idle
fwUpgrade 112-0-0-2 hebrew
ipeCardDisable <loop-shelf-card>
Disables IPE card with <loop-shelf-card> TN. All units on this card are disabled and unregistered.
Example:
ipeCardDisable 240-1-2
ipeCardEnable <loop-shelf-card>
Enables IPE card with <loop-shelf-card> TN. All units on this card are enabled and try to register.
Example:
ipeCardEnable 240-1-2
ipeCardGetSerialId <loop-shelf-card>
Prints the hardware ID, revision, and serial ID of the IPE card with <loop-shelf-card> TN.
Example:
ipeCardGetSerialId 240-1-2
ipeShow <loop-shelf> or <loop-shelf-card> or <loop-shelf-card-unit>
Shows the hardware status of the IPE cards or units.
Example:
ipeShow 240-1
ipeShow 240-1-2
ipeShow 240-1-2-0
ipeUnitDisable <loop-shelf-card-unit>
Disables the IPE unit with <loop-shelf-card-unit> TN. The unit is unregistered.
Example:
ipeUnitDisable 240-1-2-0
ipeUnitEnable <loop-shelf-card-unit>
Enables IPE unit with <loop-shelf-card-unit> TN. Tries to register the unit.
Example:
ipeUnitEnable 240-1-2-0
ipeUnitGetSerialId <loop-shelf-card-unit>
Prints the serial ID of the IPE unit with <loop-shelf-card-unit> TN.
Example:
ipeUnitGetSerialId 240-1-2-0
mgcFailback <loop-shelf>
Forces an MGC with the given loop and shelf to re-register on its primary cluster.
Example:
mgcFailback 112-0
mgcReboot <loop-shelf>
Reboots an MGC with the given loop and shelf.
Example:
mgcReboot 112-0
mgcShow
Displays a list and type of media gateway controllers registered on the Avaya Breeze® platform server. The mgcShow command does not require any parameters.
Example:
mgcShow
mgcUpgrade <loop-shelf> <current/legacy> <type>
Forces MGC upgrade to current or legacy loadware.
Where:
  • loop-shelf: Is the loop and shelf of the MGC that you want to upgrade.
  • current/legacy: Are optional parameters. The default is current.
    • current: The MGC loadware is upgraded on the MGC load that is injected in the current Device Adapter Snap-In load.
    • legacy: The MGC loadware is upgraded on legacy CS 1000 R7.6 loadware.
  • type: Can be one of the following: csp, msp, boot, fpga, app, db1, db2. type is an optional parameter. If you do not specify the type, all loadware is upgraded.
Example:
mgcUpgrade 4-0 legacy
mgcUpgrade 4-0 current csp
resetMPMode <digital/analog phone TN>
Resets the media preservation mode for the given phone along with its linked VGW channel.
Example:
resetMPMode 4-0-5-12
vgwShow <without parameters> or <loop-shelf> or <loop-shelf-card> or <loop-shelf-card-unit>
Shows the status of the registered VGW channels. The vgwShow command along with the <loop-shelf-card-unit> option shows detailed information of one particular channel.
Example:
vgwShow
vgwShow 240-1
vgwShow 240-1-11
vgwShow 240-1-11-5
tnInfo
Displays a list of TNs of the Device Adapter endpoints that are configured in System Manager.
See Avaya Communication Server 1000 Software Input Output Reference — Maintenance (NN43001-711) for a list of maintenance commands. Not all commands listed in this document are supported by Device Adapter.
Related links
Viewing the list of Device Adapter maintenance and troubleshooting commands