03 7600

© 2009 Cisco Systems, Inc. All rights reserved. Cisco Confidential 1

Cisco 7600 Update

Alexey Mitronichev

[email protected]


Agenda

New Hardware

SRD Release feature

SRE Release features


New Hardware


BNGBROADBANDNEXT GEN.


ES+XT Feature Highlights at FCS• Feature Parity with ES+

• IPoDWDM enabled: LAN, WAN, ITU-T G.709 OTN Transport Modes

• ITU-T G.709/FEC (interop with CRS-1/GSR/MSTP)

• EFEC – ITU G.975.1 I.4 mode between 7600’s only

• OTN G.709 and WANPHY Performance Monitoring

• Automatic Laser Shutdown (safety compliance)

• SyncE Ready, Physical layer (SSM, etc. to follow)

• Network Clocking Support (parity with SIP200/400), Local Port Loop Timing

• BITS Timing (Import/Export), T1 (ESF or D4), E1 (CRC4), J1 (ESF), 2.048Mb (unframed)

• Loopback Line and Loopback Internal for troubleshooting support

• CISCO-OTN-MIB support

ES+ Extended Transport Card Overview

Future Feature Support:• Proactive-Protection (PRE FEC BER for TE-FRR)• Circuit Provisioning Integration with CTM• Virtual Transponder• WANPHY MIB (RFC 3637)• OPT-IF-MIB (RFC 3591)• PRE FEC BER QinQ Margin displayed to operator

Chassis Support:7606, 7609, 7603-S, 7604, 7606-S, 7609-S, 7613

Processor Support: Sup720-3B/XL, RSP720-3C/XL, RSP720-10GE-3C/XL

General Feature Support: Parity with ES+ software and hardware based features

Min IOS SW: 12.2(33)SRD1

Enabling IPoDWDMon 7600


XFP Based 10GigE Ports• LR, ER, ZR Optics• Pluggable DWDM optics in 32 wavelengths (non-tunable)• LANPHY, WANPHY, and OTN modes

BITS Interface• Used to capture external clocking• 1588 and SyncE support (partial at FCS)

ES+ Based linecard with DFC-3CXL• 1M FIB Entries• IPv4/IPv6 in Hardware• Support for 96k MAC Addresses• 256,000 HW Queues (128K supported)• 48Mpps forwarding capability• 512MB buffer per port (100ms tx and 100ms rx)• EVC, VPLS, MPLS, L2TPv3, REP

ES+XT: IPoDWDM with Advanced Ethernet Services


* ES+XT parity - OTN (G.709/FEC) WANPHY support, post FCS (CY10)

2x10GE + 20x1

1x10GE + 10x1

ES+XC Feature Highlights

BNGBROADBANDNEXT GEN.


NNIFacing Links

Core or Optical

Network

UNIFacing Links

Slo

t 1

Slo

t 2

Slo

t 3

Slo

t 4

Slo

t 5

Slo

t 6

Slo

t 7

Slo

t 8

Slo

t 9

ES

+X

C

ES

+X

C

ES

+40

GE

ES

+40

GE

RS

P-7

20

RS

P-7

20

ES

+40

GE

ES

+40

GE

ES

+40

GE7609

Chassis

UNI and NNI links on one slot

Uplink/Slot Redundancy

Cisco Internal

1. Efficiency

2. Resiliency


16k 128k (I/E)

No Yes

128k (I/E)

YesBNG Capable

Number of Queues

LAN/WANLAN LAN

YesNoNo

ES+

OTN – G.709/FEC

10G Interface Modes

ES+XTES20

Video Mon Capable

L3VPN

YesYesNo

YesYesYes

H-QoS YesYesYes

L2VPN/VPLS YesYesYes

DFC 3CXL3C/3CXL3C/3CXL

SyncE Capable YesYesNo

128k (I/E)

Yes

LAN/WAN

Yes

ES+XC

Yes

Yes

Yes

Yes

3C/3CXL

