how to add ipv6 address to switch

Stack Exchange Network

Stack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Super User is a question and answer site for computer enthusiasts and power users. It only takes a minute to sign up.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

How do I assign IPv6 addresses manually?

So I'm still rather clueless with IPv6, but I wanted to try something with my network today. Currently, I assign IPv4 LAN addresses manually, so that my router is 192.168.0.1 , then my first computer is 192.168.0.2 , and so on.

So far, I haven't been able to figure out how to do this with IPv6. Or is the process completely different that this is not how it would work?

Router is an Archer C4000, and my main system runs Ubuntu 19.04

EDIT: To clarify with how I manually set network IP addresses, my router has a page where I can set an address of my choosing to a MAC address. No configuration is done outside of the router.

• Please edit question and indicate how you assign LAN addesses manually. (On the router only? On your first computer as well?) I suspect you just set a network range on the router, and then addresses are not assigned "manually", but by DHCP from the router. On IPv6 then your router needs to advertise a subnet. On Ubuntu, you can set both IPv4 and IPv6 address manually with ip addr add ... . –  dirkt Sep 10, 2019 at 11:22
• Edited. I'm going to guess then that it is assigned from a range, but then I limit what can be assigned based on MAC addresses. If I'm setting the IP address manually on each device, is there any further configuration that needs to be done (apart from avoiding duplicates), or will the router just accept that device A is going to use its own configured address? –  hiigaran Sep 10, 2019 at 12:00
• If there's a page where you can assign an IPv4 address based on a MAC address, then this is for static addresses assigned via DHCP from the router. IPv6 works differently. While there is DHCPv6, the normal way is to use SLAAC , and let each computer pick an IPv6 address based on the announced subnet prefix.So this page won't help you to assign IPv6 addresses... –  dirkt Sep 10, 2019 at 12:05

2 Answers 2

To clarify with how I manually set network IP addresses, my router has a page where I can set an address of my choosing to a MAC address. No configuration is done outside of the router

This usually isn't called "manual configuration" to avoid confusion (from the LAN hosts' point of view, it is still automatic configuration). The usual terms are "static DHCP lease" or "DHCP reservation".

Overall, the process in IPv6 is usually completely different.

In IPv6 primary address auto-configuration mechanism (SLAAC) is completely stateless: the router does not issue individual addresses; it only periodically advertises the subnet address prefix and each host just combines it with its own chosen suffix. The router cannot limit hosts to just a specific sub-range; in fact the router does not receive any feedback about hosts' chosen address at all.

