| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3132.1 | Not all of those can be blamed on Hubwatch | SCHOOL::RLEBLANC | | Tue Jan 09 1996 09:12 | 12 |
|
Well don't blame Hubwatch for everything ;^). Number 1 belongs to me.
Number 2 and 3 I suspect also belongs to me and possibly 4. Please send
me the snmp commands that you are using for Number 2,3, 4 and I
will have a look see.
Rene'
GIGAswitch/FDDI
firmware team
|
| 3132.2 | | NETCAD::DRAGON | | Tue Jan 09 1996 10:29 | 31 |
|
Otto,
As item 1 states HUBwatch does not show the proper PMD on the
Front Panel.
For item 2, as pointed out in the previous reply, an SNMP trace will
help track this down.
For item 3, is this the bad FGL-4 being refered to or any FGL-4?
Could you explain item 4 further? Does this refer to FGL-4 in
general or the defective FGL-4? Also what particular
views/fields/LEDs were incorrect?
Since HUBwatch uses FDDI related MIBs to determine the LED states on
an FGL-4, it is not possible to obtain LED states given by
diagnostic FW. I guess the answer to item 5 depends on the extent of
the linecards problems and whether FDDI is running or if the
linecard is halted in diagnostics.
I believe that HUBwatch does show the Port Type correctly (item 6),
however a situation may exist where this is not true (ie a bug). An SNMP
trace will help narrow this down.
HUBwatch does not show DNA, but does show UNA on the Linecard
Summary View (item 7). We could add DNA to the wish list.
Regards,
Bob
|
| 3132.3 | | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Tue Jan 09 1996 11:01 | 10 |
| P.S. There is an entire family of bugs in the FGL-4 firmware which are
caused by confusion of port numbers in the FGL-4 SNMP firmware.
Re: .2 - please indicate exactly which steps you are taking in Hubwatch
Re: .4 & .5 - which displays in Hubwatch are you using? If the module
fails diagnostics, it should indicate the problem in the Operatinal
Status field of the System Summary display.
MDL
|
| 3132.4 | Bob Dragon gets off easy! | SLINK::HOOD | My God, what have I done to my spleen? | Tue Jan 09 1996 11:20 | 7 |
| Geez, Bob!
You must live right. Someone reports a "HUBwatch" problem and two
GIGAswitch people step in to claim it as their problem???
What's your secret? 8-{)}
|
| 3132.5 | | NETCAD::DRAGON | | Tue Jan 09 1996 12:06 | 4 |
|
Just lucky I guess:-)
bd
|
| 3132.6 | FGL-4 Cards managed thru Hubwatch V4.1.1 | PRIVAT::OTTO | ...this is the last message You will ever hear... | Wed Jan 10 1996 07:57 | 12 |
| Hello,
Thanks for your fast response . today we received a FGL-4 Card
which enables us to do the traces .Unfortunately we have no TP PMD�s
so we can not verify whether the PMD type is identified correctly .
to the other points we will hopefully find something out with the traces.
regards
OTTO
|
| 3132.7 | Trace on number 1 | MUN01::HILGER | | Wed Jan 10 1996 08:21 | 159 |
| Number 1 IRIS trace. You see SNMP object ID ePORTPMDType.n.1 returns
an integer value of pmdMM(2) instead of pmdUTP(7).
Look out for #####
I'll try to get the other traces done today
Peter
IRIS capture data Page 1
SNMP-Trace GIGAswitch Port Type auf FGL-4 11/23/95 14:53:34
** Summary for frame 12 **
12 +9.6m NACG01<- NACWS2 SNMP 16.186.0.158�16.186.0.1 "public" Get #2 (5 var.)
UDP UDP Dest=16.186.0.158 Src=16.186.0.1 Len=178
IP UDP Dest=16.186.0.158 Src=16.186.0.1 Len=178
DLL DIX PType=08-00
** Detail for frame 12 **
DLL:
DLL: - - - - - Datalink Header - - - - -
DLL:
DLL: Frame 12 arrived at 19093.7 milliseconds, length = 192 bytes
DLL:
DLL: Destination Address = 08-00-2B-A2-5F-CB (NACG01)
DLL: Source Address = AA-00-04-00-71-C6 (NACWS2)
DLL:
DLL: DIX format, Protocol Type = 08-00
IP:
IP: - - - - - Internet protocol (IP) - - - - -
IP:
IP: Internet header version = 4
IP: Internet header length = 20 bytes
IP: Type of service = 00
IP: .....0.. = Normal Reliability
IP: ....0... = Normal Throughput
IP: ...0.... = Normal Delay
IP: 000..... = Routine
IP:
IP: Total Packet Length = 178
IP: Identification = 31280
IP: Fragment Information = 0000
IP: Fragment Offset = 0
IP: ..0............. = May Fragment
IP: .0.............. = More Fragments
IP:
IP: Time to live (sec) = 128
IP: Protocol Type = 17 (UDP)
IP: Header Checksum = 40440
IP: Source Address = 16.186.0.1
IP: Destination Address = 16.186.0.158
UDP:
UDP: - - - - - User Datagram Protocol (UDP) - - - - -
UDP:
UDP: Source port = 1064 (Unknown)
UDP: Destination port = 161 (SNMP)
UDP: Length = 158
UDP: Checksum = 48577
UDP:
SNMP:
SNMP: - - - - - Simple Network Management Protocol X1.0.12 - - - - -
SNMP:
SNMP: Community = "public"
SNMP: Command = Get
SNMP: Request ID = 2
SNMP:
SNMP: - - - - - Varbind List - - - - -
SNMP:
SNMP: 1: {ePORTSMTIndex.10.1}
IRIS capture data Page 2
SNMP-Trace GIGAswitch Port Type auf FGL-4 11/23/95 14:53:34
SNMP: 2: {ePORTIndex.10.1}
SNMP: 3: {ePORTPHYIndex.10.1}
SNMP: 4: {ePORTPMDType.10.1}
SNMP: 5: {ePORTRejectReason.10.1}
SNMP: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
IRIS capture data Page 3
SNMP-Trace GIGAswitch Port Type auf FGL-4 11/23/95 14:53:34
** Summary for frame 13 **
13 +16.0m NACWS2<- NACG01 SNMP 16.186.0.1�16.186.0.158 "public" GetResponse #2 (5 var.)
UDP UDP Dest=16.186.0.1 Src=16.186.0.158 Len=175
IP UDP Dest=16.186.0.1 Src=16.186.0.158 Len=175
DLL DIX PType=08-00
** Detail for frame 13 **
DLL:
DLL: - - - - - Datalink Header - - - - -
DLL:
DLL: Frame 13 arrived at 19109.7 milliseconds, length = 189 bytes
DLL:
DLL: Destination Address = AA-00-04-00-71-C6 (NACWS2)
DLL: Source Address = 08-00-2B-A2-5F-CB (NACG01)
DLL:
DLL: DIX format, Protocol Type = 08-00
IP:
IP: - - - - - Internet protocol (IP) - - - - -
IP:
IP: Internet header version = 4
IP: Internet header length = 20 bytes
IP: Type of service = 04
IP: .....1.. = High Reliability
IP: ....0... = Normal Throughput
IP: ...0.... = Normal Delay
IP: 000..... = Routine
IP:
IP: Total Packet Length = 175
IP: Identification = 43
IP: Fragment Information = 0000
IP: Fragment Offset = 0
IP: ..0............. = May Fragment
IP: .0.............. = More Fragments
IP:
IP: Time to live (sec) = 32
IP: Protocol Type = 17 (UDP)
IP: Header Checksum = 30717
IP: Source Address = 16.186.0.158
IP: Destination Address = 16.186.0.1
UDP:
UDP: - - - - - User Datagram Protocol (UDP) - - - - -
UDP:
UDP: Source port = 161 (SNMP)
UDP: Destination port = 1064 (Unknown)
UDP: Length = 155
UDP: Checksum = 55988
UDP:
SNMP:
SNMP: - - - - - Simple Network Management Protocol X1.0.12 - - - - -
SNMP:
SNMP: Community = "public"
SNMP: Command = GetResponse
SNMP: Request ID = 2
SNMP:
SNMP: - - - - - Varbind List - - - - -
SNMP:
SNMP: 1: {ePORTSMTIndex.10.1}
IRIS capture data Page 4
SNMP-Trace GIGAswitch Port Type auf FGL-4 11/23/95 14:53:34
SNMP: Integer = 10
SNMP: 2: {ePORTIndex.10.1}
SNMP: Integer = 1
SNMP: 3: {ePORTPHYIndex.10.1}
SNMP: Integer = 0
SNMP: 4: {ePORTPMDType.10.1}
SNMP: Integer = 2 #####
SNMP: 5: {ePORTRejectReason.10.1}
SNMP: Integer = 1
SNMP: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
|
| 3132.8 | More taces to .1 - .6 | MUNICH::HILGER | | Mon Feb 12 1996 05:30 | 65 |
| We used HUBwatch for Windows 4.1 and the IRIS Analyzer to obtain this
traces. All traces are available in File MUNICH::EC_TRACE.BCK. You will
also find a more complete SNMP database for GIGAswitch variables. I
compiled this with all MIBs used by the GIGAswitch/FDDI V1.2. This is
for GIGAswitch Firmware 2.2. Copy PD_GIGA.DAT to your Iris directory as
PD_SNMP.DAT.
Number 1. Trace PORT_PMD.DWC/TXT
As mentioned in previous reply SNMP variable ePORTPMDType.n.1 returns
an integer value of pmdMM(2) instead of pmdUTP(7) when a TP-PMD is installed.
This is probably a FGL-4 Firmware bug.
Number 2. Trace PORT_OFF.DWC/TXT PORT_ON.DWC/TXT
From the FDDI/GIGAswitch Line Card Summary window the first port was
disabled. An SNMP set for variable {snmpFddiPORTAction.29.1} value
disable(4) is send to the GIGAswitch. After this, Hubwatch reads back all
Line card parameters with GetNext command. The returned variable
{snmpFddiPORTConnectState.n.1} for ports 29,30,31 and 32 shows a value of
disabled(1). Only port 29 should show this status. Ports 30,31 and 32
should still be (e.g.) connecting(2) (no FDDI station connected there).
After port 29 is enabled again all other ports on this card show
{snmpFddiPORTConnectState.n.1} enabled(2).
This is probably a FGL-4 Firmware bug.
Number 3. Also see Number 6
This one is ment to be the LED indication on the HUBwatch Main Display.
The right and left PMD LEDs are on the GIGAswitch board are as described
in V2.2 Release notes. But they don't light the same way on the
HUBwatch display as on the physical Box
This is probably a HUBwatch bug because the SNMP traces show correct A/B and
M/S port snmpFddiPORTPCType.n.0's.
Number 4. and 5.
Re: .3 Yes the status is displayed in the system summary display. What the
customer wanted is a trap on Linecard status changes. He had a problem that
the card was continuously running selftest. He wanted a trap whenever a selftest
is initiated. This may be good for the wishlist.
Number 6. Trace PORT_M.DWC/TXT
If Port 30 (second port on FGL-4) is managed to M/S the snmpFddiPORTPCType.n.0
on all Ports are reported with a value=s(3) or m(4).
This is probably a FGL-4 Firmware bug.
Hubwatch does not indicate the correct LED Status for PMDs on the Main display.
Number 7.
DNA is also mentioned for the wishlist
One more. HUBwatch for Windows 4.1 has a problem displaying the number of
ports in a slot as well as for the modules. It also does not display the
seven segment indicator.
Regards Peter
|
| 3132.9 | | NETCAD::DRAGON | | Wed Feb 14 1996 08:24 | 20 |
|
Peter,
Thanks very much for the feedback.
Number 3:
There is a problem with the right PMD LED in HUBwatch. It is never lit.
Number 7:
Could you please explain this problem ("problem displaying the number
of ports...") a bit further. Which HUBwatch view is this on?
The seven segment indicator is not currently supported under Windows.
We will add that to the the wish list items.
Thanks again,
Bob
|
| 3132.10 | 1,2, and 3 "features" fixed. | SCHOOL::RLEBLANC | | Fri Feb 16 1996 10:55 | 18 |
|
>>>1. Hubwatch does not correctly show the type of PMD ( TP is seen as Fiber)
>>>2. Switching off one Port on a FGL-4 Card switches off all Ports on that card
>>>3. Neither the Port State nor the PMD State is shown correctly
Okay these things are now fixed and will be placed in the V3.0 path of
GIGAswitch/FDDI firmware. Two bugs were found, one in FGL4 code and
one in SCP code, so obviously you will need both. As it stands now
you will only see the status/PMD type/switching off port for Port 2
of the FGL4 no matter which port of that card you select.
Cheers,
Rene'
|