UNSOLVED

asidko

updated

18 years ago

A

asidko

8 Posts

0

24333

May 23rd, 2008 22:00

DELL powerconnect Inter VLAN routing by Cisco 72xx

Hello.

 

I have switch Dell powerconnect 5448 and router Cisco 7200. I want to create VLANs and perform VLAN routing by Cisco.

This is my cisco router configuration:

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

interface GigabitEthernet0/3
 no ip address
 duplex auto
 speed auto
 media-type rj45
 negotiation auto
!
interface GigabitEthernet0/3.2
 encapsulation dot1Q 2
 ip address 10.2.2.2 255.255.255.0
!
interface GigabitEthernet0/3.3
 encapsulation dot1Q 3
 ip address 10.3.3.3 255.255.255.0
!

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

 

I connected dell switch port g44 to Cisco router Gi 0/3 port. I want switch port g44 to work as trunk.

Also I want port g2 belongs to VLAN 2 and port g3 belongs to VLAN 3 accordingly. so my switch configuration is:

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

config
vlan database
vlan 2-3
exit
interface ethernet g2
switchport mode access
switchport access vlan 2
exit
interface ethernet g3
switchport mode access
switchport access vlan 3
exit

interface ethernet g44
switchport mode trunk
switchport trunk allowed vlan add 2-3
exit

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

 

after that I tied to ping host belongs to VLAN 2 (10.2.2.3) from host belongs to VLAN 3 (10.3.3.4)

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

root@ant:/home/andrew# ping -Ieth1:0 10.2.2.3
PING 10.2.2.3 (10.2.2.3) from 10.3.3.4 eth1:0: 56(84) bytes of data.
From 10.3.3.4 icmp_seq=1 Destination Host Unreachable
From 10.3.3.4 icmp_seq=2 Destination Host Unreachable
From 10.3.3.4 icmp_seq=3 Destination Host Unreachable

--- 10.2.2.3 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3009ms
, pipe 3
root@ant:/home/andrew#

 

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

 

The same situation I see when I tried to ping host from switch

------------------
User Name:admin
Password:***********


console# ping 10.2.2.3
Pinging 10.2.2.3 with 56 bytes of data:

PING: no reply from 10.2.2.3
PING: timeout
PING: no reply from 10.2.2.3
PING: timeout
PING: no reply from 10.2.2.3
PING: timeout
PING: no reply from 10.2.2.3
PING: timeout

----10.2.2.3 PING Statistics----
4 packets transmitted, 0 packets received, 100% packet loss

console#

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

Router interface from switch console I can ping (wrunk is working)

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

console# ping 10.2.2.2
Pinging 10.2.2.2 with 56 bytes of data:

56 bytes from 10.2.2.2: icmp_seq=1. time=0 ms
56 bytes from 10.2.2.2: icmp_seq=2. time=0 ms
56 bytes from 10.2.2.2: icmp_seq=3. time=0 ms
56 bytes from 10.2.2.2: icmp_seq=4. time=0 ms

----10.2.2.2 PING Statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0

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

 

Can somebody give me an advice. What's wrong?

 

Thank you.

  • asidko

    8 Posts

    400

    0

    Posted May 23rd, 2008 22:00

    Forget.

    In seems to me trunk doesen't work because when I'm pinging from host 10.2.2.3 belongs to VLAN2 its Default gateway 10.3.3.3 I got only this:

     

    root@ant:/home/andrew# ping -Ieth1:0 10.2.2.2
    PING 10.3.3.3 (10.3.3.3) from 10.3.3.4  56(84) bytes of data.
    From 10.3.3.4 icmp_seq=2 Destination Host Unreachable
    From 10.3.3.4 icmp_seq=3 Destination Host Unreachable
    From 10.3.3.4 icmp_seq=4 Destination Host Unreachable

    --- 10.2.2.2 ping statistics ---
    4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms
    , pipe 3
    root@ant:/home/andrew#

    Could you explaine me?

     

    Thanks.

  • 400

    0

    Posted May 26th, 2008 21:00

    Can you first check that your trunk is actually up, and the Cisco router view of world :

     

    Cisco-router#  show ip int brief

     

    Cisco-router# show interface gig0/3

     

    Then with one of your hosts attached in the relevant VLAN.....form the router try

     

    Cisco-router# ping 10.2.2.4 

    Cisco-router# ping 10.3.3.4

     

     

  • asidko

    8 Posts

    400

    0

    Posted May 26th, 2008 22:00

    I checked out router interfaces. This is output:

    gate#sh ip int bri
    Interface                  IP-Address      OK? Method Status                Protocol
    GigabitEthernet0/1         xxx.xxx.xxx.xxx  YES NVRAM  up                    up
    FastEthernet0/2            unassigned      YES NVRAM  administratively down down
    GigabitEthernet0/2         xxx.xxx.xxx.xxx      YES manual up                    up
    GigabitEthernet0/2.1       unassigned      YES NVRAM  deleted               down
    GigabitEthernet0/2.2       unassigned      YES manual deleted               down
    GigabitEthernet0/2.3       unassigned      YES manual deleted               down
    GigabitEthernet0/2.4       unassigned      YES manual deleted               down
    GigabitEthernet0/2.5       unassigned      YES manual deleted               down
    GigabitEthernet0/3         unassigned      YES NVRAM  up                    up
    GigabitEthernet0/3.2       10.2.2.2        YES manual up                    up
    GigabitEthernet0/3.3       10.3.3.3        YES manual up                    up
    Virtual-Access1            unassigned      YES unset  down                  down
    gate#
     ----------------------------------

     gate#sh ip int gi 0/3
    GigabitEthernet0/3 is up, line protocol is up
      Internet protocol processing disabled
    gate#
    -----------------------------------

    gate#ping 10.2.2.3

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 10.2.2.3, timeout is 2 seconds:
    .....
    Success rate is 0 percent (0/5)
    gate#ping 10.3.3.4

    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 10.3.3.4, timeout is 2 seconds:
    .....
    Success rate is 0 percent (0/5)
    gate#
    ---------------------------------

     

    Dosen't work. Magik.

    Actually maybe dell has defferent model/syntax of define trunk  than cisco? Frankly speeling I didn't work with dell before.

     

    Do you have any idea? For example why dell has many different types of trunk? (acces, general, customer)?

     

    Thank you. 

  • 400

    0

    Posted May 26th, 2008 22:00

    I think its the Dell trunking or tagging thats stopping this from working :

     

    Can you try this on your Dell trunk port

     

    switchport allowed vlan add 2-3  tagged

  • asidko

    8 Posts

    400

    0

    Posted May 27th, 2008 20:00

    Unfortunately it dosen't work.

    When I entered 'tagging' command I got error:

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

    console(config-if)# switchport trunk allowed vlan add 2-3 tagged
    % Wrong number of parameters or invalid range, size or characters entered

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

     

    Maybe I have to define 'tagging' before?

     

    Andrew.