Motorola 68241 User Guide - Page 36

Configuration, Booting Connections Within the Group, RIP Split Horizon, Limitations

Get Motorola 68241 - Vanguard 312 Router PDF manuals and user guides View all Motorola 68241 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 36 highlights

LANView of the WAN - Group LCONs Configuration Considerations Limitations You configure the LANView using the LAN Connection Table described on "Configuring LAN Connection Table" section on page 3-11. Configuration parameters are also described in the Vanguard Configuration Basics Manual. LANView configuration is similar to LAN Connection configuration. Entering the same Router Interface address for several LAN Connections ties all desired LAN Connections to the same Router Interface. Booting Connections Within the Group Booting any LAN Connection that is part of a group does not affect any other LAN Connections belonging to that group. Also, any LAN Forwarder changes, Bridge Link Number Changes, or Router Interface Number changes (unless the Router Interface is already associated with a group) require a Node boot to take effect. Other changes can take effect with a LAN Connection boot. You can perform the following operations without a node boot; only a LAN Connection boot is required: • Configure a new LAN Connection and boot it into an existing LAN Connection Group • Move a LAN Connection from one LAN Connection Group to another. RIP Split Horizon On broadcast-type networks, RIP split horizon reduces the possibility of routing loops by blocking information about routes from being advertised out the interface from which it originated. Since LANView makes multiple remote nodes reachable through a single Router Interface, you must disable RIP Split Horizon on that Router Interface for all nodes to receive all necessary routing information. When you disable split horizon, internal hold down timers ensure that nodes stop "listening" after a network failure. This eliminates the possibility of accepting any route misinformation and allows time for the failure information to work its way into all the routing databases. The following limitations apply to the LANView feature: • Bridging traffic is not allowed over On Demand SVCs that are part of a LANView. However, Bridging traffic is allowed over permanent SVCs that are part of LANView. • X.25 PVCs are not supported as part of a LAN Connection Group. 2-20 Vanguard Routing Model

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
2-20
Vanguard Routing Model
LANView of the WAN - Group LCONs
Configuration
Considerations
You configure the LANView using the LAN Connection Table described on
“Configuring LAN Connection Table” section on page 3-11. Configuration
parameters are also described in the
Vanguard Configuration Basics Manual
.
LANView configuration is similar to LAN Connection configuration. Entering the
same Router Interface address for several LAN Connections ties all desired LAN
Connections to the same Router Interface.
Booting Connections Within the Group
Booting any LAN Connection that is part of a group does not affect any other LAN
Connections belonging to that group. Also, any LAN Forwarder changes, Bridge
Link Number Changes, or Router Interface Number changes (unless the Router
Interface is already associated with a group) require a Node boot to take effect. Other
changes can take effect with a LAN Connection boot.
You can perform the following operations
without
a node boot; only a LAN
Connection boot is required:
•
Configure a new LAN Connection and boot it into an existing LAN
Connection Group
•
Move a LAN Connection from one LAN Connection Group to another.
RIP Split Horizon
On broadcast-type networks, RIP split horizon reduces the possibility of routing
loops by blocking information about routes from being advertised out the interface
from which it originated.
Since LANView makes multiple remote nodes reachable through a single Router
Interface, you must disable RIP Split Horizon on that Router Interface for all nodes
to receive all necessary routing information.
When you disable split horizon, internal hold down timers ensure that nodes stop
“listening” after a network failure. This eliminates the possibility of accepting any
route misinformation and allows time for the failure information to work its way into
all the routing databases.
Limitations
The following limitations apply to the LANView feature:
•
Bridging traffic
is not
allowed over On Demand SVCs that are part of a
LANView. However, Bridging traffic
is
allowed over permanent SVCs that
are part of LANView.
•
X.25 PVCs are not supported as part of a LAN Connection Group.