Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1417
Views
0
Helpful
13
Replies

EtherSwitch configuration on Cisco 2951 / CISCO Etherswitch SM-ES3G-16-P

alienkidmj12
Level 1
Level 1

‎08-11-2019 02:33 AM - edited ‎08-11-2019 02:34 AM

i am trying to configure an internal trunk between router and etherswitch

 

however, i cannot get any traffic to flow, at the moment i am using an external cable from router to switch,

 

also is there some routing commands i should use ? or should it be automatic ?

 

im using a cisco 2951 router and CISCO Etherswitch SM-ES3G-16-P

 

similar issue to https://community.cisco.com/t5/switching/etherswitch-configuration-on-cisco-2921/m-p/3906547#M470980

 

 

######################################

Router config

######################################

interface GigabitEthernet2/0
ip address 1.0.0.1 255.255.255.0
!
interface GigabitEthernet2/0.1
encapsulation dot1Q 1 native
bridge-group 1
!
interface GigabitEthernet2/0.10
encapsulation dot1Q 10
bridge-group 10
!
interface GigabitEthernet2/0.20
encapsulation dot1Q 20
bridge-group 20
!
interface GigabitEthernet2/0.30
encapsulation dot1Q 30
bridge-group 30

 


interface BVI1
mac-address 5c83.8f03.7dc4
mtu 9014
ip address 192.168.0.102 255.255.255.0
ip virtual-reassembly in
!
interface BVI10
mac-address 5c83.8f03.7dc5
mtu 9014
ip address 192.168.1.102 255.255.255.0
ip virtual-reassembly in
!
interface BVI20
mac-address 5c83.8f03.7dc6
mtu 9014
ip address 192.168.2.102 255.255.255.0
ip virtual-reassembly in
!
interface BVI30
mac-address 5c83.8f03.7dc7
mtu 9014
ip address 192.168.3.102 255.255.255.0
ip virtual-reassembly in

 

 

######################################

Etherswitch Module config

######################################

 

interface GigabitEthernet0/17
description <== INTERNAL_TRUNK_TO_ROUTER_G1/1--DO_NOT_SHUTDOWN ==>
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,10,20,30
switchport mode trunk

interface Vlan1
ip address 192.168.0.103 255.255.255.0
!
interface Vlan10
ip address 192.168.1.103 255.255.255.0
!
interface Vlan20
ip address 192.168.2.103 255.255.255.0
!
interface Vlan30
ip address 192.168.3.103 255.255.255.0

Labels:
0 Helpful
13 Replies 13

marce1000
VIP
VIP

‎08-11-2019 02:43 AM

 

 -  What happens when the trunk is trying to get established and/or are the ports trunking or not ? At the same time post the output of show logging on both platforms when the trunk is being tried.

 M.



-- ' 'Good body every evening' ' this sentence was once spotted on a logo at the entrance of a Weight Watchers Club !
0 Helpful

alienkidmj12
Level 1
Level 1
In response to marce1000

‎08-11-2019 03:34 AM

how do i check to see trunk being established ?

nothing really much to go on in logging

bifrost-cisco2951sw#show logging
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.



No Inactive Message Discriminator.


Console logging: level debugging, 239 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 239 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
File logging: disabled
Persistent logging: disabled

No active filter modules.

Trap logging: level informational, 210 message lines logged
Logging Source-Interface: VRF Name:

Log Buffer (4096 bytes):
in configuration mode
Aug 11 00:10:51.494: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to down
Aug 11 00:10:52.500: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
Aug 11 00:13:44.450: %SYS-5-CONFIG_I: Configured from console by console
Aug 11 00:16:42.171: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
Aug 11 00:16:42.171: DHCPD: interface GigabitEthernet0/2 coming up
Aug 11 00:16:43.178: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to up
Aug 11 00:21:39.488: %SYS-5-CONFIG_I: Configured from console by console
Aug 11 00:22:41.136: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to down
Aug 11 00:22:42.143: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
Aug 11 00:25:00.630: %SYS-5-CONFIG_I: Configured from console by console
Aug 11 00:33:26.170: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to up
Aug 11 00:33:26.170: DHCPD: interface GigabitEthernet0/2 coming up
Aug 11 00:33:27.176: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to up
Aug 11 00:41:10.941: %SYS-5-CONFIG_I: Configured from console by sivesrutherfordd on vty3 (192.168.0.1)
Aug 11 00:41:40.032: %SYS-5-CONFIG_I: Configured from console by sivesrutherfordd on vty3 (192.168.0.1)
Aug 11 00:43:42.431: %SYS-5-CONFIG_I: Configured from console by console
Aug 11 00:43:45.316: %ADJ-3-RESOLVE_REQ: Adj resolve request: Failed to resolve 192.168.0.100 Vlan1
Aug 11 00:44:38.995: %SYS-5-CONFIG_I: Configured from console by sivesrutherfordd on vty3 (192.168.0.1)
Aug 11 00:49:53.517: %SYS-5-CONFIG_I: Configured from console by sivesrutherfordd on vty3 (192.168.0.1)
Aug 11 08:45:02.100: %SYS-5-CONFIG_I: Configured from console by sivesrutherfordd on vty3 (192.168.0.1)
Aug 11 08:51:05.218: DHCPD: interface Vlan10 coming up
Aug 11 08:51:05.218: DHCPD: interface Vlan10 coming up
Aug 11 08:51:07.223: %LINK-3-UPDOWN: Interface Vlan10, changed state to up
Aug 11 08:51:07.231: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to up
Aug 11 08:51:13.925: DHCPD: IP address change on interface Vlan10
Aug 11 08:51:19.856: DHCPD: interface Vlan20 coming up
Aug 11 08:51:19.856: DHCPD: interface Vlan20 coming up
Aug 11 08:51:21.861: %LINK-3-UPDOWN: Interface Vlan20, changed state to up
Aug 11 08:51:21.869: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan20, changed state to up
Aug 11 08:51:26.760: DHCPD: IP address change on interface Vlan20
Aug 11 08:51:32.145: DHCPD: interface Vlan30 coming up
Aug 11 08:51:34.150: %LINK-3-UPDOWN: Interface Vlan30, changed state to down
Aug 11 08:51:35.996: DHCPD: IP address change on interface Vlan30
Aug 11 08:51:38.454: %SYS-5-CONFIG_I: Configured from console by sivesrutherfordd on vty3 (192.168.0.1)
Aug 11 08:56:30.973: %SYS-5-CONFIG_I: Configured from console by sivesrutherfordd on vty3 (192.168.0.1)
Aug 11 08:57:04.074: %SYS-5-CONFIG_I: Configured from console by sivesrutherfordd on vty3 (192.168.0.1)
bifrost-cisco2951sw#

theres nothing in the logs from 2951 to be honest.

thanks

dave


0 Helpful

alienkidmj12
Level 1
Level 1
In response to alienkidmj12

‎08-11-2019 03:40 AM

bifrost-cisco2951#show interface trunk

Port Mode Encapsulation Status Native vlan
Gi2/1 on 802.1q trunking 1

Port Vlans allowed on trunk
Gi2/1 1-2,10,20,1002-1005

Port Vlans allowed and active in management domain
Gi2/1 1-2

Port Vlans in spanning tree forwarding state and not pruned
Gi2/1 1-2
bifrost-cisco2951#

 

 

 

bifrost-cisco2951sw#show interface trunk

Port Mode Encapsulation Status Native vlan
Gi0/1 on 802.1q trunking 1
Gi0/17 on 802.1q trunking 1
Gi0/18 on 802.1q trunking 1

Port Vlans allowed on trunk
Gi0/1 1,10,20,30
Gi0/17 1,10,20,30
Gi0/18 4