(Depending on each device's OS, the suffix might be a MAC address in traditional RFC4862 SLAAC; it might be a static hash value in RFC7217; it might be completely random in RFC4941 "Privacy Extensions"; and it might even be a user-provided value if the OS allows that.)

For example, the router advertises 2001:db8:123:456::/64 as the LAN address prefix; client A combines it with its own MAC address and begins using 2001:db8:123:456:6af2:68fe:ff7c:e25c .

That said, DHCP does exist in the IPv6 world and handles address leases in much the same way as IPv4 DHCP does. That means you can create DHCPv6 address pools, you can configure static address leases in DHCPv6, and so on. But not all clients support DHCPv6 at all (e.g. Android does not), so having SLAAC alongside is almost unavoidable.

So if you have a DHCPv6-capable client on a DHCPv6-capable network, chances are it'll have both a nice DHCPv6-assigned address and a longer SLAAC-autoconfigured address.

If I'm setting the IP address manually on each device, is there any further configuration that needs to be done (apart from avoiding duplicates), or will the router just accept that device A is going to use its own configured address?

As you can see above, that's how IPv6 address configuration works anyway .

Your router's manual is found in User Guide and contains for IPv6 only an option for entering a static IPv6 address for the router itself (as received from the ISP).

The section about specifying the IP addresses that the router assigns by MAC address does not say whether they are IPv4 or IPv6, but I think it is highly unlikely that this will work for IPv6. And here is why.

IPv6 is quite unlike IPv4 in the sense that the long IPv6 address is made up of two parts. The first (the prefix) is assigned by the ISP. The second is assigned locally by the router or by each computer and is usually a random value based on the MAC address.

This means that the router does not control the IPv6 prefix which the ISP can change whenever it likes. You can force your computer to use a static IPv6 address, but only if it agrees with the ISP. You may be able to ask the ISP for a static IPv6 address, but that is a bad idea.

The reason it's a bad idea, is that all your devices are visible to the entire Internet by their IPv6 address (unless the router intervenes). Therefore having a fixed IPv6 address just makes tracking you that much easier.

If you wish, you would in Windows set a computer's static IPv6 inside Start > Network > Network and Sharing Center > Change Adapter Setting , right-click on the Ethernet connection IPv6 and choose Properties, right-click "Internet Protocol Version 6 (TCP/IPv6)" and click on Properties, the set "Use the following IPv6 address".

But the fact you can does not mean you should. The only place that static IPv6 addresses makes sense is inside a local network which is not connected to the Internet.

• What about if I wanted to run a web server? I'm constantly traveling for work, and I would love to have access to one of the computers at home which runs 24/7. I'd need to set a static IPv6 for this to work, wouldn't I? –  hiigaran Sep 10, 2019 at 19:23
• A general solution would require an IPv6 dynamic DNS provider. See for that the article dynv6.com: IPv6 dynamic DNS done right . –  harrymc Sep 10, 2019 at 19:29
• @harrymc Help me understand your logic, why would a server in a data center have a static IP but a server at home a dynamic one? In what world does that make any sense? –  Chazy Chaz Jul 29, 2022 at 12:40
• In a world where the ISP attributes to users dynamic IP addresses. –  harrymc Jul 29, 2022 at 12:51

You must log in to answer this question.

Not the answer you're looking for browse other questions tagged networking router ipv6 ..

• The Overflow Blog
• Can GenAI 10X developer productivity?
• How to scale a business-ready AI platform with watsonx: Q&A with IBM sponsored post
• Featured on Meta
• We're rolling back the changes to the Acceptable Use Policy (AUP)
• Seeking feedback on tags update

Hot Network Questions

• What should I do if I suspect one of the journal reviews I got is AI-generated?
• Folding chairs/tables on Shabbat
• Why does compiler optimization flag cause function definitions other than main() to break program in AVR ATMega C code?
• How do you publish on a ROS topic when the message type is not known?
• Is Venus' north towards Earth's south
• I need guidance in this integral
• Did Iraq declare outright support for Hamas after Oct 7?
• Can you ever be certain that you will not be tried for an alleged crime?
• Doubts: continuity VS existence of the limit
• to paint someone (other than oneself) "into a corner"
• Why does concept of degree of unsaturation not work for fullerene molecule?
• Why do oversized images appear better than images that are the correct size on the web?
• Which parent should you start playing against?
• Formatting LaTEX equations
• Why does a plastic bag rip when it is raised to a higher position when being held but not when it is stationary?
• How would the government cover up a nuclear war?
• Macro to remove all non-numeric characters from its argument
• Can a creature controlled by Dominate Person warn his allies?
• What stops stolen software from offering a valid license?
• How to perform a "bridge edge loops" on two geometries using nodes
• What is the difference between Super Value Economy, Flexi-Saver Economy, and Flexible Economy?
• Why can a model's SHAP values change on a new dataset?
• SRAM quick link reuse
• How does this scam work where a potential employer emails me the scan of a check to deposit?

Your privacy

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy .

Switch Your Network To IPv6

Introduction

IPv6 is an "emerging" technology that has been emerging for some time…at least in the U.S. Development on IPv6 began in the mid 1990’s and here we are in 2015 with most of the U.S. yet to implement IPv6. (Google statistics show that less than 14% of the US has adopted IPv6.)

Interest in IPv6 is increasing, though. With IPv4 addresses nearly exhausted, ISPs, network device manufacturers and even end-users are taking notice and deploying or working on implementing IPv6.

I covered some IPv6 terms and basics a few years back. So this article is intended as a practical how-to for moving a home/SOHO network to an IPv6 internet connection.

Before we start, it’s important to note that IPv4 and IPv6 are not mutually exclusive. In fact, you can and will likely use both at the same time. A network running both IPv4 and IPv6 is said to be “dual stacked.” IPv4 may be phased out over time. But it is likely we’ll be running in dual stack mode for some time.

Making The Switch

Step 1: Determine whether your Interent Service Provider (ISP) supports IPv6

The best way is to check your ISP’s help pages, or do a quick search using your ISP’s name and "IPv6". Or as a last resort, you could even call customer support.

The road to IPv6 was a long one for me. My ISP was Windstream and I wanted to experiment with IPv6. But Windstream didn’t support it. Periodically, I’d call customer service and ask if they supported IPv6. But the Windstream customer service usually didn’t understand my question and couldn’t provide an answer.

However, I recently switched to Time Warner as my ISP, prompted by a new customer promotion. After switching, I noticed on Time Warner’s website that “TWC has rolled out IPv6 to over 90% of its residential network”. So, I set about getting an IPv6 internet connection.

Step 2: Determine whether your modem and router support IPv6

ISPs that support IPv6 usually list supported devices. (Time Warner lists supported devices here .) My modem is a Motorola SB6121 and is listed as "approved for use with Time Warner Cable high-speed data services and supports IPv6." You can access the SB6121 at 192.168.100.1 , but the only available option is to reset it. I didn’t have to change anything on the cable modem to enable IPv6.

Since I’m not using a Time Warner router, I was on my own figuring out if my router supports IPv6. Fortunately, I recently reviewed the Linksys LRT224 router and worked with one of their engineers, who assured me the LRT224 supports IPv6.

If you don’t have a friend at your router’s maker, dig into your router’s admin pages and look for IPv6 settings. The ones you want are usually found in the WAN configuration section. Here’s the relatively simple options provided on an old Linksys E4200 . I suspect they would not be much help in getting a working IPv6 connection.

Linksys E4200 IPv6 WAN connection options

Here are more comprehensive options on a D-Link DIR-615 , which look like they would provide a better shot at getting you connected.

D-Link DIR-615 WAN connection options

As noted earlier, other devices on your network, such as switches, access points, and internal network devices, do not need to support IPv6 for you to deploy IPv6. They will continue to operate at IPv4. But you should have at least one device that supports IPv6. You’ll need it to determine whether you have a proper IPv6 internet connection. Fortunately, Windows 7 and above and MacOS 10 both support IPv6.

Making the Switch – more

Step 3: Enable IPv6 on your router

To enable IPv6 on the LRT224, I enabled dual-stack in the IP Mode screen in the Setup > Network menu, as shown below.

Enable IPv6

Once I enabled dual-stack, I noticed the WAN interface on my router now had a global IPv6 address, but my PCs did not. A global IPv6 address is similar to what we refer to as a "public" IPv4 address. Global IPv6 addresses typically have a first digit of 2 .

In addition to the IPv6 address on my WAN interface, I knew I needed a global IPv6 subnet (also known as a prefix) to assign to my LAN, but I had no idea how to get one. I called Time Warner for guidance, but received none, to put it politely. Eventually, I reached out to Linksys and they told me to enable the DHCP-PD feature on the router. DHCP-PD (PD = Prefix Delegation) is a component of DHCPv6, which is the version of DHCP used for IPv6 addressing.

In the below screenshot, you can see DHCP-PD enabled on the LRT224 and an IPv6 prefix successfully received from Time Warner. (Note, in the below screenshot and others throughout this article, I’ve replaced digits of my actual IPv6 addresses with “xxxx.” Since these are globally accessible IPv6 addresses, it isn’t wise to publish them on the Internet.)

With DHCP-PD enabled, an end user’s router will send a DHCPv6 request to the ISP for an IPv6 address and an IPv6 prefix. The ISP will respond with an IPv6 address for the router’s WAN interface and an IPv6 prefix the router can use for the LAN.

As shown in the below wireshark output of the DHCPv6 reply from Time Warner to my LRT224, I received a WAN IPv6 address of 2606:a000:dfc0:15:a1f4:4829:a55d:xxxx , a LAN IPv6 prefix length = 64 and a LAN prefix = 2606:a000:1205:xxxx: . Subsequently, and as I’ll show in Step 4, devices on my LAN will get an IPv6 address starting with 2606:a000:1205:xxxx .

DHCPv6 Wireshark trace

Note that a /64 prefix is typically the smallest IPv6 subnet assigned since it is required for SLAAC (stateless address autoconfiguration) to work (more on SLAAC shortly). But it’s possible to subnet an IPv6 address to a smaller subnet than /64 if you use DHCPv6 or static addressing. In case you’re wondering, a /64 IPv6 subnet is 2 64 addresses, i.e. 18,446,744,073,709,551,616. Enjoy!

Step 4: Get an IPv6 address on your device

This should happen automatically for IPv6-enabled devices. But a quick way to force it to happen on a Windows 7 or higher system is to type ipconfig /release and then ipconfig /renew from the command prompt. Once complete, type ipconfig /all . The output will look something like that below.

Notice the line labeled Temporary IPv6 address with an arrow next to it on the left. This is a global IPv6 address my PC uses when I go to a public IPv6 website. Notice that the first half of that address matches the prefix I received via DHCP-PD.

ipconfig /all

A new issue with IPv6 is Stateless Address Autoconfiguration (SLAAC). SLAAC is an IPv6 method devices use to request network information and generate their own unique IPv6 addresses without a DHCP server. Windows labels addresses generated via SLAAC as “Temporary.” In this case, the global IPv6 address my Windows PC is using has been generated via SLAAC.

SLAAC is considered a more efficient means of delivering IPv6 addresses, as a DHCP server isn’t needed and router resources aren’t consumed maintaining a list of devices and their associated address. The downside is SLAAC eliminates the convenience of viewing a DHCP table on the router, displaying devices and their IP addresses. On the LRT224, the DHCPv6 server is disabled by default. You can manually configure DHCPv6 on the LRT224, which would then provide the ability to see devices and their IPv6 addresses.

You’ll also notice an IPv6 device has multiple IPv6 addresses. It is common for a device to have multiple IPv6 addresses, each with a different purpose. In addition to global addresses, other IPv6 address types include link-local addresses, multicast addresses and unique local addresses.

Link-local addresses, which start with FE80 , are automatically created by IPv6 enabled devices for local communication only and are not routable addresses. Multicast addresses, which start with FF , are used for various purposes, such as to request router information via IPv6 Neighbor Discovery Protocol (NDP). Unique local addresses, which start with FC , are similar to private addresses in IPv4. However, since Network Address Translation (NAT) is typically not used in IPv6, the use of unique local IPv6 addresses has limitations.

Clearly, all these addresses are going to require a change in the way we think about LAN address space!

Verification

IPv6 is now enabled on my network and all devices capable of running IPv6 should be good to go. My Windows 7 and Windows 8 PCs all had global IPv6 addresses without any configuration. My Macbook running MacOS 10.9.5 and my iPhone 4 running iOS 7.0.4 also had global IPv6 addresses without any action on my part.

To verify IPv6 is working, just browse to test-ipv6.com . This website will tell you the global IPv6 address used by your device and verify your IPv6 functionality. As you can see from the screenshot below, the test shows my PC is communicating via IPv6 over the Internet. Notice also that the IPv6 address detected by the IPv6 test site matches the IPv6 address displayed in the ipconfig /all output shown above.

Another useful test is to type ping google.com from the command line. Google has enabled IPv6, and since IPv6 is now supported on my network, my PC will use IPv6 when communicating to an IPv6 enabled destination. As you can see from the ping output, I’m getting an IPv6 response from google.com to my ping.

The above test also illustrates the “intelligence” of IPv6. You don’t have to decide when to use IPv6. An IPv6 enabled device will use IPv6 when available and fall back to IPv4 when necessary. In the above example, my PC first did a DNS lookup on google.com and received both IPv6 and IPv4 addresses. You can try this yourself. On an IPv6-enabled system, type nslookup google.com from the command line. As you can see below, the DNS lookup returned both the IPv6 address and IPv4 addresses for google.com.

IPv6 and DNS

As mentioned previously, IPv6 eliminates the need for NAT for IP address conservation. However, NAT’s "firewall" provides a measure of security by hiding the IPv4 addresses of LAN devices from the Internet. With global IPv6 addresses, NAT is not needed to share a measly single (temporary) IPv4 address, grudgingly assigned by your ISP; you have 18,446,744,073,709,551,616 addresses! But devices that haven’t made the jump to IPv6 will still need your router’s NAT to share that single IPv4 WAN IP. IPv6 traffic, on the other hand, will simply be routed.

Without NAT, I wondered whether the LRT224 firewall would provide any protection for devices with IPv6 addresses, so again I reached out to Linksys. Linksys informed me that the LRT224 firewall “by default will block a connection initiated from the WAN side unless access rules allow it.” So just because an IPv6 address is "global", doesn’t mean it can be freely accessed outside your LAN. Whew!

Further investigation of the LRT224 showed it had a section for both IPv4 and IPv6 in its firewall settings. Below is a screenshot of the IPv6 Access Rules. The default configuration on the LRT224 firewall is the same for both IPv4 and IPv6; all traffic initiated from the WAN blocked by default and all traffic initiated from the LAN allowed. As with IPv4, you can still open ports to a specific device, but that can be tricky, given the lack of DHCP client lists. I’ll come back to this in a follow-on piece.

IPv6 Firewall

Closing thoughts.

Certainly, there are pros and cons to IPv6. On the pro side, IPv6 provides unlimited addresses and resolves the issue with IPv4 address exhaustion. Another value to IPv6 is improved connectivity. NAT can be problematic for protocols like VPN tunnels and VoIP. NAT can cause call connection and call quality problems for VoIP users. NAT can also cause problems if you want to host a server, perhaps for gaming or some other purpose. Having a global IPv6 address on your VoIP device or game server removes NAT from the equation and improves connectivity.

IPv6 also opens up a lot of cool new technologies. Many IPv6 enabled routers support IPv6 technologies such as 6to4 and 6rd. 6to4 allows IPv6 packets to be sent over an IPv4 network. 6to4 can be useful if you’re trying to connect to a IPv6 destination and your ISP does not yet support IPv6. 6rd refers to IPv6 rapid deployment and is similar to 6to4, as it also provides a means to transmit IPv6 over an IPv4 network. IPv6 also holds the promise of increased security by supporting IPsec security between IPv6 endpoints.

I think the biggest downside to IPv6 is the lack of information and relative immaturity of the technology. I had the benefit of using a Linksys LRT224 with direct access to Linksys engineering to figure out DHCP-PD. However, the manual for the LRT224 doesn’t even mention DHCP-PD. Regarding maturity, IPv6 is not a new technology, but it is still new to ISPs, device manufacturers and customers. IPv6 has a lot more advantages than the few points I’ve mentioned, but it is going to take some time before those advantages are simplified enough so the majority of us can understand and use them.

My experience shows Time Warner has IPv6 working, at least in my area. Comcast also appears to be relatively far along in its deployment of IPv6. Here’s a link to Comcast’s IPv6 site and Comcast’s list of supported devices .

Discuss this in the Forums

Related posts

How to: setting up file and printer sharing between two routers.

We often hear from people who have two (or more!) routers in their LAN and are trying to get Microsoft File and Printer sharing running among all their computers. This ProblemSolver will explain why this doesn't work by default and provide some suggestions for working around the problem.

VLAN How To: Segmenting a small LAN

VLANs aren't just for large networks. Doug Reid shows you how to use a smart switch and VLANs to divide a small LAN into secure, separate segments.

How We Test Powerline Products

Updated - This article describes how we test powerline products.

Configuring a static IPv6 address on a VLAN

This option enables configuring of unique, static unicast IPv6 addresses for global and link-local applications, including:

link-local unicast (including EUI and non-EUI interface identifiers)

global unicast (and unique local unicast)

Statically configuring a link-local unicast address

[no] ipv6 address fe80:: <interface-id> link-local

If IPv6 is not already enabled on the VLAN, this command enables IPv6 and configures a static link-local address. If IPv6 is already enabled on the VLAN, this command overwrites the current, link-local address with the specified static address. (One link-local address is allowed per VLAN interface.) <interface-id> The low-order 64 bits, in 16-bit blocks, comprise this value in a link-local address: xxxx xxxx : xxxx xxxx : xxxx xxxx : xxxx xxxx

Where a static link-local address is already configured, a new, autoconfigured global unicast addresses assignment uses the same interface identifier as the link-local address.

NOTE: An existing link-local address is replaced, and is not deprecated, when a static replacement is configured. The prefix for a statically configured link-local address is always 64 bits, with all blocks after fe80 set to zero. That is: fe80:0:0:0.

After verification of uniqueness by DAD, a statically configured link-local address status is set to preferred , with a permanent lifetime.

For link-local addressing, the no form of the static IPv6 address command produces different results, depending on how IPv6 is configured on the VLAN:

If IPv6 was enabled only by a statically configured link-local address, deleting the link-local address disables IPv6 on the VLAN.

If other IPv6-enabling commands have been configured on the VLAN, deleting the statically configured link-local address causes the switch to replace it with the default (EUI-64) link-local address for the VLAN, and IPv6 remains enabled.

See also Disabling IPv6 on a VLAN .

Statically configuring a global unicast address

[no] ipv6 address [ <network-prefix> <interface-id> | <prefix-length> ]

[no] ipv6 address [ <network-prefix> ::/ <prefix-length> eui-64 If IPv6 is not already enabled on a VLAN, either of these command options do the following: enable IPv6 on the VLAN configure a link-local address using the EUI-64 format statically configure a global unicast address If IPv6 is already enabled on the VLAN, the above commands statically configure a global unicast address, but have no effect on the current link-local address. After verification of uniqueness by DAD, the lifetime of a statically configured IPv6 address assigned to a VLAN is set to permanent and is configured as a preferred address. The no form of the command erases the specified address and, if no other IPv6-enabling command is configured on the VLAN, disables IPv6 on the VLAN. <network-prefix> : This includes the global routing prefix and the subnet ID for the address. <interface-id> : Enters a user-defined interface identity. <prefix-length> : Specifies the number of bits in the network prefix. If you are using the eui-64 option, this value must be 64. eui-64 : Specifies using the Extended Unique Identifier (EUI) format to create an interface identifier based on the VLAN MAC address.

Viewing the currently configured static IPv6 addresses per-VLAN

To view the currently configured static IPv6 addresses per-VLAN, use show run commands.

show ipv6 Lists IPv6 addresses for all VLANs configured on the switch.

show ipv6 vlan <vid> Lists IPv6 addresses configured on VLAN <vid> .

For more information, see Viewing the current IPv6 addressing configuration .

Operating notes

With IPv6 enabled, the switch determines the default IPv6 router for the VLAN from the RAs it receives. (See Router access and default router selection .)

If DHCPv6 is configured on a VLAN, then configuring a static global unicast address on the VLAN removes DHCPv6 from the VLAN's configuration and deletes the DHCPv6-assigned global unicast address.

Note that for a statically configured global unicast address to be routable, a gateway router must be transmitting RAs on the VLAN.

If an autoconfigured global unicast address already exists for the same subnet as a new, statically configured global unicast address, the statically configured address is denied. In the reverse case, you can add an autoconfig command to the VLAN configuration, but it will not be implemented unless the static address is removed from the configuration.

Duplicate address detection (DAD) for statically configured addresses

Statically configured IPv6 addresses are designated as permanent. If DAD determines that a statically configured address duplicates a previously configured and reachable address on another device belonging to the VLAN, the more recent, duplicate address is designated as duplicate . For more on this topic, see:

Duplicate Address Detection (DAD) .

Viewing the current IPv6 addressing configuration

Copyright © 2015 Hewlett-Packard Development Company, L.P.

CCNA 200-301

• CCNA 200-301 Labs
• CCNP 350-401 ENCOR
• CCNP 350-401 ENCOR Labs
• CCNP 300-410 ENARSI
• CCIE Enterprise Infrastructure
• Cisco Packet Tracer Lab Course
• NRS II IRP Course
• NRS II MPLS Course
• NRS II Service Architecture
• Nokia Configuration Course
• Nokia SRC Program
• JNCIA Junos
• HCIA (HCNA)
• HCIA Configuration Course
• What is Huawei R&S Certification?
• Huawei ICT Certifications
• Python Course
• IPv6 Course
• IP Multicast Course
• NRS I Configuration Course
• Cisco Packet Tracer How To Guide
• Online Courses
• Udemy Courses
• CCNA Flashcard Questions
• Protocol Cheat Sheets
• Subnetting Cheat Sheet
• Linux Cheat Sheet
• Python Cheat Sheet
• CLI Commands Cheat Sheets
• Miscellaneous Cheat Sheets
• Cisco Packet Tracer Labs
• Cisco GNS3 Labs
• Huawei eNSP Labs
• Nokia GNS3 Labs
• Short Config Videos
• Network Tools
• IPCisco on Social Media
• Network Engineer Interview Questions
• Personality Interview Training
• Sign In/Up | Members
• Lost password
• Sign In/Sign Up
• ENROLL HERE

• IPv6 Configuration on Cisco Packet Tracer

Table of Contents

IPv6 Configuration

IPv6 is the new version of the most important Network Layer Protocol IP. With this new IP version, IPv6, beside different features, some configuration differencies are also coming. In this lesson, we will focus on these IPv6 Configuration Steps, IPv6 Configuration on Cisco devices . We will use the below Packet Tracer topology for our IPv6 Config .

You can download Packet Tracer IPv6 Lab , in Packet Tracer Labs page.

In this configuration lesson, we will follow the below IPv6 Configuration steps :

Enable IPv6 Globally

Enable ipv6 on interface, configure eui-64 format global unicast address, configure manual global unicast address, manual link local address configuration, auto ipv6 address configuration, enable dhcpv6 client, ipv6 verification commands.

  So, let’s go to the IPv6 Configuration steps and configure IPv6 for Cisco routers .

After going to the configuration mode with “ configure terminal ” command, to enable IPv6 on a Cisco router, “ ipv6 unicast-routing ” command is used. With this Cisco command, IPv6 is enabled globally on the router. This can be used before both interface configurations and IPv6 Routing Protocol configurations.

Router 1# configure terminal Router 1(config)# ipv6 unicast-routing Router 2# configure terminal Router 2(config)# ipv6 unicast-routing

After enabling IPv6 globally, we should enable IPv6 under the Interfaces. To enable IPv6 under an interface, we will use “ ipv6 enable ” command. Let’s enable IPv6 on two interfaces of each router.

Router 1 (config)# interface FastEthernet0/0 Router 1 (config-if)# ipv6 enable Router 1 (config-if)# no shutdown Router 1 (config)# interface FastEthernet0/1 Router 1 (config-if)# ipv6 enable Router 1 (config-if)# no shutdown

Router 2 (config)# interface FastEthernet0/0 Router 2 (config-if)# ipv6 enable Router 2 (config-if)# no shutdown Router 2 (config)# interface FastEthernet0/1 Router 2 (config-if)# ipv6 enable Router 2 (config-if)# no shutdown

EUI-64 format is the IPv6 format used to create IPv6 Global Unicast Addresses . It is a specific format that we have also talked about before. With this format, basically, interface id of the whole IPv6 adderess is ceated with the help of the MAC address. After that, this created interface id is appended to the network id.

To configure an interface with EUI-64 format (Extended Unique Identifier), firstly we will go under the interface, then we will use “ ip address ipv6-address/prefix-length eui-64 ” command. Here, our IPv6 address and prefix-length are 2001:AAAA:BBBB:CCCC::/64. The real EUI-64 Global Unicast Address will be created with this address and MAC address after IPv6 configuration.

Router 1 (config)# interface FastEthernet0/0 Router 1(config-if)# ipv6 address 2001:AAAA:BBBB:CCCC::/64 eui-64 Router 1(config-if)# end

Let’s check the IPv6 address that is created with EUI-64 format with “ show ipv6 interface brief ” command.

Router 1# show ipv6 interface brief FastEthernet0/0            [up/up] FE80::2E0:B0FF:FE0E:7701 2001:AAAA:BBBB:CCCC:2E0:B0FF:FE0E:7701 FastEthernet0/1            [up/up] FE80::2E0:B0FF:FE0E:7702 Vlan1                      [administratively down/down] unassigned

If we do not use EUI-64 format address, we have to write the whole IPv6 Address to the configuration line. Let’s configure Gigabit Ethernet 0/0 interface of Router 2 manually .

Router 2 (config)# interface FastEthernet0/0 Router 2 (config-if)# ipv6 address 2001:AAAA:BBBB:CCCC:1234:1234:1234:1234/64 Router 2(config-if)# end

Here, both of these directly connected interfaces are in the same subnet, the Network ID is same (2001:AAAA:BBBB:CCCC::/64).

Let’s check the IPv6 address that we have manually assigned with “ show ipv6 interface brief ” command.

Router 2# show ipv6 interface brief FastEthernet0/0            [up/up] FE80::206:2AFF:FE15:BD01     2001:AAAA:BBBB:CCCC:1234:1234:1234:1234 FastEthernet0/1            [administratively up/up] FE80::206:2AFF:FE15:BD02 Vlan1                      [administratively down/down] unassigned

To check the connectivity between two node, we use ping. As IPv4, with IPv6, we also use ping, but this time it is called IPv6 Ping . The format of IPv6 Ping is a little difference than IPv4 Ping. These  differences are the format of the used IP address and the used keywords. With IPv6 Ping , “ ping ipv6 ” keywords are used before the destination IPv6 address.

Here, we will ping from Router 1 GigabitEthernet0/0 interface to Router 2 GigabitEthernet0/0 interface.

Router 1# ping ipv6 2001:AAAA:BBBB:CCCC:1234:1234:1234:1234   Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:AAAA:BBBB:CCCC:1234:1234:1234:1234, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/1 ms

To check the configured IPv6 Address, we can use “ show ipv6 interface interface-name ” command.

Router 1# show ipv6 interface FastEthernet0/0 FastEthernet0/0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::2E0:B0FF:FE0E:7701 No Virtual link-local address(es): Global unicast address(es): 2001:AAAA:BBBB:CCCC:2E0:B0FF:FE0E:7701 , subnet is 2001:AAAA:BBBB:CCCC::/64 [EUI] Joined group address(es): FF02::1 FF02::2 FF02::1:FF0E:7701 MTU is 1500 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is enabled, number of DAD attempts: 1 ND reachable time is 30000 milliseconds ND advertised reachable time is 0 (unspecified) ND advertised retransmit interval is 0 (unspecified) ND router advertisements are sent every 200 seconds ND router advertisements live for 1800 seconds ND advertised default router preference is Medium Hosts use stateless autoconfig for addresses.

Router 2# show ipv6 interface FastEthernet0/0 FastEthernet0/0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::206:2AFF:FE15:BD01 No Virtual link-local address(es): Global unicast address(es):     2001:AAAA:BBBB:CCCC:1234:1234:1234:1234 , subnet is 2001:AAAA:BBBB:CCCC::/64 Joined group address(es): FF02::1 FF02::2 FF02::1:FF15:BD01 FF02::1:FF34:1234 MTU is 1500 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is enabled, number of DAD attempts: 1 ND reachable time is 30000 milliseconds ND advertised reachable time is 0 (unspecified) ND advertised retransmit interval is 0 (unspecified) ND router advertisements are sent every 200 seconds ND router advertisements live for 1800 seconds ND advertised default router preference is Medium Hosts use stateless autoconfig for addresses.

Here, with ipv6 ping, there are some options that we can use. These are given below:

ping ipv6 [hostname | ip_address] [repeat repeat-count | size datagram-size | source [ interface-name | source-address ]

• repeat : Ping packet count. The default ping repeat value is 5.
• size : Datagram size. The default value ping size is 56 bytes.
• source : Source Address of the ping. Default value is None.

So if we would like to send 10 IPv6 ping packet with 200 byte datagrams from 2001:AAAA:BBBB:CCCC:1234:1234:1234:1234 to 2001:AAAA:BBBB:CCCC:1111:2222:3333:4444, we will use the below command:

Router 2 # ping ipv6 2001:AAAA:BBBB:CCCC:1111:2222:3333:4444 repeat 10 size 200 source 2001:AAAA:BBBB:CCCC:1234:1234:1234:1234

To configure a Link Locak address manually, we use “ ipv6 address link-local ipv6-address ” command. Here, we should write an IPv6 address in the range of Link Local addresses. If you would like to learn more about a Link Local Address, you can check Link Local Address lesson.

Let’s configure GigabitEthernet0/1 interface of Router 1 with Link Local Address FE80::AAAA:BBBB:CCCC:DDDD. Here, there is no need to write a prefix length but we will add link-local keyword at the end of the command.

Router 1 (config)# interface FastEthernet0/1 Router 1 (config-if)# ipv6 address FE80::AAAA:BBBB:CCCC:DDDD link-local Router 1 (config-if)# end

Let’s check the manually configure ipv6 Link-Local address with “ show ipv6 interface brief ” command.

Router 1# show ipv6 interface brief FastEthernet0/0            [up/up] FE80::2E0:B0FF:FE0E:7701 2001:AAAA:BBBB:CCCC:2E0:B0FF:FE0E:7701 FastEthernet0/1            [administratively down/down]     FE80::AAAA:BBBB:CCCC:DDDD Vlan1                      [administratively down/down] unassigned

IPv6 Addresses can be configured automatically. This is one of the most important characteristics coming with IPv6. For IPv6 Auto configuration , we will use “ ipv6 address autoconfig ” command. Let’s use it on Router 2 on GigabitEthernet0/1.

Router 2 (config)# interface FastEthernet0/1 Router 2 (config-if)# ipv6 address autoconfig Router 2 (config-if)# end

This type of IPv6 address configuration is Sateless Auto Configuration .

Let’s check the Autoconfigured Link-Local ipv6 address with “ show ipv6 interface brief ” command.

Router 2# show ipv6 interface brief FastEthernet0/0            [up/up] FE80::206:2AFF:FE15:BD01 2001:AAAA:BBBB:CCCC:1234:1234:1234:1234 FastEthernet0/1            [up/down]     FE80::206:2AFF:FE15:BD02 Vlan1                      [administratively down/down] unassigned

Let’s ping from Router 2 to Router 1 to test this second interfaces’ ipv6 connection.

Router 2# ping ipv6 FE80::AAAA:BBBB:CCCC:DDDD Output Interface: FastEthernet0/1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to FE80::AAAA:BBBB:CCCC:DDDD, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/1 ms

To enable DHCPv6 Client function on an interface, we use “ ipv6 address dhcp ” command under this interface. With this command, interface gets its IPv6 address form the DHCPv6 server . Let’s enable DHCPv6 on GigabitEthernet0/2 of Router 2.

Router 1 (config)# interface FastEthernet0/1 Router 1 (config-if)# ipv6 address dhcp Router 1 (config)# end

To verify DHCPv6 enabled interfaces, we can use “ show ipv6 dhcp interface ” command.

Router 1 # show ipv6 dhcp interface

To verify IPv6 Configuration, we can use different show commands. These IPv6 show commands are given below

• To check IPv6 interface configuration and status we use “ show ipv6 interface interface-id ”.

Router 1# show ipv6 interface FastEthernet0/0 FastEthernet0/0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::2E0:B0FF:FE0E:7701 No Virtual link-local address(es): Global unicast address(es): 2001:AAAA:BBBB:CCCC:2E0:B0FF:FE0E:7701, subnet is 2001:AAAA:BBBB:CCCC::/64 [EUI] Joined group address(es): FF02::1 FF02::2 FF02::1:FF0E:7701 MTU is 1500 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is enabled, number of DAD attempts: 1 ND reachable time is 30000 milliseconds ND advertised reachable time is 0 (unspecified) ND advertised retransmit interval is 0 (unspecified) ND router advertisements are sent every 200 seconds ND router advertisements live for 1800 seconds ND advertised default router preference is Medium Hosts use stateless autoconfig for addresses.

• To check IPv6 neighbor cache entries we use “ show ipv6 neighbors ”.

Router 1# show ipv6 neighbors IPv6 Address                              Age Link-layer Addr State Interface 2001:AAAA:BBBB:CCCC:1234:1234:1234:1234    23 0006.2A15.BD01  REACH Fa0/0 FE80::206:2AFF:FE15:BD02                    7 0006.2A15.BD02  REACH Fa0/1

• To check IPv6 Routing Table we use “ show ipv6 route ”.

Router 1# show ipv6 route   IPv6 Routing Table – 3 entries Codes: C – Connected, L – Local, S – Static, R – RIP, B – BGP U – Per-user Static route, M – MIPv6 I1 – ISIS L1, I2 – ISIS L2, IA – ISIS interarea, IS – ISIS summary O – OSPF intra, OI – OSPF inter, OE1 – OSPF ext 1, OE2 – OSPF ext 2 ON1 – OSPF NSSA ext 1, ON2 – OSPF NSSA ext 2 D – EIGRP, EX – EIGRP external C   2001:AAAA:BBBB:CCCC::/64 [0/0] via ::, FastEthernet0/0 L   2001:AAAA:BBBB:CCCC:2E0:B0FF:FE0E:7701/128 [0/0] via ::, FastEthernet0/0 L   FF00::/8 [0/0] via ::, Null0

• To check IPv6 DHCP we use “ show ipv6 dhcp ”.

Router 1# show ipv6 dhcp This device’s DHCPv6 unique identifier (DUID): 0003000100E0B00E7701

• To check IPv6 Protocols we use “ show ipv6 protocols ”.

Router 1# show ipv6 protocols IPv6 Routing Protocol is “connected” IPv6 Routing Protocol is “static

Questions For IPv6 Configuration

Question 1: with which command do we enable ipv6 globally for ipv6 configuration.

a) ipv6 enable

b) ipv6 unicast-routing

c) ipv6 no shutdown

d) ipv6 run

Question 2: Which command enables IPv6 under an interface?

Question 3: which command enables auto ipv6 addressing under an interface .

a) ipv6 auto

d) ipv6 address autoconfig

e) ipv6 run

Question 4: Which command enables DHCPv6 under an interface?

a) ipv6 auto dhcp

b) ipv6 address dhcp

c) ipv6 address autoconfig

d) ipv6 dhcp run

e) ipv6 dhcp on

Question 5: How to send 20 ping packet to 001:AAAA:BBBB:CCCC:1111:2222:3333:4444 address?

a) ping ipv6 2001:AAAA:BBBB:CCCC:1111:2222:3333:4444 source 20

b) ping ipv6 2001:AAAA:BBBB:CCCC:1111:2222:3333:4444 size 20

c) ping ipv6 2001:AAAA:BBBB:CCCC:1111:2222:3333:4444 repeat 20

Answers: 1) b     2) a    3) d    4) b    5) c   

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Network Fundamentals

• Collision Domain vs Broadcast Domain
• Types of Networks
• Top Internet Access Technologies
• WAN Topology Types
• Network Topology Architectures
• Power Over Ethernet (PoE)
• Ethernet Collisions and Troubleshooting
• Cisco NGFW and Cisco NGIPS
• Networking Connectors
• Ping Command
• Basic Cisco Router Configuration on Packet Tracer
• ICMP (Internet Control Message Protocol)
• Address Resolution Protocol (ARP)
• Network Cabling
• Network Devices
• TCP/IP Model
• OSI Referance Model

