MOP

Expressway Restart PRocess

Method of
Procedure

TABLE OF CONTENTS

Table of Contents.................................................................................................................... 1

OPTANIX MOP V1.0 1

Revision History...................................................................................................................... 1

Change details........................................................................................................................ 2

Affected devices...................................................................................................................... 2

Associated devices.................................................................................................................. 2

Contacts.................................................................................................................................. 2

Supplemental information....................................................................................................... 3

Terminal Servers.................................................................................................................. 3

Vendor Documentation........................................................................................................ 3

Purpose................................................................................................................................... 3

Description........................................................................................................................... 3

Reason for change............................................................................................................... 3

Technical impact/Risk............................................................................................................. 3

Requirements.......................................................................................................................... 3

Preliminary steps.................................................................................................................... 4

Pre-change output collection................................................................................................... 4

Implementation plan............................................................................................................... 4

Implementation.................................................................................................................... 4

Verification........................................................................................................................... 4

Backout Plan........................................................................................................................... 5

Backout Implementation...................................................................................................... 5

Backout Verification............................................................................................................. 5

post-change output collection................................................................................................. 5

Final Steps.............................................................................................................................. 5

REVISION HISTORY
Revisi Tea
Date Engineer Notes
on m

OPTANIX MOP V1.0 2

CHANGE DETAILS
Information Details
Optanix Ticket #
Customer Ticket #
Vendor Ticket #
Estimated Duration of
00 hrs and 00 mins
Pre-Checks
Estimated Change
00 hrs and 0 mins
Duration

AFFECTED DEVICES

The following list contains devices that will be modified:

Device Name IP Address Device Type/Function

ASSOCIATED DEVICES

The following list contains devices that will NOT be modified but may be indirectly impacted.

Device Name IP Address Device Type/Function

CONTACTS

The following list contains all individuals involved with the change (including vendors):

Primar
Organizati y
Name Role Email Address Phone Number
on Contac
t

OPTANIX MOP V1.0 3

SUPPLEMENTAL INFORMATION

TERMINAL SERVERS

 Port Forwarding access is the best option as it allows access to all Expressway servers.
 It was found that from the Horizon client you are not able to reach the internal IP
addresses for the E servers.

VENDOR DOCUMENTATION

PURPOSE

Recover services on MRA servers that are not allowing registrations

DESCRIPTION

 The two devices listed in affected devices will be ‘restarted’ so that the software can
bring up services properly and then test with netstat from root to ensure that the problem
is resolved.
 Cisco SR was used for troubleshooting.

REASON FOR CHANGE

 Certain Expressway servers are not allowing MRA registrations

TECHNICAL IMPACT/RISK

The risk for this is high as the servers will not work properly without the appropriate
certificates to use for secure/trusted connections

REQUIREMENTS
Function Required Details (if function required)
Onsite support ☐

Vendor or TAC ☐

Hardware RMA ☐

Customer/User/App ☐
Testing
WebEx or ☒ Webex TBD
Conference Bridge

OPTANIX MOP V1.0 4

 Customer contact ☒ The customer will have a change that they
required before need to set to active in their systems.
change

PRELIMINARY STEPS
 Review all steps in the implementation plan before proceeding
 If applicable, create outage for associated device(s) to suppress alarms
 If required, join bridge
 Update case with details from the above steps taken and change case status to “Work in
progress”.
 Notify all listed in the Contact(s) section via email, please follow the format specified in
the Change Management documentation.

PRE-CHANGE OUTPUT COLLECTION

 Take the necessary backups/screenshots of the current configurations that will be
modified and any informative “show” commands. Please reference, MOP Workflow for
more details.
 Filename should utilize a similar format to the below:
[devicename]_[pre,post]-change_[date].log
Date format: yyyy.mm.dd
Example: Router001_pre-change_2014.12.3.log

Cisco Expressway-VCS - Pre-Change Output Collection:

The devices have been listed under “Affected Devices” on previous steps.
The actual commands and details are found in: https://tacconnect > Home > Homepage > Health Checks
Perform a Pre-change Health Check from each node as follows: (Gather, Review and
Document)
Gather system details; status, hostname, version, resource usage,
etc.
Gather Zone/registrations/connections status
Gather hardware details
Gather the last 100 config/event/network logs
Gather Cluster status

VIA GUI (review the following)

o Status, overview, alarms
o Hardware/Software Resource and Performance status
o Unified Communications status / Calls / Zone Status
o Licensing details
o System Events