Yes

Interfaces 2/4x10GE

20/40xGE

2/4x10GE

20/40xGE

2x10GE

4x10GE

2x10+20X1

1x10+10X1

7600 Ethernet Services Linecard Portfolio


Cisco 7609-S

Power Consumption – ES40 is Green

7609-S

6000w max

7609-S

6000w max

Slot 1 ES40-GE-3C 391w ES20-GE 340w




Slot 5 RSP720-3C 400w RSP720-3C 400w

Slot 6 RSP720-3C 400w RSP720-3C 400w

Slot 7 ES40-10G-3C 371w ES20-10G 375w

Slot 8 ES40-10G-3C 371w ES20-10G 375w

Slot 9 ES40-10G-3C 371w ES20-10G 375w

Dual Fan tray 480w Dual Fan tray 480w

Total power required

3957w 3765wES40 is Greener

With Double Performance


7600 Ethernet CardsHigh-Level Comparison

ES40/ES20+ ES20 SIP600 SIP400 WS-X67xx

Interface Density 2,4x10G/20,40x1G 2x10G/20x1G 1x10G/5,10x1G 2x,5xG/1x10G 24,48x1G/4,8x10G

Bandwidth Capacity 40G/20G 20G 10G 5G 40G

Forwarding Capacity Up to 48Mpps Up to 30Mpps Up to 25Mpps Up to 6 Mpps Up to 48Mpps

VPLS 12.2SRD Supported Supported Supported Not Supported

EVC Infrastructure/Scale 12.2SRD Supported Not Supported Supported Not Supported

Vlan Local significance 12.2SRD Supported Not Supported Supported Not Supported

H-QoS 12.2SRD Supported Supported Supported Not Supported

Number of Queues 128k for ES40, 64k

for ES20+ via

MQC

16K per line

card via

MQC

8K per line

card via

MQC

32k per line

card via

MQC

1 OR 2 RX queues

4 OR 8 TX queues

per port

Shaping 12.2SRD Supported Supported Supported Not Supported


ES-40 Forwarding Performance

Per NPU No QoS With 100% Line Rate

With QoS With 100% Line Rate

Raw IPv4/v6 Forwarding 64B/84B 85B

Raw L2 v4/v6 Switching 64B/84B 85B

L3VPN 64B 96B

L3 Multicast 64B 85B

VPLS 64B 96B

L2 Multicast 80B 85B

EVC – MPB 128B 128B

EVC – EoMPLS 128B 128B


7600 RSP720-10GE HA Support In SRC

Primary Engine

Standby Engine

Standby GEs Not Accessible

Standby 10GEs Not Accessible

HA support in SRC for a redundant configuration is limited to RPR mode

If Primary fails, system only supports RPR –5 minutes outage, states are lost and convergence required.

Primary GEs Are Accessible

Primary 10GEs Are Accessible


7600 RSP720-10GE HA Support In SRE

Primary Engine

Standby Engine

Standby GEs Are Accessible

Standby 10GEs Are Accessible

HA support in SRE will have parity with Sup720 and RSP720-GE

If Primary fails, system supports follow HA • RPR• RPR+• NSF/SSO• eFSU• ISSU Capable

Primary GEs Are Accessible

Primary 10GEs Are Accessible


Service Module SupportRSP720, and RSP720-10G

RSP720 RSP720-10G

SRC SRD SRC SRD

NAM-1 Yes Yes No No

NAM-2 Yes Yes No Yes

CSG1 No No No No

MWAM No No No No

SAMI Yes Yes No No

CSG2 No Yes No Yes

IDSM2 Yes Yes No No

FWSM Yes Yes No No

ACE Yes Yes No No

ADM Yes Yes No No

AGM Yes Yes No No

7600-SSC-400/IPSec

Yes Yes No No

WiSM1 No No No No

SBC Yes Yes No No

DPI No No No No


Licencing


New ES+ Licensing


Changes to ES20 Licensing


Carrier Ethernet Update


