Medianet Launches Plugfest with Media Services Proxy (MSP) Solutions

© 2012 Cisco and/or its affiliates. All rights reserved. 1

Conference Dates: September 10-13, 2012

Exhibit Dates: September 10-12, 2012

Location: Pennsylvania Convention Center; Philadelphia, PA

© 2012 Cisco and/or its affiliates. All rights reserved. 2 © 2012 Cisco and/or its affiliates. All rights reserved. 2

Validate your product’s interoperability with Cisco Medianet!

Speaker: Karthik Dakshinamoorthy, Product Manager, Cisco

New


PLUGFEST launches Media Services Proxy (MSP) as part of Cisco Medianet

MSP Capabilities Automatic Device Detection Automatic Switch Port Configuration Network Bandwidth Reservation Quality of Service Automatic Flow Awareness

Verification Testing

Plug-and-Play Testing of your IP Cameras with MSP No change required on the IP Cameras MSP Based on Open Standard Protocols Please visit us at Booth 213, Sep 10-12th with your Camera (s)

Partner Benefits

Interoperability with Cisco Medianet Cisco Developer Network (CDN) Benefits Cisco Compatible Logo Listing on Cisco Partner site with Test Results


Benefits for You..

!  No IP Camera Development or Upgrades … Plugfest (with Media Services Proxy) is network centric …

!  Value for your Installed Base … With only the network needing an upgrade, Medianet extends reach to the installed base of IP Cameras ….

!  Open Standards Based . . . MSP relies on IP Cameras supporting open standards based protocols. . .

!  Strong Cisco Partnership . . . Benefits of Cisco’s CDN (Cisco Developer Network) program: Cisco Compatible Logo, Listing on Cisco Partner pages and more…

!  Seamless IP Camera Integration with the Network . . . Reduces deployment time and mitigates admin challenges . . .


How does my network know what IP Cameras connected to it automatically?

Will any IP Camera benefit from Cisco Medianet solutions?

I want to apply my network features, say QoS, bandwidth reservation etc. specific to IP Cameras..

Auto device detection with MSP : No end point upgrades!!

Third Party support with MSP: supporting a range of well known protocols

Metadata: app-level info available to the network; Integration with core features/services like QoS, RSVP, Flow Metadata

I want to configure the network ports knowing it’s a surveillance camera behind it, automatically…

Auto Smart Ports (ASP): Device detection and port config happens in the switch automatically


Third-party extension of Medianet Benefits

MSP

Identification

Subset of Medianet Services

H.323/ RAS

DHCP

SIP/SDP snooping

RTSP

Auto Smart Ports

RSVP

Flow Metadata

QoS/C3PL

mDNS

Services Auto Network Port config

Bandwidth Reservation

App Awareness

Quality of Service

Plugfest @

ASIS’12!

MSP is a network-based solution where the switches and routers automatically identify end points and applications, flows coming from them and provide the right set of network services to them automatically


MSP Apps ! Services

End point Identification

Network Services

Flow Identification

mDNS SIP

SIP/SDP snooping

H.323

RTSP/SDP

H.323 Gateway Discovery

QoS Auto Smart Ports

Metadata

RSVP CAC


Use Cases for IP Surveillance Cameras


Provision

Application Visibility

Differentiated Services

Network as a Platform for IP Surveillance

Use Case 1

Use Case 2 Use Case 3


G 3/1

G 5/1

G 4/1

Device/End Point/Application Identification by MSP.

Apply ASP on the port based on downloaded profile for the device

Learn: Device Type Name Version Application AppID Version

Can apply the following:

•  QoS configuration •  Spanning-tree portfast) •  Port security/Trust •  Put port into certain VLAN •  Enable multicast •  EnergyWise - Power reporting, prioritization

MSP Providing Auto Smart Ports for IP Surveillance Cameras

Device Type – IPVS Camera

Download Port Templates for IP

surveillance cameras M


MSP Acting as a Metadata Producer

G 3/1

G 5/1

G 4/1

Device/Flow Identification by MSP. Update Metadata in local node

Propagate Metadata to downstream nodes: Metadata Proxy

Metadata Signaling RSVP

Transport

Device Type – IPVS Camera

IP Src IP Dst Prot L4 Src L4 Dst Application Vendor Model Version Other properties

10.1.1.2 20.1.1.2 UDP 2000 4000 IP Surveillance Axis XYZ 1.2 …

Flow Identifier Metadata


MSP Based Differentiated QoS Services for IP Surveillance Cameras

Metadata Database

IT-supported UC Clients

Best-effort Applications

MSP on Switch identifies surveillance applications, remarks packets

Packets from surveillance cameras sent to priority queue

M

IP Src IP Dst Prot L4 Src L4 Dst Application Vendor Model Version Other properties

