we recieve a number of downstream hand-offs that are delivered as SVID/CVID ccts. There are mixture of data, and VOIP subscribers, the only way to tell the different type of subscribers is that the all voip services are marked as cos 4. All data subscribers are marked cos 0. I have no control over the SVID/CVID mix, and there is no "pattern" so I cannot enter ranges.
I am wanting to deliver each subscriber type to a different bridge-domain then use xconnect to forward these so ultimately i have one bridge-domain with VOIP services, and one with data services.
on the me3600x I tried the following:
switchport trunk allowed vlan none
switchport mode trunk
service instance 950 ethernet
encapsulation dot1q 1-4096 secondary 1-4096
service instance 951 ethernet
encapsulation dot1q 1-4096 secondary 1-4096 cos 4
This seemed to work with cos 4 traffic being sent to a differnet bridge-domain than other traffic, however when i try to apply this config to more than 4 interfaces (8 bridge-domain members) i get a "command rejected" error when i enter the "encapsulation dot1q" command. "Encapsulation deafult" is still accepted though.
can any one explain to me why there is this limitation, or if there is any way around it, or any other way to do what i am trying to do?
I replicated your setup in the lab and it appears the problematic line causing this interesting limitation is the “encapsulation dot1q any second-dot1q any” under the “service instance 950”
Since you are not really interested in the second tag value you can leave it out of the equation using just “encapsulation dot1q any” –to match any frame (not matching any more specific service instance rules) with at least one 802.1q tag or you can use “encapsulation default” –to match any frame (not matching any more specific service instance rules)
Some of you may have watched the session at Cisco’s first all-digital Cisco Live and I hope you found it helpful. This is the first in a series of companion blogs that will later cover in more detail the topics discussed in the session today. ...
CCO documentation lists out the ability to do a password recovery for eXR with a ZTP/PXE boot.
One can also perform the operation manually, like a "turboboot" for classic XR in this facinity.
this procedure will wipe out the complete system and install a...
Below is a link to a video showing how to analyze traceroute output in L3VPN and look up CEF forwarding and MPLS/TE/SR/SR-TE forwarding for labels through a domain. Some basic examples of traffic engineering are used but the concepts lend the...
This document summarises various health checks that can be done on a Cisco VIM pod.
Cloud sanity checks the health status of network, storage and various openstack infrastructure components like mariadb, rabbitmq etc....
The following pre-requisites are necessary for the migration from RSP440 to RSP880-LT to be successful.
Make sure that you have console access to the router.
Verify that the system is running a minimum o...