06-20-2017 07:07 AM - edited 03-08-2019 11:02 AM
Dear all,
Can anyone help in this issue?
PID: ISR4331/K9 , VID: V02, SN: FLM2044W2X6 , module: SM-X-ES3-24-P
Thank you in advance.
06-20-2017 12:30 PM
Hello,
apparently Ethernet-Internal1/0/0 maps to GigabitEthernet0/26 on the ESW. Either way, try the configuration below:
Router
spanning-tree extend system-id
no spanning-tree vlan 404
!
bridge-domain 1
bridge-domain 404
!
interface Ethernet-Internal1/0/0
no negotiation auto
service instance 1 ethernet
encapsulation dot1q 404
rewrite ingress tag pop 1 symmetric
!
interface BDI404
ip address 192.168.0.2 255.255.255.252
!
no cdp enable
!
*****
Switch module:
ip routing
!
system mtu routing 1500
!
license boot level ipservices
!
spanning-tree mode pvst
spanning-tree extend system-id
no spanning-tree vlan 404
!
interface GigabitEthernet0/2
switchport access vlan 404
switchport trunk encapsulation dot1q
switchport mode trunk
switchport protected
!
interface GigabitEthernet0/25
switchport trunk encapsulation dot1q
switchport mode trunk
switchport protected
!
interface GigabitEthernet0/26
switchport trunk vlan allowed 404
switchport mode trunk
!
vlan 404
!
interface Vlan1
!
interface Vlan404
ip address 192.168.0.1 255.255.255.252
!
ip route 0.0.0.0 0.0.0.0 192.168.0.2
06-22-2017 12:35 AM
Thank you Georg for your quick reply.
With this configuration I could test the communication between the module and the ISR4331 router; and it is working!
The main goal would be to let 2 routers talk via back-to-back connection (using the module SM-X as all the other ports of the routers are taken already)
I suspected that there was a problem between the card and the router first. But apparently this is not the case.
Basically the design what you have is:
ISR4331 SM-X-ES3-24-P port G2 --- <Nexus switches> --- ISR4331 SM-X-ES3-24-P port G2
One end should be 192.168.0.2 and the other .1 (/30)
Slight change in the very first configuration: on all the switches and switch modules :
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 404
switchport mode trunk
Have you ever met this kind of problem?
Could you please advise if the above setup could work with any alternative configuration template?
06-22-2017 01:02 AM
Hello,
so basically you want GigabitEthernet0/2 on each router configured with an IP address ? I'll have a look, I'll get back with you...
06-22-2017 01:40 AM
Hello,
The routed ports are taken so we would like to use the switch module.
The Nexus device is plugged onto G2 port of the SM-X-ES3-24-P module.
On the router as far as I know virtual interfaces must be used (BDI/SVI) for L3 communication.
This back-2-back connection will be used for iBGP; ISR1 must be able to ping ISR2.
The 2 ISRs are in different cities, and I have no visibility on the Nexus configuration/interconnection.
IOS verisons I tried:
isr4300-universalk9.03.16.01a.S.155-3.S1a-ext.SPA.bin
isr4300-universalk9.03.16.03.S.155-3.S3-ext.SPA.bin
(to exclude possible IOS related bugs)
Let me know if I missed some important information or if I was not clear while describing the issue.
Thank you in advance for your time and support,
06-22-2017 06:22 AM
Hello,
sorry for the delay.
How are both routers currently connected ? Can you post the configuration of the interface on the router that is connected to the router in the other city ?
06-29-2017 01:09 AM
Hi, I am sorry for the delay.
The good news are: The Back-2-Back connection is working now.
The bad news: unfortunately I am not sure what was the origin of the issue. It can be the interconnection between the 2 cities or the module just needed a reset. Probably both.
We did a switch module re-set, removed the related parts and re-configured the router and the built-in module exactly the same way as it was before.
Let me share with you the working configuration:
GigabitEthernet0/0/0 y.y.y.y YES NVRAM up up - LAN - towards customer
GigabitEthernet0/0/1 x.x.x.x YES NVRAM up up - WAN - towards PE
GigabitEthernet0/0/2 unassigned YES NVRAM down down - FW (reserved for future use)
Ethernet-Internal1/0/0 unassigned YES unset up up - B2B - to the router /other city
Ethernet-Internal1/0/1 unassigned YES unset up up
GigabitEthernet0 unassigned YES NVRAM down down
BDI404 192.168.0.1 YES manual up up - the other end is 192.168.0.2
router:
spanning-tree extend system-id
no spanning-tree vlan 1,404
!
bridge-domain 1
bridge-domain 404
!
!
vlan internal allocation policy ascending
!
!
interface Ethernet-Internal1/0/0
no negotiation auto
service instance 1 ethernet
encapsulation dot1q 1
rewrite ingress tag pop 1 symmetric
bridge-domain 1 split-horizon group 0
!
service instance 404 ethernet
encapsulation dot1q 404
rewrite ingress tag pop 1 symmetric
bridge-domain 404 split-horizon group 0
!
!
interface Ethernet-Internal1/0/1
no negotiation auto
switchport mode trunk
!
interface BDI404
ip address 192.168.0.1 255.255.255.252
no cdp enable
---
Module:
license boot level ipservices
!
spanning-tree mode pvst
spanning-tree extend system-id
no spanning-tree vlan 404
!
!
interface GigabitEthernet0/2
switchport access vlan 404
switchport trunk encapsulation dot1q
switchport mode trunk
!
!
interface GigabitEthernet0/25
description Trunk to host router
switchport trunk encapsulation dot1q
switchport mode trunk
switchport protected
!
interface GigabitEthernet0/26
description Trunk to host router
switchport trunk encapsulation dot1q
switchport mode trunk
switchport protected
!
interface Vlan1
no ip address
!
---
switch connected to G2
!
vlan 404
name TEST
end
!
interface GigabitEthernet2/2
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 404
switchport mode trunk
logging event link-status
load-interval 30
wrr-queue bandwidth 120 150 180
wrr-queue cos-map 1 1 0 1 2
wrr-queue cos-map 1 2 3
wrr-queue cos-map 2 1 4
wrr-queue cos-map 2 2 6 7
mls qos trust dscp
end
!
Thank you again for having a look at it, really appreciate it!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide