Rte format, Ripng packet processing procedure, Request packet – H3C Technologies H3C SR8800 User Manual
Page 295
279
Figure 102 RIPng basic packet format
Packet header description:
•
Command—Type of message. 0x01 indicates Request, 0x02 indicates Response.
•
Version—Version of RIPng. It can only be 0x01 now.
•
RTE—Route table entry, 20 bytes for each entry.
RTE format
The following are types of RTEs in RIPng:
•
Next hop RTE—Defines the IPv6 address of a next hop.
•
IPv6 prefix RTE—Describes the destination IPv6 address, route tag, prefix length and metric in the
RIPng routing table.
Figure 103 Next hop RTE format
IPv6 next hop address is the IPv6 address of the next hop.
Figure 104 IPv6 prefix RTE format
IPv6 prefix RTE format description:
•
IPv6 prefix—Destination IPv6 address prefix
•
Route tag—Route tag
•
Prefix len—Length of the IPv6 address prefix
•
Metric—Cost of a route
RIPng packet processing procedure
Request packet
When a RIPng router first starts or needs to update entries in its routing table, usually a multicast request
packet is sent to ask for needed routes from neighbors.
- H3C SR6600-X H3C SR6600 H3C WX6000 Series Access Controllers H3C WX5000 Series Access Controllers H3C WX3000 Series Unified Switches H3C LSWM1WCM10 Access Controller Module H3C LSWM1WCM20 Access Controller Module H3C LSQM1WCMB0 Access Controller Module H3C LSRM1WCM2A1 Access Controller Module H3C LSBM1WCM2A0 Access Controller Module