IPv4 Addressing

• Verify IP Parameters for Client OS
• Cisco IP Address Configuration
• APIPA Address
• Private IP Address Ranges
• Subnetting Examples
• IP Addressing (IPv4)
• IP Subnetting and Subnetting Examples

TCP and UDP

• TCP Header : Sequence & Acknowledgement Number
• TCP Handshake
• TCP versus UDP
• UDP (User Datagram Protocol)
• TCP (Transmission Control Protocol)
• TCP Header : TCP Options
• TCP Header : TCP Window Size, Checksum &amp; Urgent Pointer
• TCP Header : TCP Flags
• Voice VLAN Configuration
• Packet Tracer VLAN Example 2
• How to Configure Cisco VLANs
• VTP Configuration with Packet Tracer
• VTP (VLAN Trunking Protocol)
• DTP and VLAN Frame Tagging protocols ISL, dot1.q
• Cisco Packet Tracer VLAN Configuration Example
• VLAN Port Assignment and VLAN Port Types
• VLANs (Virtual Local Area Networks)

Switching and LANs

• Ethernet Basics
• MAC Address Lookup
• What is a mac address
• Local Area Networks
• Network Topologies
• Hubs, Switches and Routers

Spanning Tree Protocol

• Loop Guard, Uplink Fast, Backbone Fast and UDLD
• Portfast, Root Guard, BPDU Filter and BPDU Guard
• PVST+ and Rapid PVST+
• STP (Spanning Tree Protocol) Example on Packet Tracer
• RSTP Configuration on Packet Tracer
• STP Portfast Configuration with Packet Tracer
• Spanning Tree Protocol Operation
• Rapid Spanning Tree Protocol (RSTP)
• Spanning Tree Protocol (STP)