10.1.1.2 20.1.1.2 UDP 2000 4000 Surveillance Axis XYZ 1.2 …

Policy on switch:

class-map match-all test match application surveillance

policy-map test class test set dscp af11 AF11 queue (surveillance)

Egress Queues for other traffic


MSP Offering Bandwidth Reservation services for IP Surveillance Cameras

G 3/1

G 5/1

G 4/1

Device/Flow Identification by MSP. Learn flow bandwidth parameters needed for RSVP reservations

Initiate RSVP reservation for the flow locally and downstream

RSVP Reservation RSVP CAC

Learn: Bandwidth IP Dst Address/Port IP Src Address/Port MTU

IP Header, Prot=46

RSVP Header MsgType=PATH TTL=255

HOP Object

Policy Object: App=TP

Tspec

Session=IP=A,Prot=17,Port=30000

SenderTemplate:sIP,sPort

RSVP Packet is formed and sent downstream with

learnt flow parameters and bandwidth

M


NEs

Metadata Signaled by Switch using MSP

1.1.1.1 10.1.1.1 2134 80 IP Surveillance

10.76.109.45 10.76.109.51 1200 2000 Telepresence

10.76.109.45 10.76.109.50 450 5060 IP Surveillance

20.1.1.1 125.1.1.1 1500 1600 IP Surveillance

FNF on the NEs

Netflow Cache: SRC ADDR DST ADDR APP NAME ======== ======== ======== 1.1.1.1 10.1.1.1 IP Surveillance 10.76.109.45 10.76.109.51 Telepresence 10.76.109.45 10.76.109.51 IP Surveillance 20.1.1.1 125.1.1.1 IP Surveillance

Metadata Database

Flow Begins

IP Surveillance Cameras


Component Solution Function

Auto Smart Ports (Switches)

"  Download IP Surveillance specific configuration to switch ports after detecting presence of a IP surveillance camera behind the port

Metadata (Routers + Switches)

"  Generate information about the IP Surveillance flow locally after detection and optionally propagate flow information to rest of the network

Flexible Netflow (Routers) *

"  Export learnt Metadata attributes to Netflow collectors (Cisco or third party) for better application visibility – Collectors can identify IP Surveillance traffic in the network

RSVP (Routers + Switches)

"  For Call Admission Control (CAC) functions: to reserve bandwidth for a surveillance flow for guaranteed network resources in the event of congestion

QoS (Routers + Switches)

"  To provide differentiated remarking of IP Surveillance flows based on generated Metadata

MSP "  Ties all above services together with simple, intuitive configuration (detection and services) on a port or global level

* - Not available today; In the roadmap


Procedures for Interoperability Verification Testing (IVT)


•  Demonstrate interoperability and support of your products with Cisco Medianet technologies

•  Will facilitate faster deployment of your IP Cameras/solutions and make integration with the network simpler and less error prone

•  Provide a prescriptive set of use cases that closely models realistic customer usage scenarios for your Cameras with the network

•  Key requirement for being recognized as a “Cisco Compatible” partner and to be eligible for go-to-market activities (as part of CDN)


(PLUGFEST)

Partners Register For PlugFest (provide contact details); Specify Models they would like to get tested/validated;

Optionally, provide a PCAP file for each of their models;

Partners Enroll for CDN if not already a member; Specify CDN level (Registered Developer);

Partners walk in for Plugfest with IP Cameras; Tests carried out during the event for partners;

Verification results need not be announced the same day;

1

2

3

MANDATORY

RECOMMENDED

CDN Registration is MANDATORY for IVT Results to be Published and to get the Cisco Compatible Status

PLEASE WALK INTO BOOTH 213 DURING SHOW HOURS (SEP 10-12) for Cisco Verification!


•  To be a candidate for IVT partners need to be a registered CDN member As soon as partners are registered they can use the Registered Logo

•  Once partners go through IVT and demonstrate their support for the all test cases, they will be granted the status of “Compatible” and will be able to use the CDN Compatible Logo. Their level of certification would be listed in the Medianet CDN page

•  Partners/endpoint models will be listed on the CDN Partner Page with the associated release on which the IVT has been performed


Features Use Cases

Partner Media Services Proxy (MSP)

UC – 1 Easier Deployment

UC – 2 Enhanced Application Awareness

UC – 3 Differentiated network treatment

UC – 4 Bandwidth Reservations

Vendor A – Surveillance Camera – 1 Model #, version, Address Contact person

Verified on: 09/01/2012 Medianet version 3.0

Vendor A – Surveillance Camera – 1 Model #, version, Address Contact person


Vendor B – Surveillance Camera – 1 Model #, version, Address Contact person


Simplified example of page

No support

Partial support

Full support


•  If interested in registering for an IVT or working closer with the MSP team – please register on the CDN program website if not already registered with CDN: http://developer.cisco.com/web/partner - apply for the program Medianet – Media Services Proxy

