[j-nsp] Interfaces, deactivate vs disable

[Harry Reynolds]

AFAIK, we have sticky SNMP index values as they are written to a file.
Unless new HW is added, or pics are moved, I think the index will stay
the same. Also, IMO deactivate is not the same as pulling the card. With
no card the interface is not listed in a show interface. With
deactivate, it is listed but as if there was no configuration.
Deactivating will cause any logical units/sub interfaces to
disappear....

Cheers


 

> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net 
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Eric Van Tol
> Sent: Wednesday, June 08, 2005 8:26 AM
> To: Raymond, Steven; juniper-nsp at puck.nether.net
> Subject: RE: [j-nsp] Interfaces, deactivate vs disable
> 
> Disable is especially useful in the case of monitoring.  
> Deactivate removes the interface from the config (same as 
> physically pulling the card out), rendering a previously 
> monitored (SNMP, etc.) port or interface "gone", thereby 
> causing alarms in your monitoring station.
> Reactivation, if I am correct, could cause the SNMP-index 
> number to change, thereby requiring a change in the NMS(es).
> 
> Disabling just disables the interface (shutdown), which still 
> provides your NMS a point to monitor, albeit zero traffic on 
> that interface.
> 
> In addition, if you are an NSP, you may have customers that 
> move from one medium to another on the same router.  The 
> ability to deactivate can offer you the option of 
> pre-building the configuration of the interface if they want 
> to keep the same IPs.
> 
> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of 
> Raymond, Steven
> Sent: Wednesday, June 08, 2005 11:17 AM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] Interfaces, deactivate vs disable
> 
> I don't quite understand the difference between deactivate 
> and disable on an interface, from below:
> 
> <https://www.juniper.net/techpubs/software/junos/junos60/swcon
> fig60-gett
> ing-started/html/cli-configuration-mode43.html>
> 
> "In some portions of the configuration hierarchy, you can 
> include a disable statement to disable functionality. One 
> example is disabling an interface by including the disable 
> statement at the [edit interface interface-name] hierarchy 
> level. When you deactivate a statement, that specific object 
> or property is completely ignored and is not applied at all 
> when you issue a commit command. When you disable a 
> functionality, it is activated when you issue a commit 
> command but is treated as though it is down or 
> administratively disabled."
> 
> Can anyone please give an example of where it would be better 
> to use either of disable or deactivate, specifically as it 
> pertains to downing an interface?
> 
> Thanks
> 
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> http://puck.nether.net/mailman/listinfo/juniper-nsp
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>