Technology Work Centers in Cisco Prime LAN Management Solution 4.1
Chapter 5: Managing Medianet
Downloads: This chapterpdf (PDF - 473.0KB) The complete bookPDF (PDF - 2.0MB) | Feedback

Managing Medianet Endpoints Using LMS

Table Of Contents

Managing Medianet Endpoints Using LMS

What is Medianet?

Features and Benefits of Medianet in LMS

Medianet Supported Devices and Images

Getting Started with Medianet and Assessing Medianet Readiness of Your Network

Medianet Devices

Medianet Software Incapable Devices

Medianet Hardware Incapable Devices

Prerequisites for Configuring and Monitoring Medianet Endpoints

Device Groups and Port Groups for Medianet

Enabling Location Collection

Configuring Devices with Medianet Endpoints

Configure Auto Smartports

Configure Location Settings Using Templates

Configure Video Conferencing

Configure Video Transcoding

Configure RSVP

Configure PfR

Configure QoS

Configure Performance Monitoring

Configure IPSLA Video Operations

Configure Dynamic User Tracking

Configuring Location Settings Using Templates

Understanding the Medianet Dashboard

Customizing the Display of Location Attributes

Last N Faults on Devices with Medianet Endpoints

Last N Unreachable Medianet Endpoints Portlet

Last N Connected Medianet Endpoints Portlet

Config Changes on Devices with Medianet Endpoints Portlet

Medianet Endpoints Status Across Locations Portlet

Troubleshooting Medianet Portlets

Generating Medianet Reports

Using Medianet Custom Layouts

Medianet Endpoint Inventory Report

Interpreting Medianet Endpoint Inventory Report

Troubleshooting Medianet Endpoints

Managing Medianet Jobs

Viewing Job Details


Managing Medianet Endpoints Using LMS


This chapter tells you how to simplify the deployment and how to manage day-to-day configuration of the Cisco Medianet 2.2 solution using LMS.

LMS provides workflows for setting up auto configuration, and for configuring location settings to aid the provisioning and tracking of Medianet endpoints such as digital media players (DMP) and IP video surveillance cameras (IPVSC). The LMS Medianet workflows enable the network operator to prepare the network for deployment and to ensure that appropriate location attributes are configured on the endpoints for tracking and monitoring purposes. LMS helps in reducing the errors in configuring location attributes on the Medianet-supported devices at port level and the time required to set up an end-to-end video infrastructure.

This section contains:

What is Medianet?

Features and Benefits of Medianet in LMS

Medianet Supported Devices and Images

Getting Started with Medianet and Assessing Medianet Readiness of Your Network

Prerequisites for Configuring and Monitoring Medianet Endpoints

Medianet Endpoints Connected Group

Port and Module Groups for Medianet

Enabling Location Collection

Configuring Devices with Medianet Endpoints

Configuring Location Settings Using Templates

Understanding the Medianet Dashboard

Generating Medianet Reports

Troubleshooting Medianet Endpoints

Managing Medianet Jobs

What is Medianet?

Media applications, especially video-oriented media applications are exploding in today's networks. Converging media applications onto an IP network is very complex as they are bandwidth-intensive and are of different types. These media applications include

Streaming media

IP video surveillance

Telepresence

Desktop collaboration

Each video application has a unique traffic and QoS (Quality of Service) requirement.

The Cisco Medianet solution is an end-to-end architecture for a media-optimized network comprising advanced, intelligent technologies and devices in a platform that is optimized for the delivery of rich-media applications.

A medianet is

Media-aware: Detects and optimizes different media and application types to deliver the best experience.

Endpoint-aware: Detects and configures media endpoints automatically.

Network-aware: Detects and responds to changes in device, connection, and service availability

Cisco Medianet enables intelligent services in the network infrastructure for a variety of video applications. Medianet extends the boundary of networks to include the endpoints to scale, optimize, and enhance the performance of video.

Cisco Medianet aids in configuring and provisioning of video endpoints using:

Cisco Auto Smartports on switches

Location Services

Cisco AutoQoS for video endpoints

Cisco Auto Smartports

With the Auto configuration capability of Auto Smartports, when endpoints connect to an access switch, the access switch recognizes the type of endpoint and automatically configures the port for VLAN, QoS, or AutoQoS, security features, and location information on the endpoints.

To recognize and auto-configure an endpoint, the access switch must have the Auto Smartports feature enabled. For more information, see Auto Smartports Supported Devices and Images.

Access switches with Auto Smartports can recognize endpoint devices based on the Cisco Discovery Protocol (CDP), or the MAC address range of the endpoint device. Figure 5-1 shows an example of Cisco Medianet deployment with a Cisco digital media player (DMP) and a Cisco IP Video Surveillance (IPVS) camera connected to a Cisco Catalyst switch.

Figure 5-1 Example of Cisco Medianet Deployment

1

Digital Media Player (DMP)

2

IP video surveillance cameras (IPVSC)


Location Services

Location Services is a feature of the Cisco Medianet solution that provides the Catalyst switch, or a switch module with the ability to send location information to an endpoint. The total size of the location information that can be sent via CDP and Link Layer Discovery Protocol (LLDP) is limited to 256 bytes. The network administrator should keep the location information size under 256 bytes.

Features and Benefits of Medianet in LMS

Table 5-1 lists the features and benefits of Medianet in LMS.

Table 5-1 Features and Benefits of Medianet in LMS

Feature
Benefits

View Medianet dashboard

You can

Monitor the operational status of Medianet endpoints.

View the configuration changes on Medianet Endpoints connected devices.

View the faults that have occurred on devices, which have Medianet endpoints connected to them.

View details of the missing Medianet Endpoints, which are connected to Medianet devices.

Generate reports and troubleshoot the endpoints using portlets.

For more information, see Understanding the Medianet Dashboard.

Manage Auto Smartports templates

You can

Group multiple Auto Smartports events and their associated macros into ASP templates.

Deploy the templates on multiple switches.

Customize system-defined Auto Smartports templates in LMS to suit your needs.

Define new Auto Smartports template.

For more information, see Managing Auto Smartports Templates.

Auto configure Medianet endpoints

You can

Deploy the system-defined or any user-defined Medianet templates, available in LMS, on devices

Auto configure endpoints with Auto Smartports macros when they connect to a switch or switch module.

Reduce configuration costs.

