Is there any way around limitation for several vlan-range on l2transport subinterface?
RP/0/RP0/CPU0:NCS540-01(config-subif)#show configuration failed Tue Feb 25 10:41:36.128 GMT-3 !! APPLY ERRORS: This configuration was accepted by the system, !! but errors occurred when the system attempted to make the !! configuration operational. The individual errors for each !! failed configuration command can be found below. These errors !! will cause an inconsistency between the system's running !! configuration and its operational state, which may be addressed !! by using the 'no' form of the command to remove it from the !! running configuration.
interface TenGigE0/0/0/20.100 l2transport encapsulation dot1q 100-200 , 300-400 !!% 'VLAN EA' detected the 'warning' condition 'The platform DLL returned the following error': Operation not supported ! end
RP/0/RP0/CPU0:NCS540-01#sh run int te0/0/0/20.100 Tue Feb 25 11:42:14.842 GMT-3 interface TenGigE0/0/0/20.100 l2transport encapsulation dot1q 100-200 , 300-400 !
RP/0/RP0/CPU0:NCS540-01#sh run int te0/0/0/20.200 Tue Feb 25 11:42:18.060 GMT-3 interface TenGigE0/0/0/20.200 l2transport encapsulation dot1q 500-600 !
RP/0/RP0/CPU0:NCS540-01#show ethernet infra internal ea subs tenGigE 0/0/0/20.100 Tue Feb 25 11:40:54.301 GMT-3 Interface: TenGigE0/0/0/20.100 (0x457a) Interface is not Up Normal flags: None No pending work flags Error flags: HW_PLCY_ERR: Platform policy update error Parent Interface: TenGigE0/0/0/20 (0x130) Plat AIB AAI: None provided Policy (internal, version=0, size=80) ether_if_type: PHY_L2_SUB interface_ready: 0 is_l2: 1 not provisioned MTU: 1500 sub.parent: 0x00000130 sub.admin_up: 0 sub.efp_filtering: 0 EFP MATCH: (none) EFP REWRITE: (none)
RP/0/RP0/CPU0:NCS540-01#show ethernet infra internal ea subs tenGigE 0/0/0/20.200 Tue Feb 25 11:40:56.351 GMT-3 Interface: TenGigE0/0/0/20.200 (0x45aa) Interface is not Up Normal flags: None No pending work flags No error flags Parent Interface: TenGigE0/0/0/20 (0x130) Plat AIB AAI: None provided Policy (internal, version=0, size=92) ether_if_type: PHY_L2_SUB interface_ready: 0 is_l2: 1 not provisioned MTU: 1500 sub.parent: 0x00000130 sub.admin_up: 0 sub.efp_filtering: 0 EFP MATCH: encap dot1q 500-600 EFP REWRITE: (none)
L2VPN and Ethernet Services Configuration Guide for Cisco NCS 540 Series Routers, IOS XR Release 7.0.x
Restrictions and Limitations To configure VLAN sub-interface, the following restrictions are applicable. • For double tagged packet, the VLAN range is supported only on the inner tag. • VLAN list is not supported. VLANs separated by comma is called a VLAN list. See the example below. Router(config)#interface tenGigE 0/0/0/2.0 l2transport Router(config-subif)#encapsulation dot1q 1,2 >> VLAN range with comma Router(config-subif)#commit • If 0x9100/0x9200 is configured as tunneling ether-type, then dot1ad (0x88a8) encapsulation is not supported. • If any sub-interface is already configured under a main interface, modifying the tunneling ether-type is not supported. • You can program a maximum number of 16 virtual MAC addresses on your router.
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...
BGP flowspec in a nutshell is a feature that will allow you to receive IPv4/IPv6 traffic flow specification (source X, destination Y, protocol UDP, source port A .. etc) and actions that need to be taken on that traffic (...