This week my Mobile Internet Odyssey comes back to Earth, grounded in a very specific technical concern for today’s Mobile Internet interworking – MEF 22 compliance
For those of you already intimately aware of MEF 22, let me share the punch line …
Cisco is an official member of Metro Ethernet Forum (MEF) and complies with the major recommendations of MEF for Mobile networks, including MEF 22
For those of you who may be wondering “What is MEF 22?” please read on.
"Carrier Ethernet for Mobile Backhaul Implementation Agreement (IA)", or MEF 22 was officially announced at Mobile World Congress in February 2009. Light Reading offers a nice summary of this technical specification in the Feb 13, 2009 article MEF Standardizes Backhaul
By offering a practical migration path to 3G and 4G services, while preserving legacy services revenue, the MEF 22 allows mobile service providers to take part in two rapidly expanding markets -- the delivery of high bandwidth mobile applications and Carrier Ethernet.
In layman’s terms, Cisco’s IP RAN Solution connects multiple vendor radios, with multiple vendor gateways, efficiently, reliably, and in compliance with best practices and standards. The solution leverages the latest and greatest benefits of Carrier Ethernet technology and design, including MEF 22 compliance. And the solution is already live. Live deployments allow Cisco to offer valuable lessons learned interoperating with all major mobile radio vendors, back to MEF.
For inquiries and clarifications of specific details related to MEF 22, please add your comments to this post and/or launch a Discussion in our Cisco Mobility Community.
Note: For the MEF aficionados, Cisco does not support MEF 8 nor plan to get support / certification for MEF 18 because MEF 18 relies on MEF 8 outdated circuit emulation technique over Ethernet, initially designed for transporting enterprise PBX traffic. Cisco uses IP MPLS and Pseudowires. The actual impairment tests in MEF 18 are almost identical to the one found in the IP/MPLS Forum test suite for IP MPLS 23, where the only difference between MEF8 , and a static MPLS Pseudowire is one byte in the ethertype encapsulation. There is no point in supporting MEF8 just to have a byte in the ethertype be set to a different value.
Hi, I executed upgrade in ASR9010 with RSP A9K-RSP440-TR and A9K-RSP880-SE, in the previous version (IOS XR 6.1.4 and IOS XR 5.3.3) When I showed the show redundancy the Redundancy node status was NSR-Ready, but with IOS XR 6.4.2 the status is: NSR-not-co...
Topology BriefThree isolated IGP domains AGG-A, AGG-B, CORE running ISIS level 2 onlySegment routing is enabled on all IGP domainsCORE10 (SRPCE) running BGP-LS all border routers to learn topology from all three domainsFor reachability between PE/PCC to S...
Hi team,My ASR 903 to start send message:%SYSHW-3-SYSHW_REG_WRITE: R0/0: emd: A register write operation has failed for device: CPU_I2C_Outlet_Temp_Sensor register: /sys/bus/i2c/drivers/max6654/10-0019/reg_configuration error: Input/output error. sys...
Hi, I am trying to use the configuration conversion inside the ASR9K to ASR9K-64 migration tools, but it prompts "Failed to get the publish date of the most recent NoX conversion tool on CCO.", How to solve it? Thank you. BR,Joe