SRD EVC New Features SummaryFeature SIP-400 ES20 ES40

QoS

BRR on EVC Now 12.2SRD 12.2SRD

2R3C policers on EVC Now12.2SRD

(ingress only)12.2SRD

QoS Parity for “encapdefault” EVC

12.2SRD 12.2SRD 12.2SRD

Resiliency MST on EVC BD Not Planned 12.2SRD 12.2SRD

OAM and MIB

CFM for EVC Bridge-domain

Not Planned 12.2SRD 12.2SRD

EVC 2.0 MIB 12.2SRD 12.2SRD 12.2SRD

Security

DHCP snooping w/ Option 82 insertion and DAI

12.2SRD 12.2SRD 12.2SRD

Broadcast storm control Not Planned 12.2SRD 12.2SRD

L2 ACLs Not Planned 12.2SRD 12.2SRD

IP Source Guard Not Planned 12.2SRE 12.2SRD

Port/MAC security Not Planned 12.2SRD 12.2SRD

EVC Port-channel with LACP Not Planned 12.2SRD 12.2SRD

Miscellaneous UDLD Not Planned 12.2SRD 12.2SRD

Custom Ethertype Not Planned 12.2SRD 12.2SRD


MST on EVC – Design Points

MST only – no boundary functionality (i.e. peer in the port must be running MST)

Outer Encap VLAN to MST Instance Mapping

No changes to existing MST configuration

Support for unambiguous Outer Encap VLAN

Outer VLAN Tag must be unique (i.e. encap 100 or encap 100 second 200-400)

No Support for the following service instances

Default

Untagged

Range or list on outer tag (i.e. encap 100,200 or encap 100-200)

Priority tagged (not supported by EVC on 7600)


MST on EVC – Design Points (cont)

Bridged Services blocking

Only bridge-domain EVCs are blocked

Service instances with same Outer VLAN must be bridged together

Automatic addition of Bridge-domain into the VLAN Database

VLAN local significance: MST acts on outer Encap VLAN. Bridging acts on Bridge-domain

Object visible to MST: [Port, Outer VLAN] aka VPORT

Single MST “Region”, 64+1 MST Instances

VPLS or Switchport in the core

No TCN grouping – when merging multiple customers in the same outer Vlan, TCN affects all customers on that MST instance


MST on EVC – Configuration Model

No change to port’s configurationInterface gi1/1

Service instance 1 ethernet

encapsulation dot1q 10 second dot1q 200

rewrite ingress tag pop 2 symmetric

bridge-domain 100

No Changes to existing MST Configurationspanning-tree mode mst

spanning-tree mst configuration

name cisco

instance 1 vlan 1-1000



No changes to existing NPE-Redundancy Configl2 vfi PE1 manual

vpn id 1

forward permit l2protocol all

neighbor 2.2.2.2 encapsulation mpls

Int vlan 100

Xconnect vfi PE1


SRD EVC Scalability Update


VPLS Scalability

Nothing changed except the maximum peers per VFI

Maximum peers per VFI increase to be 110 if the uplink is SIP-400 or ES20 or ES40

If uplink is SIP-600, the number will drop to 60 per system unless you manually configure it to be 110. In this case, SIP-600 won’t be selected as VPLS uplink even if it’s present and configured on the box

AGG1-rossi(config)#platform vfi max-peers ?

<110-110> max peers value allowed 60 or 110

<60-60> max peers value allowed 60 or 110


EVC Scalability 32k EVCs per box independent of service (local

connect, xconnect, bridge-domain)

16K EVCs per line card (ES20, ES40, SIP-400)

8K EVCs per port without QoS, 4K EVCs per port with QoS

Maximum EVCs (service instances) per Bridge-domain–120 EVCs per bridge-domain per SIP-400

–110 EVCs per bridge-domain per NP for ES20 and ES40, thus ES20 support 220 EVCs per bridge-domain per linecard, ES40 support 440 EVCs per bridge-domain per linecard

