[Top] [Table Of Contents] [Prev] [Next] [Index]
10 out of 25 total pages
 

Basic Routing   7

  This chapter describes the commands you use to configure the PortMaster 4 for static and default routing, the Routing Information Protocol, versions RIP-1 and RIP-2, route propagation, and subnet masks--including variable-length subnet masks (VLSMs). See the PortMaster Routing Guide  for configuration instructions and examples.
  To configure the PortMaster for advanced routing protocols, see Chapter 8, "OSPF Routing," and Chapter 9, "BGP Routing."
 

       Displaying Routing Information

  To display routing information on the console, use the following commands:
  For general information about using the command line interface, refer to Chapter 1, "Introduction."
 

       Summary of Routing Commands

  The commands shown in Table 10-1 are used for displaying route information and configuring the PortMaster for the following:
 

       General Routing Commands

  The following commands set the default route gateway address, user and IP netmasks, route filters, and route propagation.
 

       add|delete propagation

  These commands create, modify, or delete a propagation rule that defines how routes coming from one routing protocol are translated and advertised by the PortMaster into another routing protocol.

  add propagation Protocol(src) Protocol(dest) Metric Filtername

  delete propagation Protocol(src) Protocol(dest)

 
 
 Protocol(src)  Designates the source protocol of the route. Use one of the following keywords:

  · rip 

  · static 

  · ospf 

  · bgp 

 Protocol(dest)  Designates the destination routing protocol for the route propagation. Use one of the following keywords:

  · rip 

  · static 

  · ospf 

  · bgp 

 Metric  Common metric used to translate from one protocol to the other. A metric of 0 indicates that the automatic rules in use in the PortMaster attempt to build a metric automatically.  By default, all routes propagate and the common metric is 0.
 Filtername  IP access filter added to the filter table with the add filter  command and configured with the set filter  command for use in the propagation rule.

  Caution ¯ If you plan to use a constant metric instead of the automatically generated metric provided by the ComOS, then you run the risk of creating routing loops if you do not provide for filters or policies to screen the route information that the PortMaster accepts from each routing protocol.

  Use the add propagation  command to create or modify an entry. See "Modifying a Propagation Rule" later in this section for modification instructions. Use the delete propagation  command to delete an entry.
  The add propagation  command allows routes coming from one protocol to be advertised into another, based on the filter specified in the rule. The filter is a familiar IP access filter that uses the source address(es) specified in the filter to indicate the routes.
  BGP-to-OSPF or BGP-to-RIP Propagation.  You must explicitly configure the add propagation  command to enable BGP routes to be propagated into OSPF or RIP.
  Static-to-BGP Propagation.  When static routes are the source protocol and BGP is the destination protocol, you need no other routing protocol. This combination allows the automatic, immediate advertisement into BGP of any configured static routes or static routes learned via RADIUS. This type of configuration is useful is for points of presence (POPs) with a single LAN and an attachment to a BGP-routed backbone. Configuring static routes as the source protocol and BGP as the destination protocol eliminates the overhead of using a routing protocol other than BGP just to advertise static routes learned via RADIUS.
  RIP-to-OSPF Propagation.  To propagate RIP routes from an Ethernet interface into OSPF, you must first use the set ether0 ospf accept-rip on  command.
  Modifying a Propagation Rule.  The recommended sequence for changing a propagation rule is as follows:

  1. Delete your propagation rule with delete propagation .

  2. Add the revised propagation rule with add propagation .

  3. Enter the command reset propagation .

  The output of the reset propagation  command prompts you to enter the reset ospf  or reset bgp  command, if necessary.

  4. Follow any instructions for entering the reset ospf  or reset bgp  command.

  To propagate BGP routes into OSPF, you can use a set of commands similar to the following:

  Command> add filter fullprop
 New Filter successfully added

  Command> set filter fullprop 1 permit 0.0.0.0/0 0.0.0.0/0
 Filter fullprop updated

  Command> set propagation static bgp 1 fullprop
 Propagation rule successfully defined

 

       reset propagation

  This command resets the propagation rules system.

  reset propagation

  This command must be used each time the propagation filters are changed. If the propagation affects OSPF or BGP, use the commands reset  ospf  or reset bgp , respectively.
 

       set Ether0|W1 crossbar-ip

  This command enables the crossbar IP feature on the specified interface or for a specified location (destination) or user.

  set Ether0 |W1 |user Username |location Locname  crossbar-ip Ipaddress

 
 Ether0  Ethernet interface. For a list of configurable Ethernet interfaces see page 4-3.  To activate crossbar IP configuration on the Ether0 interface, you must use the reboot command. On all other Ethernet interfaces, you must use the reset slotSlotnumber command.
 W1  Network hardwired synchronous port. You must first select the slot associated with the port using the set view  command. To activate the new crossbar IP setting, you must reset the port.
 Username  Network user in the user table. Configures the crossbar IP feature on the user profiles of a network user on the PortMaster user table.  You can also configure a crossbar IP address for a user via RADIUS. If both are configured, the PortMaster uses the local user table by default.  The new crossbar IP setting is activated the next time the user connects.

  Note ¯ If a user configured with a crossbar IP address is deleted from the user table and added back again, the crossbar IP address configuration is automatically added back with the user.

 Location  Dial-out location or Frame Relay subinterfaces in the location table.  The crossbar IP setting takes effect the next time the location is used.
 Ipaddress  IP address of the next hop for all packets leaving the interface. Enter the IP address in dotted decimal notation or the hostname--a string of up to 39 characters.
 

  The PortMaster  4 supports IP crossbar on ComOS 4.1 and later releases.
  Use the crossbar IP address to specify the next hop destination of packets leaving the specified interface. The PortMaster 4 selects the next hop address chosen in the following order of priority:

  1. Crossbar IP address, if specified

  2. IP pool range gateway address, if specified

  3. IP pool gateway address, if specified

  4. PortMaster routing table

  To disable the crossbar IP address on an interface, use the address 0.0.0.0.
  When crossbar IP is enabled on an interface, the output from the ifconfig  command displays CROSSBAR  next to interface. You do not have to configure named IP pools to use the IP crossbar feature.

  Note ¯ To use the crossbar IP feature, you must also add the corresponding RADIUS attribute to the RADIUS dictionary file. The attribute for crossbar IP is called LE-IP-Gateway . For additional information about configuring crossbar IP on an interface, see the ComOS release notes.

  Command> set ether1 crossbar-ip 149.198.96.78