•  Once your application is accepted and you are ready for IVT, please submit and IVT request

Access your Developer Dashboard, go to the Registered Products Tab and select "Actions" and "Add New IVT Request" next to the product to be submitted for IVT – Choose Medianet – Medianet Services Proxy


Test Cases


M WAN Cloud

Cat4k Switch ISRG2 Router ISRG2 Router

IP Surveillance Camera

Laptop with VLC

Equipment Required:

•  1 Catalyst 4500 Switches •  2 ISRG2 Routers •  Laptop with VLC client •  IP Surveillance Camera from Partner •  Another laptop connected to cat4k for wireshark purposes

MSP Runs here: Check Auto Smart Ports Local Metadata Generation QoS remarking

Verify RSVP CAC Verify Metadata generation QoS remarking


Test Case Number Test Case Name

MSP01 Automatic Device Detection

MSP02 Automatic Flow Identification

MSP03 Automatic Port Provisioning

MSP04 MSP Triggered Metadata Generation

MSP05 MSP Triggered Bandwidth Reservation

MSP06 QoS Remarking Based on Metadata Attributes


Feature UC-01 UC-02 UC-03 UC-04

Media Services Proxy (MSP)

MSP01, MSP03 MSP01, MSP02, MSP03 MSP01, MSP02, MSP03, MSP05

MSP01, MSP02, MSP04


Global MSP and Metadata Configuration

•  First 2 slides also include generic MSP configs required for subsequent use cases

•  Enable Media Services Proxy on the access switch using “Profile flow” configuration

Sample Config:

cat4k1#conf t

cat4k-1(config)# profile flow

cat4k-1(config)#end

cat4k1#

•  Enable Metadata on all the nodes using “metadata flow” config

Sample Config:

cat4k1#conf t

cat4k-1(config)# metadata flow

cat4k-1(config)#end

cat4k1#


Configuring MSP Services and associating with Interface

•  Configure Media Services Profile to specify the services to the flow. In the below config we are configuring both rsvp and metadata services

Sample Config:

cat4k#conf t

cat4k(config)#media-proxy services profile msp_all

cat4k(config-ms)#rsvp

cat4k(config-ms-rsvp)#exit

cat4k(config-ms)#metadata

cat4k(config-ms-md)#end

•  Enable this profile on a interface

Sample Config:

cat4k#conf t

cat4k(config)#int gi3/47

cat4k(config-if)#media-proxy services msp_all

cat4k(config-if)#end


Validate Connected Endpoint

•  Name: Identify the End point device connected to the access switch.

•  Detailed steps:

a.  Connect the end point to the access switch.

b.  Verify that the end point device is identified using “Show profile device” CLI.

c.  Enable debugs using “debug profile flow all” for detailed tracking

•  Sample Output:

cat4k1#show profile device

MAC Address Interface Device class Device Name Device Vendor

============== ========== ================= ============ ==============

0040.8cad.c993 Gi3/47 Surveillance-Camera AXIS-Camera AXIS,Network Camera,


Validate Flow coming from the Endpoint

•  Name: Identify the flow details of the video stream from the Camera.


a.  Register the camera to the VSOM . Alternatively, we can use VLC player.

b.  Request for streaming from the camera using VSOM / VLC player.

c.  Verify that the flow is identified using “Show profile flow” CLI.

d.  Enable debugs using “debug profile flow all”


cat4k-1#show profile flow

Source-IP sPort Dest-IP dPort pro I/F Media Services profile

70.1.1.10 50004 60.1.1.11 1722 UDP Gi3/47 msp_all

cat4k-1#


Validate automatic port configurations through Auto Smart Ports

•  Name: Validate port configurations being applied through ASP after detecting an IP Surveillance end point


a.  Verify no active configurations are applied to the switch port

b.  Connect the end point to the access switch.

c.  Verify that a syslog is generated on device detection and ASP configuration being applied to the port

d.  Verify if the IP surveillance (IPVS) specific config has been applied to the port. An example of a built in macro for IPVS is listed alongside

e.  Enable debugs using “debug profile flow all” for detailed tracking

Example Config: Before macro is applied interface GigabitEthernet2/12 no switchport ip address 70.1.1.1 255.255.255.0 After macro is applied: interface GigabitEthernet2/12 no switchport ip address 70.1.1.1 255.255.255.0 neighbor device type ip-camera macro description CISCO_MS_IPVSC_EVENT spanning-tree portfast spanning-tree bpdufilter enable service-policy input AutoQos-4.0-Cisco-IPVSV-Input-Policy service-policy output AutoQos-4.0-Output-Policy


Metadata Generation through MSP

•  Name: Generation of Metadata in local Device


a.  Request for streaming from the camera using VSOM / VLC player.

