Start a Conversation

Unsolved

This post is more than 5 years old

21112

May 15th, 2015 05:00

Campus over SM fiber 10g - with powerconnect 6224f ?

Hi there


we are trying to connect two of dell powerconnect 6224f over sm fiber.

dell-elfak(160.99.8.2) <----10g fiber------->(160.99.8.1)dell-junis(160.99.1.31)<----copper---> (160.99.1.12)gateway

(160.99.7.11)
|
|
copper
|
|
cisco-remote campus

(160.99.7.1)                   


Configurations are in attachment. for both dell switches.

The problem is that from network 160.99.1.x i can ping and trace route all the devices - all the time- but web and telnet access to 160.99.8.1 and 160.99.8.2 is not working all the time!!!



Would you be so kind to help us debug this situation?
Is it possible at all to do this with the powerconnect switches?!



Kind regards

Marko Živković
head of IT
Unviersity of Niš

10g dell_JUNIS configuration

______________________________________________________________________________


!Current Configuration:
!System Description "PowerConnect 6224F, 3.3.12.1, VxWorks 6.5"
!System Software Version 3.3.12.1
!Cut-through mode is configured as disabled
!
configure
gvrp enable
vlan database
vlan 2,36,100
vlan routing 2 1
vlan routing 100 2
vlan routing 36 3
exit
hostname "10GB_junis"
sntp unicast client enable
sntp server 147.91.8.77
clock timezone 1 minutes 0 zone "UTC"
stack
member 1 3
exit
ip address none
ip domain-name junis.ni.ac.rs
ip name-server 160.99.1.1
logging console debug
logging file debug
logging buffered warning
access-list proba deny ip any 160.99.8.2 255.255.255.252 log
ip routing
ip route 0.0.0.0 0.0.0.0 160.99.1.12
ip route 0.0.0.0 0.0.0.0 160.99.8.11
ip route 160.99.7.0 255.255.255.0 160.99.8.2
router rip
split-horizon none
no hostroutesaccept
default-metric 1
redistribute connected metric 1
redistribute static metric 1
exit
interface vlan 2
name "Veza_JUNIS"
routing
ip address 160.99.1.31 255.255.255.0
exit
interface vlan 36
name "10GB_optika"
routing
ip address 160.99.36.1 255.255.255.0
bandwidth 100000
ip mtu 1500
exit
interface vlan 100
name "10giga"
routing
ip address 160.99.8.1 255.255.255.0
ip netdirbcast
bandwidth 10000000
no ip proxy-arp
ip local-proxy-arp
ip mtu 1500
exit

line telnet
exec-timeout 30
exit
no flowcontrol
no spanning-tree
!
interface ethernet 1/g1
shutdown
switchport mode general
switchport general pvid 100
exit
!
interface ethernet 1/g2
switchport access vlan 2
exit
!
interface ethernet 1/g21
description "abc"
switchport access vlan 2
exit
!
interface ethernet 1/g23
spanning-tree portfast
exit
!
interface ethernet 1/g24
ip arp inspection trust
description "VezaJUNIS"
gvrp enable
switchport mode general
switchport general pvid 2
switchport general ingress-filtering disable
switchport general allowed vlan add 2,100 tagged
switchport general allowed vlan remove 1
dot1x unauth-vlan 100
exit
!
interface ethernet 1/xg1
spanning-tree portfast
switchport mode general
switchport general pvid 100
switchport general allowed vlan add 100
switchport general allowed vlan remove 1
vlan priority 7
exit
exit

10GB_junis#

______________________________________________________________________________

10g dell_elfak configuration

!Current Configuration:
!System Description "PowerConnect 6224F, 3.3.12.1, VxWorks 6.5"
!System Software Version 3.3.12.1
!Cut-through mode is configured as disabled
!
configure
vlan database
vlan 8,33-34,36-38,100
vlan routing 8 1
vlan routing 100 2
vlan routing 36 3
vlan routing 37 4
vlan routing 38 5
vlan routing 34 6
vlan routing 33 7
exit
hostname "10GB_elfak"
sntp unicast client enable
sntp server 147.91.8.77
sntp server time.nist.gov
sntp server 160.99.1.12

clock timezone 2 minutes 0
stack
member 1 3
exit
ip address none
ip domain-name junis.ni.ac.rs
ip name-server 160.99.1.1
ip name-server 8.8.8.8
logging console debug
logging file debug
logging buffered debug
no diffserv
ip routing
ip route 0.0.0.0 0.0.0.0 160.99.8.1
ip route 160.99.1.0 255.255.255.0 160.99.8.1
arp dynamicrenew
no ip helper enable
router rip
no enable
split-horizon none
no hostroutesaccept
default-metric 1
redistribute connected metric 1
redistribute static metric 1
exit
interface vlan 8
routing
ip address 160.99.7.11 255.255.255.0
ip rip send version rip1
ip rip receive version both
exit
interface vlan 33
routing
ip address 160.99.33.254 255.255.255.0
exit
interface vlan 34
routing
ip address 160.99.34.101 255.255.255.0
exit
interface vlan 36
routing
ip address 160.99.36.2 255.255.255.0
ip rip send version rip1
ip rip receive version rip1
exit
interface vlan 37
routing
ip address 160.99.37.11 255.255.255.0
exit
interface vlan 38
routing
ip address 160.99.38.129 255.255.255.224
exit
interface vlan 100
routing
ip address 160.99.8.2 255.255.255.0
ip rip send version rip1
ip rip receive version both
exit

line console
speed 115200

exit
line telnet
exec-timeout 15
exit
ip ssh server
no spanning-tree
spanning-tree mode stp
!
interface ethernet 1/g1
gvrp enable
switchport mode trunk
switchport trunk allowed vlan add 8,36
exit
!
interface ethernet 1/g5
switchport access vlan 8
exit
!
interface ethernet 1/g7
switchport access vlan 8
exit
!
interface ethernet 1/g9
switchport access vlan 33
exit
!
interface ethernet 1/g15
switchport access vlan 34
exit
!
interface ethernet 1/g21
switchport access vlan 34
exit
!
interface ethernet 1/g22
switchport access vlan 8
exit
!
interface ethernet 1/g23
switchport access vlan 37
exit
!
interface ethernet 1/g24
switchport access vlan 38
exit
!
interface ethernet 1/xg1
description "KaJUNISu"
spanning-tree portfast
switchport mode general
switchport general pvid 100
switchport general allowed vlan add 100
switchport general allowed vlan remove 1
exit
exit

10GB_elfak#

____________________________________________________________________________

5 Practitioner

 • 

274.2K Posts

May 15th, 2015 11:00

The 6200 switches are not able to route their own management VLAN, which by default is VLAN 1. This could be part of the problem. Are you able to Telnet to the switches from within 160.99.8.x? From 160.99.1.x are you able to telnet to 160.99.1.31?

10 Posts

May 15th, 2015 12:00

Yes I can telnet to the x.x.1.31 and also to x.x.7.11. . But not to x.x.8.1 and .2.  But when I telnet to x.x.1.31 I can telnet to x.x.8.2.

What do you suggest?

10GB_junis#show vlan 

VLAN       Name                         Ports          Type      Authorization

-----  ---------------                  -------------  -----     -------------

1      Default                         ch1-48,1/g1,   Default   Required     

                                            1/g3-1/g20,

                                            1/g22-1/g23,

                                            1/xg2-1/xg4

2      Veza_JUNIS               1/g2,1/g21,    Static    Required     

                                            1/g24

36     10GB_optika                                    Static    Required     

100    10giga                      1/g24-1/xg1    Static    Not Required 

5 Practitioner

 • 

274.2K Posts

May 15th, 2015 12:00

Yeah it sounds like the Management VLAN limitation. Could you Please be more specific about "when I telnet to x.x.1.31 I can telnet to x.x.8.2." Are you saying once you telnet to to a different IP you can then simultaneously open another telnet session to 160.99.8.1?

10 Posts

May 15th, 2015 12:00

Sorry for not explaining it ok.

When i telent to first switch - from there i can telnet to the other one (x.x.8.2).

10 Posts

May 15th, 2015 12:00

But i can telnet directly from x.x.1.x to x.x.7.11

5 Practitioner

 • 

274.2K Posts

May 15th, 2015 13:00

Here is a KB articles that talks about routing VLAN 1.

http://dell.to/1FiQhu7

The behavior you are seeing seems to fit this scenario.

10 Posts

May 18th, 2015 03:00

This didnt help.

Still the same problem...

5 Practitioner

 • 

274.2K Posts

May 18th, 2015 06:00

What changes were made and to which switch?

10 Posts

May 19th, 2015 02:00

I tried this http://dell.to/1FiQhu7

You can find both configs in attachment.

1 Attachment

5 Practitioner

 • 

274.2K Posts

May 19th, 2015 13:00

Thanks for the current configs. Their are a couple of static routes in place, that I am not certain why they are present, but I don't think they would affect this situation. If you connect to the cli of switch 160.99.8.1, can you ping 160.99.8.2? From the 160.99.8.1 CLI can you telnet to 160.99.8.2? Instead of using terminal software.

No Events found!

Top