|
Sounds normal to me. Don't forget that "snmp interface" as defined
in mib-2 ( rfc 1213 ) means "tcp/ip interface" : and you don't have
6 tcp/ip interfaces in a DECconcentrator 900MX.
So you need to use specific mibs to display all the ports. Let's
assume that your concentrator is plugged in port #N of a DEChub 900
( so the read-only community is "public-N" ) and the MAM address
is something as x.x.x.x :
1/ To display the number of ports :
MCC> show snmp x.x.x.x fddi fddimib fddimibport fddimibPORTNumber , -
_MCC> by passw="public-N"
fddimibPORTNumber = 6
2/ To display a list of the ports :
MCC> show snmp x.x.x.x fddi fddimib fddimibport fddimibPORTTable *, -
_MCC> by passw="public-N"
Examination of attributes shows:
fddimibPORTTable_Index = ( 1,
1 )
Examination of attributes shows:
fddimibPORTTable_Index = ( 1,
2 )
...................
Examination of attributes shows:
fddimibPORTTable_Index = ( 1,
6 )
3/ And finally to display characteritics for a specific port :
MCC> show snmp x.x.x.x fddi fddimib fddimibport fddimibPORTTable (1,5)-
_MCC> all attributes, by passw="public-N"
fddimibPORTTable_Index = ( 1,
5 )
fddimibPORTConnectState = connecting
fddimibPORTPCMState = pc1
CounterCreationTime = 25-APR-1995 17:38:29.98
fddimibPORTLCTFailCts = 0
fddimibPORTLemRejectCts = 0
fddimibPORTLemCts = 0
fddimibPORTSMTIndex = 1
fddimibPORTIndex = 5
fddimibPORTMyType = m
fddimibPORTNeighborType = none
fddimibPORTConnectionPolicies = 0
fddimibPORTMACIndicated = tVal9FalseRVal9True
fddimibPORTCurrentPath = ce0
fddimibPORTRequestedPaths = %X000400
fddimibPORTMACPlacement = 0
fddimibPORTAvailablePaths = 1
fddimibPORTPMDClass = unspecified
fddimibPORTConnectionCapabilities = 0
fddimibPORTBSFlag = false
fddimibPORTLerEstimate = 15
fddimibPORTLerCutoff = 8
fddimibPORTLerAlarm = 8
fddimibPORTPCWithhold = none
fddimibPORTLerFlag = false
fddimibPORTHardwarePresent = true
fddimibPORTAction = other
On the other hand, you can of course register a DECrepeater 900FP as
a single entity ( means standalone or in a hub but not accessed through
the MAM ). Then you just need to use the repeater mib as follows :
MCC> show snmp Y.Y.Y.Y SNMPDOT3RPTRMGT RPTRBASICPACKAGE RPTRPORTINFO -
_MCC> RPTRPORTTABLE *
Examination of attributes shows:
rptrPortTable_Index = ( 1,
1 )
Examination of attributes shows:
rptrPortTable_Index = ( 1,
2 )
Examination of attributes shows:
rptrPortTable_Index = ( 2,
1 )
Examination of attributes shows:
rptrPortTable_Index = ( 2,
2 )
... and so on until (7,2). And to display a specific port :
MCC> sho snmp Y.Y.Y.Y SNMPDOT3RPTRMGT RPTRBASICPACKAGE RPTRPORTINFO -
_MCC> RPTRPORTTABLE (6,2) all attributes
rptrPortTable_Index = ( 6,
2 )
rptrPortAutoPartitionState = notAutoPartitioned
rptrPortOperStatus = operational
rptrPortGroupIndex = 6
rptrPortIndex = 2
rptrPortAdminStatus = enabled
Hope this helps,
Guy.
|
| Guy ,
My customer does the following MCC command that you gave as an
example:
MCC>show snmp x.x.x.x fddi fddimib fddimibport fddiPORTNumber, -
MCC>by password = "public-5"
The ip address is the 900FP, which is also the MAM. Moreover, the 900FP
is also in slot 5 in the DEChub 900. He receives an error message stating
ATTRIBUTE IS NOT GETTABLE. What could cause this to happen?
Another issue is when he looks at the next 2 slots in the DEChub 900,
slots 6 and 7. DECbridge 900MXs are in the 5 and 6 and it only
states that he has 2 ports. In Slot 8 of the DEChub 900 there is a
DECconcentrator 900MX and it states that there are 9 ports when there
should only be 7.
He is using the same MAM ip address. Is there something we are not
seeing here? Any help would be appreciated..
Richard
|
|
Richard,
>>> My customer does the following MCC command that you gave as an
>>> example:
>>> MCC>show snmp x.x.x.x fddi fddimib fddimibport fddiPORTNumber, -
>>> MCC>by password = "public-5"
>>> The ip address is the 900FP, which is also the MAM. Moreover, the 900FP
>>> is also in slot 5 in the DEChub 900. He receives an error message stating
>>> ATTRIBUTE IS NOT GETTABLE. What could cause this to happen?
"ATTRIBUTE IS NOT GETTABLE" means that your device does not support
this mib variable. From your note, it is not clear to me if slot 5 is
a DECswitch or a DECrepeater : of course, only DECswitches support
fddiPORTNumber attribute. DECrepeaters 900FP ( or PORTswitches ... )
support repeater mib ( top level variable is SNMPDOT3RPTRMGT instead
of FDDI ).
To be sure that slot 5 is actually a DECswitch, do the following :
MCC>show snmp x.x.x.x sysdescr, by password = "public-5"
A DECswitch900 SHOULD answer to the request on fddiPORTNumber.
>>> Another issue is when he looks at the next 2 slots in the DEChub 900,
>>> slots 6 and 7. DECbridge 900MXs are in the 5 and 6 and it only
>>> states that he has 2 ports. In Slot 8 of the DEChub 900 there is a
>>> DECconcentrator 900MX and it states that there are 9 ports when there
>>> should only be 7.
DECswitches 900 ( or DECbridges 900MX ) have only 2 fddi ports :
port A and port B, configured in backplane or front panel or mixed.
But you can't have more than 2 ports.
DECconcentrators have 6 fddi ports by default, configured on the
front panel ( 1 port A, 1 port B and 4 ports M ). You can use up
to 8 ports if backplane is in used : 1 port A, 1 port B and 6 ports M.
To check the actual port type, do the following :
MCC>show snmp x.x.x.x fddi fddimib fddimibport fddimibporttable * -
_MCC> fddimibportmytype, by password = "public-8"
Guy.
|