Port Vlans allowed and active in management domain
Gi0/1 1,10,20
Gi0/17 1,10,20
Gi0/18 none

Port Vlans in spanning tree forwarding state and not pruned
Gi0/1 1,10,20
Gi0/17 1,10,20
Gi0/18 none
bifrost-cisco2951sw#

 

0 Helpful

alienkidmj12
Level 1
Level 1
In response to alienkidmj12

‎08-11-2019 03:43 AM - edited ‎08-11-2019 03:58 AM

bifrost-cisco2951sw#show int GigabitEthernet0/17 switchport
Name: Gi0/17
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Administrative Native VLAN tagging: enabled
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk Native VLAN tagging: enabled
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk associations: none
Administrative private-vlan trunk mappings: none
Operational private-vlan: none
Trunking VLANs Enabled: 1,10,20,30
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL

Protected: false
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled
Appliance trust: none
bifrost-cisco2951sw#

 

 

 

bifrost-cisco2951sw#show int GigabitEthernet0/17 trunk

Port Mode Encapsulation Status Native vlan
Gi0/17 on 802.1q trunking 1

Port Vlans allowed on trunk
Gi0/17 1,10,20,30

Port Vlans allowed and active in management domain
Gi0/17 1,10,20

Port Vlans in spanning tree forwarding state and not pruned
Gi0/17 1,10,20

bifrost-cisco2951sw#

 

 

 

bifrost-cisco2951#show int GigabitEthernet2/0 trunk
bifrost-cisco2951#

0 Helpful

alienkidmj12
Level 1
Level 1
In response to alienkidmj12

‎08-11-2019 03:44 AM

would spanning tree need to be enabled for this ?

0 Helpful

alienkidmj12
Level 1
Level 1
In response to alienkidmj12

‎08-11-2019 05:41 AM

Can you give me some help here please.

0 Helpful

marce1000
VIP
VIP
In response to alienkidmj12

‎08-11-2019 05:57 AM

 

>how do i check to see trunk being established ?

  - Just and only show the output of show int Gix/y status on both platforms.

 M.



-- ' 'Good body every evening' ' this sentence was once spotted on a logo at the entrance of a Weight Watchers Club !
0 Helpful

alienkidmj12
Level 1
Level 1
In response to marce1000

‎08-11-2019 06:48 AM

There is no status option available on the 2951 router

 

******** SWITCH

bifrost-cisco2951sw#show int GigabitEthernet0/17 status

Port Name Status Vlan Duplex Speed Type
Gi0/17 <== INTERNAL_TRUNK connected trunk full 1000 1000BaseX
bifrost-cisco2951sw#

 

******** ROUTER

bifrost-cisco2951#show int GigabitEthernet2/0 status
^
% Invalid input detected at '^' marker.

bifrost-cisco2951#

 

bifrost-cisco2951#show int GigabitEthernet2/0 summary

*: interface is up
IHQ: pkts in input hold queue IQD: pkts dropped from input queue
OHQ: pkts in output hold queue OQD: pkts dropped from output queue
RXBS: rx rate (bits/sec) RXPS: rx rate (pkts/sec)
TXBS: tx rate (bits/sec) TXPS: tx rate (pkts/sec)
TRTL: throttle count

Interface IHQ IQD OHQ OQD RXBS RXPS TXBS TXPS TRTL
-----------------------------------------------------------------------------------------------------------------
* GigabitEthernet2/0 0 0 0 0 0 0 3000 5 0
* GigabitEthernet2/0.1 - - - - - - - - -
* GigabitEthernet2/0.10 - - - - - - - - -
* GigabitEthernet2/0.20 - - - - - - - - -
* GigabitEthernet2/0.30 - - - - - - - - -
NOTE:No separate counters are maintained for subinterfacesbifrost-cisco2951#show int GigabitEthernet2/0 trunk
bifrost-cisco2951#

