6 - SDM

SmartStream Device Manager
(SDM)
Motorola General Business Information, SDM, Rev 2.6

MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office.
All other product or service names are the property of their respective owners. Motorola, Inc. 2005
Page 0
Agenda
Module 1: Functional Overview

Module 2: Initial Configuration
Module 3: Device Management
Module 4: Fault Management
Module 5: System Administration/Maintenance

Page 1
Course Objectives
After completing this section of the course, you will be

able to complete the following tasks:
List the overall functions and devices supported by the

SDM
Perform the initial SDM configuration steps
Manage devices using the SDM
Manage device faults using the SDM
Perform administrative tasks using the SDM

Page 2
Module 1 SDM Overview

Page 3
Overview
The Motorola SmartStream Device Manager (SDM):
Enables you to manage Motorola digital video network elements
Provides a single configuration point for digital video headend
products, simplified fault detection, smart alarm management, and an
interface to integrated network management systems.
Provides both management of configuration and monitoring in one
easy-to-use solution.
SDM server software:

Is a client-server, multi-user environment
Is installed on a server (computer) dedicated to element management
Can automatically discover devices and add them to its database
Communicates using Simple Network Management Protocol (SNMP)

Page 4
Functions
Major functions:
Configuration management
Fault management
Performance management
Feature entitlements

Page 5
Configuration Management
Configuration management provides:
Bootstrap Protocol (BOOTP) server capabilities

Basic IP provisioning
Code download
A graphical user interface (GUI) for viewing and editing
device configuration parameters remotely
Synchronization of device configuration information

Page 6
Fault Management
Fault management allows you to:
Monitor the operating status of headend devices and detect

malfunctions
Conduct status polling
View/manage events and alarms
Forward or filter traps

Event an action or occurrence detected by a program

Ex: configuration change
Alarm result of an event which has a perceived severity
Ex: loss of input signal
Page 7
Performance Management
Performance Management allows you to:
Poll statistical parameters from headend devices

Example: SEM Output Bandwidth Utilization
Process threshold alarms
Examples: OM1000 input/output utilization and DAC 6000 queuing
Generate reports
Example: Status Poll Summary Report

Page 8
Feature Entitlements
Feature Entitlements allow you to:
Authorize available licensed features applicable to the

device
Ex: SEM Common Tier Encryption, NC 1500 increased set top box
support
License must be procured from Motorola (program
manager)

Page 9
Devices Supported
Full support including: Limited support including:
Discovery Discovery
Configuration
Status Polling
BOOTP
Full monitoring capability Devices
Devices DAC 6000
IRT 1000/2000 RADD 6000
MPS CS 1000
SEM
SE
NE
ECMG SEP
NC 1500 TMX
OM 1000/2000 UCS
RPD 1000/2000 NCS
ARPD
DEM
SVOM
SVM
ERM

Page 10
Chassis Front and Rear Views

1 Mouse connector (green)

2 Power cord connector
3 Video connector (blue)
4 USB connectors (black)
5 NIC 2 connector
6 NIC 1 connector
7 Keyboard connector (purple)
Page 11
SDM GUI Screen Components

The SDM Main Screen displays the Menu bar, View List, Active Window, Alarm Summary, and Status
area.
Menu bar - provides access to drop down menus containing SDM commands.
View List - shows a tree list of available views including Networks, Groups, Inventory, and Fault
Management (Events and Alarms).
Active Window - displays items that have been selected in the View List. The Active Window
background can be modified.
Alarm Summary - displays an overview of the active alarms and allows you to display the alarms of a
selected severity and category in the Active Window. You can click on any cell in the Alarm Summary to
obtain additional alarm detail.
Status area - displays status and broadcast messages.
A colored bar displayed above each icon indicates the items overall alarm status.
Each devices name is used as a label. However, if no name was configured in the host file prior to
discovering the device, the IP address is used as the label.
Page 12
SDM GUI Navigation Elements
The view list provides access to the various main window

views available in the SDM.

Networks: Devices can be viewed based on network connectivity. The SDM automatically discovers
connected networks and devices within them.
Groups: A group is a user defined collection of devices by IP addresses, regional location, device type,
etc. Clicking on a groups name shows all of the elements inside of that group. The group Unassigned
always exists, and contains all devices that do not fit into a user defined group.
Inventory: Displays a list of all devices in the SDMs database in tabular format.
Fault Management > Network Events: A list of all events, or a subset of events associated with a
device, group, or network node
Fault Management > Alarms: A list of all alarms, or a subset of alarms associated with a device, group,
or network node.
Page 13
SDM Help - Topics
Help > Help Topics

