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

9348 Mgmt mac not showing up in it's own mac address table

JimFranklin6775
Level 1
Level 1

Hi...I have the mgmt (gi0/0) port of a 9348 plugged into an access port of itself, but the mac isn't showing up in the table (in any vlan). I also have a 3560's Mgmt port plugged into the 9348, and it does show up. 

Both Mgmt ports are in the Mgmt-vrf vrf on their respective switches, and the access ports on the 3650 are in the same vlan (199, our mgmt vlan). 

I have repeated this configuration in 4 closets so it isn't an isolated issue. Is there something preventing a switch's own mac from appearing in the table, even though it's in a different vrf? Does the 3650 not understand the 9348? For the curious- I'm using this topology to put mgmt traffic on vlan 199 and trunking it to our core and then to an OOB Meraki MX, in case the main routing goes down in the building. We don't have the cabling to run it to the core separately.

 

Below are some config details. Thanks for any light you can shed on this conundrum.

 

jim

 

9348:

CSA01#sh run int gi0/0

interface GigabitEthernet0/0
vrf forwarding Mgmt-vrf
ip address 198.18.113.12 255.255.255.0
end

 

CSA01#sh int gi0/0
GigabitEthernet0/0 is up, line protocol is up
Hardware is RP management port, address is d4ad.7181.0e80 (bia d4ad.7181.0e80)
Internet address is 198.18.113.12/24

 

---------------------------
3650:

CSS01#sh run int gi0/0

interface GigabitEthernet0/0
vrf forwarding Mgmt-vrf
ip address 198.18.113.13 255.255.255.0
end

 

CSS01#sh int gi0/0
GigabitEthernet0/0 is up, line protocol is up
Hardware is RP management port, address is 843d.c691.b980 (bia 843d.c691.b980)
Internet address is 198.18.113.13/24

 

CSS01#sh run int gi1/0/13
interface GigabitEthernet1/0/13
switchport access vlan 199
switchport mode access
spanning-tree portfast

CSS01#sh run int gi1/0/14
interface GigabitEthernet1/0/14
switchport access vlan 199
switchport mode access
spanning-tree portfast

 

CSS01#sh vlan | in 199
199 OOB-vlan active Gi1/0/13, Gi1/0/14

 

CSS01#sh mac address-table | in 199
199 00a3.d19e.9689 DYNAMIC Te1/1/1
199 9818.886c.3820 DYNAMIC Te1/1/1
199 d4ad.7181.0e80 DYNAMIC Gi1/0/14

 

 

 

 

1 Accepted Solution

Accepted Solutions

Reza Sharifi
Hall of Fame
Hall of Fame

Jim,

 

When you connect an out-of-band management port (gi0/0) to the switch itself, you are basically looping the switch ports together even though the OOB port is in a different VRF. This may have worked, if say gi0/0 was in a different VDC than gi1/0/13 but not in a case of VRF, I have never seen it work and not sure if it is possible at all. OOB port should connect to a OOB switch.

If you don't have the cabling in place to run the 9348 directly to the OOB switch, than you may have to use an in-band management solution where you simply create vlan 199 on the switch and trunk it to the core and finally OOB switch. 

HTH

 

View solution in original post

4 Replies 4

balaji.bandi
Hall of Fame
Hall of Fame

what is the out put of ( can you post)

 

CSS01#sh mac address-table

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Here you go...

 

CSS01#sh mac address-table
Mac Address Table
-------------------------------------------

