[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | FDDI - The Next Generation |
|
| Moderator: | NETCAD::STEFANI |
|
| Created: | Thu Apr 27 1989 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2259 |
| Total number of notes: | 8590 |
842.0. "IN BAND MANAGEMENT of AP3 and V1.3 FT2 ???" by GADWAL::WOESTEMEYER (Why??...Why not!!!) Tue Jan 26 1993 09:10
Appearently there is a problem with in band management with the AP3
module in DECbridge 610, V1.3 FT2.
Bridge KEROON_NS:.br.db610-1
AT 26-JAN-1993 06:54:22 Characteristics
Examination of attributes shows:
Hardware Type = DEFEB DECbridge 610
ROM Version = V2.9.0
Device Configuration Error Condition = False
Device Configuration = ( (
FRU Type = AP Card,
FRU State = Working,
FRU ID = N/A,
FRU Revision = Revision 4 ),
(
FRU Type = Three NI Card,
FRU State = Working,
FRU ID = N/A,
FRU Revision = Revision 8 ),
(
FRU Type = FI Card,
FRU State = Working,
FRU ID = N/A,
FRU Revision = Revision 0 ),
(
FRU Type = QM Card,
FRU State = Working,
FRU ID = N/A,
FRU Revision = Revision 0 ),
(
FRU Type = Fan,
FRU State = Working,
FRU ID = N/A,
FRU Revision = Revision 0 ) )
IEEE802 Spanning Tree Version = V0.0.0
ID = %X08002B2FFCF0
LB100 Spanning Tree Version = V0.2.0
Port Count = 4
Root Priority = 128
Bad Hello Limit = 15
Bad Hello Reset Interval = 5
Port Test Passed Threshold = 10
Port Test Interval = 60 Seconds
No Frame Interval = 300 Seconds
Hello Interval = 1 Seconds
Listen Time = 15 Seconds
Forwarding Delay = 30 Seconds
Last Load Host = 00-00-00-00-00-00
Reset Defaults Switch = False
Update Switch = False
IP Fragmentation Switch = True
LB100 Poll Time = 300 Seconds
LB100 Response Timeout = 15 Seconds
LB100 Spanning Tree Compatibility = Auto-Select
Software Version = "V1.3 FT2"
NTP Table = { 80-F3 }
Using the pack settings from a DECbridge 500, since I don't have one for
the 610 and AP3 module, I tried to set the bridge IP address using DECmcc
V1.2 and the ELM access module:
MCC> SET BR BR.DB610-1 IP ADDRESS 16.63.16.247
Bridge KEROON_NS:.BR.DB610-1
AT 26-JAN-1993 06:37:31 Characteristics
The Bridge management switch is currently off for this bridge.
I check the pack and switches 3 and 4 and sure enough they were up,
management writes disabled, but I did notice on the OBM terminal that
IP address did get set. I then palyed around a bit, found that no matter
how switches 3 and 4 were set, I could set the IP address even though
I would always get:
The Bridge management switch is currently off for this bridge.
Further experimentation showed that if the unit was power cycled it would
loss the IP address.
After getting the IP address temporarily set, I registered the bridge
as an SNMP entity successfully.
MCC> register snmp snmp.db610-1 synon db610-1, address 16.63.16.247
SNMP KEROON_NS:.snmp.db610-1
AT 26-JAN-1993 07:01:22
Registration successful.
MCC> sh snmp db610-1 all char
SNMP db610-1
AT 26-JAN-1993 07:04:59 Characteristics
Examination of attributes shows:
sysDescr = "DECbridge 610 BL1.3 FT2 "
sysObjectID = "1.3.6.1.4.1.36.2.15.3.6.10"
ifNumber = 4
sysContact = -- Attribute Not Available
sysName = -- Attribute Not Available
sysLocation = -- Attribute Not Available
sysServices = 10
However, when I tried to set a trap address via MCC using the SNMP AGENT
CONFIGURATION guide lines I was unsuccessful:
MCC> set snmp db610-1 dec ema eauth1 eauthtrapusertable 16.63.16.27 -
_MCC> eauthtrapuseraddr 16.63.16.27
SNMP db610-1 dec ema eauth1 eauthTrapUserTable 16.63.16.27
AT 26-JAN-1993 07:04:35 Identifiers
No response from entity.
Is in band management of the AP3 module and V1.3 FT2 possible??
Steve Woestemeyer
CSC/CS Network Support Team
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 842.1 | Enable management, use password for sets | QUIVER::WALTER | | Tue Jan 26 1993 13:38 | 40 |
| > Using the pack settings from a DECbridge 500, since I don't have one for
> the 610 and AP3 module, I tried to set the bridge IP address using DECmcc
> V1.2 and the ELM access module:
The pack settings for the DECbridge 600 are different than for the 500
because it has 4 ports vs. 2 for the 500. Switches 3,4,5, and 6 enable
management sets from ports 1 (FDDI), 2,3, and 4 respectively. The
switch must be in the down position to manage the bridge from that
port.
Note that you can always change parameters from OBM without regard for
the position of any of the management switches.
> Further experimentation showed that if the unit was power cycled it would
> loss the IP address.
If the IP address is set via management (such as MCC), or through OBM
(for bridges with the new AP3 board), the address should be saved in
NVRAM and not lost across power cycles. However, if the IP address is
learned through Bootp, it is NOT saved in NVRAM. It must be loaded
through the bootp process each time the bridge is reset.
> MCC> set snmp db610-1 dec ema eauth1 eauthtrapusertable 16.63.16.27 -
> _MCC> eauthtrapuseraddr 16.63.16.27
>
> SNMP db610-1 dec ema eauth1 eauthTrapUserTable 16.63.16.27
> AT 26-JAN-1993 07:04:35 Identifiers
>
> No response from entity.
You must specify the password (actually the ReadWrite Community string)
on the command line when doing a set. By default, the ReadWrite string
is just the port 1 address in lower case characters, no dashes. For
example, if port 1 address is 08-00-2b-12-34-56, you would append to
the command line:
,by password "08002b123456"
Dave
|