Changing crossbar ip address from 0.0.0.0 to 149.198.96.78
  Command 2> set w70 crossbar-ip 192.168.123.4
Changing crossbar ip address from 0.0.0.0 to 192.168.123.4

Command 2> set location krabappel crossbar-ip 192.168.96.69
Changing crossbar ip address from 0.0.0.0 to 192.168.96.69
  Command> set user skinner crossbar-ip 192.168.1.2
Changing crossbar ip address from 0.0.0.0 to 192.168.1.2
 

       set Ether0|C0|W1 netmask

  This command sets the IP netmask for a specified interface.

  set Ether0|C0|W1|user Username|location Location netmask Ipmask

 
 Ether0  Ethernet interface. See page 4-3 for more information.
 C0  Network hardwired asynchronous port.
 W1  Network hardwired synchronous port.
 Username  User from the user table.

  Locname

 Location from the location table.
 Ipmask  IP netmask in dotted decimal notation.

  set  Ether0 address  - page 4-3
  set location netmask - page 11-15
set user netmask - page 10-14
 
 

       set Ether0|C0|W1|user|location route-filter

  This command applies an input or output filter to a specified interface on the PortMaster or to a specified remote location (destination) or user. The filters determine which RIP or OSPF routes are injected into the routing table or advertised to other routers.

  Note ¯ These filters are ignored for BGP routes. Use BGP policies instead of filters to determine how BGP routes are accepted, injected, and advertised by the PortMaster. See "BGP Routing" on page 9-1 for details on the add bgp policy  and set bgp policy  commands.

  set Ether0|C0|W1|user Username |location Locname route-filter incoming|outgoing [Filtername]

 
 Ether0  Ethernet interface that the route filter is applied to. See page 4-3 for more information.
 C0  Asynchronous port that the route filter is applied to.
 W1  Synchronous port that the route filter is applied to.
 Username  User from the user table.

  Locname

 Location from the location table.
 incoming  Inbound filter.
 outgoing  Outbound filter.
 Filtername  IP access filter that has been created in the filter table with the add filter  command and configured with the set filter  command. Using the command without Filtername  removes the filter.

  The filters used are standard packet filters, with the source and destination addresses significant on input filters, and only the destination address significant on output filters.
  The effects of a route filter depend on the protocol being filtered and on whether the filter is for inbound or outbound routes. See Table 7-2 for more information.
  To disable a filter, enter the command with no Filtername value.
  To change a filter, enter the command with the new Filtername value.
  After applying a route filter to be used with OSPF to an interface or making changes to it, use the reset  ospf  command.

  Table 7-2 The Effect of Protocol on Route Filters 

 
  Protocol    Inbound Route Filter--Route Injection    Outbound Route Filter--
