|
Posted by Dave_T on January 20, 2006, 4:00 am
If you were Registered and logged in, you could reply and use other advanced thread options
Just wondering if anyone knew whether there was a way to (temporarily)
change the default behaviour for a 6500 running native IOS (V12), with
regards to the way in which the routed VLAN interface is handled when
there are no active devices in the VLAN...
That is, deafult behaviour is to not bring up the routed VLAN interface
if there are no active VLAN ports. But if you are creating a VLAN at a
remote site in preparation for something, you might have scheduled the
work to be out of hours to minimise risk/disruption, and want the VLAN
interface to come up so that any routing table changes kick in
immediately - so you can see that there are no issues. Having re-assured
yourself that the normal dynamic routing changes associated with the
VLAN interface going up/down are seamless and non-disruptive, and once a
real active device goes onto the VLAN, you could switch back to default
behaviour, so that if the last device on the VLAN does indeed go down,
the route gets (transparently) withdrawn.
Or any other suggestions about "workarounds" to temporarily fool the
switch into thinking that there is an active port, when there is not
(physically).
Ta,
|
|
Posted by Andrey Tarasov on January 25, 2006, 7:23 pm
If you were Registered and logged in, you could reply and use other advanced thread options
Hello, Dave_T!
You wrote on Fri, 20 Jan 2006 09:00:24 +0000 (UTC):
DT> Just wondering if anyone knew whether there was a way to
DT> (temporarily) change the default behaviour for a 6500 running
DT> native IOS (V12), with regards to the way in which the routed
DT> VLAN interface is handled when there are no active devices in the
DT> VLAN...
http://www.cisco.com/en/US/products/hw/switches/ps700/products_tech_note09186a0080160b14.shtml#topic1
...
Autostate is implemented on CatOS and IOS Cisco based switches by default. On
some CatOS platforms, this feature can be disabled in order to allow redundancy
in special scenarios. On IOS based switches, this feature cannot be disabled.
...
With best regards,
Andrey.
|
|
Posted by on January 26, 2006, 5:47 am
If you were Registered and logged in, you could reply and use other advanced thread options
DT> (temporarily) change the default behaviour for a 6500 running
DT> native IOS (V12), with regards to the way in which the routed
DT> VLAN interface is handled when there are no active devices in the
DT> VLAN...
You could perhaps force a spare port up somehow.
e.g.
Plug something in.
Plug it into itself? (if you had two spare ports) (Tin hat on)
Maybe on a spare port you could get it to come 'up'
with "no keepalive"?
Put the address on a loopback interface temporarily.
This would allow you to check out the routing.
|
| Similar Threads | Posted | | Cat 6500 - weird boot behaviour | May 3, 2006, 1:41 am |
| True routed interfaces for a 6500 switch? | March 8, 2006, 10:31 pm |
| Get Interface stats NOT VLAN stats on 6500 | July 3, 2006, 7:14 am |
| Routed interface redundancy | May 21, 2006, 12:21 am |
| VLAN across a routed connection? | September 15, 2007, 3:13 am |
| Trunking vlan on 6500-Help Please. | August 17, 2006, 6:29 pm |
| VLAN trunk between Cat 6500 and Force 10 S50 | May 7, 2007, 12:07 am |
| Configuring VLAN in 6500 Switch | July 27, 2007, 4:44 pm |
| Default route using interface not next-hop on LAN | March 2, 2005, 6:39 am |
| Can't set default route to outside interface | May 29, 2008, 10:12 pm |
|
|
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML site map