Note,

–Both VPLS VC and service instance VC are presented as pseudo port which require LTL index resource. The LTL index is shared among VPLS VC and service instance VC


EVC Port-Channel with LACP


Overview

Port Channel interfaces represent aggregated Ethernet ports for both bandwidth increasing and link redundancy

7600 supports routed interfaces and L2 switchports over port channels long time ago

EVC Port Channel allows Ethernet service instances (EVCs) to be configured over port channel interfaces. It’s supported from SRCrelease with static channel mode “on”

SRD release will support LACP as channel protocol in addition to static channel mode on configuration. PAGP is not supported

SIP-400 doesn’t support port-channel


Traffic Load Balancing Overview

Gi4/0/0

Gi4/0/10

Interface po5

Forwarding Function

EVC 1

EVC 2

EVC 1

EVC 2

Ingress traffic for an EVC can be received on any of the member ports of the port channel depends on the load balancing algorithm used on the peer device Egress traffic for an EVC is transmitted out of a single pre-determined member port. Thus the egress load balancing is per service instance

Gi4/0/0

Gi4/0/10

Interface po5

Forwarding Function

EVC 1

EVC 2

Ingress Egress


Egress Traffic Load Balancing

Egress load balance show command on LC

ESM-20G-4# show platform interface port-channel 5 efp all

index 0x4002 if_number 79 efp ID 2

service: bridging

configured member ports:

slot 4 port 1 pseudo_slotunit 192

slot 4 port 11 pseudo_slotunit 256

egress interface: Gi4/0/0

ppe [0]: index 3

ppe [1]: index 2

index 0x4003 if_number 79 efp ID 3

service: xconnect

circuit ID: 16387, local vc label 17

egress interface: Gi4/0/10

ppe [0]: index 4

ppe [1]: index 3

Number of entries: 2


SRD QoS update


Interface Types

Main Interface

Sub Interface

Switchport

Service Instance

evc port channel

L3 port channel

L2 Port channel

Port channel Member link

Qos Not supported in SRD

Will be in SRDx/SRE


QoS Features: Classification Matrix

Classify PREC / DSCP

ACL EXP COS COS-INNER

VLAN VLAN-INNER

INPUT VLAN (O/P Intf.)

Interface Type ingress

egree

ingress

egree

ingress

egree

ingress

egree

ingress

egree

ingress

egree

ingress

egree egress

L3 Main Interface yes yes yes yes yes yes Yes Yes no no Yes (1)

Yes (1)

no no Yes (3)

L3 Sub Interface yes yes yes yes yes yes yes yes no no Yes Yes no no No

Switchport / Trunk port

Yes Yes Yes (*2)

Yes (*2)

yes yes yes yes no no yes yes no no no

Interface Vlan / SVI ( *3)

no no no no no no Yes Yes no no no no no no no

EVC / QinQ Yes Yes Yes (*2)

Yes (*2)

no no yes yes yes yes yes yes yes yes no

1.for policy-map on main interface and identifying sub-IF or EVC via “match vlan” in parent classes2.Only classified based on SMAC using L2ACL.3. ES+ supports classification on SVI only for the case SW-EOMPLS/VPLS


QoS Features: Marking Matrix

Marking PREC / DSCP EXP COS COS-INNER

Interface Type ingress Egress ingress Egress ingress Egress ingress Egress

L3 Main Interface yes yes yes yes Yes (*1) Yes (*1) no no

L3 Sub Interface yes yes yes yes yes yes no no

Switchport / Trunk port no no no no yes yes no no