Backups:
Perform a backup of the configurations prior to any upgrades/changes/reboots.

IMPLEMENTATION PLAN

OPTANIX MOP V1.0 5

IMPLEMENTATION

TO TAKE THE EXPRESSWAY OUT OF SERVICE.

1. Log into the expressway device.
2. Enable maintenance mode using the following sequence:
o Go to the Maintenance mode page Maintenance > Maintenance mode.
o Set Maintenance mode to On.
o Click Save and Click Ok on the confirmation dialog.
o NOTE: Since the Expressway servers are clustered this will cause the
cluster to enter maintenance mode.
3. Check the status and number of active calls by monitoring the Resource usage
page (Status > System > Resource usage).

TO RESTART A SERVER
4. Restart the expressway to allow the new certificate to take effect.
5. Go to Maintenance > Restart & select the options to perform the restart.
6. Once the expressway has returned to normal operation; repeat the above on
the remaining Expressway servers in the affected device section.

REFRESH CUCM CONNECTIVITY

1. From the GUI, navigate to Configuration > Unified Communications > Unified CM
Servers
2. Place a check mark next to and select “refresh servers”
3. Reload the webpage and confirm that the “currently found Unified CM Nodes” are
all shown as active.

If at any point during implementation there are unexpected results that may cause impact
to production:
Spot check the appliance to assist in determining the impact
Take steps noted in the Unsuccessful Implementation section under Final Steps
Call the customer listed in the Contact(s) section
Do your best to remediate the issue

VERIFICATION

OPTANIX MOP V1.0 6

 - Verify the affected devices using the following command from CLI logging
in as root.
netstat -tulpn | grep 8443
- The above command will have return that the server is listening this can
be verified against the associated devices.
- Cisco Expressway/VCS Verification:
o Navigate to Configuration > Zones > Traversal Zone
o Scroll down to the “Location” section and confirm that all peers are
reachable
o Confirm that the Status for the Zone is “Active”

o Confirm system accessibility

o Test the MRA feature;
 NOTE: A User will be required to attempt to log in via MRA in
order for testing to be done.
 Jabber registration from external/internet;
 Test features, such as Instant Messaging, Contact
Status, Phone Services, Voicemail, WebEx Meeting;
o Proceed to the Post-Change Output collection section to collect and
verify all the required components.

1. If at any point during implementation there are unexpected results that may cause
impact to production:
a. Spot check the appliance to assist in determining the impact
b. Take steps noted in the Unsuccessful Implementation section under Final Steps
c. Call the customer listed in the Contact(s) section
d. Do your best to remediate the issue

VERIFICATION

 Cisco Expressway/VCS Verification:

o Confirm system accessibility
o If applicable: Perform video calls from/to external
systems
o If applicable: Test the MRA feature;

OPTANIX MOP V1.0 7

  Jabber registration from external/internet;
 Test features, such as Instant Messaging,
Contact Status, Phone Services, Voicemail, WebEx
Meeting;
 External physical phone end-point registration
 Federation
o Proceed to the Post-Change Output collection section to
collect and verify all the required components.

1. If verification fails:
a. Do your best to remediate the issue
b. If unable to remediate, jump to the “Back-out Plan” section
2. If verification succeeds, jump to the “Post Output Collection” section

BACKOUT PLAN

BACKOUT IMPLEMENTATION

1. No backout plan as the certificates need to be updated/renewed.

BACKOUT VERIFICATION

1. NA

POST-CHANGE OUTPUT COLLECTION

Cisco Expressway-VCS - Post-Change Output Collection:
The devices have been listed under “Affected Devices” on previous steps:
 The steps needed here are the same or similar to the “Pre-change output
collection” from previous steps. Repeat all the steps from the “Pre-Change Output
Collection” and compare the outputs to confirm that they match accordingly.

 Take the necessary backups/screenshots of the current configurations and any

informative “show” commands that were run in the “Pre-change Output Collection”
section. Verify for any differences between the pre and post output.
 Filename should utilize a similar format to pre-change filenames

FINAL STEPS
 Ensure that all debugs and elevated traces are disabled unless explicitly stated
otherwise

OPTANIX MOP V1.0 8

 Please refer to the Operations documentation, Change Management, and complete all
steps to finalize the change and to communicate effectively on the change
status/completion.

OPTANIX MOP V1.0 9