Route Advertisement 
 RIP  The filter permit/deny rule applies and determines which routes are placed into the PortMaster routing table when

  · The address of the advertiser of the route matches the source address in the filter.

  · The destination address in the route being advertised matches the destination address in the filter.

 For RIP, the advertiser is the next-hop (direct) advertiser of the information. 		 The destination addresses in the filter determine which routes are advertised out of this interface.
 OSPF  The filter permit/deny rule applies and determines which routes are placed into the routing table when

  · The address of the advertiser of the route matches the source address in the filter.

  · The destination address in the route being advertised matches the destination address in the filter.

 For OSPF, the advertiser is the ultimate advertiser of the information, not the next-hop OSPF router. Also, the filter specifies only the information that is in the routing table.  Because OSPF area flooding rules make filtering inbound or outbound information on a per-interface basis impractical, applying the same inbound filter to all interfaces running OSPF within the same area is generally good practice. 		 The filter is ignored. OSPF area flooding rules make the definition of outbound route filters impractical on a per-interface basis.  Use propagation filters to translate routing information from RIP, static, or BGP routes so that they do not enter OSPF as external Type 2 routes. See the add propagation  command on page 7-3 for details.
 
 

  Command> set user zephyr route-filter outgoing routes.out

  Username: zephyr

  Type: Dial-in Network User

  Address: Negotiated

  Netmask: 255.255.255.255

  Protocol: PPP

  Options: Quiet Compression

  MTU: 1500

  Async Map: 00000000

  OSPF: on

 

  OSPF accept-rip: off

 

  OSPF cost: 1

 

  OSPF Hello Int: 10

 

  OSPF Dead Time: 40

 

  OSPF(WAN Type): nbma

 

  route-filter

 

  incoming: routes.in

 

  outgoing: routes.out

 

 

       set gateway

  This command sets the default route gateway address.

  set gateway Ipaddress [Metric]

 
 Ipaddress  IP address. The default is 0.0.0.0.
 Metric  Metric for the default route, between 1 and 15. Default is 1.

  The route gateway is the address of a router of last resort to which packets are sent when the PortMaster has no routing information for a packet. The gateway must not be the address of any interface on the PortMaster itself, but must be an address on a network attached to the PortMaster.
 

       set user-netmask

  This command sets the PortMaster behavior for the treatment of user netmasks.

  Caution ¯ Be careful when using this command because it affects both routing and Proxy ARP on the PortMaster.

  set user-netmask on|off

 
 on  The PortMaster adds routes for dial-in users based on the specified netmask.
 off  The PortMaster treats all netmasks specified in the user table or RADIUS as though they were 255.255.255.255.
This is the default.

  Because ComOS supports variable-length subnet masks (VLSMs), you do not have to use the same netmask for all subnets of a network.
  If the user netmask is set to off,  the PortMaster treats all netmasks specified in the user table or RADIUS as if they were 255.255.255.255. The command set user-netmask on  adds routes based on the specified netmask, and the PortMaster uses the actual value of the Framed-IP-Netmask RADIUS reply item to update the routing table when a user logs in.

  Note ¯ You must always use a netmask of 255.255.255.255--or the default