The SDM Help screens are opened in a separate web browser and can remain open even when the SDM
applications have been shut down.
Page 14
Module 2 Initial Configuration

Page 15
Initial Configuration Steps
1. Start client
2. Load device firmware
3. Edit host file (optional)
4. Add groups and configure network mappings
5. Discover devices
6. Set trap receiver address

Page 16
Initial Configuration
Step 1 Start the Client (Requirements)
Client Requirements
Microsoft Internet Explorer 5.0.1 or higher
Can be downloaded from: http://www.microsoft.com/ie
Java Runtime Environment (JRE) 1.4.2 or higher

Can be downloaded from: http://java.com

Page 17
Step 1 Start the Client
To access the SDM, open a Web browser and type all three of
the following in the Address field:
http://
the SDM's IP address
a colon (:) and the port number (9090)

Be sure that:
your client computer is on the same network as the SDM
you are not using any proxy servers or firewalls that would prevent communication with the SDM
Page 18
Step 1 Start the Client
You should see the following login page on your web
browser. Click the Web Start Client button to
continue.

It is recommended that you use the Java Web Start application to remotely access the SDM.
Java Web Start lets you:
Launch the SDM client quickly
Run multiple versions of Java on the client machine
Note: When using Java Web Start the SDM must be added to the clients host file located at
C:\Windows\System32\drivers\etc\hosts when not using a DNS.
Page 19
Step 1 Start the Client (Web Start Login)
If Java is installed correctly, you will see the following login
window. Enter your username and password1 and then click
on the Connect button.

1root/public
is the default user name/password combination. The password can be changed and additional
users can be added to the system.
Page 20
1. Start client
5. Discover devices

Page 21
Step 2 Load Device Firmware
Administration>Firmware Management
Must be done before discovering or adding devices to the
SDM

1. To add firmware, click Add Firmware. The Firmware Management control screen is displayed.
2. If loading firmware from CD-ROM, change the path to D: and click Scan as necessary to browse to
the target folder location and to load the firmware. Otherwise, the list of pre-loaded firmware will be
displayed.
3. To filter the list:
Highlight a single line item in the filter panel and click Filter to display only those table rows
pertinent to that item.
Highlight All and click Filter to list all device types and firmware revisions presently defined in
the chosen directory.
4. To load a single firmware version, select the checkbox next to the desired version and click Load. A
Firmware Management screen is displayed showing the firmware and the status (complete or not
complete) of the load operation.
Page 22
Step 2 Load Device Firmware
When all firmware items have a status of ok, you can

close the Firmware Management window.

Note: This page does not automatically refresh. To view the current status click the Refresh link.
Page 23
1. Start client
5. Discover devices

Page 24
Step 3 Edit host File (optional)
Must be done when naming devices
If the hosts file is not edited, a devices name will be

equivalent to its IP address
To edit the hosts file on SDM platform

Open the file (C:\winnt\system32\drivers\etc\hosts)
Add device names and associated IP addresses
Example:
165.137.104.45 om001
165.137.104.23 sem001

If you want device names to be displayed in SDM, you must enter the device IP addresses and names in
the host file. This must be done before you discover or add devices. If the names of the devices are not
added to the host file, the devices are named by their IP addresses.
Any changes in the host file to devices that were already discovered or added by SDM require those
devices to be deleted and rediscovered.
Page 25
1. Start client
5. Discover devices

Page 26
Step 4a Add Groups
Configuration>Add Group
After naming the group, click Apply and the Network

Mapping tab will become available.
A device group is any grouping of devices that you define, by IP address range and device type. For
example, you can create a device group for separate headends, subsets of headends, or groupings of
same device types.
A group is defined only on the New Group window; however, devices are assigned to a group manually, or
through device discovery, using network mapping. When using device discovery network mapping, you
can specify a single device by IP address, or multiple devices within a specified IP range, and this range
can be further defined optionally by device type. It is not necessary to define groups before discovering
devices for the SDM; however, if discovered devices are to be associated with a specific group, it is better
to define the group first, followed by the network mapping.
For example, if you create a device group called Headend A, define it to contain devices in the IP address
range of 165.137.103.11 to 165.137.103.40, and then discover a device with an IP address of
165.137.103.20, this device will automatically be assigned to the device group Headend A.
Following discovery, devices can be moved between device groups.
Page 27
Step 4b Configure Network Mappings
You can define IP address ranges and device types that should be
associated with groups to assist with device discovery.
Click Add to define another IP address range for the selected group.
Network mapping can be performed using the following methods:

