On A Nexus, Is The Metric-type Keyword Not Available In The “defaul

1.	On A Nexus, Is The Metric-type Keyword Not Available In The “default-information Originate” Command?
Answer» On a Nexus, USE a route-map COMMAND with a set clause of metric-type type-[½] in order to have the same functionality as in IOS USING the default-information originate always metric-type [½] command. For example: switch(config)#route-map STAT-OSPF, PERMIT, sequence 10switch(config-route-map) #match interface ethernet 1/2switch(config-route-map) #set metric-type {EXTERNAL \| internal \| type-1 \| type-2} On a Nexus, use a route-map command with a set clause of metric-type type-[½] in order to have the same functionality as in IOS using the default-information originate always metric-type [½] command. For example: switch(config)#route-map STAT-OSPF, permit, sequence 10switch(config-route-map) #match interface ethernet 1/2switch(config-route-map) #set metric-type {external \| internal \| type-1 \| type-2}

On A Nexus, Is The Metric-type Keyword Not Available In The “default-information Originate” Command?

Answer»

On a Nexus, USE a route-map COMMAND with a set clause of metric-type type-[½] in order to have the same functionality as in IOS USING the default-information originate always metric-type [½] command.

For example:

switch(config)#route-map STAT-OSPF, PERMIT, sequence 10switch(config-route-map) #match interface ethernet 1/2switch(config-route-map) #set metric-type {EXTERNAL | internal | type-1 | type-2}

On a Nexus, use a route-map command with a set clause of metric-type type-[½] in order to have the same functionality as in IOS using the default-information originate always metric-type [½] command.

For example:

switch(config)#route-map STAT-OSPF, permit, sequence 10switch(config-route-map) #match interface ethernet 1/2switch(config-route-map) #set metric-type {external | internal | type-1 | type-2}

Discussion

No Comment Found

Related InterviewSolutions

What Does The %oc_usd-slot18-2-rf_crc: Oc2 Received Packets With Crc Error From Mod 6 Through Xbar Slot 5/inst 1 Error Message Mean?
During Nexus 7010 Upgrade From 5.2.1 To 5.2.3 Code, The X-bar Module In Slot 4 Keeps Powering Off. The %module-2-xbar_diag_fail: Xbar 4 Reported Failure Due To Module Asic(s) Reported Sync Loss (deverr Is Linknum). Trying To Resync In Device 88 (device Error 0x0) Error Message Is Received.?
Is There A Best Practice For Port-channel Load Balancing Between Nexus 1000v Series And Nexus 7000 Series Switches?
How Do I Implement Vtp In A Nexus 7000 Series Switch Where Vlans Are Manually Configured?
How Do I Verify If Xl Mode Is Enabled On A Nexus 7000 Device?
Can A Nexus 7000 Be A Dhcp Server And Can It Relay Dhcp Requests To Different Dhcp Servers Per Vlan?
On A Nexus 7000 Running Nx-os 5.1(3), Can The Decnet Be Bridged On A Vlan?
How Do I Enable/disable Logging Link Status Per Port Basis On A Nexus 7000 Series Switch?
How Can I Avoid Receiving The "configuration Does Not Match The Port Capability" Error Message When Enabling "switchport Mode Fex-fabric"?
How Do I Avoid Receiving The "failed To Process Kickstart Image. Pre-upgrade Check Failed" Error Message When Upgrading The Image On A Nexus 7000 Series Switch?