# SRGB Modifcation Load **basic.isis.sr.enabled.cfg** ``` configure load bootflash:basic.isis.sr.enabled.cfg commit replace y ``` SR is already enabled using ISIS. Modify the SRGB on R3 so that the range is 30000-30999. Modify the SRGB on R5 so that the range is 50000-50999. Use two different methods to solve this task. ## Answer ``` #R3 segment-routing global-block 30000 30999 #R5 router isis 1 segment-routing global-block 50000 50999 ``` ## Explanation The SRGB is a local range on each node from which global SIDs are assigned MPLS labels. By default this range is 16,000-23,999. Each node advertises its SRGB into the IGP, allowing for different SRGBs on each node. We can configure the SRGB in two places: globally under SR, and under the individual IGP process. ``` #R3 segment-routing global-block 30000 30999 #R5 router isis 1 segment-routing global-block 50000 50999 ``` As you might imagine, this is a heirarchical configuration. The IGP inherits the SRGB from the globally configured block. By configuring the SRGB under the individual IGP, it allows you to use a different SRBG per IGP instance on a single node. The IGP configuration overrides the global configuration. We can verify the LSD (label switch database) using the following command:

* Labels 0-15 are reserved * 0 = IPv4 explicit null * 1 = router alert * 2 = IPv6 explicit null * 3 = IPv4 implicit null * Labels 16-14999 are used for static labels * Labels 15000-15999 are the SRLB (by default) * Labels 16000-23999 are the SRGB (by default) * R3 has altered this to 30000-30999 in the screenshot above * Labels 24000-max are dynamic labels * If the SRGB uses up this range, it displaces dynamic labels. So for R3, the dynamic label range is now 24000-29999, 31000-max. We can verify the default dynamic label min and max values using the following command:

#### Verification We can see the current SRGB used by the ISIS process with the following show command:

The command **show isis segment-routing label table** displays the local global prefix label values on that particular node. For example, on R3, we see each value as \ + \:

Each node advertises its SRGB into the IGP, which allows all nodes in the IGP to calcualte the correct global label value for a given prefix SID for every other node in the IGP.

This allows R1 to program a swap for 16007 to 30007, for example:

If we traceroute to this prefix, we see that R1 uses R3’s correct global label, and R3 uses R5’s correct global label:

The global SID prefixes no longer are globally signficant in terms of label value. Instead, global SID prefixes are only globally significant in terms of index value. If you retain the default SRGB on all nodes, then global SID prefixes will also have globally significant label values. This is always the preferred deployment method. SR supports non-global SRGBs in the network, but it is always easier to just use the same SRBG on all nodes. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://ccie-sp.gitbook.io/ccie-spv5.1-labs/labs/sr/srgb-modifcation.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.