Ensure that the devices are deployed correctly.

For more information, see Configuring Auto Smartports.

Deploy Location configuration

You can

Deploy location attributes on the Medianet-supported devices at port level to configure location settings of the Medianet endpoints.

Automate physical location configuration.

Customize device configuration based on its location.

For more information, see Configuring Location Settings Using Templates.

Configure Medianet devices

You can perform the following configurations on Medianet devices:

Auto Smartports

Video Conferencing

Video Transcoding

RSVP

PfR

QoS

Performance Monitoring

IPSLA Video Operations

Dynamic User Tracking

For more information, see Configuring Devices with Medianet Endpoints.

Monitor Medianet endpoints

You can

View and monitor real-time status of Medianet endpoints using Medianet portlets and the Medianet inventory report.

Confirm if the Medianet endpoints are registered with the Digital Media Manager (DMM) or Video Surveillance Manager (VSM) in your network, using the Medianet inventory report.

You can compare the data of the report with the DMPs and IPVSCs registered in the DMM or VSM in your network.

For more information, see Generating Medianet Reports.

Troubleshoot Medianet endpoints

You can

Troubleshoot problems, if any, using the troubleshooting workflows of LMS.

Mouse over the Medianet endpoints in the Dashboard or Search results, click Troubleshoot and view details of:

Access port to which the endpoint is connected.

Host information

Active Faults and Events associated with the port

Reset the access port to which the endpoint is connected.

For more information, see Troubleshooting Medianet Endpoints.


Medianet Supported Devices and Images

Table 5-2 and Table 5-3 list the devices, switch modules, and images, that support Medianet.

Table 5-4 lists the Medianet Supported DMPs and IPVSCs.


Note Support for location deployment is available for Cat 2K devices and SM ES2 Module, but Location MIB collection is not supported through Inventory.


Table 5-2 Supported Devices and Images for Medianet

Device Type
Minimum Software

Cisco Catalyst 3750, 3750-E, 3750-X, 3750-G

12.2(58)SE

Cisco Catalyst 3560, 3560-E, 3560-X, 3560-G

12.2(58)SE


Table 5-3 Medianet Supported Switch Modules of ISRs

Routers
Medianet Supported Switch Module
Switch Image
Minimum IOS Software

3900 Series ISRs

SM-D-ES3G-48-P

12.2(55)EX

15.1(4)M

SM-D-ES3-48-P

12.2(55)EX

SM-D-ES2-48

12.2(55)EX

SM-ES3G-24-P

12.2(55)EX

SM-ES3-24-P

12.2(55)EX

SM-ES2-24-P

12.2(55)EX

SM-ES2-24

12.2(55)EX

SM-ES3G-16-P

12.2(55)EX

SM-ES3-16-P

12.2(55)EX

SM-ES2-16-P

12.2(55)EX

NME-16ES-1G-P

12.2(55)EZ

2900 Series ISRs

SM-ES3G-24-P

12.2(55)EX

15.1(4)M

SM-ES3-24-P

12.2(55)EX

SM-ES2-24-P

12.2(55)EX

SM-ES2-24

12.2(55)EX

SM-ES3G-16-P

12.2(55)EX

SM-ES3-16-P

12.2(55)EX

SM-ES2-16-P

12.2(55)EX

NME-16ES-1G-P

12.2(55)EZ

3800 Series ISRs

NME-16ES-1G-P

12.2(55)EZ

15.1(4)M

NME-X-23ES-1G

12.2(55)SEC

NME-X-23ES-1G-P

12.2(55)EZ

NME-XD-24ES-1S-P

12.2(55)EZ

NME-XD-48ES-2S-P

12.2(55)EZ

2800 Series ISRs

NME-16ES-1G-P

12.2(55)EZ

15.1(4)M

NME-X-23ES-1G

12.2(55)SEC

NME-X-23ES-1G-P

12.2(55)EZ


Table 5-4 Medianet Supported DMPs and IPVSCs

Endpoint
OUI
Camera PID

CIVS-IPC-4300

00-1E-BD

CIVS-IPC-4500

00-21-IB

CIVS-IPC-2421

00-1D-E5

CIVS-IPC-2520V/
CIVS-IPC-2521V

00-21-1B

CIVS-IPC-2530V
CIVS-IPC-2531V

00-1E-BD

CIVS-IPC-2500

00-21-1B

CIVS-IPC-2500W

00-1D-E5

DMP

DMP

0023.AC

DMP

000F.44


Getting Started with Medianet and Assessing Medianet Readiness of Your Network

The Getting Started workflow guides you on provisioning Medianet for Day 1 operations.

Both, the Getting Started and the Medianet Readiness Assessment pages help you to assess the Medianet readiness of your network. A pie chart appears with the following types of devices:

Medianet Devices

Medianet Software Incapable Devices

Medianet Hardware Incapable Devices

Click on any of the pie chart slices to view the details of the devices.


Note You need Adobe flash player 9 or later to display the readiness assessment pie chart. You can install the flash player from LMS. Reload the page after installing the flash player.


Medianet Devices

Click the Medianet Devices slice of the pie chart. These devices run with Medianet-capable images.

You can select devices and enable the required Medianet sub-technology on these devices. You can view the number of Medianet endpoints connected to each device and also the supported technologies of each Medianet device.

Medianet Software Incapable Devices

Click the Medianet Software Incapable Devices slice of the pie chart. These devices does not have Medianet-capable images. You can upgrade to the Medianet-capable image version.

Medianet Hardware Incapable Devices

Click the Medianet Hardware Incapable Devices slice of the pie chart. These devices do not support the Medianet technology. You can get the latest Medianet supported hardware from Cisco.com.

See, Medianet Supported Devices and Images for more details.

Prerequisites for Configuring and Monitoring Medianet Endpoints

The prerequisites for configuring and monitoring Medianet endpoints are:

Ensure that the devices with Medianet endpoints are managed in LMS.

To configure the location attributes for Medianet endpoints, select Configuration > Tools > Template Center.

To collect location attributes from devices, you must configure SNMPv3 AuthPriv credentials on the devices, and update these credentials in the Device Management page. To update the credentials in the Device Management page, select Inventory > Device Administration > Add / Import / Manage Devices.

To enable LMS to collect location attributes from the devices, select Admin > Collection Settings > Inventory > Location Collection Settings.