1. For new groups, use the Network Mapping tab on the New Group window (Configuration > Add Group)
2. From the Network Mapping tab on the Discovery Properties window (Configuration > Discover
Devices)
3. If you accidentally close the group definition window before configuring the network mapping or want
to modify an existing group, you can proceed by:
a. Clicking on "Groups" in the View List
b. Right clicking on the group you're configuring and choosing "Properties
c. Clicking on the "Network Mapping" tab
Page 28
1. Start client
5. Discover devices

Page 29
Step 5 Discover Devices
Configuration>Discover Devices

Discovery is the process by which the SDM automatically adds existing, pre-configured (IP provisioned)
devices to the SDM. The discovery process can be performed any time by:
1. Selecting a managed network in the Discovery Management window
2. Clicking on the Start Discovery button.
This will start the discovery process in the background. You can continue to work on the SDM while the
discovery is in progress. You can also click the Refresh button to update the status display. When the
discovery is completed, the status will be FINISHED. You can also cancel the discovery process by
clicking Stop Discovery.
When discovering a device, the SDM:

Maps the device to the SDMs managed firmware
Retrieves all device configuration information
Synchronizes the devices alarm status
Adds the device to the appropriate group (if a group has been defined that contains the devices IP
address)
It is recommended that all existing devices be added using discovery.

All discovered devices are added with BOOTP processing disabled.
Once you press the Discover button, the discovery process is kicked off in the background. If you wish to
cancel the discovery process, click Cancel Discovery. To update the Discovery Status field, press the
Refresh button.
Discovering a large range of IP addresses could take a considerable amount of time. Therefore, try to
keep the IP address range as small as possible when performing device discovery.
Page 30
1. Start client
5. Discover devices

Page 31
Step 6 Set Trap Receiver Address
Configuration>Global Parameters

For proper SDM operation, set the Trap Receiver IP address for the devices. Setting the trap receiver
address instructs the devices to send all of their SNMP traps to the SDM or other network management
device within the network.
Be sure to select the group you want to modify.
Note: If you would like the SDM manage BOOTP requests you may want to set the Process BOOTP
Request to Conditional globally.
Page 32
Lab
Complete Lab Exercise #1 Initial Configuration of the SDM

Page 33
Module 3 Device
Management

Page 34
Device Configuration

The Configuration & Status tab in any devices Properties window allows you to configure all of the
devices parameters.
Page 35
Device Configuration
When configuring devices using the SDM, fields will sometimes turn
green, yellow, blue or red.
Green: The parameter is modified in the SDM window only. To apply

the change to the SDM and device hit the Apply button.
Yellow: The parameter you chose is invalid. This change will not be
applied.
Blue: The parameter has been applied to the SDM but not the device.
A reboot of the device is typically required to apply this change to
the device.
Red: There is a discrepancy between the device's configuration and

what appears on the SDM.

If a field is red, right-click on it and the SDM will show you:

The configured parameter on the SDM
The configured parameter on the device
Click the option you want to apply to device, then click the Apply button.
Page 36
Upgrading Firmware
Step 1: Load the target firmware (Administration>Firmware Management)
Step 2: Upgrade the selected device in the SDMs database
(Configuration>Upgrade Device Firmware)

Upgrading device firmware does not actually force an update to the device. The device must have
Conditional or Unconditional BOOTP control enabled in the device Properties window (Administration
tab) and the device must be rebooted.
To upgrade device firmware already installed on the SDM:

Step 1: Load the target firmware (Configuration > Firmware Management)
Step 2: Upgrade the selected device in the SDMs database (Configuration > Upgrade Device Firmware)
a. In the Device Type drop-down list, select the Device Type
b. In the Firmware Version, select the version you want to upgrade to
c. Optionally, you can select the specific Device Group, Model, or Firmware Version you wish to
upgrade using the drop-down lists in the Device Selection Criteria panel.
d. In the Available devices table, click the specific device(s) you wish to upgrade and then click
the right arrow (->) button. The device is displayed in the Modify Firmware for Devices table.
e. Click Modify to upgrade the firmware for the selected device(s). It may take a few minutes for
the firmware files to be updated in the SDMs database.
Step 3: Verify that the BOOTP setting is set to Conditional or Unconditional for each device youre
upgrading.
Step 4: Reboot each device.
Page 37
Upgrading Firmware - BOOTP
Step 3: Verify that the BOOTP setting is set to Conditional or
Unconditional for each device youre upgrading
Step 4: Reboot each device

