[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

686.0. "Disable Port 0 on a 90C?" by CGOS01::DMARLOWE (dsk dsk dsk (tsk tsk tsk)) Thu Feb 03 1994 12:13

    When using MOP to a DB90 you are able to disable Port 0 on a 90T
    and 90C repeater.  How can this be done thru the DECagent.
    
    I need to group 10BaseT users onto 9xxC (for now only 90C available)
    and feed them their own 10Mb.  But that means disabling Port 0 so
    the modules aren't connected to a common 10Mb thinwire in the chassis.
    
    Any suggestions?
    dave
T.RTitleUserPersonal
Name		DateLines
686.1Can't do it with a DECagent, only via MOP to the bridgeNAC::FORRESTMon Mar 07 1994 14:3716
	The DECagent 90 MIB doesn't support port 0. I'm not sure that 
	SNMP's syntax allows an index value of 0. I suppose it could have 
	been implemented as port 9 (on a DECMR), but it never was.

	drpt90PortIndex OBJECT-TYPE
        SYNTAX  INTEGER (101..1608)
        ACCESS  read-only
        STATUS  mandatory
        DESCRIPTION
         "Identifies the module and port.  The value of this object is given by:

                (slot number*100) + port number"

    ::= { drpt90PortEntry 1 }
686.2got my repeaters mixed upNAC::FORRESTMon Mar 07 1994 14:382
	Oops that should have said (on a DETMR)!
686.3Thanks.CGOS01::DMARLOWEHave you been HUBbed lately?Tue Mar 08 1994 00:285
    Well it would be port 9 for a 90T, port 7 for a 90C and port 33
    for a 900TM and .......  People are confused enough now.  Anyways 
    I'll create a solution to my problem later.

    dave