b.  Verify that the flow is identified using “Show profile flow” CLI.

c.  Verify that Metadata is generated for the flow using “show metadata flow” CLI

d.  Enable debugs using “debug metadata flow all” for detailed tracking


cat4k-1#show metadata flow table

Flow To From Protocol DPort SPort Ingress I/F Egress I/F SSRC

1 60.1.1.11 70.1.1.10 UDP 1722 50004 Gi3/47 Gi3/48 1716307277

cat4k-1#



•  Name: Verify metadata attributes of the flow generated by MSP


a.  Verify the metadata attributes using “show metadata flow local-flow-id <id>”


cat4k1#sh metadata flow local-flow-id 1

To From Protocol SPort DPort Ingress I/F Egress I/F

60.1.1.11 70.1.1.10 UDP 50000 6970 GigabitEthernet3/47

Metadata Attributes :

End Point Model : AXIS-Camera

Application Name : rtp

Application Tag : DDA64892

Device-class : “Surveillance”

Mime Type : H264

Payload Type : 96

Clock Frequency : 90000

Bandwidth : 50000

SSRC : 2986382046



•  Name: Verify metadata attributes are sent downstream to the network


a.  Verify the metadata attributes using “show metadata flow local-flow-id <id>” on downstream device


ISR-1#sh metadata flow local-flow-id 1

To From Protocol SPort DPort Ingress I/F Egress I/F

60.1.1.11 70.1.1.10 UDP 50000 6970 GigabitEthernet0/0

Metadata Attributes :

End Point Model : AXIS-Camera

Application Name : rtp

Application Tag : DDA64892

Device-class : “Surveillance”

Mime Type : H264

Payload Type : 96

Clock Frequency : 90000

Bandwidth : 50000

SSRC : 2986382046


RSVP CAC Reservation through MSP

•  Name: Bandwidth reservation for the video flow using RSVP


a.  Request for streaming from the camera using VSOM/VLC player

b.  Verify that the flow is identified using “Show profile flow” CLI.

c.  Verify that RSVP is triggered to reserve bandwidth for the flow.

d.  Verify that bandwidth is reserved using “show ip rsvp reservation” CLI

e.  Enable debugs using “debug ip rsvp”


cat4k-1#show ip rsvp sender

To From Pro DPort Sport Prev Hop I/F BPS

60.1.1.11 70.1.1.10 UDP 49160 49152 40.1.1.2 Gi3/47 256K

cat4k-1#show ip rsvp reservation

To From Pro DPort Sport Next Hop I/F Fi Serv BPS

60.1.1.11 70.1.1.10 UDP 49160 49152 40.1.1.2 Gi3/47 256K


RSVP CAC Reservation on Intermediate Nodes

•  Name: Verify bandwidth reservation for the flow on intermediate nodes.


a.  Verify that bandwidth is reserved on intermediate nodes using “show ip rsvp reservation” and “show ip rsvp int “ CLI on the intermediate ISRG2 devices

b.  Enable debugs using “debug ip rsvp”


ISR-1#show ip rsvp reservation


60.1.1.11 70.1.1.10 UDP 49160 49152 40.1.1.2 Gi0/0 256K

ISR-2#show ip rsvp reservation


60.1.1.11 70.1.1.10 UDP 49160 49152 40.1.1.2 Gi0/1 256K

ISR-2#sh ip rsvp int

interface rsvp allocated i/f max flow max sub max

G0/0 ena 0 75M 75M 0

G0/1 ena 256K 75M 75M


Remarking IP Surveillance to specific DSCP

•  Configure class-map to filter flows based on metadata attributes Sample Config:

cat4k#conf t

cat4k(config)#class-map match-any test

cat4k(config-cmap)#match application attribute device-class surveillance

cat4k(config-cmap)#end

•  Configure a policy-map to remark dscp of all the flows belonging to above class-map

Sample Config:

cat4k#conf t

cat4k(config)#policy-map test

cat4k(config-pmap)#class test

cat4k(config-pmap-c)#set dscp cs4

cat4k(config-pmap-c)#end


Remarking IP Surveillance to specific DSCP

•  Configure a service-policy on the egress interface with policy “test” Sample Config:

cat4k(config)#int g3/47

cat4k(config-if)#service-policy output test

•  Verify that the packets from the camera are remarked with dscp cs4. Sample Output:

cat4k#sh policy-map int g3/47

Service-policy output: test Class-map: test (match-any)

37297 packets, 29643526 bytes

5 minute offered rate 1503000 bps

match: application attribute device-class surveillance 37297 packets, 29643526 bytes

5 minute offered rate 357000 bps, drop rate 0000 bps

Qos Set

Packets marked 37297


Medianet Launches Plugfest with Media Services Proxy (MSP) Solutions

Technology