| |
|
|
Interfaces underlie the physical and network layer protocols. The type of interfaces depends on the type of port configured. The Avici router supports the following interface types:
- ATM interfaces and sub-interfaces support OC-12c Internet Protocol (IP) over Asynchronous Transfer Mode (ATM) termination on the Multi-Service Connect Module. ATM interfaces are identified by bay#/slot#/port#. Sub-interfaces are identified by bay#/slot#/port#.n where n is the number of the sub-interface. See the ATM Configuration section of this document for configuration details.
- POS interfaces support OC-3c, OC-12c, OC-48c, and OC-192c Packet Over SONET/SDH (POS) Layer 3 IP traffic. POS interfaces are identified by bay#/slot#/port#.
- Composite links consist of groups of POS interfaces that automatically distribute traffic. The POS interfaces inherit the Layer-3 attributes of their composite link. These attributes include IP address, default peer address, and MTU size. Composite link interfaces are identified by text names of up to 20 characters.
- Link aggregations consist of groups of Gigabit Ethernet interfaces that form a single Layer 2 link using the IEEE 802.3ad standard. Automatic member link activation is provided via the Link Aggregation Control Protocol (LACP). Controled removal of member links is provided by the marker protocol. The Gigabit Ethernet interface inherits a number of the link aggregation attributes including: MAC address, IP address, and MTU. Link aggregations are identified by text names of up to 20 characters.
- Gigabit Ethernet interfaces interconnect to other Gigabit Ethernet compliant devices. Gigabit Ethernet interfaces are identified by bay#/slot#/port#.
- VLAN sub-interfaces associate elements of multiple physical LANs onto a single logical network. VLANs are identified by bay#/slot#/port#.vlanID on any gigabit Ethernet interface with VLAN enabled.
- A single Ethernet interface supports attachment of customer network management entities to the Avici router server. This interface provides IP host functions and does not support routing. This interface is identified as ethernet 0.
- Multiple virtual loopback interfaces enable you to allow your IP connections to stay up no matter what interface is used to reach a neighbor. This feature eliminates the problems of dealing with normally configured interfaces that are dependent on the performance of hardware interfaces. The loopback interface is identified as loopback number.
- By default, a null interface is also configured. Null interfaces are used by routing protocols to discard traffic that is not addressed to their more-specific IP address. Null interfaces do not require any configuration.
Interfaces on the local router send and receive data to and from interfaces on peers. Peers are routers connected to the far end of the physical media between the two routers.
Preparing for Interface Configuration
The Avici router bay includes a frame of two or four shelves with ten slots in each shelf. Each slot holds one routing module or one server. Each bay can house one or two servers.
Four shelf Avici routers configured as split bays have two servers: one server controls the slots in shelf 1 and shelf 2 (upper server) and one server controls the slots in shelf 3 and shelf 4 (lower server).
Servers are identified with the ID defined by the server command.
Interfaces are identified by their bay#/slot#port#.
Slots and shelves are numbered as follows:
Figure 4-1. Numbering of Slots and Shelves in a Avici router
There are eight types of modules, each with between one and sixteen optical fiber ports (interfaces):
The interface identifier is made up of the bay number, slot number and port number delineated by slashes (/) in the following format: bay#/slot#/port#. For example, the interface identifier for the second port on a 4xOC-12c module located in slot #32 would be: 1/32/2 (bay# = 1, slot# = 32, port# = 2).
You must configure modules using the module commands before configuring interfaces. Refer to the IPriori Command-Line Interface Reference for information about the module commands. Modules are auto-configured if they are discovered and no configuration file exists. Auto-configured modules and their associated ports are administratively down.
After a module has been discovered and configured, you must use the no shutdown command in module configuration mode to activate the module.
NOTE The configuration file for each Avici router must start with the server-id command to identify the server(s).
Before you begin configuring interfaces, make sure that the server-id has been configured.Interface Default Settings
IPriori includes a variety of default settings. You may wish to accept many of these defaults and therefore skip some steps of configuring interfaces. The POS defaults are as follows:
The Gigabit Ethernet defaults are as follows:
Overview of Interface Configuration
PROCEDURE: Use the following steps to configure interfaces:
Step 1 Use the show module command to display configured modules. Refer to "Displaying Configured Modules." If the module is shut down, use the no shutdown command in module configuration mode to activate the module.
Step 2 Use the configure terminal command to enter configuration command mode.
Step 3 Use the interface command to enter interface configuration command mode.
Step 4 Optionally, modify the default settings. Refer to "Modifying Default Settings."
Step 5 Optionally, configure a description for the interface. Refer to "Configuring a Description."
Step 6 Configure a peer default address. Refer to "Configuring a Peer Default Address."
Step 7 Use the no shutdown command to activate the interface. Refer to "Enabling the Interface."
Step 8 Use the show interface command to display and verify the new interface configuration. Refer to "Displaying Interfaces."
Displaying Configured Modules
Use the show modules command to display the modules configured in your Avici router.
- In the following example, the show modules command shows that four modules have been configured:
router>show modules
MODULE 1/5:
Server Access Module attached to interface Eth2
Discovered (1xOC48c) 1 Port Packet Over SONET OC-48c/STM-16c MPLS-Capable
Configured (1xOC48c) 1 Port Packet Over SONET OC-48c/STM-16c
Physical port type is short range single mode fiber
Hardware is 1xOC48c, Version 3.1, Revision AB
Fabric version is 2.0
IPriori release version: 4.1.54.0
Operational image version: Platform: cm-d; Label: R4.1_REL.54,
Built on Oct 20 2001, 17:35:03
ROM Version: IPriori Bootrom Release 5.10 built Oct 11 2001, 19:30:38
POST Software Version: 8.22. 0
Product Id: S1/6O48-POS-1-SR-R (Rev. 04); S/N CELROM000173
Started 2 times
Last started on MON OCT 22 10:49:18 2001
Module uptime is 33 minutes, 19 seconds
Administratively Up; Current state is Up
Max number of historical logging files: 5
Non-default logging filters:
transport information
failure-protection-handler information
MODULE 1/6:
Discovered (1xOC48c) 1 Port Packet Over SONET OC-48c/STM-16c MPLS-Capable
Configured (1xOC48c) 1 Port Packet Over SONET OC-48c/STM-16c
Physical port type is long range single mode fiber
Hardware is 1xOC48c, Version 4.4, Revision 4
Fabric version is 2.0
IPriori release version: 4.1.54.0
Operational image version: Platform: cm-d; Label: R4.1_REL.54,
Built on Oct 20 2001, 17:35:03
ROM Version: IPriori Bootrom Release 5.10 built Oct 11 2001, 19:30:38
POST Software Version: 8.22. 0
Product Id: S16/O48-POS-1-SR-B (Rev. 05); S/N CELROM000083
Started 2 times
Last started on MON OCT 22 10:49:24 2001
Module uptime is 34 minutes, 14 seconds
Administratively Up; Current state is Up
Max number of historical logging files: 5
Non-default logging filters:
transport information
failure-protection-handler information
MODULE 1/7:
Discovered (2x1GbE) 2 Port Gigabit Ethernet MPLS-Capable
Configured (2x1GbE) 2 Port Gigabit Ethernet
Physical port type is multi mode fiber
Hardware is 2x1GbE, Version 1.1, Revision 07
Fabric version is 2.0
IPriori release version: 4.1.54.0
Operational image version: Platform: cm-d; Label: R4.1_REL.54,
Built on Oct 20 2001, 17:35:03
ROM Version: IPriori Bootrom Release 5.10 built Oct 11 2001, 19:30:38
Line Card FPGA Software Version: 0.10
POST Software Version: 8.22. 0
Product Id: GE2-GBE-SX-R (Rev. AX); S/N AVSROM002291
Started 2 times
Last started on MON OCT 22 10:49:29 2001
Module uptime is 33 minutes, 10 seconds
Administratively Up; Current state is Up
Max number of historical logging files: 5
Non-default logging filters:
transport information
failure-protection-handler information
MODULE 1/8:
Discovered (16xoc3c) 16 Port Packet Over SONET OC-3c/STM-1 MPLS-Capable
Configured (16xoc3c) 16 Port Packet Over SONET OC-3c/STM-1
Physical port type is intermediate range single mode fiber
Hardware is 16xoc3c, Version 1.1, Revision 07
Fabric version is 2.0
IPriori release version: 4.1.54.0
Operational image version: Platform: cm-d; Label: R4.1_REL.54,
Built on Oct 20 2001, 17:35:03
ROM Version: IPriori Bootrom Release 5.10 built Oct 11 2001, 19:30:38
POST Software Version: 8.22. 0
Product Id: ˙˙˙˙˙˙˙˙˙˙˙˙(Rev. ˙); S/N ˙˙˙˙˙˙
Started 2 times
Last started on MON OCT 22 10:49:23 2001
Module uptime is 36 minutes, 46 seconds
Administratively Up; Current state is Up
Max number of historical logging files: 5
Non-default logging filters:
transport information
failure-protection-handler information
- Module 1/5 is located in Bay #1/Slot #5 and is a server-attached-module (SAM). Module 1/5 is a 1 port OC-48c POS module. Numbering for the interface on this module is 1/5/1.
- Module 1/6 is located in Bay #1/Slot #6, has a single OC-48c POS interface. Numbering for the interface on this module is 1/6/1.
- Module 1/7 is located in Bay #1/Slot #7, has 2 Gigabit Ethernet interfaces. Numbering for the interfaces on this module is 1/7/1 through 1/7/2.
- Module 1/8 is located in Bay #1/Slot #8, has sixteen OC-3c POS interfaces. Numbering for the interfaces on this module is 1/8/1 through 1/8/16
Configuring Interface Type and Number
Use the interface command to configure an interface and change the command mode to interface configuration mode:
router(config)#interface pos 1/1/1
router(config-if)#
In this example, the interface pos 1/1/1 command specifies that you configured an interface located at Bay #1/Slot#1/Port #1 to support Packet Over SONET (POS). Notice that the command mode changes from configuration mode router(config)# to interface configuration mode: router(config-if)#.
Interfaces are not enabled until you:
- Use the ip address command to assign an IP address to the interface. Refer to "Assigning IP Addresses to Interfaces" in the "IP Routing" chapter.
- Use the no shutdown command to enable the interface. Refer to "Enabling the Interface" in this chapter.
Configuring the Ethernet Interface
A single Ethernet interface supports attachment of customer network management entities to the Avici router server. This interface provides IP host functions and does not support routing. The exchange of routing protocol messages does not take place on the Ethernet interface. This interface is identified by the interface identifier ethernet 0.
A management station located several hops away can reach the interface by configuring a static route from the intermediate routers to Ethernet interface 0.
PROCEDURE: To configure the Ethernet interface, use the following steps:
Step 1 Use the interface ethernet 0 command to configure the Ethernet interface.
Step 2 Use the ip address to assign an IP address to the interface.
Step 3 Use the no shutdown command to enable the interface.
Step 4 Use the show interface ethernet 0 command to display the interface:
router(config)#interface ethernet 0
router(config-if)#ip address 10.5.2.27 255.255.0.0
router(config-if)#no shutdown
router(config-if)#end
router#show interface ethernet 0
Ethernet 0 interface status is up, line protocol is up
Internet address is 10.210.166.11/16
Broadcast address is 10.210.255.255
Ethernet address is 00:a0:f7:0f:01:6f
MTU 1500 bytes, Bandwidth 10 Mbit/Sec
Encapsulation ARPA
Received:
3446164 bytes
1860 directed packets, 0 multicast packets, 0 broadcast packets
0 discards, 0 errors, 0 unknown protocols
Transmitted:
160260 bytes
2671 directed packets, 0 multicast packets, 0 broadcast packets
0 discards, 0 errors
Configuring Multiple Virtual Loopback Interfaces
Multiple Virtual Loopback Interfaces (VLI) improve the reliability of IP connections, no matter what interface is used to reach a neighbor. Virtual loopback interfaces resides in RAM and never goes down unless administratively shutdown. VLIs provide a stable IP address. An externally visible IP address must be assigned to the virtual loopback.
A loopback interface can be administratively shutdown using the shutdown command in interface mode. Up to 10 VLIs can be configured per Avici router. VLIs are assigned an ID with a value between 0 - 2147483647.
Use the interface loopback loopbackID command, specifying the loopback ID, in interface command mode to create a loopback interface.
Use the neighbor update-source loopback loopbackID command in router configuration mode to force BGP, for this router, to use the IP address of the loopback interface when talking to a neighbor.
Use the passive interface loopback loopbackID command in router configuration mode to suppress IS-IS or OSPF packets on the specified interface.
Example 1: To configure the loopback interface, use the following steps:
- Use the interface loopback identifier command to configure the loopback interface.
- Use the ip address to assign an IP address to the interface.
- Use the no shutdown command to enable the interface.
- Use the show interface loopback 25 command to display the interface:
router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#interface loopback 25
router(config-if)#ip address 5.1.2.1/24
router(config-if)#no shutdown
router(config-if)#end
router#show interface loopback 25
Loopback 25 interface status is up, line protocol is up
Internet address is 5.1.2.1/24
MTU 32768 bytes, BW 0.000 Mbit/Sec
Payload BW: 0.000 Mbit/Sec, Total BW: 0.000 Mbit/Sec
Encapsulation None, CRC-00
Received:
0 bytes
0 directed packets, 0 multicast packets, 0 broadcast packets
0 discards, 0 errors, 0 unknown protocols
Transmitted:
0 bytes
0 directed packets, 0 multicast packets, 0 broadcast packets
0 discards, 0 errors
router#
Example 2: In the following example, this router (Router A) is configured with a loopback interface and a neighbor (Router B) is configured to use the loopback interface for connections to Router A:
Configuration for Router A:
- The interface command configures a loopback interface.
- The ip address command specifies the IP address of the loopback interface.
- The neighbor update-source command specifies that BGP connections to the neighbor are sourced from the loopback interface's IP address.
router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#interface loopback 25
router(config-if)#ip address 160.69.2.4 255.255.0.0
router(config-if)#end
router(config)#router bgp 101
router(config-router)#network 160.69.0.0
router(config-router)#neighbor 160.69.2.3 remote-as 101
router(config-router)#neighbor 160.69.2.3 update-source Loopback 25
Configuration for Router B:
- The neighbor remote-as command specifies that Router B uses the loopback interface for connections to router A.
router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#router bgp 101
router(config-router)#neighbor 160.69.2.4 remote-as 101
Configuring a POS Interface
NOTE Be aware that the default for industry-standard routers is to obtain their clock from line. If both ends of the fiber are configured to recover the clock from line, the connection does not work, characterized by SONET failing to come up.
Be sure to include the clock source internal command in your configuration file when configuring the Avici router to interoperate with industry-standard routers.PROCEDURE: To configure a POS interface, use the following steps:
Step 1 Use the interface pos bay#/slot#/port# command name the POS interface and enter Interface Configuration command mode.
Step 2 Use the ip address to assign an IP address to the interface.
Step 3 Use the clock source internal command to select the internal clock of the interface for transmissions.
Step 4 Use the no shutdown command to enable the interface.
Step 5 Use the show interface pos bay#/slot#/port# command to display the interface:
router(config)#interface pos 1/7/1
router(config-if)#ip address 5.10.1.2 255.255.0.0
router(config-if)#clock source internal
router(config-if)#no shutdown
router(config-if)#exit
router(config)#show interface pos 1/7/1
POS 1/7/1 interface status is administratively down, line protocol is down
MTU 4470 bytes
Payload BW: 150 Mbit/Sec, Total BW: 155 Mbit/Sec
Encapsulation PPP, CRC-32
Loopback: None, Keepalive: Enabled, Scramble: Enabled
LCP: Closed, IPCP: Closed, OSICP: Closed, MPLSCP: Closed
Received:
0 bytes
0 directed packets, 0 multicast packets, 0 broadcast packets
0 discards, 0 errors, 0 unknown protocols
Transmitted:
0 bytes
0 directed packets, 0 multicast packets, 0 broadcast packets
0 discards, 0 errors
Medium Type SONET, Line Coding: NRZ, Line Type: Other
Sonet Loopback: None, Sonet Clock Source: Line
PPP: SNMP Trap link-status: enabled
Sonet/Path: SNMP Trap sonet link-status: enabled
Tx J0 Section Trace: "1"
Rx J0 Section Trace: "0"
Tx Path Trace: "<NULL>"
Rx Path Trace: "<NULL>"
Configuring a Gigabit Ethernet Interface
PROCEDURE: Use the following steps to configure and activate a 2 port gigabit Ethernet module, and configure the interfaces:
Step 1 Use the module command with the 2x1gbe keyword (use 8x1gbe when configuring an 8 port gigabit Ethernet module) to identify the 2-port Gigabit Ethernet module installed in the slot.
Step 2 Use the boot command to specify which image the module loads.
Step 3 Use the no shutdown command to activate the module.
Step 4 Use the show modules command to display the new interface:
router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#module 1/4 2x1gbe
router(config-module)#boot 2
router(config-module)#no shutdown
router(config-module)#end
router#show module 1/4
MODULE 1/4:
Discovered (2x1GbE) 2 Port Gigabit Ethernet MPLS-Capable
Configured (2x1GbE) 2 Port Gigabit Ethernet
Physical port type is multi mode fiber
Hardware is 2x1GbE, Version 1.1, Revision 07
Fabric version is 2.0
IPriori release version: 4.1.54.0
Operational image version: Platform: cm-d; Label: R4.1_REL.54,
Built on Oct 20 2001, 17:35:03
ROM Version: IPriori Bootrom Release 5.10 built Oct 11 2001, 19:30:38
Line Card FPGA Software Version: 0.10
POST Software Version: 8.22. 0
Product Id: GE2-GBE-SX-R (Rev. AX); S/N AVSROM002291
Started 2 times
Last started on MON OCT 22 10:49:29 2001
Module uptime is 33 minutes, 10 seconds
Administratively Up; Current state is Up
Max number of historical logging files: 5
Non-default logging filters:
transport information
failure-protection-handler information
Step 5 Use the interface gbe bay/slot/port command to enter interface configuration command mode.
Step 6 Optionally, use the description command to configure a description for the interface.
Step 7 Use the ip address command to configure the local address.
Step 8 Use the arp command to statically map the IP address to the interfaces MAC address of other nodes.
Step 9 Use the no shutdown command to activate the interface.
Step 10 Use the flowcontrol asymmetric command to change flow control from symmetric to asymmetric for this interface.
Step 11 Optionally use the no negotiation auto command to disable autonegotiation for the interface.
Step 12 Optionally use the no remote-fault-indication command to disable RFI if the port is connected to a third party vendor that does not support remote fault indication.
Step 13 Use the arp command configure the interface for the Snap or ARP encapsulation protocol.
Step 14 exit from the interface command mode and use the show command to display the new setting.
Step 15 Use the show interface gbe command to display detailed information about the interface:
router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#interface gbe 1/35/1
router(config-if)#ip address 5.10.1.2 255.255.0.0
router(config-if)#arp 16.12.4.1 0090.b2fd.0259
router(config-if)#no shutdown
router(config-if)#flowcontrol asymmetric
router(config-if)#no negotiation auto
router(config-if)#no remote-fault-indication
router(config-if)#arp snap
router(config-if)#end
router#show interface gbe
interface gbe 1/34/1
flowcontrol asymmetric
negotiation auto
arp snap
no shutdown
ip address 5.10.1.2 255.255.0.0
router(config-if)#end
router#show interface gbe 1/35/1
GBE 1/35/1 is up
Internet address is 5.10.1.2/16
Broadcast address is 5.10.255.255
Ethernet address is 00:90:b2:fd:00:06
MTU 4470 bytes, Bandwidth 1000 Mbit/Sec
Encapsulation ARPA
Frame type for ARP is ARPA, Frame type for IP is ARPA
Autonegotiation is Disabled, Flow control is asymmetric
Received:
474 bytes
0 directed packets, 0 multicast packets, 0 broadcast packets
0 discards, 0 errors, 0 unknown protocols
Transmitted:
2882 bytes
0 directed packets, 1 multicast packets, 1 broadcast packets
0 discards, 0 errors
The 1-Port 10 Gigabit Ethernet Module
The Avici router supports a 1-Port 10 Gigabit Ethernet module. The 1-Port 10 Gigabit Ethernet interface interconnects to other Gigabit Ethernet compliant devices. Support for the following optional clauses of IEEE 802.3-2000 standards are currently supported:
- Full duplex (clause 4)
- Flow control (clause 31)
NOTE For the 1x10gbe interface flow control is symmetric. Autonegotiation is not a function within the 10gbe specification.
Address Resolution Protocol (ARP) processing is available for the conversion of internetwork addresses to physical addresses hard coded in the network interface hardware. ARP support includes:
- Recognition of multiple MAC layer end points per IETF RFC 826
- Ability to clear individual ARP entries from the cache
- Ability to flush the cache on a per interface, module, or router basis
- Ability to globally define ARP cache entry timeout
- Ability to display ARP entries
- Ability to define a static binding
Activating a 1-Port 10 Gigabit Ethernet Module
PROCEDURE: Use the following steps to configure and activate a module.
Step 1 Use the module command to identify the module to be activated. Module type is auto detected.
Step 2 Use the boot command to specify which image the module loads.
Step 3 Use the no shutdown command to activate the module.
Example: In the following example:
- The module command assigns a 1-Port Gigabit Ethernet module to bay 1, slot 1.
- The no shutdown command enables the module.
- The show modules command displays the new configuration:
router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#module 1/1 1x10gbe
router(config-module)#no shutdown
router(config-module)#end
router#show modules
MODULE 1/1:
Discovered (1x10GbE) 1 Port 10 Gigabit Ethernet MPLS-Capable
Configured (1x10GbE) 1 Port 10 Gigabit Ethernet
Physical port type is multi mode
Hardware is 1x10GbE, Version 1.1, Revision 1
Fabric version is 3.0
IPriori Bootrom Release 5.2.1020
Operational image version: Platform: modc-d; Label: R5.2_DEV.20,
Built on Jun 16, 2003, 12:09:45
ROM Version: Ipriori Bootrom Release 6.22 built May 12 2003, 19:25:10
Line Card FPGA Software Version: 0.3
Switch Card FPGA Software Version: 0.17
POST Software Version: 11.14.0
Product Id: P4-S16O48-SR-R (Rev. AX); S/N AVCRBM000077
Module CLEI Code: IP5IBA0AAA
Last started on WED JUN 18 17:35:31 2003
Module uptime is 0 weeks, 0 days, 0 hours, 29 minutes, 40 seconds
Administratively Up; Current state is Up
Max number of historical logging files: 5
Configuring/Deleting ARP Bindings
About ARP Bindings
The IP network layer is a four-byte address. The Ethernet link layer is a six-byte MAC address. These two address types must be mapped (bound) together to allow the transmission of data between the layers.
Two types of IP to MAC address bindings or entries are supported: static and dynamic.
- Static is a manual entry from the CLI using the arp command in interface mode.
- Dynamic binding requires a protocol to bind addresses between the two layers. Address Resolution Protocol (ARP) dynamically binds the configured IP network layer address with the Ethernet link layer hardware address.
Static bindings have absolute precedence over dynamic bindings. If a binding for a given IP address already exists when a static binding for that address is specified, the MAC address on the static binding takes precedence. All subsequent updates for that IP address are discarded.
A dynamic database of address pairings is kept in the ARP cache on each Avici router module. Dynamic bindings are learned from the ARP protocol in three ways( as described in RFC 826):
- The Avici router sends out an ARP request for an IP address. The ARP reply provides the IP address requested by the Avici router.
- The Avici router receives an ARP request. The new binding is the source IP and MAC address.
- An existing binding for this Avici router is updated by an ARP request or reply.
Dynamic bindings are subject to timeout or aging policy that takes into account both transmit inactivity as well as failure to periodically refresh. A timer is started when a new binding is entered for the first time in the ARP Cache. This timer is reset whenever that binding is updated, or whenever a packet is sent to the entry's IP/MAC address. If the timer expires, the binding is removed from the ARP Cache.
Dynamic bindings can also be deleted manually using the CLI.
Static bindings are also placed in the ARP Cache; however, they're not considered for deletion on the flush command. These bindings are also not subject to any timeouts.
Configuring a Static Binding
PROCEDURE: Use the arp command to manually enter a static binding.
Step 1 Use the interface gbe command to enter Interface configuration command mode for Gigabit Ethernet for the specified port.
Step 2 Use the arp ipaddress mac-address command to enter the IP/MAC address pair into the ARP cache.
Step 3 Use the show ip arp command to display the configuration:
router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#interface gbe 1/4/1
router(config-if)#arp 11.25.1.50 0090.b2fd.0259
router(config-if)#end
router#show interface
interface gbe 1/25/1
ip address 11.25.1.1 255.255.255.0
no shutdown
arp 11.25.1.50 0090.b2fd.0259
router#show ip arp
IP Address H/W Address Flags Interface Age (min)
10.210.0.1 00:01:81:2c:5e:3 C Ethernet 0 15
ARP Table of Gigabit Ethernet interfaces
IP Address H/W Address Flags Interface Age(min) Retry
11.25.1.50 00:90:b2:fd:02:59 S GBE 1/4/1 - -
6.1.1.2 00:10:94:02:01:f7 S GBE 1/6/1 - -
6.2.1.2 00:10:94:02:01:05 S GBE 1/6/2 - -
Deleting Bindings
Delete a Single Binding
PROCEDURE: Use the following steps to delete a single binding from the ARP cache:
Step 1 Use the interface gbe command to enter interface mode for Gigabit Ethernet for the specified port.
Step 2 Use the no arp ipaddress mac-address command to delete specified IP/MAC address pair.
or:
Step 1 Use the interface gbe command to enter interface mode for Gigabit Ethernet for the specified port.
Step 2 Use the clear arp-cache ipAddress command to clear the ARP cache for the specified IP address.
Clearing the ARP Cache
PROCEDURE: Use the clear arp-cache command to clear the ARP cache for a specific IP address, an interface, a module, or for all Gigabit Ethernet interfaces for this Avici router.
Syntax: clear arp-cache {all | interface bay/slot/port | module bay/slot | entry ipAddress}
Step 1 Use the interface gbe command to enter interface mode for Gigabit Ethernet for the specified port.
Step 2 Use the clear arp-cache all command to clear the ARP cache for all the Gigabit Ethernet interfaces for this Avici router. This command only affects dynamic entries. All static entries entered using the arp command must be manually deleted using the no arp command.
or:
Step 1 Use the interface gbe bay/slot/port command to enter Interface configuration command mode for the specified port.
Step 2 Use the clear arp-cache interface command to clear the ARP cache for the specified Gigabit Ethernet interface.
or:
Step 1 Use the clear arp-cache module command to clear the ARP cache entries for all interfaces on the specified Gigabit Ethernet module.
Example: The following command clears the ARP cache for all Gigabit Ethernet interfaces on the module in bay 1, slot 5.
router#clear arp-cache module 1/5
router#
Modifying Default Settings
In the output from the show interface command, the interface comes up with many values preset to defaults. Refer to "Interface Default Settings."
You can operate your interfaces using defaults or you can modify the defaults. Do not modify the defaults if you do not have a clear understanding of their behavior in your network.
The following sections describe the steps to modify the defaults.
Modifying CRC
The Cyclical Redundancy Check (CRC) is a calculation used to check for transmission errors. By default, the number of bits in a CRC is 32. A CRC of 32 provides better error detection, but increases overhead. SONET interfaces operate with very few errors, and the CRC for a properly operating POS interface can be set to 16.
NOTE Both ends of the connection must use the same value for CRC.
Use the crc command to set the length of the CRC to16 bits.
In the following example, the crc command sets the CRC to 16, and the show interface pos command displays the new setting:
router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#interface pos 1/4/1
router(config-if)#crc 16
router(config-if)end
router#show interface 1/4/1
POS 1/4/1 is up, line protocol is up
IP address is 1.2.3.1 255.255.0.0
MTU 4470 bytes, BW 155 Mbps
Encapsulation PPP, CRC-16
.
.
.
Modifying the Keepalive Timer
Keepalive messages check the health of a link. The keepalive timer is the number of seconds a router waits between sending keepalive messages.
If no response is received from the remote peer, the local router retransmits the keepalive message up to five times. If no response is received from the remote peer after the five retransmissions, the local router brings down the link and withdraws the route from the routing table.
If you change the keepalive timer at one end of a link, you must assure that the other end is configured for the same value, otherwise it is possible that no communication will take place between the two ends of the link.
In the following example, the keepalive command sets the keepalive interval timer to 15 seconds and the show interface pos command displays the setting:
router(config)#interface pos 1/1/1
router(config-if)#crc 16
router(config-if)#end
router#show interface pos 1/1/1
.
.
.
router(config)#interface pos 1/1/1
router(config-if)#keepalive 15
router(config-if)#end
router#show interface pos 1/1/1
.
.
.
POS 1/1/1 is down, line protocol is down
MTU 4500 bytes, BW 155 Mb/Sec
Encapsulation PPP, CRC-16
Loopback: None, Keepalive: Enabled, Scramble: Enabled
.
.
.
Modifying MTU
Maximum Transmission Unit (MTU) specifies the largest size packet transmitted from this interface. Valid values for MTU are integers from 64 to 10240.
NOTE For Gigabit Ethernet, VLAN, or Aggregate-link interfaces, when the protocol is IS-IS, packets transmit with a maximum MTU of 1500 bytes. If lsp-mtu is configured, a POS interface transmit MTU is decided based on the configured lsp-mtu. This restriction does not apply to receiving packet MTU for these interfaces.
Two considerations when configuring MTU:
- The best forwarding rate is obtained when MTU values are the same over all links in a given path.
- Fragmentation is costly and should be avoided if possible.
In the following example, the mtu command sets the maximum transmission unit to 4500 for a POS interface and 1200 for Gigabit Ethernet interface, and the show running-config command displays the POS setting:
router(config)#interface pos 1/1/1
router(config-if)#mtu 4500
router(config-if)#exit
router(config)#interface gbe 1/2/1
router(config-if)#mtu 1200
router(config-if)#end
router#show interface pos 1/1/1
.
.
.
POS 1/1/1 is down, line protocol is down
MTU 4500 bytes, BW 155 Mb/Sec
Encapsulation PPP, CRC-16
Loopback: None, Keepalive: Enabled, Scramble: Enabled
.
.
.
Modifying PPP Negotiation Timer
PPP negotiation-timeout is the maximum interval the router waits without receiving a response from a peer, before a new attempt to negotiate with the peer is started.
In the following example, the ppp negotiation-timeout command sets the amount of time allowed for LCP negotiations to 20 seconds, and the show running-config command displays the new setting:
router(config)#interface pos /1/1/1
router(config-if)#ppp negotiation-timeout 20
router(config-if)#end
router#show running-config
.
.
.
interface pos 1/1/1
mtu 4500
ppp negotiation-timeout 20
.
.
.
Configuring PPP MTU Negotiation
IPriori provides for enabling or disabling PPP negotiation of the Maximum Transmission Unit (MTU) value between peers. MTU specifies the largest size packet transmitted from this interface. This value is used while negotiating LCP on a POS interface. The local interface negotiates to the lower packet size of the peer and local interface by default. The interface can be configured not to negotiate the MTU value between this interface and a peer. If PPP negotiation of MTU is disabled, this interface keeps the configured MTU value and replies to the peer with a request that the peer change its MTU value to agree with this interface.
Use the mtu-negotiate command to enable PPP MTU negotiation on this interface.
Use the no mtu-negotiation command to disable PPP MTU negotiation on this interface.
Example 1: In the following example, the mtu command sets the maximum transmission unit to 4500, disables PPP negotiation for MTU, and the show interface pos command displays the setting:
router(config)#interface pos 1/1/1
router(config-if)#mtu 4500
router(config-if)#no mtu-negotiation
router(config-if)#end
router>show interface pos 1/1/1
POS 1/1/1 interface status is up, line protocol is up
Internet address is 201.1.1.10/24
MTU 4500 bytes
PPP MTU negotiation disabled
.
.
.
Example 2: In the following example, the mtu-negotiation command enables PPP MTU negotiation on the 1/1/1 interface:
router(config)#interface pos 1/1/1
router(config-if)#mtu-negotiation
router(config-if)#end
router#show interface pos 1/1/1
POS 1/1/1 interface status is up, line protocol is up
Internet address is 201.1.1.10/24
MTU 4470 bytes
PPP MTU negotiation enabled
.
.
.
Modifying Flow Control
Flow control controls traffic rates during periods of congestion on a Gigabit Ethernet interface. There are two types of IEEE 802.3x flowcontrol: symmetric and asymmetric. Asymmetric flow control is used to allow the local port to determine whether flow control will be performed on the remote port. During periods of local port congestion, the local port will send a pause request for the remote port to stop transmitting. Symmetric flow control is used to allow the local port to perform flow control only if the remote port can also perform flow control. If the remote port is not able to perform flow control locally, the local port will also not perform flowcontrol.
Flow control defaults to Symmetric. Use the flowcontrol asymmetric command to change flow control to asymmetric for this Gigabit Ethernet interface.
Example: In the following example:
- The interface gbe command specifies Gigabit Ethernet interface and changes the command mode to interface configuration
- The flowcontrol asymmetric command to sets flow control for this interface to asymmetric.
- The show command displays the new setting:
router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#interface gbe 1/34/1
router(config-if)#flowcontrol asymmetric
router(config-if)#show
interface gbe 1/34/1
ip address 197.1.1.17 255.255.255.240
flowcontrol asymmetric
arp snap
negotiation auto
no shutdown
Modifying Auto Negotiation
Autonegotiation detects the capabilities of the device at the other end of the link and attempts to configure the highest performance mode of interoperability between the two devices. Auto Negotiation is enabled by default. Use the no negotiation auto command to disable autonegotiation for this Gigabit Ethernet interface.
NOTE It is recommended that autonegotiation be enabled on the interface.
NOTE For the 1x10gbe interface flow control is symmetric. Autonegotiation is not a function within the 10gbe specification.
Example: In the following example:
- The interface gbe command specifies a Gigabit Ethernet interface and changes the command mode to Interface configuration.
- The no negotiation auto command disables autonegotiation on the specified interface.
- The show command displays the new configuration:
router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#interface gbe 1/34/1
router(config-if)#negotiation auto
router(config-if)#show
interface gbe 1/1/1
no negotiation auto
no shutdown
mpls traffic-engineering tunnels
ip address 197.1.1.17 255.255.255.240
Modifying Remote Fault Indication
Remote Fault Indication (RFI) provides the ability for a remote Gigabit Ethernet link to signal an RFI to the local end that it no longer sees the link in the case where a single strand of fiber in a link is broken/disconnected. RFI is enabled by default. It is recommended that RFI be enabled as long as both ends of the link support RFI. Disable RFI if the other end of the link is a third party router that does not support RFI. Use the no remote-fault-
indication command to disable RFI.Example: In the following example, the no remote-fault-indication command disables RFI on a Gigabit Ethernet interface:
router(config)#interface gbe 1/1/1
router(config-if)#no remote-fault-indication
router(config-if)#end
router#
Configuring a Description
Text descriptions provide an additional method to identify an interface. The description command enables you to add a line of descriptive text of up to 128 characters to the interface configuration. This text is displayed when you use the show interfaces, and show running-config commands.
In the following example, the description command configures a description and the show-running-config command displays the new setting:
router(config)#interface pos 1/1/1
router(config-if)#description Chicago-Lab4 Row7
router(config-if)#end
router(config)#show running-config
.
.
.
interface pos 1/1/1
description Chicago-Lab4 Row7
mtu 4400
crc 16
.
.
.
Configuring a Peer Default Address
To establish an IP connection with a peer using composite links or an OC-192c interface, IPriori must know the IP address of the interface on the peer. The peer default address is an IP address sent to any peer connecting to this interface. The default address eliminates the requirement to specifically identify the IP address of every peer connecting to this interface.
In the following example, the peer default ip address command sets the IP address of the remote interface to 10.5.12.126 and the show running-config command displays the new setting:
router(config)#interface pos 1/1/1
router(config-if)#peer default ip address 10.5.12.126
router(config-if)#end
router#show running-config
.
.
.
interface pos 1/1/1
peer default ip address 10.5.12.126
mtu 4400
ppp negotiation-timeout 20
.
.
.
Configuring Port Mirroring and Netflow Sampling
The mirror command is used to:
- Define a packet filtering destination port when a sample is specified in the packet filtering access-list configured for this interface. This context is referred to as port mirroring.
- Enable Netflow sampling on this interface.
The mirror command can be configured per interface for either port mirroring or Netflow sampling, but not both.
Port mirroring is always used in the context of packet filtering. Port mirroring can only take place if a sample is associated with the packet filtering access-list configured on the interface. A sample can be associated with any access-list entry: permit or deny. You can assign any POS or Gigabit Ethernet interface as the destination port for mirrored packets. Up to 32 ACE entries per module may be configured to mirror packets when an access-list match occurs.
See the "Packet Filtering Access Lists" in IPriori Software Configuration Guide (Vol. 2) for port mirroring information and an example within a packet filtering context.
Netflow is a means of collecting and exporting packet summaries to an external collector. Collected summaries can be used by applications that analyze the data on the collector and provide traffic usage statistic and profiling information. Unlike port mirroring, the mirror command does not specify a destination port for Netflow sampled packets. The destination collector for Netflow is specified using the ip flow-export destination command. The mirror command is used to enable Netflow sampling.
See the "Configuring Individual Netflows" in IPriori Software Configuration Guide (Vol. 2) for information and an example of the mirror command within a Netflow sampling context.
Enabling the Interface