Interface Vlan / SVI (*#) (*2)

no no Yes (SW-EOMPLS/V

PLS)

no no no no no

EVC / QinQ yes yes yes (EVC Based SW-EOMPLS)

no Yes

(Except ScEoMPLS)

Yes Yes yes

1. To match Sub-if/EVC traffic and policy-map applied on Main-Intf2. ES+ supports Marking on SVI only for the case SW-EOMPLS/VPLS


QoS Features: Policing

2 levels of policing.

-first child and then parent class policing

48K policers per NP (Ingress and Egress together)

1r2c

2r3c

Granularity Policer

cir and pir can be any value between 64,000bps to 10Gbps

256 profiles/different rates per NP

Multiple marking can be specified (for conform/exceed/violate police actions)


QoS Features: Queuing

8 queues per policymap at child level 2x priority queues and 6x CBWFQ queues or

8x CBWFQ queues

Egress: 8k parent (logical links) per NP

Ingress: 4k parent (logical links) per NP

32K child queues on Ingress per NP (128K per LC)

64K child queues on Egress per NP (256K per LC)

Parent class-default on sub-interface/evcs.

Parent user defined class-map on Main Interface/Switchport.


L2TPv3 on ES-40


L2TPv3 Overview

An L2TPv3 tunnel sits between a PE pair, usually terminating on loopback interfaces as the tunnel endpoints

One L2TPv3 tunnel can have multiple data connections, and each data connection is termed as an L2TPv3 session

Each session is identified by a session ID which is unique across the entire router.

IP cloudEthernet

7600 as PE

CE

CE7600 as PE

L2TPv3 Tunnel

Pseudowire

Attachment ckt Attachment ckt

L2 Frame Outer L2

Header

Outer

IPv4

Header

Session-id Cookie L2-specific

sublayer

L2

Payload

L2 Frame


Hardware and Software Requirements

Introduced in SRC on SIP-400 cards ( ATM and Ethernet only)

SRD brings in L2TPv3 on ES-40.

The minimum requirement is ES-40 should be facing the CE.

Core facing can be any card

The command “mls reserve l2tpv3 slot [1-13] [processor [1-4]]”is being introduced along with this feature

Supported features

• Ethernet port to port mode

• Ethernet VLAN to VLAN mode

• DF Bit Reflection from Inner IP to Outer IP

• L2TPV3 Packet ToS Marking

• Path MTU Discovery. Path MTU Discovery is enabled when “ip mtu” is configured for the PW.

• L2TPV3 IP Packet Fragmentation , performed by RP


SRE


Carrier EthernetEVC (Service) Groups

802.1ag-2007 (draft 8.1)CFM on VPLS/EVC

CFM in EVC with xconnectREP integration with EVC and VPLS

Reverse L2GP (ES, ES+)Static MAC (ucast/mcast) EFP & PW

GEC multi-chassis – mLACP Ph.IFlex service EVC (CoS, Ethertype)

Control Word Configuration for VPLSL3/L4 ACL on EVC

Y.1731 Ethernet Lock (AIS/RDI/LCK)802.1ah (inc. VPLS integration)LAG Support for VPLS Uplink

GE LAG on UNI with adv. EVC LBBridge Domain MIB

Custom Ethertype with EVC (ES+ PC)MAC security on EVC (ES+ PC)

DHCP snooping w/ Option 82 insertionon EVC (PC ES+)

MobileMS PW with OAM/VCCV

Cell Packing for OC-48 ATM SPA on SIP-400Cell Packing for CEoPS

End-to-End VCCV on MS-PWACR for PW (MPLS)

SyncE L1 support on ES+ & Metronome SPALTE gateway - GTPv2

2G grooming with CEOP SPA AIS proc. (in SRD3)

12.2SRE Feature Summary

High AvailabilityMulticast HA

PW-redundancy w/PW Status TLVActive/Standby Bit -- Hot Standby PW

BFD on port channelBFD NSF / SSO support

BFD MIB IPv4/IPv6BFD Scale 1200 sessions MPLS/IP BGP PIC Edge

TE Path Protection > 8 +paths

Video / MulticastLSM:P2MP TE

VideoMon Phase 1* (ES+)

MPLS/VPNMPLSoGRE on ES+

2547oMGREISIS LDP SyncL3VPN scale

Routing4Byte ASN

IPv6 restructuring

QOS4 level Egress/3-level ingress H-QoS

on EFP GroupSIP-400 triple nesting QOS

L3/L4 class./marking on EVC(ES20)IPv6 Hop By Hop policing on EFlexWAN

and SIP-200 (in SRD3)

ISGIP Sessions on GEC/1:1

RAS ProjectsES+ ISG Feature Parity SIP400

ES+ PPPoE Feature Parity (SRD)Multicast Co-existence with sessionNas port option 82 + option 60 TAL

DHCP Auth. Policy (SIP400/ES+)ISG usability enhancements

HardwareX2-ZR (RSP720-10GE, 6708)

X2-DWDM-XX.XX (RSP720-10GE, 6708)X2-10GB-LRM (RSP720-10GE, 6708)

8 new DWDM-SFP PIDsRSP720-10GE Phase II

4500W DC power supply for 7606-SES+ Combo Cards

Metronome SPA (2 x 1GE)

* Targeted for a rebuilt of SRE

Status: Execute CommittedFCS : Q4 CY09


Carrier Ethernet


Carrier Ethernet

draft-ietf-pwe3-redundancy-bit-01

http://tools.ietf.org/html/draft-ietf-pwe3-redundancy-bit












What is Video Monitoring

Video Monitoring is for video transmission quality

MPEG is the coding scheme for digitized video/audio. The network over which it transports are different

IP + UDP + MPEG <-- What we support

IP + UDP + RTP + MPEG

The different transmission methods use different monitoring techniques

METRICS – various measuring data by using those techniques

All METRICS are performance measurement data with respect to the video transmission quality (delay, jitter, latency, loss)


MDI Metric (RFC 4445)

Components:

• Media Loss Rate (MLR): Rate at which discontinuities are detected in the flow

• Delay Factor (DF): Measured as max difference between the arrival and drain of packets


IP-CBR Metric

Components:

• Media Rate Variation (MRV): Variation in the media rate when compared with the nominal media rate (CBR)

Expected MRV = (Actual rate – Expected rate)/(Expected rate)

• Delay Factor (DF): Measured as max difference between the arrival and drain of packets – [Same as DF in MDI metric]


TCA (Threshold Crossing Alerts)

The routers can be made to generate SYSLOG messages (alarms) when the thresholds have reached

MDI Metrics: MDI-MLR, MDI-DF

IP-CBR Metrics: IP-CBR-MRV, IP-CBR-DF

TCA Severity Mapping to SYSLOG

alerts (severity=1) => map to TCA severity level "critical"

critical (severity=2)=> map to TCA severity level "major"

errors (severity=3)=> map to TCA severity level "minor"

warnings (severity=4)=> map to TCA severity level "warning"


MSE (Media Stop Event)

MSE is a boolean value representing that no packets have been received on a valid flow for the entire measurement period. It assumes knowledge of the transport rules for valid flow delivery.

The following conditions should trigger a valid MSE:

o Server failure

o Upstream network node failure

The following example will NOT trigger MSE:

o IGMP Leave

o SPT (shortest path tree) switchover

o RPF path change


Ingress/Egress Monitoring VideoMon metrics can be collected on both ingress and egress interfaces

Ingress: Pros: Less configuration; Single set of data per multicast flow

Cons: Provides data for preceding network segment; Deployment restricted

Egress: Pros: Measurement includes current hop; Deployment not restricted

Cons: More configuration and monitoring points; Potentially redundant and voluminous data


Example

Topology

Source-----router-1----router-2------receiver

te3/3 te4/3

Packet Loss profile

0.05% uniform packet loss

Step:

1)1 minutes no loss no jitter traffic

