Unsolved
This post is more than 5 years old
1 Rookie
•
10 Posts
0
2715
June 14th, 2018 16:00
Routing issues between N4064F's and N1524P's
I have a limited background in Routing. Here is what I am trying to do.
The 2 N4064F's are my core stack. From there I break out to my other areas where I have stacks of N1524P's. The N1524P's are all connected through Fiber Optic LAGs with at least 2 connections back to the core. There is also a router connected to the 136 network with an address of 192.168.143.65
The first issue is sending emails alerts from all stacks. I ended up turning on router discovery and setting the OOB port of the core stack to 192.168.2.2 this allowed emails to get out from the core.
I have tried multiple configurations on the other stacks and with the last changes I attempted I can tracert to the router but no further. There is a route in the router from 192.168.0.0 to 192.168.143.65 and the Vlan1 IP is 192.168.143.2 and Vlan2 IP is 192.168.2.3. The only thing that caught my attention is that the router had Vlan8 for the 192.168.143.65 interface.
The second issue or maybe it is not really an issue, is I will need both Vlan1 and Vlan2 to go across the LAG interfaces. I have found a few examples but I am not confident that it is exactly what I need to do.
//Core Config//
configure
vlan 2
exit
vlan 2
name "192.168.2.0 Network"
exit
snmp-server location "xxxxxxx"
hostname "xxxxxx Core"
slot 1/0 5 ! Dell Networking N4064F
slot 2/0 5 ! Dell Networking N4064F
sntp unicast client enable
sntp server 192.168.140.253
clock summer-time recurring USA
clock timezone -6 minutes 0
stack
member 1 4 ! N4064F
member 2 4 ! N4064F
exit
interface out-of-band
ip address 192.168.2.2 255.255.255.0 192.168.2.1
no ipv6 enable
exit
ip domain-name "xxxxxx.local"
ip name-server "192.168.0.17"
ip name-server "192.168.0.18"
ip name-server "192.168.0.154"
logging email
logging email from-addr xxxxxx@xxxxxx.com
logging email message-type urgent to-addr it@xxxxxx.com
logging email message-type urgent to-addr xxxxxx@xxxxxx.com
logging email message-type urgent to-addr xxxxxx@xxxxxx.com
mail-server "192.168.0.134"
exit
ip http timeout-policy idle 3600 life 86400
boot auto-copy-sw
ip routing
router rip
no enable
default-metric 1
exit
interface vlan 1
ip address 192.168.143.254 255.255.248.0
ip netdirbcast
ip igmp version 2
ip pim
exit
ip route 192.168.0.0 255.255.255.0 192.168.143.65
username "admin" password xxxxxx privilege 15 encrypted
line console
exec-timeout 65535
exit
line telnet
password xxxxxx encrypted
exit
no spanning-tree
spanning-tree portfast bpdufilter default
spanning-tree bpdu-protection
spanning-tree priority 0
ip igmp snooping querier
ip igmp snooping querier address 192.168.143.254
ip igmp snooping querier vlan 1
ip multicast-routing
ip pim sparse-mode
application install SupportAssist auto-restart start-on-boot
!
interface Te1/0/1
speed auto
spanning-tree portfast
spanning-tree guard loop
switchport access vlan 2
exit
!
interface Te1/0/2
switchport access vlan 2
exit
!
interface Te1/0/3
switchport access vlan 2
exit
!
interface Te1/0/4
switchport access vlan 2
exit
!
interface Te1/0/5
switchport access vlan 2
exit
!
interface Te1/0/6
switchport access vlan 2
exit
!
interface Te1/0/7
channel-group 1 mode on
exit
!
interface Te1/0/8
channel-group 1 mode on
exit
!
interface Te1/0/9
channel-group 2 mode on
exit
!
interface Te1/0/10
channel-group 2 mode on
exit
!
interface Te1/0/11
channel-group 11 mode on
exit
!
interface Te1/0/12
channel-group 12 mode on
exit
!
interface Te1/0/13
channel-group 13 mode on
exit
!
interface Te1/0/14
channel-group 14 mode on
exit
!
interface Te1/0/15
channel-group 15 mode on
exit
!
interface Te1/0/16
channel-group 16 mode on
exit
!
interface Te1/0/17
channel-group 17 mode on
exit
!
interface Te1/0/18
channel-group 18 mode on
exit
!
interface Te1/0/19
channel-group 19 mode on
exit
!
interface Te1/0/20
channel-group 20 mode on
exit
!
interface Te1/0/21
channel-group 21 mode on
exit
!
interface Te1/0/22
channel-group 22 mode on
exit
!
interface Te1/0/23
channel-group 23 mode on
exit
!
interface Te1/0/24
channel-group 24 mode on
exit
!
interface Te1/0/25
channel-group 3 mode on
exit
!
interface Te1/0/26
channel-group 3 mode on
exit
!
interface Te1/0/27
channel-group 4 mode on
exit
!
interface Te1/0/28
channel-group 4 mode on
exit
!
interface Te1/0/39
channel-group 6 mode on
exit
!
interface Te1/0/40
channel-group 6 mode on
exit
!
interface Te1/0/41
channel-group 7 mode on
exit
!
interface Te1/0/42
channel-group 7 mode on
exit
!
interface Te1/0/43
channel-group 5 mode on
exit
!
interface Te1/0/44
channel-group 5 mode on
exit
!
interface Te1/0/47
channel-group 47 mode on
exit
!
interface Te1/0/48
channel-group 48 mode on
exit
!
interface Te2/0/1
switchport access vlan 2
exit
!
interface Te2/0/2
switchport access vlan 2
exit
!
interface Te2/0/3
switchport access vlan 2
exit
!
interface Te2/0/4
switchport access vlan 2
exit
!
interface Te2/0/5
switchport access vlan 2
exit
!
interface Te2/0/6
switchport access vlan 2
exit
!
interface Te2/0/7
channel-group 1 mode on
exit
!
interface Te2/0/8
channel-group 1 mode on
exit
!
interface Te2/0/9
channel-group 2 mode on
exit
!
interface Te2/0/10
channel-group 2 mode on
exit
!
interface Te2/0/11
channel-group 11 mode on
exit
!
interface Te2/0/12
channel-group 12 mode on
exit
!
interface Te2/0/13
channel-group 13 mode on
exit
!
interface Te2/0/14
channel-group 14 mode on
lacp port-priority 65535
exit
!
interface Te2/0/15
channel-group 15 mode on
lacp port-priority 65535
exit
!
interface Te2/0/16
channel-group 16 mode on
lacp port-priority 65535
exit
!
interface Te2/0/17
channel-group 17 mode on
lacp port-priority 65535
exit
!
interface Te2/0/18
channel-group 18 mode on
lacp port-priority 65535
exit
!
interface Te2/0/19
channel-group 19 mode on
lacp port-priority 65535
exit
!
interface Te2/0/20
channel-group 20 mode on
exit
!
interface Te2/0/21
channel-group 21 mode on
exit
!
interface Te2/0/22
channel-group 22 mode on
exit
!
interface Te2/0/23
channel-group 23 mode on
exit
!
interface Te2/0/24
channel-group 24 mode on
exit
!
interface Te2/0/25
channel-group 3 mode on
exit
!
interface Te2/0/26
channel-group 3 mode on
exit
!
interface Te2/0/27
channel-group 4 mode on
exit
!
interface Te2/0/28
channel-group 4 mode on
exit
!
interface Te2/0/39
channel-group 6 mode on
description "Stack 1 LAG"
spanning-tree portfast
spanning-tree guard loop
exit
!
interface Te2/0/40
channel-group 6 mode on
exit
!
interface Te2/0/41
channel-group 7 mode on
exit
!
interface Te2/0/42
channel-group 7 mode on
exit
!
interface Te2/0/43
channel-group 5 mode on
exit
!
interface Te2/0/44
channel-group 5 mode on
exit
!
interface Te2/0/47
channel-group 47 mode on
exit
!
interface Te2/0/48
channel-group 48 mode on
exit
!
interface port-channel 6
gvrp enable
exit
!
interface port-channel 47
switchport access vlan 2
exit
//N1524P Config//
configure
vlan 2
exit
vlan 2
name "xxxxxx Network"
exit
snmp-server location "xxxxxx"
hostname "xxxxxx Stack 1"
sntp unicast client enable
sntp server 192.168.140.253
clock summer-time recurring USA
clock timezone -6 minutes 0
stack
member 1 2 ! N1524P
member 2 2 ! N1524P
member 3 2 ! N1524P
member 4 2 ! N1524P
exit
no ip domain-lookup
logging email
logging email from-addr SkyStack1@dell.com
logging email message-type urgent to-addr xxxxxx@xxxxxx.com
mail-server "192.168.0.134"
exit
boot auto-copy-sw
ip routing
interface vlan 1
ip address 192.168.143.2 255.255.248.0
exit
interface vlan 2
ip address 192.168.2.3 255.255.255.0
exit
ip route 0.0.0.0 0.0.0.0 192.168.143.254
username "admin" password xxxxxx privilege 15 encrypted
flowcontrol receive off
no spanning-tree
application install SupportAssist auto-restart start-on-boot
application install hiveagent start-on-boot
!
interface port-channel 1
gvrp enable
exit
snmp-server engineid local 800002a203141877e0fb79
no hiveagent
exit
WillG354
1 Rookie
•
10 Posts
0
June 19th, 2018 16:00
Well, part of my confusion was on the OOB interface. My understanding from the docs is that it was the only way to configure the switch. I have that all corrected now. As far as spanning tree goes right now, it is off because I am converting an old network over to fiber and I apparently had too many hops in the old way and spanning tree was completely stopping the core switches. The only way to get them running again was to shut it down. In my current configuration all other switches are connected direct to the core so I will not exceed the hops.
So if Vlan 1 is my untagged do I have to set Vlan 2 to tagged?
WillG354
1 Rookie
•
10 Posts
0
June 27th, 2018 08:00
so I am working on the left switch and the core that is in my diagram. I had the left switch preconfigured and added it into the system. I ran the following command and it started pinging the switch using the 192.168.143.9 IP address.
interface Te1/0/47
channel-group 47 mode active
exit
interface Te2/0/47
channel-group 47 mode active
exit
interface port-channel 47
switchport mode trunk
switchport trunk allowed vlan add 2
exit
when I try to connect(computer to server) on the 192.168.2.0 network from the left switch to the core I can't connect.
WillG354
1 Rookie
•
10 Posts
0
June 27th, 2018 10:00
I have ports 1 through 6 on the left switch for vlan2. On the core switches I have ports 1 through 6 set for Vlan 2. The IP for the computer is 192.168.2.200 and the server is 192.168.2.148
other than putting them into Vlan2, I have no other config yet.
WillG354
1 Rookie
•
10 Posts
0
June 30th, 2018 19:00
ok, here is where I am at. I have routes set up but am unable to cross vlans. Here is what is configured. I can ping from the core to the attached routers but am unable to ping from any of the switches which are on 192.168.143.xxx to the 192.168.2.1
Core(config)#show ip route
Route Codes: R - RIP Derived, O - OSPF Derived, C - Connected, K - Kernel, S - S
tatic
B - BGP Derived, E - Externally Derived, IA - OSPF Inter Area
E1 - OSPF External Type 1, E2 - OSPF External Type 2
N1 - OSPF NSSA External Type 1, N2 - OSPF NSSA External Type 2
S U - Unnumbered Peer, L - Leaked Route, T - Truncated ECMP Route
* Indicates the best (lowest metric) route for the subnet.
Default Gateway is 192.168.2.1
K *0.0.0.0/0 [1/0] via 192.168.2.1, 29d:08h:22m, Vl2
C *192.168.2.0/24 [0/0] directly connected, Vl2
C *192.168.136.0/21 [0/0] directly connected, Vl1
WillG354
1 Rookie
•
10 Posts
0
July 3rd, 2018 15:00
I am only at the point of trying to cross vlans in the core.
my computer is 192.168.140.221
core switch vlan1 is 192.168.143.1 (I can ping)
core switch vlan2 is 192.168.2.2 (I can not ping)
I think my routes look right so I do not know if I am missing something else.
WillG354
1 Rookie
•
10 Posts
0
August 11th, 2018 13:00
I finally got everything done except for turning spanning tree back on. you have been a big help. thanks.
one last question. I got the email working. my routes were good the whole time. I just missed enabling some of the switches for email. I am sending ok but they continue to increment the failed email count. is there a way to clear out the old stuck emails other than rebooting? this would give me clear logs.
WillG354
1 Rookie
•
10 Posts
0
August 11th, 2018 18:00
Well, I take that back. even though I tested the email and it worked, it has now stopped working which is why I am still seeing the errors. out of 15 switch stacks, 4 are working and have clear log files. all of the stacks have identical configurations. not sure why the rest are not working.
WillG354
1 Rookie
•
10 Posts
0
August 14th, 2018 07:00
I figured out the problem but I do not understand why it affected it. on the switches that did not send email GVRP was enabled on the LAG that connects them to the core switch. once that was disabled I also had to reset the stack and everything works.
So on the ones that I have fixed I have received a few alerts over this weekend. when I look in the logs I am still getting the email fail counter incrementing every 30 minutes.