Re: native vlan for mgmt



Yes, I dont have access to my router/switch configuration at the moment and I done this before and had no problem

My configuration is as follows

I have a router with the fa0/0 configured with sub interfaces my mgmt vlan 100 10.1.10.0/24

router

int fa0/0
no ip address

int loop0 10.1.254.1 255.255.255.255

int fa0/0.100
encap dot1x 100
ip address 10.1.10.1 255.255.255.0
..
..
..
int fa0/0.900
enca dot1x 900
ip address 192.168.1.254 255.255.255.0

router eigrp 19
network 10.0.0.0
auto-summary

ip route 0 0 192.168.1.1



switch

vtp domain MAIN-HQ
vtp mode transparent

vlan 100
name MGTM-VLAN100
..
..
..
vlan 900
name INTERNET-VLAN

int fa0/24
switchport
switchport mode trunk
switchport trunk native vlan 100
switchport trunk all vlan add 100, 200, 300, 400, 900

ip default-gateway 10.1.10.1

int vlan 1
shut

int vlan 100
ip address 10.1.10.15 255.255.255.0

My data and voice vlans are working fine and the phones and laptops are replying and I can http into the 7960's.

I cannot telnet to the switch or ping the switch on 10.1.10.15 or the router 10.1.10.1 from my workstation, router, or switch. If i am on the router and try to ping the 10.1.10.15 address of the switch I get no reply and not able to telnet to it. I can only telnet to the loop0 interface which is what I want, but I cannot access the switch via the mgmt ip address.

All other vlans and subnet works fine and the phones get their ip address from the router which is a 1760-V running advanceservices and cme 4.1 the switch is a 2940 Enhanced Image.







"Trendkill" <jpmason@xxxxxxxxx> wrote in message news:5c4f3f12-2e47-470f-8e78-17fe71bb7594@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jul 18, 9:20 pm, "swpa" <s...@xxxxxxxxxxxxxxxxxxx> wrote:
I configured two routers each with a trunk port up to a switch. I have
created subinterface and .1q trunking on the sub interfaces and have trunk
mode set on the switch port with the native vlan set for the vlan I am using
for the management vlan. I set the default gateway on the switch to the L3
address of the vlan interface on the router. I set an ip address on the int
vlan on the switch on the management vlan subnet. I am unable to telnet or
ping to the switches ip address on the management vlan. What am I missing?

The default gateway on the switch is only used for the management
interface. So just to be sure I understand what you have done, your
switch should have an IP in the mgmt vlan, and its gateway should be
the router interface in the mgmt vlan. The rest of the vlans on the
switch are layer 2 and no routing or default gateway statements are
needed for those (at least on the switch side). Also make sure that
the trunks are up and trunking, and you can see all the vlans on the
switch, particularly the one you have designated as the 'mgmt' vlan.

.



Relevant Pages

  • Re: Help configuring Point-To-Point T1
    ... that you could have a VLAN that spans across both offices? ... 1700 series router w/ Internet T1 ... 3560 Switch ... because you wouldn't have to worry about tons of static routes. ...
    (comp.dcom.sys.cisco)
  • Re: probably an easy routing question, so please help
    ... non-contiguous subnets into one VLAN and avoid having to run out to the ... router for intra-VLAN traffic, ... VLAN capable Layer 2 switches ignore VLAN tags on unicast traffic. ... A Layer 3 switch can route intraVLAN/interVLAN unicast traffic AS ...
    (comp.dcom.sys.cisco)
  • RE: Different terms for the same or more secure?
    ... On a switch, each port is its own collision domain, unlike ... a broadcast does not traverse a router unless explicitly told ... is more accurate to say a VLAN separates broadcast domains. ... "creates" a broadcast domain, which inherently separates itself from the ...
    (Security-Basics)
  • Re: native vlan for mgmt
    ... I have a router with the fa0/0 configured with sub interfaces my mgmt vlan ... : int fa0/0 ... To complete a "Router on a Stick" Configuartion with VLAN 100 as the ... I cannot telnet to the switch or ping the switch on 10.1.10.15 or the router ...
    (comp.dcom.sys.cisco)