Neighbor Discovery

• LLDP Configuration on Cisco IOS
• Neighbour Discovery Protocols
• CDP Configuration with Packet Tracer

EtherChannels

• PAgP Configuration on Cisco Devices
• LACP Configuration on Cisco Devices
• Link Aggregation Control Protocol (LACP)

Routing Fundamentals

• Route Summarization
• Routing Path Determination
• Routing Table
• Static Routes
• IPv4 Floating Static Routes
• Inter VLAN Routing Configuration on Packet Tracer
• Switch Virtual Interface Configuration on Packet Tracer
• Switch Virtual Interfaces
• Inter VLAN Routing with Router on Stick
• IP and Layer 3 Overview
• Static Route Configuration on Cisco Routers
• Dynamic Routing Protocols
• OSPF Cost and SPF Algorithm
• OSPFv3 Configuration Example on Cisco IOS
• OSPFv3 (Open Shortest Path First Version 3)
• Cisco Single Area OSPF Configuration
• Other OSPF Key Points
• OSPF Network Types
• OSPF Area Types
• OSPF LSA Types
• OSPF Packet Types
• OSPF Adjacency
• OSPF(Open Shortest Path First) Overview

WAN (Wide Area Networks)

• MLPPP Configuration on Cisco Packet Tracer
• What is MLPPP?
• Metro Ethernet Technology
• WAN and WAN Technologies

DHCP and DNS

• DNS Configuration on Cisco Routers
• Domain Name System Overview
• Router DHCP Configuration with Packet Tracer
• DHCP IP Allocation Operation
• DHCP (Dynamic Host Configuration Protocol)
• NAT (Network Address Translation)
• PAT Configuration with Packet Tracer
• Dynamic NAT Configuration with Packet Tracer
• Static NAT Configuration with Packet Tracer

First Hop Redundancy

• HSRP Configuration on Cisco IOS
• HSRP (Hot Standby Router Protocol)
• First Hop Redundancy Protocols (FHRPs)

Network Management

• Syslog Overview
• Configuration Register
• TFTP, FTP, SFTP and SCP
• SSH Configuration on Packet Tracer
• Syslog Configuration Cisco
• Cisco NTP Configuration
• NTP (Network Time Protocol)
• SNMP Overview
• SNMP Configuration On Cisco IOS
• Cisco Router Password Recovery
• IPv6 Floating Static Routes
• IPv6 Static and Default Route Configuration
• Stateless Address Auto Configuration
• IPv6 NDP (Neighbour Discovery Protocol)
• What does IPv6 bring?
• Subnetting in IPv6
• IPv6 Address Types
• IPv4 and IPv6 Headers
• IPv6 and IPv6 Addresses

Quality of Service

• Network Traffic Types
• Policing and Shaping in QoS
• Classification and Marking in QoS
• Quality of Service Overview
• Radius Configuration for Wireless Users
• Cisco RADIUS Server Configuration on Packet Tracer
• TACACS+ Overview
• RADIUS Overview
• AAA Protocols : RADIUS and TACACS+
• Authentication, Authorization, Accounting (AAA)
• WLAN Frequency Bands
• Other Wireless Network Extention Types
• Wireless Principles
• WLAN Components
• Wireless Network Design Models
• WLC Management Access Connections
• Wireless Access Point Modes
• Wireless Security Protocols
• WLAN Configuration on Packet Tracer

Security Fundamentals

• DHCP Snooping Configuration on Packet Tracer
• Cisco Banner Configuration on Packet Tracer
• What is DHCP Snooping?
• Access Control Lists
• Multifactor Authentication (MFA)
• Dynamic ARP Inspection
• Cyber Attacks, Network Attacks, Threats and Mitigation
• 802.1x (Port Based Network Access Control)
• Switch Port Security Configuration on Cisco Packet Tracer
• Switch Port Security
• Extended Access List Configuration With Packet Tracer
• Standard Access List Configuration With Packet Tracer
• Basic Cisco Router Security Configuration

Automation and Programmability

• Ansible vs Puppet vs Chef
• Chef Overview
• Puppet Overview
• Ansible Overview
• Network Automation Tools
• Interpret JSON Encoded Data
• Cisco DNA Center
• Cisco SD-Access
• Data Serialization Languages: JSON, YAML, XML
• Traditional Network Management versus Cisco DNA Center
• Cisco DNA and Intent-Based Networking (IBN)
• How Network Automation Impacts Network Management

SDN (Software Defined Networking)

• What is SDN ?
• Traditional Network Drawbacks Versus SDN
• What Will SDN Bring?
• SDN Architecture Components
• SDN Terminology
• Virtualization
• Virtual Network Structure

Latest Lessons

• IPv6 Floating Static Routing Part of: CCNP Enterprise 350-401 ENCOR
• IPv6 Link Local Addresses Part of: CCNP Enterprise 350-401 ENCOR
• IPv6 Neighbour Discovery Protocol Part of: CCNP Enterprise 350-401 ENCOR
• IPv6 Configuration Example on Packet Tracer Part of: CCNP Enterprise 350-401 ENCOR
• Private IPv4 Address Ranges Part of: CCNP Enterprise 350-401 ENCOR
• APIPA Addresses Part of: CCNP Enterprise 350-401 ENCOR
• Cisco TrustSec Part of: CCNP Enterprise 350-401 ENCOR
• Wireless Mobility: Roaming Explained Part of: CCNP Enterprise 350-401 ENCOR
• uRPF (Unicast Reverse Path Forwarding) Part of: CCNP Enterprise 350-401 ENCOR
• Conditional debugging Part of: CCNP Enterprise 350-401 ENCOR
• More Lessons

Latest Blog Posts

WHAT YOU WILL FIND?

• 250.000+ Students All Over The World
• 8.000+ Questions & Answers
• 100+ Lab Files & Cheat Sheets
• 30+ IT/Network Courses
• A Real Desire To Help You
• Daily Social Media Shares
• %100 Satisfaction
• CISCO Courses
• NOKIA Courses
• HUAWEI Courses
• JUNIPER Courses
• PYTHON Course
• KEY Courses
• VIDEO Courses
• UDEMY Courses
• Cheat Sheets
• Configuration Files
• Interview Questions
• IPCisco On Social Media
• Pärnu mnt. 139c – 14, 11317, Tallinn, Estonia
• [email protected]

Thank you for taking the time to respond. The NETGEAR documentation team uses your feedback to improve our knowledge base content.

Rating Submitted

Do you have a suggestion for improving this article?

Characters Left : 500

MyNETGEAR® Account

Welcome back

Access your NETGEAR

NETGEAR Support

How do I create an IPv6 VLAN routing interface using the web interface on my managed switch?

Was this article helpful?    Yes      No

• In the VLAN ID field, enter 500 .
• In the VLAN Type field, select Static .
• Click Add .  

• In the VLAN ID list, select 500 .
• Click Unit 1 . The ports display.
• Click the gray box under port 1 until U displays, indicating that the egress packet is untagged for the port.
• Click Apply .  

• Under PVID Configuration, scroll down and select the Interface 1/0/1 check box.
• In the PVID (1 to 4093) field, enter 500 .
• Click Apply to save the settings.  

• For IPv6 Unicast Routing, select the Enable radio button.
• For IPv6 Forwarding, select the Enable radio button.

• Click VLANS. The logical VLAN interface 0/4/2 displays.
• Select the 0/4/2 check box.
• Under IPv6 Interface Configuration, in the IPv6 Mode field, select Enable .
• Click Apply.  

• In the Interface field, select 0/4/2 .
• In the IPv6 Prefix field, enter 2000::1 .
• In the Length field, enter 64 .
• In the EUI64 field, select Disable .
• Click Add .

For more information see the How do I create an IPv6 routing VLAN using CLI commands on my managed switch?  support article.

This article applies to the following managed switches and their respective firmware:

• M5300 - firmware version 10.0.0.x
• M5300-28G (GSM7228S)
• M5300-5G (GSM7252S)
• M5300-28G3 (GSM7328Sv2h2)
• M5300-52G3 (GSM7352Sv2h2)
• M5300-28G_POE+ (GSM7228PSv1h2)
• M5300-52G-POE+ (GSM7252PSv1h2)
• M5300-28GF3 (GSM7328FSv2)
• XSM7224S - firmware version 9.0.1.x (license required to support the feature described in this article)

Last Updated:04/04/2023 | Article ID: 21971

Was this article helpful?

This article applies to:.