BOOTP:
The Process BOOTP Request section allows you to configure BOOTP parameters. The three options are:
Unconditional: The SDM will send a response back each time a BOOTP request is made.
Conditional (Recommended for devices managed by the SDM): The BOOTP request will only be
processed when a pending change requires it.
Disable: All BOOTP requests will be ignored. (This is the default when discovering or adding a
device.)
Page 38
Device Administration

Other options on the Administration screen:
Managed:
When a device is first discovered it is automatically marked as a managed device. When a device is
managed, the SDM can determine the devices current status by retrieving the alarm status from the
device.
When a device is unmanaged the alarm status is grayed out and the discovery process does not retrieve
the devices current alarm status. Additionally, status polling is disabled, traps are not processed, and
performance polling is disabled for the device.
Management Operations:
Reboot:
Reboot: Reboot a device that has already been configured with an IP address.
(To reboot a new or unconfigured device, cycle power to that device.)
Force Download: Reloads the Entire firmware image for the device during next BOOTP. (Unconditional
must be checked.)
Reapply Configuration:
All: Resend all device configuration settings via SNMP.
Not Applied: Resend configuration changes not previously applied.
Synchronize:
Configuration: Synchronize the devices current configuration with what is recorded in the SDM.
Alarm Status: Synchronize the devices current alarm status with what is recorded in the SDM.
(For this feature to work, the SDM IP needs to be set as the Trap Receiver Address.)
Network and Trap Destination Parameters

Provide additional information about the device, including where it will send its traps/errors.
Page 39
Synchronize Device Configuration
Click to compare the devices current configuration settings with the
settings stored in the SDMs database.

Page 40
Synchronize Device Configuration

A device parameter report is displayed when discrepancies exist between the SDMs database and the
devices current configuration. In order to clear the discrepancy perform one of the following.
Select one of the following from the Action drop down menu for each of the discrepant parameters:
Configured - Sends the value for the selected parameter stored within the SDM database to the
device
Device Modifies the value for the selected parameter stored in the SDMs database to match the
current device setting
If youd like to set all parameters to the value stored within the SDM database or the device, click one of
the following buttons:
All Configured Sends the values stored within the SDM database to the device
All Device Modifies the values stored in the SDMs database to match the current device
settings
Note: In order for some parameters to take effect the Process BOOTP Request must be set to Conditional
or Unconditional before the device is rebooted.
Page 41
Add a Device
Configuration > Add Device

When adding a new, unconfigured device to your headend, you can use the Add a Device option. This
option adds the device to the SDM with Motorolas default configuration parameters. The devices IP
Address and Type determine to which device group the device will be added. Do not use this option for
devices that are already configured with a valid IP address. In those cases, devices should be discovered
instead of added.
If you are not using device names via the hosts file, enter the devices IP address in the Name: field. If
you are using device names, edit the hosts file first, then enter the devices name in the Name: field. If
you are not using a gateway, enter 0.0.0.0 in the Gateway: field.
Page 42
Delete a Device

To delete a device right-click the device and select Delete from the drop-down list. A confirmation
message is displayed. When a device is deleted from the SDM it maintains the previously configured
parameters stored in its non-volatile memory.
Page 43
Copy a Device

You may want to add a new device by copying configuration parameters from a like device that has
already been configured. For example, if you are adding a SEM v8 to your headend and have previously
configured a similar SEM v8 using the SDM you can copy that SEM. If you are using device names, you
must first add the device name to the host file.
Page 44
Replace a Device
SDM can push configuration parameters to replacement

device
1. Access Device Properties window for device
2. Click Administration tab
3. Modify MAC address to match new device
4. Ensure BOOTP processing is not disabled for the device
5. Click Apply
6. Reboot device if required
7. Click Reapply Configuration (All)
Note: Contact Conditional Access operator to configure

additional device parameters when required1.