0 Helpful

alienkidmj12
Level 1
Level 1
In response to alienkidmj12

‎08-11-2019 06:54 AM

i did notice that the other internal interface can be used with status

 

bifrost-cisco2951#show int GigabitEthernet2/1 status

Port Name Status Vlan Duplex Speed Type
Gi2/1 <== Internal switc connected trunk auto auto 10/100BaseTX
bifrost-cisco2951#

 

bizaire, maybe GigabitEthernet2/0 is not configured correctly to allow status option.

0 Helpful

alienkidmj12
Level 1
Level 1
In response to alienkidmj12

‎08-11-2019 06:57 AM - edited ‎08-11-2019 06:58 AM

two interfaces on router, and two on switch - i believe they speak to each other, i wanted to use the first interface for comms.

 

ROUTER

#############################

interface GigabitEthernet2/0
ip address 1.0.0.1 255.255.255.0
!
interface GigabitEthernet2/0.1
encapsulation dot1Q 1 native
bridge-group 1
!
interface GigabitEthernet2/0.10
encapsulation dot1Q 10
bridge-group 10
!
interface GigabitEthernet2/0.20
encapsulation dot1Q 20
bridge-group 20
!
interface GigabitEthernet2/0.30
encapsulation dot1Q 30
bridge-group 30
!
interface GigabitEthernet2/1
description <== Internal switch interface connected to Service Module ==>
switchport trunk allowed vlan 1,2,10,20,1002-1005
switchport mode trunk
no ip address

 

 

SWITCH

########################

interface GigabitEthernet0/17
description <== INTERNAL_TRUNK_TO_ROUTER_G1/1--DO_NOT_SHUTDOWN ==>
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,10,20,30
switchport mode trunk
switchport nonegotiate
!
interface GigabitEthernet0/18
description <== MUST_BE_ENABLED_TO_PROVIDE_POWER_TO_IP_PHONES ==>
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 4
switchport mode trunk

0 Helpful

alienkidmj12
Level 1
Level 1
In response to alienkidmj12

‎08-11-2019 09:16 AM

bifrost-cisco2951sw#show int GigabitEthernet0/18 status

Port Name Status Vlan Duplex Speed Type
Gi0/18 <== MUST_BE_ENABLE connected trunk full 1000 1000BaseX
bifrost-cisco2951sw#

 

bifrost-cisco2951#show int GigabitEthernet2/1 status

Port Name Status Vlan Duplex Speed Type
Gi2/1 <== Internal switc connected trunk auto auto 10/100BaseTX
bifrost-cisco2951#

 

managed to fix it i think, but there is a speed mismatch

 

 

0 Helpful

marce1000
VIP
VIP
In response to alienkidmj12

‎08-12-2019 12:27 AM

 

 - How did you fix it ? Why do you think there is a speed mismatch ?

  M.



-- ' 'Good body every evening' ' this sentence was once spotted on a logo at the entrance of a Weight Watchers Club !
0 Helpful

paul driver
VIP
VIP
In response to alienkidmj12

‎08-12-2019 02:03 AM - edited ‎08-12-2019 02:04 AM

Hello

Glad you fixed this problem just would like to point out for future ref.

interface GigabitEthernet2/0  <---- by default  this would be your native vlan 1
ip address 1.0.0.1 255.255.255.0
!
interface GigabitEthernet2/0.1
encapsulation dot1Q 1 native
bridge-group 1

interface GigabitEthernet2/0.10
encapsulation dot1Q 10
bridge-group 10<----- IRB isn't required

interface GigabitEthernet2/0.20
encapsulation dot1Q 20
bridge-group 20<----- IRB isn't required

interface GigabitEthernet2/0.30
encapsulation dot1Q 30
bridge-group 30<----- IRB isn't required

 


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul
0 Helpful
Customers Also Viewed These Support Documents
Review Cisco Networking products for a $25 gift card