set user-netmask off --when using the PortMaster assigned address pool.

 

       Static Routing Commands

  Static routes are used to provide routing information instead of or in addition to that provided by RIP or other routing protocols. The static routes are stored in the PortMaster route table.
 

       add ipxroute

  This command adds a static route to the PortMaster IPX route table.

  Note ¯ The PortMaster 4 supports IPX protocols on ComOS 4.1 and later releases.

 

  add ipxroute Ipxnetwork Ipxgateway:Ipxhost Metric Ticks

 
 Ipxnetwork  Destination IPX network number. A 32-bit hexadecimal number.
 Ipxgateway:  Ipxhost          Gateway IPX address in the following format: IPX gateway and IPX host address separated by a colon (:).
 Metric  Hop count to the remote destination. An integer from 1 to 15.
 Ticks  Time required to send the packet to the destination network in 50ms increments. An integer from 1 to 15.

  The destination is the IPX network that the PortMaster is sending packets to. The gateway is the address of a router where packets are sent for forwarding to the destination.

  Note ¯ The gateway must not be set to an address on the PortMaster itself. The IPX node address is usually the MAC address on PortMaster products.

 

       add route

  This command adds a static route to the IP route table on the PortMaster.

  Caution ¯ If you plan to use a static netmask, add it before setting any static routes that will be affected. However, Lucent recommends using RIP-2 or the OSPF routing protocol instead of a netmask table for most routing configurations. The PortMaster supports RIP-2 on ComOS 4.1 and later releases.

  add route Ipaddress[/NM] Ipaddress(gw) Metric

 
 Ipaddress  Destination address or network.
 /NM  Netmask--a number from 1 to 32 preceded by a slash (/)--for example, /24.
 Ipaddress(gw)  Gateway IP address.
 Metric  Hop count to the remote destination. An integer from 1 to 15.

  The destination is the IP address of the host or network for which the PortMaster is routing. The gateway is the address of a router where packets should be sent for forwarding to the destination.
  Static routes support VLSM by means of this command, as shown in the example.

  Note ¯ The gateway IP address must not be set to an address on the PortMaster itself.

  The following example adds a route to the 192.168.1.32/27 subnet through gateway 192.168.1.1 with metric 2:
  Command> add route 192.168.1.32/27 192.168.1.1 2
 

       delete ipxroute

  This command deletes a static route from the PortMaster IPX route table.

  delete Ipxroute Ipxnetwork

 
 Ipxnetwork   Destination IPX network number.
 

  Only static routes can be deleted.

  Note ¯ The PortMaster 4 supports IPX protocols on ComOS 4.1 and later releases.

 
 

       delete route

  This command deletes a static route from the PortMaster IP static route table.

  delete route Ipaddress[/NM]

 
 Ipaddress  Destination IP address.
 /NM  Netmask--a number from 1 to 32 preceded by a slash (/)--for example, /24.

  Only static routes can be deleted. Use this command only when the routing entry is unique.
 

       save route

  This command writes the current PortMaster static IP and IPX route tables to the nonvolatile memory of the PortMaster.

  save route

  save all  can also be used.

  Note ¯ The PortMaster 4 supports IPX protocols on ComOS 4.1 and later releases.

 

       RIP Commands

  ComOS 4.1 and later releases support both RIP-1 and RIP-2 on the PortMaster 4. Earlier releases of ComOS support only RIP-1.
  Unlike RIP-2 and OSPF, RIP-1 does not support variable length subnet masks (VLSMs). RIP-1 fails to propagate netmask information and next-hop addresses in its route information.
 
 

       set default

  When RIP is enabled, this command sets all PortMaster interfaces to send and listen for default route information.

  set default on|off|broadcast|listen

 
 on  The PortMaster sends and listens for default route information.
 off  The PortMaster neither sends nor listens for default route information. This is the default.
 broadcast  The PortMaster sends default route information, if it has a default route.
 listen  The PortMaster listens for default route information.

  With this command set on , the PortMaster listens for default route information in RIP and OSPF messages, and if the PortMaster has a default route it is advertised to RIP and OSPF.
 

       set Ether0|CO|W1|user|location rip

  This command enables RIP-1 or RIP2 parameters on a specified interface.

  set Ether0|C0|W1|user Username |location Locname  rip on|off|broadcast|listen|v2 
{broadcast|multicast|on|v1-compatibility}

 
 Ether0  Ethernet interface. For a list of configurable Ethernet interfaces see page 4-3.
 C0  Console port--C0  or C1 --asynchronous ports.
 W1  Network hardwired synchronous port.
 user  Sets RIP-1 or RIP-2--options for a network user. If set to on , the PortMaster sends and listens for RIP packets to the interface established when this user logs in.
 Username  Name of a network user.
 location  Sets RIP-1 or RIP-2--options for a location.  Locations can have routing associated with them--for example, a dial-on-demand connection where the remote router is defined as a location on the local PortMaster. If routing is not set to off  for an on-demand location, the PortMaster dials out to the location at boot time to perform routing, and hangs up when the idle timer expires. RIP packets do not affect the idle timer.
 Locname  Location name that is in the location table.
 rip  Enables RIP-1 or RIP-2 on the interface. Use rip  with one of the following options:
   on  The PortMaster sends RIP broadcasts and listens for RIP-1 packets on this interface.
   off  The PortMaster neither sends nor listens for RIP packets on this interface. This is the default for all interfaces.
   broadcast  The PortMaster sends RIP-1 updates on the interface's broadcast address every 30 seconds, and ignores RIP packets received on the interface.
   listen  RIP packets received on the interface are interpreted as RIP-1 updates. Any subnet mask or next-hop information is ignored.
   v2     Enables RIP-2 on the interface. v2  is used with one of the following options:
     broadcast--The PortMaster 4 sends RIP-2 updates using the interface's broadcast address every 30 seconds and ignores received RIP-1 and RIP-2--packets on the interface.
     on --The PortMaster 4 sends RIP-2 updates every 30 seconds using multicast, and listens for RIP-1 updates on the multicast address, or on the interface's broadcast address.
     multicast --The PortMaster 4 sends RIP-2 updates every 30 seconds using the multicast broadcast address 244.0.0.9. The PortMaster 4 does not use the Internet group management protocol (IGMP) when it sends RIP-2 packets because the updates are sent from router to router. Received RIP packets are ignored.
     v1-compatibility--The PortMaster 4 sends RIP-2 updates on the broadcast address of the interface every 30 seconds. RIP-1 updates are listened for coming from the broadcast address.

  Lucent Technologies supports RIP-2 on the PortMaster 4 running ComOS 4.1 and later releases.
  This command enables the PortMaster to send and listen for RIP packets--and IPX RIP packets if IPX is enabled--on the specified interface. By default, if IPX is enabled, IPX RIP is enabled on the Ethernet interface.
  Using this command without specifying any interface or port sets ether0 by default. Normally, the PortMaster 4 sends RIP packets at least every 30 seconds. However, it may broadcast RIP packets sooner if it detects changes in routing information in nonvolatile RAM.

  Note ¯ The PortMaster 4 supports IPX protocols on ComOS 4.1 and later releases.

 
 
 Command> set user josey rip on  

  Username:

 josey

  Type:

 Dial-in Network User

  Address:

 Negotiated

  Netmask:

 255.255.255.255

  Protocol:

 PPP

  Options:

 Broadcast, Listen, Compression

  MTU:

 1500

  Async Map:

 00000000
 

       set rip cost

  This command sets the RIP cost per interface.

  set Ether0|C0|W1|user Username |location Locname  rip cost Number

 
 Ether0  Ethernet interface. For a list of configurable Ethernet interfaces see page 4-3.
 C0  Console port--C0  or C1 --asynchronous ports.
 W1  Network hardwired synchronous port.
 Username  Name of a network user.
 Locname  Location name that is in the location table.
 Number  Cost--integer between 0 and 16 that is added to the metric of RIP routes learned over the interface.
 

  Lucnet Technologies implementation of RIP supports this command on the PortMaster 4 running ComOS 4.1 and later releases.
  Command> set ether1 rip cost 10