Vlan Mac Address Type Ports
---- ----------- -------- -----
All 0100.0ccc.cccc STATIC CPU
All 0100.0ccc.cccd STATIC CPU
All 0180.c200.0000 STATIC CPU
All 0180.c200.0001 STATIC CPU
All 0180.c200.0002 STATIC CPU
All 0180.c200.0003 STATIC CPU
All 0180.c200.0004 STATIC CPU
All 0180.c200.0005 STATIC CPU
All 0180.c200.0006 STATIC CPU
All 0180.c200.0007 STATIC CPU
All 0180.c200.0008 STATIC CPU
All 0180.c200.0009 STATIC CPU
All 0180.c200.000a STATIC CPU
All 0180.c200.000b STATIC CPU
All 0180.c200.000c STATIC CPU
All 0180.c200.000d STATIC CPU
All 0180.c200.000e STATIC CPU
All 0180.c200.000f STATIC CPU
All 0180.c200.0010 STATIC CPU
All 0180.c200.0021 STATIC CPU
All ffff.ffff.ffff STATIC CPU
10 0000.5e00.0106 DYNAMIC Te1/1/1
10 000f.ff1b.f58a DYNAMIC Te1/1/1
10 000f.ff81.36e3 DYNAMIC Te1/1/1
10 0010.7fbb.44c9 DYNAMIC Te1/1/1
10 0010.7fc7.5bdc DYNAMIC Te1/1/1
10 0010.7fc7.8210 DYNAMIC Te1/1/1
10 0010.7fc9.2d3f DYNAMIC Te1/1/1
10 0019.92f9.4ec1 DYNAMIC Te1/1/1
10 00a0.c890.e78d DYNAMIC Te1/1/1
10 00a2.ee6c.47c6 STATIC Vl10
10 00a3.d19e.9688 DYNAMIC Te1/1/1
10 00a3.d19e.96c6 DYNAMIC Te1/1/1
10 0c8d.dbb3.eafe DYNAMIC Te1/1/1
10 0c8d.dbb3.eb3a DYNAMIC Te1/0/19
10 0c8d.dbb3.eb4c DYNAMIC Te1/0/20
10 0c8d.dbb3.edbc DYNAMIC Te1/0/18
10 0c8d.dbb3.ee36 DYNAMIC Te1/0/17
10 0c8d.dbb3.ee84 DYNAMIC Te1/1/1
10 1c1b.0d27.2d80 DYNAMIC Te1/1/1
10 1c7d.221b.9956 DYNAMIC Te1/1/1
10 1c7d.221b.9da1 DYNAMIC Te1/1/1
10 6416.7f12.ebec DYNAMIC Gi1/0/10
10 7845.0104.fb4f DYNAMIC Te1/1/1
10 7845.0105.5575 DYNAMIC Te1/1/1
10 8815.4460.8890 DYNAMIC Te1/1/1
10 8815.4460.8bb6 DYNAMIC Te1/1/1
10 8815.4460.8dda DYNAMIC Te1/1/1
10 8815.4460.8de6 DYNAMIC Te1/1/1
10 8815.4460.8e78 DYNAMIC Te1/1/1
10 8815.4460.8e88 DYNAMIC Te1/1/1
10 8815.4460.8e94 DYNAMIC Te1/1/1
10 8815.4460.8e9a DYNAMIC Te1/1/1
10 8815.4460.8f84 DYNAMIC Te1/1/1
10 8815.4460.8ffc DYNAMIC Te1/1/1
10 8815.4460.9002 DYNAMIC Te1/1/1
10 8815.4460.9044 DYNAMIC Te1/1/1
10 8815.4460.92d2 DYNAMIC Te1/1/1
10 8815.4460.970a DYNAMIC Te1/1/1
10 8815.4460.fbf0 DYNAMIC Te1/1/1
10 8815.4460.fca8 DYNAMIC Te1/1/1
10 8815.4460.ff46 DYNAMIC Te1/1/1
10 8cdc.d43e.a1c6 DYNAMIC Te1/1/1
10 9457.a514.2938 DYNAMIC Te1/1/1
10 9c93.4e64.6cdd DYNAMIC Te1/1/1
10 9c93.4e64.6cde DYNAMIC Te1/1/1
10 9c93.4e65.03cb DYNAMIC Te1/1/1
10 9c93.4e97.0a87 DYNAMIC Te1/1/1
10 9c93.4e97.2003 DYNAMIC Te1/1/1
10 9c93.4e97.3b24 DYNAMIC Te1/1/1
10 a036.9fe9.79ac DYNAMIC Te1/1/1
10 b00c.d151.a330 DYNAMIC Te1/1/1
10 cc3d.820c.891f DYNAMIC Te1/1/1
10 d481.d756.1d14 DYNAMIC Te1/1/1
10 ec8e.b5be.eb05 DYNAMIC Te1/1/1
10 ec8e.b5be.eb06 DYNAMIC Te1/1/1
99 00a2.ee6c.47dd STATIC Vl99
99 00a3.d19e.9688 DYNAMIC Te1/1/1
99 00a3.d19e.96dd DYNAMIC Te1/1/1
99 00c0.b759.c070 DYNAMIC Te1/1/1
99 00c0.b759.c0ac DYNAMIC Te1/1/1
99 2829.860f.1629 DYNAMIC Gi1/0/7
99 2829.8617.40a9 DYNAMIC Te1/1/1
99 2829.8624.6e1d DYNAMIC Te1/1/1
100 0010.491a.dbcd DYNAMIC Te1/1/1
100 0010.491d.6d37 DYNAMIC Te1/1/1
100 0010.491e.0ad8 DYNAMIC Te1/1/1
100 0010.491e.148e DYNAMIC Te1/1/1
100 0010.492e.a4b6 DYNAMIC Te1/1/1
100 0010.494e.d385 DYNAMIC Te1/1/1
100 0010.4955.7c5c DYNAMIC Te1/1/1
100 00a3.d19e.9688 DYNAMIC Te1/1/1
100 0cc4.7ab5.56cd DYNAMIC Te1/1/1
100 14ae.db05.8ef7 DYNAMIC Te1/1/1
100 14ae.db10.b4bf DYNAMIC Te1/1/1
100 14ae.db11.338a DYNAMIC Te1/1/1
100 6416.7f12.e7d7 DYNAMIC Te1/1/1
2 0012.ea03.f7af DYNAMIC Te1/1/1
2 00a3.d19e.9688 DYNAMIC Te1/1/1
80 00a3.d19e.9688 DYNAMIC Te1/1/1
20 00a3.d19e.9688 DYNAMIC Te1/1/1
199 00a3.d19e.9688 DYNAMIC Te1/1/1
199 7035.096d.8480 DYNAMIC Gi1/0/14
199 9818.886c.3820 DYNAMIC Te1/1/1
Total Mac Addresses for this criterion: 104

Reza Sharifi
Hall of Fame
Hall of Fame

Jim,

 

When you connect an out-of-band management port (gi0/0) to the switch itself, you are basically looping the switch ports together even though the OOB port is in a different VRF. This may have worked, if say gi0/0 was in a different VDC than gi1/0/13 but not in a case of VRF, I have never seen it work and not sure if it is possible at all. OOB port should connect to a OOB switch.

If you don't have the cabling in place to run the 9348 directly to the OOB switch, than you may have to use an in-band management solution where you simply create vlan 199 on the switch and trunk it to the core and finally OOB switch. 

HTH

 

Thanks Reza. This makes sense even though I wished they'd made a loop exception. I can always just wire each Mgmt port to the other switch's access port, but I wanted to avoid a non-desktop vlan on the desktop switch. Ah well.

 

jim

Review Cisco Networking for a $25 gift card