MDS DS-SFP-FC8 GLW 9 Micron between 2 9148 switches Max DB loss?

                   Does anyone know where to find a table that would indciate what the max acceptable DB loss would be between two 9148 switches utilizing
                   DS-SFP-FC8 GLW over 9 Micron cable.
It seems the SFP product data sheets do not provide this type of data.
I currently have two 9148 switches running at 8Gbps
TE link 1 is up and running at 8Gbps with 32 bb credits assigned to the port.
TE link 2 will not stay online at any speed 2-8Gbps with 32 to 64 credits assigned. I'm fairly certain this is a DB loss problem becuase the problem follows the cable path.
What I'm trying to resolve is how to determine what the max DB loss is over the link.
I understand the max distance for Dark fiber is as follows: 1310nm  SMF 9.0 8.Gbps 10 km (6.2 mi)
So when I talk to folks that analyze the cables I can be eductaed on what the max DB loss is.
1310 SMF9.0 8.500 10 km (6.2 mi)
DB loss is as follows for TE link 1
Cable ID: 09 990
OTDR End1 PASSDate / Time: 10/02/2012 02:55:39pm
Cable Type: OS1 Singlemode
Tester: OptiFiber (9053014 V2.6.4)
Module: OFTM-5630 (9055001 V2.6.4)
Overall Length: 3706.8 ft
PASS
Overall Loss
PASS
1550 nm: 1.19 dB
PASS
ORL: < 32.32 dB1310 nm (n=1.4660) 1550 nm (n=1.4670)
Location Loss Status Loss Status
(ft) (dB) (dB)
0.0 N/A N/A N/A N/A
73.8 N/A N/A N/A N/A
246.1 0.30 N/A 0.74 N/A
334.6 N/A N/A N/A N/A
429.4 0.05 N/A N/A N/A
496.9 0.07 N/A N/A N/A
3573.9 0.48 N/A -0.01 N/A
3706.8 N/A N/A N/A N/A
OTDR End2 PASSDate / Time: 10/02/2012 01:51:32pm
Cable Type: OS1 Singlemode
Tester: OptiFiber (9053014 V2.6.4)
Module: OFTM-5630 (9055001 V2.6.4)
Overall Length: 3878.2 ft
PASS
Overall Loss
1310 nm: 1.24 dB
PASS
1550 nm: 0.80 dB
PASS
ORL: < 31.53 dBWARNING:
- Negative Loss value found in test result.1310 nm (n=1.4660) 1550 nm (n=1.4670)
Location Loss Status Loss Status
(ft) (dB) (dB)
0.0 N/A N/A N/A N/A
137.9 0.65 N/A 0.61 N/A
3464.1 -0.72 N/A N/A N/A
3612.5 N/A N/A N/A N/A
3640.2 1.00 N/A N/A N/A
3707.3 N/A N/A N/A N/A
3776.0 N/A N/A N/A N/A
3812.9 N/A N/A N/A N/A
3878.2 N/A N/A N/A N/A
Thanks,
Mike
OTDR End2 PASSDate / Time: 10/02/2012 01:55:57pm
Cable Type: OS1 Singlemode
Tester: OptiFiber (9053014 V2.6.4)
Module: OFTM-5630 (9055001 V2.6.4)
Overall Length: 3706.4 ft
PASS
Overall Loss
1310 nm: 1.34 dB
PASS
1550 nm: 0.79 dB
PASS
ORL: < 34.25 dB1310 nm (n=1.4660) 1550 nm (n=1.4670)
Location Loss Status Loss Status
(ft) (dB) (dB)
0.0 N/A N/A N/A N/A
138.0 0.46 N/A 0.17 N/A
303.8 N/A N/A 0.26 N/A
3464.5 0.47 N/A N/A N/A
3611.3 N/A N/A N/A N/A
3641.0 N/A N/A N/A N/A
3706.4 N/A N/A N/A N/A
Notice the 3.42 db loss overall loss occurs on the failing side of the cable link.
Cable ID: 09 990
OTDR End1 PASSDate / Time: 10/02/2012 02:57:16pm
Cable Type: OS1 Singlemode
Tester: OptiFiber (9053014 V2.6.4)
Module: OFTM-5630 (9055001 V2.6.4)
Overall Length: 3884.5 ft
PASS
Overall Loss
1310 nm: 3.42 dB
PASS
1550 nm: 0.75 dB
PASS
ORL: < 30.99 dB1310 nm (n=1.4660) 1550 nm (n=1.4670)
Location Loss Status Loss Status
(ft) (dB) (dB)
0.0 N/A N/A N/A N/A
73.0 N/A N/A N/A N/A
142.6 N/A N/A N/A N/A
245.7 0.04 N/A N/A N/A
331.9 N/A N/A N/A N/A
419.0 1.27 N/A N/A N/A
488.9 N/A N/A N/A N/A
501.1 N/A N/A N/A N/A
586.2 0.55 N/A N/A N/A
673.0 0.47 N/A N/A N/A
766.1 0.21 N/A N/A N/A
855.4 -0.01 N/A N/A N/A
959.0 0.19 N/A N/A N/A
3573.5 N/A N/A N/A N/A
3706.8 N/A N/A N/A N/A
3794.1 N/A N/A N/A N/A
3884.5 N/A N/A N/A N/A
1310 nm: 1.18 dB

I believe you run 'show interface fc x/y transceiver detail', it will provide the current light levels as well as the minimum and maximum limits.
Thank You,
Dan Laden