To monitor Medianet endpoints in real time and not wait till the next UTMajor Acquisition cycle using LMS, you must enable dynamic tracking of Medianet endpoints. To enable dynamic tracking, select Admin > Collection Settings > User Tracking > Device Trap Configuration.

Device Groups and Port Groups for Medianet

This section explains the following new groups that have been added for Medianet in LMS:

Medianet Endpoints Connected Group

Port and Module Groups for Medianet

Medianet Endpoints Connected Group

This is a new system-defined group to group all the devices connected with Medianet Endpoints (DMP and IPVSC).

To collect location attributes from these devices, you must configure SNMPv3 AuthPriv credentials on the devices, and update these credentials in the Device Management page.

To update the credentials in the Device Management page, select Inventory > Device Administration > Add / Import / Manage Devices.

To enable LMS to collect location attributes from the devices, select Admin > Collection Settings > Inventory > Location Collection Settings.

Port and Module Groups for Medianet

Two new system-defined PMC groups have been introduced in LMS for Medianet. They are:

DMP Ports —Contains all ports connected to DMP endpoints.

IPVSC Ports—Contains all ports connected to IPVSC endpoints.

LMS also allows you to define rules to create port and module groups using location attributes (Admin > System > Group Management > Port and Module). Some of the location attributes are Location.Floor, Location.House, Location.Place, and Location.City. For more information, see Defining Rule Expression for Port or Module Groups in Admin Online Help.

Enabling Location Collection

LMS can collect the location attributes configured on access layer ports to which Medianet endpoints are connected. You must enable the collection settings for location attributes to view details of the location attributes in the Medianet endpoint inventory reports. By default, the location collection settings are disabled.

To enable LMS to collect location attributes from the devices, select Admin > Collection Settings > Inventory > Location Collection Settings.

Select Yes and click Apply to enable the collection settings for location attributes.

Select No and click Apply to disable the collection settings for location attributes.

When you disable the Location Collection Settings, the collected location attributes of the Medianet devices will not be lost. You can view the location attributes for Medianet devices in the Medianet Endpoint Inventory Report. However, you must enable Location collection to view the latest location attributes.


Note For the location collection of the Medianet devices, configure SNMPv3 AuthPriv credentials on the devices, and update these credentials in the Device Management page (Inventory > Device Administration > Add / Import / Manage Devices).


To view location attributes of Medianet endpoints:


Step 1 Run Inventory Collection (Inventory > Job Browsers > Inventory Collection).

Step 2 Ensure Inventory Collection has completed, and then run User Tracking (Admin > Collection Settings > User Tracking > Acquisition Schedule).

Step 3 Launch Medianet Endpoint Inventory Report (Reports > Technology > Medianet).



Note You can use IC_Server.log to debug the location attributes collection of the Medianet devices.


Configuring Devices with Medianet Endpoints

From the Medianet Workcenter, you can do the following on devices with Medianet endpoints:

Configure Auto Smartports

Configure Location Settings Using Templates

Configure Video Conferencing

Configure Video Transcoding

Configure RSVP

Configure PfR

Configure QoS

Configure Performance Monitoring

Configure IPSLA Video Operations

Configure Dynamic User Tracking

Configure Auto Smartports

When you select a Medianet device, click Configure, and choose Auto Smartports from the drop-down list, the Auto Smartports configuration page appears (Work Centers > Auto Smartports > Configure > Auto Smartports).

LMS provides Medianet templates that contains all the system-defined events and the system-defined macros for the Medianet endpoints. You can select a template and customize it, if required. You can select an event to trigger the macro associated with it on the ASP-capable switch. For more information, see Configuring Auto Smartports.

Configure Location Settings Using Templates

When you select a Medianet device, click Configure, and choose Location from the drop-down list, the Template Center (Configuration > Tools > Template Center) page appears with the Location templates.

Three templates are available to facilitate configuration of location attributes on the Medianet-connected devices in your network. The system-defined location templates that are available in LMS are:

DMP Location Configuration—Configures location information on access ports that are connected to the Digital Media Player. This is a port-based template.

IPVSC Location Configuration—Configures location information on access ports that are connected to the IP Video Surveillance Camera. This is a port-based template.

Location Configuration—Configures location information on access ports that are connected to any Medianet endpoint. This is a port-based template.

For more information, see Configuring Location Settings Using Templates.

Configure Video Conferencing

When you select a Medianet device, click Configure, and choose Video Conferencing from the drop-down list, the Template Center (Configuration > Tools > Template Center) page appears with the Video Conferencing templates.

You can configure different video endpoints for video conferences.

You can configure three types of video profiles:

Homogeneous conferences (video switching)

Heterogeneous conferences (video mixing)

Guaranteed audio conferences (best-effort video)

Configure Video Transcoding

When you select a Medianet device, click Configure, and choose Video Transcoding from the drop-down list, the Template Center (Configuration > Tools > Template Center) page appears with the Video Transcoding templates.

This template provides video transcoding services, where video can be converted from one format to another.

You can configure video transcoding when the bit rate, frame rate, resolution, or codec is different between two endpoints.

Configure RSVP

When you select a Medianet device, click Configure, and choose RSVP from the drop-down list, the Template Center (Configuration > Tools > Template Center) page appears with the RSVP templates.

Resource Reservation Protocol (RSVP) signals the QoS needs of an application's traffic along the devices, in the end-to-end path through the network.

You can configure:

User or application that requires an RSVP request

Bandwidth that has to be reserved

Admission policy, which the devices use, to admit the RSVP message

Configure PfR

When you select a Medianet device, click Configure, and choose PfR from the drop-down list, the Template Center (Configuration > Tools > Template Center) page appears with the PfR templates.

Performance Routing (PFR) provides best path optimization and advanced load balancing of traffic over the WAN and to the Internet for enterprise networks with multiple paths.

You can:

Configure traffic classes for performance routing

Configure performance metrics of these individual traffic classes

Control the traffic by applying suitable traffic class and link policies.

Configure QoS

When you select a Medianet device, click Configure, and choose QoS from the drop-down list, the Template Center (Configuration > Tools > Template Center) page appears with the QoS templates.

This template provides QoS macros to switch ports upon detection of a Medianet endpoint.

You can:

Select specific network traffic

Prioritize it according to its relative importance