• M4200-10MG-PoE+ (GSM4210P)
• M4250-10G2F-PoE+ (GSM4212P)
• M4250-10G2XF-PoE+ (GSM4212PX)
• M4250-10G2XF-PoE++ (GSM4212UX)
• M4250-12M2XF (MSM4214X)
• M4250-16XF (XSM4216F)
• M4250-26G4F-PoE+ (GSM4230P)
• M4250-26G4F-PoE++ (GSM4230UP)
• M4250-26G4XF-PoE+ (GSM4230PX)
• M4250-40G8F-PoE+ (GSM4248P)
• M4250-40G8XF-PoE+ (GSM4248PX)
• M4250-40G8XF-PoE++ (GSM4248UX)
• M4250-8G2XF-PoE+ (GSM4210PX)
• M4250-9G1F-PoE+ (GSM4210PD)
• M4300-12X12F (XSM4324S)
• M4300-16X (XSM4316PA)
• M4300-16X (XSM4316PB)
• M4300-24X (XSM4324CS)
• M4300-24X24F (XSM4348S)
• M4300-24XF (XSM4324FS)
• M4300-28G (GSM4328S)
• M4300-28G-PoE+ (GSM4328PA)
• M4300-28G-PoE+ (GSM4328PB)
• M4300-48X (XSM4348CS)
• M4300-48XF (XSM4348FS)
• M4300-52G (GSM4352S)
• M4300-52G-PoE+ (GSM4352PA)
• M4300-52G-PoE+ (GSM4352PB)
• M4300-8X8F (XSM4316S)
• M5300-28G-POE+ (GSM7228PSv1h2)
• M5300-52G (GSM7252S)
• M7300-24XF (XSM7224S)

Looking for more about your product?

Get information, documentation, videos and more for your specific product.

Can’t find what you’re looking for?

Quick and easy solutions are available for you in the NETGEAR community.

Need to Contact NETGEAR Support?

With NETGEAR’s round-the-clock premium support, help is just a phone call away.

Complimentary Support

NETGEAR provides complimentary technical support for NETGEAR products for 90 days from the original date of purchase.

NETGEAR Premium Support

Gearhead support for home users.

GearHead Support is a technical support service for NETGEAR devices and all other connected devices in your home. Advanced remote support tools are used to fix issues on any of your devices. The service includes support for the following:

• Desktop and Notebook PCs, Wired and Wireless Routers, Modems, Printers, Scanners, Fax Machines, USB devices and Sound Cards
• Windows Operating Systems (2000, XP or Vista), MS Word, Excel, PowerPoint, Outlook and Adobe Acrobat
• Anti-virus and Anti-Spyware: McAfee, Norton, AVG, eTrust and BitDefender

ProSUPPORT Services for Business Users

NETGEAR ProSUPPORT services are available to supplement your technical support and warranty entitlements. NETGEAR offers a variety of ProSUPPORT services that allow you to access NETGEAR's expertise in a way that best meets your needs:

• Product Installation
• Professional Wireless Site Survey
• Defective Drive Retention (DDR) Service

Where to Find Your Model Number

To find the model/version number, check the bottom or back panel of your NETGEAR device.

Select a product or category below for specific instructions.

Nighthawk Routers

Powerline and Wall Plug Extenders

Cable and DSL Modem Routers

ReadyNAS Network Storage

Wireless Access Points

Other Business Products

Mobile Broadband

• Create Post
• Create Chapter Note
• Create Note for Selection
• View All Notes
• Show All Notes on Page
• Hide All Notes on Page
• Print with Notes
• Share on Facebook
• Share on Twitter
• Email a Link
• Copy Link to Clipboard
• Cisco 1000 Series Integrated Services Routers

Published On: February 7ᵗʰ, 2020 09:33

Cisco 1000 Series Software Configuration Guide, Cisco IOS XE Gibraltar 16.12.x

Ipv6 support on switch virtual interface.

This document provides an overview of the switch virtual interface (SVI) for Cisco1000 Series and Cisco 4000 Series Integrated Services Routers.

Information About IPv6 Support on Switch Virtual Interface

Cisco IOS Software Features Supported by Switch Virtual Interface

The table lists the Cisco IOS Software features supported by SVI and summarized the typical use of these features. Please refer to the Feature Navigator Tool to check whether a specific platform supports a specific feature.

Additional Information for IPv6 Support on Switch Virtual Interface

SVI on Cisco Integrated Services Routers is designed to provide basic Layer 3 functions for the Layer 2 switch ports that belong to a specific VLAN. The SVI does not provide the same feature set and functions as the integrated Layer 3 Ethernet ports of the integrated services routers and should not be used to entirely replace the Layer 3 Ethernet ports. Customer who need additional Layer 3 Ethernet ports for their Integrated Services Routers may consider the use of 1- and 2-Port Fast Ethernet High-Speed WIC for modular ISR platforms. The guidelines presented in this document summarize feature support considerations for an Integrated Services Router deployment that uses SVIs.

For more information, please refer to the following links:

• Cisco 4-Port and 8-Port Gigabit Ethernet Switch NIM

• Cisco IOS Security Configuration Guide: http://www.cisco.com/en/US/partner/products/ps6441/products_configuration_guide_book09186a008049e249.html

• Cisco IOS Quality-of-Service Solutions Configuration Guide: http://www.cisco.com/en/US/partner/products/ps6441/products_configuration_guide_book09186a008065c7a1.html

Configuration Examples for IPv6 Support on Switch Virtual Interface

Easy VPN Remote and NAT

Example: dhcp, example: qos marking, example: pbr, custom book.

Welcome to the custom book wizard. Using this tool you can create books containing a custom selection of content. To get started, enter a name for the book or select an existing book to add to.

Select the topics and posts that you would like to add to your book.

Preview your selected content before you download or save to your dashboard.

PDF View with Adobe Reader on a variety of devices.

ePub View in various apps on iPhone, iPad, Android, Sony Reader or Windows devices.

Mobi View on Kindle device or Kindle app on multiple devices.

Save to Dashboard

Save the custom book to your dashboard for future downloads.

Your contact details will be kept confidential and will not be shared outside Cisco. If we need additional information regarding your feedback, we will contact you at this email address.

Select Folder

Content library - -.

Click on the file types below to dowload the content in that format.

•   This Document
•   Entire Library

Document Information

Using This Documentation

Product Notes

Related Documentation

Acronyms and Abbreviations

CLI Command Modes

Support and Accessibility

Protocol Description

Introduction

Basic SEFOS IPv6 Topology

Route Redistribution Topology in IPv6

General Configurations

Default Settings

Completing Preliminary Configurations

Create an Interface

Configure an IPv4 Address for an Interface

Configuring the Basic IPv6 Topology

Configure Switch 1

Configure Switch 2

Configuring the Route Redistribution Topology

Configure Switch 3

IPv6 Feature Configuration

Configuring IPv6 Support in an Interface

Enable IPv6 Support

Disable IPv6 Support

Configuring IPv6 Addressing

Add IPv6 Addresses to an Interface

Remove IPv6 Addresses From an Interface

Configuring IPv6 Routing

Enable IPv6 Routing

Disable IPv6 Routing

Configuring IPv6 Static Routes

Add a Static Route

Remove a Static Route

Configuring Static Neighbor Cache Entries

Add a Neighbor Cache Entry

Delete a Neighbor Cache Entry

Checking a Local or Remote Endpoint

Check an Endpoint Using Default Values

Check an Endpoint Using the Link-Local Address

Configuring Router Advertisement Parameters

Configure Router Advertisement Parameters

Configuring DAD Entries

Set the DAD Attempts

Reset the DAD Attempts

Configuring PMTU Discovery

Enable PMTU Discovery

Disable PMTU Discovery

Setting the MTU for Use in PMTU Discovery

Set the MTU for Use in PMTU Discovery

Configuring the IPv6 Route Redistribution Policy for Routing Protocols

Configure the IPv6 Route Redistribution Policy for Routing Protocols

• Enter Interface Configuration mode for VLAN 1 , and enable IPv6. SEFOS# configure terminal SEFOS(config)# interface vlan 1 SEFOS(config-if)# ipv6 enable

The default prefix type is set as unicast. You can configure the prefix type as anycast, eui64, or link-local address by defining the prefix type in the command.

• Configure the IPv6 link-local address for the interface. SEFOS(config-if)# ipv6 address fe80::203:2ff:fe03:501 link-local SEFOS(config-if)# end
• Review the IPv6 information for the VLAN 1 interface. SEFOS# show ipv6 interface vlan 1   vlan1 is up, line protocol is up IPv6 is Enabled Link local address: fe80::203:2ff:fe03:501 Global unicast address(es): fec0::1111:0:1/96 ...

You are using an outdated browser. Please upgrade your browser to improve your experience.

You might have to change the supported traffic type for a VMkernel adapter, or the way IPv4 or IPv6 addresses are obtained.

• In the vSphere Client , navigate to the host.
• On the Configure tab, expand Networking and select VMkernel adapters .
• Select the VMkernel adapter that resides on the target distributed or standard switch and click Edit .

• Skip to content
• Skip to search
• Skip to footer

Configuring the Switch IP Address and Default Gateway

Available languages, download options.