Similar Messages

  • Using Cisco MDS 9148 switch for switching and routing

    Hi Gurus,
    Can you please advice me! Can i configure interface trunking, routing and dhcp services on the Cisco MDS 9148 switch?
    Thanks for your response!!

    Tommy,
    MDS9148 is a Storage SAN Fibre Channel switch, it doesn't support Ethernet, IP, VLANs, VLAN trunking, 802.1Q, IP routing, DHCP. It's meant for Fibre Channel connectivity between Fibre Channel server HBAs and Fibre Channel storage.
    Roman

  • How to show module and SFP information include hardware serial number on Nexus switch?

       How to show module and SFP information include hardware serial number on Nexus switch?                 Thanks.

    Hi,
    The show inventory command will give you details of the Nexus chassis, power supplies, Supervisor, Fabric, I/O modules (including FEX if you have them) etc. To get the details of the installed SFP/SFP+ then you'll need to use the show interface transceiver command.
    Regards

  • Etherchannel between two 2950 switches

    I have a etherchannel defined between 2 L2 switches using LACP as shown below. The etherchannel works fine, however when I hard code speed/duplex on both ends the etherchannel fails. What is causing this behaviour?
    SW02:
    interface Port-channel5
    interface GigabitEthernet1/0/1
    switchport mode trunk
    channel-group 5 mode active
    interface GigabitEthernet1/0/2
    switchport mode trunk
    channel-group 5 mode active
    SW02:
    interface Port-channel5
    interface GigabitEthernet1/0/1
    switchport mode trunk
    channel-group 5 mode active
    interface GigabitEthernet1/0/2
    switchport mode trunk
    channel-group 5 mode active

    Thank you for the rating.
    Regarding your replacement scenario, I'll give the standard engineering answer ("it depends"), but actually follow up with something I hope is more helpful.    I'm sincerely interested to see other's viewpoint on this as well, as it has changed over the years.
    Many years ago (let's say a decade) I ran into problems with some devices not being able to auto-negotiate properly.  There was a tendancy for devices to fail or negotiate to half-duplex mode when a full-duplex connection was warranted.  At the time, the problems we experienced were mainly with traffic shaping devices and some other gear.  There were others using fixed settings as a standard practice, and we did the same since we had verifiable issues.
    Fast forward to now.  I personally have not experienced auto-negotiation problems in a long time and am reading more from others in the field that auto-negotiation is the way to go (such as from the link provided).  Indeed, I've now run into the opposite scenario: I had a particular situation where a link between two devices defaulted to half-duplex EVEN THOUGH they were both set to 100/Full.  It turned out to be a race condition between a device and a Cisco router...the other device booted faster, didn't see anything on the link, and "helpfully" dropped down to half-duplex.  I confirmed the issue with the device vendor, who recommended setting ports to auto-negotiate as the fix (their software would not be updated for a bit of time).
    I would recommend auto-negotiate as a standard practice, with the exception of areas where you have encountered specific problems.  Those latter cases should be caught through your pre-deployment testing, and discussed with the respective vendors so that you fully understand why the devices are behaving the way they are so that the proper mitigation measures can be put in place (i.e. - It is going to act the same way every time, and you can work with that).
    Good luck!  -Ed

  • Can use SFP-H10GB-CU3M to connect 6120XP to Cat6K Switch?

    Can use SFP-H10GB-CU3M OR SFP-H10GB-CU5M to connect 6120XP to Cat6K Switch?

    You dont have to connect to Nexus equipment. Your LAN can be anything as long as you can connect the UCS system to it.
    Currently you need a switch with 10GE ports to uplink from your 6100s.
    I believe that in the next version of the firmware/software in UCS you will be able to connect your 6100s to the LAN using 1G ports.
    Nuno Ferreira

  • Link vlan between 2 SG200 switches

    Hi,
    Trying to figure this one out...
    I have 2 SG200 50port switches connected together by fibre modules on port 50. The fibre is linking the switches between different buildings.
    I'm hoping to create the following connection route...
    Device -- SG200 Switch B Port 25 -- SG200 Switch B Fibre Port 50    ---Fibre Cable Between Buildings---    SG200 Switch A Fibre Port 50 -- SG200 Switch A Port 25 -- Cisco RV320 Router Port 3
    All ports are on the same vlan (20), untagged.
    Ultimately I'm trying to achieve a direct connection between 'Device' and 'RV320 router port 3', and have 'Device' pick up the DHCP configured for port 3's vlan (20).
    I've tried different configs of tagged and untagged, but no luck.
    Any advice would be greatly appreciated.
    Many thanks

    Hi Iamael,
    Thanks for getting back to me.
    Only ports 25 and 50 on both SG200 switches are on vlan20. All other ports are on the default vlan.
    I can't seem to achieve 20U on those 4 ports... only 20UP. The tick box to disable PVID is greyed out.
    Is the SG200 capable of routing vlan traffic between ports? Or would an SG300 L3 switch be required?
    Many thanks

  • HSRP between 2 access switches and 2 core switches

    Hi I am looking for running HSRP between 2 access switches and 2 core switches for client PC and Server network’s next-hop redundancy as per attached setup.
    As you can see I have used one /29 network for connecting CORE & ACCESS switches & configure Interface VLAN10 (Layer 3 SVI) with shown IPs and standby IP (VIP).G0/1 on Access Switches & G2/1 on Core Switches are access ports for VLAN10.
    There is a L2 Trunk interconnecting Core-Main/Backup & as well as Access-Main/Backup Switches allowing VLAN10 to allow VLAN10’s HSRP packets to pass through (apart from other HSRP instances).
    Below are the HRSP & Trunk configuration on Core and Access Switches please have a look and suggest if they are correct in term of HSRP implementation, as I can see on both side HSRP master & standby status are fine as desired, but I can’t ping VIP of ACCESS Switch from CORE switch, but the VIP of CORE switch I can ping from ACCESS switch.
    Access-Main
    interface GigabitEthernet0/1
     description ***Connected to CR-SW-01 PORT G2/1***
     switchport access vlan 10
     switchport mode access
     load-interval 30
    interface GigabitEthernet0/2
     description ***Connected to AC-SW-01 & AC-SW-02 for HRSP***
     switchport trunk encapsulation dot1q
     switchport trunk allowed vlan 10,40
     switchport mode trunk
     load-interval 30
    interface Vlan10
     description ***Connected to CR-SW-01 PORT G2/1***
     ip address 10.10.11.1 255.255.255.248
     standby 1 ip 10.10.11.2
     standby 1 timers msec 200 msec 750
     standby 1 preempt delay minimum 180
     standby 1 authentication accvlan10
    Access-Backup
    interface GigabitEthernet0/1
     description ***Connected to CR-SW-02 PORT G2/1***
     switchport access vlan 10
     switchport mode access
     load-interval 30
    interface GigabitEthernet0/2
     description ***Connected to AC-SW-01 & AC-SW-02 for HRSP***
     switchport trunk encapsulation dot1q
     switchport trunk allowed vlan 10,40
     switchport mode trunk
     load-interval 30
    interface Vlan10
     description ***Connected to CR-SW-02 PORT G2/1***
     ip address 10.10.11.3 255.255.255.248
     standby 1 ip 10.10.11.2
     standby 1 priority 10
     standby 1 timers msec 200 msec 750
     standby 1 preempt delay minimum 180
     standby 1 authentication accvlan10
    Core-Main
    interface GigabitEthernet2/1
     description ***Connected to AC-SW-01 PORT G0/1***
     switchport access vlan 10
     switchport mode access
     load-interval 30
    interface GigabitEthernet2/2
     description ***Connected to CR-SW-01 & CR-SW-02 for HRSP***
     switchport trunk encapsulation dot1q
     switchport trunk allowed vlan 10,20
     switchport mode trunk
     load-interval 30
    interface Vlan10
     description ***Connected to AC-SW-01 PORT G0/1***
     ip address 10.10.11.4 255.255.255.248
     standby 1 ip 10.10.11.5
     standby 1 timers msec 200 msec 750
     standby 1 preempt delay minimum 180
     standby 1 authentication crvlan10
    Core-Backup
    interface GigabitEthernet2/1
     description ***Connected to AC-SW-02 PORT G0/1***
     switchport access vlan 10
     switchport mode access
     load-interval 30
    interface GigabitEthernet2/2
     description ***Connected to CR-SW-01 & CR-SW-02 for HRSP***
     switchport trunk encapsulation dot1q
     switchport trunk allowed vlan 10,20
     switchport mode trunk
     load-interval 30
    interface Vlan10
     description ***Connected to AC-SW-02 PORT G0/1***
     ip address 10.10.11.6 255.255.255.248
     standby 1 ip 10.10.11.5
     standby 1 priority 10
     standby 1 timers msec 200 msec 750
     standby 1 preempt delay minimum 180
     standby 1 authentication crvlan10

    Hi Rick thanks once again, so I am assuming I should use to configure as below and still one /29 subnet I can use to connect these Switches with the above static routings.
    Access Switch-Main
    interface Vlan10
     description ***Connected to CR-SW-01 PORT G2/1***
     ip address 10.10.11.1 255.255.255.248
     standby 2 ip 10.10.11.2
     standby 2 timers msec 200 msec 750
     standby 2 preempt delay minimum 180
     standby 2 authentication accvlan10
    ip route 192.168.20.0 255.255.255.0 10.10.11.5
    Access Switch-Backup
    interface Vlan10
     description ***Connected to CR-SW-02 PORT G2/1***
     ip address 10.10.11.3 255.255.255.248
     standby 2 ip 10.10.11.2
     standby 2 priority 10
     standby 2 timers msec 200 msec 750
     standby 2 preempt delay minimum 180
     standby 2 authentication accvlan10
    ip route 192.168.20.0 255.255.255.0 10.10.11.5
    Core Switch -Main
    interface Vlan10
     description ***Connected to AC-SW-01 PORT G0/1***
     ip address 10.10.11.4 255.255.255.248
     standby 1 ip 10.10.11.5
     standby 1 timers msec 200 msec 750
     standby 1 preempt delay minimum 180
     standby 1 authentication crvlan10
    ip route 192.168.40.0 255.255.255.0 10.10.11.2
    Core Switch -Backup
    interface Vlan10
     description ***Connected to AC-SW-02 PORT G0/1***
     ip address 10.10.11.6 255.255.255.248
     standby 1 ip 10.10.11.5
     standby 1 priority 10
     standby 1 timers msec 200 msec 750
     standby 1 preempt delay minimum 180
     standby 1 authentication crvlan10
    ip route 192.168.40.0 255.255.255.0 10.10.11.2

  • Can anyone tell me the difference in performance between CSS URL switching

    first
    Can anyone tell me the difference in performance between CSS URL switching and F5 Big-IP?
    second
    Can anyone tell me the difference in performance between CSS URL switching and alteon ?
    third what is best overally?
    i think alteon is best
    is that right?
    best regard

    It looks like the primary question here is performance, in which case:Performance is not an issue, so long is it is sufficient. In the case of CSS 11000 and Alteon, performance fall within the same order of magnitude (supporting web sites with several billion hits per day.) F5 does not have sufficient performance, due to platform and OS limitations (I’ve heard as low as 50 connections per second in complex configurations). The Cisco CSM posts up over 10x the performance at 200k flows/second.
    Typically the primary concern is features, then CSS 11000 switches lead with a wide and flexible array of features that are not only helpful to network and web administrators, but well integrated too. CSS 11000 switches offer configuration through CLI, Web GUI, and XML. CSS 11000 collects statistics that can be exported to non-Cisco applications for billing and management.
    The CSS11000 also supports URL load balancing and HTTP header balancing within one content rule, with complex matching. Further, it supports user agent, pragma/no-cache, host field, cookie field, language field, accept, accept charset, accept-encoding, and Connection within the http header field.
    In addition, the CSS11000 matches up to 128 bytes with support of wildcards anywhere within the string.On the other hand, Nortel (Alteon) - HTTP header load balancing is not supported on the same VIP as URL load balancing. Eg. This means that a simulated WAP user cannot be directed to a server while load balancing "normal" browsers to their servers based on URL without using two separate VIPs. Only ONE http header load balance is supported on the entire switch. This limits you to either User Agent (WAP, Netscape, IE, Palm, etc), OR pragma/no cache (do not send the user to cache, allow (the user) to go to the origin), or Host field (allowing you to direct on domain name), or Cookie. Also, Nortel does not support the language field.
    In regards to F5, many of the performance claims are based on HTTP 1.0 requests (most web sites today are not using HTTP 1.0), Many emerging applications rely on HTTP 1.1 rather than HTTP 1.0. Also, the BIG-IP cannot spoof the connection to detect the URL, cannot do NAT on the flow, and cannot maintain states for persistent connections.
    Overall, I think CSS switches are the lowest cost to own, and most effective of all the load balancing platforms on the market.

  • Difference between vpc peer-switch and vpc+

    Hi, I would like to understand the difference between vpc peer-switch when used in vpc and vpc+ when used in fabricapath when both are delivered to achieve the same thing i.e making the 2 nexus switches look like a 1 logical switch to an other device connected to it.

    Hi,
    vPC+ overcomes a problem we would have when connecting non FabricPath devices to the FabricPath cloud in a resilient way using port-channels.
    If you look at the first diagram below, when Host A sends traffic to Host B, it can be sent over either link of the port-channel and so can take the path via either S100 or S200. The problem with this is that from the perspective of the MAC address table on S300, the MAC address of Host A would be constantly flap between being sourced from S100 and S200.
    What happens with vPC+ is that S100 and S200 create an emulated switch that effectively becomes the point of connection of the port-channel interface. This is seen in the second diagram as S1000. Now when traffic is sent from Host A it is always seen as originating from S1000 so there's no longer any MAC flapping.
    Hope that helps.
    Regards

  • Speed/Duplex between two different switchs & SFP

    Hi everybody,
    I'm sorry about my poor english... I'm French (but it is not contagious)
    I need your help (or TAC Help ) about speed and duplex problems.
    My network :
    [C2960G-24TC-L with sfp GLC-FE-100LX on Gig 0/23] <--> (Singlemode Fiber 9/125µ) <--> [Cisco SF200-24 with sfp MFELX1 on Gi1]
    Autonegociation everywhere...
    My problem :
    %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on GigabitEthernet0/23 (not full duplex), with f02929f97095 gi1 (full duplex).
    - I can't force speed/duplex on MFELX1 (actually a-full a-100)
    - I can't force speed/duplex on GLC-FE-100LX (actually a-half a-100)
    Is there an incompatibility between this equipements ?
    Configuration detail :
    WS-C2960G-24TC-L   12.2(58)SE2           C2960-LANBASEK9-M
    Cisco SF200-24 Firmware Version (Active Image):  1.2.9.44
    #sh int gig 0/23 capabilities
    GigabitEthernet0/23
      Model:                 WS-C2960G-24TC-L
      Type:                  100BaseLX-FE SFP
      Speed:                 100
      Duplex:                half,full
      Trunk encap. type:     802.1Q
      Trunk mode:            on,off,desirable,nonegotiate
      Channel:               yes
      Broadcast suppression: percentage(0-100)
      Flowcontrol:           rx-(off,on,desired),tx-(none)
      Fast Start:            yes
      QoS scheduling:        rx-(not configurable on per port basis),
                             tx-(4q3t) (3t: Two configurable values and one fixed.)
      CoS rewrite:           yes
      ToS rewrite:           yes
      UDLD:                  yes
      Inline power:          no
      SPAN:                  source/destination
      PortSecure:            yes
      Dot1x:                 yes
      Multiple Media Types:  rj45, sfp, auto-select
    #show int gigabitEthernet 0/23 transceiver properties
    Diagnostic Monitoring is not implemented.
    Name : Gi0/23
    Administrative Speed: auto
    Administrative Duplex: auto
    Administrative Auto-MDIX: on
    Administrative Power Inline: N/A
    Operational Speed: 100
    Operational Duplex: half
    Operational Auto-MDIX: on
    Media Type: 100BaseLX-FE SFP
    Configured Media: auto-select
    Active Media: sfp
    Thank you so much for yor help !

    Thank you Leo,
    It doesn't work, but I found an solution !
    A strange solution...
    I forced the C2960G-24TC-L to work with SFP :
    media-type sfp
    When I do that, I have the possibility to force the duplex (but not the speed... ok why not... ) :
    duplex full
    It is not very clean but my link is up and full-100 both sides.
    Not very clean because :
    C2960 side = force duplex, auto speed
    SF200 side = auto duplex, auto speed
    No errors... the link is clean.
    Anyone known the reason or a better solution ?

  • CISCO MDS 9124 SFP Compatibility

    We recently received a number of spare SFPs in case of failure of the installed items. After having installed one of these SFPs in our test bed we receive the following notification:
    %PORT-5-IF_DOWN_FCOT_VENDOR_NOT_SUPPORTED: %$VSAN 1%$ Interface fc1/1 is down (Error disabled - FCOT vendor not supported)
    On checking the online documentation we located the following:
    Error Message ETHPORT-5-IF_DOWN_FCOT_VENDOR_NOT_SUPPORTED: Interface [chars] is down (Error disabled - Fcot vendor not supported).
    Explanation The inserted small form-factor pluggable (SFP) device is not supported.
    Recommended Action Contact customer support for a list of authorized SFP vendors.
    Introduced Cisco MDS SAN-OS Release 1.2(2a).
    Does anyone know of any workarounds for this? Also does anyone know where we may locate a defnitive list of supported vendors [other than waiting on results from customer support].
    Thanks

    Hi Daniel,
    As far as I know, only Cisco SFPs are supported.
    Here is a link to the information on what SFPs are supported and where:
    Cisco MDS 9000 Family Pluggable Transceivers Data Sheet
    Best regards,
    Jim

  • What are the major differences between a Access Switch and Aggregation Switch w.r.t Carrier Ethernet domain?

    In a Carrier Ethernet domain,Could someone please help me understand what's the basic difference between Access Switch and Aggregation Switch both in terms of s/w and h/w functionalities. MEF deals OAM,CFM, EVC provisioning only at the access edge switches. Do we need to repeat all these at the aggregation level? or  is it just used for routing purpose? Do we have a separate Fault Management at the aggregation level?

    Duplicate posts.  :P
    Go here:  https://supportforums.cisco.com/discussion/12137156/what-are-major-differences-between-access-switch-and-aggregation-switch-wrt

  • Nexus 6004 EIGRP Relationship between the two switches

    Hi All,
    I will try to explain this as best as I can. In our current TEST LAB we have a Pair of Cisco ASA5585x running in Active/Passive mode. We use a VRF transit to connect the 10 GB interface to a Pair of Cisco Nexus 6004 (L3) switches running vPC between them. Downstream we also have a pair of Cisco 9372 switches (L2) also running vPC between the two.
    As of right now we have EIGRP neighbor relationship formed between the two N6K's and the ASA.
    ASA
    ciscoasa# sh eigrp neighbors
    EIGRP-IPv4 neighbors for process 100
    H Address Interface Hold Uptime SRTT RTO Q Seq
    (sec) (ms) Cnt Num
    1 172.16.230.9 Te0/8.451 12 01:30:25 1 200 0 52
    0 172.16.230.10 Te0/8.451 12 01:30:25 1 200 0 48
    The ASA formed relationship with both N6K's
    SWITCH1
    Nexus6-1# sh ip eigrp neighbors vrf inside
    IP-EIGRP neighbors for process 100 VRF Inside
    H Address Interface Hold Uptime SRTT RTO Q Seq
    (sec) (ms) Cnt Num
    0 172.16.8.3 Vlan680 11 01:28:28 1 50 0 45
    1 172.16.230.10 Vlan451 13 01:28:28 1 50 0 46
    2 172.16.230.11 Vlan451 10 01:28:00 4 50 0 13
    Nexus6-1#
    SWITCH2
    Nexus6-2# sh ip eigrp neighbors vrf Inside
    IP-EIGRP neighbors for process 100 VRF Inside
    H Address Interface Hold Uptime SRTT RTO Q Seq
    (sec) (ms) Cnt Num
    2 172.16.8.2 Vlan680 14 01:30:11 23 138 0 48
    0 172.16.230.9 Vlan451 13 01:30:11 480 2880 0 50
    1 172.16.230.11 Vlan451 13 01:29:48 1598 5000 0 13
    Nexus6-2#
    Both Nexus Switches formed EIGRP neighbors using the vPC Peer-Link. There is enough documentation out there that strongly suggest not to use vPC Peer-Links for EIGRP anything.
    We do have additional interfaces available on the 6K's that we can use as a cross connect for EIGRP. What we are having trouble understanding how we can force EIGRP traffic over those ports?
    Here is a complete Switch config:
    Switch1
    Nexus6-1# sh run
    feature telnet
    cfs eth distribute
    feature eigrp
    feature interface-vlan
    feature lacp
    feature vpc
    feature lldp
    vlan 1
    vlan 451
    name P2P_VRF_SVI
    vlan 652
    name Management
    vlan 680
    name Inside
    vrf context Inside
    vrf context management
    ip route 0.0.0.0/0 172.16.52.1
    vrf context peer-keepalive
    vpc domain 99
    role priority 1
    peer-keepalive destination 10.200.50.2 source 10.200.50.1 vrf peer-keepalive
    delay restore 120
    interface Vlan1
    interface Vlan451
    description Inside p2p to ASA
    no shutdown
    vrf member Inside
    ip address 172.16.230.9/29
    ip router eigrp 100
    no ip passive-interface eigrp 100
    interface Vlan651
    interface Vlan680
    description Inside Network
    no shutdown
    vrf member Inside
    ip address 172.16.8.2/22
    ip router eigrp 100
    interface port-channel99
    switchport mode trunk
    spanning-tree port type network
    vpc peer-link
    interface port-channel102
    switchport mode trunk
    vpc 102
    interface Ethernet1/1
    description vPC Peer Link 1.1
    switchport mode trunk
    speed auto
    channel-group 99
    interface Ethernet1/6
    interface Ethernet1/7
    description vPC Peer Link 1.7 to Nexus 9372 PRI
    switchport mode trunk
    speed auto
    channel-group 102 mode active
    interface Ethernet1/8
    interface Ethernet1/9
    interface Ethernet2/1
    description vPC Peer Link 2.1
    switchport mode trunk
    speed auto
    channel-group 99
    interface Ethernet2/2
    interface Ethernet2/7
    description vPC Peer Link 2.1 to Nexus SEC
    switchport mode trunk
    speed auto
    channel-group 102 mode active
    interface Ethernet2/8
    interface Ethernet8/1
    description keep-alive peer-link to ALNSWI02
    no switchport
    vrf member peer-keepalive
    ip address 10.200.50.1/30
    interface Ethernet8/2
    description Uplink to ASA
    switchport mode trunk
    interface Ethernet8/3
    interface mgmt0
    vrf member management
    ip address 172.16.52.3/23
    line console
    line vty
    boot kickstart bootflash:/n6000-uk9-kickstart.7.0.1.N1.1.bin
    boot system bootflash:/n6000-uk9.7.0.1.N1.1.bin
    router eigrp 100
    passive-interface default
    default-information originate
    vrf Inside
    autonomous-system 100
    default-information originate
    poap transit
    Nexus6-1#
    Nexus6-1# sh ip eigrp neighbors vrf inside
    IP-EIGRP neighbors for process 100 VRF Inside
    H Address Interface Hold Uptime SRTT RTO Q Seq
    (sec) (ms) Cnt Num
    0 172.16.8.3 Vlan680 11 01:28:28 1 50 0 45
    1 172.16.230.10 Vlan451 13 01:28:28 1 50 0 46
    2 172.16.230.11 Vlan451 10 01:28:00 4 50 0 13
    Nexus6-1#
    Nexus6-1# sh ip eigrp topology vrf Inside
    IP-EIGRP Topology Table for AS(100)/ID(172.16.8.2) VRF Inside
    Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
    r - reply Status, s - sia Status
    P 172.16.8.0/22, 1 successors, FD is 2816
    via Connected, Vlan680
    P 172.16.230.8/29, 1 successors, FD is 2816
    via Connected, Vlan451
    Nexus6-1# sh vpc
    Legend:
    (*) - local vPC is down, forwarding via vPC peer-link
    vPC domain id : 99
    Peer status : peer adjacency formed ok
    vPC keep-alive status : peer is alive
    Configuration consistency status : success
    Per-vlan consistency status : success
    Type-2 consistency status : success
    vPC role : primary
    Number of vPCs configured : 1
    Peer Gateway : Disabled
    Dual-active excluded VLANs : -
    Graceful Consistency Check : Enabled
    Auto-recovery status : Disabled
    vPC Peer-link status
    id Port Status Active vlans
    1 Po99 up 1,451,652,680
    vPC status
    id Port Status Consistency Reason Active vlans
    102 Po102 up success success 1,451,652,6
    80
    Nexus6-1# sh spanning-tree
    VLAN0001
    Spanning tree enabled protocol rstp
    Root ID Priority 32769
    Address 1005.caf5.88ff
    Cost 2
    Port 4197 (port-channel102)
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Bridge ID Priority 32769 (priority 32768 sys-id-ext 1)
    Address 8c60.4f2d.2ffc
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Interface Role Sts Cost Prio.Nbr Type
    Po99 Desg FWD 1 128.4194 (vPC peer-link) Network P2p
    Po102 Root FWD 1 128.4197 (vPC) P2p
    Eth8/2 Desg FWD 2 128.1026 P2p
    Eth8/3 Desg FWD 2 128.1027 P2p
    VLAN0451
    Spanning tree enabled protocol rstp
    Root ID Priority 33219
    Address 8c60.4f2d.2ffc
    This bridge is the root
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Bridge ID Priority 33219 (priority 32768 sys-id-ext 451)
    Address 8c60.4f2d.2ffc
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Interface Role Sts Cost Prio.Nbr Type
    Po99 Desg FWD 1 128.4194 (vPC peer-link) Network P2p
    Po102 Desg FWD 1 128.4197 (vPC) P2p
    Eth8/2 Desg FWD 2 128.1026 P2p
    VLAN0652
    Spanning tree enabled protocol rstp
    Root ID Priority 33420
    Address 1005.caf5.88ff
    Cost 2
    Port 4197 (port-channel102)
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Bridge ID Priority 33420 (priority 32768 sys-id-ext 652)
    Address 8c60.4f2d.2ffc
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Interface Role Sts Cost Prio.Nbr Type
    Po99 Desg FWD 1 128.4194 (vPC peer-link) Network P2p
    Po102 Root FWD 1 128.4197 (vPC) P2p
    Eth8/2 Desg FWD 2 128.1026 P2p
    VLAN0680
    Spanning tree enabled protocol rstp
    Root ID Priority 33448
    Address 1005.caf5.88ff
    Cost 2
    Port 4197 (port-channel102)
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Bridge ID Priority 33448 (priority 32768 sys-id-ext 680)
    Address 8c60.4f2d.2ffc
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Interface Role Sts Cost Prio.Nbr Type
    Po99 Desg FWD 1 128.4194 (vPC peer-link) Network P2p
    Po102 Root FWD 1 128.4197 (vPC) P2p
    Eth8/2 Desg FWD 2 128.1026 P2p
    Nexus6-1#
    Switch2
    Nexus6-2# sh run
    !Command: show running-config
    !Time: Sat Feb 12 19:02:44 2011
    version 7.0(1)N1(1)
    hostname Nexus6-2
    feature telnet
    cfs eth distribute
    feature eigrp
    feature interface-vlan
    feature lacp
    feature vpc
    feature lldp
    vlan 1
    vlan 451
    name P2P_VRF_SVI
    vlan 652
    name Management
    vlan 680
    name Inside
    vrf context Inside
    vrf context P2P_Inside_VRF
    vrf context management
    ip route 0.0.0.0/0 172.16.52.1
    vrf context peer-keepalive
    vpc domain 99
    role priority 2
    peer-keepalive destination 10.200.50.1 source 10.200.50.2 vrf peer-keepalive
    delay restore 120
    interface Vlan1
    interface Vlan451
    description Inside p2p to ASA
    no shutdown
    vrf member Inside
    ip address 172.16.230.10/29
    ip router eigrp 100
    no ip passive-interface eigrp 100
    interface Vlan680
    description Inside Network
    no shutdown
    vrf member Inside
    ip address 172.16.8.3/22
    ip router eigrp 100
    interface port-channel99
    switchport mode trunk
    spanning-tree port type network
    vpc peer-link
    interface port-channel102
    switchport mode trunk
    vpc 102
    interface Ethernet1/1
    description vPC Peer Link 1.1
    switchport mode trunk
    speed auto
    channel-group 99
    interface Ethernet1/2
    interface Ethernet1/6
    interface Ethernet1/7
    description vPC Link 1.7 to Nexus 9372 SEC
    switchport mode trunk
    speed auto
    channel-group 102 mode active
    interface Ethernet1/8
    interface Ethernet1/12
    interface Ethernet2/1
    description vPC Peer Link 2.1
    switchport mode trunk
    speed auto
    channel-group 99
    interface Ethernet2/2
    interface Ethernet2/6
    interface Ethernet2/7
    description vPC Link 2.1 to Nexus PRI
    switchport mode trunk
    speed auto
    channel-group 102 mode active
    interface Ethernet2/8
    interface Ethernet2/12
    interface Ethernet8/1
    description keep-alive peer-link to ALNSWI01
    no switchport
    vrf member peer-keepalive
    ip address 10.200.50.2/30
    interface Ethernet8/2
    description Uplink to ASA
    switchport mode trunk
    switchport trunk allowed vlan 1,451,652,680
    interface Ethernet8/3
    interface Ethernet8/20
    interface mgmt0
    vrf member management
    ip address 172.16.52.4/23
    line console
    line vty
    boot kickstart bootflash:/n6000-uk9-kickstart.7.0.1.N1.1.bin
    boot system bootflash:/n6000-uk9.7.0.1.N1.1.bin
    router eigrp 100
    vrf Inside
    autonomous-system 100
    default-information originate
    poap transit
    logging logfile messages 6
    Nexus6-2#
    Nexus6-2#
    Nexus6-2# sh ip eigrp neighbors vrf Inside
    IP-EIGRP neighbors for process 100 VRF Inside
    H Address Interface Hold Uptime SRTT RTO Q Seq
    (sec) (ms) Cnt Num
    2 172.16.8.2 Vlan680 14 01:30:11 23 138 0 48
    0 172.16.230.9 Vlan451 13 01:30:11 480 2880 0 50
    1 172.16.230.11 Vlan451 13 01:29:48 1598 5000 0 13
    Nexus6-2#
    Nexus6-2# sh ip eigrp topology vrf Inside
    IP-EIGRP Topology Table for AS(100)/ID(172.16.8.3) VRF Inside
    Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
    r - reply Status, s - sia Status
    P 172.16.8.0/22, 1 successors, FD is 2816
    via Connected, Vlan680
    P 172.16.230.8/29, 1 successors, FD is 2816
    via Connected, Vlan451
    Nexus6-2#
    Nexus6-2#
    Nexus6-2# sh vpc
    Legend:
    (*) - local vPC is down, forwarding via vPC peer-link
    vPC domain id : 99
    Peer status : peer adjacency formed ok
    vPC keep-alive status : peer is alive
    Configuration consistency status : success
    Per-vlan consistency status : success
    Type-2 consistency status : success
    vPC role : secondary
    Number of vPCs configured : 1
    Peer Gateway : Disabled
    Dual-active excluded VLANs : -
    Graceful Consistency Check : Enabled
    Auto-recovery status : Disabled
    vPC Peer-link status
    id Port Status Active vlans
    1 Po99 up 1,451,652,680
    vPC status
    id Port Status Consistency Reason Active vlans
    102 Po102 up success success 1,451,652,6
    80
    Nexus6-2#
    Nexus6-2#
    Nexus6-2# sh spanning-tree
    VLAN0001
    Spanning tree enabled protocol rstp
    Root ID Priority 32769
    Address 1005.caf5.88ff
    Cost 3
    Port 4194 (port-channel99)
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Bridge ID Priority 32769 (priority 32768 sys-id-ext 1)
    Address 8c60.4f2d.777c
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Interface Role Sts Cost Prio.Nbr Type
    Po99 Root FWD 1 128.4194 (vPC peer-link) Network P2p
    Po102 Root FWD 1 128.4197 (vPC) P2p
    Eth8/2 Desg FWD 2 128.1026 P2p
    Eth8/3 Desg FWD 2 128.1027 P2p
    VLAN0451
    Spanning tree enabled protocol rstp
    Root ID Priority 33219
    Address 8c

    Jon,
    Are you ready for the mass confusion?
    when Looking at the ASA EIGRP neighbors output here is what I see.
    ASA# sh eigrp neighbors
    EIGRP-IPv4 neighbors for process 100
    H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq
                                                (sec)         (ms)       Cnt Num
    3   172.16.230.1            Te0/8.450        13  16:45:14 1    200   0   64
    2   172.16.230.2            Te0/8.450        11  16:45:14 1    200   0   84
    1   172.16.230.10           Te0/8.451        11  16:45:20 1    200   0   178
    0   172.16.230.9            Te0/8.451        13  16:45:20 1    200   0   148
    For simplicity sake lets just concetrate on Interface TenGigabit0/8.451 which is the SVI on the Nexus switch that is VLAN451
    From the Nexus Switch 6004 that is directly connected to the ASA here is what I see
    SWI01# sh ip eigrp neighbors vrf Inside
    IP-EIGRP neighbors for process 100 VRF Inside
    H   Address                 Interface       Hold  Uptime  SRTT   RTO  Q  Seq
                                                (sec)         (ms)       Cnt Num
    0   172.16.8.3              Vlan680         10   17:04:30  54   324   0   177
    1   172.16.230.10           Vlan451         11   16:59:10  819  4914  0   178
    2   172.16.230.11           Vlan451         14   16:53:48  24   144   0   20
    The Inside VRF that is tied to both SVI's on the Switch vlans 451 and 680 is in EIGRP 100 on the switch
    SWI01# sh run int vlan 451
    interface Vlan451
      description Inside p2p to ASA
      no shutdown
      vrf member Inside
      ip address 172.16.230.9/29
      ip router eigrp 100
      no ip passive-interface eigrp 100
    SWI01# sh run int vlan 680
    interface Vlan680
      description Inside Network
      no shutdown
      vrf member Inside
      ip address 172.16.8.2/22
      ip router eigrp 100
      hsrp 1
        authentication text test
        preempt
        priority 250
        ip 172.16.8.1
    so you with me so far?
    If you are you have noticed that on the ASA neighbors the ASA sees 172.16.230.11 as a neighbor which is the Secondary Nexus SW. That is becauise they all share the same subnet.
    172.16.230.8/29
    Brakedown:
    PRI Nexus 6004 - 172.16.230.9
    SEC NEXUS 6004 - 172.16.230.10
    PRI ASA 5585x  - 172.16.230.11
    SEC ASA 5585x  - 172.16.230.12
    Because the ASA EIGRP network is a /29 it learns the Secondary Nexus via the Primary Nexus.
    I am not sure that the link we created between the two Nexus Switches is doing anything but consuming ports right now.
    SWI01# sh run int ethernet 8/9
    interface Ethernet8/9
      description EIGRP PORT to Secondary Nexus
      switchport mode trunk
      switchport trunk allowed vlan 450-451
    SWI02# sh run int ethernet 8/9
    interface Ethernet8/9
      description EIGRP PORT to Primary Nexus
      switchport mode trunk
      switchport trunk allowed vlan 450-451
    So the SVI's that go up to the ASA for inspection are 450 and 451. The network SVI's are 600 and 680 all of them live on the switch, and 680, and 600 are extended over the peer links down to the 9372's.
    I think that we are breaking the golden rule of vPC BUT.. I am not 100% sure. Some of the documents read that we should not be allowing network vlans over peer links, but then how do you extend the vlans down to the leaf switch?
    This is giving me nightmares at the moment…
    does this make sense? 

  • No link between Sg200-26 switch and netgear gs1081 v2switch

    Hi everyone,
    Would someone be kind enough to guide me through my problem. I am a newbie and dont know much about networking more so other technical stuff like trunking, vlans etc....
    there is no connection (no link activity) betwen my cisco sg200-26  switch and a netgear gs108T switch which i have purchased recently. Whereas, a link is automatically  obtained if i connect the sg 200 to an unmanged asus ASUS Gx-D1081 V2.. Any help  would be greatly appreciated.
    Thanks very much in advance
    Isaac

    Hi Isaac, can you describe the physical port behavior between the switches? Does the link lights turn on at either switch?
    Are you able to manage either switch locally? (connect your computer to either switch and log in to the supported access method?)
    -Tom
    Please mark answered for helpful posts

  • SFP (Cisco GLC-SX-MM) unknown in cisco switch 2960s

    I have cisco switch WS-C2960S-24TS-S with IOS 12.2(55)SE8  C2960S-UNIVERSALK9-M when I connect the SFP Cisco GLC-SX-MM to the interface the switch does not know it .
    Switch#sh interfaces gig0/25 status
    Port      Name               Status       Vlan       Duplex  Speed Type
    Gi0/25                       err-disabled 1            auto   auto unknown

    Switch(config)#int gigabitEthernet 0/25
    Switch(config-if)#sho
    Switch(config-if)#shu
    Switch(config-if)#shutdown
    Switch(config-if)#do sh
    *Mar  1 00:08:10.481: %LINK-5-CHANGED: Interface GigabitEthernet0/25, changed state to administratively down ip int br
    Interface              IP-Address      OK? Method Status                Protocol
    Vlan1                  unassigned      YES unset  up                    up
    FastEthernet0          unassigned      YES unset  down                  down
    GigabitEthernet0/1     unassigned      YES unset  down                  down
    GigabitEthernet0/2     unassigned      YES unset  down                  down
    GigabitEthernet0/3     unassigned      YES unset  down                  down
    GigabitEthernet0/4     unassigned      YES unset  down                  down
    GigabitEthernet0/5     unassigned      YES unset  down                  down
    GigabitEthernet0/6     unassigned      YES unset  down                  down
    GigabitEthernet0/7     unassigned      YES unset  down                  down
    GigabitEthernet0/8     unassigned      YES unset  down                  down
    GigabitEthernet0/9     unassigned      YES unset  down                  down
    GigabitEthernet0/10    unassigned      YES unset  down                  down
    GigabitEthernet0/11    unassigned      YES unset  down                  down
    GigabitEthernet0/12    unassigned      YES unset  down                  down
    GigabitEthernet0/13    unassigned      YES unset  down                  down
    GigabitEthernet0/14    unassigned      YES unset  down                  down
    GigabitEthernet0/15    unassigned      YES unset  down                  down
    GigabitEthernet0/16    unassigned      YES unset  down                  down
    GigabitEthernet0/17    unassigned      YES unset  down                  down
    GigabitEthernet0/18    unassigned      YES unset  down                  down
    GigabitEthernet0/19    unassigned      YES unset  down                  down
    GigabitEthernet0/20    unassigned      YES unset  down                  down
    GigabitEthernet0/21    unassigned      YES unset  down                  down
    GigabitEthernet0/22    unassigned      YES unset  down                  down
    GigabitEthernet0/23    unassigned      YES unset  down                  down
    GigabitEthernet0/24    unassigned      YES unset  up                    up
    GigabitEthernet0/25    unassigned      YES unset  administratively down down
    GigabitEthernet0/26    unassigned      YES unset  down                  down
    Switch(config-if)#no shut
    Switch(config-if)#
    *Mar  1 00:08:30.326: %LINK-3-UPDOWN: Interface GigabitEthernet0/25, changed state to down
    Switch(config-if)#
    Switch#show ip int brief
    Interface              IP-Address      OK? Method Status                Protocol
    Vlan1                  unassigned      YES unset  up                    down
    FastEthernet0          unassigned      YES unset  down                  down
    GigabitEthernet0/1     unassigned      YES unset  down                  down
    GigabitEthernet0/2     unassigned      YES unset  down                  down
    GigabitEthernet0/3     unassigned      YES unset  down                  down
    GigabitEthernet0/4     unassigned      YES unset  down                  down
    GigabitEthernet0/5     unassigned      YES unset  down                  down
    GigabitEthernet0/6     unassigned      YES unset  down                  down
    GigabitEthernet0/7     unassigned      YES unset  down                  down
    GigabitEthernet0/8     unassigned      YES unset  down                  down
    GigabitEthernet0/9     unassigned      YES unset  down                  down
    GigabitEthernet0/10    unassigned      YES unset  down                  down
    GigabitEthernet0/11    unassigned      YES unset  down                  down
    GigabitEthernet0/12    unassigned      YES unset  down                  down
    GigabitEthernet0/13    unassigned      YES unset  down                  down
    GigabitEthernet0/14    unassigned      YES unset  down                  down
    GigabitEthernet0/15    unassigned      YES unset  down                  down
    GigabitEthernet0/16    unassigned      YES unset  down                  down
    GigabitEthernet0/17    unassigned      YES unset  down                  down
    GigabitEthernet0/18    unassigned      YES unset  down                  down
    GigabitEthernet0/19    unassigned      YES unset  down                  down
    GigabitEthernet0/20    unassigned      YES unset  down                  down
    GigabitEthernet0/21    unassigned      YES unset  down                  down
    GigabitEthernet0/22    unassigned      YES unset  down                  down
    GigabitEthernet0/23    unassigned      YES unset  down                  down
    GigabitEthernet0/24    unassigned      YES unset  down                  down
    GigabitEthernet0/25    unassigned      YES unset  down                  down
    GigabitEthernet0/26    unassigned      YES unset  down                  down
    Switch#
    Mar  1 00:07:55.508: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi0/25 has bad crc
    *Mar  1 00:07:55.508: %PM-4-ERR_DISABLE: gbic-invalid error detected on Gi0/25, putting Gi0/25 in err-disable state
    *Mar  1 00:08:24.003: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi0/25 has bad crc
    *Mar  1 00:08:39.144: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi0/25 has bad crc
    Mar  1 00:24:18.611: %GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port Gi0/25 has bad crc
    *Mar  1 00:24:18.611: %PHY-4-UNSUPPORTED_TRANSCEIVER: Unsupported transceiver found in Gi0/25

Maybe you are looking for

  • Unable to connect with Database server in MDM

    Hi Experts, I have installed the MDM server 7.1 on windows 64 bit box, but installed MDM console (32 bit). Getting the issue like below Can anybody please help me out to fix the issue. Thanks in advance, Bhaskar N

  • How to add colors from one doc to another in CS2

    I thought I could pull a text frame with text and colors in fill background out to the sideboard to create a snippet but it didn't work. Is this only in CS3? or what is the easiest way to transfer swatches between docs?

  • Time sheet Display through CAT3

    Hi, We are using Cross application time sheets and expense sheet entry in SAP. We have the following issue, can someone please help out to sort it. When we go to the Expense sheet (PR05) through the CAT 2 transaction code (Aeroplane Sign) we see the

  • Purchase requisition with MRP controller

    Hi everybody, I need support because I have to control during purchase requisition to block users with specific MRP controller. I mean, user A only have permission to create purchase requisition with MRP controller Z and user B only have permission t

  • Has anyone been able to combine OpenGL ES with another View controller?

    Looking at all the sample code, I still can't find any example of combining OpenGL ES with another View controller. So that one could have a view that the user could input values, and another that draws OpenGL ES stuff in. Is this possible, or does o