Use QoS macros to provide preferential treatment of traffic in your network.

Configure Performance Monitoring

When you select a Medianet device, click Configure, and choose Performance Monitoring from the drop-down list, the Template Center (Configuration > Tools > Template Center) page appears with the Performance Monitoring templates.

Using these templates, you can configure a flow record and specify how the collected data is aggregated and presented.

You can configure the following for endpoints like CUVA, Movi, Tandberg, and Webex Servers:

Configure a flow record to specify the fields you want to monitor.

Configure a policy to include one or more classes

Reaction ID, jitter and threshold of lost packets

You can also configure voice data on all endpoints.

Configure IPSLA Video Operations

When you select a Medianet device that supports IPSLA, click Configure, and choose IPSLA from the drop-down list, the IPSLA Operations (Monitor > Performance Settings > IPSLA > Operations) page appears. You cannot select multiple devices and perform this configuration.

You can configure specific collectors for video operation to analyze Latency, Availability, one-way delay, one-way packet loss, one-way jitter and connectivity of networks that carry the video traffic.

Configure Dynamic User Tracking

When you select a Medianet device, click Configure, and choose Dynamic UT from the drop-down list, the Configure Trap on Devices page appears (Admin > Collection Settings > User Tracking > Device Trap Configuration) page appears.

You must configure the Cisco devices for sending SNMPv1/SNMPv2 MAC Notification Traps when a host is connected to or disconnected from that port.

Configuring Location Settings Using Templates

The Template Center (Configuration > Tools > Template Center) in LMS provides both system-defined and user-defined location templates. In LMS, three new templates are available to facilitate configuration of location attributes on the Medianet-connected devices in your network.

You can export the system-defined template, modify it, import it and save it as a user-defined location template. The system-defined location templates that are available in LMS are:

DMP Location Configuration—Configures location information on access ports that are connected to the Digital Media Player. This is a port-based template.

IPVSC Location Configuration—Configures location information on access ports that are connected to the IP Video Surveillance Camera. This is a port-based template.

Location Configuration—Configures location information on access ports that are connected to any Medianet endpoint. This is a port-based template.

To configure location attributes on access ports:


Step 1 Select Configuration > Tools > Template Center > Deploy. The Template Deployment page appears with the list of system-defined and user-defined templates.

Step 2 Select a location template.

Step 3 Click Next. Select devices from the Device Selector.

Step 4 Click Next. Select port groups from the Port Selector.

Step 5 Click Next. The Configure Location Attributes page appears.

Step 6 Click Export device level attributes to export the template information to an excel sheet.

A dialog box appears, prompting you to open or save the template file.

Step 7 Enter the applicable values in the template.


Note The location data, which includes metadata and the corresponding location attributes, can have a maximum of 256 characters.


Step 8 Click Import device level attributes to import the template and click Upload to upload it to the LMS server.

Step 9 Click Next. The Adhoc Configuration for Selected Port Groups pane appears.

You can enter more configuration commands that will be deployed on the selected devices or ports in addition to the commands in the template. The commands that you enter here will not be validated by LMS. Entering additional commands is optional.

Step 10 Click Next. The Schedule Deployment pane appears, displaying Scheduler and Job Options details.

Enter the Job Description, select the Schedule and Job options and click Finish. A notification message appears along with the Job ID. The newly created job appears in the Template Center Jobs.


To view location attributes of Medianet endpoints:


Step 1 Trigger Inventory Collection (Inventory > Job Browsers > Inventory Collection).

Step 2 Ensure Inventory Collection has completed, and then run User Tracking (Admin > Collection Settings > User Tracking > Acquisition Schedule).

Step 3 Launch Medianet Endpoint Inventory Report (Reports > Technology > Medianet).


Understanding the Medianet Dashboard

You can access the Medianet dashboard using My Menu > Default Dashboards > Medianet.

The Medianet dashboard provides a quick snapshot of the operational status of Medianet endpoints. You can also view the configuration changes for all the Medianet devices after every inventory or configuration collection, and view faults that have occurred on devices, which have Medianet endpoints connected to them.

The various Medianet portlets are:

Last N Faults on Devices with Medianet Endpoints

Last N Unreachable Medianet Endpoints Portlet

Last N Connected Medianet Endpoints Portlet

Config Changes on Devices with Medianet Endpoints Portlet

Medianet Endpoints Status Across Locations Portlet

When you mouse over some columns in the Medianet portlets like MAC address of the Medianet endpoint, you can view the location attributes in the Endhost details popup. You can customize the display of the location attributes in this popup. For more details, see Customizing the Display of Location Attributes.

For details on troubleshooting Medianet portlets, see Troubleshooting Medianet Portlets.

Customizing the Display of Location Attributes

When you move the mouse over the MAC address columns of the Medianet portlets, you can view the location attributes in the Endhost details popup. You can customize the display of the location attributes in this popup using the medianet.properties file located at:

For Windows-NMSROOT\lib\classpath

For Solaris and Soft Appliance-NMSROOT/lib/classpath

NMSROOT is the LMS install directory. For Solaris and Soft Appliance, it will be /opt/CSCOpx.

LMS also has the medianet.properties.orig file with the default layout of the location attributes. You can use this file if the medianet.properties file gets corrupted. If the medianet.properties file gets corrupted, you should take a copy of the medianet.properties.orig file and replace the corrupted medianet.properties file.

The location attributes that appear in the Endhost details popup vary according to the type of Medianet endpoint. See, Sample Default medianet.properties File.

You can add any location attribute to any address line. By default, the address of the Medianet endpoint is 5 lines. If the you want to add or remove a line, you should change the value of the property MOUSEHOVER.DMP.LOCATION.NUMBER_OF_LINES.

For example, to add the sixth line to the DMP endpoint address in the Endhost details popup, you should:

Add MOUSEHOVER.DMP.LINE6={1}, {2},

Modify the MOUSEHOVER.DMP.LOCATION.NUMBER_OF_LINES to 6.

The number within the braces refers to the location attribute listed in the properties file. In this example, it is State and County respectively. See, Sample Default medianet.properties File.

If you choose to add a line in between, you need to modify the subsequent lines.

You can also move the mouse over the end host records in the search results and view the location attributes only for Medianet endpoints.

Sample Default medianet.properties File

### Location attributes order

#

#SNo     Fields                     Description