1Ifthe device being replaced is an encrypting device, the Conditional Access operator will need to
reacquire the ACP (Access Control Processor = encryption chip) addresses for the device.
Page 45
Lab
Complete Lab Exercise #2 Managing Devices Using the

SDM

Page 46
Module 4 Fault Management

Page 47
Module 4 - Objectives
Given the training material, the student will perform the

following tasks using the SDM:
Determine the status of each device
Manage events, traps and alarms

Page 48
Viewing Alarms and Events
The SDM enables you to view alarms and events:
Events are notifications of any trap received from a managed device or any
operation change or state change within the SDM. An example of an event is a
configuration change or a change in device state.
Alarms are based on events and alert the user to problems in the network or
within the SDM.
There are 6 alarm severities:
critical (red)
major (orange)
minor (yellow)
warning (blue)
unknown (gray)
clear (green)
An alarm is a direct result of an event, but every event does not cause an
alarm.

Page 49
Event/Alarm Generation
Filter traps
Traps Forward to other NMS
(User specified)
SDM
(All)
Internal events in
the SDM generated by:
Network Events window
- Discovery
Events View events list and
- Status poller
details
- Threshold events
- Custom events
(Not All) (Not All)
Filter alarms Alarms View/

Alarms Alarm Details windows
(User specified)
View and act on alarms
(Not All)
Northbound Alarms View/

Traps Alarm Details windows
View and act on alarms
Third Party NMS

There are two ways in which events are generated in the SDM:
Through SDM operations such as device discovery, threshold events, status polling, or custom events.
Through traps. A trap is an unsolicited notification sent to the SDM by the SNMP agent in the network
element. The SDM collects and displays traps. The SDM logs traps with a time and date signature so
technicians in the headend can analyze the logs for fault patterns. The SDM also forwards SNMP traps to
other network management stations (NMS).
Traps can be filtered, but doing so will affect all users of the SDM and halt the data for the filtered traps
from becoming events.
Events are stored in the SDM database and can be viewed in the Network Events window.
When there is an event that indicates a failure, alarms are generated. The correlation of events into alarms
is done using the failure object of the event objectfor all events with the same failure object there will
only be one alarm and the severity of the alarm will be the severity of the latest event with the same failure
object.
Event/Alarm storage:
- Events are stored for 7 days
- The last 10,000 events are viewable in the GUI
- The event report will show full list of saved events
- Up to 10,000 alarms are stored
- once reached, SDM begins deleting old alarms
- Cleared alarms are deleted every 24 hours
- Up to 500 alarm annotations are stored
Page 50
Events / Alarms Views
Demonstration:
Events View
Event Details
Alarms View
Alarm Details
Alarm Summary Panel
Alarm actions (suppressing, generating an e-mail, performing a
command)
Troubleshooting using the SDM
Details can be found in the SDM Operators Manual and in the online
help.
You can also search for specific events or alarms. When viewing events or alarms, access this feature via the menu
bar: Edit>Search
Actions that can be performed on Alarms by right clicking:

Clear: Changes the severity of the alarm to Clear. This affects the alarm status and alarm count for the device and
the device group. This change is local to the SDM. The device may show a different alarm status and when the
device re-synchronizes with the SDM, if the alarm is still active on the device, it will revert to its previous severity.
Acknowledge (also called Pick in the alarm details window): Assigns you as the owner of the alarm. Acknowledging
and alarm does not affect device status.
Delete: Deletes the alarm from the database and removes it from view. This change is local to the SDM. If the
condition still exists on the device, the alarm may re-appear when the SDM re-synchronizes with the device.
The alarm summary panel on the lower left section of the main screen displays a table of alarm counts color-coded by
severity and sorted by category.
If you choose to have an alarm automatically generate an e-mail message, you must configure the
destination e-mail server. The e-mail server can be identified by IP address, host name (in host file) or its
domain name. To configure the e-mail server, select Administration>Email Server from the menu, enter
the e-mail server info, and click Apply.
Page 51
Troubleshooting Using the SDM
All managed networks, groups, and devices have an alarm

status icon in the SDM GUI. Using these alarms, you can
troubleshoot using a top-down technique:
Open a group or network that has an alarm status other
than clear
Look for sub-groups or devices that have alarm statuses
other than clear
Open a devices properties window, and view the Identity
and Fault tabs for more information on the devices error
state.

Page 52
Lab
Complete Lab Exercise #3 SDM Fault Management