• PDF (263.8 KB) View with Adobe Reader on a variety of devices

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Table Of Contents Configuring the Switch IP Address and Default Gateway Understanding How the Switch Management Interfaces Work Understanding How Automatic IP Configuration Works Automatic IP Configuration Overview Understanding DHCP Understanding RARP Preparing to Configure the IP Address and Default Gateway Default IP Address and Default Gateway Configuration Setting the In-Band (sc0) Interface IP Address Setting the Management Ethernet (me1) Interface IP Address Configuring Default Gateways Configuring the SLIP (sl0) Interface on the Console Port Using DHCP or RARP to Obtain an IP Address Configuration Renewing and Releasing a DHCP-Assigned IP Address Configuring the Switch IP Address and Default Gateway This chapter describes how to configure the IP address, subnet mask, and default gateway on the Catalyst enterprise LAN switches. Note For complete syntax and usage information for the commands used in this chapter, refer to the Catalyst 4500 Series, Catalyst 2948G, Catalyst 2948G-GE-TX, and Catalyst 2980G Switches Command Reference . This chapter consists of these sections: • Understanding How the Switch Management Interfaces Work • Understanding How Automatic IP Configuration Works • Preparing to Configure the IP Address and Default Gateway • Default IP Address and Default Gateway Configuration • Setting the In-Band (sc0) Interface IP Address • Setting the Management Ethernet (me1) Interface IP Address • Configuring Default Gateways • Configuring the SLIP (sl0) Interface on the Console Port • Using DHCP or RARP to Obtain an IP Address Configuration • Renewing and Releasing a DHCP-Assigned IP Address Understanding How the Switch Management Interfaces Work The Catalyst 4500 series, the Catalyst 2948G, Catalyst 2948G-GE-TX, and the Catalyst 2980G switches have three management interfaces: • In-band interface (sc0) • SLIP interface (s10) • Management Ethernet interface (me1) The in-band (sc0) management interface is connected to the switching fabric and participates in all of the functions of a normal switch port, such as spanning tree, Cisco Discovery Protocol (CDP), and VLAN membership. The out-of-band management interfaces (me1 and sl0) are not connected to the switching fabric and do not participate in any of these functions. When you configure the IP address, subnet mask, and broadcast address (and when you configure VLAN membership on the sc0 interface) of the sc0 or me1 interface, you can access the switch through Telnet or SNMP. When you configure the SLIP (sl0) interface, you can open a point-to-point connection to the switch through the console port from a workstation. All IP traffic that is generated by the switch (for example, a Telnet session that is opened from the switch to a host) is forwarded according to the entries in the switch IP routing table. For intersubnetwork communication to occur, you must configure at least one default gateway for the sc0 or me1 interface. The switch IP routing table is used to forward traffic originating on the switch only, not for forwarding traffic sent by devices that are connected to the switch. Because sc0 and me1 are two distinct interfaces, they potentially can have duplicate IP addresses or overlapping subnets. Therefore, when you enter a command that causes sc0 and me1 to have the same IP address or occupy the same subnet, the switch software brings one of the interfaces down. In most cases, the switch software brings down the sc0 interface after you confirm the change. However, when the switch boots with the IP address 0.0.0.0 configured on both the sc0 and me1 interfaces, the me1 interface is brought down to allow BOOTP and RARP requests to broadcast out the sc0 interface. Note When the switch boots with the IP address 0.0.0.0 configured on both the sc0 and me1 interfaces, the me1 interface is automatically brought down by the switch software. You are not asked to confirm the change, and no console messages or traps are generated in this case. Duplicate IP addresses and equal subnets are allowed on the sc0 and me1 interfaces if one of the interfaces is configured down. Non-equal subnets are not allowed (for example, sc0 with IP address 10.1.1.1 and subnet mask 255.0.0.0 and me1 with IP address 10.1.1.2 and subnet mask 255.255.255.0). Understanding How Automatic IP Configuration Works These sections describe how the switch can obtain its IP configuration automatically: • Automatic IP Configuration Overview • Understanding DHCP • Understanding RARP Automatic IP Configuration Overview The switch can obtain its IP configuration automatically using one of the following protocols: • Dynamic Host Configuration Protocol (DHCP) • Reverse Address Resolution Protocol (RARP) The switch makes DHCP and RARP requests only if the sc0 interface IP address is set to 0.0.0.0 when the switch boots up. This address is the default for a new switch or a switch whose configuration file has been cleared using the clear config all command. DHCP and RARP requests are only broadcast out the sc0 interface. Note If the CONFIG_FILE environment variable is set, all configuration files are processed before the switch determines whether to broadcast DHCP and RARP requests. For more information about the CONFIG_FILE environment variable, see Chapter 32, "Modifying the Switch Boot Configuration." If both the sc0 and me1 interfaces are unconfigured (IP address 0.0.0.0), the me1 interface is brought down to allow the switch to broadcast requests on the sc0 interface. If the me1 interface is configured and the sc0 interface is not, requests are not sent. Similarly, if the sc0 interface is not configured but the interface is configured down, requests are not sent. Understanding DHCP In software release 5.2 and later releases, the switch can obtain an IP address and other IP configuration information using DHCP. There are three methods for obtaining an IP address from the DHCP server: • Manual allocation—The network administrator maps the switch MAC address to an IP address at the DHCP server. • Automatic allocation—The switch obtains an IP address when it first contacts the DHCP server. The address is permanently assigned to the switch. • Dynamic allocation—The switch obtains a "leased" IP address for a specified period of time. The IP address is revoked at the end of this period, and the switch surrenders the address. The switch must request another IP address. In addition to the sc0 interface IP address, the switch can obtain the subnet mask, broadcast address, default gateway address, and other information. DHCP-learned values are not used if user-configured values are present. The switch broadcasts a DHCPDISCOVER message 1 to 10 seconds after all of the switch ports are online. The switch always requests an infinite lease time in the DHCPDISCOVER message. If a DHCP or Bootstrap Protocol (BOOTP) server responds to the request, the switch takes appropriate action. If a DHCPOFFER message is received from a DCHP server, the switch processes all the supported options that are contained in the message. Table 3-1 shows the supported DHCP options. Other options that are specified in the DHCPOFFER message are ignored. Table 3-1 Supported DHCP Options  Code Option 1 Subnet mask 2 Time offset 3 Router 6 Domain name server 12 Host name 15 Domain name 28 Broadcast address 33 Static route 42 NTP servers 51 IP address lease time 52 Option overload 61 Client-identifier 66 TFTP server name If a BOOTP response is received from a BOOTP server, the switch sets the in-band (sc0) interface IP address to the address that is specified in the BOOTP response. If no DHCPOFFER message or BOOTP response is received in reply, the switch rebroadcasts the request using an exponential backoff algorithm (the amount of time between requests increases exponentially). If no response is received after 10 minutes, the sc0 interface IP address remains set to 0.0.0.0 (provided that RARP requests fail as well). If you reset or power cycle a switch with a DHCP- or BOOTP-obtained IP address, the information learned from DHCP or BOOTP is retained. At boot up, the switch attempts to renew the lease on the IP address. If no reply is received, the switch retains the current IP address. Understanding RARP With RARP, you map the switch MAC address to an IP address on the RARP server. The switch retrieves its IP address from the server automatically when it boots up. The switch broadcasts ten RARP requests after all of the switch ports are online. If a response is received, the switch sets the in-band (sc0) interface IP address to the address that is specified in the RARP response. If no reply is received, the sc0 interface IP address remains set to 0.0.0.0 (provided that DHCP requests fail as well). If you reset or power cycle a switch with a RARP-obtained IP address, the information that is learned from RARP is retained. Preparing to Configure the IP Address and Default Gateway Before you configure the switch IP address and default gateway, obtain the following information, as appropriate: • IP address for the switch (sc0 and me1 interfaces only) • Subnet mask/number of subnet bits (sc0 and me1 interfaces only) • (Optional) Broadcast address (sc0 and me1 interfaces only) • VLAN membership (sc0 interface only) • SLIP and SLIP destination addresses (sl0 interface only) • Interface connection type: – In-band (sc0) interface Configure this interface when assigning an IP address, subnet mask, and VLAN to the in-band management interface on the switch. – Out-of-band management Ethernet (me1) interface Configure this interface when assigning an IP address and subnet mask to the out-of-band management Ethernet interface on the switch. – SLIP (sl0) interface Configure this interface when setting up a point-to-point SLIP connection between a terminal and the switch. Default IP Address and Default Gateway Configuration Table 3-2 shows the default IP address and default gateway configuration. Table 3-2 Switch IP Address and Default Gateway Default Configuration  Feature Default Value In-band (sc0) interface • IP address, subnet mask, and broadcast address set to 0.0.0.0 • Assigned to VLAN 1 Management Ethernet (me1) interface • IP address, subnet mask, and broadcast address set to 0.0.0.0 Default gateway address • Set to 0.0.0.0 with a metric of 0 SLIP (sl0) interface • IP address and SLIP destination address set to 0.0.0.0 • SLIP for the console port is not active (set to detach ) Setting the In-Band (sc0) Interface IP Address Before you can Telnet to the switch or use Simple Network Management Protocol (SNMP) to manage the switch, you must assign an IP address to either the in-band (sc0) logical interface or the management Ethernet (me1) interface. You can specify the subnet mask ( netmask ) using the number of subnet bits or using the subnet mask in dotted decimal format. To set the IP address and VLAN membership of the in-band (sc0) management interface, perform this task in privileged mode:   Task Command Step 1  Assign an IP address, subnet mask (or number of subnet bits), and (optional) broadcast address to the in-band (sc0) interface. set interface sc0 [ ip_addr [ / netmask ] [ broadcast ]] Step 2  Assign the in-band interface to the proper VLAN (make sure that the VLAN is associated with the network to which the IP address belongs). set interface sc0 [ vlan ] Step 3  If necessary, bring the interface up. set interface sc0 up Step 4  Verify the interface configuration. show interface This example shows how to assign an IP address, specify the number of subnet bits, and specify the VLAN assignment for the in-band (sc0) interface: Console> (enable) set interface sc0 172.20.52.124/29 Interface sc0 IP address and netmask set. Console> (enable) set interface sc0 5 Interface sc0 vlan set. Console> (enable) This example shows how to specify the VLAN assignment, assign an IP address, specify the subnet mask in dotted decimal format, and verify the configuration: Console> (enable) set interface sc0 5 172.20.52.124/255.255.255.248 Interface sc0 vlan set, IP address and netmask set. Console> (enable) show interface sl0: flags=51<UP,POINTOPOINT,RUNNING> slip 0.0.0.0 dest 0.0.0.0 sc0: flags=63<UP,BROADCAST,RUNNING> vlan 5 inet 172.20.52.124 netmask 255.255.255.248 broadcast 172.20.52.17 Console> (enable) Setting the Management Ethernet (me1) Interface IP Address Before you can Telnet to the switch or use SNMP to manage the switch, you must assign an IP address to either the in-band (sc0) logical interface or the management Ethernet (me1) interface. The me1 interface is present only on the Catalyst 4500 series, Catalyst 2948G, Catalyst 2948G-GE-TX, and Catalyst 2980G switches. You can specify the subnet mask ( netmask ) using the number of subnet bits or using the subnet mask in dotted decimal format. To set the management Ethernet (me1) interface IP address, perform this task in privileged mode:   Task Command Step 1  Assign an IP address and subnet mask to the management Ethernet (me1) interface. set interface me1 [ ip_addr [ / netmask ]] Step 2  If necessary, bring the interface up. set interface me1 up Step 3  Verify the interface configuration. show interface This example shows how to assign an IP address and subnet mask to the management Ethernet (me1) interface and how to verify the interface configuration: Console> (enable) set interface me1 172.20.52.12/255.255.255.224 Interface me1 IP address and netmask set. Console> (enable) show interface sl0: flags=51<UP,POINTOPOINT,RUNNING> slip 0.0.0.0 dest 0.0.0.0 sc0: flags=63<UP,BROADCAST,RUNNING> vlan 1 inet 0.0.0.0 netmask 0.0.0.0 broadcast 0.0.0.0 me1: flags=63<UP,BROADCAST,RUNNING> inet 172.20.52.12 netmask 255.255.255.224 broadcast 172.20.52.31 Console> (enable) Configuring Default Gateways The supervisor engine sends IP packets that are destined for other IP subnets to the default gateway (typically, a router interface in the same network or subnet as the switch IP address). The switch does not use the IP routing table to forward traffic from connected devices; the switch forwards only IP traffic that is generated by the switch (for example, Telnet, TFTP, and ping). Note In some cases, you might want to configure static IP routes in addition to default gateways. For information on configuring static routes, see the "Configuring Static Routes" section on page 27-9 . You can define up to three default IP gateways. Use the primary keyword to make a gateway the primary gateway. If you do not specify a primary default gateway, the first gateway that is configured is the primary gateway. If more than one gateway is designated as primary, the last primary gateway that is configured is the primary default gateway. The switch sends all off-network IP traffic to the primary default gateway. If connectivity to the primary gateway is lost, the switch attempts to use the backup gateways in the order that they were configured. The switch sends periodic ping messages to determine whether each default gateway is up or down. If connectivity to the primary gateway is restored, the switch resumes sending traffic to the primary gateway. If both the in-band (sc0) and management Ethernet (me1) interfaces are configured when you specify default gateways, then the switch software automatically determines through which interface each default gateway can be reached. To specify one or more default gateways, perform this task in privileged mode:   Task Command Step 1  Configure a default IP gateway address for the switch. set ip route default gateway [ metric ] [ primary ] Step 2  (Optional) Configure additional default gateways for the switch. set ip route default gateway [ metric ] [ primary ] Step 3  Verify that the default gateways appear correctly in the IP routing table. show ip route To remove default gateway entries, perform one of these tasks in privileged mode: Task Command Clear an individual default gateway entry. clear ip route default gateway Clear all default gateways and static routes. clear ip route all This example shows how to configure three default gateways on the switch and how to verify the default gateway configuration: Console> (enable) set ip route default 10.1.1.10 Route added. Console> (enable) set ip route default 10.1.1.20 Route added. Console> (enable) set ip route default 10.1.1.1 primary Route added. Console> (enable) show ip route Fragmentation Redirect Unreachable ------------- -------- ----------- enabled enabled enabled The primary gateway: 10.1.1.1 Destination Gateway RouteMask Flags Use Interface --------------- --------------- ---------- ----- -------- --------- default 10.1.1.1 0x0 UG 6 sc0 default 10.1.1.20 0x0 G 0 sc0 default 10.1.1.10 0x0 G 0 sc0 10.0.0.0 10.1.1.100 0xff000000 U 75 sc0 default default 0xff000000 UH 0 sl0 Console> (enable) This example shows how to configure two default gateways on a Catalyst 4500 series, Catalyst 2948G, Catalyst 2948G-GE-TX, or Catalyst 2980G switch, with one default gateway reachable through the sc0 interface and one reachable through the me1 interface: Console> (enable) show interface sl0: flags=50<DOWN,POINTOPOINT,RUNNING> slip 0.0.0.0 dest 0.0.0.0 sc0: flags=63<UP,BROADCAST,RUNNING> vlan 5 inet 172.20.52.38 netmask 255.255.255.240 broadcast 172.20.52.47 me1: flags=63<UP,BROADCAST,RUNNING> inet 10.1.1.100 netmask 255.255.255.0 broadcast 10.1.1.255 Console> (enable) set ip route default 172.20.52.33 Route added. Console> (enable) set ip route default 10.1.1.1 Route added. Console> (enable) show ip route Fragmentation Redirect Unreachable ------------- -------- ----------- enabled enabled enabled The primary gateway: 172.20.52.33 Destination Gateway RouteMask Flags Use Interface --------------- --------------- ---------- ----- -------- --------- default 10.1.1.1 0x0 G 0 me1 default 172.20.52.33 0x0 UG 12 sc0 172.20.52.32 4000-2 0xfffffff0 U 180 sc0 10.1.1.0 10.1.1.100 0xffffff00 U 22 me1 Console> (enable) Configuring the SLIP (sl0) Interface on the Console Port Use the SLIP (sl0) interface for point-to-point SLIP connections between the switch and an IP host. Caution You must use the console port for the SLIP connection. When the SLIP connection is enabled and SLIP is attached on the console port, an EIA/TIA-232 terminal cannot connect through the console port. If you are connected to the switch CLI through the console port and you enter the slip attach command, you will lose the console port connection. Use Telnet to access the switch, enter privileged mode, and enter the slip detach command to restore the console port connection. To enable and attach SLIP on the console port, perform this task:   Task Command Step 1  Access the switch from a remote host with Telnet. telnet { host_name | ip_addr } Step 2  Enter privileged mode on the switch. enable Step 3  Set the console port SLIP address and the destination address of the attached host. set interface sl0 slip_addr dest_addr Step 4  Verify the SLIP interface configuration. show interface Step 5  Enable SLIP for the console port. slip attach To disable SLIP on the console port, perform this task:   Task Command Step 1  Access the switch from a remote host with Telnet. telnet { host_name | ip_addr } Step 2  Enter privileged mode on the switch. enable Step 3  Disable SLIP for the console port. slip detach This example shows how to configure SLIP on the console port and verify the configuration: sparc20% telnet 172.20.52.38 Trying 172.20.52.38 ... Connected to 172.20.52.38. Escape character is '^]'. Cisco Systems, Inc. Console Enter password: Console> enable Enter password: Console> (enable) set interface sl0 10.1.1.1 10.1.1.2 Interface sl0 slip and destination address set. Console> (enable) show interface sl0: flags=51<UP,POINTOPOINT,RUNNING> slip 10.1.1.1 dest 10.1.1.2 sc0: flags=63<UP,BROADCAST,RUNNING> vlan 522 inet 172.20.52.38 netmask 255.255.255.240 broadcast 172.20.52.7 me1: flags=62<DOWN,BROADCAST,RUNNING> inet 10.1.1.100 netmask 255.255.255.0 broadcast 10.1.1.255 Console> (enable) slip attach Console Port now running SLIP. Console> (enable) slip detach SLIP detached on Console port. Console> (enable) Using DHCP or RARP to Obtain an IP Address Configuration Note For complete information on how the switch uses DHCP or RARP to obtain its IP configuration, see the "Understanding How Automatic IP Configuration Works" section . To use DHCP or RARP to obtain an IP address for the switch, perform this task:   Task Command Step 1  Make sure that there is a DHCP, BOOTP, or RARP server on the network. — Step 2  Obtain the last address in the MAC address range for module 1 (the supervisor engine). This address is displayed under the MAC-Address(es) heading. (With DHCP, this step is necessary only if using the manual allocation method.) show module Step 3  Add an entry for each switch in the DHCP, BOOTP, or RARP server configuration, mapping the MAC address of the switch to the IP configuration information for the switch. (With DHCP, this step is necessary only with the manual or automatic allocation methods.) — Step 4  Set the sc0 interface IP address to 0.0.0.0. set interface sc0 0.0.0.0 Step 5  Reset the switch. The switch broadcasts DHCP and RARP requests only when the switch boots up. reset system Step 6  When the switch reboots, confirm that the sc0 interface IP address, subnet mask, and broadcast address are set correctly. show interface Step 7  For DHCP, confirm that other options (such as the default gateway address) are set correctly. show ip route This example shows the switch broadcasting a DHCP request, receiving a DHCP offer, and configuring the IP address and other IP parameters according to the contents of the DHCP offer: Console> (enable) Sending RARP request with address 00:90:0c:5a:8f:ff Sending DHCP packet with address: 00:90:0c:5a:8f:ff dhcpoffer Sending DHCP packet with address: 00:90:0c:5a:8f:ff Timezone set to '', offset from UTC is 7 hours 58 minutes Timezone set to '', offset from UTC is 7 hours 58 minutes 172.16.30.32 added to DNS server table as primary server. 172.16.31.32 added to DNS server table as backup server. 172.16.32.32 added to DNS server table as backup server. NTP server 172.16.25.253 added NTP server 172.16.25.252 added %MGMT-5-DHCP_S:Assigned IP address 172.20.25.244 from DHCP Server 172.20.25.254 Console> (enable) show interface sl0: flags=51<UP,POINTOPOINT,RUNNING> slip 0.0.0.0 dest 0.0.0.0 sc0: flags=63<UP,BROADCAST,RUNNING> vlan 1 inet 172.20.25.244 netmask 255.255.255.0 broadcast 172.20.25.255 dhcp server: 172.20.25.254 Console> Renewing and Releasing a DHCP-Assigned IP Address If you are using DHCP for IP address assignment, you can perform either of these tasks: • Renew—Renew the lease on a DHCP-assigned IP address. • Release—Release the lease on a DHCP-assigned IP address. To renew or release a DHCP-assigned IP address on the in-band (sc0) management interface, perform one of these tasks in privileged mode: Task Command Renew the lease on a DHCP-assigned IP address. set interface sc0 dhcp renew Release the lease on a DHCP-assigned IP address. set interface sc0 dhcp release This example shows how to renew the lease on a DHCP-assigned IP address: Console> (enable) set interface sc0 dhcp renew Renewing IP address... Console> (enable) Sending DHCP packet with address: 00:90:0c:5a:8f:ff <...output truncated...> This example shows how to release the lease on a DHCP-assigned IP address: Console> (enable) set interface sc0 dhcp release Releasing IP address... Console> (enable) Sending DHCP packet with address: 00:90:0c:5a:8f:ff Done Console> (enable)

Was this Document Helpful?

Contact Cisco

• (Requires a Cisco Service Contract )