#-----------------------------------------------------------------------------

#1       State                       National subdivision (state)

# 2        County                       Land area of local government

# 3        City                          City

# 4       City Division                City division

# 5        Neighborhood                 Neighborhood

# 6       Street Group                 Group of streets

# 7       Leading Street Direction     Leading street direction

# 8       Trailing Street Direction    Trailing street direction

# 9        Street Suffix                Street suffix

# 10      House                        House number

# 11      Street Number                Street number suffix

# 12      Landmark                     Landmark

# 13      Additional Location          Additional location information

# 14      Name                         Name of the resident

# 15      Zipcode                      Postal/Zip Code

# 16      Building                     Building name

# 17      Unit                         Unit

# 18      Floor                        Floor number

# 19      Room                         Room number

# 20      Place                        Place type

# 21      PostalCommunity Name         Postal community name

# 22      PostOffice Box               PO Box

# 23      Additional Code              Additional code information

# 24      Seat                         Seat number

# 25      Primary Road                 primary road or street name

# 26      Road Section                 Road section name

# 27      Road Branch                  Road branch name

# 28      Road SubBranch               Road sub-branch name

# 29      StreetName PreMod            Street pre modifier name

# 30      StreetName PostMod           Street post modifier name

# 31      Country Code                 Country

# Location Attributes format for DMP Mouse Hover

MOUSEHOVER.DMP.LOCATION.NUMBER_OF_LINES=5

MOUSEHOVER.DMP.LINE1={14},

MOUSEHOVER.DMP.LINE2={17}, {18}, {19},

MOUSEHOVER.DMP.LINE3={25}, {9},

MOUSEHOVER.DMP.LINE4={5},

MOUSEHOVER.DMP.LINE5={3}, {1}- {15}

# Location Attributes format for IPVSC Mouse Hover

MOUSEHOVER.IPVSC.LOCATION.NUMBER_OF_LINES=5

MOUSEHOVER.IPVSC.LINE1={14},

MOUSEHOVER.IPVSC.LINE2={17}, {18},

MOUSEHOVER.IPVSC.LINE3={25}, {9},

MOUSEHOVER.IPVSC.LINE4={5},

MOUSEHOVER.IPVSC.LINE5={3}, {1}- {15}

# Location Attributes format for End Host Troubleshooting

TS.LOCATION.NUMBER_OF_LINES=12

TS.LOCATION.LINE1={14},

TS.LOCATION.LINE2={18}, {17}, {24}, {19},

TS.LOCATION.LINE3={16}, {10},

TS.LOCATION.LINE4={11}, {7}, {29}, {30}, {8}, {9},

TS.LOCATION.LINE5={6},

TS.LOCATION.LINE6={25}, {29}, {27}, {28},

TS.LOCATION.LINE7={12},

TS.LOCATION.LINE8={20}, {13}, {5},

TS.LOCATION.LINE9={22}, {21},

TS.LOCATION.LINE10={4},

TS.LOCATION.LINE11={3}, {2}, {1}, {31},

TS.LOCATION.LINE12={15}, {23}

# Property to enable/disable location collection. Default is TRUE

# To disable, change it to FALSE

LOCATION_COLLECTION=TRUE

Last N Faults on Devices with Medianet Endpoints

In the Last N Faults on Devices with Medianet Endpoints portlet, you can view the faults that have occurred on devices, which have Medianet endpoints connected to them. By default, you can view the latest five events and a maximum of ten events by changing the value of the No. of Alerts to be displayed field in the configuration page.

Before you monitor the devices with Medianet endpoints, you must read the prerequisites, see Prerequisites for Configuring and Monitoring Medianet Endpoints.

You can click the title bar to navigate to the Fault Monitor page with Medianet device faults.

To configure Last N Faults on Devices with Medianet Endpoints portlet:


Step 1 Move the mouse over the title bar of the portlet to view the icons.

Step 2 Click the Configuration icon.

You can:

Select the minute and hour from the Refresh Every drop-down list to change the Refresh time. The items in the portlet get refreshed at the changed Refresh time.

Select the number of faults to be displayed in the portlet from the No.of Alerts to be Displayed drop-down list.

For example, if you select four faults, the details of any four faults appear in the portlet.

Step 3 Click Save to view the configured portlet with the changed settings.

Table 5-5 provides the details of Last N Faults on Devices with Medianet Endpoints portlet.

Table 5-5 Details of Last N Faults on Devices with Medianet Endpoints portlet

Field
Description

Severity

Displays the severity of the event. It can be Critical, Warning, or Informational.

Status

Lists the faults status such as

Active—Fault is active. All suspended devices remain active.

Cleared—Fault is no longer alive. When the fault is in the Cleared state for 20 minutes, it expires and is removed from the display.

User Cleared—User has cleared the fault. When the fault is in the Cleared state for 20 minutes, it expires and is removed from the display.

Acknowledged—Fault is manually acknowledged by the user from the Alerts and Activities Detail page.

Device Name

Name of the device which has the fault.

You can move the mouse over the name to view its details in the Device Details popup.

Event Name

Displays the name of the event

Component Name

Displays the component name of the device

Creation Time

Displays the time at which the fault occurred.

Owned By

Displays the user who owns the fault.



Last N Unreachable Medianet Endpoints Portlet

Before you monitor the Medianet endpoints, you must read the prerequisites, see Prerequisites for Configuring and Monitoring Medianet Endpoints.

In the Last N Unreachable Medianet Endpoints portlet, you can view details of the missing Medianet Endpoints, which are connected to Medianet devices.

The missing Medianet Endpoints include the following endpoints, after every User Tracking collection:

Endpoints connected to the interfaces of the switch that are down.

Endpoints missing on the interfaces of the switch that are up.

These endpoints were found in one cycle of User Tracking and were missing in the next cycle.

Users with the following roles can access this portlet:

Network Admin

Network Operator

System Administrator

Approver

Super Admin

Help Desk

You can click the title bar to navigate to the Medianet Endpoint Inventory Report generator page.

To configure the Last N Unreachable Medianet Endpoints portlet:


Step 1 Move the mouse over the title bar of the Last N Unreachable Medianet Endpoints portlet to view the icons.

Step 2 Click the Configuration icon.

You can

Select the minute and hour from the Refresh Every drop-down list to change the Refresh time. The items in the portlet get refreshed at the changed Refresh time.