Routing for ether1 changed to RIP On (Broadcast, Listen) Cost 10
  set debug rip|rip-detail - page 14-12
set default - page 7-16
set rip|v2 broadcast|listen|on|off - page 7-17
set rip password - page 7-20
 

       set rip-password

  This command sets the password for RIP-2 packets.

  set rip-password Password |none

 

  Password

  16-character password. The first character cannot be a question mark (?). If quotation marks (" ")are used to encapsulate the password, the quotation marks are dropped.

  none

  Removes the password. This is the default.

  Using set rip-password without any arguments also disables the password.

  Lucent Technologies implementation of RIP-2 supports this command on ComOS 4.1 releases and later. This command prevents RIP packets from being accepted unless they are authenticated. Because the password is sent in the packet as clear text, no security is implied. If a password is set and the PortMaster 4 receives a RIP-1 or RIP-2 packet without the matching password, the packet is dropped.
  Because authentication occupies the first route entry of every RIP packet sent, setting the RIP password adds 20 bytes of overhead for every 24 routes sent via RIP-2.
  The RIP password is enabled as soon as it is configured.
  Command> set rip-password test
RIP Password Updated
  set debug rip|rip-detail - page 14-12
set default - page 7-16
set rip|v2 broadcast|listen|on|off - page 7-17
set rip cost - page 7-19
 

       Netmask Commands

  The netmask commands configure a table of netmasks that are used for routing over noncontiguous subnets in RIP. Read the information on setting static routes in the PortMaster 4 Configuration Guide.

  Caution ¯ Do not use the static netmask table unless you thoroughly understand and need its function. In most circumstances its use is not   necessary. Very large routing updates can result from overuse of the netmask table, adversely affecting performance. In most cases it is easier to use OSPF and RIP-2 instead of using the netmask table and RIP-1. Lucent strongly recommends that you use OSPF if you require noncontiguous subnets or variable-length subnet masks (VLSMs).

 

       add netmask

  This command adds a static netmask to the netmask table. Use caution with the static netmask table. Refer to the PortMaster 4 Configuration Guide for more information.

  add netmask Ipaddress Ipmask

 
 Ipaddress  IP address of the network.
 Ipmask  IP netmask used for the network.

  You can have only one netmask per network when using RIP-1. The example shows the propagation of host routes for all dial-in clients with 192.168.8 addresses, instead of sending out a summarized network route for 192.168.8.0.

  Caution ¯ Be sure to add the netmask before setting any static routes that will be affected. If you change a static netmask, you must delete and then re-enter any affected static routes; otherwise, these static routes are not valid.

 

       delete netmask

  This command deletes a static netmask from the netmask table.

  delete netmask Ipaddress

 
 Ipaddress  IP address of the network.

 

       save netmask

  This command saves the netmask table.

  save netmask

  After changing the netmask table, use this command to save the new netmask table to the nonvolatile memory of the PortMaster. The command save all  can also be used.
 

       Routing Information

  The following commands display routing information on the console.
 

       show ipxroutes

  This command shows the IPX routing table.

  show ipxroutes

  Note ¯ The PortMaster 4 supports IPX protocols on ComOS 4.1 and later releases.

 
 

       show propagation

  This command shows any route propagation rule set with the add propagation  command.

  show propagation

 

       show routes

  This command shows the IP routing table. See the PortMaster Routing Guide for a description of a routing table.

  show routes [String|Prefix/NM]

 
 String  Displays only routes that contain the matching String. For example, show routes local  shows only routes that contain the matching String local  in a search of the route database.
 Prefix/NM  Displays routes only to the destination indicated by the IP address prefix Prefix and netmask NM. The netmask indicates the number of high-order bits in the IP prefix.

  · Specify Prefix in dotted decimal notation.

  · Specify NM as number from 1 to 32, preceded by a slash (/)--for example, /24.

 
 
 Command> show routes 192.168.1.0/24        
 Destination  Mask  Gateway  Source  Flag  Met  Interface
 ------------  -----  --------------  -------  -----  ----  ----------
 192.168.1.0  24  192.168.2.31  rip  ND  2  ether0
 

       show route to-dest

  This command displays the route in the routing table that the PortMaster uses to forward an IP packet to the address Ipaddress .

  show route to-dest Ipaddress

 
 Ipaddress  IP address of the remote destination.
 

  This command can be useful for debugging routing problems.
  Compare the output of show routes , which displays the entire routing table for the PortMaster, with the more specific output of show route to-dest :
 
 Command> show route           
 Destination  Mask  Gateway  Source  Flag  Met  Interface
 -----------  ----  -------------  ------  ----  ---  ------
 0.0.0.0  0  192.198.110.2  local  NS  1  ether0
 192.198.110.64  27  192.198.110.4  rip  ND  2  ether0
 192.198.0.0  27  192.198.110.9  rip  ND  3  ether0
 192.198.110.0  27  192.198.110.3  local  NL  1  ether0
 192.168.32.0  24  192.198.110.9  rip  ND  2  ether0
 10.0.0.0  8  192.198.110.9  rip  ND  3  ether0

 

 
  Command> show route to-dest 192.198.110.68 
  Destination  Mask  Gateway  Source  Flag  Met  Interface
  ------------  ----  -------------  ----  ----  ---  ---------
  192.198.110.64  27  192.198.110.4  rip  ND  2  ether0

  The displayed route in the example is a network route with a 27-bit netmask. The route covers IP addresses .65 through .94, where .64 is the network address and .95 is the broadcast address. The PortMaster displays this route because .68 is a member of this subnet.
  show routes - page 7-24
 

       show table netmask

  This command shows the status of active and static special netmasks.

  show table netmask

  The netmask table also supports special netmasks that override the consolidation of hosts into subnets and subnets into networks in RIP broadcasts.
  show routes - page 7-24
[Top] [Table Of Contents] [Prev] [Next] [Index]
10 out of 25 total pages
spider@livingston.com
Copyright © 1999, Lucent Technologies. All rights reserved.