Page 53
Module 5 System
Administration/Maintenance

Page 54
Backup SDM Database
File>Database Backup/Restore
Database should be backed up anytime changes are
made to device or system configuration
Should be backed up on a network drive (not on SDM)
Configuration record of each device is backed up

Important note: the database backup directory should contain only database backups and no other types
of files or folders. A bug in SDM v2.1.1 will cause stored databases to be deleted during a DB backup if
other types of files exist.
Page 55
Restore SDM Database
1. Exit SDM application and shut down services

a. Motorola SDM
b. Adaptive Server Anywhere
2. Locate file to be restored
3. Run the SDM restore script from command prompt
a. Choose the appropriate backup file
4. Restart the applications
a. Adaptive Server Anywhere
b. Motorola SDM

The restore function can only be performed from the SDM server.
Details can be found in the SDM Operators Manual and in the online help.
Page 56
Other Administrative Tasks
Demonstration:
reports1
user accounts
northbound interface
Details can be found in the SDM Operators Manual and in

the online help.

1When running reports, be sure to click the Generate Report button instead of just hitting <ENTER>.
Doing the latter may generate an HTML error.
Page 57
Lab
Complete Lab Exercise #4 Administer/Maintain SDM

Page 58

6 - SDM

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

6 - SDM

Загружено:

Авторское право:

Доступные форматы

SmartStream Device Manager

Motorola General Business Information, SDM, Rev 2.6

Module 1: Functional Overview

Motorola General Business Information, SDM, Rev 2.6

After completing this section of the course, you will be

List the overall functions and devices supported by the

Motorola General Business Information, SDM, Rev 2.6

Motorola General Business Information, SDM, Rev 2.6

SDM server software:

Motorola General Business Information, SDM, Rev 2.6

Motorola General Business Information, SDM, Rev 2.6

Configuration management provides:

Bootstrap Protocol (BOOTP) server capabilities

Motorola General Business Information, SDM, Rev 2.6

Monitor the operating status of headend devices and detect

Motorola General Business Information, SDM, Rev 2.6

Event an action or occurrence detected by a program

Performance Management allows you to:

Poll statistical parameters from headend devices

Motorola General Business Information, SDM, Rev 2.6

Feature Entitlements allow you to:

Authorize available licensed features applicable to the

Motorola General Business Information, SDM, Rev 2.6

Motorola General Business Information, SDM, Rev 2.6

Motorola General Business Information, SDM, Rev 2.6

1 Mouse connector (green)

Motorola General Business Information, SDM, Rev 2.6

The view list provides access to the various main window

Motorola General Business Information, SDM, Rev 2.6

Help > Help Topics

Motorola General Business Information, SDM, Rev 2.6

Motorola General Business Information, SDM, Rev 2.6

Motorola General Business Information, SDM, Rev 2.6

Java Runtime Environment (JRE) 1.4.2 or higher

Motorola General Business Information, SDM, Rev 2.6

Motorola General Business Information, SDM, Rev 2.6

Motorola General Business Information, SDM, Rev 2.6

Motorola General Business Information, SDM, Rev 2.6

Motorola General Business Information, SDM, Rev 2.6

Motorola General Business Information, SDM, Rev 2.6

When all firmware items have a status of ok, you can

Motorola General Business Information, SDM, Rev 2.6

Motorola General Business Information, SDM, Rev 2.6

Must be done when naming devices

If the hosts file is not edited, a devices name will be

To edit the hosts file on SDM platform

Motorola General Business Information, SDM, Rev 2.6

Motorola General Business Information, SDM, Rev 2.6

After naming the group, click Apply and the Network

Following discovery, devices can be moved between device groups.

Network mapping can be performed using the following methods:

Motorola General Business Information, SDM, Rev 2.6

Motorola General Business Information, SDM, Rev 2.6

When discovering a device, the SDM:

It is recommended that all existing devices be added using discovery.

Motorola General Business Information, SDM, Rev 2.6

Motorola General Business Information, SDM, Rev 2.6

Be sure to select the group you want to modify.

Complete Lab Exercise #1 Initial Configuration of the SDM

Motorola General Business Information, SDM, Rev 2.6

Motorola General Business Information, SDM, Rev 2.6

Motorola General Business Information, SDM, Rev 2.6

Green: The parameter is modified in the SDM window only. To apply

Red: There is a discrepancy between the device's configuration and