Select the type of Medianet endpoint

Select the number of endpoints to be displayed in the portlet from the Show Last N Unreachable Medianet Endpoints drop-down list.

For example, if you select 4 endpoints, the details of any four endpoints appear in the portlet.

Step 3 Click Save to view the configured portlet with the changed settings.

Table 5-6 provides details of the Last N Unreachable Medianet Endpoints portlet.

Table 5-6 Details of Last N Unreachable Medianet Endpoints portlet

Field
Description

MAC Address

Displays the MAC address of the Medianet endpoint.

You can move the mouse over the MAC address to view the details of the endpoint in the Endhost Details popup. You can troubleshoot the endpoint and view its location details in this popup. You can also customize the display of the location attributes, see Customizing the Display of Location Attributes.

IP Address

Displays the IP address of the switch or switch module.

Note IP Address will be blank if the endpoint does not have an ARP entry in the router.

Connected Device

Displays the name of the switch or switch module.

You can move the mouse over the name to view its details in the Device Details popup.

Port

Displays the port of the switch or switch module, to which the Medianet endpoint is connected. You can move the mouse over the port to view details of the port in the Port Details page.

In the Port Details popup, you can click the Reset Port link to shutdown the port and then enable it. The reset action is logged as part of syslogs for audit purposes. You can view the changes in the Change Audit report (Reports > Change Audit), if syslogs are enabled in the device.

Last Connected

Date and time when User Tracking last found an entry for this endpoint in the switch.

The format is dd mon yyyy hh:mm:ss.



Last N Connected Medianet Endpoints Portlet

In the Last N Connected Medianet Endpoints portlet, you can view the following Medianet endpoints, during the last N specified time period:

Endpoints connected to a switch or switch module.

Endpoints that were down in the previous UT collection and up in the current collection.

Before you monitor the Medianet endpoints, you must read the prerequisites, see Prerequisites for Configuring and Monitoring Medianet Endpoints.

You can select one from the following time intervals:

Last 24 hours

Last Week

Last Month

Last Year

Only users following roles can use this portlet:

Network Admin

Network Operator

You can click the title bar to navigate to the Medianet Endpoint Inventory Report generator page.

To configure the Last N Connected Medianet Endpoints portlet:


Step 1 Move the mouse over the title bar of the Last N Connected Medianet Endpoints portlet to view the icons.

Step 2 Click the Configuration icon.

You can:

Select the minute and hour from the Refresh Every drop-down list to change the Refresh time. The items in the portlet get refreshed at the changed Refresh time.

Select the type of Medianet endpoint.

Step 3 Click Save to view the configured portlet with the changed settings.

Step 4 Select the time interval such as, Last 24 hours, Last Week.

Table 5-7 lists details of Last N Connected Medianet endpoints portlet.

Table 5-7 Details of Last N Connected Medianet Endpoints portlet

Field
Description

MAC Address

Displays the MAC address of the Medianet endpoint.

You can move the mouse over the MAC address to view the details of the endpoint in the Endhost Details popup. You can troubleshoot the endpoint and view its location details in this popup. You can also customize the display of the location attributes, see Customizing the Display of Location Attributes.

IP Address

Displays the IP address of the switch or switch module.

Note IP Address will be blank if the endpoint does not have an ARP entry in the router.

Device Name

Displays the name of the switch or switch module.

You can move the mouse over the name to view its details in the Device Details popup.

Port

Displays the port of the switch or switch module, to which the Medianet endpoint is connected. You can move the mouse over the port to view details of the port.

In the Port Details popup, click the Reset Port link to shutdown the port and then enable it. You can monitor the changes in the Change Audit report (Reports > Change Audit), if syslogs are enabled in the device.

VLAN

VLAN associated with the MAC address or port

First Connected

Date and time when User Tracking first found an entry for this endpoint in the switch.

The format is dd mon yyyy hh:mm:ss.



Config Changes on Devices with Medianet Endpoints Portlet

In the Config Changes on Devices with Medianet Endpoints portlet, you can view the changes in the configuration information for all the Medianet devices after every inventory or configuration collection. However, the VLAN config change details will not be displayed.

Before you monitor the devices with Medianet endpoints, you must read the prerequisites, see Prerequisites for Configuring and Monitoring Medianet Endpoints.

Users with the following roles can access this portlet:

Network Admin

Network Operator

Approver

Super Admin

Help Desk

Table 5-8 provides details of the Config Changes on Devices with Medianet Endpoints portlet.

Table 5-8 Details of Config Changes on Devices with Medianet Endpoints portlet

Field
Description

Connected Device

Name of the device to which the endpoint is attached.

You can mouse over the name to view details of the device in the Device Details page.

User Name

Name of the user who performed the change on the device. This is the name entered when the user logged in.

The User Name field may not always reflect the user name.

The User Name is reflected only when:

Config change was performed using LMS

Config change was performed outside LMS, and the network has username based on AAA security model where the authentication is performed by a AAA server (such as TACACS/RADIUS or local server)

Date and Time

Date and the time at which the application communicated the network change or when Change Audit saw the change record.

View Changes

Click Details to view the config diff report


To configure the Config Changes on Devices with Medianet Endpoints portlet:


Step 1 Move the mouse over the title bar of the Config Changes on Devices with Medianet Endpoints portlet to view the icons.

Step 2 Click the Configuration icon.

Step 3 Select the minute and hour from the Refresh Every drop-down list to change the Refresh time. The items in the portlet get refreshed at the changed Refresh time.

Step 4 Select the numbers of records that should appear in the portlet.

Step 5 Select the View exception period data over the last 24 hours check box to view the exception period data.

An Exception period is a time you specify when no network changes should occur. This period does not prevent you from making any changes in your network. You can define Exceptions periods in the Change Audit Settings (Admin > Network Administration > Change Audit Settings > Exception Periods).

Step 6 Click Save to view the configured portlet with the changed settings.


Medianet Endpoints Status Across Locations Portlet

In the Medianet Endpoints Status Across Locations portlet, you can view a bar chart that displays the operational status of the Medianet endpoints grouped according to a specific location attribute.

By default, the bar chart appears for the Medianet Endpoints grouped by the location attribute city.

Before you monitor the Medianet endpoints, you must read the prerequisites, see Prerequisites for Configuring and Monitoring Medianet Endpoints.

