From: Oliver Ziltener (ziltener@netcloud.ch)
Date: Tue Jun 03 2003 - 17:20:05 GMT-3
Hello
Sup IV in the 4506/7R can use the managment port only for deaster
recovery(boot up sequenze, for download IOS)
and is not accessible during normal operation!
Oliver
-----Urspr|ngliche Nachricht-----
Von: MADMAN [mailto:dave@interprise.com]
Gesendet: Dienstag, 3. Juni 2003 20:30
An: Mhlanga Libone
Cc: ccielab@groupstudy.com
Betreff: Re: 4506 on 12.1(12c)EW - mgmt interface ??
Since you say there is no catOS I assume you have a supIII or IV, no
MSFC so I don't know what you mean about hoping into the MSFC. Don't
know what you mean about the trunk, you don't configure a trunk between
the L2 and L3 unless you have a supII and a seperate L3 blade. I don't
think I see the big picture.
There is nothing special to do, configure an interface vlan x so long
as x is a valid VLAN and it works.
The "management" VLAN here is 64:
C4006SUPIII#sh ip int bri
Interface IP-Address OK? Method Status
Prot
ocol
Vlan1 unassigned YES NVRAM up
up
Vlan64 172.28.64.40 YES NVRAM up
up
Dave
Mhlanga Libone wrote:
> For the life of me I CANNOT find any way of configuring the mgmt interface
> on any vlan other than vlan 1.
>
> Documentation says you can put the management interface in any vlan as long
> as there are access ports in that vlan. So I tried putting it in vlan 17 as
> I have 42 devices in that vlan ....then put a default route pointing to the
> msfc with trunking between the two....still no joy. Although I can reach
the
> 4506 by first hoping onto the msfc but no access from anywhere else. The
> attached hosts are fine they can talk to anything ..its just the switch
> mgmt....why get rid of CatOS I ask ??
-- David Madland CCIE# 2016 Sr. Network Engineer Qwest Communications 612-664-3367"Government can do something for the people only in proportion as it can do something to the people." -- Thomas Jefferson
This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:10:52 GMT-3