2)2.5 minutes of injection loss

3)1 minutes no loss no jitter traffic again


Sample Configuration (on router-2)ip access-list extended video_1

permit ip any 232.0.0.0 0.255.255.255

class-map match-any video_1

match access-group name video_1

policy-map type flow-mon video_1

class video_1

flow-param mon-interval 60

flow-param history 15

flow-param timeout 4

mdi-metric bit-rate 100000000

mdi-metric pkt-size 1347

react mdi-mlr threshold lower-limit 1 upper-limit 100 severity

minor

react mdi-mlr threshold type immediate

react mdi-mlr action syslog

interface TenGigabitEthernet4/3

ip address 30.30.33.1 255.255.255.0

ip pim sparse-dense-mode

ip igmp version 3

load-interval 30

service-policy type flow-mon output video_1

1. Configure ACL to filter the flows to

monitor

2. Configure class-map

3. Configure policy-map

3.1 Flow parameter to define how you

want the monitoring to be done

3.2 Configure Flow

monitoring TCA reaction

4. Apply on the interface with right

direction


Sample Show commandUPE1-7609S#show policy-map type flow-mon interface gi2/1.100

GigabitEthernet2/1.100

Service-policy output: video_2

class-map: video_2

mon-interval 30, history 10, timeout 5

flow: 1, IPV4; Dest: 232.0.1.26 port 4000; Src: 20.9.2.2 port 1024