You can configure the location attribute used to group endpoints. A maximum of 15 endpoint groups with the highest number of unavailable endpoints can be displayed. You can view the status of up to fifty endpoint groups.

Users with the following roles can access this portlet:

Network Admin

Network Operator

To configure the Medianet Endpoints Status Across Locations portlet:


Step 1 Move the mouse over the title bar of the Medianet Endpoints Status Across Locations portlet to view the icons.

Step 2 Click the Configuration icon.

Step 3 Select the minute and hour from the Refresh Every drop-down list to change the Refresh time. The items in the portlet get refreshed at the changed Refresh time.

Step 4 Select the type of Medianet endpoint.

Step 5 Select the Location attribute from the list.

Step 6 Select the number of locations that you want in the chart. A maximum of five endpoint groups with the highest number of unavailable endpoints can be displayed.

Step 7 Click Save to view the configured portlet with the changed settings.


Troubleshooting Medianet Portlets

Table 5-9 provides details of log files to troubleshoot Medianet portlets.

Table 5-9 Log Files for Medianet Portlets

Portlet
Log File
Enable Debugging Option

Last N Faults on Devices with Medianet Endpoints

AAD.log

1. Select Admin > System > Debug Settings > Fault Debugging Settings.

2. Enable Alert and Activities log (AAD.log)

Last N Config Changes on Devices with Medianet Endpoints

RMEPortlets.log

1. Select Admin > System > Debug Settings > Config and Image Management Debugging settings.

2. Select Application as portlet.

3. Enable RMEportlets log.

Last N Unreachable Medianet Endpoints

campusportal.log

To enable debug for campusportal.log go to:

NMSROOT/campus/www/classpath/log4j-cm-portal.properties

ERROR should be changed to DEBUG for the following lines

log4j.category.com.cisco.nm.portalapi=ERROR

log4j.category.com.cisco.nm.portalapi.ds=ERROR

log4j.category.com.cisco.nm.portalapi.qtopo=ERROR

log4j.category.com.cisco.nm.portalapi.qtopo.ds=ERROR

log4j.category.com.cisco.nm.util.systemstatus=ERROR

log4j.category.com.cisco.nm.util.systemstatus.ds=ERROR

Last N Connected Medianet Endpoints

Medianet Endpoints Status Across Locations


.

You can use cwportal.log for troubleshooting other portlets. To enable debugging for this porlet, select Admin > System > Debug Settings > Common Services Log Configurations. Enable CiscoWorks Portal log.

Generating Medianet Reports

LMS allows you to generate a Medianet Endpoint Inventory Report. For more information, see Medianet Endpoint Inventory Report

You can customize the Medianet endpoint inventory report with different layouts using Reports > Report Designer > Medianet Custom Layouts. For more information, see Using Medianet Custom Layouts.

Using Medianet Custom Layouts

You can customize the columns displayed in the Medianet Endpoint Inventory Report using Reports > Report Designer > Medianet Custom Layouts.

You can view, create, and copy Medianet Custom Layouts. You can customize the inventory report by selecting the required location attributes and end host attributes. You cannot edit or delete the standard layouts.

The following Medianet default layouts are available after a fresh install:

Digital Media Player Standard—Standard layout for Digital Media Player (DMP) endpoints

IP Video Surveillance Camera Standard—Standard layout for IP Video Surveillance Camera (IPVSC) endpoints

Medianet Endpoints Standard—Standard layout for all Medianet endpoint types.

Medianet Endpoint Inventory Report

The Medianet Endpoint Inventory Report provides information about the Medianet endpoints such as the subnets on which LMS has detected the endpoints, any state changes, and the number of discrepancies found associated with the port. The details of the report vary according to the layout that you choose.

You can use this information to register the Medianet endpoints in Medianet management systems like Cisco Digital Media Manager (DMM) or Cisco Video Surveillance Manager (VSM).

To generate this report:


Step 1 Select Reports > Technology > Medianet

Step 2 Select the required devices using the Device Selector or Group Selector.

Step 3 Select the Endpoint type. You can choose to generate reports for:

Digital Media Player

IP Video Surveillance Camera

Step 4 Select the Layout from the list. By default, the following layouts for the report are available:

Medianet Endpoints Standard

Digital Media Player Standard

IP Video Surveillance Camera Standard

Step 5 Enter the information required to add a Filter Rule and click Add.

Step 6 Click Validate Rule to validate the filter rule you have added.

Step 7 Enter the scheduling details and the job information.

Step 8 After you enter the required information, click Submit. You can click Reset to reset all the information.

The Medianet Endpoint Inventory Report page appears. For more details, see Interpreting Medianet Endpoint Inventory Report.


The mini job browser appears at the bottom of the Medianet report generator screen; it shows only the Medianet report jobs.

Interpreting Medianet Endpoint Inventory Report

Table 5-10 displays details of the columns in the Medianet Endpoint Inventory Report. Some of the columns might vary according to the Layout you choose. This section contains Printing Medianet Endpoint Inventory Reports.

Table 5-10 Details of Medianet Endpoint Inventory Report 

Fields
Description

MAC Address

MAC address of network interface card in end-user node.

For Ethernet topology, the MAC address is displayed in the format, xx-xx-xx-xx-xx-xx.

Host Name

Name of the host

IP Address

IP address of the host

Subnet

Subnet of IP address

Status

Operational status of the port

Device Name

Name of the device

Port

User assigned port name (port label) in the device to which a host is connected

VLAN

VLAN associated with the MAC address or port

Last Seen

Date and time when User Tracking last found an entry for this user or host in a switch. Last Seen is displayed in the format dd mon yyyy hh:mm:ss.

IPv6 Address

IPv6 address of the host, if any

Prefix Length

Length of the IPv6 address prefix

Prefix

IPv6 address prefix

Device

IP address of device to which end user node is attached. Click on the value to launch the Troubleshooting page for that device.

Port Name

User assigned port name (port label)

Port State

Configured port mode

Port Duplex

Operational duplex

Port Speed

Operational speed

VTP Domain

VTP Domain with which the switch is associated.

VLAN ID

VLAN identifier associated with the MAC address or port

VLAN Type

Ethernet, FDDI, unassigned, or unknown

Parent VLAN

Parent VLAN of the host

Secondary VLAN

Secondary VLAN of the host

