| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4259.1 | Question 2 | KERNEL::FREKES | Like a thief in the night | Mon Mar 10 1997 09:31 | 28 |
| Ton
>2. Portswitch 900TP has connections to several internal LAN's. However, after
>removal and re-insertion of the module the connections to those LAN's are not
>restored. Is this intended behaviour?
I am running ClearVISN V5 and V5 of the MAM code. I put some of the portswitch
legs onto different LANS. I thne removed the module from the HUB did screen
refresh, and the legs had gone. Strangley enough the actual picture of the
module remained in the LAN interconnect screen. Even after two refresh's.
I then re-inserted the module, and hit screen refresh. The module appeared,
but the green legs for each of the port groups did not reconnect. Only the
blue leg, for the ethernet connection re-connected. Odd, not what I was
expecting, but none the less a problem. The PORTswitch900TP is running V2.1.1.
I have done a reset with current settings on the MAM. This made no difference.
I then downgraded the MAM to V4.2 and did the same test. This time without
doing a screen refresh, between removing the module, and re-inserting it.
It made no difference. I got the same result. Only the blue leg remained
connected.
I guess we have a problem here!?
Regards
Steven Freke
UK CSC - Networks.
|
| 4259.2 | Question 2 | STU03::RUEGGEN | | Tue Mar 11 1997 05:11 | 6 |
| Hello,
for this to work you need MAM V5.0 and MCM 6.0 (Clearvisn1.1)
The LAN interconnect then enables you to do a Backplane Auto Healing
I tried this with a 900FP and it works perfectly.
|
| 4259.3 | | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Wed Mar 12 1997 09:51 | 38 |
| >3. MCM on the Gigaswitch/FDDI: when looking at the 'bridging' section, it will
>not show the first two ports of an FGL-4 card. It should be noted that these
>ports have UTP-pmd's installed. Zooming into the module straight from the
>chassis view works ok, except for the portnumbers itself.
What version of the GIGAswitch/FDDI firmware is your customer
running? I seem to recall a bug in the past where TP-PMD was not
reported correctly. The proper (and current) release is BL3.1 of
GIGAswitch/FDDI firmware.
...also, when observing this problem, is the FGL-4 in a four port
slot or a two port slot?
>4. MCM: still at the Gigaswitch, ratelimiting looks adjustable, but is not.
>Should this work?
I've used this, and I know some customers who have used this.
Precisely what are you doing, and how does it fail?
>5. The Gigaswitch seems to support a statistics window. However, the output we
>see is incorrect; it varies when there is for shure a steady load (by means of
>an analyzer) and sometimes is even negative (i.e. graph below the x-axis).
>Does this feature maybe require a special setup??
I've used this too and have not observed any unexplained
descrepancies. ...again, what version of GIGAswitch/FDDI firmware are
you using. Note that there have been known bugs related to MIB objects
for port 2 for some time. They were fixed for BL3.1 except for AGLs
(for which the fix was inadvertantly left out).
There is no special setup required.
I believe that the statistics display uses MIB objects which
reflect data packets. This does not include non-data traffic, which
most analyzers include.
MDL
|
| 4259.4 | | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Wed Mar 12 1997 10:04 | 10 |
| >
>1. In MCM the 'Find Address' command only reports slot AND portnumber when
>output is redirected to a file. This is valid for the 900EF.
>For the Gigaswitch/FDDI it NEVER reports the portnumber.
I just tried this (with MCM 5.0 and a FT version of GIGAswitch/FDDI
BL3.1 firmware) and it works fine. What version of MCM and the
GIGAswitch/FDDI firmware are you using?
MDL
|
| 4259.5 | this is normal behavior | NETCAD::MOWER | | Wed Mar 12 1997 22:27 | 23 |
|
> 2. Portswitch 900TP has connections to several internal LAN's. However, after
> removal and re-insertion of the module the connections to those LAN's are
> not restored. Is this intended behaviour?
First, a terminology nit: I suspect you actually mean to say "backplane LAN"
on line #1 above, rather than "internal LAN" ? Assuming that is the case...
With auto-healing disabled, this is expected, normal behavior. Whenever a
module is removed, (with auto-healing disabled), all previous connections
are lost.
In order to use auto-healing of Ethernet backplane connections, you must be
running MAM v5; if you are running MAM v5 you must be running clearVISN
v1.1a.
Remember that after inserting or removing a module from the hub, you must
first refresh the front panel window, (options-->polling-->refresh), and
THEN refresh the LAN Interconnect view, in that order.
Carl Mower.
|