| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 785.1 | depends on the protocol | MARVIN::HART | Tony Hart, InterNetworking Prod. Eng. Group | Thu Mar 06 1997 12:44 | 7 | 
|  | The cost of a circuit depends on the routing protocol you're using, for OSPF
you would use the "OSPF Config>set interface .....".  If you're running RIP
then you're out of luck since it uses hop-counts rather than metrics.
Why do you want to change the cost ?  
Tony
 | 
| 785.2 | I use RIP and I need to setup a interf. metric | 21272::THR_CHICO |  | Thu Mar 06 1997 14:32 | 24 | 
|  |     
    Hi,
    
    Thanks for the answer,
    
    I really need to change the cost of one interface in DECswitch. I use
    RIP. I have a lot of routers and I can do it in all of them. Why can't I
    do that on DECswitch ??
    
    I need it because I have the DECswitch connected in 3 networks ( FDDI,
    Ethernet and Hub's backplane). If another station that is connected to
    the same FDDI and Ethernet sends an IP message to a station connected to 
    the backplane the message goes to ETHERNET instead of FDDI. I want the
    message goes to FDDI, then to a DECswitch, then to a station connected
    in the backplane. I really dont't want to setup any statics routes.
    
    To implement it I will setup all machines, that are the gateways between 
    FDDI and Ethernet, to have metric 1 on Ethernet and metric 0 on FDDI.
    
    
    Thanks in advance,
    
    	Francisco.
         
 | 
| 785.3 |  | MARVIN::HART | Tony Hart, InterNetworking Prod. Eng. Group | Fri Mar 07 1997 05:53 | 6 | 
|  | Francisco,
	Unfortunately you can't change the RIP cost on an interface.  So you'd
have to use static routes (and tell RIP not to override them) or turn RIP
reception off on the Ethernet.
Tony
 | 
| 785.4 | what about the next release ? | 21272::THR_CHICO |  | Fri Mar 07 1997 07:56 | 13 | 
|  |     
    That's too bad !!
    
    Do you know if this feature will be available in a next release of this
    software ?
    
    My customer is really worry because He spent a Lot of money with this  
    hardware, and this hardware doesn't attend his needs !!!! :-(
    
    The IP router  implementation in DECswitch is poor in comparation with
    its price.
    
    Francisco   :-(
 | 
| 785.5 |  | MARVIN::HART | Tony Hart, InterNetworking Prod. Eng. Group | Fri Mar 07 1997 09:02 | 23 | 
|  | >    Do you know if this feature will be available in a next release of this
>    software 
	Its not in any plans.  The only way its likely to get in is if you
	make a formal request for the feature.
>    My customer is really worry because He spent a Lot of money with this  
>    hardware, and this hardware doesn't attend his needs !!!! :-(
>    
>    The IP router  implementation in DECswitch is poor in comparation with
>    its price.
	Please make of list of missing features and their importance to your
	customer and let the RouteABout/DECSwitch management know 
	or make a formal request for the features to be added.  You will
	probably have a better idea of what features are missing than most
	people in engineering.
	Out of interest can you tell me which of the Routers you're using
	support changing the RIP circuit cost ?
	Tony
 | 
| 785.6 | list of routers that support | 21272::THR_CHICO |  | Tue Mar 11 1997 08:08 | 15 | 
|  |     
    Routers that support changes in the circuit's cost :
    
    - All DECstation with OSF/1
    
    - HP routers ER
    
    - DEC wanrouter 250
    
    I will make my list of desirable features...
    
    Thanks for all..
    
    
    Francisco
 | 
| 785.7 |  | MARVIN::HART | Tony Hart, InterNetworking Prod. Eng. Group | Tue Mar 11 1997 08:21 | 4 | 
|  | Thanks for the info.  I notice Cisco isn't on the list, do you know if they
support changing the RIP cost ?
Tony
 | 
| 785.8 |  | MARVIN::CLEVELAND |  | Wed Mar 12 1997 03:03 | 8 | 
|  |     
>    - DEC wanrouter 250
    
    I don't remember WANrouter supporting this, but if it did then DECnis
    would have as well.  Note we're talking about changing the RIP cost of
    a circuit, not IS-IS metrics....
    
    
 | 
| 785.9 |  | MARVIN::HART | Tony Hart, InterNetworking Prod. Eng. Group | Wed Mar 12 1997 03:30 | 4 | 
|  | The DECNIS doesn't support it.  Also the only attribute in the ROUTING MSL that
comes close is "RIP Send Local Metric" but thats a ROUTING entity attribute
not a ROUTING CIRCUIT attribute so it won't help here anyway.
 | 
| 785.10 | the problem continues... | 21272::THR_CHICO |  | Thu Mar 13 1997 17:11 | 11 | 
|  |     
    Ok,
    
    When I talked about wan-router support for RIP cost I was thinking in
    "RIP Send Local Metric". I'm sorry ...
    
    The major problem is that DEcswitch EF has 6 interfaces ethernets and one
    FDDI and you can't say do him that the FDDI is more FAST !!! or you
    can't say to him that one interface ETHERNET is better then other :-(
    
    Francisco
 | 
| 785.11 | That's the way RIP is | MARVIN::HART | Tony Hart, InterNetworking Prod. Eng. Group | Fri Mar 14 1997 03:07 | 12 | 
|  | >    The major problem is that DEcswitch EF has 6 interfaces ethernets and one
>    FDDI and you can't say do him that the FDDI is more FAST !!! or you
>    can't say to him that one interface ETHERNET is better then other :-(
 
	This is a feature of RIP.  It doesn't use costs it uses hops, the
protocol assumes that all links are equal.  With a hop-limit of 16 you have
very little scope for assigning different values to a circuit.
	I would suggest either running OSPF or use static routes on one of the
interfaces to override the RIP routes.
Tony
 |