cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1884
Views
0
Helpful
4
Replies

ES20 line-card L3 question

bbuhlman
Level 1
Level 1

I've been using SIP/SPA 2x1GE with this config for connecting customers:

interface GigabitEthernet2/1/0.64

description edge1

bandwidth 100000

encapsulation dot1Q 64

ip address 192.168.2.1 255.255.255.252

ip verify unicast source reachable-via rx allow-default

ip flow ingress

logging event subif-link-status

How do I do the equivalent on the ES20? I'm a newb with this line-card and I don't know what best practice is...

Thanks in advance,

Bill

4 Replies 4

Nagendra Kumar Nainar
Cisco Employee
Cisco Employee

Hi Bill,

AFAIK, ES20 card supports L3 sub interface. You can create similar subinterafce on ES20 ports and apply your L3 configs.

Are you facing any issue in enabling subinterface on ES20 card?.

-Nagendra

Hi Nagendra, I've tried all these configs below but I've not been able to bring the circuit up. When I enable a subinterface and try to use encap dot1q 3 I get an error:

cccoe-edge(config-subif)#encap dot1q 3

Command rejected: VLAN 3 not available 

So I've went another direction and tried the configs below:

interface GigabitEthernet7/0/5  description ASE #1 

switchport 

switchport trunk allowed vlan 3 

switchport mode trunk 

speed nonegotiate 

no mls qos trust 

no cdp enable 

ethernet dot1ad nni

interface Vlan3  ip address 192.168.4.177 255.255.255.252

  -----------------------------------------

interface GigabitEthernet7/0/5 

description ASE1

bandwidth 1000000 

ip address 192.168.4.177 255.255.255.252 

ip verify unicast source reachable-via rx allow-default 

ip flow ingress 

speed nonegotiate

vlan-id dot1q 3  

exit-vlan-config  ! 

no mls qos trust 

no cdp enable end 

----------------------------------------------------

You must remove the Vlan from the vlan database .(No vlan x   and no interface  vlan x)

After that you can add the subinterface

Regards

ilir

yes, that's it!!

vlan 3 already exist in vlan database while you need it for L3 subinterface. You can not have the same vlan in the vlan db and on a L3 link.

Riccardo