| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| 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 |
Folks
I have the following configuration. My problem is detailed below.
1 2 3 4 5 6 7 8
Probe PS900 PS900 PS900 PS900 PS900 PS900 PS900
90 TP TP TP TP TP TP FP
123 123 123 123 123 71234 1234
| ||| ||| ||| ||| ||| ||||| ||||
T/W --#-----|||----|||----|||----|||----|||----#||||--||||
||| ||| ||| ||| ||| |||| ||||
LAN 1 --------#||----#||----#||----#||----#||-----#|||--#|||
|| || || || || ||| |||
LAN 2 ---------#|-----#|-----#|-----#|-----#|------#||---#||
| | | | | || ||
LAN 3 ----------#------#------#------#------#-------#|----#|
| |
LAN 4 -----------------------------------------------#-----#
We than have a couple of switches connected into the ports in slot 8. Providing
connectivity across the backplane LANS.
Expaned View of Slot 8
Ports 1-2 in Group 1
Ports 3-4 in Group 2
Ports 5-6 in Group 3
Ports 7-8 in Group 4
Switch 1 900FP Switch 2
port 1 ------- Port 1
Port 2 --------- port 1
port 2 ------- Port 3
Port 4 --------- port 2
port 3 ------- Port 5
Port 6 --------- port 3
port 4 ------- Port 7
Port 8 -------- port 4
The two switches are then connected together by two seperate links. One in
spanning tree forwarding, and the other in spanning backup.
Hanging off one of the switches I have an NT server.
The NMS is connected through slot 2 to LAN 1 (of the hub).
The Workstation is connected through slot 7 to LAN 3 (of the hub).
We are able to ping all three stations. ie NT ->NMS
NT ->WS
WS -> NMS
I am able to trace between NMS -> NT Server
NMS -> Workstation (WS)
But unable to trace between WS and Server.
Rmon Manager V3.3
Probe V2.6
The customer tells me that when he installed RMON Manager, he was unable to
trace packets from his NMS. But he fixed that by editing a config file. The
name of which escapes him.
Does anybody have any ide why I cannot trace a data exchange between the
Workstation abd the NT server. But I am able to ping both stations from the
NMS?
Steven
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4395.1 | NETCAD::HOPPE | Mon May 12 1997 17:51 | 12 | ||
What group is the Thinwire connection associated with in slot 7?
It appears that LAN 1 and the thinwire are associated by a repeater
group. Therefore, the thinwire will see every packet on LAN1.
LAN 3 and the thinwire are seperated by a bridge. Therefore,
the thinwire will only see packets flooded from LAN 3.
That would explain why you cannot capture the conversation between
the WS and the server. The WS on LAN 3 is talking to a server on
another bridge port. The bridge will not flood that conversation
onto LAN 1, so the packet probe will never see it.
Chris
| |||||
| 4395.2 | now I am confused | KERNEL::FREKES | Like a thief in the night | Tue May 13 1997 13:16 | 22 |
Chris
Thanks for the response. I am having problems trying to get my head
around the switching matrix on the portswitch.
On the Portswitch you can bring up the switching matrix. And you have the
ability to place a tick from BP (port33) into 1 of 6 groups.
Am I correct in assuming that this assigns the thinwire connection to
the group you have placed the tick in. Therefore what ever LAN you
connect that group to from the LAN Interconnect screen you will also
see traffic from the TW. IE place the tick in group 2, and then place
the leg for group 2 onto LAN 2. Would this then allow you to see all
traffic on the thinwire or LAN 2, by plugged a device into whatever
groups are assigned to group 2.
Underneath the switching matrix, there is a scroll bar and the word
Thinwire. From here you can have thinwire on group 1-6 or no
connection. Does this not conflict with what the switching matrix above
tells us?
Confused
| |||||
| 4395.3 | LAN Interconnect as well | SNOFS1::KHOOJEANNIE | Laziness breeds Efficiency | Wed May 14 1997 22:13 | 15 |
Hi Steve
On the PORTswitch grouping screen, there is an extra column you can
tick to determine which group the MAC address is associated with.
Underneath, there is the scroll bar where you can select which
group the PORTswitch's thinwire is associated with. However, if you
want the DEChub's thinwire to be in the same LAN as that group, you
have to, in addition, pull down the PORTswitch's thinwire stub (7) to the
hub thinwire in the LAN Interconnect screen.
Regards
Jeannie
| |||||