intvl type pkt_cnt mrv/mlr df

-----+----+------------+------------+--------

63 mdi 13290 0 2357

64 mdi 13290 0 2362

65 mdi 13247 8 2364

66 mdi 13279 13 4576

67 mdi 13247 11 2364

68 mdi 13283 7 4541

69 mdi 13284 7 4550

70 mdi 13290 0 2364

71 mdi 13290 0 2362

Interval 63 – 64 : no loss, no jitter

Interval 65 : start injecting 0.05% of packet loss

Interval 66 – 68 : loss is continuously injected

Interval 69 : stop injecting 0.05% of packet loss

Interval 70 - 71 : no loss, no jitter again

Note: This is MDI metric on a 1G output port


Sample TCA SYSLOGrsp720-2#show policy-map type flow-mon interface te3/3

TenGigabitEthernet3/3

Service-policy output: mn_cont

class-map: mn_cont

mon-interval 30, history 11, timeout 4

flow: 1, IPV4; Dest: 232.0.1.1 port 0; Src: 30.30.30.2 port 0

intvl type pkt_cnt mrv/mlr df(usec)

-----+----+------------+------------+----------

72 cbr 8220144 0.0101 4

73 cbr 8220144 0.0101 5

74 cbr 8217481 0.00978 20

75 cbr 8215909 0.00958 440

76 cbr 8216035 0.0096 16

77 cbr 8216040 0.0096 16

78 cbr 8216577 0.00966 17

79 cbr 8220144 0.0101 4

80 cbr 8220144 0.0101 4

TCA on MRV: Lower-limit: 0.0001, upper-limit: 0.0098

Alert set:*Apr 24 01:01:22.371: %FLOWMON-2-ALERT_MAJ_SET: [IPCBR-

MRV]: SRC:30.30.30.2, DST:232.0.1.1, Te3/3, Output

Alert Clear:*Apr 24 01:03:23.095: %FLOWMON-2-ALERT_MAJ_CLEAR: [IPCBR-

MRV]: SRC:30.30.30.2, DST:232.0.1.3, Te3/3, Output


Case Study – MediaNet The ability to proactively monitor the

health of the infrastructure carrying MPEG-2 streams is essential for increasing IP video subscribers’ quality of experience (QoE) (MDI Metric is used)

o Case 1: many providers already deploy multicast based service through the use of PIM-SSM

o Case 2: providers planning on deploying point-to-multipoint RSVP-TE (LSM)

Enable Vidmon for MDI metric on Ingress ports of 7600-1, and egress ports of both 7600-2 and 7600-3

Impairment is introduced between 7600-3 and CRS-1-2

Expected results:

- Only egress ports on 7600-3 will report error of the stream

03 7600

Documents

cisco systems

cisco confidential

hardware support

fec wanphy support

cxlgeneral feature support

es xt parity otn

operatorchassis support

processor support