dot1xEnabled

Status of Dot 1x authentication on the device. Two status are:

True—When authentication is enabled on the device.

False—When authentication is disabled on the device.

Associated Routers

IP addresses of the routers associated with the host.

Discrepancies Found

Number of discrepancies found on the port. Click on the number to launch the Discrepancies report.

Best Practice Deviations Found

Number of best practice deviations found associated with the port. Click on the number to launch the Best Practice Deviations report.

Name

Name of the resident

Location Attributes

The location attributes that appear in the report depend on the layout that you choose. There are 31 attributes like, State, City, Neighborhood, and Street Number.


Printing Medianet Endpoint Inventory Reports

You can print only 10,000 records at a time.

Comma separated values are not accepted in the print range. For example, specifying the range as 10-40, 70-80 will not work. Specify the range as 10-40 to print from the 10th record to the 40th record. Repeat it for the 70-80 range.

Troubleshooting Medianet Endpoints

You can quickly locate the Medianet endpoints and get their network details by entering the MAC address or IP address of the Medianet endpoints in the LMS Search text box. You can also search the Medianet endpoints configured with various location attributes by using the pattern:
<location attribute>=<value>, example: city=Chicago. There should be no blank space between the attribute type and the delimiter in the LMS Search text box.

You can move the mouse over the end host records in the search results and troubleshoot them it by using the Troubleshoot button.

LMS runs a standard troubleshooting check to provide the following information:

Details about the port to which the end host is connected:

IfSpeed

Duplex

VLAN

Admin Status

Operational status

Discrepancies found in the port

Port level configuration

Host

IP address, host name, firmware version, OS version, and CPU utilization

Ping and trace route statistics to host from LMS

Active Faults and Events associated to the ports

You can also reset a port using the Reset Port link to shutdown the port and then enable it. The reset action is logged as part of syslogs for audit purposes. You can view the changes in the Change Audit report (Reports > Change Audit), if syslogs are enabled in the device.

Managing Medianet Jobs

You can browse the Medianet jobs that are deployed on the system. Using the Medianet Job Browser you can manage Medianet jobs; you can retry, stop, or delete jobs using this job browser.

To invoke the Medianet job browser:

Select Work Center > Medianet > Jobs.

The Medianet job browser appears with a detailed list of all Medianet jobs. The browser has the following information:

Column
Description

Job ID

Unique number assigned to job when it is created.

Click on the hyperlink to view the Job details (seeViewing Job Details).

Status

Status of the job:

Successful—When the job is successful.

Failed—When the job has failed.

The number, within brackets, next to Failed status indicates the count of the devices that had failed for that job. This count is displayed only if the status is Failed.

For example, If the status displays Failed (5), then the count of devices that had failed is 5.

Stopped—When the job has been stopped.

Running—When the job is in progress.

Description

Description of the job, entered at the time of job creation.

Owner

Username of the job creator.

Scheduled at

Date and time at which the job was scheduled.

Completed at

Date and time at which the job was completed.

Schedule Type

Type of job schedule—Immediate, Once.

Job Type

The types of Medianet job.


You can filter the jobs displayed in the Medianet Job Browser using any of the following criteria and clicking Quick Filter. You can select any of the following criteria from the respective drop-down list, enter the details in the textbox.

Filter Criteria
Description

Job ID

Select Job ID and enter the Job IDs that you want to display. For a non-periodic job, the specified Job ID appears in the browser. For periodic jobs, all the instances of the selected Job ID will also be displayed in the browser.

Status

Select Status and then enter any one of these:

Successful

Failed

Stopped

Running

Scheduled

Description

Select Description and enter the complete description.

Owner

Select Owner and enter the full name.

Scheduled at

Select Scheduled at and enter the date and time at which the job was scheduled.

Completed at

Select Completed at and enter the date and time at which the job was completed.

Schedule Type

Select Schedule Type and enter any one of the following:

Immediate

Once

Job Type

Select Job Type and enter any one of the following:

Autosmartport

Config Template

Dynamic User Tracking


You can click Refresh icon to refresh the Medianet job browser, and Refresh Job icon to refresh the selected Medianet job.

You can perform the following operations using the Medianet job browser. (See Table 5-11):

Table 5-11 Operations Using the Medianet Job Browser 

Button
Description

Stop

Stops or cancels a running job.

You can stop or cancel a running job. You will be alerted to confirm the cancellation of the job.

However, the job will be stopped only after the devices currently being processed are successfully completed. This is to ensure that no device is left in an inconsistent state.

Click OK to cancel all instances.

If you click Cancel, only the selected instance of the job is cancelled. The next instance of the job will appear in the Job browser with the status Scheduled.

Unless you own the job, your login determines whether you can use this option. You cannot re-start the stopped job.

Delete

Deletes the selected job from the job browser. You can delete more than one job.

Click OK to confirm the deletion. The job and its instances will be deleted.

You can delete a job that has been successful, failed, or stopped, but you cannot delete a running job.

Unless you own the job, your login determines whether you can use this option. You must stop a running job before you can delete it.

Refresh

Refreshes the Medianet job browser.

Refresh Job

Refreshes the job and you can see the current status of the job.


Viewing Job Details

From the Job Browser dialog box, you can learn more about any job by viewing its details.

The Job Details appears below the list of Medianet jobs. details are grouped into three parts:

Work Order

Device Details

Job Summary

Page/Folder
Description

Work Order

Displays general information about the job:

Job policies

Job details

Device Details

Contains detailed job results for each device in a table:

Device—List of devices on which the job was scheduled.

Status—Status of job (success, failure, etc.)

Message Summary—A message about the status of a job.

If the job failed on the device, the reason for failure is displayed.

If the job was a success on that device, the message Deploy Successful is displayed.

You can filter the devices by selecting a status or message summary and clicking Filter.

This page displays the number of rows you have set for display in the Rows per Page field. You can increase the rows up to 500 in each page.

You can navigate among the pages of the report using the navigation icons at the right bottom of this table.

Select a device and click Show Details to view the details such as protocol, status, and reason when applicable, task used and the CLI output for that device. These details appear in a pop-up window.

Job Summary

Click to display summary of completed job:

Job Summary:

Status

Start Time

End Time

Job Messages:

Pre-job Execution

Post-job Execution

Device Update:

Successful

Failed

Not attempted

Pending