Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About cre8toruk
Stats
Member since
11-08-2019
32
Posts
5
Helpful
0
Solutions
12-09-2019
06:45 AM
Hi All, I've configured a port on my POE switch as a trunk port assigned it the relevant VLAN's that it should host traffic for and I've configured the AP with an IP address in the management VLAN - 192.168.254.146. I can ping the ip address of the AP from any of the switches (all in the same VLAN and subnet perhaps the clue there) but whilst I can ping all of the switches on the same subnet from a client on a completely different subnet I'm unable to ping the access point. Consequently I'm not able to get it working on the wifi controller server (also on a different subnet). Any ideas ? The AP's port looks like this; interface gigabitethernet5
description Wifi-AP
switchport trunk allowed vlan add 101-103,190
switchport trunk native vlan 254 AP: 192.168.254.146 (vlan 254) Client: 192.168.200.116 (vlan 200) Client is connected to an access port on SW3 which has a trunk to SW1 i.e: interface Port-Channel3
description CORE-SW1-UPLINK
spanning-tree link-type point-to-point
switchport mode trunk
switchport trunk native vlan 200
switchport trunk allowed vlan 200,254
macro description switch
!next command is internal.
macro auto smartport dynamic_type switch AP is connected to SW2 and has a trunk to SW1 interface Port-channel4
description CORE-SW2
spanning-tree link-type point-to-point
switchport trunk allowed vlan add 10,101-103,190,200,254,400,2122,2126
macro description "switch "
!next command is internal.
macro auto smartport dynamic_type unknown I'm sure I'm missing something obvious.. grateful as always for any assistance. Paul.
... View more
Labels:
12-09-2019
06:25 AM
Right after a lot of Googling etc.. I tried the above btw... I resolved to simply disable the message... thanks to all for your assistance.
... View more
12-09-2019
02:21 AM
300: CORE-SW2
v1.4.11.2 / R800_NIK_1_4_216_022
CLI v1.0
set system mode router
file SSD indicator encrypted
@
ssd-control-start
ssd config
ssd file passphrase control unrestricted
no ssd file integrity control
ssd-control-end cb0a3fdb1f3a1af4e4430033719968c0
!
vlan database
vlan 10,17,101-103,190,200,254,400,2122,2126
exit
ip dhcp relay address 192.168.10.10
ip dhcp relay address 192.168.10.11
ip dhcp relay enable
bonjour interface range vlan 1
hostname CORE-SW2
logging buffered warnings
ip ssh server
clock timezone J 0 minutes 0
clock summer-time web recurring eu
clock source browser
no ip domain lookup
!
interface vlan 1
shutdown
!
interface vlan 10
name SERVERS
ip address 192.168.10.102 255.255.255.0
!
interface gigabitethernet24
switchport mode access
switchport access vlan 254
!
interface gigabitethernet51
description CORE-SW-UPLINK-01
channel-group 4 mode auto
no macro auto smartport
!next command is internal.
macro auto smartport dynamic_type unknown
!
interface gigabitethernet52
description CORE-SW-UPLINK-02
spanning-tree link-type point-to-point
channel-group 4 mode auto
macro description "switch "
!next command is internal.
macro auto smartport dynamic_type switch
!
interface Port-channel1
description SVR-HOST-01
switchport trunk allowed vlan add 2122,2126
switchport trunk native vlan 10
!
interface Port-channel2
description SVR-HOST-02
switchport trunk allowed vlan add 101-103,400
switchport trunk native vlan 10
!
interface Port-channel3
description EDGE-NETWORK
spanning-tree link-type point-to-point
switchport trunk native vlan 200
macro description switch
no macro auto smartport
!next command is internal.
macro auto smartport dynamic_type switch
!
interface Port-channel4
description CORE-SW2
spanning-tree link-type point-to-point
switchport trunk allowed vlan add 10,101-103,190,200,254,400,2122
switchport trunk allowed vlan add 2126
macro description "switch "
!next command is internal.
macro auto smartport dynamic_type unknown
!
exit
banner login
################# CORE-SW2 ####################
########### No Unauthorised Access ############
###############################################
ip helper-address 192.168.200.0 192.168.10.10 37 42 49 53 137 138
ip default-gateway 192.168.254.254 DELL !Current Configuration:
!System Description "PowerConnect 6224, 3.3.16.1, VxWorks 6.5"
!System Software Version 3.3.16.1
!Cut-through mode is configured as disabled
!
configure
vlan database
vlan 5,10,20-21,50-51,100-103,190,200,254,400,1000-1004,2000,2010,2122,2126
vlan routing 10 1
vlan routing 200 2
vlan routing 254 3
vlan routing 2000 4
vlan routing 5 5
vlan routing 2010 6
vlan routing 400 7
vlan routing 190 8
vlan routing 50 9
vlan routing 51 10
vlan association mac 0015.5D0A.0236 10
vlan association mac 0015.5D0A.0237 10
vlan association mac F01F.AF3D.5391 1
sntp unicast client enable
sntp server 192.168.10.10
sntp server 192.168.10.11 priority 2
clock summer-time recurring EU
stack
member 1 1
member 2 1
ip address 192.168.1.20 255.255.255.0
no ip domain-lookup
no ipv6 enable
no ipv6 forwarding
ip routing
ip route 0.0.0.0 0.0.0.0 192.168.254.1
ip helper-address 192.168.10.10 dhcp
ip helper-address 192.168.10.11 dhcp
ip helper-address 192.168.254.1 dhcp
ip helper-address 192.168.10.10 ntp
ip helper-address 192.168.10.11 ntp
router rip
no enable
interface vlan 10
name "Server VLAN"
routing
ip address 192.168.10.254 255.255.255.0
ipv6 mtu 1500
no ipv6 unreachables
no ip proxy-arp
interface vlan 200
name "Client VLAN"
routing
ip address 192.168.200.254 255.255.255.0
ipv6 mtu 1500
no ipv6 unreachables
no ip proxy-arp
interface vlan 254
name "Network VLAN"
routing
ip address 192.168.254.254 255.255.255.0
ipv6 mtu 1500
no ipv6 unreachables
no ip proxy-arp
interface vlan 2122
name "DSL Nimrod VLAN"
interface vlan 2126
name "DSL Cobham VLAN"
dhcp l2relay vlan 10
!
interface ethernet 1/g20
description "TEMP-CiscoXG"
switchport mode trunk
switchport trunk allowed vlan add 10,101-103,190,200,254
!
... View more
12-09-2019
02:09 AM
Hi All, got this annoying CDP message which I don't seem to be able to shake off. 350XG connected to a SF300 via PO4 (port channel is PO4 on both switches to be helpful :-)) On SW2 (SF300) the ports gi51 & gi52 make up the port channel.... config below. interface gigabitethernet51
description CORE-SW-UPLINK-01
spanning-tree link-type point-to-point
channel-group 4 mode auto
no macro auto smartport
!
interface gigabitethernet52
description CORE-SW-UPLINK-02
channel-group 4 mode auto
no macro auto smartport
interface Port-channel4
description CORE-SW2
spanning-tree link-type point-to-point
switchport trunk allowed vlan add 10,101-103,190,200,254,400,2122
switchport trunk allowed vlan add 2126
macro description "switch "
!next command is internal.
macro auto smartport dynamic_type unknown on the 350XG PO4 is made up of te1/0/2 and te2/0/2 config below interface TenGigabitEthernet1/0/2
description CORE-SW2-1
spanning-tree link-type point-to-point
channel-group 4 mode auto
switchport mode trunk
switchport trunk allowed vlan 10,101-103,190,200,254,400,2122,2126
macro description "switch "
!next command is internal.
macro auto smartport dynamic_type switch
interface TenGigabitEthernet2/0/2
description CORE-SW2-2
spanning-tree link-type point-to-point
channel-group 4 mode auto
switchport mode trunk
switchport trunk allowed vlan 10,101-103,190,200,254,400,2122,2126
macro description "switch "
interface Port-Channel4
description CORE-SW2
spanning-tree link-type point-to-point
switchport mode trunk
switchport trunk allowed vlan 10,101-103,190,200,254,400,2122,2126
macro description "switch "
!next command is internal.
macro auto smartport dynamic_type switch
If I check all ports for native vlan they say Native VLAN is VLAN 1 (on both switches). SW1:
show int switchport po4
S-VLAN Ethernet Type: 0x8100 (802.1q)
VLAN Mapping Tunnel L2 protocols Global CoS: 5
Name: Po4
Switchport: enable
Administrative Mode: trunk
Operational Mode: up
Access Mode VLAN: 1
Access Multicast TV VLAN: none
Trunking Native Mode VLAN: 1 (Inactive)
Trunking VLANs: 10,101-103,190,200,254,400,2122,2126
General PVID: 1
General VLANs: none
General Egress Tagged VLANs: none
General Forbidden VLANs: none
General Ingress Filtering: enabled
General Acceptable Frame Type: all
General GVRP status: disabled
Customer Mode VLAN: none
Customer Multicast TV VLANs: none
Private-vlan promiscuous-association primary VLAN: none
Private-vlan promiscuous-association Secondary VLANs: none
Private-vlan host-association primary VLAN: none
Private-vlan host-association Secondary VLAN: none
SW2:
Show int switch po4
Port : Po4
Port Mode: Trunk
Gvrp Status: disabled
Ingress Filtering: true
Acceptable Frame Type: admitAll
Ingress UnTagged VLAN ( NATIVE ): 1
Port is member in:
Vlan Name Egress rule Added by
---- -------------------------------- ----------- ----------------
1 1 Untagged V
10 SERVERS Tagged S
101 MEL-MOBILE Tagged S
102 MEL-PUBLIC Tagged S
103 MEL-CONTROLS Tagged S
190 MEL-WIRELESS Tagged S
200 ENDPOINTS Tagged S
254 OTHER-DEVICES Tagged S
400 BURKINA-CONTROLS Tagged S
2122 NIMROD-DSL Tagged S
Any ideas how I can correct the CDP error ? Also on SW should te1/0/2 & te2/0/2 be configured like that if they're part of a port channel ? SW2 wouldn't let the ports have any configuration prior to being added to the port channel. Grateful for all assistance as ever. Paul.
... View more
Labels:
12-09-2019
12:43 AM
Hi, Sorry... I meant to reply to your post apologies... Currently the Dell 6224 is the ip gateway device, however the SG350XG is also set as a layer 3 switch and IP routing is enabled on it. If I switch the 300 to a layer 3, It does seem to solve the problem though which would seem to bear out my theory. Ultimately the Dell switch will be retired and the new cisco kit will take over, it's complicated at the moment because I have to have both sets of infrastructure running and connected together.
... View more
12-06-2019
04:16 AM
All sorted on this one now... it was simply a missing VLAN in the trunk I think. I've remade both port channels and fingers crossed it seems to be working now. Moving on (since I now have a working DHCP client :-))…. Previously my Pc has had to have two network cards in it, one one the client (200) VLAN and one on the Net management (254) VLAN. As I'm implementing new switches I'd like to only have one network card but still be able to access the cli and consoles of all the new switches on the management VLAN (254). I have assigned an IP address on VLAN 254 on each of the switches; 192.168.254.11, 12 & 13 respectively. SW1 (VLAN254:192.168.254.11): is a layer 3 350XG with IP routing enabled and a default route of 192.168.254.254 (the current dell layer 3 switch) SW2 (VLAN254:192.168.254.12): is currently set as a layer 2 switch SW3 (VLAN254: 192.168.254.13): The Client PC is on VLAN 200 and has an ip address of 192.168.200.207 I can ping the Layer 3 core switch on 192.168.254.11, however I can't ping 192.168.254.12 or 192.168.254.13 (the switch I'm connected to), presumably because it doesn't know what to do with the return route i.e. 192.168.200.0... so cut a long story short(er), I enabled IP routing on SW3 (192.168.254.13) and gave it a default route as per SW1. This seems to have done the trick, however I still cant connect or ping SW2 on it's 192.168.254.12 ip. So my questions are I guess is, is this the best way to do this? i.e. do ip routing or should there be a better way to do it? Do we think I should enable Layer 3 capabilities on the layer 2 switch i.e. 192.168.254.12? Hopefully the diagram below makes some sense.
... View more
12-04-2019
04:59 AM
Update: Ok I've added VLAN 200 to the trunk (Doh!) and now I can get a DHCP address....
... View more
12-04-2019
03:57 AM
Hi All, I need some help! I'm trying to figure out why I can't get an IP address assigned via our existing DHCP server. I have some new Cisco switches which will replace some old Dell switches but in the mean time I'm having to sort of merge the two infrastructures together while we migrate everything over. The image should show the existing infrastructure. The stuff in green is the existing infrastructure, the stuff in red is the new stuff. The stuff in green works (obvs) but the stuff in red doesn't. I can ping the dhcp server from the Cisco layer 3 switch. If I manually set the ip address to 192.168.200.30 on the client I'm not able to ping the .200 gateway (200.254). I'm obviously doing something wrong... HELP ! :-)
... View more
Labels:
12-03-2019
02:58 PM
Short answer, I don't know... next time it happens I'll try. Thanks.
... View more
12-03-2019
05:45 AM
Hi All, pretty much there with my new infrastructure config... 2 x 350XG's stacked & 1 x 300 POE in the core, 4 x 350X-48's stacked at the edge. I've patched the management vlan (was 1 now something else) through to my PC's second ethernet card and can connect to all three switch entity's on 192.168.254.11, 12 & 13 respectively. A funny thing has been happening (though only a couple of times) that I noticed.... having connected to one of the switches (.12) via the web console and via SSH and basically been doing a sh run to document the config, I've become disconnected. I can connect to .11 & 13 still (I'm patched through to 13 directly) but .12 has just vanished. If I go and physically plug it into another port voila! I can connect again. My first thought was port-security, however I've checked that and all the interfaces are set to "Unlocked" currently. There's not been anything obvious in the logs on .12 to indicate what's happening though of course the .12 switch is connected via trunk to .11 and via trunk .13... Is there anything I can check to see what is occurring? thanks as ever. Paul.
... View more
Labels:
11-28-2019
02:27 AM
Ok all sorted... I think the laptops firewall was causing some issues, thanks to all.
... View more
11-28-2019
01:53 AM
I couldn't ping the gw from the switch since (the cisco that is) didn't have an IP address assigned to any vlan… we're talking layer 2 here not 3... If I add 192.168.200.253 to the vlan 200 interface I can ping the default gateway (192.168.200.254) on the Dell switch and all other subnets i.e. 192.168.10.254 (the default gateway for the server VLAN (10)) and the server on 192.168.10.10.... I'll run some more diagnostics and determine what is working and what isn't and then summarise it.... I'm hoping this is only a temporary hookup while I'm migrating the company's VM infrastructure to new servers (and new switches)..
... View more
11-27-2019
01:02 PM
Laptop def gateway: 192.168.200.254 - hosted on Dell Switch (Laptop connected to Cisco switch) Server def gateway: 192.169.10.254 - hosted on Dell Switch (Server connected to Dell switch) Laptop can ping 192.168.200.254 but not 192.168.10.254... do i need to trunk that?
... View more
12-09-2019
Right after a lot of Googling etc.. I tried the above btw... I resolved
to simply disable the messag...
12-09-2019
300:CORE-SW2 v1.4.11.2 / R800_NIK_1_4_216_022 CLI v1.0 set system mode
router file SSD indicator enc...
12-09-2019
Hi All, got this annoying CDP message which I don't seem to be able to
shake off.350XG connected to ...
12-09-2019
Hi, Sorry... I meant to reply to your post apologies... Currently the
Dell 6224 is the ip gateway de...
12-06-2019
All sorted on this one now... it was simply a missing VLAN in the trunk
I think.I've remade both por...
12-04-2019
Hi All,I need some help! I'm trying to figure out why I can't get an IP
address assigned via our exi...
12-03-2019
Hi All,pretty much there with my new infrastructure config... 2 x
350XG's stacked & 1 x 300 POE in t...
11-28-2019
I couldn't ping the gw from the switch since (the cisco that is) didn't
have an IP address assigned ...
Public Statistics
| Date Registered | 11-08-2019 03:18 AM |
| Date Last Visited | 12-09-2019 01:01 AM |
| Total Messages Posted | 32 |
| Total Helpful Votes Received | 5 |
Helpful Votes Given To
.jpg "VIP Expert"){kind=icon}
.jpg "Hall of Fame Guru"){kind=icon}
