Keith Bui
asked on
Edge switch problems cisco 2960
Hi,
Having problems with an edge switch not communication out through core switch. All others switches work fine.
Edge switch configuration: port 49 is connection to core switch
interface GigabitEthernet1/0/49
description Link to Core bkcswp01
switchport mode trunk
switchport nonegotiate
!
interface GigabitEthernet1/0/50
description Link to Core bkcswp02
switchport mode trunk
switchport nonegotiate
!
interface GigabitEthernet1/0/51
!
interface GigabitEthernet1/0/52
!
interface Vlan1
no ip address
!
interface Vlan900
ip address 10.194.70.12 255.255.255.0
!
interface Vlan990
ip address 10.192.0.51 255.255.255.0
!
ip default-gateway 10.194.2.5
__________________________ __________ __________ ____
traceroute shows that it is trying to go through 10.194.70.1, whilst traceroute with working switches going through 10.194.0.1.
On core i can see the edge switch with CDP nei command.
Core - show IP route:
Gateway of last resort is 10.194.2.1 to network 0.0.0.0
S* 0.0.0.0/0 [1/0] via 10.194.2.1
10.0.0.0/8 is variably subnetted, 40 subnets, 3 masks
C 10.194.0.0/24 is directly connected, Vlan990
L 10.194.0.1/32 is directly connected, Vlan990
C 10.194.2.0/29 is directly connected, TenGigabitEthernet5/14
L 10.194.2.5/32 is directly connected, TenGigabitEthernet5/14
C 10.194.6.0/24 is directly connected, Vlan130
L 10.194.6.1/32 is directly connected, Vlan130
C 10.194.10.0/24 is directly connected, Vlan10
L 10.194.10.1/32 is directly connected, Vlan10
C 10.194.11.0/24 is directly connected, Vlan11
L 10.194.11.1/32 is directly connected, Vlan11
C 10.194.12.0/24 is directly connected, Vlan12
L 10.194.12.1/32 is directly connected, Vlan12
C 10.194.13.0/24 is directly connected, Vlan13
L 10.194.13.1/32 is directly connected, Vlan13
C 10.194.14.0/24 is directly connected, Vlan14
L 10.194.14.1/32 is directly connected, Vlan14
C 10.194.15.0/24 is directly connected, Vlan15
L 10.194.15.1/32 is directly connected, Vlan15
C 10.194.16.0/24 is directly connected, Vlan16
L 10.194.16.1/32 is directly connected, Vlan16
C 10.194.17.0/24 is directly connected, Vlan17
L 10.194.17.1/32 is directly connected, Vlan17
C 10.194.18.0/24 is directly connected, Vlan18
L 10.194.18.1/32 is directly connected, Vlan18
C 10.194.70.0/24 is directly connected, Vlan900
L 10.194.70.1/32 is directly connected, Vlan900
C 10.194.90.0/24 is directly connected, Vlan90
L 10.194.90.1/32 is directly connected, Vlan90
C 10.194.91.0/24 is directly connected, Vlan91
L 10.194.91.1/32 is directly connected, Vlan91
C 10.194.92.0/24 is directly connected, Vlan92
L 10.194.92.1/32 is directly connected, Vlan92
C 10.194.100.0/24 is directly connected, Vlan100
L 10.194.100.1/32 is directly connected, Vlan100
C 10.194.110.0/24 is directly connected, Vlan110
L 10.194.110.1/32 is directly connected, Vlan110
C 10.194.120.0/24 is directly connected, Vlan120
L 10.194.120.1/32 is directly connected, Vlan120
C 10.194.121.0/24 is directly connected, Vlan121
L 10.194.121.1/32 is directly connected, Vlan121
Thanks
Having problems with an edge switch not communication out through core switch. All others switches work fine.
Edge switch configuration: port 49 is connection to core switch
interface GigabitEthernet1/0/49
description Link to Core bkcswp01
switchport mode trunk
switchport nonegotiate
!
interface GigabitEthernet1/0/50
description Link to Core bkcswp02
switchport mode trunk
switchport nonegotiate
!
interface GigabitEthernet1/0/51
!
interface GigabitEthernet1/0/52
!
interface Vlan1
no ip address
!
interface Vlan900
ip address 10.194.70.12 255.255.255.0
!
interface Vlan990
ip address 10.192.0.51 255.255.255.0
!
ip default-gateway 10.194.2.5
__________________________
traceroute shows that it is trying to go through 10.194.70.1, whilst traceroute with working switches going through 10.194.0.1.
On core i can see the edge switch with CDP nei command.
Core - show IP route:
Gateway of last resort is 10.194.2.1 to network 0.0.0.0
S* 0.0.0.0/0 [1/0] via 10.194.2.1
10.0.0.0/8 is variably subnetted, 40 subnets, 3 masks
C 10.194.0.0/24 is directly connected, Vlan990
L 10.194.0.1/32 is directly connected, Vlan990
C 10.194.2.0/29 is directly connected, TenGigabitEthernet5/14
L 10.194.2.5/32 is directly connected, TenGigabitEthernet5/14
C 10.194.6.0/24 is directly connected, Vlan130
L 10.194.6.1/32 is directly connected, Vlan130
C 10.194.10.0/24 is directly connected, Vlan10
L 10.194.10.1/32 is directly connected, Vlan10
C 10.194.11.0/24 is directly connected, Vlan11
L 10.194.11.1/32 is directly connected, Vlan11
C 10.194.12.0/24 is directly connected, Vlan12
L 10.194.12.1/32 is directly connected, Vlan12
C 10.194.13.0/24 is directly connected, Vlan13
L 10.194.13.1/32 is directly connected, Vlan13
C 10.194.14.0/24 is directly connected, Vlan14
L 10.194.14.1/32 is directly connected, Vlan14
C 10.194.15.0/24 is directly connected, Vlan15
L 10.194.15.1/32 is directly connected, Vlan15
C 10.194.16.0/24 is directly connected, Vlan16
L 10.194.16.1/32 is directly connected, Vlan16
C 10.194.17.0/24 is directly connected, Vlan17
L 10.194.17.1/32 is directly connected, Vlan17
C 10.194.18.0/24 is directly connected, Vlan18
L 10.194.18.1/32 is directly connected, Vlan18
C 10.194.70.0/24 is directly connected, Vlan900
L 10.194.70.1/32 is directly connected, Vlan900
C 10.194.90.0/24 is directly connected, Vlan90
L 10.194.90.1/32 is directly connected, Vlan90
C 10.194.91.0/24 is directly connected, Vlan91
L 10.194.91.1/32 is directly connected, Vlan91
C 10.194.92.0/24 is directly connected, Vlan92
L 10.194.92.1/32 is directly connected, Vlan92
C 10.194.100.0/24 is directly connected, Vlan100
L 10.194.100.1/32 is directly connected, Vlan100
C 10.194.110.0/24 is directly connected, Vlan110
L 10.194.110.1/32 is directly connected, Vlan110
C 10.194.120.0/24 is directly connected, Vlan120
L 10.194.120.1/32 is directly connected, Vlan120
C 10.194.121.0/24 is directly connected, Vlan121
L 10.194.121.1/32 is directly connected, Vlan121
Thanks
Can you please advise what is 10.194.2.5. Is it a Router?
ASKER
it is the core switch interface to router.
i can see IP of the edge switch is 10.194.2.1
What is the IP of the core switch.
Can u run the following on both switch and post it.
Show VTP Status
Show Int Trunk
What is the IP of the core switch.
Can u run the following on both switch and post it.
Show VTP Status
Show Int Trunk
ASKER
The ip 10.194.2.1 is the router interface
Edge Switch:
BKGNDFCR2SW01#sh vtp status
VTP Version capable : 1 to 3
VTP version running : 3
VTP Domain Name : sjog_bk
VTP Pruning Mode : Disabled
VTP Traps Generation : Disabled
Device ID : f8a5.c581.b180
Feature VLAN:
--------------
VTP Operating Mode : Transparent
Number of existing VLANs : 28
Number of existing extended VLANs : 0
Maximum VLANs supported locally : 1005
Feature MST:
--------------
VTP Operating Mode : Transparent
Feature UNKNOWN:
--------------
VTP Operating Mode : Transparent
BKGNDFCR2SW01#
__________________________ __________ __________ __________ _________
Show Interface trunk:
BKGNDFCR2SW01#sh int trunk
Port Mode Encapsulation Status Native vlan
Gi1/0/49 on 802.1q trunking 1
Port Vlans allowed on trunk
Gi1/0/49 1-4094
Port Vlans allowed and active in management domain
Gi1/0/49 1-2,10-18,90-92,100,110,12 0-121,130, 900,990,99 2,997,999
Port Vlans in spanning tree forwarding state and not pruned
Gi1/0/49 1-2,10-18,90-92,100,110,12 0-121,130, 900,990,99 2,997,999
BKGNDFCR2SW01#
-------------------------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- --
Core switch
BKCSWP01#sh vtp status
VTP Version : 3 (capable)
VTP version running : 3
VTP Domain Name : sjog_bk
VTP Pruning Mode : Disabled (Operationally Disabled)
VTP Traps Generation : Enabled
Device ID : 002a.1061.ee40
Feature VLAN:
--------------
VTP Operating Mode : Transparent
Number of existing VLANs : 28
Number of existing extended VLANs : 0
Feature MST:
--------------
VTP Operating Mode : Transparent
Feature UNKNOWN:
--------------
VTP Operating Mode : Transparent
BKCSWP01#
__________________________ __________ __________ __________ __
Show interface trunk
BKCSWP01#sh int trunk
Port Mode Encapsulation Status Native vlan
Te1/13 on 802.1q trunking 1
Te1/14 on 802.1q trunking 1
Te1/15 on 802.1q trunking 1
Te1/16 on 802.1q trunking 1
Te2/9 on 802.1q trunking 1
Te2/10 on 802.1q trunking 1
Port Vlans allowed on trunk
Te1/13 1-4094
Te1/14 1-4094
Te1/15 1-4094
Te1/16 1-4094
Te2/9 1-4094
Te2/10 1-4094
Port Vlans allowed and active in management domain
Te1/13 1-2,10-18,90-92,100,110,12 0-121,130, 900,990,99 2,997,999
Te1/14 1-2,10-18,90-92,100,110,12 0-121,130, 900,990,99 2,997,999
Te1/15 1-2,10-18,90-92,100,110,12 0-121,130, 900,990,99 2,997,999
Te1/16 1-2,10-18,90-92,100,110,12 0-121,130, 900,990,99 2,997,999
Te2/9 1-2,10-18,90-92,100,110,12 0-121,130, 900,990,99 2,997,999
Port Vlans allowed and active in management domain
Te2/10 1-2,10-18,90-92,100,110,12 0-121,130, 900,990,99 2,997,999
Port Vlans in spanning tree forwarding state and not pruned
Te1/13 1-2,10-18,90-92,100,110,12 0-121,130, 900,990,99 2,997,999
Te1/14 1-2,10-18,90-92,100,110,12 0-121,130, 900,990,99 2,997,999
Te1/15 1-2,10-18,90-92,100,110,12 0-121,130, 900,990,99 2,997,999
Te1/16 1-2,10-18,90-92,100,110,12 0-121,130, 900,990,99 2,997,999
Te2/9 1-2,10-18,90-92,100,110,12 0-121,130, 900,990,99 2,997,999
Te2/10 1-2,10-18,90-92,100,110,12 0-121,130, 900,990,99 2,997,999
BKCSWP01#
Edge Switch:
BKGNDFCR2SW01#sh vtp status
VTP Version capable : 1 to 3
VTP version running : 3
VTP Domain Name : sjog_bk
VTP Pruning Mode : Disabled
VTP Traps Generation : Disabled
Device ID : f8a5.c581.b180
Feature VLAN:
--------------
VTP Operating Mode : Transparent
Number of existing VLANs : 28
Number of existing extended VLANs : 0
Maximum VLANs supported locally : 1005
Feature MST:
--------------
VTP Operating Mode : Transparent
Feature UNKNOWN:
--------------
VTP Operating Mode : Transparent
BKGNDFCR2SW01#
__________________________
Show Interface trunk:
BKGNDFCR2SW01#sh int trunk
Port Mode Encapsulation Status Native vlan
Gi1/0/49 on 802.1q trunking 1
Port Vlans allowed on trunk
Gi1/0/49 1-4094
Port Vlans allowed and active in management domain
Gi1/0/49 1-2,10-18,90-92,100,110,12
Port Vlans in spanning tree forwarding state and not pruned
Gi1/0/49 1-2,10-18,90-92,100,110,12
BKGNDFCR2SW01#
--------------------------
Core switch
BKCSWP01#sh vtp status
VTP Version : 3 (capable)
VTP version running : 3
VTP Domain Name : sjog_bk
VTP Pruning Mode : Disabled (Operationally Disabled)
VTP Traps Generation : Enabled
Device ID : 002a.1061.ee40
Feature VLAN:
--------------
VTP Operating Mode : Transparent
Number of existing VLANs : 28
Number of existing extended VLANs : 0
Feature MST:
--------------
VTP Operating Mode : Transparent
Feature UNKNOWN:
--------------
VTP Operating Mode : Transparent
BKCSWP01#
__________________________
Show interface trunk
BKCSWP01#sh int trunk
Port Mode Encapsulation Status Native vlan
Te1/13 on 802.1q trunking 1
Te1/14 on 802.1q trunking 1
Te1/15 on 802.1q trunking 1
Te1/16 on 802.1q trunking 1
Te2/9 on 802.1q trunking 1
Te2/10 on 802.1q trunking 1
Port Vlans allowed on trunk
Te1/13 1-4094
Te1/14 1-4094
Te1/15 1-4094
Te1/16 1-4094
Te2/9 1-4094
Te2/10 1-4094
Port Vlans allowed and active in management domain
Te1/13 1-2,10-18,90-92,100,110,12
Te1/14 1-2,10-18,90-92,100,110,12
Te1/15 1-2,10-18,90-92,100,110,12
Te1/16 1-2,10-18,90-92,100,110,12
Te2/9 1-2,10-18,90-92,100,110,12
Port Vlans allowed and active in management domain
Te2/10 1-2,10-18,90-92,100,110,12
Port Vlans in spanning tree forwarding state and not pruned
Te1/13 1-2,10-18,90-92,100,110,12
Te1/14 1-2,10-18,90-92,100,110,12
Te1/15 1-2,10-18,90-92,100,110,12
Te1/16 1-2,10-18,90-92,100,110,12
Te2/9 1-2,10-18,90-92,100,110,12
Te2/10 1-2,10-18,90-92,100,110,12
BKCSWP01#
ASKER
Hi , IP address of edge switch should be 10.194.0.51 in vlan 990
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Edge switch :
BKGNDFCR2SW01#sh spanning-tree vlan 990
VLAN0990
Spanning tree enabled protocol rstp
Root ID Priority 25566
Address 002a.1061.ee40
Cost 4
Port 49 (GigabitEthernet1/0/49)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33758 (priority 32768 sys-id-ext 990)
Address f8a5.c581.b180
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- -------------------------- ------
Gi1/0/49 Root FWD 4 128.49 P2p
__________________________ __________ __________ __________ __________ __________ __________ ____
VLAN0900
Spanning tree enabled protocol rstp
Root ID Priority 25476
Address 002a.1061.ee40
Cost 4
Port 49 (GigabitEthernet1/0/49)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33668 (priority 32768 sys-id-ext 900)
Address f8a5.c581.b180
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- -------------------------- ------
Gi1/0/49 Root FWD 4 128.49 P2p
BKGNDFCR2SW01#
__________________________ __________ __________ __________ __________ __________ __________ __________
On Core Switch
BKCSWP01#sh spanning-tree vlan 990
VLAN0990
Spanning tree enabled protocol rstp
Root ID Priority 25566
Address 002a.1061.ee40
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 25566 (priority 24576 sys-id-ext 990)
Address 002a.1061.ee40
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 480
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- -------------------------- ------
Te1/13 Desg FWD 4 128.13 P2p
Te1/14 Desg FWD 4 128.14 P2p
Te1/15 Desg FWD 4 128.15 P2p
Te1/16 Desg FWD 4 128.16 P2p
Te2/9 Desg FWD 4 128.137 P2p
Te2/10 Desg FWD 4 128.138 P2p
__________________________ __________ __________ ___
VLAN0900
Spanning tree enabled protocol rstp
Root ID Priority 25476
Address 002a.1061.ee40
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 25476 (priority 24576 sys-id-ext 900)
Address 002a.1061.ee40
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 480
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- -------------------------- ------
Te1/13 Desg FWD 4 128.13 P2p
Te1/14 Desg FWD 4 128.14 P2p
Te1/15 Desg FWD 4 128.15 P2p
Te1/16 Desg FWD 4 128.16 P2p
Te2/9 Desg FWD 4 128.137 P2p
Te2/10 Desg FWD 4 128.138 P2p
BKCSWP01#
BKGNDFCR2SW01#sh spanning-tree vlan 990
VLAN0990
Spanning tree enabled protocol rstp
Root ID Priority 25566
Address 002a.1061.ee40
Cost 4
Port 49 (GigabitEthernet1/0/49)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33758 (priority 32768 sys-id-ext 990)
Address f8a5.c581.b180
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------
Gi1/0/49 Root FWD 4 128.49 P2p
__________________________
VLAN0900
Spanning tree enabled protocol rstp
Root ID Priority 25476
Address 002a.1061.ee40
Cost 4
Port 49 (GigabitEthernet1/0/49)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33668 (priority 32768 sys-id-ext 900)
Address f8a5.c581.b180
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------
Gi1/0/49 Root FWD 4 128.49 P2p
BKGNDFCR2SW01#
__________________________
On Core Switch
BKCSWP01#sh spanning-tree vlan 990
VLAN0990
Spanning tree enabled protocol rstp
Root ID Priority 25566
Address 002a.1061.ee40
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 25566 (priority 24576 sys-id-ext 990)
Address 002a.1061.ee40
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 480
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------
Te1/13 Desg FWD 4 128.13 P2p
Te1/14 Desg FWD 4 128.14 P2p
Te1/15 Desg FWD 4 128.15 P2p
Te1/16 Desg FWD 4 128.16 P2p
Te2/9 Desg FWD 4 128.137 P2p
Te2/10 Desg FWD 4 128.138 P2p
__________________________
VLAN0900
Spanning tree enabled protocol rstp
Root ID Priority 25476
Address 002a.1061.ee40
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 25476 (priority 24576 sys-id-ext 900)
Address 002a.1061.ee40
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 480
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------
Te1/13 Desg FWD 4 128.13 P2p
Te1/14 Desg FWD 4 128.14 P2p
Te1/15 Desg FWD 4 128.15 P2p
Te1/16 Desg FWD 4 128.16 P2p
Te2/9 Desg FWD 4 128.137 P2p
Te2/10 Desg FWD 4 128.138 P2p
BKCSWP01#
ASKER
sorry have just updated on edge switch :
!
interface Vlan990
ip address 10.192.0.51 255.255.255.0
to
!
interface Vlan990
ip address 10.194.0.51 255.255.255.0
but still not working
!
interface Vlan990
ip address 10.192.0.51 255.255.255.0
to
!
interface Vlan990
ip address 10.194.0.51 255.255.255.0
but still not working
If question is related to management VLAN.
Switch's ip default-gateway 10.194.2.5 is outside IP range of management VLAN. Typically - default gateway should be from the same IP address range as management IP address (interface VLAN IP address on core switch).
Additionally interface for VLAN 990 is not present on core switch according to your output (or in down state since it is not listed in routing table).
Also, if 2960 is in use as L2 switch only 1 SVI will be in up up state and that one need to be used as management switch (only SVI for Vlan 900 or 990 can be active in this case - not both).
sh ip int brief
check which is in up up state.
Switch's ip default-gateway 10.194.2.5 is outside IP range of management VLAN. Typically - default gateway should be from the same IP address range as management IP address (interface VLAN IP address on core switch).
Additionally interface for VLAN 990 is not present on core switch according to your output (or in down state since it is not listed in routing table).
Also, if 2960 is in use as L2 switch only 1 SVI will be in up up state and that one need to be used as management switch (only SVI for Vlan 900 or 990 can be active in this case - not both).
sh ip int brief
check which is in up up state.
ASKER
Hi Predrag,
VLAN 990 is in the routing table at the top of the list, not sure but 7 other switches are connected to the core switch and is working fine, however this one edge switch can not get to the router at 10.194.2.1.
However, it seems that it can reach everything else such as other edge switches and core but not past the core, hope this helps.
VLAN 990 is in the routing table at the top of the list, not sure but 7 other switches are connected to the core switch and is working fine, however this one edge switch can not get to the router at 10.194.2.1.
However, it seems that it can reach everything else such as other edge switches and core but not past the core, hope this helps.
VLAN 990 is in the routing tableIt is at the top.. did not notice it :)
Not past core - points to bad default gateway address for switch generated traffic.
If VLAN 990 is your management VLAN (and in up up state when ip int brief is issued) default gateway should be configured as:
ip default-gateway 10.194.0.1
ASKER
I think the vlan 990 is for switch management of traps messages for SNMP and others features. The gateway in design was 10.194.2.1 as the router.
Design is not good in that case (relays on proxy ARP). Default gateway IP address should be IP address of interface VLAN 990 on core device (if SVI for 990 is management interface).
And interface VLAN 990 need to be in up up state.
And interface VLAN 990 need to be in up up state.
ASKER
Vlan 990 is in up up state
BKCSWP01#sh ip int brief
Interface IP-Address OK? Method Status Protoc ol
TenGigabitEthernet1/1 unassigned YES unset administratively down down
TenGigabitEthernet1/2 unassigned YES unset administratively down down
TenGigabitEthernet1/3 unassigned YES unset administratively down down
TenGigabitEthernet1/4 unassigned YES unset administratively down down
TenGigabitEthernet1/5 unassigned YES unset administratively down down
TenGigabitEthernet1/6 unassigned YES unset administratively down down
TenGigabitEthernet1/7 unassigned YES unset administratively down down
TenGigabitEthernet1/8 unassigned YES unset down down
TenGigabitEthernet1/9 unassigned YES NVRAM down down
TenGigabitEthernet1/10 unassigned YES NVRAM down down
TenGigabitEthernet1/11 unassigned YES unset down down
TenGigabitEthernet1/12 unassigned YES unset down down
TenGigabitEthernet1/13 unassigned YES unset up up
TenGigabitEthernet1/14 unassigned YES unset up up
TenGigabitEthernet1/15 unassigned YES unset up up
TenGigabitEthernet1/16 unassigned YES unset up up
TenGigabitEthernet2/1 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/2 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/3 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/4 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/5 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/6 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/7 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/8 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/9 unassigned YES unset up up
TenGigabitEthernet2/10 unassigned YES unset up up
TenGigabitEthernet2/11 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/12 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/13 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/14 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/15 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/16 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/1 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/2 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/3 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/4 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/5 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/6 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/7 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/8 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/9 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/10 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/11 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/12 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/13 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/14 10.194.2.5 YES NVRAM up up
TenGigabitEthernet5/15 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/16 unassigned YES NVRAM administratively down down
mgmt0 unassigned YES unset down down
Vlan1 unassigned YES NVRAM administratively down down
Vlan2 unassigned YES unset administratively down down
Vlan10 10.194.10.1 YES NVRAM up up
Vlan11 10.194.11.1 YES NVRAM up up
Vlan12 10.194.12.1 YES NVRAM up up
Vlan13 10.194.13.1 YES NVRAM up up
Vlan14 10.194.14.1 YES NVRAM up up
Vlan15 10.194.15.1 YES NVRAM up up
Vlan16 10.194.16.1 YES NVRAM up up
Vlan17 10.194.17.1 YES NVRAM up up
Vlan18 10.194.18.1 YES NVRAM up up
Vlan90 10.194.90.1 YES NVRAM up up
Vlan91 10.194.91.1 YES NVRAM up up
Vlan92 10.194.92.1 YES NVRAM up up
Vlan100 10.194.100.1 YES NVRAM up up
Vlan110 10.194.110.1 YES NVRAM up up
Vlan120 10.194.120.1 YES NVRAM up up
Vlan121 10.194.121.1 YES NVRAM up up
Vlan130 10.194.6.1 YES NVRAM up up
Vlan900 10.194.70.1 YES NVRAM up up
Vlan990 10.194.0.1 YES NVRAM up up
BKCSWP01#
BKCSWP01#sh ip int brief
Interface IP-Address OK? Method Status Protoc ol
TenGigabitEthernet1/1 unassigned YES unset administratively down down
TenGigabitEthernet1/2 unassigned YES unset administratively down down
TenGigabitEthernet1/3 unassigned YES unset administratively down down
TenGigabitEthernet1/4 unassigned YES unset administratively down down
TenGigabitEthernet1/5 unassigned YES unset administratively down down
TenGigabitEthernet1/6 unassigned YES unset administratively down down
TenGigabitEthernet1/7 unassigned YES unset administratively down down
TenGigabitEthernet1/8 unassigned YES unset down down
TenGigabitEthernet1/9 unassigned YES NVRAM down down
TenGigabitEthernet1/10 unassigned YES NVRAM down down
TenGigabitEthernet1/11 unassigned YES unset down down
TenGigabitEthernet1/12 unassigned YES unset down down
TenGigabitEthernet1/13 unassigned YES unset up up
TenGigabitEthernet1/14 unassigned YES unset up up
TenGigabitEthernet1/15 unassigned YES unset up up
TenGigabitEthernet1/16 unassigned YES unset up up
TenGigabitEthernet2/1 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/2 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/3 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/4 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/5 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/6 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/7 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/8 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/9 unassigned YES unset up up
TenGigabitEthernet2/10 unassigned YES unset up up
TenGigabitEthernet2/11 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/12 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/13 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/14 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/15 unassigned YES NVRAM administratively down down
TenGigabitEthernet2/16 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/1 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/2 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/3 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/4 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/5 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/6 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/7 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/8 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/9 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/10 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/11 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/12 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/13 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/14 10.194.2.5 YES NVRAM up up
TenGigabitEthernet5/15 unassigned YES NVRAM administratively down down
TenGigabitEthernet5/16 unassigned YES NVRAM administratively down down
mgmt0 unassigned YES unset down down
Vlan1 unassigned YES NVRAM administratively down down
Vlan2 unassigned YES unset administratively down down
Vlan10 10.194.10.1 YES NVRAM up up
Vlan11 10.194.11.1 YES NVRAM up up
Vlan12 10.194.12.1 YES NVRAM up up
Vlan13 10.194.13.1 YES NVRAM up up
Vlan14 10.194.14.1 YES NVRAM up up
Vlan15 10.194.15.1 YES NVRAM up up
Vlan16 10.194.16.1 YES NVRAM up up
Vlan17 10.194.17.1 YES NVRAM up up
Vlan18 10.194.18.1 YES NVRAM up up
Vlan90 10.194.90.1 YES NVRAM up up
Vlan91 10.194.91.1 YES NVRAM up up
Vlan92 10.194.92.1 YES NVRAM up up
Vlan100 10.194.100.1 YES NVRAM up up
Vlan110 10.194.110.1 YES NVRAM up up
Vlan120 10.194.120.1 YES NVRAM up up
Vlan121 10.194.121.1 YES NVRAM up up
Vlan130 10.194.6.1 YES NVRAM up up
Vlan900 10.194.70.1 YES NVRAM up up
Vlan990 10.194.0.1 YES NVRAM up up
BKCSWP01#
On edge switch? This is core. :)
For L2 device typically only one SVI is in up up state.
For L2 device typically only one SVI is in up up state.
ASKER
oops sorry , :)
BKGNDFCR2SW01#sh ip int brief
Interface IP-Address OK? Method Status Protocol
Vlan1 unassigned YES unset up up
Vlan900 10.194.70.12 YES manual up up
Vlan990 10.194.0.51 YES manual up up
FastEthernet0 unassigned YES unset down down
GigabitEthernet1/0/1 unassigned YES unset down down
GigabitEthernet1/0/2 unassigned YES unset down down
GigabitEthernet1/0/3 unassigned YES unset down down
GigabitEthernet1/0/4 unassigned YES unset down down
GigabitEthernet1/0/5 unassigned YES unset down down
GigabitEthernet1/0/6 unassigned YES unset down down
GigabitEthernet1/0/7 unassigned YES unset down down
GigabitEthernet1/0/8 unassigned YES unset down down
GigabitEthernet1/0/9 unassigned YES unset down down
GigabitEthernet1/0/10 unassigned YES unset down down
GigabitEthernet1/0/11 unassigned YES unset down down
GigabitEthernet1/0/12 unassigned YES unset down down
GigabitEthernet1/0/13
BKGNDFCR2SW01#sh ip int brief
Interface IP-Address OK? Method Status Protocol
Vlan1 unassigned YES unset up up
Vlan900 10.194.70.12 YES manual up up
Vlan990 10.194.0.51 YES manual up up
FastEthernet0 unassigned YES unset down down
GigabitEthernet1/0/1 unassigned YES unset down down
GigabitEthernet1/0/2 unassigned YES unset down down
GigabitEthernet1/0/3 unassigned YES unset down down
GigabitEthernet1/0/4 unassigned YES unset down down
GigabitEthernet1/0/5 unassigned YES unset down down
GigabitEthernet1/0/6 unassigned YES unset down down
GigabitEthernet1/0/7 unassigned YES unset down down
GigabitEthernet1/0/8 unassigned YES unset down down
GigabitEthernet1/0/9 unassigned YES unset down down
GigabitEthernet1/0/10 unassigned YES unset down down
GigabitEthernet1/0/11 unassigned YES unset down down
GigabitEthernet1/0/12 unassigned YES unset down down
GigabitEthernet1/0/13
OK both are in up up state.
By default if not specifically configured the least number VLAN interface will be used to sent switch generated traffic (like snmp traps etc) so in your case VLAN 900 should be used.
By default if not specifically configured the least number VLAN interface will be used to sent switch generated traffic (like snmp traps etc) so in your case VLAN 900 should be used.
ASKER
thanks for the info, :) so is there a reason it is using it in this case?
ASKER
I did do a hard reset on the switch as i was unable to access due to bad password set, but that should not affect it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thankyou for everyones help, i just swapped out the sfp cable with one on the other switch and it seems to be working now.... very strange....
ASKER
Thank You for the support, much appreciated :)
It is strange, but again what is written above are general rules.
- Decide which VLAN is management VLAN
- configure device to use that VLAN interface to generate switch traffic (or have just that SVI configured with IP address)
- configure IP address of the same VLAN on core switch as default gateway
You're welcome.
- Decide which VLAN is management VLAN
- configure device to use that VLAN interface to generate switch traffic (or have just that SVI configured with IP address)
- configure IP address of the same VLAN on core switch as default gateway
You're welcome.
ASKER
So we should have the same vlan for switch generated traffic, device management and the gateway of the switch on the same vlan?
Yes.